Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2075616.1
Update Date:2018-05-14
Keywords:

Solution Type  Technical Instruction Sure

Solution  2075616.1 :   How to Replace an Oracle Server X5-2L, X6-2L Internal RAID HBA Card  


Related Items
  • Oracle Server X6-2L
  •  
  • Oracle Server X5-2L
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
  •  




In this Document
Goal
Solution


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: The raid hba on a x5-2L is a FRU so this document would not benefit customers

Applies to:

Oracle Server X6-2L - Version All Versions and later
Oracle Server X5-2L - Version All Versions and later
Information in this document applies to any platform.

Goal

 How to Replace an Oracle Server X5-2L, X6-2L Internal RAID HBA Card.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED?:
Oracle Server X5-2L, X6-2L Training

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 1

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: An Oracle Server X5-2L, X6-2L Internal RAID HBA Card 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 occurs. As 'root' user, set all logical volumes cache policy to WriteThrough cache mode:

# StorCli64 -ldsetprop wt -lall -a0

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

# StorCli64 -ldpdinfo -a0 | grep BBU

Default Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteThrough, ReadAheadNone, Direct, No Write Cache if Bad BBU

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.

 

Note: MegaCli commands can be run on StorCli utility as well

 

 

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Removing the Raid HBA:

1. Prepare the server for service

  1. Power off the server and disconnect the power cords from the power supplies.
  2. Extend the server to the maintenance position.
  3. Attach an antistatic wrist strap.
  4. Remove the server top cover.

2. Remove the super capacitor from the chassis.

  1. Grasp both ends of the cable connector, press in on the release latch, and then unplug the connector.  The HBA super capacitor is secured to the air baffle by a recloseable fastener, which allows it to be easily removed and replaced.
  2. To separate the HBA super capacitor from the air baffle, place your finger under the rear of the super capacitor and lift up.  Place the super capacitor on an antistatic mat.

3. Swivel the air baffle into the upright position to allow access to the super capacitor cable and the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card.

4. Rotate the PCIe card locking mechanism, and then lift up on the RAID HBA card to disengage it from the motherboard connector.

5. Disconnect the super capacitor cable and the SAS cables from the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card.

  1. Grasp the RAID HBA, press in on the release latch for the super capacitor cable, and then unplug the cable from the connector.
  2. To disconnect the SAS cables between the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card in PCIe slot 6 and the front storage drive backplane, press each latch, and then pull out to disengage the cable from each SAS connector.

6. Lift and remove the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card and super capacitor cable from the chassis.

7. Place the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card and super capacitor cable on an antistatic mat.

 

Install the Raid HBA:

1. Unpack the replacement Oracle Storage 12 Gb/s SAS PCIe RAID HBA card and place it on an antistatic mat.

2. Swivel the air baffle into the upright position and install the super capacitor cable along the left sidewall of the chassis.  Install the super capacitor cable on top of the SAS cable bundle along the left sidewall of the chassis.  Otherwise, the SAS cable bundle will interfere with the air baffle.

3. Connect the super capacitor cable to the Oracle Storage 12 Gb/s SAS PCIe RAID HBA, and then reconnect the SAS cables that you unplugged during the removal procedure.

4. Insert the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card into PCIe slot 6, and rotate the PCIe locking mechanism to secure the PCIe HBA card in place.

5. Install the super capacitor in the chassis.

  1. Lower the air baffle to the installed position.
  2. Apply a re-useable fastener to the underside of the super capacitor.
  3. Align the re-useable fastener on the super capacitor with the re-useable fastener on the air baffle and press down.
  4. Connect the super capacitor's cable.

6. Return the server to operation.

  1. Install the top cover.
  2. Return the server to the normal rack position.
  3. Reconnect the power cords to the power supplies and power on the server.

7. Use Oracle ILOM to clear any server PCIe card faults, if any.

 

OBTAIN CUSTOMER ACCEPTANCE

 

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

Boot up system and if necessary you may need to import the foreign configuration detected on the hard disks after the HBA replacement, when prompted during the boot process press Ctrl+R to Run LSI Configuration Utility.
Use CTRL+N to navigate to the VD MGMT screen, highlight the controller, press F2, Foreign config, Import/Clear.

Once the OS is booted, login as root and set all logical drives cache policy back to WriteBack cache mode:

# StorCli64 -ldsetprop wb -lall -a0

 Verify the current cache policy for all logical drives is using WriteBack cache mode:

# StorCli64 -ldpdinfo -a0 | grep BBU

Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Default Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU
Current Cache Policy: WriteBack, ReadAheadNone, Direct, No Write Cache if Bad BBU

 

REFERENCE INFORMATION:

Oracle Server X5-2L Documentation:
http://docs.oracle.com/cd/E41033_01/html/E48325/index.html

Oracle Server X6-2L Documentation:
http://docs.oracle.com/cd/E62172_01/index.html


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback