HP HA s Software manual Configuring MC/ServiceGuard Package Dependencies, Service EMS

Page 26

Installing and Using EMS

Using EMS HA Monitors

Configuring MC/ServiceGuard Package

Dependencies

This section describes how to use SAM to create package dependencies on EMS resources. This creates an EMS request to monitor that resource and to notify MC/ServiceGuard when that resource reaches a critical user-defined level. MC/ServiceGuard will then failover the package. Here are some examples of how EMS might be used:

• In a cluster where one copy of data is shared between all nodes in a cluster, you may want to fail over a package if the host adapter has failed on the node running the package. Because busses, controllers, and disks are shared, package fail over to another node because of bus, controller, or disk failure would not successfully run the package. To make sure you have proper failover in a shared data environment, you must create identical package dependencies on all nodes in the cluster. MC/ServiceGuard can then compare the resource “UP” values on all nodes and fail over to the node that has the correct resources available.

• In a cluster where each node has its own copy of data, you may want to fail over

 

a package to another node for any number of reasons:

 

• host adapter, bus, controller, or disk failure

 

• unprotected data (the number of copies is reduced to one)

 

• performance has degraded because one of the PV links has failed

 

In this sort of cluster of web servers, where each node has a copy of the data and

 

users are distributed for load balancing, you can fail over a package to another

 

node with the correct resources available. Again, the package resource

 

dependencies should be configured the same on all nodes.

 

This information for creating requests is also valid for EMS monitors sold with

 

other products (ATM or OTS, for example) and for user-written monitors written

 

according to developer specifications in Writing Monitors for the Event Monitoring

 

Service (EMS).

 

 

NOTE

You should create the same requests on all nodes in an MC/ServiceGuard cluster.

 

A package can depend on any resource monitored by an EMS monitor. To create

 

 

package dependencies, choose create or modify a package from the Package

 

Configuration interface under the High Availability Clusters subarea of SAM,

 

Figure 1-7. You see a new option called “Specify Package Resource Dependencies.”

26

Chapter 1

Image 26
Contents Using EMS HA Monitors B5735-90001 AugustLegal Notices Contents Monitoring Cluster Resources Monitoring Network InterfacesGlossary TroubleshootingMonitoring System Resources Contents B5735-90001 Printing HistoryPrinting Date Part Number Edition 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? Removing Monitoring Requests Copying Monitoring RequestsModifying 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 Cluster Monitor ReferenceCluster Monitor Resource Class Hierarchy Cluster Status Interpreting Custer StatusNode Status Interpreting Node StatusPackage Status Interpreting Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Interpreting LAN Interface Status Network Monitor ReferenceNetwork Monitor Resource Class Hierarchy Chapter 30 sec Net/interfaces/lan/status/LANname When value isConfiguring Network Monitoring Requests HourMonitoring System Resources System Monitor Reference System Resource Monitor Class HierarchyResource Name Value Range Interpretation Number of UsersInterpreting Number of Users Resource Name Value Interpretation Range Job QueuesInterpreting Job Queues Resource Name Filesystem Available SpaceFilesystem Available Space Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log Logging and tracing EMS LoggingEMS Tracing Performance Considerations System Performance IssuesNetwork Performance Issues 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