HP Integrity rx2800 i4 User Manual page 76

FRU IDs:
--------
Log Entry 3: 02 Aug 2012 11:28:16
Alert Level 2: Informational
Keyword: BOOT_START
CPU starting boot
Logged by: System Firmware
Data: Major change in system state - Boot Start
5480006309E10005 0000000000000000
8. Go to SL system event and check if there is Memory IPMI event. If you see the event text
messages such as the ones shown below, it means that the system cannot find the DIMMs.
Check your memory riser expansion and DIMMs, or replace your memory riser expansion
and DIMMs.
FRU IDs:
--------
Log Entry 1: 01 Aug 2012 17:20:38
Alert Level 5: Critical
Keyword: INSUFFICIENT_SYSTEM_MEMORY
This HW configuration does not have enough memory for the OS to boot.
Logged by: integrated Lights Out
Data: Data field unused
A080274200E10001 0000000000000000
Log Entry 11: 02 Aug 2012 11:28:38
Alert Level 7: Fatal
Keyword: MEM_NO_MEM_FOUND
No memory found
Logged by: System Firmware
Data: Location - Blade (Blade Board)
E48000D109E10010 FFFFFFFFFFFFFF94
9. If you still see the above alert level 5 and 7 messages after CPU, memory expansion and
DIMMs change, then you must replace the system board. With a good CPU, memory expansion
and DIMMs, your system will boot to UEFI and will display the following event text messages
NOTE:
FRU IDs
-------
Log Entry 11: 03 Aug 2012 11:04:58
Alert Level 2: Informational
Keyword: EFI_START
CPU starting to boot EFI
Logged by: System Firmware
Data: Major change in system state - State Change
5480020709E1000F 000000000011000C
Log Entry 12: 03 Aug 2012 11:05:20
Alert Level 2: Informational
Keyword: EFI_LAUNCH_BOOT_MANAGER
Launching EFI boot manager
Logged by: System Firmware
Data: Major change in system state - EFI
5480020B09E10011 0000000000000006
If the installed CRUs are all functional, then the system initiates POST on all processors. HP
recommends that you observe the system console output through Live Logs to ensure that POST
is initiated and completes without error.
If POST does not start after a few seconds then suspect some sort of system board or processor
issue. Typical issues appear in the SEL or FPL. If the IPMI event logs do not point to a root
cause, then seek assistance.
76 Troubleshooting
Your display might not exactly match the display shown.
located in socket 0,cpu 2,thread 0
located in socket 0,cpu 2,thread 0
located in socket 0,cpu 2,thread 0
located in socket 0,cpu 2,thread 0
HP Confidential