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-2201602.1
Update Date:2016-12-30
Keywords:

Solution Type  Technical Instruction Sure

Solution  2201602.1 :   How to Remove and Replace an Oracle Server x6-2M RAID HBA  


Related Items
  • Oracle Server X6-2M
  •  
  • Netra Modular System
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
  •  




In this Document
Goal
Solution
References


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

Applies to:

Oracle Server X6-2M - Version All Versions to All Versions [Release All Releases]
Netra Modular System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

 How to Replace and Replace an Oracle Server x6-2M HBA RAID in the Netra Modular System (NMS).

Solution

CAP PROBLEM OVERVIEW: Raid HBA Replacement

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:
Netra Modular System Training

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 1

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.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

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

Removing the Raid HBA

1. 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 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:

# MegaCli64 -ldsetprop wt -lall -a0

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

# MegaCli64 -ldpdinfo -a0 | grep BBU

d. Once the RAID cache is in WriteThrough mode, perform an orderly and graceful shutdown by pressing and quickly releasing the Power button on the front panel.
e. The green OK LED begins to flash, indicating that the node power-down sequence has completed.

2. When the node has powered off, removed it from the system to a clean, antistatic workbench

3. Attach an antistatic wrist strap to your wrist, and then to a metal area on the chassis

4. Open the server fan door to gain access to the disk backplanes

5. Remove fan module FM0 (the left most fan viewing the server from the front)

6. Remove the PCIe riser from slots 3 and 4

7. Remove the internal host bus adapter card from the riser

a. Hold the riser in one hand and use your other hand to carefully remove the card from slot 4 of the riser
b. Disconnect the rear bracket attached to the PCIe card from the rear of the PCIe riser

8.  Skip to step 9

9. Disconnect the SAS cables and the super capacitor cable from the internal HBA card and place the card on an antistatic mat

10. Use a No. 2 Philips screwdriver to remove the specially fitted bracket from the HBA card
NOTE: You will need to install the specially fitted bracket on the replacement HBA card. Set the bracket aside until you are ready to install the replacement HBA card

Install the Raid HBA

1. Unpack the replacement host bus adapter (HBA) card, the super capacitor, the SAS cables, and the super capacitor cable, and retrieve the PCIe riser for slot 3

2. Using a No. 2 Philips screwdriver, remove the standard HBA bracket that shipped with the replacement HBA card

3. Install the specially fitted bracket that was removed from the original raid HBA

4. Connect the SAS cables and the super capacitor cable to the internal HBA card

5. Insert the rear bracket on the internal HBA card into the rear connector on the PCIe riser

6. Insert the internal HBA card connector into the bottom connector on the riser for PCIe slot 3 and 4

7. Install the PCIe riser

8. Install fan module FM0

9. Close the server fan door

10. Return the server to the normal rack position

11. Power on the server

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:

# MegaCli64 -ldsetprop wb -lall -a0

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

# MegaCli64 -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
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:

Netra Modular System Service Manual Supplement:
http://docs.oracle.com/cd/E59318_01/html/E59323/index.html

 

References

<NOTE:2063685.1> - How to Replace an Oracle Server X5-2 and X6-2 RAID HBA.

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