SPARC T7-4
 

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 CAP

Applies to:

Goal

How to Replace a SPARC T7-4 Rear Chassis Subassembly (RCSA)

Solution

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

DISPATCH INSTRUCTIONS

WHAT SKILLS ARE REQUIRED?: SPARC T7-4 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: 120 minutes

Task Complexity: 1

REMOVAL/REPLACEMENT INSTRUCTIONS:

PROBLEM OVERVIEW: SPARC T7-4 Rear Chassis Subassembly (RCSA) 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 NEED TO TAKE:

Replace the Rear Chassis Subassembly (RCSA)

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 Rear Chassis Subassembly (RCSA) replacement the fruid data should be confirmed to have matching data in at least the Backup1 (SPM) and Backup2 (FIO; Front I/O Module) containers so that the RCSA 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 Backup1 and Backup2 containers match then proceed with the following steps to replace the RCSA. 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 RCSA 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 Backup1 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. Attach an anti-static wrist strap.

3. Go to the rear of the server and remove the following components:

    a. All five fans
    b. All PCIe carriers (being used or not). Make note of the slots for each carrier so that you can install them into the same slots after replacement.
    c. Rear I/O module (RIO) 

4. Go to the front of the server and remove the following components:

    a. Both processor modules or processor filler modules
    b. Main module motherboard
    c. All four power supplies

5. Locate the eight green mounting screws that secure rear chassis subassembly (RCSA).

6. Using a flat head screwdriver (some servers may use TORX wrench), loosen the eight screws that secure the rear chassis subassembly (RCSA) to the system chassis.

7. Slide the rear chassis subassembly (RCSA) out and away from the server.

8. Slide the replacement rear chassis subassembly (RCSA) into the rear of the server.

9. Using a flat head screwdriver (some servers may use TORX wrench), tighten the eight green screws to secure the rear chassis subassembly (RCSA) in the server.

    a. Tighten the screws in the following order: 

        Lower right outside screw.

        Upper left outside screw.

        Upper right outside screw.

        Lower left outside screw.

        Lower right inside screw.

        Upper left inside screw.

        Upper right inside screw.

        Lower left inside screw.

10. Remove the connector covers from the replacement rear chassis subassembly (RCSA).

11. Install all four power supplies, main module, and processor modules that were removed from the front of the server.

12. Install the following components back into the rear of the server:

    a. All five fans
    b. All PCIe carriers. Verify that you are installing the PCIe cards back in their original slots using the notes that you took when removing the cards from the slots earlier.
    c. Rear I/O module 

13. Return the Server to operation.

    a. Remove any anti-static measures that were used.
    b. Re-install the AC power cords and any data cables that were removed.
    c. Power on server. Verify that the Power/OK indicator led lights steady on.

14. Set the system serial number/fruid data, if needed.

     a. The RCSA is the primary fruid container in this server so when it is replaced you will 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 RCSA 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.       

      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 backup use the copypsnc command to write the good data from the backup to the primary container on the RCSA. The following example shows copying from backup1 to the primary 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 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. 

     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/ADMINISTRATOR 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_partner/Systems/SPARC_T7_4/components.html#Chassis

REFERENCE INFORMATION:
SPARC T7-4 Service Manual: http://docs.oracle.com/cd/E54990_01/html/E54994/index.html

See also:  Oracle Integrated Lights Out Manager (ILOM) 3.2.1 Documentation Collection: http://docs.oracle.com/cd/E37444_01/

Save

Save

References

This solution has no attachment