![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 2290637.1 : How to Replace SPARC T8-1 Disk Backplane [VCAP]
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). 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 SPARC T8-1 Disk Backplane Solution
************************************************************************************** ESD Caution:
Contamination Caution:
DISPATCH INSTRUCTIONS Note:
Damage Alert:
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 disk backplane (DBP) replacement the fruid data should be confirmed to have matching data in at least the Backup1 (SPM) and Backup2 (MB) containers so that the DBP 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) bur-t81-300-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 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 Backup1 and Backup2 containers match then proceed with the following steps to replace the DBP. 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.
1. Pull each storage disk out far enough to disengage it from the disk backplane. Note:
2. Remove the fan cover. a. Remove 12 screws on the top and side of the fan cover. Note:
b. Lift the fan cover from the server. 3. If necessary, remove the fan modules from the server. 4. Disconnect the cables from the disk backplane. a. Disconnect the two SAS cables from the disk backplane to the motherboard. Note:
b. Disconnect the power cable from the disk backplane. 6. Lift up on the left-side spring tab, and then gently release the disk backplane from the standoff hooks and out from under the spring tab. 7. Pull the storage disk backplane away from the standoff hooks and spring tab and out of the chassis and place it on an antistatic mat. 8. Lower the new disk backplane into the server, and then position it under the spring tab to engage the standoff hooks. a. The standoff hooks fit into small openings in the disk backplane. 9. Using a No. 2 Phillips screwdriver, install and tighten the spring-mounted screw (on the power supply side of the server) to secure the disk backplane to the chassis. 10. Reconnect the cables to the disk backplane. a. Reconnect the auxiliary signal cable to the drive backplane. 11. Reinstall the fan modules if they were removed and replace the fan cover by securing the cover with either the 12 T6 Torx screws or 12 No. 2 Phillips screws that were removed in Step #2. Note:
12. Return the Server to operation. a. Remove any anti-static measures that were used. Note:
1. Set the system serial number/fruid data if needed. a. The disk backplane is the primary fruid container in this server so when it is replaced you will normally need to fix the serial number information. -> set SESSION mode=restricted
WARNING: The "Restricted Shell" account is provided solely to allow Services to perform diagnostic tasks. [(restricted_shell) bur-t81-300-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 c. When the disk backplane is replaced the Primary fruid container will likely not 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). -> 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. bur-t81-300-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: bur-t81-300-sp -> cd /SP/users/escuser/escalation -> set SESSION mode=escalation Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** * Short form password is: NOSE HAAG MED [(escalation_mode) bur-t81-300-sp:~]# i. 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 backup to the primary container on the DBP. The following example shows copying from backup1 to the primary but you could also copy from backup2 if needed. [(restricted_shell) bur-t81-300-sp:~]# showpsnc
Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 [(restricted_shell) bur-t81-300-sp:~]# copypsnc Backup1 Primary [(restricted_shell) bur-t81-300-sp:~]# showpsnc Element | Primary | Backup1 | Backup2 [(restricted_shell) bur-t81-300-sp:~]# exit 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 Backup1 Backup2" to copy backup1 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) bur-t81-300-sp:~]# showpsnc Primary: fruid:///SYS/DBP Backup 1: file:///persist/psnc_backup1.xml Backup 2: fruid:///SYS/MB Element | Primary | Backup1 | Backup2 [(restricted_shell) bur-t81-300-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 Disk Backplane is working properly -> show /SYS/DBP
/SYS/DBP Targets: HDD0 HDD1 HDD2 HDD3 HDD4 HDD5 HDD6 HDD7 NVME0 NVME1 NVME2 NVME3 Properties: type = Disk Backplane ipmi_name = DBP fru_description = ASSY,8DBP,1U/2U fru_manufacturer = Oracle Corporation fru_part_number = 7097205 fru_rev_level = 05 fru_serial_number = 489089M+17036L4BTD fault_state = OK clear_fault_action = (none) Commands: cd set show -> 2. Check ILOM event log to see if any error related to the disk backplane. -> show /SP/faultmgmt
-> show /SP/logs/event/list
WHAT ACTION DOES THE FE/CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
PARTS NOTE: REFERENCE INFORMATION:
References<NOTE:1571054.1> - Performing an AC power cycle on the T3/T4/T5/S7/T7/T8 ServersAttachments This solution has no attachment |
||||||||||||||||
|