Operations Guide, Fourth Edition - HP Integrity rx1620

Table A-1 EFI Error and Warning Messages (continued)
SolutionError/Warning MessageError
Number
Information only, no action requiredEFI NVM cleared49
Reboot the server. If the error message is
repeated, contact the HP Support center for
assistance.
EFI NVM failed50
Check processor installation. (Verify
installation.) Replace processor that was
deconfigured.
CPU deconfigured by SAL_B51
One or more firmware components (Firmware,
BMC, MP) is out of date
A ROM revision is inconsistent with FIT or
REVBLOCK
52
Contact the HP Support center for assistance.Error building SMBIOS53
Contact the HP Support center for assistance.Failure constructing the EFI Memory Data Table
(MDT)
54
Update with sysset command.Universal Unique IDentifier (UUID) error55
Reboot the server. If the error message is
repeated, replace the failing processor.
Error reading CPU SMBIOS information ROM56
Replace the FRU which was reported. If the error
message is repeated, contact the HP Support
center for assistance.
Error accessing Field Replaceable Unit (FRU)
information
57
Replace the FRU which was reported. If the error
message is repeated, contact the HP Support
center for assistance.
Checksum error accessing FRU information58
Replace the FRU which was reported. If the error
message is repeated, contact the HP Support
center for assistance.
FRU information version error59
SEL and FPL Log Entries
This section is a quick reference for the intelligent platform management interface (IPMI) events
recorded in the SEL and FPL files. These logs are available via the management processor (MP)
card interface or the BMC command line interface (CLI).
• All entries from the SEL are forwarded to the FPL. The FPL is a circular log so the newest
entries replace the oldest. The FPL contains forward progress messages from the BMC,
System firmware, EFI, and the OS.
• The SEL will not accept new entries once it is full and contains only those events considered
of major importance to system operation.
• Both contain type 02 and E0 messages.
• A triplet is formed from the SensorType, EventType, and the lower nibble of the Data1 fields
of Type 02 events. MP firmware displays the triplet in the Keyword field.
NOTE: Systems with firmware version 2.0 or higher also have a clearlogs command that
will clear out the log files should they become full.
Accessing the logs with BMC CLI commands
The cli>sl -fcommand displays the forward progress log. For example:
Rec# Sev Generator/Sensor Description Event ID Data, Timestamp
-------- - ---------------- ------------ ----------- --------------------------
00000000 - BMC Chass cntrl 00-12:70:A3 81:03 2003-10-31 22:41:29
EFI Error and Warning Messages 103