Compatibility Information and Installation Requirements

EMS should be installed on each node that you want to monitor. It does not need to be installed on the management station, unless you want to also monitor the management station itself.

Compatibility with HP-UX Releases

Table 1-1 EMS Hardware and HP-UX Compatibility

EMS Version	Compatible HP-UX Releases	Compatible Hardware
EMS A.01.00	HP-UX 10.20	HP-UX 800 series servers
EMS A.02.00	HP-UX 11.00	HP-UX 800 series servers
EMS A.03.00, A.03.00.01,A.03.10, andA.03.20	HP-UX 10.20 OR HP-UX 11.00	HP-UX 700 and 800 series servers
EMS A.03.20.01	HP-UX 11i B.11.11	HP-UX 700 and 800 series servers

Software Requirements

If you are a licensed MC/ServiceGuard customer using EMS to configure resources as package dependencies, you must have the correct version of MC/ServiceGuard installed.

Table 1-2 EMS MC/ServiceGuard Compatibility

EMS Version	HP-UX Release	ServiceGuard Version
A.01.00	HP-UX 10.20	MC/ServiceGuard A.10.10
A.02.00	HP-UX 11.00	MC/ServiceGuard A.11.01, A.11.03
A.02.00	HP-UX 11.00	MC/LockManager A.11.01, A.11.02, A.11.03
A.03.00, A.03.00.01, A.03.10, and A.03.20	HP-UX 10.20	MC/ServiceGuard A.10.11, A.10.12
	HP-UX 11.00	MC/ServiceGuard A.11.04, A.11.05, A.11.07, A.11.08, A.11.09
		MC/LockManager A.11.04, A.11.05, A.11.06
		ServiceGuard OPS Edition A.11.08, A.1109
A.03.20.01	HP-UX 11i B.11.11	MC/ServiceGuard A.11.09
		MC/LockManager A.11.06
		ServiceGuard OPS Edition A.11.09

Requirements for HP OpenView Users:

Configure templates into HP OpenView ITO or NNM to see the EMS events. To configure, download the latest templates from the http://software.hp.com web site. Click High Availability, then Event Monitoring Service Developers' Kit. The templates are in a list near the bottom of the Developers' Kit page. Instructions are provided with the templates.

Hardware Requirements

EMS runs on the HP 9000 series 700 and 800 servers.

Disk Requirements

EMS requires 2.75 Mb of disk space to install.

An additional 13.0 Mb of disk space should be allocated for /etc/opt to support EMS logging facilities.

Memory Requirements

EMS requires approximately 3 Mb of memory to execute.

Installing the Event Monitoring Service

EMS checks the resources for local systems only. EMS is most effective when installed and configured on all systems in your environment.

EMS should be installed on each node that you want to monitor. EMS can be installed on a running system in multi-user mode.

Use the software management tools in SAM or the swinstall command to install EMS. For details, see the swinstall manpage.




	NOTE: Updated monitors may have new status values that change the meaning of your monitoring requests. When you update a monitor: Check for recent updates of the EMS bundle to ensure compatibility with the new monitor Review your existing monitoring requests to ensure they are current and reasonable for the new monitor

The EMS bundle (Part Number B7609BA) version A.03.20.01 contains the following file sets:

EMS-Core.EMS-CORE — EMS framework
EMS-Config.EMS-GUI — SAM interface to EMS
EMS-MIBMonitor.MIBMON-RUN — MIB (Management Information Base) monitors for cluster, networking interface, and system resources

You can install EMS either of these ways:

Use swinstall, or
Use the Software Management area in SAM

If you have many systems, it may be easier to install over the network from a central location:

Create a network depot according to the instructions in Managing HP-UX Software with SD-UX.
rlogin or telnet to the remote host on which you are installing EMS.
Install over the network from the depot.

Your requests are retained when monitors are updated, or when you re-install a monitor on top of an existing monitor. This is part of the functionality provided by the persistence client.

To install EMS, the installation process may need to modify /etc/services, /etc/inittab, or /etc/inetd.conf. If it does, it first puts a copy of the unmodified version in the /var/tmp directory. For example,

/etc/inittab may be copied to /var/tmp/ems_inittab.old
/etc/services may be copied to /var/tmp/services.old
/etc/inetd.conf may be copied to /var/tmp/inetd.conf.old

Removing EMS

To remove EMS, use swremove or the Software Management products under SAM. Note that the monitors are persistent, that is, they are always automatically started if they are stopped. Therefore, it is likely you will have warnings in your removal log file that say:

Could not shut down process

or errors that say:

File /etc/opt/resomn/lbin/p_client could not be removed.

Even if you see these warnings, monitors are removed and any dirty files are cleaned up on reboot.




	CAUTION: When you remove EMS, all log files are also removed. If you wish to save any of the EMS log files, rename them or store them off before you remove EMS.