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-1984206.1
Update Date:2018-04-10
Keywords:

Solution Type  Technical Instruction Sure

Solution  1984206.1 :   How to Replace an Exadata X5-2/X6-2 Memory DIMM Module  


Related Items
  • Oracle SuperCluster T5-8 Full Rack
  •  
  • Oracle SuperCluster M7 Hardware
  •  
  • Zero Data Loss Recovery Appliance X6 Hardware
  •  
  • Exadata SL6 Hardware
  •  
  • Exadata X5-2 Eighth Rack
  •  
  • Exadata X5-2 Hardware
  •  
  • Exadata X5-2 Full Rack
  •  
  • Oracle SuperCluster T5-8 Half Rack
  •  
  • Exadata X6-2 Hardware
  •  
  • Exadata X6-8 Hardware
  •  
  • Exadata X5-2 Quarter Rack
  •  
  • Exadata X4-8 Hardware
  •  
  • Exadata X5-2 Half Rack
  •  
  • Zero Data Loss Recovery Appliance X5 Hardware
  •  
  • Oracle SuperCluster T5-8 Hardware
  •  
  • Oracle SuperCluster M6-32 Hardware
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
  •  




In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: FRU for engineered system

Applies to:

Exadata X5-2 Quarter Rack - Version All Versions and later
Exadata X5-2 Eighth Rack - Version All Versions and later
Exadata X5-2 Hardware - Version All Versions and later
Exadata X5-2 Full Rack - Version All Versions and later
Exadata X5-2 Half Rack - Version All Versions and later
Information in this document applies to any platform.

Goal

 How to Replace a Exadata  X5-2/X6-2 Memory DIMM Module

Solution

 CAP PROBLEM OVERVIEW:Memory DIMM Replacement

DISPATCH INSTRUCTIONS

WHAT SKILLS DOES THE ENGINEER NEED:
Exadata trained.

TIME ESTIMATE: 30 minutes
TASK COMPLEXITY: 3


FIELD ENGINEER INSTRUCTIONS

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.

Refer to Doc: How to shutdown and startup Exadata X5 compute node and storage cells when performing hardware
maintenance (Doc ID 1982342.1)

For Extended information on this section, check MOS Note 1093890.1 Steps To Shutdown/Startup The Exadata & RDBMS
Services and Cell/Compute Nodes On An Exadata Configuration. (https://support.oracle.com/epmos/faces/ui/km
/SearchDocDisplay.jspx?id=1093890.1&type=DOCUMENT )

For a documentation reference, in the Exadata Owner’s Guide (E13874), use the section of chapter 7 titled “Non-Emergency Power
Procedures” section “Powering Off Oracle Exadata Rack” sub-section “Powering off Database Servers” available on the customer's
cell server image in the /opt/oracle/cell/doc.

http://amomv0115.us.oracle.com/archive/cd_ns/E13877_01/doc/doc.112/e13874/maintenance.htm#autoId18
A data backup is not a prerequisite but is a wise precaution.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:


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

B. Identify and replace the DIMM, confirm population rules

for complete DIMM population rules reference the Service Manual

X5-2 Service manual : http://docs.oracle.com/cd/E41059_01/html/E48312/napsm.z40003f01425075.html#scrolltoc

X5-2L Service manual : http://docs.oracle.com/cd/E41033_01/html/E48325/cnpsm.ceicjagi.html#scrolltoc

1. Do not populate any DIMM sockets next to an empty processor socket. Each processor contains a separate memory controller.

2. The server supports 32-GB quad-rank (QR) Load-Reduced DIMMs (LRDIMMs) and 8-GB single-rank (SR) and 16-GB dual-rank
(DR) Registered DIMMs (RDIMMs).

3. Do not mix 32-GB LRDIMMs and 8-GB or 16-GB RDIMMs in the same server. If the server has 32-GB LRDIMMs installed, you
cannot install 8-GB or 16-GB RDIMMs and vice versa.

4. Within a memory channel, DIMMs must be populated in the black sockets first, then in the black sockets with white tabs, and
then in the white sockets.

Black Sockets D0/D11/D3/D8

Black Sockets with white tab : D1/D10/D4/D7

White Sockets : D2/D9/D5/D6

5. If you are installing a mix of RDIMM sizes (for example, 8-GB and 16-GB), install the larger size RDIMMs first, then the smaller
RDIMMs, until all of the RDIMMs are installed.

6. There are no restrictions on the minimum number of DIMM sockets that must be populated.

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

8. To remove the DIMM rotate both DIMM socket ejectors outward as far as they will go.

9. Carefully lift the DIMM straight up to remove it from the socket and set it aside on an antistatic mat.

10. Unpack the replacement DDR4 DIMM and place it on an antistatic mat.

11. Ensure that the replacement DDR4 DIMM matches the size it is replacing.

12. Install the DIMM into the motherboard by ensuring that the ejector tabs of the DIMM slots are in the open position.

13. Then align the notch in the DIMM with the key in the connector.

14. Push the DDR4 DIMM into the connector until the ejector tabs lock the DIMM in place.

C. Return the Server to operation

1. Replace the top cover

2. Remove any anti-static measures that were used.

3. Return the server to it's normal operating position within the rack.

4. Re-install the AC power cords and any data cables that were removed.

NOTE:Do not power on the host at this point ,complete the next step first.

 

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

3. faultmgmtsp> fmadm faulty -a

4. 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 /SYS/MB/P0/D2

5. confirm that the faults are cleared and then exit out of the fault management shell

faultmgmtsp> fmadm faulty -a
No faults found
faultmgmtsp> exit
->

6.Once all faults are clear Power on the host.

Check all memory is detected by the ILOM

-> show /System/Memory/

 


OBTAIN CUSTOMER ACCEPTANCE

 

Once the host has completed booting login to the host and check the operating system has detected the memory.

Issue the following command to ensure all memory is detected

# grep MemTotal /proc/meminfo


WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Boot up system and verify full functionality

Refer to doc How to shutdown and startup Exadata X5 compute node and storage cells when performing hardware
maintenance (Doc ID 1982342.1)

REFERENCE INFORMATION:


How to shutdown and startup Exadata X5 compute node and storage cells when performing hardware
maintenance (Doc ID 1982342.1)

Oracle Server X5-2 service guide: http://docs.oracle.com/cd/E41059_01/html/E48312/napsm.gntoq.html#scrolltoc
Oracle server X5-2L service guide : http://docs.oracle.com/cd/E41033_01/html/E48325/cnpsm.ceicjagi.html#scrolltoc


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