HP HA s Software manual Physical Volume and Physical Volume Link Status

Page 36

Monitoring Disk Resources

Disk Monitor Reference

Physical Volume and Physical Volume Link Status

Requests to monitor physical volumes and physical volume links give you status on the individual physical volumes and PV links in a volume group. In the case of most RAID arrays, this means the monitor can talk to the physical link to a logical unit number (LUN) in the array. In the case of stand-alone disks, it means the monitor can talk to the disk itself.

The pv_pvlink status is used to calculate pv_summary. Although it is somewhat redundant to use both, you might want to have more specific status sent by pv_summary, and only have status sent on pv_pvlinks if a device is DOWN.

Pv_pvlinks and pv_summary supplement lv_summary by giving status on the accessibility of both active and inactive volume groups and logical volumes.

To pinpoint a failure to a particular disk, bus, or I/O card, you need to use the disk monitor alerts in conjunction with standard troubleshooting methods: reading log files, inspecting the actual devices. The disk monitor uses the data in /etc/lvmtab to see what is available for monitoring, and /etc/lvmtab does not distinguish between physical volumes and physical volume links, so you need to do additional investigation to detect whether a disk, bus, or I/O card has failed.

The value in Table 2-2 is used by the disk monitor to determine how conditions compare in logical operations. For example, you may create a request that alerts you when the condition is greater than or equal to BUSY. The numeric value allows you to tell which conditions qualify.

Table 2-2

Interpreting Physical Volume and Physical Volume Link Status

 

 

 

 

 

Resource Name

/vg/vgName/pv_pvlink/status/deviceName

 

 

 

 

 

Condition

Value

Interpretation

 

 

 

 

 

UP

1

SCSI inquiry was successful.

 

 

 

 

 

BUSY

2

SCSI inquiry returned with DEVICE BUSY; the disk monitor will try 3 times

 

 

 

to see if it gets either an UP or DOWN result before marking a device BUSY.

 

 

 

 

 

DOWN

3

SCSI inquiry failed; either the bus or disk are not accessible.

 

 

 

 

When configuring requests from the SAM interface, a wildcard (*) may be used in place of deviceName to monitor all physical volumes and physical volume links in a volume group.

36

Chapter 2

Image 36
Contents Using EMS HA Monitors B5735-90001 AugustLegal Notices Contents Monitoring Cluster Resources Monitoring Network InterfacesTroubleshooting Monitoring System ResourcesGlossary Contents Printing History Printing Date Part Number EditionB5735-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? Copying Monitoring Requests Modifying Monitoring RequestsRemoving 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 Reference Cluster Monitor Resource Class HierarchyCluster Cluster Status Interpreting Custer StatusNode Status Interpreting Node StatusPackage Status Interpreting Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Reference Network Monitor Resource Class HierarchyInterpreting 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 HierarchyNumber 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 Logging and tracing EMS LoggingEMS Tracing System Performance Issues Network 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