User Guide for CiscoWorks Health and Utilization Monitor 1.2 - Chapter 4 Typical Uses for HUM [CiscoWorks Health and Utilization Monitor]

Table Of Contents

Typical Uses for HUM

Monitoring Devices for Availability

Monitoring Devices for CPU, Memory and Interface Utilization

Monitoring Device Interface Errors

Monitoring PoE-enabled Devices

Creating Custom Templates for Polling

Creating Threshold Rules for MIB Variables

Creating TrendWatch Rules for MIB Variable

Generating Periodic Reports

Viewing Reports from LMS Applications

Compiling New MIB Files

Typical Uses for HUM

This chapter provides the following use cases for CiscoWorks Health and Utilization Monitor (HUM):

•Monitoring Devices for Availability

•Monitoring Devices for CPU, Memory and Interface Utilization

•Monitoring Device Interface Errors

•Monitoring PoE-enabled Devices

•Creating Custom Templates for Polling

•Creating Threshold Rules for MIB Variables

•Creating TrendWatch Rules for MIB Variable

•Generating Periodic Reports

•Viewing Reports from LMS Applications

•Compiling New MIB Files

Monitoring Devices for Availability

A network administrator wants to keep track on the critical devices in the network and wants to make sure they are available always.

To monitor the availability levels, the network administrator needs to:

Step 1 Create a Poller by selecting the devices and adding the Device Availability template.

Step 2 Set a polling interval.

CiscoWorks HUM starts monitoring the devices for availability status in the network.

The network administrator can launch the Device Availability Quick report to analyze the device availability status for the last 24 hours. For more information, see Quick Report.

For information on creating Pollers and adding devices, see Creating a Poller.

Monitoring Devices for CPU, Memory and Interface Utilization

A network administrator wants to monitor the critical devices in the network to make sure these devices are performing at an optimal level. The network administrator wants keep track on the CPU, memory, and interface utilization levels on those devices.

To monitor the CPU, memory and interface utilization levels, the network administrator needs to:

Step 1 Create a Poller by selecting the devices and adding the following templates:

•CPU Utilization

•Memory Utilization

•Interface Utilization

Step 2 Set a polling interval.

Step 3 Select the device instances.

CiscoWorks HUM starts monitoring these devices for CPU, memory and interface utilization levels.

The network administrator can launch Quick reports for CPU, memory and interface to analyze the utilization levels during the last 24 hours. For more information, see Quick Report.

For information on creating Pollers and adding devices, see Creating a Poller.

Monitoring Device Interface Errors

A network administrator wants to monitor the interface error rate levels (ifInError, ifOutErrors, ifInDiscards, ifOutDiscards) on few critical devices in the network and wants to generate a report based on the error rate levels.

To monitor the interface error rate levels, the network administrator needs to:

Step 1 Create a Poller by selecting the devices and Interface Error Rate template.

Step 2 Set a polling interval.

Step 3 Select the device instances.

CiscoWorks HUM starts monitoring the devices for interface error rate levels.

The network administrator can generate the Interface Error Rate Quick report and analyze the interface error rate levels of these critical devices. For more information, see Quick Report.

For information on creating Pollers and adding devices, see Creating a Poller.

Monitoring PoE-enabled Devices

A network administrator wants to monitor the power consumption and utilization of the PoE enabled devices in the network and wants to generate a report based on the power utilization and power consumption levels.

To monitor the PoE enabled device utilization levels, the network administrator needs to:

Step 1 Create a Poller by selecting the devices and PoE Port Utilization and PoE Power Source Equipment (PSE) Consumption template.

Step 2 Set a polling interval.

Step 3 Select the device instances.

CiscoWorks HUM starts monitoring the devices for Power utilization.

The network administrator can generate the PoE Port Utilization and PoE PSE consumption Quick Report and analyze the power utilization and consumption levels of these critical devices.

For more information, see Quick Report.

For information on creating Pollers and adding devices, see Creating a Poller.

Creating Custom Templates for Polling

A network administrator wants to create user-defined templates to monitor certain performance parameters in a device. The network administrator wants to create these templates by selecting and grouping MIB variables from a new MIB file.

CiscoWorks HUM allows the network administrator to create user-defined templates by either leveraging MIB variables from an existing System-defined template, or by grouping new MIB variables from a MIB file.

The following MIB files are available in HUM:

•CISCO-ENHANCED-MEMPOOL-MIB

•CISCO-ENVMON-MIB

•CISCO-MEMORY-POOL-MIB

•CISCO-PROCESS-MIB

•ENTITY-MIB

•OLD-CISCO-CHASSIS-MIB

•RFC1213-MIB

•IF-MIB

•CISCO-POWER-ETHERNET-EXT-MIB

•POWER-ETHERNET-MIB

•CISCO-RTTMON-MIB

To create a user-defined templates in HUM:

Step 1 Create a template by adding MIB variables from a MIB file.

Step 2 Assign alias name for the MIB variables.

Step 3 Complete template creation.

The user-defined template is created. The network administrator can use the template to monitor the performance parameters in a device.

For more information, see Creating a Template.

Network administrators can also create user-defined templates from an external MIB file. See Compiling New MIB Files.

Creating Threshold Rules for MIB Variables

A network administrator has few critical devices in the network and wants to know if these devices are performing at an optimum level. The network administrator wants to be alerted or notified if the utilization levels of these devices exceed or fall below an optimum performance level.

CiscoWorks HUM allows the network administrator to create and set threshold rules for all the devices selected for polling. Threshold rules can be set for only one MIB variable at a time and the network administrator can set many thresholds for each MIB variable.

To create threshold rules:

Step 1 Create a threshold by selecting MIB templates and adding device MIB instances.

Step 2 Apply a threshold criteria.

Threshold is created for MIB variable instance to monitor the optimal performance level of critical devices.

A user specified external command or script can also be added and is executed when a threshold rule is violated. HUM can also send E-mail notifications Trap and Syslogs when a threshold rule is violated.

The network administrator can also generate a report on Threshold Violation and analyze the data. For more information, see Threshold Violations Report.

For information on creating Pollers and adding devices, see Creating a Threshold.

Creating TrendWatch Rules for MIB Variable

A network administrator has several devices in the network and needs to know if these polled devices are within defined service level. The network administrator needs to be alerted or notified if the utilization levels of these devices exceed or fall below a defined service level.

Trendwatch is not a real-time monitor like Thresholds and is calculated on past or historical data

CiscoWorks HUM allows the network administrator to create and set trendwatch rules for all the polled devices. TrendWatch rules can be set for only one MIB variable at a time and the network administrator can set many TrendWatches for each MIB variable.

To create TrendWatch rules:

Step 1 Create a TrendWatch rule by selecting MIB variables and adding device instances.

Step 2 Apply a TrendWatch condition.

TrendWatch is created for MIB variable instance to monitor the critical devices.

When a TrendWatch rule is violated, notification is sent as an email or a trap or a syslog based on the configuration.

The network administrator can also generate a report on TrendWatch Violation and analyze the data. For more information, see TrendWatch Report.

For information on creating TrendWatch rules and adding devices, see Creating a TrendWatch.

Generating Periodic Reports

A network administrator wants to analyze the performance parameters of critical devices on a periodic basis. To do this, the network administrator wants to schedule and create a report job that generates reports on a periodic basis.

The network administrator also wants these reports to be sent as an E-mail or published to a directory as PDF files.

The network administrator can configure and schedule report jobs in HUM to generate and publish reports on a periodic basis. These reports can also be sent as an E-mail or published to a directory as PDF files.

The network administrator can schedule the following report types:

•Quick Reports

•Poller Reports

•Custom Reports

•Threshold Violation Reports

•TrendWatch Reports

•TrendWatch Summary Reports

To generate and publish reports periodically:

Step 1 Select a report type and create a schedule.

Step 2 Provide an E-mail address.

Step 3 Select a report publish directory.

Step 4 Create the report job.

The report is generated based on the schedule and sent as an E-mail. The report is also published to a directory in a PDF format.

For more information, see Report Management.

Viewing Reports from LMS Applications

A network administrator is currently working on other LMS applications such as Campus Manager, CiscoView, Device Center, LMS Portal. The network administrator wants view the reports generated by HUM while working on other LMS applications.

The network administrator can launch Device Dashboard and Interface Reports from other LMS applications such as Campus Manager, CiscoView, Device Center and LMS Portal.

To launch HUM reports from Campus Manager:

Step 1 Go to Campus Manager > Visualization > Topology Services.

Step 2 Go to Topology Map area from the Topology Tree View.

Step 3 Right-click on a device or its components.

Step 4 Select the HUM report.

The HUM report is launched.

For more information, see Launching HUM Reports from Campus Manager.

To launch HUM reports from CiscoView:

Step 1 Go to CiscoView and select a device from the Device Selector.

A graphical representation of the device chassis appears.

Step 2 Select one or more components on the device chassis by holding the Ctrl key. You can select only similar types of components. For example, you cannot select a card and an interface.

Step 3 Right-click while holding down the Ctrl key to display the context menu. Select the HUM report.

The selected HUM report is launched.

For more information, see Launching HUM Reports from CiscoView.

To launch HUM reports from Device Center:

Step 1 Go to Device Diagnostic Tools and select Device Center.

Step 2 Select a device from the Device Selector.

The Device Summary page appears.

Step 3 Go to the Functions Available panel.

Step 4 Select the HUM report from the Reports section.

The selected HUM report is launched.

For more information, see Launching HUM Reports from Device Center.

To launch HUM reports from LMS Portal:

Step 1 Go to the HUM View in LMS Portal.

Step 2 Click the device name or the interface name from the HUM portlets.

The corresponding Device Center page is launched.

For more information, see Launching HUM Reports from LMS Portal.

Compiling New MIB Files

A network administrator wants to compile a new MIB file into HUM. The network administrator wants to use this new MIB file to create user-defined templates by grouping MIB variables from this MIB file.

Network administrator can use the Load MIB option to load an external MIB file into HUM. HUM compiles this new MIB file. The network administrator can later group the MIB variables from the MIB file to create user-defined templates.

To load a MIB file into HUM:

Step 1 Go to the Admin > System Preferences page.

Step 2 Use the Load MIB option to load an external MIB file into HUM.

The selected MIB file is compiled and listed in the Show MIB drop-down list.

For more information, see Load MIB Files.

	User Guide for CiscoWorks Health and Utilization Monitor 1.2
	Chapter 4 Typical Uses for HUM
User Guide for CiscoWorks Health and Utilization Monitor 1.2 Notices Preface Chapter 1 Overview of HUM Chapter 2 What's New in HUM Chapter 3 Getting Started Chapter 4 Typical Uses for HUM Chapter 5 Poller Configuration Chapter 6 Threshold Configuration Chapter 7 Trendwatch Chapter 8 Reports Chapter 9 Administration Chapter 10 Integration with Other Applications Chapter 11 Troubleshooting and FAQs Appendix A Index	Download this chapter Chapter 4 Typical Uses for HUM Download the complete book User Guide for CiscoWorks Health and Utilization Monitor 1.2 (PDF - 3 MB) Table Of Contents Typical Uses for HUM Monitoring Devices for Availability Monitoring Devices for CPU, Memory and Interface Utilization Monitoring Device Interface Errors Monitoring PoE-enabled Devices Creating Custom Templates for Polling Creating Threshold Rules for MIB Variables Creating TrendWatch Rules for MIB Variable Generating Periodic Reports Viewing Reports from LMS Applications Compiling New MIB Files Typical Uses for HUM This chapter provides the following use cases for CiscoWorks Health and Utilization Monitor (HUM): •Monitoring Devices for Availability •Monitoring Devices for CPU, Memory and Interface Utilization •Monitoring Device Interface Errors •Monitoring PoE-enabled Devices •Creating Custom Templates for Polling •Creating Threshold Rules for MIB Variables •Creating TrendWatch Rules for MIB Variable •Generating Periodic Reports •Viewing Reports from LMS Applications •Compiling New MIB Files Monitoring Devices for Availability A network administrator wants to keep track on the critical devices in the network and wants to make sure they are available always. To monitor the availability levels, the network administrator needs to: Step 1 Create a Poller by selecting the devices and adding the Device Availability template. Step 2 Set a polling interval. CiscoWorks HUM starts monitoring the devices for availability status in the network. The network administrator can launch the Device Availability Quick report to analyze the device availability status for the last 24 hours. For more information, see Quick Report. For information on creating Pollers and adding devices, see Creating a Poller. Monitoring Devices for CPU, Memory and Interface Utilization A network administrator wants to monitor the critical devices in the network to make sure these devices are performing at an optimal level. The network administrator wants keep track on the CPU, memory, and interface utilization levels on those devices. To monitor the CPU, memory and interface utilization levels, the network administrator needs to: Step 1 Create a Poller by selecting the devices and adding the following templates: •CPU Utilization •Memory Utilization •Interface Utilization Step 2 Set a polling interval. Step 3 Select the device instances. CiscoWorks HUM starts monitoring these devices for CPU, memory and interface utilization levels. The network administrator can launch Quick reports for CPU, memory and interface to analyze the utilization levels during the last 24 hours. For more information, see Quick Report. For information on creating Pollers and adding devices, see Creating a Poller. Monitoring Device Interface Errors A network administrator wants to monitor the interface error rate levels (ifInError, ifOutErrors, ifInDiscards, ifOutDiscards) on few critical devices in the network and wants to generate a report based on the error rate levels. To monitor the interface error rate levels, the network administrator needs to: Step 1 Create a Poller by selecting the devices and Interface Error Rate template. Step 2 Set a polling interval. Step 3 Select the device instances. CiscoWorks HUM starts monitoring the devices for interface error rate levels. The network administrator can generate the Interface Error Rate Quick report and analyze the interface error rate levels of these critical devices. For more information, see Quick Report. For information on creating Pollers and adding devices, see Creating a Poller. Monitoring PoE-enabled Devices A network administrator wants to monitor the power consumption and utilization of the PoE enabled devices in the network and wants to generate a report based on the power utilization and power consumption levels. To monitor the PoE enabled device utilization levels, the network administrator needs to: Step 1 Create a Poller by selecting the devices and PoE Port Utilization and PoE Power Source Equipment (PSE) Consumption template. Step 2 Set a polling interval. Step 3 Select the device instances. CiscoWorks HUM starts monitoring the devices for Power utilization. The network administrator can generate the PoE Port Utilization and PoE PSE consumption Quick Report and analyze the power utilization and consumption levels of these critical devices. For more information, see Quick Report. For information on creating Pollers and adding devices, see Creating a Poller. Creating Custom Templates for Polling A network administrator wants to create user-defined templates to monitor certain performance parameters in a device. The network administrator wants to create these templates by selecting and grouping MIB variables from a new MIB file. CiscoWorks HUM allows the network administrator to create user-defined templates by either leveraging MIB variables from an existing System-defined template, or by grouping new MIB variables from a MIB file. The following MIB files are available in HUM: •CISCO-ENHANCED-MEMPOOL-MIB •CISCO-ENVMON-MIB •CISCO-MEMORY-POOL-MIB •CISCO-PROCESS-MIB •ENTITY-MIB •OLD-CISCO-CHASSIS-MIB •RFC1213-MIB •IF-MIB •CISCO-POWER-ETHERNET-EXT-MIB •POWER-ETHERNET-MIB •CISCO-RTTMON-MIB To create a user-defined templates in HUM: Step 1 Create a template by adding MIB variables from a MIB file. Step 2 Assign alias name for the MIB variables. Step 3 Complete template creation. The user-defined template is created. The network administrator can use the template to monitor the performance parameters in a device. For more information, see Creating a Template. Network administrators can also create user-defined templates from an external MIB file. See Compiling New MIB Files. Creating Threshold Rules for MIB Variables A network administrator has few critical devices in the network and wants to know if these devices are performing at an optimum level. The network administrator wants to be alerted or notified if the utilization levels of these devices exceed or fall below an optimum performance level. CiscoWorks HUM allows the network administrator to create and set threshold rules for all the devices selected for polling. Threshold rules can be set for only one MIB variable at a time and the network administrator can set many thresholds for each MIB variable. To create threshold rules: Step 1 Create a threshold by selecting MIB templates and adding device MIB instances. Step 2 Apply a threshold criteria. Threshold is created for MIB variable instance to monitor the optimal performance level of critical devices. A user specified external command or script can also be added and is executed when a threshold rule is violated. HUM can also send E-mail notifications Trap and Syslogs when a threshold rule is violated. The network administrator can also generate a report on Threshold Violation and analyze the data. For more information, see Threshold Violations Report. For information on creating Pollers and adding devices, see Creating a Threshold. Creating TrendWatch Rules for MIB Variable A network administrator has several devices in the network and needs to know if these polled devices are within defined service level. The network administrator needs to be alerted or notified if the utilization levels of these devices exceed or fall below a defined service level. Trendwatch is not a real-time monitor like Thresholds and is calculated on past or historical data CiscoWorks HUM allows the network administrator to create and set trendwatch rules for all the polled devices. TrendWatch rules can be set for only one MIB variable at a time and the network administrator can set many TrendWatches for each MIB variable. To create TrendWatch rules: Step 1 Create a TrendWatch rule by selecting MIB variables and adding device instances. Step 2 Apply a TrendWatch condition. TrendWatch is created for MIB variable instance to monitor the critical devices. When a TrendWatch rule is violated, notification is sent as an email or a trap or a syslog based on the configuration. The network administrator can also generate a report on TrendWatch Violation and analyze the data. For more information, see TrendWatch Report. For information on creating TrendWatch rules and adding devices, see Creating a TrendWatch. Generating Periodic Reports A network administrator wants to analyze the performance parameters of critical devices on a periodic basis. To do this, the network administrator wants to schedule and create a report job that generates reports on a periodic basis. The network administrator also wants these reports to be sent as an E-mail or published to a directory as PDF files. The network administrator can configure and schedule report jobs in HUM to generate and publish reports on a periodic basis. These reports can also be sent as an E-mail or published to a directory as PDF files. The network administrator can schedule the following report types: •Quick Reports •Poller Reports •Custom Reports •Threshold Violation Reports •TrendWatch Reports •TrendWatch Summary Reports To generate and publish reports periodically: Step 1 Select a report type and create a schedule. Step 2 Provide an E-mail address. Step 3 Select a report publish directory. Step 4 Create the report job. The report is generated based on the schedule and sent as an E-mail. The report is also published to a directory in a PDF format. For more information, see Report Management. Viewing Reports from LMS Applications A network administrator is currently working on other LMS applications such as Campus Manager, CiscoView, Device Center, LMS Portal. The network administrator wants view the reports generated by HUM while working on other LMS applications. The network administrator can launch Device Dashboard and Interface Reports from other LMS applications such as Campus Manager, CiscoView, Device Center and LMS Portal. To launch HUM reports from Campus Manager: Step 1 Go to Campus Manager > Visualization > Topology Services. Step 2 Go to Topology Map area from the Topology Tree View. Step 3 Right-click on a device or its components. Step 4 Select the HUM report. The HUM report is launched. For more information, see Launching HUM Reports from Campus Manager. To launch HUM reports from CiscoView: Step 1 Go to CiscoView and select a device from the Device Selector. A graphical representation of the device chassis appears. Step 2 Select one or more components on the device chassis by holding the Ctrl key. You can select only similar types of components. For example, you cannot select a card and an interface. Step 3 Right-click while holding down the Ctrl key to display the context menu. Select the HUM report. The selected HUM report is launched. For more information, see Launching HUM Reports from CiscoView. To launch HUM reports from Device Center: Step 1 Go to Device Diagnostic Tools and select Device Center. Step 2 Select a device from the Device Selector. The Device Summary page appears. Step 3 Go to the Functions Available panel. Step 4 Select the HUM report from the Reports section. The selected HUM report is launched. For more information, see Launching HUM Reports from Device Center. To launch HUM reports from LMS Portal: Step 1 Go to the HUM View in LMS Portal. Step 2 Click the device name or the interface name from the HUM portlets. The corresponding Device Center page is launched. For more information, see Launching HUM Reports from LMS Portal. Compiling New MIB Files A network administrator wants to compile a new MIB file into HUM. The network administrator wants to use this new MIB file to create user-defined templates by grouping MIB variables from this MIB file. Network administrator can use the Load MIB option to load an external MIB file into HUM. HUM compiles this new MIB file. The network administrator can later group the MIB variables from the MIB file to create user-defined templates. To load a MIB file into HUM: Step 1 Go to the Admin > System Preferences page. Step 2 Use the Load MIB option to load an external MIB file into HUM. The selected MIB file is compiled and listed in the Show MIB drop-down list. For more information, see Load MIB Files.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks