HP HA s Software manual How Do I Tell EMS When to Send Events?

Page 22

Installing and Using EMS

Using EMS HA Monitors

How Do I Tell EMS When to Send Events?

While the monitor may be polling disks every 5 minutes, for example, you may only want to be alerted when something happens that requires your attention. When you create a request, you specify the conditions under which you receive an alert. Here are the terms under which you can be notified:

When value is...

You define the conditions under which you wish to be

 

notified for a particular resource using an operator (e.g. =,

 

not equal, >, >=, <, <=) and a value returned by the

 

monitor (e.g. UP, DOWN, INACTIVE). Text values are

 

mapped to numerical values. Specific values are in the

 

chapters describing the individual monitors.

When value changes

This notification might be used for a resource that does

 

not change frequently, but you need to know each time it

 

does. For example, you would want notification each time

 

the number of mirrored copies of data changes from 2 to 1

 

and back to 2.

At each interval

This sends notification at each polling interval. It would

 

most commonly be used for reminders or gathering data

 

for system analysis. Use this for only a small number of

 

resources at a time, and with long polling intervals of

 

several minutes or hours; there is a risk of affecting

 

system performance.

If you select conditional notification, you may select one or more of these options:

Initial

Use this option as a baseline when monitoring resources such as

 

available filesystem space or system load. It can also be used to

 

test that events are being sent for a new request.

Repeat

Use this option for urgent alerts. The Repeat option sends an

 

alert at each polling interval as long as the notify condition is

 

met. Use this option with caution; there is a risk of high CPU

 

use or filling log files and alert windows.

Return

Use this option to track when emergency situations return to

 

normal.

22

Chapter 1

Image 22
Contents Using EMS HA Monitors B5735-90001 AugustLegal Notices Contents Monitoring Cluster Resources Monitoring Network InterfacesMonitoring System Resources TroubleshootingGlossary Contents Printing Date Part Number Edition Printing HistoryB5735-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 MonitorsRemoving EMS HA Monitors Status AvailMB Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy PvpvlinkEvent Monitoring Service Screen Selecting a Resource to Monitor ScreenUsing Wildcards Creating a Monitoring Request Monitoring Request ParametersHow Do I Tell EMS When to Send Events? What is a Polling Interval? Which Protocols Can I Use to Send Events?What is a Notification Comment? Modifying Monitoring Requests Copying Monitoring RequestsRemoving Monitoring Requests Configuring MC/ServiceGuard Package Dependencies Service EMSPackage Configuration 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 HierarchyPhysical Volume Summary Interpreting Physical Volume SummaryDisk Monitor Reference Physical Volume and Physical Volume Link Status Interpreting Physical Volume and Physical Volume Link StatusLogical Volume Summary Interpreting Logical Volume SummaryLogical volume is inactive Logical Volume StatusInterpreting Logical Volume Status Logical volume is DOWN, a complete copy of the data is notLogical Volume Number of Copies Interpreting Logical Volume CopiesRules 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 StateCreating 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 ExamplePvgup Return Resources to Monitor for Mirrored Disks Mirrored Disks ExampleMonitoring Parameters Resource Notify Condition Option Number Pvsummary Valid Meaning Value Devices Resources to Monitor for Lock DisksExample for Interpreting the pvsummary for Mirrored Disks Resource Monitoring Parameters Notify Condition OptionResources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Cluster Status Interpreting Custer StatusNode Status Interpreting Node StatusPackage Status Interpreting Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status Chapter 30 sec Net/interfaces/lan/status/LANname When value isConfiguring Network Monitoring Requests HourMonitoring System Resources System Monitor Reference System Resource Monitor Class HierarchyInterpreting Number of Users Number of UsersResource Name Value Range Interpretation Interpreting Job Queues 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 LoggingEMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations Testing Cluster Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Network Monitor RequestsMaking Sure Monitors are Running Glossary Notification See alert Glossary Glossary Index Index Index