Table Of Contents
Readme for CiscoWorks Health and Utilization Monitor 1.2 on Windows
Overview
Description
New Features
Hardware and Software Requirements
Downloading CiscoWorks HUM 1.2
Installing CiscoWorks HUM 1.2
Known Problems in CiscoWorks HUM 1.2
Resolved Problems in CiscoWorks HUM 1.2
Related Documentation
Documentation for CiscoWorks HUM 1.2
Readme for CiscoWorks Health and Utilization Monitor 1.2 on Windows
This Readme is for CiscoWorks Health and Utilization Monitor 1.2 on Windows over LMS 3.1. This document contains the following sections:
•
Overview
•Description
•New Features
•Hardware and Software Requirements
•Downloading CiscoWorks HUM 1.2
•Installing CiscoWorks HUM 1.2
•Known Problems in CiscoWorks HUM 1.2
•Resolved Problems in CiscoWorks HUM 1.2
•Related Documentation
Overview
CiscoWorks Health and Utilization Monitor (HUM) is a Simple Network Management Protocol (SNMP)-based MIB polling application that monitors network elements.
For instance, these network elements can be CPUs, memory, interfaces/ports, or links. HUM monitors them for their availability and utilization metrics and provides historical trends.
Description
CiscoWorks HUM 1.2 should be installed on top of either CiscoWorks HUM 1.1, HUM 1.1.1 or HUM 1.1.2. This section is applicable only if you are upgrading to HUM 1.2 from HUM 1.1 or HUM 1.1.1.
This section includes: Upgrade Notes
Upgrade Notes
•After you upgrade to HUM 1.2, all pollers configured for interface utilization of high-speed interfaces will automatically be re-configured to poll 64-bit counters.
HUM polls 64-bit counters for high-speed interfaces (greater than 20 mbps) and 32-bit counters for low speed interfaces (less than 20 mbps).
This Poller Upgrade process occurs automatically after installation. It occurs only during the initial startup of the UPMProcess.
–If the device is running with SNMPv1 image, all interfaces that are associated with the device, will poll for 32-bit Interface Utilization counters, without considering the ifspeed value.
–If the device is running with SNMPv2 or SNMPv3 images, the ifspeed value is checked for the interface. The ifspeed value is checked before polling the 32-bit and 64-bit counters.
Note If CiscoWorks daemons stop unexpectedly during Poller Upgrade, it will re-start after the UPMProcess is restarted.
•The Poller Upgrade process may take up to two hours, depending upon the number of interfaces. You can access HUM UI only after the upgrade process is complete. If you try to access HUM UI during the Poller Upgrade process, the following message appears:
Cannot access HUM GUI. Pollers are being upgraded to facilitate polling 64-bit counters. This may take several minutes to 2 hours based on the number of interfaces.
Check $NMSROOT\log\upm_pollerupgrade.log for the poller upgrade status.
As HUM data is displayed in Device Center for the devices that are being polled in HUM, Summary pane of the Device Center will be blocked and the above mentioned error message will be displayed for the devices being polled by HUM.
For the devices that are not being polled by HUM, Summary data will be available in Device Center.
•After Poller Upgrade, you must log out and log into HUM again. After Poller Upgrade,
–If some devices were not reachable during upgrade
Or
–If you want to re-configure all pollers to poll the 64-bit counters for high-speed interfaces and 32-bit counters for low-speed interfaces
Run the following script at command prompt, without modifying the pollers:
$NMSROOT\bin\perl $NMSROOT\hum\scripts\upgradePollers2HC.pl
Where, $NMSROOT is the CiscoWorks install directory.
You can also edit the pollers manually, to achieve the same result as running the command line script.
Note While running the script, make sure that all CiscoWorks daemons are running.
New Features
The following are the new features and enhancements in HUM 1.2:
TrendWatch Support
TrendWatch allows you to continuously monitor the capacity, performance, and utilization of critical resources over time. It allows you to sample the value at periodic intervals to view the trends. You can watch variable trends for an hour, days, weeks, months and years.
You can configure it to send alert notifications through E-mail, Trap or Syslog and take appropriate actions.
TrendWatch does not monitor real-time data like Threshold. It is calculated on historical data.
The TrendWatch rule can be set for only one MIB variable at a time and you can set many TrendWatches for each MIB variable.
Power over Ethernet Monitoring
A set of new System defined templates are supported in HUM Template Management for Power over Ethernet (PoE) enabled devices to monitor power consumption. You can generate quick reports for PoE port power utilization and Power Sourcing Equipment (PSE) consumption. The newly added System defined templates are:
•PoE Port Utilization
•PoE PSE Consumption
Trap and Syslog Support
HUM supports Trap and Syslog notifications, apart from the existing E-mail notification. You can configure Trap and Syslog receiver groups. You can configure TrendWatch and Threshold to send Traps and Syslogs to the receiver in the respective receiver groups.
Interface Instance Selection Capability
HUM 1.2 periodically checks and stores the following status information of the devices and interfaces in the database and memory:
•If the device status is up, all the templates are polled.
•If the device status is down, only the device and interface availability status are polled.
•If the interface status is up, the interface related templates are polled.
•If the interface status is down, only interface availability template is polled.
During every polling cycle, HUM checks the status information of the devices and interfaces in the memory and then polls for the devices and interfaces.
Quick Reports Enhancements
Two new features are added in Quick reports:
•Overlay Graph: Overlay Graphs allows you to compare the historical trending of two MIB variables. The PoE Port Utilization Quick report supports Overlay Graph.
•Standard Deviation and 95th Percentile: The Quick Report graphs shows you the standard deviation and 95th percentile values.
The following Quick reports show Standard Deviation and 95th Percentile values:
–CPU Utilization report
–Memory Utilization report
–PoE PSE Consumption report
Non-Historical Poller Support
HUM 1.2 allows you to create pollers that does not store the polled data but maintains only the threshold data. The threshold data is available only if you have configured thresholds for the poller.
User Configurable Quick Reports Schedule
This feature allows you to enable or disable the generation of any pre-defined Quick Reports. It also lets you configure the frequency of generating each Quick Report. By default, all the pre-defined Quick Reports are enabled and are generated every hour.
New Portlets
The following are the new portlets added in HUM 1.2:
1. TOP-N-Power Utilization
2. TrendWatch
3. HUM Live-Graph It
4. Custom Top/Bottom- N Records
5. Top-N Environmental Temperature
By default, the new HUM 1.2 portlets will not be available in the HUM view in LMS Portal. You will have to manually add the new HUM 1.2 portlets to the HUM view. For more information on the new portlets and adding new portlets to the HUM view, see the User Guide for CiscoWorks LMS Portal 1.2. This guide is available at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lms_portal/1.2/user/guide/LMSPortal_1.2.html
For more information on the new features, see the User Guide for CiscoWorks Health and Utilization Monitor 1.2. This guide is available at: http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_health_and_utilization_monitor/1.2/user/guide_12/HUMug.html
Hardware and Software Requirements
To check the hardware and software requirements, see Installation Guide CiscoWorks Health and Utilization Monitor 1.2. This guide is available at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_health_and_utilization_monitor/1.2/Install/guide/HUMig12.html
Downloading CiscoWorks HUM 1.2
You can download CiscoWorks HUM 1.2 from Cisco.com.
Note You must be a registered Cisco.com user to download the installation image.
To download CiscoWorks HUM 1.2:
Step 1 Click http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-hum
Step 2 Enter your Cisco.com username and password.
Step 3 Locate the file hum1_2_win.zip
Step 4 Download the file into a temporary directory on your system.
Installing CiscoWorks HUM 1.2
To check the installation steps for CiscoWorks HUM 1.2, see Installation Guide CiscoWorks Health and Utilization Monitor 1.2. This guide is available at:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_health_and_utilization_monitor/1.2/Install/guide/HUMig12.html
Known Problems in CiscoWorks HUM 1.2
Table 1 lists the known problems in CiscoWorks HUM 1.2.
Table 1 Known Problems in CiscoWorks HUM 1.2
Problem
|
Description
|
Explanation
|
CSCsj35878
|
If you edit or copy a template that you created using a newly loaded MIB, it does not display the MIB file in the Show MIB drop-down list.
|
This problem occurs when you create a template using HOST-RESOURCES-MIB or IF-MIB.
If you edit or copy the template, the flow does not display the corresponding MIB in the Show MIB drop-down list. Instead it displays the following MIB files:
•CISCO-ENHANCED-MEMPOOL-MIB (if you have selected HOST-RESOURCES-MIB) with an unselected RFC1213-MIB tree.
•RFC1213-MIB (if you have selected IF-MIB) with pre-selected RFC1213-MIB tree.
Workaround:
Create a new template.
|
CSCsz67422
|
UPMProcess is down when integrated with ACS.
|
This problem occurs when the System Identity User in ACS mode does not have the required privileges to run HUM tasks.
Workaround:
Update the System Identity User in ACS with Super Admin privileges to run HUM tasks.
To restart the UPMProcess, go to command prompt and enter pdexec UPMProcess.
|
CSCsj66428
|
The search text and search results of Create flow are displayed in the Edit flow.
|
This problem occurs when you:
1. Create a poller.
2. Search and select devices from Device Selector.
3. Click Next.
The Available Instances dialog box appears.
4. Search and select instances from the Available Instances dialog box.
5. Complete the Poller Creation wizard.
6. Select the poller and click Edit.
The Search Results tab in the Device Selector displays the search results shown during poller creation.
7. Click Next.
The Search Results tab in the Available Instances dialog ox displays the search results shown during poller creation.
The Search Input field in the Available Instances dialog box also displays the search text used during poller creation.
Workaround:
Log out and log in again after creating the Poller. The Search Results tab will not show the results shown during poller creation.
|
CSCsk63597
|
Cannot add and edit templates in the same browser session.
|
This problem happens occurs when you:
1. Go to Template Management page.
2. Select a template and click either Edit or Copy.
The Select MIB Variables page appears.
3. Open the Poller Management page in another tab or page.
4. Go to Poller Create or Edit flow and click Add User Defined Template.
You will not be able to create a user-defined template.
5. Go to template edit tab or page and click Cancel.
The Select MIB Variables page does not take you to the Template Management page, instead it takes you to the Select Devices and Templates page.
This happens when you try to edit and create templates in the same browser session.
Workaround:
In a single browser session you must work only on one task at a time. This can be creating, editing or copying a template.
If you want to do multiple tasks at the same time, you must work on separate browser sessions.
|
CSCsk61569
|
PDF generation fails if a report has large amount of data.
|
This problem occurs when you:
1. Go to Report Management page.
2. Create a Copy Quick Report or Poller Report or Custom Report by selecting the Add Full Report option.
If you select the Add Full Report option for a large amount of data, the PDF report generation fails.
Workaround:
Reduce the amount of data to be reported by 50 percent and try again. You can also split the data across multiple report jobs and generate reports.
|
CSCsx46148
|
You need to delete and re-create Interface Utilization thresholds for high speed-interfaces after you upgrade from HUM 1.1 or 1.1.1 to HUM 1.2
|
This problem occurs when you:
1. Go to CiscoWorks Health and Utilization Monitor > Threshold Management.
2. Configure a threshold for a high speed interface (ifSpeed > 20 mbps) to monitor ifInOctets/ifOutOctets counters
Or
To monitor RxUtilization/TxUtilization computed variables in HUM 1.1 or 1.1.1
After upgrade to HUM 1.2, high speed interfaces are polled using high-speed counters (ifHCInOctets/ifHCOutOctets).
The computed variables are mapped to 64bitRxUtilization/64bitTxUtilization.
After upgrade HUM continues to monitor threshold violations using correct variables in the backend.
However, in the Threshold Management UI, if you edit the Interface Utilization threshold, the previously configured counters (ifInOctets/ifOutOctets or RxUtilzation/TxUtilzation), are displayed without any instances selected in the Select Instances pane.
This is because the interfaces are being monitored using high-speed counters. You cannot change the variables in the Edit mode.
Workaround:
Delete the threshold and re-create a new threshold with the required interface instances.
|
CSCsv88040
|
HUM does not work properly if there are multiple interfaces with the same name.
|
This problem occurs when there are multiple interfaces with the same name.
The graph is not launched from the Histo Graph-it and Live Graph-it portlets. Only one instance for the interface is listed, although there might be multiple instances with the same name.
In this case, if you launch the Interface report, all instance names will appear, even if they have the same name.
In Device Report, Interface Details portlet shows the number of interfaces that are actually present.
However if you click on the Detailed report link only one interface name appears. This is because it accepts only one unique interface name.
Workaround:
None.
|
CSCsq63214
|
After upgrading to LMS 3.1, UPMProcess goes down.
|
This problem occurs if you upgrade the Windows LMS server from 3.0.1 to 3.1 in the ACS mode.
The UPMProcess goes down even if you have full privileges. This is because JVM crashed the UPMProcess.
Workaround:
Re-start the UPMProcess.
|
CSCsr83672
|
Database table is not updated for pollers that are associated with multiple templates.
|
This problem occurs when you:
1. Export Interface Utilization Template
2. Change the name of the template in the exported template file
3. Import the same template file.
4. Create a poller with the Interface Utilization System defined template and Imported template
(Assume that both the template have the same MIB variables and computation variables).
After Poller Creation has run for a while and after some polling cycles are created, the Interface Utilization portlet displays:
No Data Found. Click here to configure Pollers. Please check HUMPortal.log for more details
Workaround:
None.
|
CSCsr86278
|
When you launch the Interface report from the CM portlet, it displays an error.
|
When you launch the Interface report from the Campus Manager, N-Hop View portlet, an error appears, No data found. Please try after some time.
Workaround:
None.
|
CSCsw71763
|
If you change the variable name, it is not reflected in the configured thresholds.
|
This problem occurs when you:
1. Go to the Threshold Management page
2. Create a threshold with a variable.
3. Go to the Template Management page.
4. Edit the name of the variable with which you have created the threshold.
5. Go to the Threshold Management page
6. Edit the threshold created.
An error appears:
Could not edit the threshold. The MIB variable associated with the threshold is not available.Delete this threshold and create new threshold.
Workaround:
None.
|
CSCsu84408
|
The option to duplicate the computation variable in the Template Creation module, does not work.
|
This problem occurs when you:
1. Export a Template.
2. Edit the MIB alias name so that it is the same as the computation variable name.
For example, RxUtilization.
3. Import this template.
The template is imported.
4. Go to The Template Management page and click Create.
5. Give the MIB alias name same as any computation variable name.
An error appears:
You have given duplicate AliasName. Please give unique AliasName.
Workaround:
None.
|
CSCsw80574
|
A proper message is not displayed when a TrendWatch violation rule fails.
|
This problem occurs when you:
1. Go to the TrendWatch Management page
2. Create a TrendWatch for a duration where there is no data to validate the trendwatch violation rule.
The corresponding TrendWatch report shows Partially Successful and in the report details it shows:
No data to generate the report.
3. Create a TrendWatch for a duration where there is data to validate the TrendWatch violation rule.
If the TrendWatch violation rule fails, the corresponding TrendWatch report shows Partially Successful.
However, the report details still display:
No data to generate the report.
Actually the data is available in the database to validate the rule but the TrendWatch rule alone fails.
The TrendWatch rule fails for the selected duration and hence there is no data to generate the report.
Workaround:
None.
|
Resolved Problems in CiscoWorks HUM 1.2
Table 2 lists the resolved problems in CiscoWorks HUM 1.2.
Table 2 Resolved Problems in HUM 1.2
Bug ID
|
Summary
|
Additional Information
|
CSCsk67380
|
HUM Poller did not update the SNMP version details when you upgraded the SNMP version in the device from SNMPv1 to SNMPv2 or SNMPv3.
|
This problem has been resolved.
|
CSCsq26724
|
Device Availability Portlet displayed an incorrect value for device count.
For example, if the total number of devices managed (polled) by HUM is 6, the Device Availability portlet displayed the device count as 23.
|
This problem has been resolved.
|
CSCsq31624
|
The Quick Threshold Report did not display the Low, Medium and Critical violation details.
|
This problem has been resolved.
|
CSCsl00499
|
Interface Report was not launched if the interface name contained apostrophe (`) character.
|
This problem has been resolved.
|
CSCsv76955
|
If a device would reload and its ifIndex mapping changed, HUM did not relearn the indexes and generated false data.
|
This problem has been resolved.
|
CSCsw76838
|
If HUM managed devices with different SNMP versions, like SNMPv1, SNMPv2, and the UPMProces or CiscoWorks daemons were restarted, one device's SNMP version would get assigned to another device.
|
This problem has been resolved.
|
CSCsq71608
|
Reports were not getting generated for custom Thresholds.
|
This problem has been resolved.
|
CSCsv85323
|
HUM showed an error if the poller was updated twice, without adding any instance.
|
This problem has been resolved.
|
CSCsy23777
|
Common Services could not delete jobs like SUMMARIZE_JOB from the Job Browser.
|
This problem has been resolved.
|
Related Documentation
This section contains the information on the related documentation for CiscoWorks Health and Utilization Monitor.
This section contains Documentation for CiscoWorks HUM 1.2
Documentation for CiscoWorks HUM 1.2
This table contains the documentation set for CiscoWorks HUM 1.2:
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)
Readme for CiscoWorks Health and Utilization Monitor 1.2 on Windows
Copyright © 2009, Cisco Systems, Inc.
All rights reserved
