Oracle FS1-2 Flash Storage System
 

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

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-13576381471>

Applies to:

Symptoms

Outwardly, the upper Controller shows an ID of 1 and the lower Controller shows an ID of 2.  An examination of the topology output (see Document 1970990.1 FS System: How to Read and Interpret the FS1-2 CLI Topology Command) shows that Controller 1 is connected to Input/Output Module (IOM) 1 and Controller 2 is connected to IOM 0:

Changes

Initially, this will not adversely affect the overall operation of the FS1-2.  However, it can have a negative affect when attempting to troubleshoot system issues or adding new Drive Enclosures.  If detected during an installation, it is strongly recommended to resolve this issue before going into production.

Cause

Upon initial power up of a newly assembled FS1-2, the first Controller to boot up, regardless of its position, will be Controller 1.  This is then written to the Configuration On Disk (COD) so that it remains constant in future system reboots.

Solution

If this problem is observed in an FS1-2, please contact Oracle Support for guidance on how to fix.

There are currently two ways to fix this issue, both of which mandate an outage:

• Physically swap the two Controllers
• COD reset the system (wipes out all data) with upper Controller (#2) powered off until Controller 1 is seen on the Private Management Interface (PMI).

Physical Swap of Controllers:

This method is only recommended if there is customer data involved as it involves the disconnection of all the cables from both Controllers.  In turn, this opens the door to miscabling when they are reconnected.  This document will cover the basic steps at a high level.  For additional hardware specific details it is recommended to review KM Document 1939732.1 FS System: How to Access the Internal Field Service Guides.  It is recommended that, due to the weight of each Controller, that either a mechanical lift or a second person be used to avoid injury.

1. Perform a shutdown of the FS1-2 - see KM Document 2015681.1 FS System: How to Power Off and Power On the Oracle FS1-2 Flash Storage System.
2. Deploy the anti-tip legs in the front of the rack.
3. Move the upper Controller into the service position.
4. Disconnect all external cables from the rear.  These cables are labeled in the factory, but if there are not labels, it is recommend this be done to ease in reconnection.
5. Press the appropriate release tabs to remove the Controller from their rails.
6. Return the rail extensions back into rack to provide safer access to the lower Controller.
7. Repeat step 4 through 6 for the lower Controller.
8. Reattach the Controller removed in steps 4 & 5 to the lower rails.
9. Reconnect the Controller cables and slide back into the rack.
10. Extend the rails for the upper Controller.
11. Reattach the Controller removed in step 7 to the upper rails.
12. Reconnect the Controller cables and slide back into the rack.
13. Return the anti-tip legs to their normal position.
14. From the Oracle Flash Storage Manager GUI, restart the system.

COD Reset:

1. Power off the upper Controller by removing both power cords.
2. Execute a COD reset of the FS1-2.  See KM Document 2029729.1 FS System: How to Perform a System COD Reset.
3. Once the Pilots are back on the customer LAN, enable ssh.  See KM Document 2029847.1 FS System: How to Enable SSH Access to the Pilot.
4. Ssh to the active Pilot and cd to /var/log.
5. Monitor the pcp.log file until you see Controller 1 (172.30.80.128) in the node matrix:
   
   [root@pilot1 log]# tailf pcp.log
   2016-11-15 20:18:43.795 pilot1 pilotcfgproc: 30854704 16575 pcp:info  node           2          3      
   2016-11-15 20:18:43:795 pilot1 pilotcfgproc: 30854705 16575 pcp:info    2:   1 (  4  6  0)(  0  6  0)
   2016-11-15 20:18:43:795 pilot1 pilotcfgproc: 30854706 16575 pcp:info    3:   1 (  0  6  0)(  0  6  0)
   2016-11-15 20:18:43:795 pilot1 pilotcfgproc: 30854707 16575 pcp:info  255:     (  0  6  0)(  0  6  0)
   ...
   2016-11-15 20:32:54.050 pilot1 pilotcfgproc: 30879651 16575 pcp:info  node           2          3        128
   2016-11-15 20:32:54.050 pilot1 pilotcfgproc: 30879652 16575 pcp:info    2:   1 (  4  6  0)(  0  6  0)( 20  6  0)
   2016-11-15 20:32:54.050 pilot1 pilotcfgproc: 30879653 16575 pcp:info    3:   1 (  0  6  0)(  0  6  0)( 20  6  0)
   2016-11-15 20:32:54.050 pilot1 pilotcfgproc: 30879654 16575 pcp:info  128:   1 ( a0  3  0)( a0  3  0)( c0  3  0)
   2016-11-15 20:32:54.050 pilot1 pilotcfgproc: 30879655 16575 pcp:info  255:     (  0  6  0)(  0  6  0)(  0  6  0)
   
    
6. Power on the upper Controller (#2) and continue to monitor pcp.log until Controller 2 (172.30.80.129) is seen:
   
   2016-11-15 20:39:23.161 pilot1 pilotcfgproc: 30894544 16575 pcp:info  node           2          3        128
   2016-11-15 20:39:23.161 pilot1 pilotcfgproc: 30894545 16575 pcp:info    2:   1 (  4  6  0)(  0  6  0)( 20  6  0)
   2016-11-15 20:39:23.161 pilot1 pilotcfgproc: 30894546 16575 pcp:info    3:   1 (  0  6  0)(  0  6  0)( 20  6  0)
   2016-11-15 20:39:23.161 pilot1 pilotcfgproc: 30894547 16575 pcp:info  128:   1 ( a0  6  0)( a0  6  0)( c0  6  0)
   2016-11-15 20:39:23.161 pilot1 pilotcfgproc: 30894548 16575 pcp:info  255:     (  0  6  0)(  0  6  0)(  0  6  0)
   ...
   2016-11-15 20:42:53.218 pilot1 pilotcfgproc: 30901630 16575 pcp:info  node           2          3        128        129
   2016-11-15 20:42:53.218 pilot1 pilotcfgproc: 30901631 16575 pcp:info    2:   1 (  4  6  0)(  0  6  0)( 20  6  0)( 20  6  0)
   2016-11-15 20:42:53.218 pilot1 pilotcfgproc: 30901632 16575 pcp:info    3:   1 (  0  6  0)(  0  6  0)( 20  6  0)( 20  6  0)
   2016-11-15 20:42:53.218 pilot1 pilotcfgproc: 30901633 16575 pcp:info  128:   1 ( a0  6  0)( a0  6  0)( c0  6  0)( 20  6  0)
   2016-11-15 20:42:53.218 pilot1 pilotcfgproc: 30901634 16575 pcp:info  129:   1 ( 20  3  1)( 20  3  0)( 20  3  0)(  0  3  0)
   2016-11-15 20:42:53.218 pilot1 pilotcfgproc: 30901635 16575 pcp:info  255:     (  0  6  0)(  0  6  0)(  0  6  0)(  0  6  0)
    
7. When Controller 2 completes its boot process, confirm that the Controller IDs are correct (1 for the lower Controller, 2 for the upper).

References

This solution has no attachment