Logical Volume Summary | HP HA s Software specification

Monitoring Disk Resources

Disk Monitor Reference

	Logical Volume Summary
	The logical volume summary tells you how accessible the data is in all logical
	volumes in an active volume group. Sometimes the physical connection may be
	working, but the application cannot read or write data on the disk. The disk monitor
	determines I/O activity by querying LVM, and marks a logical volume as DOWN if
	a portion of its data is unavailable.

NOTE	The disk monitor cannot determine data accessibility to logical volumes in an
	inactive volume group.
	The values in Table 2-3 are 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_DOWN.
Table 2-3	Interpreting Logical Volume Summary

Resource Name			/vg/vgName/lv_summary

Condition		Value	Interpretation

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

INACTIVE		2	The volume group is inactive. This could be because:
			• The volume group is active in exclusive mode on another node
			in an MC/ServiceGuard cluster. (This is not valid for clusters
			running MC/LockManager, because it can support a volume
			group being active on more than one node.) Note that
			MC/ServiceGuard does allow a volume group to be active in
			read-only mode, if it is already active on another node.
			• The volume group was made inactive usingvgchange -a n
			for maintenance or other reasons.
			• There was not a quorum of active physical volumes at system
			boot, i.e. not enough disks in the volume group were working.

INACTIVE_DOWN		3	The last time the inactive volume was activated, it was DOWN; at
			least one logical volume in the volume was inaccessible

DOWN		4	At least one logical volume in the volume group reports a status of
			either INACTIVE or DOWN. Note that an inactive logical volume
			in an active volume group is rare, but possible. See “Logical
			Volume Status” on page 38.

Chapter 2

37

Image 37

HP HA s Software manual Interpreting Logical Volume Summary

Contents

B5735-90001 August Using EMS HA Monitors Legal Notices Contents Monitoring Network Interfaces Monitoring Cluster Resources Monitoring 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 Monitors Chapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA Monitors Removing EMS HA Monitors Event Monitoring Service Resource Class Hierarchy Using EMS HA MonitorsStatus AvailMB Pvpvlink Event Monitoring Service Screen Screen Selecting a Resource to Monitor Using Wildcards Monitoring Request Parameters Creating a Monitoring Request How Do I Tell EMS When to Send Events? Which Protocols Can I Use to Send Events? What is a Polling Interval? What is a Notiﬁcation Comment? Modifying Monitoring Requests Copying Monitoring RequestsRemoving Monitoring Requests Service EMS Conﬁguring MC/ServiceGuard Package Dependencies Package Conﬁguration 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 Reference Interpreting Physical Volume Summary Physical Volume Summary Disk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link Status Interpreting Logical Volume Summary Logical Volume Summary Interpreting Logical Volume Status Logical Volume StatusLogical volume is inactive Logical volume is DOWN, a complete copy of the data is not Interpreting Logical Volume Copies Logical Volume Number of Copies Rules 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 Arrays Adding 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 Arrays Pvgup Return Mirrored Disks Example Resources to Monitor for Mirrored Disks Monitoring 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 Option Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Interpreting Custer Status Cluster Status Interpreting Node Status Node Status Interpreting Package Status Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status Chapter Conﬁguring Network Monitoring Requests Net/interfaces/lan/status/LANname When value is30 sec Hour Monitoring System Resources System Resource Monitor Class Hierarchy System Monitor Reference Interpreting 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 tracing EMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations Testing Disk Monitor Requests Testing Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index