HP Management Platform Synchronization Installation and Reference Manual

OVO Collection Extensions
24
Although the monitoring of hardware failures does not significantly increase the load on an OVO
management system, we recommend having some reserve capacity in OVO, and to avoid deploying
MPS when OVO resources and performance are already critical.
4-1-2 Using OVO to collect incidents
In chapter 3 the monitoring done by the Remote Support Pack (RSP) on the CMS delivered the
incidents which were then reported to OVO. This monitoring does not need the installation of
monitoring agents on the monitored devices. In the few areas where monitoring agents are still
needed, MPS can leverage existing OVO agents on the monitored devices for customers who prefer
not to deploy another monitoring client in their environment.
The required OVO agent templates are provided with the MPS installation package for HP-UX, AIX
and Solaris platforms, and they can be easily distributed using the central OVO Management
Server.
Figure 4-1 Event Collection Flow
HP Service
Process
OVO
Collection
Agent
HW
template
CMS
MPS
OVO Mgmt
Station
The monitoring of incidents of devices with OVO agents provides the same type of data as CMS
monitored clients provides to HP support personnel. Additional information is collected and added to
all events. This means that HP support personnel viewing an incident for OVO monitored devices
will have the necessary information. However, for MPS, only incident monitoring is available and not
the configuration data collections required for Mission Critical environments.
Every method of monitoring requires that the monitored device has a diagnostic package running.
All these services or demons run silently in the background. Whenever an incident occurs they
provide the related information to the OVO agent directly or through a log file. This is configured by
a template which gives exact instructions how the data is to be processed so that MPS can find the
message and copy it to HP.
The event collection and incident generation process for each of the supported platforms is different
and described below.
4-1-2-1 Event Collection and Incident Generation for the HP-UX Platform
The Event Monitoring System (EMS) is the diagnostic software for HP UNIX-based systems (until
HP-UX 11.30). EMS is part of the HP-UX operating system and it handles all events from the
hardware and the operating system. EMS pre-filters the events for relevance, and passes those
events which require intervention into one of several possible event-handling systems.
In MPS a template and configuration for EMS is provided, which performs the correct pre-filtering of
events, and calls the OVO agent directly when a qualified event has occurred. This configuration
ensures that HP support personnel can view all those events which are important to delivery of the
service contract or for warranty.
The OVO agent then runs a specific template which is applied to these events submitted by EMS. It
calls an additional diagnostic function from EMS to attach event-specific relevant information such
as firmware revisions. The OVO agent will then send the event as a regular OVO message with the
additional information to the OVO management station. MPS will look for these messages through a
webservice and copy them to HP.