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-2210382.1
Update Date:2018-05-15
Keywords:

Solution Type  Technical Instruction Sure

Solution  2210382.1 :   How to Replace a Sun Server X4-8 Internal RAID HBA BBU  


Related Items
  • Sun Server X4-8
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
  •  




Applies to:

Sun Server X4-8 - Version All Versions and later
x86_64

Goal

How to Replace a Sun Server X4-8 Internal RAID HBA BBU.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
No special skills required, Customer Replaceable Unit (CRU) procedure

TIME ESTIMATE: 45 minutes

TASK COMPLEXITY: 0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: A Sun Server X4-8 Internal RAID HBA BBU 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 BBU/SuperCap occurs. As 'root' user, set all logical volumes cache policy to WriteThrough cache mode, for X4-8 use the below commands, as the X4-8 uses an Niwot-INT HBA:

# /opt/MegaRAID/MegaCli/MegaCli64 -ldsetprop wt -lall -a0

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

# /opt/MegaRAID/MegaCli/MegaCli64 -ldpdinfo -a0 | grep 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.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Reference Doc:
Sun Server X4-8 Service Manual
http://docs.oracle.com/cd/E40591_01/html/E40317/index.html

Sun Server X4-8 System Module (SMOD) Overview
http://docs.oracle.com/cd/E40591_01/html/E40317/gnsfb.html#XFESMgnzll

Sun Server X4-8 SAS Host Bus Adapter (HBA) Card Overview

http://docs.oracle.com/cd/E40591_01/html/E40317/gnsfb.html#XFESMgnshr

 

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 BBU

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.


Caution - Physical harm or component damage. Do not use the SMOD handles to remove the SMOD from the server.

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.


Caution - Component Damage - SMOD components are extremely sensitive to electro-static discharge. Wear a wrist strap and use an anti-static mat.

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. Turn the SMOD upside down and locate the HBA.  The HBA is located inside the SMOD and is accessible through the upward-facing opening on the right side.


Note -  The connector (back) side of the SMOD should still be facing you.

10. To unlock the HBA card, rotate the green release handle out and then downward.  The handle is on the right (vertical) side of the SMOD.  To access it, you might need to push it outward from the inside.

11. To disconnect the HBA card from its connector on the SMOD motherboard, pull the card toward you.  Two cables with mini SAS4I connectors connect the HBA to the storage drive backplane.


Note -  The two storage drive backplane cables are still attached to the card.

12. Carefully lift the card up, and pull it slightly away from the SMOD until the cable connectors are visible.

13. Disconnect the cables from the card.


Note -  Do not disconnect the cables from the SMOD.

14. Remove the HBA card from the SMOD and place it on an anti-static mat.

15. Set the HBA on the work space with the component side facing down.

16. Use the screwdriver to remove and retain the three screws that secure the battery to the HBA card.

17. Remove the battery from the card.

18. Align the replacement battery with the three screw holes.

19. Use the screwdriver to tighten the screws and secure the battery to the HBA.  

 

How to Install the SAS HBA Card

20. Position the HBA card with the component side facing upward and the edge connector pointed away from you.

21. With the SMOD positioned upside down and the back (connector) side facing you, orient the HBA card in the opening on the right.

22. Ensure that the two backplane cables are routed under the support bracket on the bottom of the SMOD.

23. Connect the cables to the connectors on the HBA card.  Note the cable on the right side should connect to the adapter connector closest to the HBA PCI slot connector.  The cable on the left should connect to the connector closest to the top of the card or outside edge.

24. Lower the card and align its edge connector with the PCIe slot on the SMOD motherboard.

25. To install the HBA card, push it into the slot.

26. To lock the card, rotate the green locking lever upward.

27. Rotate the lever inward so it tucks inside the SMOD frame and does not extend outward.

 

How to Install the SMOD

28. 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).


Caution - Physical harm or component damage. Do not use the SMOD handles to install the SMOD into the server.

29. 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.

30. Align the SMOD in the slot.

31. 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.

32. 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.


Caution - Pinch point. When operating the lever, keep your fingers clear of the back side and hinged end of the lever.

33. Connect the cables to the SMOD.

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

35. 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 24 hours for the new BBU battery to be detected, although typical time ranges from 1 minute to 1 hour. 

# MegaCli64 -AdpAllInfo -a0 | grep BBU

 BBU : Present
 BBU : Yes
 Cache When BBU Bad : Disabled

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

# MegaCli64 -adpbbucmd -a0

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.

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

# MegaCli64 -ldsetprop wb -lall -a0

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

# MegaCli64 -ldpdinfo -a0 | grep BBU

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

LSI MegaRAID SAS-MFI BIOS
Version 3.29.00 (Build June 18, 2013)
Copyright(c) 2013 LSI Corporation
HA -0 (Bus 4 Dev 0) LSI MegaRAID SAS 9261-8i
FW package: 12.12.0-0178

Battery Status: Fully charged
PCI Slot Number: 0

ID LUN VENDOR    PRODUCT                     REVISION            CAPACITY
-- --- ------    -------                     --------            --------
       LSI       LSI MegaRAID SAS 9261-8i    2.130.373-2809      512MB
20 0   HGST      H101212SESUN1.2T            A690                1144641MB
21 0   HGST      H101212SESUN1.2T            A690                1144641MB
22 0   ATA       ITVSC2BA3SUN400G            0270                381554MB
   0   LSI       Virtual Drive               RAID0               1143455MB
   1   LSI       Virtual Drive               RAID0               1143455MB
   2   LSI       Virtual Drive               RAID0               380516MB
3 Virtual Drive(s) found on the host adapter.

3 Virtual Drive(s) handled by BIOS
Press <Ctrl><H> for WebBIOS or press <Ctrl><Y> for Preboot CLI

 


Check ILOM event log to see if any errors exist.

faultmgmtsp> fmadm faulty

Example

-> start /SP/faultmgmt/shell
Are you sure you want to start /SP/faultmgmt/shell (y/n)? y

faultmgmtsp> fmadm faulty
No faults found



-> show /SP/logs/event/list


Check Solaris FMA info to see if any errors exist.

Example

fmadm faulty -a
STATE RESOURCE / UUID
-------- ----------------------------------------------------------------------



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:
Sun Server X4-8 Documentation
http://docs.oracle.com/cd/E40591_01/index.html


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