What is a Notiﬁcation Comment? | HP HA s Software guide

Installing and Using EMS

Using EMS HA Monitors

You may specify the ITO message severity for both normal and abnormal events:

•Normal

•Warning

•Critical

•Minor

•Major

The ITO application group is EMS(HP), the message group, HA, and the object is the full path of the resource being monitored.

See HP OpenView IT/Operations Administrators Task Guide (P/N B4249-90003) for more information on conﬁguring notiﬁcation severity.

•SNMP traps

This sends messages to applications using SNMP traps, such as Network Node Manager. See HP OpenView Using Network Node Manager (P/N J1169-90002) for more information on conﬁguring SNMP traps. The following traps are used by EMS:

EMS_NORMAL_OID “1.3.6.1.4.1.11.2.3.1.7.0.1” - Normal notiﬁcation EMS_ABNORMAL_OID “1.3.6.1.4.1.11.2.3.1.7.0.2” - Abnormal notiﬁcation EMS_RESTART_OID “1.3.6.1.4.1.11.2.3.1.7.0.4” - Restart notiﬁcation

•TCP and UDP

This sends TCP or UDP encoded events to the target host name and port indicated for that request. Thus the message can be directed to a user-written socket program.

Templates for conﬁguring IT/Operations and Network Node Manager to display EMS events can be found on the Hewlett-Packard High Availability public web page at http://www.hp.com/go/ha.

What is a Notiﬁcation Comment?

The notiﬁcation comment is useful for sending task reminders to the recipients of an event. For example, if you have a disk monitor request that reports an alert that an entire mirror has failed, when that event shows up in IT/Operations, for example, you may want it to have the name of the person to contact if disks fail. If you have conﬁgured MC/ServiceGuard package dependencies, you may want to enter the package name as a comment in the corresponding pv_summary request.

24

Chapter 1

Image 24

HP HA s Software manual What is a Notiﬁcation Comment?

Contents

Using EMS HA Monitors B5735-90001 August Legal Notices Contents Monitoring Cluster Resources Monitoring Network Interfaces Troubleshooting Monitoring System ResourcesGlossary Contents Printing History Printing Date Part Number EditionB5735-90001 Page Preface PublicationsPage Installing and Using EMS Event Monitoring Services High Availability Monitors What are EMS HA Monitors? Chapter Role of EMS HA Monitors in a High Availability Environment Installing and Removing EMS HA Monitors Installing EMS HA Monitors Removing EMS HA Monitors Using EMS HA Monitors Event Monitoring Service Resource Class HierarchyStatus AvailMB Pvpvlink Event Monitoring Service Screen Selecting a Resource to Monitor Screen Using Wildcards Creating a Monitoring Request Monitoring Request Parameters How Do I Tell EMS When to Send Events? What is a Polling Interval? Which Protocols Can I Use to Send Events? What is a Notiﬁcation Comment? Copying Monitoring Requests Modifying Monitoring RequestsRemoving Monitoring Requests Conﬁguring MC/ServiceGuard Package Dependencies Service EMS Package Conﬁguration Screen Package Resource Dependencies Screen Resource Parameters Screen Using EMS HA Monitors Monitoring Disk Resources Monitoring Disk Resources Disk Monitor Reference Disk Monitor Resource Class Hierarchy Physical Volume Summary Interpreting Physical Volume Summary Disk Monitor Reference Physical Volume and Physical Volume Link Status Interpreting Physical Volume and Physical Volume Link Status Logical Volume Summary Interpreting Logical Volume Summary Logical Volume Status Interpreting Logical Volume StatusLogical volume is inactive Logical volume is DOWN, a complete copy of the data is not Logical Volume Number of Copies Interpreting Logical Volume Copies Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for RAID Arrays Pvsummary Calculations Case Conclusion State Creating Volume Groups on Disk Arrays Using PV Links Adding PVGs to Existing Volume Groups # mkdir /dev/vgdatabase Creating Logical Volumes Rules for Mirrored Individual Disks Creating Disk Monitoring Requests Disk Monitoring Request Suggestions Parameters When Disks Fail Resources to Monitor for RAID Arrays RAID Array Example Pvgup Return Resources to Monitor for Mirrored Disks Mirrored Disks Example Monitoring Parameters Resource Notify Condition Option Resources to Monitor for Lock Disks Example for Interpreting the pvsummary for Mirrored DisksNumber Pvsummary Valid Meaning Value Devices Resource Monitoring Parameters Notify Condition Option Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Reference Cluster Monitor Resource Class HierarchyCluster Cluster Status Interpreting Custer Status Node Status Interpreting Node Status Package Status Interpreting Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Reference Network Monitor Resource Class HierarchyInterpreting LAN Interface Status Chapter Net/interfaces/lan/status/LANname When value is Conﬁguring Network Monitoring Requests30 sec Hour Monitoring System Resources System Monitor Reference System Resource Monitor Class Hierarchy Number of Users Interpreting Number of UsersResource Name Value Range Interpretation Job Queues Interpreting Job QueuesResource Name Value Interpretation Range Filesystem Available Space Filesystem Available SpaceResource Name Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log Logging and tracing EMS Logging EMS Tracing System Performance Issues Network Performance IssuesPerformance Considerations Testing Monitor Requests Testing Disk Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index