User Service Guide, Third Edition - HP Integrity cx2620 Server

Table 5-14 EFI Error and Warning Messages (continued)
Description/SolutionMessageError Number
Contact the HP Support Center for assistance.Error building S MBIOS53
Contact the HP Support Center for assistance.Failure constructing the EFI Memory Data Table
(MDT)
54
Update with the sysset command.
UUID error55
Reboot the server. If the error message is repeated,
replace the failing processor.
Error reading CPU S MBUS information ROM56
Replace the CRU that was reported. If the error
message is repeated, contact the HP Support
Center for assistance.
Error accessing CRU information57
Replace the CRU that was reported. If the error
message is repeated, contact the HP Support
Center for assistance.
Checksum error accessing CRU information58
Contact the HP Support Center for assistance.CRU information version error59
Event Logs for Troubleshooting Diagnostics
This section describes general diagnostic tools that are provided for the server and how to generate
other event logs for troubleshooting diagnosis.
• Machine Check Analyzer
NOTE: The Machine Check Analyzer decodes and analyzes Machine Check Abort error
logs, and interprets Corrected Machine Checks (CMC) and Corrected Platform Events (CPE).
It also identifies the root cause of the failure and provides a list of CRUs that may have
caused the failure.
• Event logs not generated by the iLO MP include:
— Machine Check Abort log (MCA)
— Corrected Machine Check log (CMC)
— Corrected Platform Error log (CPE)
To access these logs, enter the following at the shell> command line prompt:
— errdump mca
— errdump cmc
— errdump cpe
Often the underlying root cause of an event is captured by the server or BMC firmware in both
the System Event and Forward Progress Event Logs (SEL and FP, respectively). These errors are
easily matched with events by their timestamps. For example, the loss of a CPU’s VRM might
cause a CPU fault. Decoding the error logs would only identify the failed CPU as the most likely
faulty CRU. Following are some important points to remember about events and event logs:
• Event logs are the equivalent of the old chassis logs for status or error information output.
• Symbolic names are used in the source code; for example, MC_CACHE_CHECK.
• The hex code for each event log is 128 bits long with an architected format:
— Some enumerated fields can be mapped to defined text strings.
— All can be displayed in hex, keyword, or text mode.
• Events are created by firmware or OS code, and are sent over the PDH bus to the BMC for
storage in either or both of the SEL and FP logs (HP-UX shows an I/O path for the BMC).
Event Logs for Troubleshooting Diagnostics 137