SPARC SuperCluster T4-4 Full Rack
 
Oracle SuperCluster T5-8 Full Rack
 
Big Data Appliance X3-2 In-Rack Expansion
 
Exadata X3-8 Hardware
 
Exadata X3-2 Quarter Rack
 
Exadata X3-2 Eighth Rack
 
Oracle SuperCluster T5-8 Half Rack
 
Exadata X3-2 Half Rack
 
Exadata X3-2 Full Rack
 
Big Data Appliance X3-2 Full Rack
 
Big Data Appliance X3-2 Hardware
 
Big Data Appliance X3-2 Starter Rack
 
Exadata X3-2 Hardware
 
SPARC SuperCluster T4-4 Half Rack
 
Sun Server X3-2L
 
Oracle SuperCluster T5-8 Hardware
 
SPARC SuperCluster T4-4
 

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

Applies to:

Goal

How to Replace a Sun Server X3-2L (Sun Fire X4270 M3) Memory DIMM.

Solution

Video - DIMM Replacement Overview (1:13)

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: A Sun Server X3-2L (Sun Fire X4270 M3) Memory DIMM needs replacement

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

If the system is still up and functioning, 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 ENGINEER NEED TO TAKE:

1. Prepare the server for service.

1. Power off the server and disconnect the power cords from the power supplies.
2. Extend the server to the maintenance position in the rack.
3. Attach an anti-static wrist strap.
4. Remove the top cover.
5. Remove the air baffle.

2. Identify and replace the DIMM, confirm population rules (for complete DIMM population rules reference the Service Manual).

1. Do not populate any DIMM sockets next to an empty processor socket. Each processor contains a separate memory controller.
2. For best performance DIMMs should be evenly distributed between the installed processors (if both are installed)
3. For each processor DIMMs should populate the slots in the following order:  D0 D2 D5 D7 D1 D3 D4 D6  (blue sockets first, then white sockets)
4. If a mix of DIMM sizes (for example, 8 GB, 16 GB, 32 GB) is being installed, then install all of the largest DIMMs first, followed next by all of the next largest, and so on until all DIMMs are installed.
5. To confirm and/or identify the location of the failed DIMM press the Fault Remind button on the motherboard. This will light the amber fault LED for the failed DIMM.
6. To remove the DIMM rotate both DIMM socket ejectors outward as far as they will go.
7. Carefully lift the DIMM straight up to remove it from the socket and set it aside on an antistatic mat.
8. Unpack the replacement DDR3 DIMM and place it on an antistatic mat.
9. Ensure that the replacement DDR3 DIMM matches the size it is replacing.
10. Install the DIMM into the motherboard by ensuring that the ejector tabs of the DIMM slots are in the open position.
11. Then align the notch in the DIMM with the key in the connector.
12. Push the DDR3 DIMM into the connector until the ejector tabs lock the DIMM in place.

3.Return the Server to operation

1. Replace the air baffle.
2. Replace the top cover
3. Remove any anti-static measures that were used.
4. Return the server to it's normal operating position within the rack.
5. Re-install the AC power cords and any data cables that were removed.
6. Power on server.

4. Check the ILOM to ensure that the fault has been cleared automatically and if not clear it manually.

1. login to the ILOM CLI and launch a Fault Management Shell session 
   -> start /SP/faultmgmt/shell
   Are you sure you want to start /SP/faultmgmt/shell (y/n)? y
   
   faultmgmtsp>
    
2. use the "fmadm faulty -a" command to list out all active faulty components
   faultmgmtsp> fmadm faulty -a
    
3. If the DIMM that was just replaced is still listed as a fault then indicate that the DIMM has been replaced by using the command "fmadm replaced <fru|cru|uuid>" for example: 
   faultmgmtsp> fmadm replaced DIMM_0
    
4. confirm that the faults are cleared and then exit out of the fault management shell
   faultmgmtsp> fmadm faulty -a
   No faults found
   faultmgmtsp> exit
   ->

OBTAIN CUSTOMER ACCEPTANCE

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

Boot up system and verify full functionality

REFERENCE INFORMATION:
Sun Server X3-2L Documentation
http://docs.oracle.com/cd/E23393_01/index.html

Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation
http://docs.oracle.com/cd/E24707_01/html/E24528/index.html

Steps to shut down or reboot an Exadata storage cell without affecting ASM (Doc ID 1188080.1)

Steps to Gracefully Shutdown and Power on a Single Node on Oracle Big Data Appliance Prior to Maintenance (Doc ID 2099858.1)

This solution has no attachment