Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2106834.1
Update Date:2018-04-18
Keywords:

Solution Type  Technical Instruction Sure

Solution  2106834.1 :   FS System: How to Warmstart the Controller Master Node  


Related Items
  • Oracle FS1-2 Flash Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
  •  




In this Document
Goal
Solution
References


Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

This document provides the instructions on how to warmstart the FS1-2 Controller master node.

Solution

One Controller acts as the Master Node. An election between all the Controllers takes place (the number of Controllers does not matter) during the ColdStart of the FS1 (boot) or when the Master Node is power cycled, fully restarted (not a warmstart) or is being Disabled.

IMPORTANT: Do NOT warmstart the master or any node unless you have instructions from Oracle Support.


The Master Node can be identified using the fscli (no option on the Axiom GUI). FSCLI is available on the webserver running on the FS1: open a web browser on the virtual IP address.

Prerequisites:
"fscli" is a requirement to execute the commands below. Refer to <Document 1991938.1> FS System: How to Obtain and Install the fscli Tool Software. It is necessary to login as user pillar to run the following commands.

 

  1. Login to the FS1-2 using the pillar account:

    $ fscli login -u pillar -oracleFS <IP shared address>
     
  2. Use fscli to find the Controller master node:

    $ fscli controller -list -master
    Master
        Fqn : /CONTROLLER-01
        Id  : 508002000158BA50

        /CONTROLLER-01
        /CONTROLLER-02 

    The master node is /CONTROLLER-01 in the above example.

  3. Clear failure history:

    $ fscli controller –reenable

      Command Succeeded

    Clear Failure History is run to clear the internal counter. The controller will disable if the controller warmstarts 3 times in one hour.

  4. Using the information from step 2 above, warmstart the master node:

    $ fscli controller –reset –controller /CONTROLLER-0X
     

    Example:
    $ fscli controller -reset -controller /CONTROLLER-01

    Command Succeeded

    The warmstart takes less than 5 seconds to run. From the step 2, the /CONTROLLER-01 is the master node

  5. Clear failure history again:

    $ fscli controller –reenable

      Command Succeeded
      


    The failure history and list of excluded Controllers is kept in /var/lib/pillar/pcp/node-info.xml on the Active Pilot.
    After issuing "fscli controller -reenable", none of the nodes in this file should have a status of "true" for either excluded or disabled and the failure_count should be 0.

    Example:
    [root@pilot2 ~]# more /var/lib/pillar/pcp/node-info.xml

    <?xml version="1.0" encoding="UTF-8" ?>
    <node_list>
    <cold_start_failure_count>0</cold_start_failure_count>
    <node>
    <wuName>WNxxxx0</wuName>
    <excluded>false</excluded>
    <disabled>false</disabled>
    <failure_count>0</failure_count>
    </node>
    <node>
    <wuName>WNxxxx1</wuName>
    <excluded>false</excluded>
    <disabled>false</disabled>
    <failure_count>0</failure_count>
    </node>
    </node_list>
    [root@pilot2 ~]#

    [This section is not visible to customers.]

References

<NOTE:2046703.1> - FS System: Passwords Associated with the Oracle FS1-2 Flash Storage System

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback