Table Of Contents

Overview of HUM

What is HUM?

Key Features of HUM

Key Processes in HUM

Key Acronyms, Terms and Definitions

Icons Used in HUM

Overview of HUM

---

This chapter provides an overview of CiscoWorks Health and Utilization Monitor (HUM). The chapter contains the following topics:

•What is HUM?

•Key Features of HUM

•Key Acronyms, Terms and Definitions

•Icons Used in HUM

What is HUM?

CiscoWorks HUM is a software application that allows the network administrator to monitor the health and utilization of devices connected to the network.

CiscoWorks HUM monitors the device for performance parameters such as CPU utilization, memory utilization, interface utilization, interface availability, device availability and so on. HUM does this by querying the device through Simple Network Management Protocol (SNMP).

Key Features of HUM

The key features of HUM are:

•Measures network performance by monitoring device components such as memory, CPU, interface ports for their Utilization and Availability levels.

•System-defined MIB templates for user convenience

CiscoWorks HUM provides System-defined MIB templates that allows network administrators to create Pollers easily. System-defined MIB templates provide most of the common network parameters that is needed to monitor a device connected to the network.

•User-defined MIB templates

CiscoWorks HUM allows network administrators to create custom or user-defined MIB templates by leveraging MIB variables from System-defined MIB templates or by grouping new MIB variables.

•Supports polling of additional SNMP data

CiscoWorks HUM allows network administrators to add any other Cisco MIB apart from the standard MIBs provided as part of the application to create pollers.

•Flexible polling frequencies

CiscoWorks HUM provides flexible polling frequencies or intervals ranging between 1 minute to 8 hours.

•Historical trending reports

CiscoWorks HUM offers comprehensive reporting on the data collected by polling the device. The polled information is displayed in the form of reports. These reports help the network administrator to analyze the utilization and availability of devices connected to the network. For more information, see Reports.

•Top-N/Bottom-N reporting

Provides Top-N/Bottom-N reporting on devices that have the highest/lowest utilization or availability values.

•Alerts and notifications

CiscoWorks HUM allows network administrators to set threshold values against the utilization and availability levels of device parameters such as memory, CPU, interface and so on. If threshold values are violated, HUM notifies the network administrator through e-mails, traps and syslogs. For more information, see Threshold Configuration.

•TrendWatch

TrendWatch ensures that the capacity, performance or utilization of critical resource remains within the defined service level. It also helps in capacity planning.

You can configure TrendWatches through HUM by setting up rules for each MIB-variable or on thresholds for a specific time period. TrendWatches can be scheduled (Immediate, Once, Daily, Weekly, or Monthly) as a job and can be configured to send notifications through email, traps and syslogs. For more information, see TrendWatch Configuration.

•Trap and Syslog support

CiscoWorks HUM supports sending of Traps and Syslogs to respective receiver groups. It also sends e-mail notifications when TrendWatch violations occur in HUM.

•Triggers external commands or scripts on receiving threshold violation alerts

CiscoWorks HUM supports triggering of user specified external commands or scripts to take appropriate action against threshold violations. For more information, see Threshold Configuration.

•User configurable Quick Reports

You can configure the frequency and the time to generate Quick Reports that supports report-wise scheduling. This will serve as a performance tuning parameter for you.

This feature allows you to enable or disable generating any Quick Report and also to change the frequency of report generation. By default, reports are generated every hour and all Quick reports are enable.

By default, the report generation time or schedule is spread over a period of time. If you try to configure the generation of all Quick Reports at the same time, you will be prompted to change the schedule time of the reports.

•Overlay Graphs

CiscoWorks HUM allows you to compare the historical trending of two MIB variables in the same graph in Quick Reports.

---

Note CiscoWorks HUM supports polling of only Cisco devices. If you add any other devices, HUM still allows these devices to be added to pollers. However, the application behavior may not be as expected.

---

Key Processes in HUM

Table 1-1 gives a discription of key processes in HUM.

Table 1-1 Key Processes in HUM

Process Name	Description	Dependent Process	Default State	Log Files
UPMDbEngine	This is the HUM database engine process. If this process is down, you will not be able to access HUM and polling, threshold monitoring, trendwatch monitoring will not happen.	None	Started	None
UPMDbMonitor	Responsible for monitoring the UPMDbEngine process.	UPMDbEngine	Started	UPMDbMonitor.log
UPMProcess	Responsible for the Polling engine, Threshold monitoring and Poller Management features of HUM. If this process is down, poller management, threshold management, trendwatch management will fail.	DCRServer, UPMDbMonitor	Started	upm_process.log

Key Acronyms, Terms and Definitions

Table 1-2 provides a list of key acronyms and definitions.

Table 1-2 Acronyms and Definitions

Acronym/Term	Definition
DCR	Device Credentials Repository. Shared store of devices and associated credentials accessible by the HUM application. Provided as part of CiscoWorks Common Services.
Poller	Collection of devices and template MIB instances.
Template	Collection of MIB variables logically grouped by the user or system.
Threshold	Optimal value for a MIB variable set by the user/system.
Active State	Indicates that HUM is currently polling for the device.
Inactive State	Indicates that HUM has stopped polling for the device.
Transient	Status displayed if either the device is down or the SNMP credentials are incorrect.
Permanent	Status displayed if the polled MIB variables or instances are not available.
Reachable	Device is available and reachable in the network.
Not Reachable	Device may be down or not reachable.

Icons Used in HUM

The following icons are used in HUM.

Icon	Name	Description
	Export	To export reports to a file of PDF or CSV.
	Print	To print the report.
	Help	To view the online help.
	Graph	To view the graph.
	Refresh	To reload the application page.
	Toggle	To switch between the Full Screen view and the Normal view of the application page. •Full Screen view—displays only the application configuration area. •Normal view—displays the Table of Contents, Application tabs along with the configuration area. By default, the Normal view is displayed.