![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 2148126.1 : How to Replace a SPARC S7-2L Motherboard and SP (Embedded Service Processor) [VCAP]
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:SPARC S7-2L - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. GoalHow to replace a SPARC S7-2L Motherboard *************************************************************************************************************** Solution ESD Caution:
Contamination Caution:
DISPATCH INSTRUCTIONS PROBLEM OVERVIEW: SPARC S7-2L Motherboard Replacement DAMAGE ALERT: Perform a visual inspection of the replacement part to make sure that there are no damaged components, connectors, bent pins, damaged packages during shipping, etc). If the part is damaged, don't install it into the system, order a new part. Handle with caution and package carefully the return FRU just as the new FRU was packaged, to avoid any damages during shipping.
Note - The LDOM configuration (if any) needs to be saved before motherboard replacement to avoid loss of LDOM configuration, refer to doc 1019720.1 for details.
NOTE: When replacing the service processor (SP), you need to backup/restore the configuration settings maintained in the SP. Before replacing the SP, save the configuration using the Oracle ILOM backup utility. Refer to the Oracle Integrated Lights Out Manager (ILOM) 3.2.x Documentation for instructions on Backing up and Restoring the Oracle ILOM configuration.
Note - A data backup is not a prerequisite but is a wise precaution.
Customer should perform an orderly and graceful shutdown of applications and OS to get the OpenBoot PROM prompt. Run the printenv command and make a note of any OpenBoot PROM variables that have been modified. Then power off the server and remove the AC power cords from the system. WHAT ACTION DOES THE ENGINEER NEED TO TAKE: Replace the Motherboard 1. Log into the ILOM and check the fruid container values and sync them if needed. a. 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 Backup1 (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) s7-2l-bur09-a-sp:~]$ showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///SYS/PS0 Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 ------------------+----------------------+-----------------------+------------------- PPN 34235727+1+1 34235727+1+1 34235727+1+1 PSN AK00370269 AK00370269 AK00370269 MACADDR 00:10:E0:B3:0C:28 00:10:E0:B3:0C:28 00:10:E0:B3:0C:28 HOSTID 86b30c28 86b30c28 86b30c28 Product Name SPARC S7-2L SPARC S7-2L SPARC S7-2L [(restricted_shell) s7-2l-bur09-a-sp:~]$ exit b. 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 c. After an ILOM reset if the Primary and Backup 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. 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). 2. Prepare the server for service. a. Power off the server and disconnect the power cords from the power supplies. Caution - Components inside the chassis might be hot. Use caution when servicing components inside the chassis.
Note - When replacing the motherboard, you will need to remove the SCC PROM from the old motherboard and install the component on the new motherboard. The SCC PROM contains the system host ID and MAC address. Transferring these components preserves the system-specific information stored on these modules.
3. Remove the top cover and open the fan door to remove all of the fan modules. 4.Remove clear plastic air duct assembly cover: Note - Always remove transceivers from a PCIe card(s) before removing the card from the server.
Note - Keep track of which slot each PCIe card was in so you can return them to their original positions Removing PCIe cards in slots 1 through 6 a. Unplug all data cables from the PCIe card Removing PCIe card in slot 7 a. PCIe slot 7 is located on the mother board between the CMP0 DIMMs and the left side of the chassis. It contains the on board SAS disk controller. 6. If you are replacing the motherboard, remove the following components and place them on an ESD mat: a. Remove all DIMMs on motherboard. Note - 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. If you do not reinstall the DIMMs in the same sockets, server performance might suffer and some DIMMs might not be used by the server.
7. Remove SAS storage drive cables 8. Remove NVMe cables 9. Remove Power Supplies Note - During the motherboard removal procedure, 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 (TLI) data might be lost
10. Disconnect the power cable from the motherboard to the rear storage drive backplane 11. Disconnect the ribbon cables from the left front LED indicator module and right front LED/USB indicator module 12. Disconnect the auxiliary signal cable from the motherboard to the front storage drive backplane 13. Disconnect the power cable from the motherboard to the front storage drive backplane 14. Disconnect the signal cable from the server intrusion switch 15. Remove the server mid-wall a. Using a hex/flat head screwdriver, remove the screw on each side of the chassis that secures the mid-wall to the chassis 16. Remove the mother board a. Carefully slide the motherboard forward, and lift it out of the chassis 17. Remove the eUSB drive from the motherboard and install it on the replacement motherboard. a. Loosen the screw that attaches the eUSB drive to the motherboard. 18. Remove the SEEPROM from the motherboard and install it on the replacement motherboard Install motherboard 1. Insert the motherboard into the server chassis a.Carefully lift and place the motherboard assembly into the chassis. 2. Install the mid-wall into the chassis. a. Lift and place the mid-wall into the chassis 3. Insert Power Supplies Note - When reinstalling power supplies, it is important to reinstall them into the slots from which they were removed during the motherboard removal procedure; otherwise, the server key identity properties (TLI) data might be lost
4. Insert PCIe Cards in Slots 1-6 a. Insert the PCIe card into the correct slot [1], and rotate the PCIe locking mechanism to secure the PCIe card in place 5. Installing PCIe card in slot 7 a. PCIe slot 7 is located on the mother board between the CMP0 DIMMs and the left side of the chassis. It contains the on board SAS disk controller. 6. Install NVMe Cables 7. Install SAS storage drive cables 8. Install Fan Modules a. Press down on the fan module and apply firm pressure to fully seat the fan module. 9. Install the air baffle a. Install the air baffle by placing it into the server 10. Return the Server to operation. a. Remove any anti-static measures that were used. a. If needed, configure the SP network port to enable the firmware image to be downloaded. Refer to the Oracle ILOM documentation for network configuration instructions. Note - The LDOM configuration (if any) needs to be restored after motherboard replacement to avoid loss of LDOM configuration, refer to doc 1019720.1 for details.
12. Power on server. Verify that the Power/OK indicator led lights steady on. 13. When you replace a motherboard since it the contains the SP, you will need to download the fallback miniroot image for your hardware and your Oracle Solaris version from My 14. Set the system serial number/fruid data if needed. -> set SESSION mode=restricted
WARNING: The "Restricted Shell" account is provided solely to allow Services to perform diagnostic tasks. [(restricted_shell) s7-2l-bur09-a-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///SYS/PS0 Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 ------------------+-------------------+-------------------+------------------- PPN 34235727+1+1 34235727+1+1 34235727+1+1 PSN AK00370269 AK00370269 0000000000 MACADDR 00:10:E0:B3:0C:28 00:10:E0:B3:0C:28 00:10:E0:B3:0C:28 HOSTID 86b30c28 86b30c28 86b30c28 Product Name SPARC S7-2L SPARC S7-2L SPARC S7-2L [(restricted_shell) s7-2l-bur09-a-sp:~]# c. When the motherboard is replaced the Backup2 fruid container will likely not match the Primary entry. If it does not you must enter escalation or service mode to fix it (if all three entries match this step is done). -> 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 = ***** g. 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 h. Login using the escuser login and enter escalation mode using the password that was provided by the TSC. s7-2l-bur09-a-sp login: escuser
Password: Oracle(R) Integrated Lights Out Manager Version 3.2.4.34 r95732 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: s7-2l-bur09-a-sp -> cd /SP/users/ecsuser/escalation -> set SESSION mode=escalation Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** * Short form password is: NOSE HAAG MED [(escalation_mode) s7-2l-bur09-a-sp:~]# i. Use the showpsnc command to confirm the current container values. Confirm that the primary container 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 primary use the copypsnc command to write the good data from the primary to the backup2 container on the MB. The following example shows copying from primary to the backup2, but you could also copy from backup1 if needed. [(escalation mode) s7-2l-bur09-a-sp:~]# showpsnc [(escalation mode) s7-2l-bur09-a-sp:~]# copypsnc Primary Backup2 [(escalation mode) s7-2l-bur09-a-sp:~]# showpsnc j. 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 Backup1") 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) s7-2l-bur09-a-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///SYS/PS0 Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 -------------------+------------------------+-------------------------+------------------- PPN 34235727+1+1 34235727+1+1 34235727+1+1 PSN AK00370269 AK00370269 AK00370269 MACADDR 00:10:E0:B3:0C:28 00:10:E0:B3:0C:28 00:10:E0:B3:0C:28 HOSTID 86b30c28 86b30c28 86b30c28 Product Name SPARC S7-2L SPARC S7-2L SPARC S7-2L [(restricted_shell) s7-2l-bur09-a-sp:~]# 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 k. If trouble is encountered during any of the steps of accessing escalation mode and fixing the fruid containers please contact the TSC for assistance. How to verify the Motherboard is working properly 1. Log into ILOM to confirm if motherboard status is working properly. Sample: -> show /SYS/MB /SYS/MB type = Motherboard Commands: -> 2. Check ILOM event log to see if any error related motherboard. -> show /SP/faultmgmt
-> show /SP/logs/event/list
OBTAIN CUSTOMER ACCEPTANCE WHAT ACTION DOES THE FE/CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE: REFERENCE INFORMATION:
References<NOTE:1280913.1> - How to update System, Chassis, and Product level Key Identity Properties on ILOM based systems which implement Top Level Identifier (TLI) functionality<NOTE:1019946.1> - How to access service mode and escalation mode on ILOM 3.x and later platforms Attachments This solution has no attachment |
||||||||||||||||
|