Interpreting Job Queues | HP HA s Software manual

Monitoring System Resources

System Monitor Reference

Job Queues

The job queue monitor checks the average number of processes that have been waiting for CPU and performing disk I/O over the last 1, 5, or 15 minutes. A value of 4 in /system/jobQueue5Min means that at the time of polling there was an average of 4 jobs in the queue over the last 5 minutes.

The MIB variables computerSystemAvgJobs1, computerSystemAvgJobs5, and computerSystemAvgJobs15 from the hp-unix MIB provides the resource value to the monitor.

		To verify the load averages on the system, use the uptime (1) command.
Table 5-2		Interpreting Job Queues

		Resource Name	Value	Interpretation
		Resource Name	Range	Interpretation
			Range

	/system/jobQueue1Min		integer	Average number of jobs in the queue in the last
				minute.

	/system/jobQueue5Min		integer	Average number of jobs in the queue in the last 5
				minutes.

	/system/jobQueue15Min		integer	Average number of jobs in the queue in the last 15
				minutes.

The minimum polling interval is 30 seconds. Unless your system load tends to ﬂuctuate wildly and need load-balancing attention frequently, set a polling interval greater than or equal to the job queue interval: 1, 5, and 15 minutes, respectively.

70

Chapter 5

Image 70

HP HA s Software manual Interpreting Job Queues, Resource Name Value Interpretation Range

Contents

Using EMS HA Monitors B5735-90001 August Legal Notices Contents Monitoring Cluster Resources Monitoring Network Interfaces Monitoring 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 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? Modifying Monitoring Requests Copying Monitoring RequestsRemoving 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 Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Cluster Status Interpreting Custer Status Node Status Interpreting Node Status Package Status Interpreting Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status 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 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 Logging and tracing EMS Logging EMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations 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