![HP integrity rx2800 i4 Скачать руководство пользователя страница 73](http://html.mh-extra.com/html/hp/integrity-rx2800-i4/integrity-rx2800-i4_user-manual_164472073.webp)
Offline support tools list
Table 25 Offline Support Tools List
Functional Area
Offline Tool
SAS/SCSI Disk Firmware Update Utility
DFDUTIL
Data Copy Utility
COPYUTIL
Fault management overview
The goal of fault management and monitoring is to increase system availability, by moving from
a reactive fault detection, diagnosis, and repair strategy to a proactive fault detection, diagnosis,
and repair strategy. The objectives are as follows:
•
To detect issues automatically, as nearly as possible to when they actually occur.
•
To diagnose issues automatically, at the time of detection.
•
To automatically report in understandable text a description of the issue, the likely causes of
the issue, the recommended actions to resolve the issue, and detailed information about the
issue.
•
To ensure that tools are available to repair or recover from the fault.
HP-UX fault management
Proactive fault prediction and notification is provided on HP-UX by SysFaultMgmt WBEM indication
providers. WBEM provides frameworks for monitoring and reporting events.
SysFaultMgmt WBEM indication providers enable users to monitor the operation of a wide variety
of hardware products, and alert them immediately if any failure or other unusual event occurs. By
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
* No SysFaultMgmt WBEM indication provider is currently available for the above-listed components
followed by an asterisk.
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
HP Confidential
Errors and reading error logs
73