A.05.80 HP Management Platform Synchronization Installation and Reference Manual (July 2012, 5900-0894)

OVO Collection Extensions
22
4 OVO Collection Extensions
4-1 Introduction
This introduction explains when it is necessary to use OVO collection extensions and how they are
installed.
IMPORTANT: This chapter describes additional features of the MPS. It is necessary to read the chapter only
IF the HW event collection is done using OVO agents:
 Collecting hardware incidents from older versions of HP-UX devices – collection can be done through
OVO agents
 Collecting hardware incidents for Solaris or AIX when a support contract for these devices is in place with
HP.
The OVO collection extension is installed according to the following steps:
1. Load or enter the entitlement data on the CMS.
2. Copy the template package on to the OVO management server.
3. Assign the templates to the monitored nodes from the OVO console.
4. Register the devices for remote monitoring from the OVO console.
4-1-1 Node Requirements
Item
Monitored HP-UX Node
Monitored AIX Node
Monitored Solaris
Node
Hardware
HP PA-RISC 9000 series
servers
p-Series
Sun Netra, Sun Starfire,
SunFire, Sun Ultra, And
Sun Ultra Enterprise
servers
O/S
HP-UX Version 11.11 or
higher
AIX Version 5.2 or higher
Solaris Version 8 or higher
Other Software
 OVO Agent Version 8.x
(HTTPS is supported as
the communication
mechanism between the
OVO agent and the OVO
Management Server)
 EMS Latest Version
OVO Agent Version 8.x (HTTPS or
DNS is supported as the
communication mechanism
between the OVO agent and the
OVO Management Server)
OVO Agent Version 8.x
(HTTPS is supported as the
communication mechanism
between the OVO agent
and the OVO Management
Server)
Network
Static TCP/IP Address
Static TCP/IP Address
Static TCP/IP Address
NOTE: For HP-UX, Solaris and AIX monitored nodes, the required software components are
deployed as part of the MPS software installation. A warning message is displayed if the minimum
hardware/software requirements are not met.