Oracle FS1-2 Flash Storage System
 

PLA-Support>Sun Systems>DISK>Flash Storage>SN-EStor: FSx
 
Tools>Type>Information Center
 

In this Document

Goal

Solution

Requirements Before Powering Off

Shut Down the FS1-2

Using the Oracle FS System Manager GUI:

Using the Oracle System Manager CLI:

Powering off the FS1-2

Powering On the FS1-2

References

Applies to:

Goal

This document details how to power off and on the Oracle FS1-2 system.

Solution

Whenever possible, it is ALWAYS better to gracefully shutdown the system before removing power cords from the entire FS1-2 system or any of its individual components.  This will minimize any potential problems during the subsequent reboot.  Oracle also recognizes that this may not always be possible depending on the current state of the system.  While there is always a proper order in which to power down the FS1-2 hardware components, it is extremely important to do so when a proper shutdown cannot be completed.  A failed shutdown may result in “pinned data” in memory which, if not properly handled, may result in data loss.  Oracle strongly recommends that in this event, customers should first consult with Oracle Support.  If the system is being powered down for relocation, Oracle also recommends that Oracle Support be engaged.

There are 4 power/operational states for the FS1-2:

• Running – System is fully functioning as an FS1-2.
• Shutdown – FS1-2 is in shutdown and no IO is possible.
• Stand-by (ILOM) – Only ILOMs are accessible.
• Power Off – all power is off to the FS1-2.

Requirements Before Powering Off

Before attempting to power off the FS1-2, ensure the following conditions are met:

• System is in Normal state.
  • GUI:
    From the System tab, select System Information and check status.
  • CLI:
    # fscli system -list -status
    
    System
        Name                         : fs1-2
        SystemStatus                 : NORMAL 
    
    
• System has no Background Tasks running.
  
  • GUI:
    Click on the Tasks button in the lower right corner.
  • CLI:
    # fscli task -list
    /GetOperation/1395/administrator
            Status        : IN_PROCESS
    # fscli task -list
    /GetOperation/1395/administrator
            Status        : COMPLETED
    /GetOperation/1398/administrator
            Status        : IN_PROCESS
    
    
    
    NOTE: this command will always capture itself.  To confirm that this is the only task running, rerun the command and it should show up as COMPLETED and that second run will show up as IN_PROCESS.
    
    
    
• Quiesce all I/O streams.
  
  • GUI:
    From the SAN tab, select Statistics and Trending then LUNs to make sure IOPs for Reads and Writes are zero.
  • CLI:
    
    # fscli statistics -list -lun
    
    LunStatistics
        Lun
            Fqn                : /LUN4
            Id                 : 414B303031323639A10421CAECEBB9F3
        CollectionTime
            StartTime          : 2016-02-26T17:20:59.187+00:00
            EndTime            : 2016-02-26T17:23:05.483+00:00
        TotalIoPerSecond                              : 0.000
        ReadIoPerSecond                               : 0.000
        WriteIoPerSecond                              : 0.000
        TotalBytesPerSecond                           : 0.000
        ReadBytesPerSecond                            : 0.000
        WriteBytesPerSecond                           : 0.000
        TotalLatency                                  : 0.000
        ReadLatency                                   : 0.000
        WriteLatency                                  : 0.000
        TotalBlockSize                                : 0.000
        ReadBlockSize                                 : 0.000
        WriteBlockSize                                : 0.000
        TotalQueueDepth                               : 0.000
        ReadQueueDepth                                : 0.000
        WriteQueueDepth                               : 0.000
        CacheHitRatio                                 : 0.000
        CacheFlushesPerSecond                         : 0.000
        NonOptimizedIoPerSecond                       : 0.000
    ...
     
    
    NOTE: it can take up to 15 minutes for the IOs to be written from cache to disks.
    
    
    
• While not always required, it is advisable to use the CLI to clear the failure history of the Controllers prior to powering down.  This is especially true if the system in question has had any recent problems with its Controllers.
   
  
  1. Login to the system using the pillar account:
     
     # fscli login -u pillar -oracleFs <fs-system IP>
     command succeeded
      
  2. Clear failure history on both Controllers:
     
     # fscli controller –reenable
     command succeeded

Shut Down the FS1-2

The Oracle FS1-2 Flash Storage System is composed of many hardware components and software processes that have inter-dependencies. To ensure they are satisfied and that the system can be powered down safely, the system must first be shut down. When the system is in a shut down state, the GUI is still accessible, albeit with limited functionality.  This can be done from either the Oracle FS System Manager GUI or CLI.  After the software is shutdown, it is safe to remove AC from the system.

Using the Oracle FS System Manager GUI:

1. From Oracle FS System Manager (GUI), select Oracle FS > Shut Down.
   
   
   
   The system displays the Confirm Shut Down dialog.
    
2. Read the information on the Confirm Shut Down dialog.
3. To shut down the system, click OK.  The system status icon changes to a yellow triangle with the message: Prepare for Shutdown. The system continues to shutdown all of the software processes; however the GUI remains running.
4. After the software is shutdown, the System Information page displays Shutdown.
5. Event Log shows System shutdown succeeded
   
   

Using the Oracle System Manager CLI:

1. Run command
   # fscli system -shutdown
   Command Succeeded
    
2. Check status
   # fscli system -list -status
   System
       Name                         : fs1-2
       SystemStatus                 : SHUTDOWN

Powering off the FS1-2

Proper care must be exercised so as to only power off components associated with the FS1-2 and in the proper order.  Many times an FS1-2 will be sharing its rack with data hosts and other devices.  Using breakers in the rack Power Distribution Units (PDUs) to power off the FS1-2 may inadvertently also power off these devices or the FS1-2 components in the incorrect order.

• For systems running R6.2.11 or higher, you can use the power button in the front of the Pilots and Controllers to put those components in stand-by mode:
1. Controllers: press the power button on both Controllers for about 1 second.  The green OK LED should transition to a slow blink (every 3-5 seconds) and the red Critical LED should become lit.
   
   • If the power connections to the PDU are such that using them will ONLY power off the Controllers, use those breakers to remove AC power from the Controllers.
   • If the power connections to the PDU are such that they share a common breaker with only the Pilots (and nothing else), do nothing at this time. The breaker can be used in the next step.
   • If the power connections to the PDU are such that they share a common breaker with other devices in the rack, it will be necessary to remove the actual power cords either from the Controllers themselves or from the PDUs.
     
     
2. Pilots: press and hold the power button on both Pilots for about 5-7 seconds.  The green OK LED should transition to a slow blink (every 3-5 seconds).
   • If the power connections to the PDU are such that using them will ONLY power off the Pilots, use those breakers to remove AC power from the Pilots.
   • If the power connections to the PDU are such that they share a common breaker with only the Controllers (and nothing else), use the breaker to remove AC power from the Controllers and Pilots at the same time.
   • If the power connections to the PDU are such that they share a common breaker with other devices in the rack, it will be necessary to remove the actual power cords either from the Pilots themselves or from the PDUs.
      
3. Drive Enclosures: from the rear of the system, turn off both power supply switches for each Drive Enclosure.
    
• For systems running R6.2.10 or lower, do NOT use the power button in the front of the Pilots and Controllers. 
  • Controllers:
    • If the power connections to the PDU are such that using them will ONLY power off the Controllers, use those breakers to remove AC power from the Controllers.
    • If the power connections to the PDU are such that they share a common breaker with only the Pilots (and nothing else), do nothing at this time. The breaker can be used in the next step.
    • If the power connections to the PDU are such that they share a common breaker with other devices in the rack, it will be necessary to remove the actual power cords either from the Controllers themselves or from the PDUs.
       
  • Pilots:
    • If the power connections to the PDU are such that using them will ONLY power off the Pilots, use those breakers to remove AC power from the Pilots.
    • If the power connections to the PDU are such that they share a common breaker with only the Controllers (and nothing else), use the breaker to remove AC power from the Controllers and Pilots at the same time.
    • If the power connections to the PDU are such that they share a common breaker with other devices in the rack, it will be necessary to remove the actual power cords either from the Pilots themselves or from the PDUs.
       
  • Drive Enclosures: from the rear of the system, turn off both power supply switches for each Drive Enclosure.

Powering On the FS1-2

After the system has been powered down, wait at least 5 minutes before powering the system back on.  This is to ensure all disks have adequately spun down.

• Drive Enclosures:
  • Power on the Drive Enclosures by turning on both switches on the power supplies of each.
  • Wait approximately 2 minutes for the drives to spin up. Confirm that all the Drive Enclosure components are green before proceeding.
     
• Pilots:
  • If the power cords were disconnected in the power down steps, plug them back in.
  • If the breakers were used to power down the Pilots and/or Controllers, power them back on.
     
• Controllers:
  • If the power cords were disconnect in the power down steps, plug them back in.
  • If the breakers were used to power down the Controllers, switch them back on.
     
• Monitor the system startup in the GUI
  
  NOTE: The booting process takes 20 to 30 minutes to complete.  If the boot gets hung in Cold Start, see Document 2107904.1 FS System: FS1-2 May Not Complete Cold Start When Both Pilots are Powered on Simultaneously for resolution. 

 Helpful information about LED status:

SP/OK Off = no power
SP/OK = slow blink (3-5 seconds) ILOM/Host in stand-by
SP/OK = fast blink (every second) ILOM/Host booting
SP/OK ON = ILOM/Host booted

This solution has no attachment