Logical Volume Status | HP HA s Software specs

Monitoring Disk Resources

Disk Monitor Reference

Logical Volume Status

Logical volume status gives you status on each logical volume in a volume group. While the lv_summary tells whether data in a volume group is available, the lv/status/lvName will tell you whether speciﬁc logical volumes have failed.

The value in Table 2-4 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 INACTIVE. The numeric value allows you to tell which conditions qualify.

Table 2-4	Interpreting Logical Volume Status

Resource Name			/vg/vgName/lv/status/lvName

Condition		Value	Interpretation

UP		1	All logical volumes are accessible, all data is accessible.

INACTIVE		2	The logical volume is inactive.

DOWN		3	The logical volume is DOWN, a complete copy of the data is not
			available for this logical volume.

When conﬁguring requests from the SAM interface, a wildcard (*) may be used in place of lvName to monitor all logical volumes in a volume group.

If you split off mirrors from your mirrored conﬁguration, you will see new logical volume resource instances when the split mirror is created.

38

Chapter 2

Image 38

HP HA s Software Interpreting Logical Volume Status, Logical volume is inactive, Available for this logical volume

Contents

Using EMS HA Monitors B5735-90001 August Legal Notices Contents Monitoring Cluster Resources Monitoring Network Interfaces Glossary 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 Monitors Removing EMS HA Monitors Status AvailMB Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy Pvpvlink Event Monitoring Service Screen Selecting a Resource to Monitor Screen Using Wildcards Creating a Monitoring Request Monitoring Request Parameters How Do I Tell EMS When to Send Events? What is a Polling Interval? Which Protocols Can I Use to Send Events? What is a Notiﬁcation Comment? Removing Monitoring Requests Copying Monitoring RequestsModifying Monitoring Requests Conﬁguring MC/ServiceGuard Package Dependencies Service EMS Package Conﬁguration 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 Hierarchy Physical Volume Summary Interpreting Physical Volume Summary Disk Monitor Reference Physical Volume and Physical Volume Link Status Interpreting Physical Volume and Physical Volume Link Status Logical Volume Summary Interpreting Logical Volume Summary Logical volume is inactive Logical Volume StatusInterpreting Logical Volume Status Logical volume is DOWN, a complete copy of the data is not Logical Volume Number of Copies Interpreting Logical Volume Copies Rules 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 State Creating 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 Example Pvgup Return Resources to Monitor for Mirrored Disks Mirrored Disks Example Monitoring 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 Option Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Cluster Monitor ReferenceCluster Monitor Resource Class Hierarchy Cluster Status Interpreting Custer Status Node Status Interpreting Node Status Package Status Interpreting Package Status Creating 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 isConﬁguring Network Monitoring Requests Hour Monitoring System Resources System Monitor Reference System Resource Monitor Class Hierarchy Resource 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 Logging EMS Tracing Performance Considerations System Performance IssuesNetwork Performance Issues Testing Cluster Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Network Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index