Netra SPARC S7-2
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
 
Microlearning>Video>ML-VID-VCAP
 

In this Document

Goal

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU part

Applies to:

Goal

How to Replace a Netra SPARC S7-2 Power Distribution Board

*******************************************************************************
To report errors or request improvements on this procedure, please add a comment on Doc ID: 2159829.1
*******************************************************************************

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS ARE REQUIRED?: Field Replaceable Unit (FRU) procedure

TIME ESTIMATE: 30 minutes

TASK COMPLEXITY: 1

REMOVAL/REPLACEMENT INSTRUCTIONS:

PROBLEM OVERVIEW: Netra SPARC S7-2 Power Distribution Board (PDB) Replacement

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

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 ACTIONS ARE REQUIRED?: 

Remove Power Distribution Board (PDB)

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.

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.

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.
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 Primary and Backup1 containers match (Backup2 is the motherboard 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 Primary and Backup1 containers have been confirmed to match proceed with the following steps.

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

3. Remove the top cover.

a. To open the server top cover, press and hold down the top cover release button and use the recessed area to slide the top cover toward the rear of the server about 0.5 inches (12.7 mm).
b. Lift the cover off the chassis and set it aside.

4. Open the front bezel.

5. Remove all Fan Modules.

6. Remove the Fan Tray.

7. Disconnect the disk backplane cables & rotate the Drive Cage to the service position.

8. Remove the USB cable from the PSU duct's channel & then remove the PSU duct.

9. Loosen the cables from the main air duct assembly.

10. Loosen the left thumb screw bracket, slide it forward to remove, & then remove the air duct.

11. Remove Power Supplies

12. Disconnect the cable from the PDB.

13. Remove DIMMs near the PDB.

14. Unscrew the 2 captive screws on the front of the motherboard & slide it forward.

15. Remove the four screws securing the PDB to the bus bars.

16. Loosen the two captive screws securing the PDB to the server, & remove the PDB from the server.

Install Power Distribution Board

1. Insert the PDB & screw in the 2 securing screws into the chassis.

2. Screw in the 4 bus bar screws.

3. Slide the motherboard back & tighten the 2 captive screws on the front of the motherboard.

4. Attach the PDB's cable.

5. Insert both Power Supplies.

6. Insert removed DIMMs

7. Place the main air duct assembly in position.

8. Place the left thumb screw bracket in position, slide it back, then tighten the thumb screw.

9. Fasten the disk cables to the Air Duct.

10. Install the PSU air duct & then route the USB cable in it's channel.

11. Rotate the Drive Cage to the service position & connect the disk backplane cables.

12. Install Fan Tray.

13. Install the fan modules.

14. Close the front bezel.

15. Install the server top cover.  Place the server top cover on the chassis and slide the top cover toward the front of the server (about 0.5 inches (12.7 mm)) until you hear the top cover release button lock into place.

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

17. Prior to powering on the server, connect a terminal or a terminal emulator (PC or workstation) to the SER MGT port.

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.
b. Download the system firmware. Follow the firmware download instructions in the Oracle ILOM documentation

18. Power on server. Verify that the Power/OK indicator led lights steady on.

19. Set the system serial number/fruid data if needed.

a. The motherboard 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).
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:

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

g. Set the check_physical_presence to false and then exit from the ILOM so that you can login as the newly created user.

h. Login using the escuser login and enter escalation mode using the password that was provided by the TSC.

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.

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.

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.

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTIONS ARE REQUIRED 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 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. Run format (# format) under Solaris to verify that the eUSB device can be seen.

4. Restart software applications per applicable administration guides to resume system operation.


PARTS NOTE:
https://support.oracle.com/handbook_partner/Systems/Netra_S7_2/components.html#Power

REFERENCE INFORMATION:
Netra SPARC S7-2 Service Manual: http://docs.oracle.com/cd/E72798_01/pdf/E73207.pdf

Save

Save

Save

Save

Save

Save

References

This solution has no attachment