Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 Using the Event Monitoring Service > Chapter 1 Understanding the Event Monitoring Service

Client and Target Applications
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

This section describes some of the client and target application options and processes. Target applications can be written using the EMS API.

EMS with ServiceGuard

ServiceGuard can be configured with EMS to monitor the health of selected resources, such as disks. Based on the status of the resources, ServiceGuard can decide to fail packages over. When working with EMS, ServiceGuard acts as both the client and target application. EMS works with MC/ServiceGuard and ServiceGuard Extension for RAC.

Configure EMS requests for use with ServiceGuard packages by editing the package configuration ASCII file.

In addition, it is recommended that you also create requests through EMS to:

  • Enable a redundant notification system

  • Monitor events that affect high availability

  • Enable alerts due to a package failover

ServiceGuard may already be configured to monitor the health of nodes, services, and subnets, and to make failover decisions based on the status of these resources. Using EMS with ServiceGuard adds to the set of failures or events that trigger failover and affect availability.

EMS GUI Client Application

The EMS GUI client application available in the Resource Management area of HP SMH (HP System Management Homepage, earlier SAM) is used to create monitoring requests for resources and targets. The EMS GUI starts from the graphical version of HP SMH. Click through and select from the various screens to define your monitoring request. The options include the following:

  1. Select the resources to be monitored.

    The full path of a resource includes the resource class hierarchy and instance. An example of a full resource path for the physical volume status of the device /dev/dsk/c0t1d2 belonging to volume group vgDataBase, is /vg/vgDataBase/pv_pvlink/status/c0t1d2.

  2. Specify when to collect the value. Select either and/or all:

    • When value is ...

      If you are setting up a request for an asynchronous monitor, this is the only option available.

    • When value changes

    • At each interval

      Select this option to send an event periodically, regardless of the value.

      Define a polling interval that is appropriate to your system performance and reaction time needs. See Step 3.

  3. Specify a polling interval for how often the monitor checks the resource and reports the value.

    This applies only to non-asynchronous monitors and goes with the At each interval option in Step 2.

  4. Specify how often the monitor should check and send notification about the resource: The options are listed below.

    • Initial option immediately checks and returns the resource value regardless of threshold conditions

    • Repeat option checks and returns the resource value at each polling interval if threshold conditions have been met

    • Return option checks and returns the resource value after a threshold condition has been resolved and the threshold condition is no longer true.

  5. Specify the notification protocols:

    • opcmsg (IT/O), by severity or map severity from values listed

    • tcp or udp

    • snmp trap, by severity or map severity from values listed

    • email

    • console

    • syslog

    • textlog

    • wbem

EMS CLI Client Application

emscli is a command line utility that is used to configure and manage persistent monitoring requests for Event Monitoring Service (EMS) monitors, such as, HA Monitors, Hardware Monitors and Kernel Monitors. The emscli utility can be used to add, modify, delete, list and view monitoring requests and resources. It allows the user to generate scripts of the configured requests and also has a help feature (emscli -h) to view the usage of various options supported by emscli.

For more information on the command line options supported by emscli, refer to the emscli(1m) manpage.

NOTE: emscli should be used on HP-UX versions where the EMS GUI is not available (HP-UX 11i Version 1.6 onwards).

EMS and Target Applications

Target applications receive notification messages about the monitored resources.

To help configure your Network Node Manager and IT/Operations or other system management software for EMS, refer to the Writing Monitors for the Event Monitoring Service (EMS)) and Event Monitoring Service developer’s kit web page:

  1. Go to the Website,

    http://software.hp.com

  2. From the Website, select High Availability, then select Event Monitoring Service Developer’s Kit.

  3. Select Templates.



EMS Resource Classes
  		 


Resource Monitors  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1997, 2003, 2007 Hewlett-Packard Development Company, L.P.