How to Replace a Sun Fire X4800, Sun Server X2-8 (Sun Fire X4800 M2) Memory DIMM

Asset ID:	1-71-1390677.1
Update Date:	2018-05-16
Keywords:

Solution Type Technical Instruction Sure

Solution 1390677.1 : How to Replace a Sun Fire X4800, Sun Server X2-8 (Sun Fire X4800 M2) Memory DIMM

Applies to:

Sun Fire X4800 Server - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X2-8 - Version All Versions to All Versions [Release All Releases]
Exadata X3-8 Hardware - Version All Versions to All Versions [Release All Releases]
Sun Server X2-8 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

How to Replace a Sun Fire X4800, Sun Server X2-8 (Sun Fire X4800 M2) Memory DIMM.

Solution

Video - Removing a DIMM (1:14)

Video - Installing a DIMM (1:17)

DISPATCH INSTRUCTIONS

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

TIME ESTIMATE: 60 minutes

TASK COMPLEXITY: 0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:

PROBLEM OVERVIEW: A Sun Fire X4800, Sun Server X2-8 (Sun Fire X4800 M2) Memory DIMM needs replacement

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

System should be powered down.

Note: If this server is part of an Exadata, please follow shutdown instructions in Section 1 of DOC ID: 1539451.1

WHAT ACTIONS ARE REQUIRED:

Memory Installation Notes

1. Install the first DIMMs in Blue slots D0, D4, D8, and D12.
2. Install the second DIMMs in White slots D2, D6, D10, and D14.
3. Install the third DIMMs in Black slots D1, D5, D9, and D13.
4. Install the fourth DIMMs in Green slots D3, D7, D11, and D15.

DIMM slots must be populated in matching pairs of identical DIMMs (from the same memory kit) within a processor:
Note: all DIMMs should have same P/N in a pair.
D0/D4
D1/D5
D2/D6
D3/D7
D8/D12
D9/D13
D10/D14
D11/D15

How to Remove a DIMM

1. Prepare the server for service, shutdown OS and power off server.

2. Remove the CMOD from the server.

3. Set the module on a flat antistatic surface with ample surrounding space and light.

4. Remove the CMOD cover.

5. Press the "DIMM FAULT REMIND BUTTON". This should turn on the slot LED for the faulty DIMM.

6. To unlock the DIMM, simultaneously rotate the two release levers outward fully away from the DIMM.
This action unlocks and ejects the DIMM from the DIMM slot.

7. Remove the DIMM from the server.

How to Install a DIMM

1. Ensure that the DIMM slot locking levers are in the fully open position.

2. Align the DIMM within the slot.
The DIMM is notched to accommodate the key (protrusion) in the slot. The key ensures correct DIMM installation. The DIMM can only be correctly installed one way.

3. To install the DIMM, simultaneously press down on both ends of the DIMM to push the it into the slot.
This action causes the DIMM locking levers to lift and lock into place on the DIMM.

4. Verify that the DIMM is properly installed and locked.
When properly locked in place, the DIMM cannot be removed.

5. Install the CMOD cover.

6. Install the CMOD into the server.

7. Make sure to clear the DIMM fault in ILOM before powering on the system otherwise BIOS will disable the new DIMM on power up due to the previous fault data.

8. Prepare server for operation, power on server and start OS.

How to verify the DIMM is working properly

Log in to the ILOM CLI.

Enter the following command to check status in normal status:

-> show /SYS/BLx/Px/Dx
note: the "x" represents which BLade/CPU/DIMM number of the DIMM replaced

Example:

-> show /SYS/BL0/P0/D0

/SYS/BL0/P0/D0
Properties:
type = DIMM
ipmi_name = BL0/P0/D0
fru_name = 2GB DDR3 SDRAM 666
fru_manufacturer = SAMSUNG
fru_part_number = M393B5673FH0-CH9
fru_serial_number = 0603D116
fault_state = OK
clear_fault_action = (none)

/SYS/BL0/P0/D0/SERVICE
Properties:
type = Indicator
ipmi_name = BL0/P0/D0/SVC
value = Off

Use the following command to clear the fault for a specific component:

For example:

-> set /SYS/BL0/P0/D0 clear_fault_action=true

Check if any error output from event log

Example

-> show /SP/logs/event/list

Check if any fault parts existed

-> show /SP/faultmgmt

Example

-> cd /SP/faultmgmt
Properties:

-> show faulty
Target | Property | Value
-----------------+-----------------------+-------------------------------------

Check FMA and OS information to verify that no errors existed

Example

# fmadm faulty -a
STATE RESOURCE / UUID
-------- ----------------------------------------------------------------------

# prtdiag -v

System Configuration: SUN MICROSYSTEMS Sun Fire X4800
BIOS Configuration: American Megatrends Inc. 11014100 08/26/2010
BMC Configuration: IPMI 2.0 (KCS: Keyboard Controller Style)

==== Processor Sockets ====================================

Version Location Tag
-------------------------------- --------------------------
Intel(R) Xeon(R) CPU X7560 @ 2.27GHz CPU 1
Intel(R) Xeon(R) CPU X7560 @ 2.27GHz CPU 2
Intel(R) Xeon(R) CPU X7560 @ 2.27GHz CPU 3
Intel(R) Xeon(R) CPU X7560 @ 2.27GHz CPU 4

==== Memory Device Sockets ================================

Type Status Set Device Locator Bank Locator
------- ------ --- ------------------- --------------------
SDRAM in use 0 BL0/P0 DIMM0<------here
SGRAM empty 0 BL0/P0 DIMM1
SDRAM in use 0 BL0/P0 DIMM2
SGRAM empty 0 BL0/P0 DIMM3
SDRAM in use 0 BL0/P0 DIMM4
.
.

Check /var/adm/messages file to verify that no errors existed

Example

bash-3.00# pwd
/var/adm

# grep -i warning messages
# grep -i error messages
# grep -i fail messages

Note: If this server is part of an Exadata, please follow restart instructions in Section 1, step 10 of DOC ID: 1539451.1

REFERENCE INFORMATION:

Sun Fire X4800/ M2 Server Service Manual
http://docs.oracle.com/cd/E20815_01/html/E20819/index.html

3D Server Overview
http://oracle.com.edgesuite.net/producttours/3d/x2-8/index.html

DIMM Population Rules
http://docs.oracle.com/cd/E20815_01/html/E20840/sfmsm.gkacs.html#scrolltoc

How to shutdown the Exadata database nodes and storage cells in a rolling fashion so certain hardware tasks can be performed. (Doc ID 1539451.1)

References

<NOTE:1381773.1> - How to clear FMA logs on the ILOM or Solaris on x86 platforms

Attachments

This solution has no attachment