HP HA s Software manual Resources to Monitor for RAID Arrays, RAID Array Example

Page 51

Monitoring Disk Resources

Creating Disk Monitoring Requests

Resources to Monitor for RAID Arrays

These considerations are relevant to all supported RAID configurations listed at the beginning of this chapter. To adequately monitor a RAID system, create requests to monitor at least the following resources for all volume groups on a node:

/vg/vgName/pv_summary

This gives you an overview of the status of the entire physical volume

 

 

group and is recommended when using EMS in conjunction with

 

 

MC/ServiceGuard; see “Rules for Using the EMS Disk Monitor with

 

 

MC/ServiceGuard” on page 40.

vg/vgName/pv_pvlink/status/*

This gives you the status of each PV link in the array and is redundant

 

 

to pv_summary. It is recommended when using EMS outside of the

 

 

MC/ServiceGuard environment, or if you require specific status on

 

 

each physical device.

vg/vgName/lv_summary

This gives you the status of data availability on the array.

 

Figure 2-4 represents a node with two RAID arrays and two PV links to each are

Figure 2-4

RAID Array Example

Bus A for vgdance: /dev/dsk/c1t0d0 /dev/dsk/c1t2d0

Bus A for vgdsing: /dev/dsk/c1t0d1 /dev/dsk/c1t2d1

t0

vgdance

 

 

 

 

 

 

 

 

Bus B for vgdance:

 

 

 

 

node1

 

 

/dev/dsk/c2t1d0

 

 

 

 

 

 

 

 

 

/dev/dsk/c2t3d0

 

 

 

 

 

 

 

 

 

Bus B for vgsing:

 

Bus A (c1)

 

 

Bus B (c2)

 

 

 

/dev/dsk/c2t1d1

 

 

 

 

 

 

 

 

 

/dev/dsk/c2t3d1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

t1

 

 

 

 

 

 

 

 

 

 

 

 

t2

 

 

t3

 

 

 

 

 

 

 

 

 

 

 

 

lun 0

lun 0

lun 0

lun 0

 

 

vgsing

 

 

 

lun1

lun1

lun1

lun1

Chapter 2

51

Image 51
Contents B5735-90001 August Using EMS HA MonitorsLegal Notices Contents Monitoring Network Interfaces Monitoring Cluster ResourcesTroubleshooting Monitoring System ResourcesGlossary Contents Printing History Printing Date Part Number EditionB5735-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? Copying Monitoring Requests Modifying 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 Reference Cluster Monitor Resource Class HierarchyCluster Interpreting Custer Status Cluster StatusInterpreting Node Status Node StatusInterpreting Package Status Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Reference Network Monitor Resource Class HierarchyInterpreting 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 ReferenceNumber 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 EMS Logging Logging and tracingEMS Tracing System Performance Issues Network 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