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-1993394.1
Update Date:2018-05-16
Keywords:

Solution Type  Technical Instruction Sure

Solution  1993394.1 :   How to Replace an Oracle Server X5-2L, X6-2L Motherboard [VCAP]  


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
  •  
  • Microlearning>Video>ML-VID-VCAP
  •  




Oracle Confidential PARTNER - Available to partners (SUN).
Reason: this is a FRU

Applies to:

Oracle Server X5-2L - Version All Versions to All Versions [Release All Releases]
Oracle Server X6-2L - Version All Versions to All Versions [Release All Releases]
x86_64

Goal

How to Replace an Oracle Server X5-2L, X6-2L Motherboard.

Solution

DISPATCH INSTRUCTIONS

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

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 3

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: An Oracle Server X5-2L, X6-2L Motherboard needs replacement

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:

X5-2L Remove the Motherboard Assembly:
http://docs.oracle.com/cd/E41033_01/html/E48325/cnpsm.z40001d31037183.html#scrolltoc

X6-2L Remove the Motherboard Assembly:
http://docs.oracle.com/cd/E62172_01/html/E62184/z40001d31037183.html#scrolltoc


1. Log into the ILOM check the fruid container values and sync them if needed.

  1. To avoid mismatched fruid values causing a failure after a motherboard replacement the fruid data should be confirmed to have matching data in at least the Primary (DBP) and Backup2 (PS0) containers so that the motherboard will have it's container updated automatically after replacement. Go into restricted mode and use the showpsnc command to check this.  
    -> set SESSION mode=restricted

    WARNING: The "Restricted Shell" account is provided solely
    to allow Services to perform diagnostic tasks.

    [(restricted_shell) x5-2l]# showpsnc
    Primary: fruid:///SYS/DBP
    Backup 1: fruid:///SYS/MB
    Backup 2: fruid:///SYS/PS0


    Element           | Backup2 (7)        | Backup2 (8)
    ------------------+-------------------+-------------------
    PPN                 33154888+1+1        33154888+1+1
    PSN                 1449NM7002          1449NM7002
    Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
    [(restricted_shell) x5-2l]# exit
     
  2. The above example shows a system with all three containers properly in sync. If the output from the system does not show all of the containers with matching values then you should reset the SP and then re-check the values again. An ILOM reset will attempt to auto-populate the matching values if one container is out of sync.  
    -> reset /SP
    Are you sure you want to reset /SP (y/n)? y
    Performing reset on /SP
     
  3. After an ILOM reset if the Primary and Backup2 containers match then proceed with the following steps to replace the motherboard. If these two containers do not match then DO NOT proceed with the replacement yet.
  4. If the containers do not match you will need to use the copypsnc command from service or escalation mode to copy the data from the good container so that the Primary and Backup2 containers match (Backup1 is the MB and we are about to replace this so it is not as important at this step). If you are unfamiliar with this process and require assistance please reference the steps for using copypsnc to fix the serial number detailed in the "How to update product serial number on systems which implement TLI functionality (Doc ID 1280913.1)" and contact the TSC if needed. How to access service mode and escalation mode on ILOM 3.x and later platforms (Doc ID 1019946.1)
  5. After the fruid data in the Primary and Backup2 containers have been confirmed to match proceed with the following steps.

2. Make sure to back up the ILOM and BIOS configurations before replacing the motherboard.

  1. See the ILOM Administrator's Guide for Configuration and Maintenance Firmware Release 4.0.x for instructions:
    1. Backup the BIOS configuration https://docs.oracle.com/cd/E81115_01/html/E86149/z40001541481533.html#scrolltoc.
    2. Backup up the ILOM configuration https://docs.oracle.com/cd/E81115_01/html/E86149/z40048b81489311.html#scrolltoc.

3. 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 server Top Cover, all of the Fan Modules, the fan assembly door, or disk cage cover.

  see the service manual for instructions :http://docs.oracle.com/cd/E41033_01/html/E48333/z400061b1011790.html#scrolltoc

5. Remove the Oracle Storage 12 Gb/s SAS PCIe RAID HBA card, associated super capacitor, and the air baffle.

 see the service manual for instructions: http://docs.oracle.com/cd/E41033_01/html/E48333/gocfy.html#scrolltoc

6. Remove the power supplies.

  1. If the cable management arm (CMA) is installed, disconnect both CMA left-side connectors and move the CMA out of the way.
    Caution  -  When disconnecting the CMA left-side connectors, use something to support the CMA so that it does not hang down under its own weight and stress the right-side connectors; otherwise, the CMA might be damaged. You must continue to support the CMA until you have reconnected both of the left-side connectors.
  2. Grasp the power supply handle and push the power supply latch to the left.
  3. Pull the power supply out of the chassis.  Repeat steps b-c for the second power supply.
    Caution  -  When removing the power supplies it is important to label power supplies with the slot numbers from which they were removed (PS0, PS1). This is required because the power supplies must be reinstalled into the slots from which they were removed; otherwise, the server key identity properties (KIP) data might be lost.

7. Remove the PCIe cards.

 see the service manual for instructions: http://docs.oracle.com/cd/E41033_01/html/E48333/z40000f91037409.html#scrolltoc

8. Disconnect all the cables from the motherboard.

  1. (Optional) To disconnect the SAS cables between the rear storage drive backplane and front storage drive backplane, press each latch, and then pull out to disengage the cable from each SAS connector.  The connector is on the right side of the backplane when facing the front of the server.  The SAS cable connectors do not fit through the right-side chassis mid-wall. If you are removing SAS cables between the rear storage drive backplane and front storage drive backplane, you first must remove the chassis mid-wall.
  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.  The connectors are on the left side of the backplane when facing the front of the server.  Depending on the disk backplane configuration your front disk backplane SAS connector locations will be different.
  3. Remove the SAS cables from the server.  Carefully remove the SAS cable bundles from the chassis mid-wall. Be careful not to snag the cables on the server components.
  4. If present, disconnect the NVMe cables from the front storage drive backplane.  Depending on the disk backplane configuration your front disk backplane NVMe connector locations will be different.
  5. Remove the NVMe cables from the server.  Carefully remove the NVMe cable bundle from the chassis mid-wall. Be careful not to snag the cables on the server components.
  6. If the server has a DVD drive, disconnect the DVD drive cable from the motherboard SATA connector.  To remove the DVD drive cable, carefully guide it through the chassis mid-wall and place it on top of the disk cage so that it is away from the motherboard. You do not need to disconnect the DVD drive cable from the DVD drive.
  7. Disconnect the power cable from the motherboard to the rear storage drive backplane.  You do not need to remove the cable from the rear backplane end.  Just lay the cable on top of the rear disk cage so it is away from the motherboard.
  8. Disconnect the ribbon cables from the left front LED indicator module and right front LED/USB indicator module.
  9. Disconnect the auxiliary signal cable from the motherboard to the front storage drive backplane.
  10. Disconnect the power cable from the motherboard to the front storage drive backplane.
    Caution - If you have a 12 drive backplane configuration when disconnecting the power cable special care must be taken to not hit the 4 capacitors on the motherboard underneath. The lip of the power cable plug comes very close and in some cases can hit the capacitors knocking them off the motherboard. If you find the capacitor has been knocked off the motherboard ensure to remove the loose capacitor so it doesn't damage any other components.  The motherboard does NOT need to be replaced if 1 or all 4 capacitors have been knocked off. There is ample redundancy built into the design of the motherboard making these 4 capacitors totally redundant.  The motherboard and system will run normally with these capacitors removed.
  11. Disconnect the signal cable from the server intrusion switch.

9. Remove the mid-wall from the chassis.

  1. Using a hex/flat head screwdriver, remove the screw on each side of the chassis that secures the mid-wall to the chassis.
  2. Using a No. 2 Phillips screwdriver, loosen the four green captive screws that secure the chassis mid-wall to the bottom of the chassis.
  3. Lift the mid-wall out of the chassis.
  4. (Optional) Move the SAS cable between the rear storage drive backplane and front storage drive backplane out of the way now that the mid-wall has been removed.

10. Remove the motherboard from the server chassis.

  1. Remove the motherboard from the server with all reusable components that populate the motherboard in place.
  2. Grasp the metal bracket located just to the rear of the DIMM sockets and carefully slide the motherboard forward towards the front of the server, and lift it slightly to disengage it from the seven mushroom-shaped standoffs that are located on the server chassis under the motherboard.
  3. Lift the motherboard out of the server chassis and place it on an antistatic mat next to the replacement motherboard.

11. Remove the motherboard components.

  1. Remove the internal USB flash drives from the motherboard making note of the original port locations.
  2. Remove the DIMMs from the motherboard.
  3. Remove the processors from the failed motherboard.

 see the service manual fore instructions to remove the processors : http://docs.oracle.com/cd/E41033_01/html/E48333/z40001d31037145.html#scrolltoc

12. Install the motherboard components on the replacement board.

  1. Remove the processor socket covers from the replacement motherboard.
    1. Disengage the processor ILM (independent loading mechanism) assembly hinge lever on the right side of the processor socket (viewing the server from the front) by pushing down on the lever and moving it to the side away from the processor, and then rotating the lever upward.
    2. Disengage the processor ILM assembly load lever on the left side of the processor socket (viewing the server from the front) by pushing down on the lever and moving it to the side away from the processor, and then rotating the lever upward.
    3. To lift the processor ILM assembly load plate off of the processor socket, rotate the ILM assembly hinge lever on the right side of the processor toward the closed position (the load plate is lifted up as the hinge lever is lowered) and carefully swing the load plate to the fully open position.
    4. Grasp the top and underside of the processor socket cover with one hand (place your thumb against the underside of the cover), place your other thumb against the underside of the cover, and carefully push the cover out of the processor ILM assembly load plate.  Be careful not to allow the processor socket cover to fall into the processor socket as this could result in damage to the socket.
    5. Repeat steps 1-4 above to remove the second processor socket cover from the replacement motherboard.
  2. Install the socket covers on the bad motherboard processor sockets to protect the sockets during transport.
    1. Open one of the processor ILM assemblies on the failed motherboard.
    2. Hold the processor ILM assembly load plate open with one hand and position the processor socket cover over the top of the ILM assembly load plate so that 1) the arrow on the processor socket cover is aligned with the arrow on the top left bottom of the load plate and 2) the fasteners on one side of the cover (the fasteners are located on the underside of the cover) are inside the load plate (it does not matter which side), and use your thumb to press the other side of the processor socket cover into the load plate.  You will hear a clicking sound when the processor socket cover snaps into place.
    3. Close the processor ILM assembly load plate.
    4. Repeat Step 1 through Step 3 above to install the second processor socket cover on the failed motherboard.
  3. Install the processors on the replacement motherboard.

       see service manual for instruction to install the processors: http://docs.oracle.com/cd/E41033_01/html/E48333/z40001d31037155.html#scrolltoc 

     4.Install the DIMMs onto the replacement motherboard in the corresponding DIMM sockets on the replacement motherboard. Install the DIMMs only in the sockets (connectors) that correspond to the sockets from which they were removed.     Performing a one-to-one replacement of the DIMMs significantly reduces the possibility that the DIMMs will be installed in the wrong slots.

     5.Install the internal USB flash drives onto the replacement motherboard.  Ensure to place in the original USB port locations.

13. Install the motherboard into the server chassis.

  1. Grasp the metal bracket located to the rear of the DIMMs and carefully lift and place the motherboard assembly into the chassis. 
  2. Tilt the motherboard to the right side to fit under the power supply assembly, level the motherboard and place it into the server chassis, then slide it to the rear of the server to engage the raised standoffs.
  3. Ensure that the indicators, controls, and connectors on the rear of the motherboard fit correctly into the rear of the server chassis.

14. Install the server mid-wall.

  1. Lift and place the mid-wall into the chassis.
  2. (Optional) Install the cables between the front storage drive backplane and the rear storage drive backplane.  Route the SAS cable bundle through the chassis mid-wall and along the right side of the chassis.
  3. Using a No. 2 Phillips screwdriver, tighten the four green captive screws that secure the mid-wall to the bottom of the chassis.
  4. Using a hex/flat head screwdriver, insert and tighten the screw on each side of the chassis to secure the mid-wall in the chassis.

15. Reconnect all the cables to the motherboard.

  1. (Optional) Reconnect the power cable to the motherboard from the rear storage drive backplane.
  2. (Optional) To reconnect the SAS cables between the front storage drive backplane and the rear storage drive backplane, plug each cable into its SAS connector until you hear an audible click.  In twelve and twenty-four drive systems, attach the SAS cable to connector (J300) on the front storage drive backplane and to SAS connectors (RHDD0 and RHDD1) on the rear storage drive backplane.
  3. Reconnect the auxiliary signal cable to the motherboard from the front storage drive backplane.
  4. Reconnect the ribbon cables from left and right LED/USB indicator modules to the motherboard.
  5. Reconnect the power cable to the motherboard from the front storage drive backplane.
    Caution - If you have a 12 drive backplane configuration when connecting the power cable special care must be taken to not hit the 4 capacitors on the motherboard underneath. The lip of the power cable plug comes very close and in some cases can hit the capacitors knocking them off the motherboard. If you find the capacitor has been knocked off the motherboard ensure to remove the loose capacitor so it doesn't damage any other components.  The motherboard does NOT need to be replaced if 1 or all 4 capacitors have been knocked off. There is ample redundancy built into the design of the motherboard making these 4 capacitors totally redundant.  The motherboard and system will run normally with these capacitors removed.
  6. Reconnect the server intrusion switch cable to the motherboard.
  7. If the server has a DVD drive, reconnect the DVD drive cable.  To reconnect the DVD drive cable, carefully guide it through the chassis mid-wall and reconnect it to the motherboard SATA connector.

16. Reinstall the PCIe cards, associated super capacitor, and the air baffle.

  see the service manual for the SAS card and super capacitor and cables :http://docs.oracle.com/cd/E41033_01/html/E48333/gocfy.html#scrolltoc

  see the service manual for the remaining PCIe cards : http://docs.oracle.com/cd/E41033_01/html/E48333/z40000f91037409.html#scrolltoc

17. Reinstall the power supplies.

  1. Install power supply 0 into the server.
    Caution  -  When installing the power supplies it is important to install the power supplies in the same slot from which they were removed (PS0, PS1). This is required because the power supplies must be reinstalled into the slots from which they were removed; otherwise, the server key identity properties (KIP) data might be lost.
  2. Align the power supply with the empty power supply slot.
  3. Slide the power supply into the slot until it is fully seated.  You will hear an audible click when the power supply fully seats.
  4. Repeat steps b-c for power supply 1.
  5. If you disconnected the two CMA left-side connectors, reconnect the connectors.

18. Reinstall the Fan Modules, the fan assembly door, or disk cage cover.

see the service manual for instructions:http://docs.oracle.com/cd/E41033_01/html/E48333/z4000419165586.html#scrolltoc

19. Reinstall the Server Top Cover.

  1. Place the top cover on the chassis.  Set the cover down so that it hangs over the rear of the server by about 1 inch (25 mm) and the side latches align with the cutouts in the chassis.
  2. Check both sides of the chassis to ensure that the top cover is fully down and flush with the chassis.  If the cover is not fully down and flush with the chassis, slide the cover towards the rear of the chassis to position the cover in the correct position.
    Caution  -  If the top cover is not correctly positioned before you attempt to latch the cover, the internal latch that is located on the underside of the cover might be damaged.
  3. Gently slide the cover toward the front of the chassis until it latches into place (with an audible click).  As you slide the cover toward the front of the server, watch the green release button. You will hear an audible click when the green release button pops up, indicating that the cover is locked.

20. Return the Server to operation.

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

21. Set the system serial number/fruid data if needed.

  1. The motherboard is not the primary fruid container in this server so when it is replaced you will normally will not need to fix the serial number information.
  2. login to the ILOM as root and then enter the restricted shell to check the fruid values. Follow the example below to enter restricted shell and use the showpsnc command   
    -> set SESSION mode=restricted

    WARNING: The "Restricted Shell" account is provided solely
    to allow Services to perform diagnostic tasks.

    [(restricted_shell) x5-2l:~]# showpsnc
    Primary: fruid:///SYS/DBP
    Backup 1: fruid:///SYS/MB
    Backup 2: fruid:///SYS/PS0

    Element           | Primary
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 1449NM7002
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup1
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 0000000000
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup2 (7)        | Backup2 (8)
    ------------------+-------------------+-------------------
    PPN                 33154888+1+1        33154888+1+1
    PSN                 1449NM7002          1449NM7002
    Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
    [(restricted_shell) x5-2l:~]#
  3. When the motherboard is replaced the Primary fruid container will likely match the Backup entries. If it does not you must enter escalation or service mode to fix it (if all three entries match this step is done).
  4. Contact the TSC to request an escalation password (service mode will work also if just the copypsnc command ends up needing to be used, if the setpsnc command is needed escalation mode is required. setpsnc is not covered in this procedure).
  5. Provide your TSC contact the output from the following ILOM commands- "version", "show /SYS product_serial_number", and "show /SP/clock". If the product_serial_number information does not give good output then provide the showpsnc output that was seen in step b above as well.
  6. The TSC will provide an escalation password that is made up of 32 short words. Follow the example below to create a new user with the 'Service' role assigned. The Service role is required to access service or escalation modes. In the following example we will create a user named 'escuser' with the service role.
    -> cd /SP/users
    /SP/users
    -> create escuser
    Creating user...
    Enter new password: ********
    Enter new password again: ********
    Created /SP/users/escuser
    -> set escuser role=aucros
    Set 'role' to 'aucros'
    -> show escuser
    /SP/users/escuser
    Targets:
    ssh
    Properties:
    role = aucros
    password = *****
  7. Set the check_physical_presence to false and then exit from the ILOM so that you can login as the newly created user.
    -> set /SP check_physical_presence=false
    Set 'check_physical_presence' to 'false'
    -> show /SP check_physical_presence
    /SP
    Properties:
    check_physical_presence = false

    -> exit
  8. Login using the escuser login and enter escalation mode using the password that was provided by the TSC.
    X5-2l login: escuser
    Password:

    Oracle(R) Integrated Lights Out Manager

    Version 3.2.4.36 r95733

    Copyright (c) 2014, Oracle and/or its affiliates. All rights reserved.

    Warning: The system appears to be in manufacturing test mode.
    Contact Service immediately.

    Hostname: x5-2l

    -> cd /SP/users/ecsuser/escalation
    -> set SESSION mode=escalation                            
    Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** *
    Short form password is:  NOSE HAAG MED

    [(escalation_mode) X5-2l:~]#
  9. Use the showpsnc command to confirm the current container values. Confirm that one of the backup containers has a serial number (the value on the PSN line) that matches the system serial number. The system serial number can be checked by comparing to the serial number RFID tag on the front left hand side of the server. After confirming that there is a valid fruid backup use the copypsnc command to write the good data from the primary to the backup1 container on the MB. The following example shows copying from primary to the backup1 but you could also copy from backup2 if needed.
    [(escalation_mode) X5-2l:~]# showpsnc
    Primary: fruid:///SYS/DBP
    Backup 1: fruid:///SYS/MB
    Backup 2: fruid:///SYS/PS0

    Element           | Primary
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 1449NM7002
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup1
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 0000000000
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup2 (7)        | Backup2 (8)
    ------------------+-------------------+-------------------
    PPN                 33154888+1+1        33154888+1+1
    PSN                 1449NM7002          1449NM7002
    Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
    [(escalation_mode) X5-2l:~]# copypsnc Primary Backup1
    [(escalation_mode) X5-2l:~]# showpsnc
    Primary: fruid:///SYS/DBP
    Backup 1: fruid:///SYS/MB
    Backup 2: fruid:///SYS/PS0

    Element           | Primary
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 1449NM7002
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup1
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 1449NM7002
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup2 (7)        | Backup2 (8)
    ------------------+-------------------+-------------------
    PPN                 33154888+1+1        33154888+1+1
    PSN                 1449NM7002          1449NM7002
    Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
    [(escalation_mode) X5-2l:~]# exit

  10. At this point if all of the fruid containers match and have the correct serial number data this step is done. If more than one of the fruid containers had non-valid entries then the copypsnc command should be used to copy over the valid data to the other container that is not valid. (ie. "copypsnc Primary Backup2" to copy primary to backup2) After confirming all fruid data is correct reset the ILOM to confirm that the fruid data persists through a reboot and remove the escalation user if needed.
    -> reset /SP
    Are you sure you want to reset /SP (y/n)? y
    Performing reset on /SP
    ..........

    ***login as the root user again and check the fruid data***

    -> set SESSION mode=restricted

    WARNING: The "Restricted Shell" account is provided solely
    to allow Services to perform diagnostic tasks.

    [(restricted_shell) x5-2l]# showpsnc
    Primary: fruid:///SYS/DBP
    Backup 1: fruid:///SYS/MB
    Backup 2: fruid:///SYS/PS0

    Element           | Primary
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 1449NM7002
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup1
    ------------------+-------------------
    PPN                 33154888+1+1
    PSN                 1449NM7002
    Product Name        ORACLE SERVER X5-2L

    Element           | Backup2 (7)        | Backup2 (8)
    ------------------+-------------------+-------------------
    PPN                 33154888+1+1        33154888+1+1
    PSN                 1449NM7002          1449NM7002
    Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
    [(restricted_shell) x5-2l]#
    exit


    -> cd /SP/users
    /SP/users
    -> delete escuser
    Are you sure you want to delete /SP/users/escuser (y/n)? y
    Deleted /SP/users/escuser
  11. If trouble is encountered during any of the steps of accessing escalation mode and fixing the fruid containers please contact the TSC for assistance.

22. Make sure to restore the ILOM and BIOS configurations after replacing the motherboard.

  1. See the ILOM Administrator's Guide for Configuration and Maintenance Firmware Release 4.0.x for instructions:
    1. Restore the BIOS configuration https://docs.oracle.com/cd/E81115_01/html/E86149/z40001541481533.html#scrolltoc.
    2. Restore the ILOM configuration https://docs.oracle.com/cd/E81115_01/html/E86149/z40048b81489452.html#scrolltoc.

23. The bios must now be checked to confirm it is set to "Legacy mode" and not "UEFI mode".

  1. Change Boot Mode in BIOS to Legacy (Boot Mode = Legacy), as described here: http://docs.oracle.com/cd/E41059_01/html/E48312/napov.goiiw.html
    1. Enter the BIOS setup menu by pressing F2.
    2. BIOS menu -> Boot -> UEFI/BIOS Boot Mode, and select Legacy.
    3. Exit by "Save Changes and Exit"

 

 

How to verify the Motherboard is working properly.

     1.  Log into ILOM to confirm if the motherboard status is working properly.

Sample

-> show /SYS/MB

 /SYS/MB
    Targets:
        BIOS
        CPLD
        FM0
        FM1
        FM2
        FM3
        NET0
        NET1
        NET2
        NET3
        P0
        P1
        PCIE6
        RHDD0
        RHDD1
        T_CORE_NET01
        T_CORE_NET23
        T_IN_PS
        T_IN_ZONE0
        T_IN_ZONE1
        T_IN_ZONE2
        T_OUT_ZONE0
        T_OUT_ZONE1
        T_OUT_ZONE2

    Properties:
        type = Motherboard
        ipmi_name = MB
        fru_description = ASM,MOBO TRAY,2U
        fru_manufacturer = MiTAC International Corporation
        fru_part_number = 7098504
        fru_rev_level = 06
        fru_serial_number = 489089M+14414S041D
        fault_state = OK
        clear_fault_action = (none)

    Commands:
        cd
        set
        show

->



    2.  Check ILOM event log to see if any error related backplane.

-> show /SP/faultmgmt
-> show /SP/logs/event/list

 

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-2L Documentation:
http://docs.oracle.com/cd/E41033_01/index.html

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

Oracle Integrated Lights Out Manager (ILOM) 3.2 Documentation:
http://docs.oracle.com/cd/E37444_01/index.html


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