Interpreting Package Status | HP HA s Software instruction

Monitoring Cluster Resources

Cluster Monitor Reference

Package Status

		The package status is the status of each package running on this node.
		The MIB variable hpmcClusterState, which is part of the hp-mcCluster MIB,
		provides the package status information to the monitor.
		The cmviewcl -vcommand displays detailed information about the current
		status of the cluster and packages on the cluster.
Table 3-3		Interpreting Package Status

	Resource Name		/cluster/package/status/packageName

	Condition	Value	Interpretation

	UP	1	The package is running on the local node.

	UNKNOWN	2	The package is not running on the local node, but may be running on
			another node in the cluster.

	DOWN	3	The package is not running on any node in the cluster.

You might want to be notiﬁed when the value of any of the packages changes to UNKNOWN or DOWN, so you can verify that MC/ServiceGuard successfully migrated the package to another system.

You may see many packages with UNKNOWN status. This is because only the node running a package has complete status for a package. Other nodes often have inactive volume groups that make it impossible to have complete knowledge of package status. If a package is running on another node in the cluster, the current node may not have complete status on that package, and reports the condition

UNKNOWN.

The minimum polling interval for cluster status is 30 seconds. You may want a longer interval, especially if system performance is affected.

Chapter 3

61

Image 61

HP HA s Software manual Interpreting Package Status

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