Mx-32 - How to Replace a Faulty CPU Memory Unit (CMU)

Asset ID:	1-71-1529502.1
Update Date:	2017-12-11
Keywords:

Solution Type Technical Instruction Sure

Solution 1529502.1 : Mx-32 - How to Replace a Faulty CPU Memory Unit (CMU)

Applies to:

SPARC M6-32 - Version All Versions and later
Oracle SuperCluster M6-32 Hardware - Version All Versions and later
SPARC M5-32 - Version All Versions and later
Information in this document applies to any platform.

Goal

CAP PROBLEM OVERVIEW: Mx-32 How to Replace a Faulty CPU Memory Unit (CMU)

*************************************************************
To report errors or request improvements on this procedure,
please go to My Oracle Support, and put a comment on Doc ID: 1529502.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.

Replacement Cautions:

The CMU is heavy. A fully-loaded CMU weighs 56 lbs, 25.5 kg.
Do not remove more than one CMU at a time. Fill the empty slot as soon as possible to avoid overheating the server, but heed the caution on the next line.
CMUs should not be swapped too fast. ILOM must have adequate time to respond to inventory changes when a CMU is inserted or removed. See detailed instructions below.

Solution

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED: Mx-32 Product Training/Experience

TASK COMPLEXITY: 3

TIME ESTIMATE: 120 minutes

FIELD ENGINEER INSTRUCTIONS

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

For a HOT replacement the customer is required to perform a domain(s) shutdown

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

1. Use one of these ILOM commands to display faulty components:

-> show faulty

-> show /System/Open_Problems

2. Stop the PDomain that contains the CMU:

a. Determine which DCU has the CMU.

-> show /System/DCUs
/System/DCUs/DCU_x

where x can be 0 through 3.
DCU0 contains CMU0 through CMU3. DCU1 contains CMU4 through CMU7. DCU2 contains CMU8 through CMU11. DCU3 contains CMU12 through CMU15.

b. Determine which PDomain has DCU_x.

-> show /System/DCUs/DCU_x host_assigned
/System/DCUs/DCUx
Properties:
host_assigned = HOST

c. Stop the specified PDomain:

-> stop /Servers/PDomains/PDomain_y/HOST

3. Wait till HOST status is "Powered Off"

-> show /Servers/PDomains/PDomain_y/HOST status

/Servers/PDomains/PDomain_y/HOST
Properties:
status = Powered Off

4. Turn on the Ready to Remove LED on the faulty CMU (/SYS/CMUx):
-> set /SYS/CMUx prepare_to_remove_action=true

To verify that the CMU is properly prepared for removal check that the prepare_to_remove_status is Ready:

-> show /SYS/CMUx prepare_to_remove_status
prepare_to_remove_status = Ready

5. Remove the CMU.

6. Place the faulty CMU on a static-safe mat.

7. Transfer DIMM components to the replacement CMU.

8. Reinstall the CMU

Caution - CMUs should not be swapped too fast. ILOM must have adequate time to respond to inventory changes before a CMU can be inserted. Check the ILOM property "-> show /System/Memory installed_dimms" to determine if ILOM inventory is completed. The displayed property value should be equal to the number of DIMMS physically residing within the system upon inventory update. Inventory changes can take 5-7minutes or more depending on the SP activity.

9. Restart the PDomain.

10. Return the faulted component to Oracle.

Caution - The removed CMU must be properly repackaged to prevent damage during return transportation to Oracle. The CMU should be repackaged in identical fashion as the dispatched FRU. See the Service Manual for details about proper repackaging.

OBTAIN CUSTOMER ACCEPTANCE

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

Restart software applications per applicable administration guides to resume system operation.

======================== Other info =====================

REFERENCE INFORMATION: Service Manual: https://www.oracle.com/technetwork/documentation/oracle-sparc-ent-servers-189996.html

Attachments

This solution has no attachment