![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 2289554.1 : How to Replace a SPARC T8-1 Service Processor Module (SPM) [VCAP]
Applies to:SPARC T8-1 - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. GoalHow to Replace a SPARC T8-1 Service Processor Module (SPM) Solution
ESD Caution:
Contamination Caution:
Warning:
DISPATCH INSTRUCTIONS PROBLEM OVERVIEW: SPARC T8-1 Service Processor Module (SPM) Replacement WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?: Note:
Damage Alert:
Note:
Replace the Service Processor Module (SPM) 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 Service Processor Module (SPM) replacement the fruid data should be confirmed to have matching data in at least the Primary (DBP) and Backup2 (MB) containers so that the SPM 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) t8-1-bur09-a-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 ------------------+-------------------+-------------------+------------------- PPN 35129165+1+1 35129165+1+1 35129165+1+1 PSN 1733NN80PF 1733NN80PF 1733NN80PF MACADDR 00:10:E0:D5:BA:E8 00:10:E0:D5:BA:E8 00:10:E0:D5:BA:E8 HOSTID 86d5bae8 86d5bae8 86d5bae8 Product Name SPARC T8-1 SPARC T8-1 SPARC T8-1 RFID SN 341A583DE5800000000225BB 341A583DE5800000000225BB 341A583DE5800000000225BB [(restricted_shell) t8-1-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 SP reset if the Primary and Backup2 containers match then proceed with the following steps to replace the SPM. 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. 3. Remove the Top Cover of system. 4. Open the clear plastic air duct assembly cover by lifting the edge of the cover closest to the rear of the server. The cover can stand in its upright position but perform the next steps if you need to remove the cover: a. Open the fan cover. 5. Locate the SPM toward the back of the system between the PCIe cards. 6. Remove the SPM a. Grasp the SPM by the two grasp points and lift up to disengage the SPM from the connectors on the motherboard. 7. Lower the side of the SPM with the Align Tab sticker at an angle down on the SPM tab on the motherboard. 8. Press the SPM straight down until it is fully seated in its socket. Caution:
9. Close the clear plastic air duct assembly cover by rotating it down over the motherboard / two memory risers and then slightly pressing in the two tabs to secure it. See following if you need to reattach the cover: a. Open the fan cover. Unrecognized Chassis: This module is installed in an unknown or unsupported chassis. You must upgrade the firmware to a newer version that supports this chassis.
If you see this message, go on to Step #13. Otherwise, skip to Step 14. Note:
13. Download the system firmware. Note:
c. If a backup file was created, use the Oracle ILOM restore utility to restore the configuration of the replacement service processor. 14. Set the ILOM time/date (-> set /SP/clock datetime=MMDDhhmmYYYY.ss) 15. Power on server. Verify that the Power/OK indicator led lights steady on. 16. Verify that the SP Status LED is illuminated green. Note:
Important:
17. Set the system serial number/fruid data if needed. a. The SPM is not the primary fruid container in this server so when it is replaced you should not normally need to fix the serial number information (TLI). -> set SESSION mode=restricted
WARNING: The "Restricted Shell" account is provided solely to allow Services to perform diagnostic tasks. [(restricted_shell) t8-1-bur09-a-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 ------------------+-------------------+-------------------+------------------- PPN 35129165+1+1 35129165+1+1 35129165+1+1 PSN 1733NN80PF 0000000000 1733NN80PF MACADDR 00:10:E0:D5:BA:E8 00:10:E0:D5:BA:E8 00:10:E0:D5:BA:E8 HOSTID 86d5bae8 86d5bae8 86d5bae8 Product Name SPARC T8-1 SPARC T8-1 SPARC T8-1 [(restricted_shell) t8-1-bur09-a-sp:~]# c. When the SPM is replaced the Backup1 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. t8-1-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: t8-1-bur09-a-sp -> cd /SP/users/ecsuser/escalation -> set SESSION mode=escalation Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** * Short form password is: NOSE HAAG MED [(escalation_mode) t8-1-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 backup1 container on the SPM. The following example shows copying from primary to the backup1, but you could also copy from backup2 if needed. [(escalation mode) t8-1-bur09-a-sp:~]# showpsnc [(escalation mode) t8-1-bur09-a-sp:~]# copypsnc Primary Backup1 [(escalation mode) t8-1-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 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) t8-1-bur09-a-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 -------------------+------------------------+-------------------------+------------------- PPN 35129165+1+1 35129165+1+1 35129165+1+1 PSN 1733NN80PF 1733NN80PF 1733NN80PF MACADDR 00:10:E0:D5:BA:E8 00:10:E0:D5:BA:E8 00:10:E0:D5:BA:E8 HOSTID 86d5bae8 86d5bae8 86d5bae8 Product Name SPARC T8-1 SPARC T8-1 SPARC T8-1 [(restricted_shell) t8-1-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 SPM is working properly 1. Log into ILOM to check SPM status. Sample: -> show SPM
/SYS/MB/SPM Properties: Commands: -> -> 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:1571054.1> - Performing an AC power cycle on the T3/T4/T5/S7/T7/T8 Servers<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 |
||||||||||||
|