using hardware event monitoring, users can virtually eliminate undetected hardware failures that
could interrupt system operation or cause data loss.
WBEM indication providers
Hardware monitors are available to monitor the following components (These monitors are distributed
free on the OE media):
• Server/fans/environment
• CPU monitor
• UPS monitor*
• FC hub monitor*
• FC switch monitor*
• Memory monitor
• Core electronics components
• Disk drives
• Ha_disk_array
NOTE: No SysFaultMgmt WBEM indication provider is currently available for components
followed by an asterisk.
OpenVMS fault management and monitoring
HP WBEM Provider software enables monitoring the health of HP Integrity servers running
OpenVMS. More information on the HP WBEM providers is available at http://
h71000.www7.hp.com/doc/wbem.html.
Web Based Enterprise Services (WEBES) suite of tools aids monitoring and diagnosing the HP
OpenVMS systems.
http://www.compaq.com/support/svctools/webes/index.html
See the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring,
and Complex Systems document for OpenVMS specific monitoring tips available at http://
h71000.www7.hp.com/doc/os84_index.html.
Errors and reading error logs
Event log definitions
Often the underlying root cause of an MCA event is captured by system or iLO MP firmware in
both the System Event and Forward Progress Logs (SEL and FPL, respectively). These errors are
easily matched with MCA events by their timestamps. For example, the loss of a processor VRM
might cause a processor fault. Decoding the MCA error logs would only identify the failed processor
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 server 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 iLO MP for
storage in either or both of the SEL and FPL logs (HP-UX shows an I/O path for the iLO MP).
74 Troubleshooting
To Next Page
Loading...
Need help?
General
