HP HA s Software manual Resources to Monitor for Lock Disks

Page 55

 

 

Monitoring Disk Resources

 

 

Creating Disk Monitoring Requests

Table 2-9

Example for Interpreting the pv_summary for Mirrored Disks

 

 

 

 

 

number of

 

pv_summary

 

valid

meaning

 

value

 

devices

 

 

 

 

 

 

 

 

 

10

all PVs and data accessible

UP

 

 

 

 

 

9

1 PV down, all data accessible

PVG_UP

 

 

 

 

 

8-5

if 5 PVs are from the same PVG, then all data is available

PVG_UP

 

 

 

 

 

 

if 2 or more physical volumes from different PVGs are DOWN,

SUSPECT

 

 

the disk monitor cannot conclude that all data is available

 

 

 

 

 

 

4-1

some data missing

 

 

 

 

DOWN

 

0

no data available

 

 

 

 

Resources to Monitor for Lock Disks

Lock disks are used as a tie-breaker in a forming or reforming cluster, so if you are using a lock disk with your cluster, you should request a monitor for that disk and send an alert to your system management software if the lock disk is unavailable. If the lock disk is unavailable during cluster formation, the cluster may fail to reform. Requests to monitor the lock disk might look like this:

Resource

Monitoring Parameters

Notify

Condition

Option

/vg/vg02/pv_pvlink/c0t0d1

when value is

>=

BUSY

RETURN

The Repeat value in the Options will send an alert until the lock disk is available.

You need to create a request on each node in the cluster. Because the bus name and SCSI path to the lock disk may be different on each node, the resource instance may have a different name. It is merely a different path to the same lock disk.

Chapter 2

55

Image 55
Contents B5735-90001 August Using EMS HA MonitorsLegal Notices Contents Monitoring Network Interfaces Monitoring Cluster ResourcesMonitoring 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 MonitorsChapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA MonitorsRemoving EMS HA Monitors Pvpvlink Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy Status AvailMBEvent 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? Modifying Monitoring Requests Copying Monitoring RequestsRemoving 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 SummaryLogical volume is DOWN, a complete copy of the data is not Logical Volume StatusInterpreting Logical Volume Status Logical volume is inactiveInterpreting 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 Resource Monitoring Parameters Notify Condition Option Resources to Monitor for Lock DisksExample for Interpreting the pvsummary for Mirrored Disks Number Pvsummary Valid Meaning Value DevicesResources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Interpreting Custer Status Cluster StatusInterpreting Node Status Node StatusInterpreting Package Status Package StatusCreating 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 isConfiguring Network Monitoring Requests 30 secMonitoring System Resources System Resource Monitor Class Hierarchy System Monitor ReferenceInterpreting 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 tracingEMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations Testing Network Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Cluster Monitor RequestsMaking Sure Monitors are Running Glossary Notification See alert Glossary Glossary Index Index Index