SPARC T7-1
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
 

Applies to:

Goal

How to Replace a SPARC T7-1 Service Processor Module (SPM)

Solution

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

DISPATCH INSTRUCTIONS

WHAT SKILLS ARE REQUIRED?: No special skills required, Customer Replaceable Unit (CRU) procedure

Time Estimate: 60 minutes

TASK COMPLEXITY: 0

REMOVAL/REPLACEMENT INSTRUCTIONS:

PROBLEM OVERVIEW: SPARC T7-1 Service Processor Module (SPM) Replacement

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

If the system is still up and functioning, the customer should perform an orderly and graceful shutdown of applications and OS. Then power off the server and remove the AC power cords from the system.

A data backup is not a prerequisite but is a wise precaution.

WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:

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.  

     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 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.
     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 Backup2 containers match (Backup1 is the SPM 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).
     e. After the fruid data in the Primary and Backup2 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 anti-static wrist strap.

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.
    b. Pull open the plastic tabs to release the clear plastic air duct assembly covers hinged edge and remove it from the server.

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.
    b. Lift the SPM up and away from 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.

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.
    b. Align the clear plastic air duct assembly cover on its hinge edge.
    c. Attach the hinged plastic tabs to the server by pulling them open and letting them seat into the holes so that the clear plastic air duct assembly cover can hinge up and down.
    d. Lower the clear plastic air duct assembly cover (making sure the two pairs of side tabs clear the sides of the server).

10. Install the top cover on the system

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

12. Prior to powering on the server, connect a terminal or a terminal emulator (PC or workstation) to the SP SER MGT port. If the SP detects that the new host firmware component is incompatible with SP firmware component, further action will be suspended and the following message will be delivered over the SER MGT port:

If you see this message, go on to Step #13.

13. Download the system firmware.
    a. Configure the SP’s 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.

    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.

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).
     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 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).
     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 backup1 container on the SPM. The following example shows copying from primary to the backup1, but you could also copy from backup2 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 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. 

     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 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 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_private/Systems/SPARC_T7_1/components.html#SystemServiceProcessor

REFERENCE INFORMATION:
SPARC T7-1 Service Manual: http://docs.oracle.com/cd/E54976_01/html/E54980/index.html

References

This solution has no attachment