HP HA s Software manual Using EMS HA Monitors, Event Monitoring Service Resource Class Hierarchy

Page 17

Installing and Using EMS

Using EMS HA Monitors

Using EMS HA Monitors

There are two ways to use EMS HA Monitors:

Configure monitoring requests from the EMS interface in the Resource Management area of SAM.

Configure package dependencies in MC/ServiceGuard by using the Package Configuration interface in the High Availability Clusters subarea of SAM or by editing the package ASCII configuration file.

The following are prerequisites to using EMS:

Disks need to be configured using the LVM (Logical Volume Manager).

Network cards need to be configured.

Filesystems need to have been created and mounted.

Resource classes are structured hierarchically, similar to a filesystem structure, although they are not actually files and directories. The classes supplied with this version of EMS are listed in Figure 1-2. Resource instances are listed in bold, and instances that are replaced with an actual name are in bold italics.

Figure 1-2

Event Monitoring Service Resource Class Hierarchy

/vg

/cluster

 

 

contains all logical volume, disk

contains all package,

and PVlink, and volume group

node, and cluster

summary status

status

 

 

/net

/system

contains network

contains all job

queue, user, and

interface status

filesystem status

 

 

 

/vgName

 

/package

/status

/interfaces /jobQueue1Min

 

 

 

 

/jobQueue5Min

 

 

 

 

 

 

 

/filesystem

 

/pv_summary

/localNode

 

 

/lan

 

/lv

/jobQueue15Min

 

 

 

 

/status

 

 

 

/lv_summary

/clusterName

 

 

 

 

 

 

 

 

 

/status

 

 

/availMB

/copies

/pv_pvlink

/packageName

/status

/numUsers

 

 

/status

/status

 

 

/clusterName

 

 

 

 

 

 

/LANname

 

/fsName

/lvName

 

 

 

 

 

 

 

 

 

 

 

/lvName /deviceName

The full path of a resource includes the class, subclasses, and instance. An example of a full resource path for the physical volume status of the device /dev/dsk/c0t1d2 belonging to volume group vgDataBase, would be /vg/vgDataBase/pv_pvlink/status/c0t1d2.

Chapter 1

17

Image 17
Contents B5735-90001 August Using EMS HA MonitorsLegal Notices Contents Monitoring Network Interfaces Monitoring Cluster ResourcesGlossary TroubleshootingMonitoring System Resources Contents B5735-90001 Printing HistoryPrinting Date Part Number Edition Page Publications PrefacePage Installing and Using EMS What are EMS HA Monitors? Event Monitoring Services High Availability MonitorsChapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA MonitorsRemoving EMS HA Monitors Event Monitoring Service Resource Class Hierarchy Using EMS HA MonitorsStatus AvailMB PvpvlinkEvent Monitoring Service Screen Screen Selecting a Resource to MonitorUsing Wildcards Monitoring Request Parameters Creating a Monitoring RequestHow Do I Tell EMS When to Send Events? Which Protocols Can I Use to Send Events? What is a Polling Interval?What is a Notification Comment? Removing Monitoring Requests Copying Monitoring RequestsModifying Monitoring Requests Service EMS Configuring MC/ServiceGuard Package DependenciesPackage Configuration 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 ReferenceInterpreting Physical Volume Summary Physical Volume SummaryDisk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link StatusInterpreting Logical Volume Summary Logical Volume SummaryInterpreting Logical Volume Status Logical Volume StatusLogical volume is inactive Logical volume is DOWN, a complete copy of the data is notInterpreting Logical Volume Copies Logical Volume Number of CopiesRules 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 ArraysAdding 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 ArraysPvgup Return Mirrored Disks Example Resources to Monitor for Mirrored DisksMonitoring Parameters Resource Notify Condition Option Example for Interpreting the pvsummary for Mirrored Disks Resources to Monitor for Lock DisksNumber Pvsummary Valid Meaning Value Devices Resource Monitoring Parameters Notify Condition OptionResources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Cluster Monitor ReferenceCluster Monitor Resource Class Hierarchy Interpreting Custer Status Cluster StatusInterpreting Node Status Node StatusInterpreting Package Status Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Interpreting LAN Interface Status Network Monitor ReferenceNetwork Monitor Resource Class Hierarchy Chapter Configuring Network Monitoring Requests Net/interfaces/lan/status/LANname When value is30 sec HourMonitoring System Resources System Resource Monitor Class Hierarchy System Monitor ReferenceResource 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 EMS Logging Logging and tracingEMS Tracing Performance Considerations System Performance IssuesNetwork Performance Issues Testing Disk Monitor Requests Testing Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor RequestsMaking Sure Monitors are Running Glossary Notification See alert Glossary Glossary Index Index Index