Managing your infrastructure from chip to the business service

5. The OM service map is updated with a failure-level status on both the physical server symbol and
the Exchange service symbol.
6. The OM event browser is updated with a similar level of hard drive and Exchange service entries.
7. From the Insight Manager symbol in the root cause display, the administrator launches the HP SIM
to collect hardware details on drive size, configuration, and overall server status
Note:
In this example, the failed drive is part of a RAID array, so there is no
server down time and no interruption to the Exchange service
8. After the drive is replaced, the RAID array begins its automatic rebuild and the OM service map is
updated to reflect only a minor problem status for both the server and the Exchange service.
Figure 1: HP Hardware Events Translated and Displayed in the OM Event Browser
9. In the OM event browser, the critical and major events previously logged are automatically closed
and replaced with minor level indications.
10. When the drive rebuild is complete, all events associated with the drive failure and replacement
are automatically closed, and the OM service map symbols for the server and the Exchange
service return to their normal condition.
The previous example illustrates how, using default functionality of the Insight Manager policies
shipped with HP OM, the administrator can:
• Clearly see the relationship between the failed hard drive and the Exchange service.
• Quickly prioritize, diagnose, and resolve the problem through easy access to service level,
application, and in-depth hardware infrastructure data.
• Maintain systems and service availability.
• Provide a resolution using a streamlined and efficient set of processes. Event closure was handled
automatically using policy based definitions, removing the need to physically acknowledge and
close each individual event (total of 4–6 events depending on the configuration).