How to replace a SPARC S7-2L 12-Disk (NVMe) Backplane [VCAP]

Asset ID:	1-71-2146275.1
Update Date:	2017-11-15
Keywords:

Solution Type Technical Instruction Sure

Solution 2146275.1 : How to replace a SPARC S7-2L 12-Disk (NVMe) Backplane [VCAP]

Applies to:

SPARC S7-2L - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

How to Replace a SPARC S7-2L 12-Disk (NVMe) Backplane

*********************************************************************************************************************
To report errors or request improvements on this procedure, please go to http://support.us.oracle.com and put a comment on Doc ID: 2146275.1
*********************************************************************************************************************

Solution

ESD Caution:

Circuit boards and drives contain electronic components that are extremely sensitive to static electricity. Ordinary amounts of static electricity from clothing or the work environment can destroy the components located on these boards. Do not touch the components along their connector edges.
Use a Antistatic Wrist strap. Attach one end of the strap to your wrist and the other end to the chassis, depending on what type of strap you use, with the adhesive end or the metal plug.
Use an Antistatic Mat. Place ESD-sensitive components such as motherboards, memory, and other PCBs on an antistatic mat.

Contamination Caution:

Dust particles of packaging material are number one cause of datacenter contamination. Make sure to remove all packaging material, up to the ESD safe packaging material, while still being outside the datacenter.

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:
SPARC S7-2L Product Training required, to be serviced by qualified Oracle Service personnel, requires the ability to follow steps similar to what is in the Product Service manual.

Time Estimate: 60 minutes

TASK COMPLEXITY: 1

FIELD ENGINEER INSTRUCTIONS

PROBLEM OVERVIEW: SPARC S7-2L 12-Disk (NVMe) Backplane Replacement

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :

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.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

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
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 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.
d. 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 Backup1 and Backup2 containers match (Primary is the DBP 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).[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.
b. Extend the server to the maintenance position in the rack.
c. Attach an antistatic wrist strap to your wrist and then to a metal area on the chassis.

Caution - Components inside the chassis might be hot. Use caution when servicing components inside the chassis.

d. Remove the server top cover.
e. Remove the air baffle from the chassis.

2. Remove all of the Fan Modules.

a. Open the Server Fan Door. Slide the fan door latches forward and swing the door up to the open position.
b. Using your thumb and forefinger, loosen the captive screw that secures the fan module in the chassis (use a No. 2 Phillips screwdriver if it is too tight to loosen with your fingers).
c. Grasp both the captive screw and the opposite end of the module and lift the fan module straight up and out of the chassis (do not rock it back and forth), and set it aside on an antistatic mat. Rocking the fan module can cause damage to the motherboard connectors.

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.
b. Remove the door from the chassis.

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 from the drive backplane.
b. Disconnect the 12 NVMe cables from the drive backplane.
c. Disconnect the auxiliary signal cable from the drive backplane.

6. Using a No. 2 Phillips screwdriver, loosen the 2 green spring-mounted screws that secure the drive backplane to the chassis.

7. Pull the drive backplane towards the rear of the server, away from the stand-off hooks, and then out of the chassis.

8. Place the drive backplane on an antistatic mat.

Install Drive Backplane

1. Lower the drive backplane into the server, position it in front of the eight standoff hooks, then push the backplane down and into place.

Note - The standoff hooks fit into small openings in the drive backplane. Align the center double hook first.

Note - Ensure that all cables are clear of the drive backplane.

2. Using a No. 2 Phillips screwdriver, tighten the two green spring-mounted 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.
b. Reconnect the two power cable to the drive backplane.
c. Connect the twelve NVMe cables to the drive backplane. Attach the cables to the similarly labeled connectors.

4. Install all the fan modules:

a. Position the fan modules into the server.
b. Press down on the fan module and apply firm pressure to fully seat the fan module.
c. Using your thumb and forefinger, tighten the captive screw to secure each of the fan modules to the chassis. Then use a No. 2 Phillips screwdriver to tighten the screw an additional 1/4 turn to secure the fan module to the chassis.

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.
b. Using a No. 2 Phillips screwdriver, insert the six screws on from the top of the fan assembly door. Using a Torx screwdriver, insert the remaining six (three on each side) T6 Torx screws to secure the fan assembly door.
c. Close the fan door.

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.
b. Return the server to it's normal operating position within the rack.
c. Re-install the AC power cords and any data cables that were removed.
d. Power on server. Verify that the Power/OK indicator led lights steady on.

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.

Verify/Update TLI After Replacement

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.
b. 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) 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).
d. 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).
e. 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.
f. 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 = *****

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
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

[(escalation mode) s7-2l-bur09-a-sp:~]# copypsnc Backup1 Primary

[(escalation mode) 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
[(escalation mode) s7-2l-bur09-a-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") 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
Targets:

NVME0
NVME1
.

.
NVME10
NVME11

Properties:
type = Disk Backplane
ipmi_name = DBP
fru_description = ASSY,12DBP,2U
fru_manufacturer = Oracle Corporation
fru_part_number = 7307304
fru_rev_level = 08
fru_serial_number = 489089M+14466L03M7
fault_state = OK
clear_fault_action = (none)

Commands:
cd
set
show

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:
Boot system and monitor boot sequence for errors. Test functionality of system:
1. Run the Solaris "fmadm faulty" and SP/ILOM "show faulty" command (if only ALOM is supported run "showfaults -v" command) to verify that the fault has been cleared.
2. Perform one of the following tasks based on your verification results:
   * If the previous steps did not clear the fault, refer to doc 1004229.1 for information about the tools and methods you can use to diagnose and clear
     component faults.
   * If the previous steps indicate that no faults have been detected, the component has been replaced successfully. No further action is required
3. Restart software applications per applicable administration guides to resume system operation.

PARTS NOTE:
https://support.oracle.com/handbook_partner/Systems/SPARC_S7_2L/components.html#DiskBackplane

REFERENCE INFORMATION:
SPARC S7-2L Service Manual: http://docs.oracle.com/cd/E72363_01/html/E73201/index.html

Save

Attachments

This solution has no attachment