Oracle FS1-2 Flash Storage System
 
Oracle FS1-2 Cloud System
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: DISK-CAP VCAP
 

Instructions on how to replace disk backplane in an X5-2 FS1-2 Pilot.

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU

Applies to:

Goal

Outline the steps required to replace a FS1-2 Pilot disk backplane using Guided Maintenance.

Solution

DISPATCH INSTRUCTIONS

- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:

Product knowledge, FS1-2 Flash Storage System

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 2

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: 

FS1-2 Pilot disk backplane.

What: A Pilot disk backplane in an FS1-2 has failed and needs to be replaced. 

Where: A failed disk backplane will have a System Alert for the affected Pilot. 

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?

The Pilot with the disk backplane failure will likely have a warning status but depending on how severe the damage is, the entire Pilot itself may be in a missing state.  The other Pilot must have a normal status as this procedure may require a Pilot failover so that the problem Pilot can be powered off in order to replace the failed disk backplane.

 QRC for this procedure:

WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:

1. Confirm Product Serial Number Containers (PSNCs) are currently synchronized.
1. Use ssh to access the good Pilot, not the one having the disk backplane replaced (root/a1s2d3f$ login/password).
   
   # fscli system -modify -enableSsh 30   
2. Use ssh to access the bad Pilot's ILOM.
   
   [root@pilot2 ~]# ssh 169.254.2.9
   Password:
   
   Oracle(R) Integrated Lights Out Manager
   
   Version 3.2.4.42 r99377
   
   Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
   
   Warning: password is set to factory default.
   
   ->
    
   
   
   NOTE: using the IP address of 169.254.2.9 will ALWAYS connect you to the other Pilot's ILOM.  In the example above, starting from Pilot 2, the connection is being made to Pilot 1's ILOM.
   
   
   
3. Enter restricted session mode and run the showpsnc command.
   
   -> set SESSION mode=restricted
   
   WARNING: The "Restricted Shell" account is provided solely
   to allow Services to perform diagnostic tasks.
   
   [(restricted_shell) ORACLESP-1516NM118D:~]# showpsnc
   Primary: fruid:///SYS/DBP0
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary           | Backup1           | Backup2
   ------------------+-------------------+-------------------+-------------------
   PPN                 7095032             7095032             7095032
   PSN                 1516NM118D          1516NM118D          1516NM118D <==== Product Serial Numbers must match.
   Product Name        ORACLE SERVER X5-2  ORACLE SERVER X5-2  ORACLE SERVER X5-2
   [(restricted_shell) ORACLESP-1516NM118D:~]#
    
   
   
4. If all 3 PSNs match, exit all the way out of the FS1-2 and proceed to step 2.
5. If the Motherboard (MB) and Power Supply 0 (PS0) are the same but Disk BackPlane (DBP0) is different, it is safe to proceed to step 2 since the disk backplane will be replaced.
6. If any other condition exists, STOP!! and re-engage the TSC for steps to correct before proceeding to replace the failed disk backplane.
   
   
2. Prepare FS1-2 for service procedure.
1. Disable Call-Home to prevent spurious alerts (see Document 1942676.1 FS System: How to disable Call Home to prevent Automatic Service Request ASR Generation).
2. Use ESD precautions.
3. Log into Oracle FS System Manager to access Guided Maintenance:
1. Select System tab
2. In the navigation tree, expand Hardware and select Pilots
3. In the main window, right click on the Pilot with the failed disk backplane and select Repair Pilot.
4. In the pop-up Repair window, select Disk backplane followed by the Next button.
5. Follow the steps in Guided Maintenance to identify and place the Pilot offline.
   
   
3. Access the Pilot disk backplane.
1. Deploy the anti-tip legs in the front of the rack.
2. Slide the Pilot into the service position.
3. Unplug both power cords.
4. Disconnect Pilot boot drive and all drive fillers from the backplane.
5. Remove the 6 screws that hold the drive cage cover, then open fan door and remove cover by sliding it forward. 
   
6. From left to right, disconnect the SAS 0-3, DBP data, SAS 4-7 and power cables from disk backplanes - suggest that they be labeled to make reconnections easier.
   
   
4. Remove failed disk backplane.
1. Loosen the captive screw on the right side that secures the backplane in place.
2. Lift the metal spring on the left side and tilt the backplane top towards the rear.
3. Once the top of the backplane is clear, lift it from the Pilot chassis.
   
   
5. Install replacement disk backplane.
1. Lift the metal spring on the right side and tilt the replacement backplane into place. 
2. Lower the backplane into place using the 3 metal hooks spread across the middle.  There are also six troughs that the bottom of the backplane will fit into when it is properly in place.
3. Tighten thecaptive screw.
4. Plug in the DBP data, SAS and power cables into the backplane.
   
   
   NOTE: Check to see if an Oracle System Assistant (OSA) USB drive is installed internally on the Pilot motherboard.  If one is installed, proactively remove it.  While having the OSA USB drive installed does not affect day to day operations of the FS1-2, it will create problems if the Pilot needs to be re-imaged in the future.
   
   
   
6. Reassemble Pilot components.
1. Reinstall the drive cage cover and secure it in place with the 6 screws removed earlier.
2. Insert the Pilot boot drive into slot 0 (lower left) and populate the remaining slots with filler panels.
3. Reinstall the fan modules into their slots.
4. Close the fan door.
   
   
7. Return Pilot to FS1-2 System.
1. Plug in both power cords.
2. Return the Pilot to the rack position.
3. Return the anti-tip legs to their normal position.
4. Once the Pilot has completed it's reboot, repeat step 1 to verify that the PSN of the replacement motherboard is synchronized to the other two quorum devices.
5. When finished, re-enable Call-Home.

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

 Confirm the System Alert associated previously is gone and the FS1-2 status is normal/green.

REFERENCE INFORMATION:

 From the Oracle Help Center: http://docs.oracle.com/en/storage/#fla select the Oracle Flash System Documentation Library for more information.

References

This solution has no attachment