![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 2161058.1 : How to Replace a SPARC S7-2L 24-Disk Backplane
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 24-Disk Backplane ************************************************************************************************************ ESD Caution:
Contamination Caution:
Solution DISPATCH INSTRUCTIONS 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 part to avoid any damages during shipping.
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. Then power off the server and remove the AC power cords from the system. Verify/Update TLI Prior to Replacement 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 (PS0) 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) s7-2l-bur09-a-sp:~]# showpsnc 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).[This section is not visible to customers.] e. After the fruid data in the Backup1 and Backup2 containers have been confirmed to match proceed with the following steps.
Remove Disk Backplane 1. 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.
d. Remove the server top cover. a. Open the Server Fan Door. Slide the fan door latches forward and swing the door up to the open position. 3. Remove the fan assembly door: a. Using a No. 2 Phillips screwdriver, remove the three screws from the top of the fan assembly door and the 2 screws (one on each side) from the sides where the door hinges. 4. Pull each storage disk out far enough to disengage it from the disk backplane. Note - It is not necessary to completely remove the storage drives from the server; simply pull them out far enough to disengage them from the disk backplane. If you do remove the storage drives from the server, record their locations so that you can reinstall them in the same locations.
5. Disconnect the cables from the drive backplane: a. Disconnect the two power cables and the auxiliary signal cable from the drive backplane. 6. Using a No. 2 Phillips screwdriver, loosen the two green captive screws that secure the drive backplane to the chassis. 7. Lift the drive backplane and attached SAS expander, over the 12 hooks that secure it, then lift the assembly up and out of the chassis. 8. Place the drive backplane on an antistatic mat.
Install Disk Backplane 1. Lower the drive backplane into the server, position it in front of the standoff hooks, then push the backplane into place. Note - The standoff hooks fit into small openings in the drive backplane.
Note - Ensure that all cables are clear of the drive backplane.
2. Using a No. 2 Phillips screwdriver, tighten the 2 green captive screws to secure the drive backplane to the disk cage. 3. Reconnect the cables to the drive backplane: a. Reconnect the auxiliary signal cable to the drive backplane. 4. Install all the fan modules: a. Position the fan modules into the server. 5. Install the fan assembly cover, and close the fan door: a. Place the fan assembly door on the server and slide it toward the front of the server, so that the 12 screw holes line up. 6. Fully install all storage drives you disengaged or removed. 7. Return the Server to operation. a. Remove any anti-static measures that were used. Note - Oracle Authorized Service personnel might need to reprogram the product serial number on the disk backplane. This number is used for service entitlement and warranty coverage. The correct product serial number is located on a label on the front of the chassis.
1. 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 0000000000 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:~]# 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. 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 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. [(escalation mode) s7-2l-bur09-a-sp:~]# showpsnc [(escalation mode) s7-2l-bur09-a-sp:~]# copypsnc Backup1 Primary [(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 Backup1 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) 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 disk backplane is working properly 1. Log into ILOM to confirm if disk backplane is working properly. Sample: -> show /SYS/DBP /SYS/DBP Properties: Commands: -> 2. Check ILOM event log to see if any error related the disk backplane. -> 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:
Attachments This solution has no attachment |
||||||||||||||
|