HP Management Platform Synchronization Installation and Reference Manual

OVO Collection Extensions
25
In the new releases of HPUX – 11.31 and later, EMS is replaced by the System Fault Manager
(SFM). Incidents from SFM are sent directly to the CMS using the WBEM message standard. In this
case there would be no collection through OVO needed.
4-1
4-1
4-1
4-1
-2-2 Event Collection and Incident Generation for the Solaris Platform
As the diagnostic software in the Solaris platform has different capabilities compared to the HP-UX
platform’s EMS, MPS uses a different approach. The template for the OVO agent on a Solaris
platform monitors the syslog file of the monitored device. The logfile reader is installed through OVO
as part of the MPS template distribution. The MPS-OVO monitoring template contains a list of all
hardware event messages of the Solaris platform that HP support should handle and process.
When a hardware event message is located, an OVO message is created and the adjacent lines in
the syslog file are appended to the message to provide enhanced problem identification data for HP
support. The OVO agent will then send the event as a regular OVO message with the additional
information to the OVO management station. MPS then picks the message up and copies it to HP
support.
-2-3 Event Collection and Incident Generation for the AIX Platform
MPS uses a similar approach to the Solaris platform for AIX managed systems. The template for the
OVO agent on an AIX platform also monitors the syslog file of the monitored device. The logfile
reader is however already part of the AIX operating system. The MPS-OVO monitoring template just
asks the errpt logfile reader to show all hardware event messages that HP support would need.
When a hardware event message is located, an OVO message is created and the information from
the errpt logfile reader is added to the message to provide enhanced problem identification data for
HP support. The OVO agent will then send the event as a regular OVO message with the additional
information to the OVO management station. MPS then picks the message up and copies it to HP
support.
-2-4 Submitting Received OVO Messages as Incidents to HP
The OVO message will be updated in OVO immediately when it is picked up by MPS to indicate that
HP has been informed about the incident.
When an event requires action by HP support, additional entitlement, contact, and contract
information from the device database on the CMS is added and it is submitted to HP’s Workflow
Manager (WFM) as an incident. MPS will obtain entitlement, contact and contract information from
the OSEM Managed Server Page database on the CMS, it will add this data to the incident, and it
will then submit the incident to HP for further processing.
-2-5 Registration of devices
In the OVO environment the devices hostname or FQDN is used for identification. For service
incidents this information is not enough. Serial numbers, Model numbers, location, contact and
contract data is needed.
To ensure that HP accepts an incident from a device which is monitored by OVO, a registration step
is part of the installation, as described below. During the registration process the device is identified
and registered in the CMS so that it can be found in the contract database of HP. Device serial
number and other information is also send and stored on the CMS. It is also necessary to add some
data like the contract identifier and contact data inside the CMS. The registration can be repeated at
anytime to ensure that changed FQDNs do identify the correct device.