![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 2162087.1 : How to Replace an Exadata X4-8, X5-8, X6-8 Compute Node Memory DIMM
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:Exadata X5-8 Hardware - Version All Versions to All Versions [Release All Releases]Exadata X4-8 Hardware - Version All Versions to All Versions [Release All Releases] Exadata X6-8 Hardware - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. GoalHow to Replace an Exadata X4-8, X5-8, X6-8 Compute Node Memory DIMM. SolutionDISPATCH INSTRUCTIONS PROBLEM OVERVIEW: An Exadata X4-8/X5-8/X6-8 Compute Node Memory DIMM needs replacement WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? : WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE?: Oracle Server X5-8 Service Manual Memory Installation Notes 1. Populate the slots with black slots and black levers first: D0, D3, D6, D9, D12, D15, D18, D21. The slot population for the minimum DIMM configuration is D0/D6/D12/D18 per CMOD 2. Populate the slots with black slots and white levers second: D1, D4, D7, D10, D13, D16, D19, D22. 3. Populate the white slot, white lever slots last: D2, D5, D8, D11, D14, D17, D20, D23
3. Remove the fan frame. 4. Remove the CMOD from the server. 8. Install the 4x fan modules. 9. After removing a CMOD the DPCCs associated with the CMOD removed/reinserted must also be reseated to ensure they have not become slightly unseated. OBTAIN CUSTOMER ACCEPTANCE Prepare server for operation, power on server and start OS. Please follow start up instructions in DOC ID: 1982342.1 How to verify the DIMM is working properly -> show /System/Memory/DIMMs/DIMM_x
note: the "x" represents the DIMM number of the DIMM replaced
-> show /System/Memory/DIMMs/DIMM_0
/System/Memory/DIMMs/DIMM_0 Targets: Properties: health = OK health_details = - part_number = 001-0003-01,M393B2G70DB0-YK0 serial_number = 00CE011412225F9C48 location = P0/D0 (CPU 0 DIMM 0) manufacturer = Samsung memory_size = 16 GB Use the fault management shell to clear the fault for a specific component: or you can use the UUID faultmgmtsp> fmadm acquit UUID
-> show /SP/logs/event/list
faultmgmtsp> fmadm faulty No faults found
# fmadm faulty -a
STATE RESOURCE / UUID -------- ----------------------------------------------------------------------
# prtdiag -v
System Configuration: Sun Server X4-8 BIOS Configuration: American Megatrends Inc. 29011300 08/26/2010 BMC Configuration: IPMI 2.0 (KCS: Keyboard Controller Style) ==== Processor Sockets ==================================== Version Location Tag -------------------------------- -------------------------- Intel(R) Xeon(R) CPU E7-8895 v2 @ 2.80GHz CPU 1 Intel(R) Xeon(R) CPU E7-8895 v2 @ 2.80GHz CPU 2 Intel(R) Xeon(R) CPU E7-8895 v2 @ 2.80GHz CPU 3 Intel(R) Xeon(R) CPU E7-8895 v2 @ 2.80GHz 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 . .
bash-3.00# pwd
/var/adm # grep -i warning messages # grep -i error messages # grep -i fail messages
PARTS NOTE: REFERENCE INFORMATION: Sun Server X4-8 Service Manual Oracle Server X5-8 Service Manual How to Shutdown and Startup Exadata X5 compute nodes and storage cells when performing hardware maintenance (includes Supercluster X5 storage cells) (Doc ID 1982342.1) References<NOTE:1381773.1> - How to clear FMA logs on the ILOM or Solaris on x86 platformsAttachments This solution has no attachment |
||||||||||||||||
|