HP HA s Software manual Package Resource Dependencies Screen

Page 28

Installing and Using EMS

Using EMS HA Monitors

Figure 1-8

Package Resource Dependencies Screen

 

When you select a resource, either from the “Add a Resource” screen, or from the

 

“Package Resource Dependencies” screen by selecting a resource and clicking

 

“Modify Resource Dependencies...” you get a screen similar to Figure 1-9.

 

To make a package dependent on an EMS resource, select a Resource Up Value

 

from the list of Available Resource Values, then click “Add.” The example in Figure

 

1-9 shows the possible values for pv_summary. Different resources show different

 

available “Up” values.

 

 

NOTE

Make sure you always select UP as one of the UP values. MC/ServiceGuard creates

 

an EMS request that sends an event if the resource value is not equal to the UP

 

value.

 

If you select UP, the package fails over if the value is anything but UP. If you select

 

 

UP and PVG-UP, the package fails over if the pv_summary value is not equal to UP

 

or PVG_UP; in other words, if pv_summary were SUSPECT or DOWN.

 

The polling interval determines the maximum amount of elapsed time before the

 

monitor knows about a change in resource status. For critical resources, you may

 

want to set a short polling interval, for example 30 seconds, which could adversely

 

affect system performance. With longer polling intervals you gain system

 

performance, but risk not detecting problems soon enough.

28

Chapter 1

Image 28
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 Using EMS HA Monitors Event Monitoring Service Resource Class HierarchyStatus AvailMB 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 Requests Removing 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 Status Interpreting Logical Volume StatusLogical volume is inactive 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 Resources to Monitor for Lock Disks Example for Interpreting the pvsummary for Mirrored DisksNumber Pvsummary Valid Meaning Value Devices 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 Net/interfaces/lan/status/LANname When value is Configuring Network Monitoring Requests30 sec 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 Monitor Requests Testing Disk Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor RequestsMaking Sure Monitors are Running Glossary Notification See alert Glossary Glossary Index Index Index