5. If you do not see all of the above CRU IDs then concentrate on the missing CRU IDs.
6. Remove the AC power cords. Add a processor in the CPU 0 socket and add a memory expansion
board with DIMMs populated in slots 4A and 3A. Plug in the AC power cords and check for the
processor, memory expansion board, and DIMM FRU IDs.
7. The following is an example of the MP DF command that appears with a processor, memory
expansion board, and two DIMMs installed.
NOTE:
Your display might not exactly match the display shown.
8.
FRU IDs:
--------
00-System Board 02-Display Board 05-Power Supply 1
0C-Memory Riser 1 20-Processor 0 24-Processor 0 RAM
42-Virtual Connect 82-DIMM CPU0-R1 3A 83-DIMM CPU0-R1 4A
9. If you do not see all of the above CRU IDs then concentrate on the missing CRU IDs.
10. Power on the server and check the SEL for any IPMI alerts related to the processor.
NOTE:
Your display might not exactly match the display shown.
Log Entry 4: 01 Aug 2012 17:22:00
Alert Level 7: Fatal
Keyword: BOOT_NOT_DETECTED
No events were received from system firmware
Logged by: integrated Lights Out
Sensor: Processor
Data1: FRB2/Hang in POST failure
20501965B8020006 FFFF036F00070400
11. If the above Level 7 IPMI alert appears, verify the installation of your processor and if necessary
replace the processor.
12. If the processor is installed and functioning properly, check the SEL for the following IPMI event after
powering on the server to verify that POST has started.
NOTE:
Your display might not exactly match the display shown.
Log Entry 3: 02 Aug 2012 11:28:16
Alert Level 2: Informational
Keyword: BOOT_START
CPU starting boot
Logged by: System Firmware located in socket 0,cpu 2,thread 0
Data: Major change in system state - Boot Start
5480006309E10005 0000000000000000
13. Check the SEL for any memory-related IPMI alerts.
Troubleshooting 109
To Next Page
Loading...
Need help?
General