Oracle Server X5-8
 

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

Applies to:

Goal

How to Replace an Oracle Server X5-8 Internal RAID HBA Energy Storage Module (ESM) and/or Cable.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?:
Oracle Server X5-8 Training

TIME ESTIMATE: 45 minutes

TASK COMPLEXITY: 1

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: An Oracle Server X5-8 Internal RAID HBA Energy Storage Module (ESM) and/or Cable needs replacement

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

If the system is up and functioning, customer should revert all the RAID disk volumes to WriteThrough mode to ensure all data in the RAID cache memory is flushed to disk and not lost when replacement of the HBA SuperCap occurs. As 'root' user, set all logical volumes cache policy to WriteThrough cache mode:

Verify the current cache policy for all logical volumes is now WriteThrough :

Once the RAID cache is in WriteThrough mode, perform an orderly and graceful shutdown of applications and OS.  Then power off the server and remove the AC power cords from the system.

A data backup is not a prerequisite but is a wise precaution.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Reference Doc:
Oracle Server X5-8 Service Manual
http://docs.oracle.com/cd/E56301_01/html/E56311/index.html

Oracle Server X5-8 SAS Host Bus Adapter (HBA) Card Overview
http://docs.oracle.com/cd/E56301_01/html/E56311/gnsfb.html#OSXSMgnshr

The server requires one internal HBA for the externally-accessible SAS (or SATA) SMOD server storage drives. The HBA is installed in a riser slot on the underside of the SMOD motherboard and connected to the backplanes by two mini-SAS4I connector cables. The card is accessible by turning over the SMOD.

How to Remove the HBA Energy Storage Module (ESM)

1. Prepare the server for cold service.

2. Access the rear of the server.

3. Label and disconnect all cables from the SMOD.

4. Disengage the SMOD from the server midplane.

    A. To Unlock the SMOD handles, squeeze together the release latches on the end of both handles.  The unlocking action is accompanied by an audible click.

    B. To disengage the SMOD from the server midplane, simultaneously, rotate both handles downward toward their fully open positions.  This action disengages the connectors on the SMOD from the connectors on the server midplane.

5. To remove the SMOD, grab it by it's sides and slide it out of the server.

6. Set the SMOD on a flat surface with the front side facing toward you.

7. Close the SMOD handles.

8. Rotate the SMOD 180 degrees so the back (connector) side is facing toward you.  Note, if you are servicing the Oracle Server X5-8 skip to step 20 now, as the HBA does not need to be removed on the X5-8.

9.  You should have skipped from step 8.  The Energy Storage Module (ESM - SuperCap) is located between the two disk drive enclosures.  Disconnect the ESM connector from the ESM extension cable.

10. Remove the ESM by lifting it out of position detaching from the velcro.  Lift it straight up and out of position.

11. Insert the new ESM into the holder so that the cable extends out the top.  Push it straight down into position.

12. Attach the ESM connector to the ESM extension cable.

How to Install the SMOD

13. Ensure that the handles on the SMOD are in their fully open position.

    A. To unlock the SMOD handles, squeeze together the release latches on the end of both handles.  The unlocking action is accompanied by an audible click.

    B. To open, rotate both handles downward until they are at a 90 degree angle to the SMOD (fully-open position).

14. Orient the SMOD with the handles facing away from the server and the connectors facing toward the open slot in the server.  The handles should be at the bottom front and the disks should be at the top front.

15. Align the SMOD in the slot.

16. Slide the SMOD into the slot until it stops.  This leaves the SMOD protruding slightly from the back of the server. Do not attempt to push the SMOD inward beyond this point.

17. To install the SMOD, simultaneously rotate both handles upward until they lock into place.  This action draws the SMOD inward engaging the SMOD connectors with the connectors on the server midplane.

18. Connect the cables to the SMOD.

19. Return the server to operation.  Verify that the Power/OK indicator LED lights steady on.

20. Verify the RAID HBA controller can see the new battery.

a) Verify the new battery is seen as "Present" by the RAID HBA controller. Note, it may take up to 10 minutes for the new battery to be detected, although typical time ranges from 1 minute to 10 minutes.

b) Verify the new battery status is charging. It may take up to 10 minutes for the new battery to be detected, although typical time ranges from 1 minute to 10 minutes.

There will be a page full of output detailing the battery information and status. If there is any type of error reading the battery status, then further investigation by Oracle Support to identify and correct the problem should be requested before continuing.

21. Set all logical drives cache policy to WriteBack cache mode to ensure the RAID volumes are being cached using the new battery:

a) Set all logical volumes cache policy to WriteBack cache mode:

b) Verify the current cache policy for all logical volumes is now WriteBack which uses the battery:

If the current cache policy is WriteThrough mode, and not WriteBack, then the battery may not have charged sufficiently to allow the cache to be used. Monitor for 3 to 4 hours and re-check the status. If the current cache policy stays as “WriteThrough” mode for a prolonged period of time and the battery status can be properly read by the HBA as above, then further investigation by Oracle Support to identify and correct the problem should be requested before continuing.

How to verify the SAS HBA is working properly.

Access the SP via web browser and open HOST/console window.  Power on the server and monitor the BIOS initialization screens to verify the HBA is visible.  Ensure the system is bootable and can see all disks.

Example

Check ILOM event log to see if any errors exist.

faultmgmtsp> fmadm faulty

Example

-> show /SP/logs/event/list


Check Solaris FMA info to see if any errors exist.

Example

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

Boot up system and verify full functionality

REFERENCE INFORMATION:
Oracle Server X5-8 Documentation
http://docs.oracle.com/cd/E56301_01/index.html

This solution has no attachment