Event Monitoring Service Version A.04.20.11.03, A.04.20.23.03, and A.04.20.31.03 Release Notes (March 2009)

NOTE: Updated monitors may have new status values that change the meaning of your
monitoring requests. When you update a monitor, do the following:
• Verify recent updates of the EMS bundle to ensure compatibility with the new monitor.
• Review your existing monitoring requests to ensure that they are current and reasonable
for the new monitor.
IMPORTANT: In a Serviceguard cluster environment, EMS must be updated on each node in
the cluster.
The EMS bundle (EventMonitoring) contains the following file sets:
Table 1-3 EMS Product Filesets
DescriptionFileset
Contains the EMS framework.
EMS-Core.EMS-CORE
Contains the EMS framework man pages and catalogs,
configuration scripts, start-up scripts, libraries, and EMS Agent.
EMS-Core.EMS-CORE-COM
Provides the EMS tool definitions for integrating into ServiceControl
Manager.
EMS-Core.EMS-MX
Contains EMSHAWrapperProvider.
EMS-Core.EMS-WRAPPER
Contains xml schema and mof files for EMSHAWrapperProvider.
EMS-Core.EMS-WRAPPER-COM
Provides SAM’s interface to EMS. This fileset also provides the
emscli command line utility. Refer to the emscli(1m) manpage
for more information.
EMS-Config.EMS-GUI
Provides SAM’s interface to EMS, and contains EMS GUI help files.
EMS-Config.EMS-GUI-COM
Provides MIB (Management Information Base) monitors for cluster,
networking interface, and system resources.
EMS-MIBMon
You can install EMS by either using the swinstall command or use the software management
tools in SAM.
If you have many systems, it may be easier to install over the network from a central location.
The steps to install over the network from a central location are given below:
1. Create a network depot according to the instructions in Managing HP-UX Software with
SD-UX.
2. rlogin or telnet to the remote host on which you are installing EMS.
3. Install EMS from the depot.
Your requests are retained when the monitors are updated, or when you reinstall a monitor on
top of an existing monitor. This is part of the functionality provided by the persistence client.
While installing EMS, the installation process may modify /etc/services, /etc/inittab
or /etc/inetd.conffiles. If the files are modified, a copy of the unmodified version is available
in the /etc directory. For example,
• /etc/inittab will be copied to /etc/ems_inittab.old
• /etc/services will be copied to /etc/services.old
• /etc/inetd.conf will be copied to /etc/inetd.conf.old
Removing EMS
You have to use the swremove utility or the Software Management tools in SAM to remove
EMS. Note that the monitors are persistent; that is, they are always automatically started if they
are stopped. Therefore, the following warning message may be created in your log file:
Compatibility Information and Installation Requirements 11