Performance Considerations | HP HA s Software specs

Troubleshooting

Performance Considerations

Performance Considerations

Monitoring your system, although an important part of high-availability, consumes system resources. You must carefully consider your performance needs against your need to know as soon as possible when a failure threatens availability.

System Performance Issues

The primary performance impact will be related to the polling interval and the number of resources being monitored. You need to balance your need to quickly detect failures with your need for system performance and adjust the number of resources you monitor and the polling intervals accordingly.

For example, pv_pvlink/status resource comprise the pv_summary resource. You may only want to create one pv_summary monitoring request rather than monitoring both pv_summary and pv_pvlink/status for all disks.

For polling intervals, you may want to set a short interval, 30 seconds, for resources for require quick response after failure, and set a longer polling interval, 5 minutes or more, for all other resources.

Network Performance Issues

Although monitoring is not likely to affect network performance, you may want to make sure that only necessary messages are being sent. Make sure your monitor requests are conﬁgured such that you are being notiﬁed only for things you really need to know.

78

Chapter 6

Image 78

HP HA s Software manual Performance Considerations, System Performance Issues, Network Performance Issues

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 Status AvailMB Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy 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 is inactive Logical Volume StatusInterpreting Logical Volume Status 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 Number Pvsummary Valid Meaning Value Devices Resources to Monitor for Lock DisksExample for Interpreting the pvsummary for Mirrored Disks 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 30 sec Net/interfaces/lan/status/LANname When value isConﬁguring Network Monitoring Requests 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 Cluster Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Network Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index