Testing Monitor Requests | HP HA s Software guide

Troubleshooting

Testing Monitor Requests

Testing Monitor Requests

To test that events are being sent, use the INITIAL option available with conditional notiﬁcation when creating a monitoring request. This option sends an initial event that you can examine to make sure your request is properly conﬁgured and showing up in the correct system management tool.

An alternative is to use the “At each interval” notiﬁcation to test that events are being sent in the correct system management tool. Once you establish that events are being sent properly, you can modify the request.

Testing Disk Monitor Requests

Conﬁguring the INITIAL option may be enough. However, if you want to test that events are sent when a disk fails, you may want to detach the bus or power down the storage devices and see if events are sent to the proper application, or if MC/ServiceGuard fails over the appropriate package. This is only recommended on clusters that are off-line, and not being accessed by users.

To test /vg/vgName/lv/copies and /vg/vgName/lv/status, use the vgchange command to deactivate and activate the volume group and see if the proper alerts were sent.

Testing Cluster Monitor Requests

Use the cmviewcl -vcommand to display detailed information about the current status of the cluster and packages on the cluster. The EMS cluster monitor should return the same values as this command.

Testing Network Monitor Requests

If you want to test whether events are sent in case of network failure, use the /usr/bin/ifconfig LANname down command to bring a card down, and examine the event to make sure it shows up in the correct system management tool.

Testing System Resource Monitor Requests

Use the uptime command to verify the number of user and system load. The EMS system resource monitor should return the sam values as this command.

Chapter 6

79

Image 79

HP HA s Software manual Testing Monitor Requests, Testing Disk Monitor Requests, Testing Cluster Monitor Requests

Contents

B5735-90001 August Using EMS HA Monitors Legal Notices Contents Monitoring Network Interfaces Monitoring Cluster Resources Monitoring System Resources TroubleshootingGlossary Contents Printing Date Part Number Edition Printing HistoryB5735-90001 Page Publications PrefacePage Installing and Using EMS What are EMS HA Monitors? Event Monitoring Services High Availability Monitors Chapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA Monitors Removing EMS HA Monitors Pvpvlink Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy Status AvailMB Event Monitoring Service Screen Screen Selecting a Resource to Monitor Using Wildcards Monitoring Request Parameters Creating a Monitoring Request How Do I Tell EMS When to Send Events? Which Protocols Can I Use to Send Events? What is a Polling Interval? What is a Notiﬁcation Comment? Modifying Monitoring Requests Copying Monitoring RequestsRemoving Monitoring Requests Service EMS Conﬁguring MC/ServiceGuard Package Dependencies Package Conﬁguration Screen Package Resource Dependencies Screen Resource Parameters Screen Using EMS HA Monitors Monitoring Disk Resources Monitoring Disk Resources Disk Monitor Resource Class Hierarchy Disk Monitor Reference Interpreting Physical Volume Summary Physical Volume Summary Disk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link Status Interpreting Logical Volume Summary Logical Volume Summary Logical volume is DOWN, a complete copy of the data is not Logical Volume StatusInterpreting Logical Volume Status Logical volume is inactive Interpreting Logical Volume Copies Logical Volume Number of Copies Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for Using the EMS Disk Monitor with MC/ServiceGuard Pvsummary Calculations Case Conclusion State Rules for RAID Arrays Adding PVGs to Existing Volume Groups Creating Volume Groups on Disk Arrays Using PV Links # mkdir /dev/vgdatabase Creating Logical Volumes Rules for Mirrored Individual Disks Creating Disk Monitoring Requests Disk Monitoring Request Suggestions Parameters When Disks Fail RAID Array Example Resources to Monitor for RAID Arrays Pvgup Return Mirrored Disks Example Resources to Monitor for Mirrored Disks Monitoring Parameters Resource Notify Condition Option Resource Monitoring Parameters Notify Condition Option Resources to Monitor for Lock DisksExample for Interpreting the pvsummary for Mirrored Disks Number Pvsummary Valid Meaning Value Devices Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Interpreting Custer Status Cluster Status Interpreting Node Status Node Status Interpreting Package Status Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status Chapter Hour Net/interfaces/lan/status/LANname When value isConﬁguring Network Monitoring Requests 30 sec Monitoring System Resources System Resource Monitor Class Hierarchy System Monitor Reference Interpreting 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 EMS Logging Logging and tracing EMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations Testing Network Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Cluster Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index