Oracle Server X6-2M
 
Netra Modular System
 

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

Applies to:

Goal

How to Replace Disk backplane on an Oracle Server X6-2M in the Netra Modular System (NMS)

Solution

CAP PROBLEM OVERVIEW: Storage Disk Backplane Replacement

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:
Oracle Server X5-2/X6-2 Training.
NMS Training

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 1-FRU

FIELD ENGINEER INSTRUCTIONS

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

Oracle Server X6-2M Differences

The Oracle Server X6-2M is a customized modular version of the Oracle Server X6-2.

These are the Oracle Server X6-2M differences for the Netra Modular System:
- Thumb-pull levers for removing a node from the system replace the green hot-swap levers.
- After you push the Power button, the green Power/OK LED begins flashing to indicate hot-swap is initiated. See Oracle Server X6-2M LEDs.
- FBA provides plug-and-play capability, eliminating the cabling process. This feature is the most significant physical difference between the servers.
- Serial console is not available because the serial port is used by the modular system to detect the node's presence. Access to the SP is through the network (NET_MGT) port through a switch in the FMM.
- The node power supply is not a CRU-serviceable item.
- The BIOS is customized.
- Some Oracle ILOM functions are either not available or have restrictions.
- A factory configuration containing an Oracle Quad 10Gb Ethernet Adapter is available.
- The DVD drive is not available.

Note - Because the nodes are identical in their serviceable components (DIMMs, hard drives, batteries, and fans) to the Oracle Server X6-2, the procedures for servicing these Oracle Server X6-2M components are mostly the same. The key difference is that some FRUs can be accessed only by removing the FBA. In the Oracle Server X6-2 Service Manual a distinction is made about CRUs that can be serviced without turning off power. This distinction does not apply to nodes used in the modular system. Any service on a node requires that the node be completely powered off and removed from the system to a clean, antistatic workbench.

The Oracle ILOM on a node in the modular system supports all the standard Oracle ILOM interfaces that are described in the Oracle ILOM documentation.

If the system is still up and functioning, the customer should perform an orderly and graceful shutdown of applications and OS. Then power off the server and remove the node from the system.
A data backup is not a prerequisite but is a wise precaution.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Note - If you pull a node out a few inches, you must wait at least 5 seconds before reinserting the node. Failing to wait might cause the node not to power on.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

1. Log into the ILOM check the fruid container values and sync them if needed.

a. To avoid mismatched fruid values causing a failure after a disk backplane replacement the fruid data should be confirmed to have matching data in at least the Backup1 (MB) and Backup2 (PS0) containers so that the disk backplane will have it's container updated automatically after replacement. Go into restricted mode and use the showpsnc command to check this.

b. The above example shows a system with all three containers properly in sync. If the output from the system does not show all of the containers with matching values then you should reset the SP and then re-check the values again. An ILOM reset will attempt to auto-populate the matching values if one container is out of sync.

c. After an ILOM reset if the Backup1 and Backup2 containers match then proceed with the following steps to replace the disk backplane. If these two containers do not match then DO NOT proceed with the replacement yet.
d. If the containers do not match you will need to use the copypsnc command from service or escalation mode to copy the data from the good container so that the Backup1 and Backup2 containers match (Primary is the DBP and we are about to replace this so it is not as important at this step). If you are unfamiliar with this process and require assistance please reference the steps for using copypsnc to fix the serial number detailed in the "How to update product serial number on systems which implement TLI functionality (Doc ID 1280913.1)" and contact the TSC if needed. How to access service mode and escalation mode on ILOM 3.x and later platforms (Doc ID 1019946.1)
e. After the fruid data in the Backup1 and Backup2 containers have been confirmed to match proceed with the following steps.

2. Prepare the server for service.

a. Stop all applications that are running or scheduled to run within the service period.
b. If the node is not responding, remove it from the modular system without powering it down.
c. If the node is responding, gracefully power down the node by pressing and quickly releasing the Power button on the front panel.
d. The green OK LED begins to flash, indicating that the node power-down sequence has completed.
e. When the node has powered off, removed it from the system to a clean, antistatic workbench.
f. Attach an anti-static wrist strap.
g. Remove the top cover.

3. Remove all of the Fan Modules.

a. Open the Server Fan Door. Slide the fan door latches forward and swing the door up to the open position.
b. Using your thumb and forefinger, grasp each of the fan modules in the finger recesses located in the plastic between the fans.
c. Lift the fan modules straight up and out of the chassis.

4. Remove all of the storage drives from the storage drive cage.

a. On each drive, push the latch release button to open the latch
b. Grasp the latch and pull each of the drives far enough out so that they disengage from the backplane.
c. It is not necessary to completely remove the storage drives from the server; simply pull them out far enough to disengage them from the disk backplane. If you do remove the storage drives from the server, record their locations so that you can reinstall them in the same locations.

5. Remove the top cover from the storage drive cage.

a. Remove six Phillips screws from the top of the drive cage — three on each side.
b. Open the server's fan door by sliding the fan door latches forward and swinging the door up.
c. Slide the storage drive cover forward (toward the front of the server) and lift it up.
IMPORTANT: Once the storage drive cover is removed, turn it over exposing the underside, and remove the black rubber spacer strip that runs parallel to the fan door hinge. This spacer is not needed for operation, and must be removed if present.

6. Disconnect the cables and remove the storage drive backplane.

a. Disconnect the SAS cables and the switch card cables (if present) from the disk backplane.
b. If the server has a DVD drive disconnect the DVD drive signal cable from the DVD drive and the DVD power cable from the disk backplane. Then remove the DVD drive.
c. Disconnect the disk backplane auxiliary signal cable from the disk backplane.
d. Disconnect the disk backplane power cable from the disk backplane.
e. Loosen the captive screw that secures the disk backplane to the chassis. The screw is on the right backside of the backplane if facing the front of the server.
f. Lift the metal spring retainer on the left side of the disk backplane, when facing the front of the server, lift the disk backplane up and tilt the bottom toward the rear of the server to free it from the holding brackets, and lift it out of the server.
g. Place the disk backplane on an antistatic mat.

7. Install the replacement storage drive backplane and connect the cables.

a. Lift the metal spring retainer and position the backplane so that it fits into the two metal brackets that are located on the chassis side walls.
b. Lower the disk backplane into the disk cage so that it engages the three metal hooks in the disk cage. These are spaced across the middle of the backplane.
c. Continue to lower the disk backplane into the disk cage until it is positioned in all six troughs that are located at the bottom of the disk cage.
d. Turn the disk backplane captive screw clockwise until the disk backplane is secure.
e. Reconnect the disk backplane power cable to the disk backplane.
f. If the server has a DVD drive install the DVD drive into the disk drive cage and reconnect the DVD cable signal connector to the DVD drive.
g. Reconnect the DVD cable power connector to the disk backplane.
h. Reconnect the disk backplane auxiliary power and signal cable to the disk backplane.
i. Reconnect the SAS cables and the switch card cables (if present) to the disk backplane.

8. Re-install the storage drives into the storage drive cage.

a. Making sure to install the drives back into the same slots from which they were removed align the drive to the drive slot.
b. Slide the drive into the bay until the drive is fully seated.
c. Close the drive latch to lock the drive in place.

9. Re-install the top cover to the storage drive cage.

a. Place the drive cage cover over the server's drive cage and slide it back to align the screw holes with the proper holes in the top of the chassis frame.
b. Install the six Phillips screws (three on each side) to secure the cover to the server.

10. Re-install the Fans.

a. Install the fan modules into the server.
b. For each module press down on the fan module and apply firm pressure to fully seat the fan module.
c. Close the fan door.

11. Return the Server to operation.

a. Install the server top cover.
b. Close the server fan door.
c. Return the server to the normal rack position.
d. Power on the server.

12. Set the system serial number/fruid data if needed.

a. The disk backplane is the primary fruid container in this server so when it is replaced you will normally need to fix the serial number information.
b. login to the ILOM as root and then enter the restricted shell to check the fruid values. Follow the example below to enter restricted shell and use the showpsnc command

c. When the disk backplane is replaced the Primary fruid container will likely not match the Backup entries. If it does not you must enter escalation or service mode to fix it (if all three entries match this step is done).
d. Contact the TSC to request an escalation password (service mode will work also if just the copypsnc command ends up needing to be used, if the setpsnc command is needed escalation mode is required. setpsnc is not covered in this procedure).
e. Provide your TSC contact the output from the following ILOM commands- "version", "show /SYS product_serial_number", and "show /SP/clock". If the product_serial_number information does not give good output then provide the showpsnc output that was seen in step b above as well.
f. The TSC will provide an escalation password that is made up of 32 short words. Follow the example below to create a new user with the 'Service' role assigned. The Service role is required to access service or escalation modes. In the following example we will create a user named 'escuser' with the service role.

  g. Set the check_physical_presence to false and then exit from the ILOM so that you can login as the newly created user.

  h. Login using the escuser login and enter escalation mode using the password that was provided by the TSC.

i. Use the showpsnc command to confirm the current container values. Confirm that one of the backup containers has a serial number (the value on the PSN line) that matches the system serial number. The system serial number can be checked by comparing to the serial number RFID tag on the front left hand side of the server. After confirming that there is a valid fruid backup use the copypsnc command to write the good data from the backup to the primary container on the DBP. The following example shows copying from backup1 to the primary but you could also copy from backup2 if needed.

 j. At this point if all of the fruid containers match and have the correct serial number data this step is done. If more than one of the fruid containers had non-valid entries then the copypsnc command should be used to copy over the valid data to the other container that is not valid. (ie. "copypsnc Backup1 Backup2" to copy backup1 to backup2) After confirming all fruid data is correct reset the ILOM to confirm that the fruid data persists through a reboot and remove the escalation user if needed.

k. If trouble is encountered during any of the steps of accessing escalation mode and fixing the fruid containers please contact the TSC for assistance.

How to verify the Disk Backplane is working properly.

1. Log into ILOM to confirm if disk backplane status is working properly.

Sample

  2. Check ILOM event log to see if any error related backplane.

Reference Docs:
Oracle Server X5-2 Remove the Disk Backplane
http://docs.oracle.com/cd/E41059_01/html/E48312/napsm.z40011771417723.html#scrolltoc
Oracle Server X6-2 Remove the Disk Backplane
http://docs.oracle.com/cd/E62159_01/html/E62171/z40011771417723.html#scrolltoc

References

This solution has no attachment