CiscoWorks Health and Utilization Monitor

Table Of Contents

Readme for CiscoWorks Health and Utilization Monitor 1.1.2 on Windows

Overview

Description

Hardware and Software Requirements

Downloading CiscoWorks HUM 1.1.2

Installing CiscoWorks HUM 1.1.2

Verifying the Installation

Uninstalling CiscoWorks HUM 1.1.2

Known Problems in CiscoWorks HUM 1.1.2

Resolved Problems in CiscoWorks HUM 1.1.2

Backup and Restore

Related Documentation

Documentation for CiscoWorks HUM 1.1.2

Documentation for CiscoWorks HUM 1.1

Readme for CiscoWorks Health and Utilization Monitor 1.1.2 on Windows

---

This Readme is for CiscoWorks Health and Utilization Monitor 1.1.2 on Windows. This document contains the following sections:

•Overview

•Description

•Hardware and Software Requirements

•Downloading CiscoWorks HUM 1.1.2

•Installing CiscoWorks HUM 1.1.2

•Uninstalling CiscoWorks HUM 1.1.2

•Known Problems in CiscoWorks HUM 1.1.2

•Resolved Problems in CiscoWorks HUM 1.1.2

•Backup and Restore

•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.1.2 is a service pack release and contains minor enhancements and solutions to some of the known problems of CiscoWorks HUM 1.1 and HUM 1.1.1.

CiscoWorks HUM 1.1.2 should be installed on top of CiscoWorks HUM 1.1. or HUM 1.1.1.

This section includes:

•Features

•Upgrade Notes

Features

CiscoWorks HUM 1.1.2 supports polling of 64-bit counters for high-speed interfaces for Interface Utilization.

Upgrade Notes

•After you upgrade to HUM 1.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 automatically occurs 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, the poller upgrade will re-start once 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, 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.

You can check the upm_pollerupgrade.log file for more details, at the following location:

$NMSROOT\log\

Where, $NMSROOT is the CiscoWorks install directory.

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 logout and login to 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.

---

Hardware and Software Requirements

Before installing CiscoWorks HUM 1.1.2, you must ensure that you have installed CiscoWorks HUM 1.1 or 1.1.1 on your system.

The hardware and software requirements are same as the requirements for CiscoWorks HUM 1.1 or HUM 1.1.1.

To check the hardware and software requirements, see Installing and Getting Started with CiscoWorks LAN Management Solution 3.1. This guide is available at:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

Downloading CiscoWorks HUM 1.1.2

You can download CiscoWorks HUM 1.1.2 from Cisco.com.

---

Note You must be a registered Cisco.com user to download the installation image.

---

To download CiscoWorks HUM 1.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_1_2_win.zip

Step 4 Download the file into a temporary directory on your system.

---

Installing CiscoWorks HUM 1.1.2

This section provides information on installing CiscoWorks HUM 1.1.2 on a Windows platform. See Downloading CiscoWorks HUM 1.1.2 for further information.

Before you install CiscoWorks HUM 1.1.2, ensure that CiscoWorks HUM 1.1 or 1.1.1 is installed on the CiscoWorks Server.

It is recommended that you take a back up of HUM 1.1 or 1.1.1 data.

To install CiscoWorks HUM 1.1.2:

---

Step 1 Navigate to the location on your system, where you have downloaded the hum1_1_2_win.zip file.

Step 2 Unzip the hum1_1_2_win.zip file.

The contents of the zip file are extracted to the hum1_1_2_win folder and stored in the system location where you have downloaded the zip file.

Step 3 Navigate to the folder where hum1_1_2_win.zip is extracted.

Step 4 Double-click the hum1_1_2_win.exe file.

A dialog box appears with the following message:

Automatic data backup do not happen during this installation. We recommend you to take a 
backup of data before starting this installation.

Step 5 Click Yes to proceed or No to exit installation.

If the WMI service is up and running, the following message appears when installation starts:

The setup program has detected Windows Management Instrumentation (WMI) services running.

This locks processes and impedes installation. To avoid WMI conflicts, this setup program 
will stop and immediately restart the WMI services.

Do you want to proceed? 

Step 6 Click Yes to proceed or No to exit installation.

If CiscoWorks Health and Utilization Monitor is not installed on the system, this message appears and the installation terminates:

Cannot install CiscoWorks HUM 1.1.2. CiscoWorks HUM 1.1 or 1.1.1 is not installed on your 
system. You must install CiscoWorks HUM 1.1 or 1.1.1 before installing CiscoWorks HUM 
1.1.2. 

---

Note If you have installed CiscoWorks HUM 1.1 in evaluation mode, this message appears and the installation terminates:
You have opted to upgrade HUM from 1.1 to 1.1.2. You must ensure that you have a licensed version of HUM 1.1 installed before upgrading.

---

Step 7 Click OK to continue.

The following upgrade message appears.

You are now upgrading to HUM 1.1.2. This version supports 64-bit counters for interface utilization. Post upgrade, all pollers configured for interface utilization of high speed interfaces will automatically be re-configured to poll 64-bit counters.

Step 8 Click OK to continue.

The Welcome window appears.

Step 9 Click Next to continue.

The Software License Agreement dialog box appears.

Step 10 Click Accept to accept the license agreement and proceed with the installation.

Step 11 Click Next.

The installation program checks the system configuration and required space.

Step 12 Click Next.

The Daemons Restart Option window appears with the following message:

Do you want to restart CiscoWorks Daemons at the end of this installation? 

Step 13 Either:

•Click Yes to restart the CiscoWorks daemons at the end of the installation.

Or

•Click No, if you do not want to restart the CiscoWorks daemons at the end of the installation.

In this case, you need to restart the CiscoWorks daemons manually, by running the following command from the command prompt:

net start crmdmgtd

The summary dialog box appears,

Step 14 Click Next to continue with the installation

The installation program installs CiscoWorks HUM 1.1.2 in the same directory where you have installed CiscoWorks HUM 1.1. or 1.1.1.

Step 15 Click Finish to complete the installation.

---

Verifying the Installation

To verify whether CiscoWorks Health and Utilization Monitor 1.1.2 is installed successfully:

---

Step 1 Log into CiscoWorks Server.

Step 2 Go to Common Services > Software Center > Software Update.

The Software Updates page appears.

Step 3 Check the version for CiscoWorks Health and Utilization Monitor in the Products Installed table.

If CiscoWorks Health and Utilization Monitor 1.1.2 is installed successfully, it will be listed as 1.1.2.

---

Uninstalling CiscoWorks HUM 1.1.2

Use the Uninstall option to remove CiscoWorks Health and Utilization Monitor 1.1.2 files and settings. You must be logged in as administrator to remove CiscoWorks Health and Utilization Monitor.

After you uninstall HUM 1.1.2, the system will not roll back to HUM 1.1 or 1.1.1, instead the entire HUM package will be removed from your system.

To uninstall CiscoWorks Health and Utilization Monitor 1.1.2:

---

Step 1 Go to the Windows desktop, select Start >  Programs >  CiscoWorks  >  Uninstall CiscoWorks.

If the WMI service is up and running, the following message appears when uninstallation starts:

The setup program has detected Windows Management Instrumentation (WMI) services running.

This locks processes and impedes installation. To avoid WMI conflicts, this setup program 
will stop and immediately restart the WMI services.

Do you want to proceed?

Click Yes to proceed with this uninstallation.

Click No to exit uninstallation. 

The Uninstallation dialog box appears with the installed components.

Step 2 Select the Health and Utilization Monitor 1.1.2 checkbox.

Step 3 Click Next.

The uninstallation dialog box lists the selected components.

Step 4 Click Next to continue uninstallation.

After uninstallation is complete, the following messages appear.

Uninstallation is complete. Click OK to finish.

Step 5 Click OK.

CiscoWorks HUM 1.1.2 is uninstalled from the server.

---

Known Problems in CiscoWorks HUM 1.1.2

Table 1 lists the known problems in CiscoWorks HUM 1.1.2.

Table 1 Known Problems in CiscoWorks HUM 1.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.
CSCsl00432	UPMProcess is down.	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 box 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 Poller Management page in another tab/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.
CSCsl00499	Cannot launch Interface Report if the interface name contains apostrophe (`) character.`5	This problem occurs when you: 1. Go to the LMS Portal and select HUM View. 2. Click the interface name link that contains apostrophe (`) character in any of the HUM portlets. The Interface Report is not launched, instead the following message is displayed: No data found. Please retry after some time A similar problem occurs if you click the Interface Name link that contains apostrophe (`) character in HUM reports. Workaround: None.
CSCsq26724	Device Availability Portlet displays an incorrect value for device count.	This problem occurs when you: 1. Go to CiscoWorks LMS Portal and select HUM View. 2. Go to Device Availability Portlet. The portlet displays an incorrect value for the device count. For example, if the total number of devices managed (polled) by HUM is 6, the Device Availability portlet displays the device count as 23. Workaround: None.
CSCsq31624	The Quick Threshold Report does not display the Low, Medium and Critical violation details.	This problem occurs when you: 1. Go to CiscoWorks Health and Utilization Monitor > Poller Management. 2. Click Create to create a poller. 3. Go to Threshold Management. 4. Configure threshold for the created Poller. 5. Delete the Poller after considerable violations have been reported for the threshold. After the Quick Threshold Violations Report is generated, the report will not display the details for Low, Medium and Critical violations. Workaround: None.
CSCsk61569	PDF generation fails if 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 the Add Full Report option is selected for large amount of data, the PDF report generation fails. Workaround: If the report has a large amount of data, do not select the Add Full Report option.
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.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.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.
CSCsk67380	HUM Poller does not update the SNMP version details when you upgrade the SNMP version in the device from SNMPv1 to SNMPv2 or SNMPv3.	If you have one or more devices with SNMPv1 image during HUM 1.1.2 upgrade, the Poller Upgrade process will not migrate the device to poll high-speed (64-bit) counters. This is because SNMPv1 version does not support 64-bit counters. The Poller Upgrade process is automatically run at the initial startup of UPMProcess. You can also manually run it or use the upgradePollers2HC.pl script. When you upgrade SNMPv1 devices with SNMPv2 or SMNMPv3 images, if you run the upgradePollers2HC.pl script, the device details in HUM are not updated to poll 64-bit counters Workaround: After you upgrade the device to support SNMPv2 or SNMPv3 image: 1. Remove the device from all the HUM Poller 2. Restart the UPMProcess. 3. After the UPMProcess is restarted add the device to HUM Pollers to poll SNMPv2 or SNMPv3 images, based on the credentials in the DCR.

Resolved Problems in CiscoWorks HUM 1.1.2

Table 2 lists the resolved problems in CiscoWorks HUM 1.1.2.

Table 2 Resolved Problems in CiscoWorks HUM 1.1.2

Problem	Description	Explanation
CSCsk84417	If the Japanese version of the Windows operating system was used, the Date format was displayed differently in the reports launched in HUM. The following message appeared when data was not available for the HUM Interface portlets: ASA -> -> -> -297 -> -> ->	This problem has been resolved.
CSCsq43172	If a template containing calculations was exported and then re-imported, the following error was displayed: Unable to parse the formula. Check if the computation formula is valid.	This problem has been resolved.
CSCsv80038	HUM did not poll high speed interfaces for utilization as per IF-MIB RFC (RFC 2233)	This problem has been resolved.

Backup and Restore

CiscoWorks Common Services provides Backup and Restore operations for all the installed applications.

CiscoWorks Common Services backs up the following HUM data:

•Configuration Data

•Threshold Violation Scripts

•Reports

•Template Configuration

•Database, Poller Configuration, Threshold Configuration, Admin Settings, Polled data, Threshold Violation data, Summarization data and Job information.

We recommend that you should back up the HUM 1.1 or 1.1.1 data before upgrading to HUM 1.1.2. You can schedule immediate, daily, weekly, or monthly automatic data backups by selecting LMS Portal > Common Services > Server > Admin > Backup. You should have necessary privileges to use this option.

In all Backup-Restore scenarios, a backup taken from a machine A, can be restored on the same machine A, or on a different machine B.

If you are restoring a backup taken from HUM 1.1 or 1.1.1 machine to a machine that has HUM 1.1.2 installed, then after restore you must create the following directory manually:

$NMSROOT/MDC/tomcat/webapps/upm/reports/Poller_Failure

Where $NMSROOT is the CiscoWorks installation directory.

For more information on Backup and Restore, see the User Guide for CiscoWorks Common Services.

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.1.2

•Documentation for CiscoWorks HUM 1.1

Documentation for CiscoWorks HUM 1.1.2

This table contains the documentation set for CiscoWorks HUM 1.1.2:

Document Title	Available Formats
Readme for CiscoWorks HUM 1.1.2 on Windows (this document)	•PDF on Cisco.com Software Download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-hum •On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/prod_release_notes_list.html
Readme for CiscoWorks HUM 1.1.2 on Solaris	•PDF on Cisco.com Software Download site: http://www.cisco.com/pcgi-bin/tablebuild.pl/cw2000-hum •On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/prod_release_notes_list.html
User Guide for CiscoWorks Health and Utilization Monitor 1.1.2	On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/products_user_guide_list.html
Context-sensitive Online help	•In the CiscoWorks Home Page, select HUM, then click Help (extreme right corner of your browser window). The Online help launches in a separate browser window. •In the HUM Graphical User Interface, click the Help link for context-sensitive help.

Documentation for CiscoWorks HUM 1.1

This table contains the documentation set for CiscoWorks HUM 1.1.

Document Title	Available Formats
Release Notes for CiscoWorks HUM 1.1 on Solaris	•PDF on the product CD-ROM. •On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/prod_release_notes_list.html
Release Notes for CiscoWorks HUM 1.1 on Windows	•PDF on the product CD-ROM. •On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/prod_release_notes_list.html
User Guide for CiscoWorks Health and Utilization Monitor 1.1	•PDF on the product CD-ROM. •On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/products_user_guide_list.html
Installation Guide for CiscoWorks Health and Utilization Monitor 1.1	•PDF on the product CD-ROM. •On Cisco.com at: http://www.cisco.com/en/US/products/ps9303/prod_installation_guides_list.html
User Guide for CiscoWorks Common Services 3.2	HTML and PDF formats on Cisco.com at this URL: http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html

CCDE, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, 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. (0812R)

Readme for CiscoWorks Health and Utilization Monitor 1.1.2 on Windows
Copyright © 2009, Cisco Systems, Inc.
All rights reserved