Oracle Server X6-2L
 
Oracle SuperCluster T5-8 Full Rack
 
Big Data Appliance X5-2 Starter Rack
 
Oracle SuperCluster M7 Hardware
 
Big Data Appliance X5-2 Full Rack
 
Zero Data Loss Recovery Appliance X6 Hardware
 
Exadata X6-8 Hardware
 
Exadata X5-2 Hardware
 
Exadata X5-2 Full Rack
 
Exadata X5-2 Eighth Rack
 
Oracle SuperCluster T5-8 Half Rack
 
Exadata X6-2 Hardware
 
Exadata X5-2 Quarter Rack
 
Big Data Appliance X5-2 Hardware
 
Zero Data Loss Recovery Appliance X5 Hardware
 
Exadata X5-2 Half Rack
 
Big Data Appliance X5-2 In-Rack Expansion
 
Big Data Appliance X6-2 Hardware
 
Oracle Server X5-2L
 
Oracle SuperCluster M6-32 Hardware
 
Oracle SuperCluster T5-8 Hardware
 

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

Applies to:

Goal

How to Replace an Oracle Server X5-2L, X6-2L Power Supply.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
No special skills required, Customer Replaceable Unit (CRU) procedure

TIME ESTIMATE: 30 minutes

TASK COMPLEXITY: 0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: An Oracle Server X5-2L, X6-2L Power Supply needs replacement

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

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.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

X5-2L Rear Panel Components and Cable Connections:
http://docs.oracle.com/cd/E41033_01/html/E48325/cnpsm.z40003ec1405871.html#scrolltoc

X6-2L Rear Panel Components and Cable Connections:
http://docs.oracle.com/cd/E62172_01/html/E62184/z40003ec1405871.html#scrolltoc

A. Log into the ILOM check the fruid container values and sync them if needed.

1. To avoid mismatched fruid values causing a failure after a power supply replacement the fruid data should be confirmed to have matching data in at least the Primary (DBP) and Backup1 (MB) containers so that the power supply will have it's container updated automatically after replacement. Go into restricted mode and use the showpsnc command to check this.  
2. -> set SESSION mode=restricted
   
   WARNING: The "Restricted Shell" account is provided solely
   to allow Services to perform diagnostic tasks.
   
   [(restricted_shell) X5-2L]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup1
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup2 (7)        | Backup2 (8)
   ------------------+-------------------+-------------------
   PPN                 33154888+1+1        33154888+1+1
   PSN                 1449NM7002          1449NM7002
   Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
   [(restricted_shell) X5-2L]# exit
   
    
3. 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
    
4. After an ILOM reset if the Primary and Backup1 containers match then proceed with the following steps to replace the power supply. If these two containers do not match then DO NOT proceed with the replacement yet.  Contact TSC for further assistance.

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

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

C. Remove the Power Supply

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

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

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

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

   If both power supplies will be removed for any reason label each power supply with the slot number from which it was removed (PS0, PS1) so that any supply that is not replaced with a new part can be re-installed to the same slot from which it was removed so that FRU TLI data is not lost.

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

6. 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 replace it with another power supply; otherwise, the server might overheat due to improper airflow.

D. Install the replacement Power Supply

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

2. Align the power supply with the empty power supply bay.

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

4. Reconnect the power cord to the power supply.

5. Verify that the amber LED on the replaced power supply and the Service Required LEDs on the chassis are not lit.

E. Return the Server to operation

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

2. If a cable management arm is installed and was removed to access the power supply reattach the two CMA left-side connectors.

3. Check all power and data cables to ensure that no connections were disturbed during the service.

4. Verify that the Power/OK indicator led lights steady on and that system is operating properly.

F. Check and set the system serial number/fruid data if needed. 

1. login to the ILOM as root and then enter the restricted shell to check the psnc 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) X5-2L]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup1
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup2 (7)        | Backup2 (8)
   ------------------+-------------------+-------------------
   PPN                 33154888+1+1        33154888+1+1
   PSN                 0000000000          1449NM7002
   Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
   [(restricted_shell) X5-2L]# exit
   

3. The above example shows a system with the Backup2 container not in sync after PSU replacement. 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.  Power Supply 1 does not contain fruid data, and therefore does not require an SP reset after replacement.
   -> reset /SP
   Are you sure you want to reset /SP (y/n)? y
   Performing reset on /SP
4. If after the ILOM reset the containers still don't match then contact the TSC for further assistance. (if all three entries match this step is done).

1. If the containers don't match you must enter escalation or service mode to fix it.
   
2. 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).
3. 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.
4. 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 = *****
5. 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
6. Login using the escuser login and enter escalation mode using the password that was provided by the TSC.
   X5-2L login: escuser
   Password:
   
   Oracle(R) Integrated Lights Out Manager
   
   Version 3.2.4.36 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: X5-2L
   
   -> cd /SP/users/ecsuser/escalation
   -> set SESSION mode=escalation                            
   Password:**** **** **** **** **** *** *** **** **** **** **** **** **** **** **** **** *** *** **** *** **** **** **** *** **** **** *** **** *** *
   Short form password is:  NOSE HAAG MED
   
   [(escalation_mode) X5-2L:~]#
7. Use the showpsnc command to confirm the current container values. Confirm that one of the backup containers 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 DBP. The following example shows copying from backup1 to the primary but you could also copy from backup2 if needed.
   
   [(escalation_mode) X5-2L:~]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup1
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup2 (7)        | Backup2 (8)
   ------------------+-------------------+-------------------
   PPN                 33154888+1+1        33154888+1+1
   PSN                 0000000000          1449NM7002
   Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
   [(escalation_mode) X5-2L:~]# copypsnc Primary Backup2
   [(escalation_mode) X5-2L:~]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup1
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup2 (7)        | Backup2 (8)
   ------------------+-------------------+-------------------
   PPN                 33154888+1+1        33154888+1+1
   PSN                 1449NM7002          1449NM7002
   Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
   [(escalation_mode) X5-2L:~]# exit
   
   
8. 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" to copy Primary to 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) X5-2L]# showpsnc
   Primary: fruid:///SYS/DBP
   Backup 1: fruid:///SYS/MB
   Backup 2: fruid:///SYS/PS0
   
   Element           | Primary
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup1
   ------------------+-------------------
   PPN                 33154888+1+1
   PSN                 1449NM7002
   Product Name        ORACLE SERVER X5-2L
   
   Element           | Backup2 (7)        | Backup2 (8)
   ------------------+-------------------+-------------------
   PPN                 33154888+1+1        33154888+1+1
   PSN                 1449NM7002          1449NM7002
   Product Name        ORACLE SERVER X5-2L ORACLE SERVER X5-2L
   [(restricted_shell) X5-2L]# 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
9. 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.

Sample

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

OBTAIN CUSTOMER ACCEPTANCE

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

N/A

REFERENCE INFORMATION:
Oracle Server X5-2L Documentation:
http://docs.oracle.com/cd/E41033_01/index.html

Oracle Server X6-2L Documentation:
http://docs.oracle.com/cd/E62172_01/index.html

Oracle Server X5-2L Power Supply module replacement procedure:
http://docs.oracle.com/cd/E41033_01/html/E48325/cnpsm.z40000091014153.html#scrolltoc

Oracle Server X6-2L Power Supply module replacement procedure:
http://docs.oracle.com/cd/E62172_01/html/E62184/z40000091014153.html#scrolltoc

Oracle Integrated Lights Out Manager (ILOM) 3.2 Documentation
http://docs.oracle.com/cd/E37444_01/index.html

This solution has no attachment