Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 

In this Document

Goal

Solution

FSCLI OPTION

POWER CORD OPTION

PSG_SHUTDOWN OPTION

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Requires access to restricted access resources. Not intended for customers.

Applies to:

Goal

This document provides the instructions that allow an Oracle support engineer to reboot an FS1-2 Controller. 

Solution

There are three methods that can be used to reboot a Controller.  They are listed here in their order of preference:

• fscli - requires that the Controller(s) be visible from the CLI.
• Power cord removal - requires physical access to the system.
• psg_shutdown - Controller utility.

FSCLI OPTION

When attempting to recover a Controller, the first option should always be the fscli.  The fscli has two methods, rebooting a specific Controller or restarting the entire FS1-2 system.  This second method will result in an outage and should also include the first so as to ensure that the failure history is cleared.

1. Using fscli to reboot a specific Controller:
   
   # fscli login -u pillar -oracleFs <ip_address_of_FS1-2>
   Password: ********
   
   Login Successful
   
   *****************************************************
   **                                                 **
   **  This is a company computer system with access  **
   **  restricted to those with proper authorization. **
   **  Authorized parties are restricted to those     **
   **  functions which have been assigned to perform  **
   **  work related duties.  Any unauthorized access  **
   **  will be investigated and prosecuted to the     **
   **  full extent of the law.  If you are not an     **
   **  authorized user, disconnect now.               **
   **                                                 **
   *****************************************************    
   
   # fscli controller -list
   
   /CONTROLLER-01
   /CONTROLLER-02
   
   # fscli controller -reenable
   
   Command Succeeded
   
   # fscli controller -forceFailure -controller /CONTROLLER-01
   
   Command Succeeded
   
   #
     
   
   
2. Using fscli to restart the FS1-2 system:
   # fscli login -u pillar -oracleFs <ip_address_of_FS1-2>
   Password: ********
   
   Login Successful
   
   *****************************************************
   **                                                 **
   **  This is a company computer system with access  **
   **  restricted to those with proper authorization. **
   **  Authorized parties are restricted to those     **
   **  functions which have been assigned to perform  **
   **  work related duties.  Any unauthorized access  **
   **  will be investigated and prosecuted to the     **
   **  full extent of the law.  If you are not an     **
   **  authorized user, disconnect now.               **
   **                                                 **
   *****************************************************    
   
   # fscli system restart
   #
     

POWER CORD OPTION

If neither Controller is on the PMI, remove a four power cords (2 from each Controller).  If the problem exists on only one Controller, care should be taken to remove only the power cords from that Controller.  Since the bad Controller will not be on the PMI, only the good Controller can be identified.  This can be done from the GUI or fscli:

• GUI:
  1. Login into the Oracle FS System Manager as administrator
  2. From the System tab, expand Hardware in the navigation tree on the left and select Controllers.
  3. In the main window will be the good Controller that is still visible on the PMI.
     NOTE: if both Controllers are seen, use the fscli commands in the previous section to recover.
       
  4. Right click on it and select Identify.
  5. In the pop-up window select the radio button next to Identify.  This will turn on the white locator LEDs in the front and rear of the Controller.
  6. With the good controller identified, power cords can be pulled from the other Controller.
     
     
• fscli:
  1. Login to the fscli as administrator
  2. List the Controllers that can be seen.
     NOTE: if both Controllers are seen, use the fscli commands in the previous section to recover.
      
  3. Turn on the Controller beacon.
     Example of turning on the beacon for Controller 1:
     # fscli login -u administrator -oracleFs <ip_address_of_FS1-2>
     The current userid on this client has not yet logged out. Continuing with this login request will logout the existing session, and all subsequent commands from this
     userid will use the new login information. Proceed with login (y/N)?
     y
     Password: ********
     
     Login Successful
     

     *****************************************************
     **                                                 **
     **  This is a company computer system with access  **
     **  restricted to those with proper authorization. **
     **  Authorized parties are restricted to those     **
     **  functions which have been assigned to perform  **
     **  work related duties.  Any unauthorized access  **
     **  will be investigated and prosecuted to the     **
     **  full extent of the law.  If you are not an     **
     **  authorized user, disconnect now.               **
     **                                                 **
     *****************************************************

     
     # fscli controller -list
     /CONTROLLER-01
     
     # fscli controller -beacon -controller /CONTROLLER-01 -powerSupply 0
     Command Succeeded
     #
      
     
  4. With the good controller identified, power cords can be pulled from the other Controller.

PSG_SHUTDOWN OPTION

/usr/bin/psg_shutdown is a utility located in the Controller and has been successfully used many times in the past.  Due to the possible negative consequences of improper usage, only the -b, -p and -r options are provided.  Execution of pas_shutdown should not be used unless directed to do so by Engineering:

It takes several minutes for a Controller that has been powered on to boot. First it will boot with its built in WWN and issue a DHCP request to obtain the system specific WWN.  Then it issues another DHCP request using that WWN to obtain a PMI IP address, and then uses that IP address to request the download of the runtime OS and Apps image from the Pilot. 

This solution has no attachment