Sun Netra T2000 Server
 

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

Applies to:

Goal

How to Replace a Netra T2000 Power Distribution Board

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

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:  T2000 Product Training or Experience

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 1

FIELD ENGINEER INSTRUCTIONS

PROBLEM OVERVIEW: PDB failure

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?  N/A

WHAT ACTION DOES ENGINEER NEED TO TAKE:

1. Shutting System Down

2. Extending Server to Maintenance Position

3. Performing Electrostatic Discharge Prevention Measures

4. Disconnecting Power From Server

5. Remove the Top Cover

6. Disengage both power supplies from the power distribution board

7. Remove the HDDs (please note current positions!), Optical drive, & then the Mass storage assembly

8. Disconnect all cables from PDB

9. Remove two screws that secure PDB to bus bar

10. Remove the 5 screws that secures the PDB to the chassis

11. Lift the PDB from the chassis

12. Place PDB on an antistatic mat

13. Loosely fit new PDB over 5 standoffs on chassis
      Note: Confirm the jumper on the power distribution board J7 is installed between pins 2 and 3. ( here )

14. Secure PDB to chassis with 5 mounting screw

15. Secure PDB to bus bar with 2 screws, and tighten all 7 screws.  The bus bar screws MUST be tightened securely to ensure good electrical connection.

16. Connect cables to PDB

17. Install thye Mass Storage Assy, hard drives in previous positions, & opticle drive

18. Re-engage power supplies with PDB connectors

19. Install the top front cover on chassis

20. Note chassis serial number (CSN), located on a sticker behind front bezel on the lower portion of the chassis. CSN is unique to each server and needs to be set after PDB replacement.


OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE FE/CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

Boot and test functionality of system, verify no service LEDs or error messages:
1. Run the Solaris "fmadm faulty" and SP/ILOM "show faulty" command (run "showfaults -v" command if only ALOM is supported ) 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, then the component has been replaced successfully. No further action is required

NOTE: After replacing the PDB and powering on the system, you must run the ALOM setcsn command to set the electronically readable chassis serial number (CSN) as shown below. CSN is used to obtain support from Sun.
1. Gain access to the ALOM sc> prompt

2. Perform the following commands to set the electronic chassis serial number on the new PDB:

sc> setsc sc_servicemode true
  Warning: misuse of this mode may invalidate your warranty.
sc> setcsn -cchassis_serial_number 

 Are you sure you want to permanently set the Chassis Serial Number to chassis_serial_number[y/n]? y
 Chassis serial number recorded.
sc> showplatform

  SUNW,Netra-T2000

  Chassis Serial Number: chassis-serial-number
sc>setsc sc_servicemode false

Caution - Once the PDB is programmed with an electronic chassis serial number, the serial number cannot be changed, so you need to execute above commands correctly.

Restart software applications per applicable administration guides to resume system operation

PARTS NOTE:  https://support.oracle.com/handbook_private/Systems/Netra_T2000/components.html#Power

REFERENCE INFORMATION:   http://docs.oracle.com/cd/E19596-01/index.html

This solution has no attachment