Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

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

Solution Type  Technical Instruction Sure

Solution  2153153.1 :   How to Replace a SPARC S7-2 L Power Supply [VCAP]  


Related Items
  • SPARC S7-2L
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: SPARC-CAP VCAP
  •  
  • Microlearning>Video>ML-VID-VCAP
  •  




In this Document
Goal
Solution
References


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

 

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

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.

Solution



DISPATCH INSTRUCTIONS

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


TIME ESTIMATE: 30 minutes

TASK COMPLEXITY: 0

REMOVAL/REPLACEMENT INSTRUCTIONS:


PROBLEM OVERVIEW: SPARC S7-2L Power Supply 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 - This is a hot service procedure that can be performed by Customers while the server is running. 
Note - The server's redundant power supplies support concurrent maintenance, which enables you to remove and replace a power supply without shutting down the server, provided that the other power supply is online and working.
Note - If a power supply fails and you do not have a replacement available, leave the failed power supply installed to ensure proper airflow in the server.

WHAT ACTIONS ARE REQUIRED?:

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).
     e. After the fruid data in the Backup1 and Backup2 containers have been confirmed to match proceed with the following steps.

Confirm the Power Supply failure and it's location

1. Confirm which Power Supply is to be replaced. When looking at the server from the rear PS0 is to the left and PS1 is to the right.

2. If the specific power supply to be replaced is not yet known check the status LEDs to identify the failed Power Supply. A failed PSU should have it's amber "service required" LED lit. A working PSU will only have it's green "AC OK" LED lit.

3. If the service is to be performed while the system is up and running confirm that the second PSU is online and working properly.

4. If a replacement Power Supply is not yet available leave the failed supply in place to provide proper airflow within the system until the replacement is available. You may notice that the failed Power Supply's fans are still turning. This is ok and the power supply may be removed while the fans are still spinning.

Remove Power Supply

1. Gain access to the rear of the server where the faulty power supply is located.

2. If the cable management arm (CMA) is installed, disconnect both CMA left-side connectors and move the CMA out of the way.

Caution - When disconnecting the CMA left-side connectors, use your arm to support the CMA so that it does not hang down under it's own weight and stress the right-sdie connectors; otherwise, the CMA might be damaged.  You must continue to support the CMA until you have reconnected both of the left-side connectors.

3. Disconnect the power cord from the failed power supply.

4. Grasp the power supply handle and push the power supply latch to the left.

5. Pull the power supply out of the chassis and set it aside on an antistatic mat.

Caution - Whenever you remove a power supply, you should immediately replace it with another power supply; otherwise, the server might overheat due to improper airflow.
Caution - If you will not be replacing the power supply immediately, install a power supply filler panel before returning power to the server.

6. Remove the replacement power supply from its packaging and place it on an antistatic mat.

7. Align the power supply with the empty power supply slot.

8. Slide the power supply into the bay until it is fully seated. (an audible click will be heard when it is fully seated)

9. Reconnect the power cord to the power supply.

10. Verify that the amber LED on the replaced power supply and the Service Required LEDs on the front and rear of the chassis are not lit.

11. Return the Server to operation

     a. If you pulled the server out of the rack to make it easier to remove the power supply, push the server into the rack until the slide-rail locks (on the front of the server) engage the slide-rail assemblies.
     b. If a cable management arm is installed and was removed to access the power supply reattach the two CMA connectors.
     c. Check all power and data cables to ensure that no connections were disturbed during the service.
     d. Verify that the Power/OK indicator led lights steady on and that system is operating properly.

Verify/Update TLI After Replacement

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

     a. PS0 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:
       

     -> 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: fruid:///SYS/PS0
     Backup 2: fruid:///SYS/MB

     Element           | Primary             |  Backup1            |    Backup2
     ------------------+-------------------+-------------------+-------------------
     PPN                  34235727+1+1      34235727+1+1        34235727+1+1
     PSN                  AK00370269          0000000000            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 PS0 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.

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

     [(escalation mode) s7-2l-bur09-a-sp:~]# showpsnc
     Primary: fruid:///SYS/DBP
     Backup 1: fruid:///SYS/PS0
     Backup 2: fruid:///SYS/MB

     Element            | Primary            |    Backup1            |   Backup2
     ------------------+-------------------+-------------------+-------------------
     PPN                   34235727+1+1       34235727+1+1        34235727+1+1
     PSN                   AK00370269           0000000000            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 Primary Backup1

     [(escalation mode) s7-2l-bur09-a-sp:~]# showpsnc
     Primary: fruid:///SYS/DBP
     Backup 1: fruid:///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 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.

        -> 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: fruid:///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 Power Supply is working properly

1. Log into ILOM to confirm if power supply status is working properly.

Example:

-> show /SYS/PS0

/SYS/PS0
Targets:
ERR
F0
FAN_ERR
INPUT_POWER
I_+12V
I_+12V_STBY
I_IN
I_OUT_ERR
I_OUT_STBY_ERR
MICRO
OUTPUT_POWER
T_AMB
T_ERR
V_+12V
V_+12V_STBY
V_IN
V_IN_ERR
V_OUT_ERR
V_OUT_OK
V_OUT_STBY_ERR

Properties:
type = Power Supply
ipmi_name = PS0
fru_description = A266_Power_Supply
fru_manufacturer = DELTA ELECTRONICS (THAILAND)
fru_part_number = 7311825
fru_rev_level = 01
fru_serial_number = 465824T+1602D30076
fault_state = OK
clear_fault_action = (none)

Commands:
cd
set
show

->

2.  Check ILOM event log to see if any error related power.

-> show /SP/faultmgmt
-> show /SP/logs/event/list


OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTIONS ARE REQUIRED TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?:
N/A

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

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

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback