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 ESM Backplane 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 ESM (Energy Storage Module) backplane using the 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:

What: A Controller ESM backplane in an FS1-2 has failed and needs to be replaced.  ESM backplanes connect ESMs located in the front drive slots to NVDIMMs on the motherboard.

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

Why: An FS1-2 Controller ESM backplane has failed.

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

The Controller with the ESM backplane failure will have a warning status.  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 ESM 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 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-1315FM2009:~]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PDB
   
   Element           | Primary           | Backup1           | Backup2
   ------------------+-------------------+-------------------+-------------------
   PPN                 70893370            70893370            70893370
   PSN                 1315FM2009          1315FM2009          1315FM2009  <=== Product Serial Numbers must match
   Product Name        FS1 Controller      FS1 Controller      FS1 Controller
   [(restricted_shell) ORACLESP-1315FM2009:~]#
    
   
   
   
5. If all 3 PSNs match, exit all the way out of the FS1-2 and proceed to step 2.
6. If the Motherboard (MB) and Power Distribution Board are the same but Disk BackPlane (DBP0) is different, it is safe to proceed to step 2 since the disk backplane 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 disk backplane.
   
   
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 ESM Backplane and select Replace Component.
4. In the pop-up Replace Component window, select ESM Backplane and then click on Next.
5. Follow the steps in Guided Maintenance to identify and place the Controller offline.
   
   
3. Access the failed ESM Backplane.
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.
   
   
4. Remove the failed ESM backplane.
1. Remove the front air filter by pressing the two green tabs towards the center and tilting back.
2. Unplug the ESMs from their drive slots - suggest they be labeled to return to same slots later on.
3. Unplug the cables connected to the Drive Compartment - suggest they be labeled to make reconnections easier.
4. Unplug the USB cable on the right front of the Controller.
5. Loosen the 4 captive screws that secure the Drive Compartment and lift it toward you into the service position.
6. Unscrew the 5 screws that secure the ESM backplane to the Drive Compartment and remove.
   
   
5. Install the replacement ESM backplane.
1. Use the two guide pins on either end (right side pin also doubles as screw hole) to align the replacement ESM Backplane in place.
2. Use the 5 screws removed in step 4-f to secure the ESM backplane into the Drive Compartment.
3. Lower the Drive Compartment from the service position and secure in place with the 4 captive screws.
4. Reconnect the cables that were unplugged in steps 4-c & d.
5. Insert the ESMs back into their drive slots.
6. Reattach the air filter.
7. Secure the top cover in place using the 2 captive screws in the rear.
   
   
6. 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 the PSN of the replacement disk backplane 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 that the replacement ESM backplane 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 20 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.

References

This solution has no attachment