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 a Controller Power Distribution Board in an FS1-2.

In this Document

Goal

Solution

References

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

Applies to:

Goal

The purpose of this document is to outline the steps required to replace an FS1-2 Controller Power Distribution Board (PDB) using the Guided Maintenance.

Solution

DISPATCH INSTRUCTIONS

- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:

Product knowledge, FS1-2 Flash Storage System

TIME ESTIMATE: 75 minutes

TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW:

What: A Controller PDB in an FS1-2 has failed and needs to be replaced. 

Where: There will be a System Alert that identifies the problem Controller. 

Why: An FS1-2 Controller PDB has failed.

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

Depending on the severity of the PDB failure, the Controller with the PDB failure may just have a warning status because of incorrect temperatures being reported or the Controller may have no power at all.  The other Controller must have a normal status as this procedure requires a Controller failover.  The problem Controller must be powered off in order to replace the failed PDB.

  
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 active Pilot (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 good Controller
   
   
   [root@pilot1 ~]# cat /etc/nodenames
   172.30.80.2 WN2008fffffffffff2 WN2008000101000000 mgmtnode
   172.30.80.128 WN508002000158ba50 WN2008000101000001  <==== Controller 1
   172.30.80.129 WN508002000158ba51                     <==== Controller 2
   172.30.80.3 WN2009fffffffffffa
   [root@pilot2 ~]# ssh 172.30.80.128
   WN508002000158BA50 #
    
   
   
   NOTE: the example above is the output expected when you have two good working Controllers in order to show the IP addresses of both Controllers.  The ssh command is being used to access Controller 1.  The WWN of that Controller will be the prompt.
    
   
   
3. Use ssh to access the bad Controller's ILOM.
   
   
   WN508002000158BA50 # ssh 169.254.2.9
   Password:
   
   Oracle(R) Integrated Lights Out Manager
   
   Version 3.1.2.40 r93718
   
   Copyright (c) 2014, 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 Controller's ILOM.  In the example above, starting from Controller 1, the connection is being made to Controller 2's ILOM.
   
   
   
4. 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-1315FMxxxx:~]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PDB
   
   Element           | Primary           | Backup1           | Backup2
   ------------------+-------------------+-------------------+-------------------
   PPN                 70893370            70893370            70893370
   PSN                 1315FMxxxx          1315FMxxxx          1315FMxxxx  <=== Product Serial Numbers must match
   Product Name        FS1 Controller      FS1 Controller      FS1 Controller
   [(restricted_shell) ORACLESP-1315FMxxxx:~]#
    
   
   
   
5. If all 3 PSNs match, exit all the way out of the FS1-2 and proceed to step 2.
6. If the Disk BackPlane 0 (DBP0) and Motherboard (MB) are the same but Power Distribution Board (PDB) is different, it is safe to proceed to step 2 since the PDB will be replaced.
7. If any other condition exists, STOP!! and re-engage the TSC for steps to correct before proceeding to replace the failed PDB.
   
   
2. Prepare the FS1-2 System 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 as pillar to access Guided Maintenance:
1. Select Support tab
2. In the navigation tree, select System Trouble.
3. In the main window, right click on the Controller with the failed PDB and select Replace Component.
4. In the pop-up Replace Component window, select Power Distribution Board and then click on Next.
5. Follow the steps in Guided Maintenance to identify and place the Controller offline.
   
   
3. Access the failed PDB.
1. Deploy the anti-tip legs in the front of the rack.
2. Slide the Controller into the service position.
3. Unplug both power cords.
4. Loosen the two captive screws in the rear of the top cover.
5. Slide the top cover back and remove.
6. Unseat both power supplies.
   
   
   NOTE: It is recommended to only unseat both power supplies rather than completely remove them.
    
7. Lift Drive Compartment into service position.
1. Unplug the cables connected to the Drive Compartment - suggest that they be labeled to make reconnections easier.
2. Unplug the USB cable on the front right side of the Controller.
3. Loosen the four captive screws that secure the Drive Compartment to the Controller chassis and tilt it up into the service position.
8. Remove air duct.
9. Remove fan tray.
1. Remove all 5 fan modules.
2. Remove fan tray.
10. Remove risers.
    1. Loosen 2 captive screws in each riser.
    2. Lift the riser up and clear of the Controller chassis.
    
    
    NOTE: it is not necessary to remove the PCIe cards from the risers nor is it required to unplug any cables connected to the PCIe cards in those risers.
    
    
11. Remove motherboard.
    
    1. Loosen the single captive screw that secures the PDB duct to the Controller chassis and lift it free.  Be sure to guide the USB cable out of the slot in the PDB duct.
    2. Remove the 4 screws that secure the PDB GND and +12V buses to the motherboard.
    3. Loosen the single captive screw at the front of the motherboard.
    4. Using the two green plastic handles, gently push the motherboard towards the rear until it is free of the chassis (only needs to move about 1/2 an inch).
       
       
       
    NOTE: Removal of CPUs, Heatsinks, DIMMs, NV-DIMMs or other cables from the motherboard is not necessary since it is not being replaced.
      
    
    
4. Remove the failed PDB.
1. Unplug the ribbon cable from the PDB.
2. Remove the 2 screws that secure the PDB to the chassis.
3. Using the green plastic handles, lift the motherboard up so that you can slide the GND and +12V buses from under the motherboard.
   
   
5. Install the replacement PDB.
1. Slide the two bus arms under the motherboard and into their fabricated locations.  If necessary use the green plastic handles on the motherboard to lift it up slightly and out of the way.
2. Tighten the 2 screws that secure the PDB to the chassis.
3. Plug in the ribbon cable to the PDB.
   
   
6. Reassemble Controller components.
1. Reinstall the motherboard
   1. Using the 2 green plastic handles, slide the motherboard forward to it's original position.  Take care to align the four holes that connect it to the PDB as well as the alignment tabs in the rear.
   2. Secure motherboard by tightening captive screw in the front of the motherboard.
   3. Secure the  PDB busses to the mother board using the 4 screws previously removed.
   4. Install the PDB duct in place and secure to chassis with captive screw.  Be sure to route the USB cable through the slot on the top.
2. Reinstall the risers.
   1. Each riser has 1 alignment hole, 2 screws and a PCIe connector.  Align the PCIe connector to the motherboard first and then adjust for the others before pushing the PCIe connector into the PCIe slot.
   2. Secure in place using the two captive screws.
3. Reinstall fan tray and Fans.  Be sure to properly route the alarm and and power cables (left side) and the USB and PDB cables (right side).
4. Reinstall the air duct
5. Return Drive compartment to it's normal position.
   1. Tilt the Drive Compartment back into it's normal position being careful not to pinch any cables.
   2. Secure in place using the 4 captive screws.
   3. Reconnect (left to right) the power cable from the motherboard, the cables from NV-DIMMS to ESMs, the SAS cable and the USB cable.
6. Reseat both power supplies.
7. Close the top cover.
8. Tighten the two captive screws in the rear of the top cover.
   
   
7. Return Controller to FS1-2 System.
1. Plug in both power cords.
2. Return the Controller to the rack position.
3. Return the anti-tip legs to their normal position.
4. Once the Controller has completed it's reboot, repeat step 1 to verify that PSN of the replacement PDB is synchronized with 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 that the replacement PDB was successful - the System Alert associated with it should be gone and the FS1-2 should be normal/green.

Note: because the Controller must cold start, it may take as long as 15 minutes for the boot process to complete and the Controller to return to a normal status.

REFERENCE INFORMATION:

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

This solution has no attachment