Manuals / HP / Computer Equipment / Software

HP HA s Software manual Pvgup Return

Models: HA s Software

1 87

Download 87 pages 29.75 Kb

Page 52

Monitoring Disk Resources

Creating Disk Monitoring Requests

Each LUN on the RAID array is in it own volume group: vgdance and vgsing. Assume this is one node in a 2-node cluster and you want to be notiﬁed when there is a failover, when any physical device fails, and when any logical volume becomes unavailable.

To be notiﬁed when a package fails over, you must conﬁgure an EMS request that is the same as the package dependency you conﬁgured in MC/ServiceGuard. See Chapter 1, “Conﬁguring MC/ServiceGuard Package Dependencies”. For this example, assume the package UP values were set as “UP” and “PVG_UP”.

To conﬁgure the EMS alerts, create the following requests:

Table 2-8		Sample Disk Monitoring Requests

				Monitoring Parameters
		Resource
		Resource	Notify				Condition	Option
			Notify				Condition	Option

	/vg/vgdance/pv_summary		when value is...		>		PVG_UP	RETURN

	/vg/vgsing/pv_summary		when value is...		>		PVG_UP	RETURN

	/vg/dance/lv_summary		when value is...		>=		INACTIVE	RETURN

	/vg/vgsing/lv_summary		when value is...		>=		INACTIVE	RETURN

If pv_summary is SUSPECT, you know a physical device fails. If pv_summary status is SUSPECT, you may want to look at your lv_summary to see if you can still access all data. If lv_summary is DOWN or INACTIVE_DOWN, you do not have a complete copy of data.

52

Chapter 2

Image 52

HP HA s Software manual Pvgup Return

Contents

Using EMS HA Monitors B5735-90001 AugustLegal Notices Contents Monitoring Cluster Resources Monitoring Network InterfacesMonitoring System Resources TroubleshootingGlossary Contents Printing Date Part Number Edition Printing HistoryB5735-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 Notiﬁcation Comment? Modifying Monitoring Requests Copying Monitoring RequestsRemoving Monitoring Requests Conﬁguring MC/ServiceGuard Package Dependencies Service EMSPackage 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 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 Resource Class Hierarchy Cluster Monitor ReferenceCluster Cluster Status Interpreting Custer StatusNode Status Interpreting Node StatusPackage Status Interpreting Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status Chapter Net/interfaces/lan/status/LANname When value is Conﬁguring Network Monitoring Requests30 sec HourMonitoring System Resources System Monitor Reference System Resource Monitor Class HierarchyInterpreting 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 Logging and tracing EMS LoggingEMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations Testing Monitor Requests Testing Disk Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor RequestsMaking Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index