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-1572132.1
Update Date:2015-06-08
Keywords:

Solution Type  Technical Instruction Sure

Solution  1572132.1 :   How to Replace an Internal SAS controller in the Oracle Database Appliance X3-2/X4-2  


Related Items
  • Oracle Database Appliance X4-2
  •  
  • Oracle Database Appliance X3-2
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
  •  




Applies to:

Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X4-2 - Version All Versions to All Versions [Release All Releases]
x86_64

Goal

How to Replace a the Internal SAS controller in a node of an Oracle Database Appliance X3-2/X4-2.

Each node has one internal LSI Erie controller and two external LSI Erie controllers.  This document outlines the steps to replace the internal LSI Erie controller.

Solution

CAP PROBLEM OVERVIEW: INTERNAL LSI ERIE CARD REPLACEMENT

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:
Oracle Database Appliance Training

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 1-CRU

FIELD ENGINEER INSTRUCTIONS

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

If the system is still up and functioning, customer should 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:

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 in the rack.
  3. Attach an anti-static wrist strap.
  4. Remove the top cover.

2. Locate and remove the internal SAS controller

  1. The SAS Controller for the internal disk drives is located in PCIe slot 4 which is located in the lower PCIe slot of the PCIe riser at the rear left-most corner of the server chassis (PCIe riser 3).
  2. Unplug the SAS data cables from the rear of the HBA making note of the connector locations so that the cables can be reinstalled in the same slots of the new HBA  (label if needed).
  3. If there is a PCIe card installed in the upper PCIe slot (slot 3) disconnect any cables from the card.
  4. open the green-tabbed latch located on the rear of the server's chassis next to the PCIe slot 3 to release the PCIe card holding bracket.
  5. To release the riser from the motherboard connector, lift the riser's green-tabbed release lever to the open position.
  6. Slide the plastic PCIe card retainer, which is mounted on the side of the chassis, forward to release the card(s) installed in the riser
  7. Grasp the riser with both hands and remove it from the server
  8. Remove the Internal HBA card from the riser, hold the riser in one hand and use your other hand to carefully remove the card from slot 4 of the riser.
  9. Disconnect the rear bracket attached to the PCIe card from the rear of the PCIe riser.
  10. place the riser and SAS controller on an anti-static mat.

3. Re-install the SAS controller.

  1. Remove the replacment HBA card from it's anti-static bag and place on an anti-static mat.
  2. If the SAS controller contains a Battery unit which is not being replaced with a new unit from stock then transfer the battery unit from the original controller to the replacement controller.
  3. Remove the rear bracket from the old SAS controller and the new SAS controller by removing the two phillips head screws.
  4. Swap the brackets so that the internal style rear bracket is installed onto the replacement card and secure it using the two phillips head screws.
  5. Attach the external style rear bracket onto the old card using the two phillips head screws and place into the static bag for return.
  6. Install the internal HBA card into the riser in slot 3 by holding the PCIe riser in one hand and inserting the rear bracket that is attached to the internal HBA card into the rear connector on the PCIe riser.
  7. Insert the internal HBA card connector into the riser's bottom connector.
  8. Reconnect the SAS cable(s) to the internal HBA card.Be sure to connect the SAS cable for storage drives 0 through 3 (HDDs 0-3) to the connector that is farther from the riser in which the HBA card is installed. (this should match the order that the cables were installed before removal)
  9. Raise the PCIe riser green-tabbed release lever to the open (up) position and gently press the riser into the motherboard connector until it seats.
  10. Ensure that the rear bracket on the internal HBA card in PCIe slot 4 is connected to the slot in the server's chassis side wall. If the bracket is not connected, remove the riser and reposition it so that the rear bracket connects to the side wall, then gently press the riser into the motherboard connector.
  11. Slide the plastic PCIe card retainer that is mounted on the side of the chassis toward the back of the server to secure the card(s) installed in the riser.
  12. Press the green-tabbed release lever on the PCIe riser to the close (down) position.
  13. To secure the PCIe card's rear bracket to the server, close the green-tabbed latch on the rear of the server's chassis.
  14. If there is a PCIe card installed in slot 3 of the riser, reconnect any external or internal cables to the card.

4.Return the Server to operation

  1. Replace the top cover
  2. Remove any anti-static measures that were used.
  3. Return the server to it's normal operating position within the rack.
  4. Re-install the AC power cords and any data cables that were removed.
  5. Power on server. Verify that the Power/OK indicator led lights steady on.

5.  Since this is an Oracle Database Appliance, there is an additional step to check the firmware on the card.  Use the following oakcli command to confirm the firmware on the Controller is "Up-to-date".  Here is an example, the versions will change depending on what is running on the servers:

# oakcli validate -c SystemComponents
INFO: oak system information and Validations
RESULT: System Software inventory details
 Reading the metadata. It takes a while...
 System Version  Component Name            Installed Version         Supported Version
 --------------  ---------------           ------------------        -----------------
 12.1.2.3.0
                 Controller_INT            11.05.03.00               Up-to-date   <<< make sure this is Up-to-date
                 Controller_EXT            11.05.03.00               Up-to-date
                 Expander                  FFFF                      0018
                 SSD_SHARED                944A                      Up-to-date
                 HDD_LOCAL                 A690                      Up-to-date
                 HDD_SHARED                A690                      Up-to-date
                 ILOM                      3.2.4.20.a r94217         Up-to-date
                 BIOS                      25020500                  Up-to-date
                 IPMI                      1.8.12.0                  Up-to-date
                 HMP                       2.3.2.1.1                 Up-to-date
                 OAK                       12.1.2.3.0                Up-to-date
                 OL                        5.11                      Up-to-date
RESULT: System Information:-
        Manufacturer:Oracle Corporation
        Product Name:SUN SERVER X4-2
        Serial Number:1348NML02H
RESULT: BIOS Information:-
        Vendor:American Megatrends Inc.
        Version:25020500
        Release Date:08/11/2014
        BIOS Revision:2.5
        Firmware Revision:3.2
SUCCESS: Controller p1 has the IR Bypass mode set correctly
SUCCESS: Controller p2 has the IR Bypass mode set correctly
INFO: Reading ilom data, may take short while..
INFO: Read the ilom data. Doing Validations
RESULT: System ILOM Version: 3.2.4.20.a r94217
RESULT: System BMC firmware version  3.02
RESULT: Powersupply PS0 V_IN=236 Volts IN_POWER=110 Watts OUT_POWER=110 Watts
RESULT: Powersupply PS1 V_IN=238 Volts IN_POWER=130 Watts OUT_POWER=120 Watts
SUCCESS: Both the powersupply are ok and functioning
RESULT: Cooling Unit FM0 fan speed F0=5600 RPM F1=3300 RPM
RESULT: Cooling Unit FM1 fan speed F0=5600 RPM F1=3300 RPM
SUCCESS: Both the cooling unit are present
RESULT: Processor P0 present Details:-
        Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
        Current Speed:2700 MHz  Core Enabled:12 Thread Count:24
SUCCESS: All 8 memory modules of CPU P0 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Hynix Semiconductor
RESULT: Processor P1 present Details:-
        Version:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
        Current Speed:2700 MHz  Core Enabled:12 Thread Count:24
SUCCESS: All 8 memory modules of CPU P1 ok, each module is of Size:16384 MB Type:DDR3 Speed:1600 MHz manufacturer:Hynix Semiconductor
RESULT: Total Physical System Memory is 264360044 kB
SUCCESS: All OS Disks are present and in ok state
RESULT: Power Supply=17 degrees C

 

If you do not see the IR Bypass message or if the controller is not Up-to-date, run the following command:

# oakcli update --patch  <version> --infra

Note * be aware that this command will reboot the node

Note * if the controller is at a higher revision than the Installed Version, there is no need to run the infra update as shown above.  It is OK to run mismatched versions, and an infra update will NOT downgrade any firmware components

 

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.  Since the SAS controller only controls the 2 internal SAS drives, it's good practice to check the mdraid status on the disk:

# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdax1[1] sdaw1[0]
      513984 blocks [2/2] [UU]

md1 : active raid1 sdax2[1] sdaw2[0]
      585545088 blocks [2/2] [UU]

unused devices: <none>



REFERENCE INFORMATION:

Oracle Database Appliance Documentation

http://docs.oracle.com/cd/E22693_01/index.htm


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