Oracle FS1-2 Flash Storage System
 

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

Instructions on how to replace disk backplane in an 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 an 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:

If you are not very familiar with servicing the Sun Server X4-2 upon which the Pilot is based, it is highly recommended that you look at the animation videos that detail the replace procedures covered in this CAP.  They are available at the Oracle Server Animations.

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).
1. Software versions prior to R6.1.12 had ssh enabled from the factory. For versions R6.1.12 and newer, it can be enabled using fscli (30 minutes in this example):
   
   # 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.1.2.10.b r77700
   
   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-1307FML0VY:~]# showpsnc
   Primary: fruid:///SYS/DBP0
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary           | Backup1           | Backup2
   ------------------+-------------------+-------------------+-------------------
   PPN                 7056044             7056044             7056044
   PSN                 1307FML0VY          1307FML0VY          1307FML0VY <==== Product Serial Numbers must match.
   Product Name        SUN FIRE X4170 M3   SUN FIRE X4170 M3   SUN FIRE X4170 M3
   [(restricted_shell) ORACLESP-1307FML0VY:~]#
    
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 (PDB0) 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. Open fan door and remove all 4 fan modules.
   
   
   NOTE: The FS1-2 Pilot has two disk backplanes but only the bottom one is used.
     
6. From left to right, disconnect the signal, flex and power cables from both disk backplanes - suggest that they be labeled to make reconnections easier.
   
      
4. Remove failed disk backplane.
1. Loosen the two captive screws that secure the backplane in place.
2. Slide the backplane towards the front of the Pilot until it can be lifted clear of the mushroom tabs at each end and in the middle of the backplane.
3. Repeat for the bottom backplane.
   
   
   NOTE: accessing the captive screws of the bottom backplane may be difficult due to the screw holes of the top backplane.  It may be necessary to use pliers or something similar to start the loosening process followed by using your fingers to finish the job.
     
   
   
5. Install replacement disk backplane.
1. Align the three mushroom tabs with their slotted holes and then push the bottom backplane towards the rear of the Pilot.  Care should be taken not to damage the front panel status cable on the left side.
2. Tighten the two captive screws.
3. Plug in the signal, SAS and power cables into the bottom backplane.
4. Align the three mushroom tabs with their slotted holes and then push the top backplane towards the read of the Pilot.  Care should be taken not to damage the signale cable  on the left side.
5. Tighten the two captive screws.
6. Plug in the signal, flex and power cables into the top backplane.
   
   
   NOTE: Be particularly careful with the flex cable on the left as it can be easily damaged.  Bad connections may cause the boot drive not to be seen and thus the Pilot won't boot.
    
6. Reassemble Pilot components.
1. Insert the Pilot boot drive into slot 0 (lower left) and populate the remaining slots with filler panels.
2. Reinstall the fan modules into their slots.
3. 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