Asset ID: |
1-71-2005943.1 |
Update Date: | 2018-01-11 |
Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2005943.1
:
How to replace a PCA X5-2, X6-2,X7-2 server DIMM memory module
Related Items |
- Private Cloud Appliance X6-2 Server Upgrade
- Private Cloud Appliance X7-2 Server Upgrade
- Private Cloud Appliance X5-2 Hardware
- Private Cloud Appliance
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: x64-CAP VCAP
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Part is a FRU
Applies to:
Private Cloud Appliance X5-2 Hardware - Version All Versions and later
Private Cloud Appliance - Version 2.0.2 and later
Private Cloud Appliance X6-2 Server Upgrade - Version All Versions and later
Private Cloud Appliance X7-2 Server Upgrade - Version All Versions and later
Information in this document applies to any platform.
Goal
Replace a DIMM module in a PCA X5-2, X6-2, X7-2 server
Solution
CAP PROBLEM OVERVIEW:Memory DIMM Replacement
DISPATCH INSTRUCTIONS
WHAT SKILLS DOES THE ENGINEER NEED:
Oracel Server X5-2, X6-2 Training
TIME ESTIMATE: 45 minutes
TASK COMPLEXITY: 2
FIELD ENGINEER INSTRUCTIONS
WHAT ACTION DOES THE ENGINEER NEED TO TAKE:
Pre-DIMM FRU replacement
1. The server should be shutdown for service by the customer. If needed the customer facing doc is
Steps to Gracefully Shutdown and Power Off a Node in Oracle Private Cloud Appliance Prior to Maintenance (Doc ID 2256834.1)
Prepare the server for service.
Caution -
Ensure that all power is removed from the server before removing or installing DDR4
DIMMs, or damage to the DDR4 DIMMs might occur. You must disconnect all power cables
from the system before performing these procedures.
2. Extend the server to the maintenance position. Attach an antistatic wrist strap to your wrist and then to a metal area on the chassis. Remove the server top cover
3. Identify and note the location of the failed DDR4 DIMM by pressing the Fault Remind button on the motherboard
To remove the failed DIMM do the following:
a.Rotate both DIMM socket ejectors outward as far as they will go
The DIMM is partially ejected from the socket.
b. arefully lift the DIMM straight up to remove it from the socket.
4. Replace each failed DIMM with either another DIMM of the same rank size (quad
rank, dual rank, or single rank) or leave the socket empty.
Install a DIMM
5. Unpack the replacement DDR4 DIMM and place it on an antistatic mat.
6. Ensure that the replacement DDR4 DIMM matches the size of the DIMM it is
replacing
You must not replace a single-rank or dual-rank DIMM with a quad-rank DIMM and vice versa.
If you violate this rule, the performance of the server might be adversely affected
7.Install a DIMM.
a.Ensure that the ejector tabs are in the open position.
b.Align the notch in the replacement DIMM with the connector key in the
connector socket.
The notch ensures that the DIMM is oriented correctly.
c.Push the DDR4 DIMM into the connector until the ejector tabs lock the DIMM in place.
If the DIMM does not easily seat into the connector socket, verify that the notch in the
DIMM is aligned with the connector key in the connector socket. If the notch is not
aligned, damage to the DIMM might occur.
Note -
If you want to move a faulty DDR4 DIMM to a new DIMM socket or re-seat a DIMM for troubleshooting, you must first manually clear the associated DIMM fault. Otherwise, the DIMM fault might follow the DIMM to the new socket location or reoccur on the current socket location, possibly causing a false DIMM fault condition
8. Check the ILOM to ensure that the fault has been cleared automatically and if not clear it manually.
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>
use the "fmadm faulty -a" command to list out all active faulty components
faultmgmtsp> fmadm faulty -a
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
confirm that the faults are cleared and then exit out of the fault management shell
faultmgmtsp> fmadm faulty -a
No faults found
faultmgmtsp> exit
9. Return the server to operation.
OBTAIN CUSTOMER ACCEPTANCE
WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
10. Customer returns the node to service per (Doc ID 2256834.1)
Attachments
This solution has no attachment