[an error occurred while processing this directive]

CiscoWorks QoS Policy Manager

Release Notes for QPM 3.0

Table of Contents

Release Notes for CiscoWorks QoS Policy Manager 3.0

Release Notes for CiscoWorks QoS Policy Manager 3.0

These release notes are for use with the CiscoWorks QoS Policy Manager (QPM) 3.0.

These release notes include:

New Features in QPM 3.0

QPM 3.0 contains the following new features:

  • QPM supports QoS monitoring. You can baseline profile traffic by top applications or DiffServ classes, select devices and interfaces for policy validation, schedule monitoring tasks, and generate monitoring reports.

  • QPM runs on the CiscoWorks Common Services server, which can be installed as a standalone server, or as an add-on to CD One 5th Edition. Common Services provides the infrastructure required by QPM to run from the CiscoWorks desktop environment, and also provides management of user roles and privileges in QPM.

  • QPM is integrated with the CiscoWorks2000 desktop, and all QPM applications are accessed from a single web interface, instead of the separate Policy Manager window and Distribution Manager window in QPM 2.x.

  • QPM's IP telephony configuration feature facilitates the QoS configuration for IP telephony. A configuration wizard guides you through the definition of your network topology, and then automatically assigns the relevant network points to the appropriate voice policy groups. You can modify the default voice policy groups.

  • QPM contains a global device inventory. Devices can be added manually, or imported directly from RME, and you assign policies to devices and network elements. This means that you do not need to define a device each time you define policies for it in different deployment groups (databases), as in QPM 2.x.

  • If you are running ACS on the network, you can use the ACS user permissions in QPM. When you use ACS user permissions, QPM synchronizes with ACS and organizes the devices in the device inventory according to the ACS device groups. Each device group can be managed separately, and a device group can contain multiple deployment groups (databases) as in QPM 2.x.

  • You can import into QPM 3.0, devices and policies from QPM 2.1.x databases. You must first export the databases to an XML file using the QPM 2.1.x export utility.

  • Additional devices and QoS features supported—see the list of supported devices and QoS features, at the following URL:


QPM 3.0 Documentation

Note   Although every effort has been made to validate the accuracy of the information in the printed and electronic documentation, you should also review the CiscoWorks QoS Policy Manager 3.0 documentation on Cisco.com for any updates.

The following documents are provided in PDF on your product CD:

  • Installation Guide for QoS Policy Manager 3.0

  • User Guide for QoS Policy Manager 3.0

  • Getting Started Guide for QoS Policy Manager 3.0

  • Note   Adobe Acrobat Reader 4.0 or later is required.

Use these publications to learn how to install and use CiscoWorks QoS Policy Manager 3.0:

  • Installation Guide for QoS Policy Manager 3.0 (DOC-7814315=)—Describes how to install QoS Policy Manager.

  • User Guide for QoS Policy Manager 3.0 (DOC-7812542=)—Describes QoS Policy Manager and how to use it.

  • Getting Started Guide for QoS Policy Manager 3.0 (DOC-7813442=)—Describes how to get started with QoS Policy Manager, and provides scenarios for using it.

  • CiscoWorks QoS Policy Manager 3.0 online help—Contains all of the information available in User Guide for QoS Policy Manager 3.0 and in Getting Started Guide for QoS Policy Manager 3.0. This ensures you have complete information even if you do not have the manual readily available while using QoS Policy Manager 3.0.

For information about QoS Policy Manager 3.0 supported devices, see the following URL:


Using the Rebuild Database Utility for QPM 3.0

The Rebuild Database utility is an external utility that enables you to rebuild a QPM database. This utility lets you compact the QPM database size. If you have a shortage of disk space during monitoring, you can free disk space by rebuilding the database. You can also use this utility to renew a QPM database that was damaged. Before running the utility, you must close QPM and CiscoWorks.

The Rebuild Database utility is installed when you install QPM 3.0, and is accessed from the QPM server's Windows Desktop.

Before You Begin

Before you run the Rebuild Database utility it is recommended that you do the following:

1. Delete the tasks that stopped due to disk space shortage.

2. Make a full backup of the QPM database, using the QPM Backup feature.

3. Close QPM and log out of the CiscoWorks2000 desktop.


Step 1   On the QPM server's Windows desktop, select Start > Programs > Cisco Systems > QoS Policy Manager > Rebuild Database.

The Rebuild Database utility starts rebuilding the QPM database.

Step 2   When the rebuild procedure is completed, you should restart your computer before resuming the monitoring of deleted tasks.

Documentation Updates

This section includes additional and updated information that is not included in the user guide, or online help.

Ports Configuration for Common Services

When you install the Common Services application, the value of the default FMS port used by the Common Services database is 9652.

This updates the information in the printed version of Quick Start Guide for QoS Policy Manager that is included in the product package.

Non-Standard TACACS Username and Password Prompts

QPM can be configured to support non-standard username and password prompts.

Your system administrator can change the system configuration file as follows:

1. On the QPM server, locate the system.cfg file under mdc\shared\config in the Common Services installation folder.

2. Open system.cfg in WordPad or other text editor.

3. Add command lines at the end of the file to configure QPM to support user-defined username, password, and enable password prompts:

  • You can configure QPM to support username, password, and enable password prompts for specific devices. For example:

where <device_name> is the name of IP of the device, and <prompt> is the user-defined prompt.
  • You can define configure QPM to support both standard and user-defined username and password prompts globally. For example:

# username prompt either old one or new one
where <prompt1> and <prompt2> are user-defined prompts.

4. Save and close the file.

5. Restart the QPM server.

QoS Types Supported by QPM Monitoring

QPM monitors class-based QoS and CAR QoS types:

  • QPM uses the information collected in the Class Based MIB and in the CAR MIB. Features that are not supported by the Class Based MIB or the CAR MIB cannot be monitored. For example, the CAR MIB does not include DSCP information, so policies with the DSCP option cannot be monitored.

  • QPM does not support monitoring of network elements that are assigned to a policy group configured with Modular Shaping.

Monitoring Task Limits

Each historical QoS analysis task can monitor a maximum of 12 interfaces, and a maximum of 12 policies on each interface. The duration limits for historical monitoring tasks depend on the polling interval, as shown in Table 1. The updated information in Table 1 replaces Table 9-1: Historical Monitoring Task Limits, in the QPM online help.

Note   The updated information in Table 1 also appears in Table 9-1: Historical Monitoring Task Limits, in the PDF version of User Guide for QoS Policy Manager 3.0 on the QPM installation CD, and in the printed version of User Guide for QoS Policy Manager 3.0.


Table 1: Historical Monitoring Task Duration Limits
Polling Interval Maximum Task Length (Days)


1 (24 hours)















Note   A full description of performing historical QoS analysis is described in Chapter 9 of User Guide for QoS Policy Manager 3.0.

Additional Information about Using the IP Telephony Wizard

The following sections provide additional information about using the IP Telephony wizard:

Multilink Interfaces with Undefined Rate

In certain types of configurations where the rate of a multilink interface is not defined, and the serial bandwidth is less than or equal to 768 kbits, the IP Telephony wizard assigns the multilink interfaces to high speed policy groups instead of low speed policy groups.

To make the correct assignment in the IP Telephony wizard, you must define the bandwidth on the multilink interface.

Policing for SoftPhone Traffic

On a Catalyst port that is connected to a PC running a SoftPhone application, the IP Telephony wizard marks all the VoIP traffic with DSCP value 46, and all the control traffic with DSCP 26. If PC users begin sending non-priority traffic using the VoIP UDP ports or the CTI TCP port, this non-priority traffic will receive the same quality of service from the network as VoIP traffic or VoIP control traffic.

You can configure policing on the inbound traffic of the Catalyst port.

For example:

  • VoIP traffic can be policed at rate 100kbps with a burst of 2kb.

  • Control traffic can be policed at 8kbps (configure 32kbs) with a burst of 8kb.

You should also set the markdown table on the device from DSCP 46 to 0, and DSCP 26 to 0. This will imply changes in the appropriate voice template.

Running the QPM Diagnostic Tool

If unusual exceptions occur or error windows are displayed while running QPM, you can obtain system status information by running the QPM Diagnostic Tool on the QPM server. The QPM Diagnostic Tool does not run automatically after installation or at any other time.

This information updates the information about the QPM Diagnostic Tool in Chapter 11 of User Guide for QoS Policy Manager 3.0.

CLI Command Translation of QPM Actions

For information about the CLI command translation of QPM actions, see the CLI Command Reference Appendix in the QPM user guide on cisco.com at the following URL:


Known Problems

Known problems (bugs) in CiscoWorks QoS Policy Manager 3.0 are graded according to severity level. These release notes contain descriptions of:

  • All severity level 1 or 2 bugs.

  • Significant severity level 3 bugs.

  • All customer-found bugs (regardless of severity level).

Table 2 describes the problems known to exist in this release.

You can search for problems using the Cisco Software Bug Toolkit. To access the Software Bug Toolkit:

Step 1   Log into Cisco.com.

Step 2   Select Service & Support>Technical Support Help—Cisco TAC>Tool Index.

Step 3   In the Jump to: links at the top of the page, click the letter S, then select Software Bug Toolkit.

You can also access the Software Bug Toolkit by entering the following URL in your web browser:

http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl .

Table 2: QoS Policy Manager 3.0 Known Problems
Bug ID
Summary Explanation

User Interface


Filtering by Voice Role doesn't work.

The filtering option for Voice Role in table headers does not work correctly.

In some cases, after filtering, all rows are still displayed, and in other cases, after filtering, no rows are displayed.

Workaround: None


bc/be must be defined although optional in 12.2T.

Class-Based Policing bc/be values are optional in 12.2T, but in QPM, you must define them.

Workaround: None.



Deployment fails for VIP DLCI with class-based QoS.

The service-policy CLI command is not supported on VIP DLCIs, and causes CLI translation errors, which result in deployment timeout.


When configuring class-based QoS for VIP DLCIs, also configure FRF policies to create an FR map-class. This prevents the CLI translation errors.


Status of deployment job remains "In progress."

If one of the devices to which the deployment job is being deployed, is not connected, the deployment job status remains "In Progress."


You can verify the deployment status for each device in the deployment job in the Job Details page.

Device Management


Cannot import devices from RME 3.4 DIFF file ver. 1 or 2.

Sometimes QPM does not import all device passwords from RME 3.4 Data Integration File Format (DIFF) export files, version 1 or 2. This results in a Telnet error for the imported devices.


When importing from RME 3.4, use Comma Separated Value Format (CSV) export files, version 1 or 2.


Problem assigning DLCI FR or VC interfaces to policy groups.

In the Interface Properties page for DLCI FR and VC, when you click on the Assign button, a Runtime error occurs.


Assign DLCI FR or VC interfaces using the Policy Group, or the Device Search.


Import fails for some devices when importing many devices.

When adding a large number of devices simultaneously, for some devices, the status remains "In progress", and the import process does not succeed.


Repeat the import process.


Not enough details given for device login errors.

Device status shows "SNMP error" or "Telnet error," but gives no details.

These are the common causes for SNMP errors:

  • The device public community string entered in QPM is incorrect. Correct the community string in QPM.

  • QPM can't read all the necessary SNMP information from the device, possibly because there are corrupted or missing MIBs.

  • The device does not have a functioning SNMP engine.

  • The SNMP request timed out, typically because the device or network was too congested to respond before the timeout limit. Retry the SNMP connection, or increase the SNMP timeout value.

These are the common causes for Telnet errors:

  • The device Telnet password entered in QPM is incorrect. Correct the Telnet password in QPM.

  • SSH is enabled, but SSH login failed because SSH is not configured correctly on the device. Fix the SSH configuration on the device.

  • The login to the device failed.

  • There is no Telnet connection to the device.

Uploading Device Configuration


CLI of uploaded ACL filter is not identical to original CLI.

Translation of uploaded class-maps that match ACLs, will not be equivalent to the original uploaded configuration if the filter is other than "match access-group xxx" where xxx is an ACL with only "permit" entries, as follows:

  • ACLs that contain more than one "deny" entry.

  • Configuration like "match not access-group xxx" if the ACL contains more than one entry.


After uploading device configuration, edit filters in QPM.

IP Telephony Wizard


Deployment to FR interface on VIP card fails.

While trying to deploy policies to a Frame Relay interface on a VIP card, the device returns the following error:

"Shaping interval is 0 milliseconds. Intervals below 4 milliseconds rejected."

This occurs because of a configuration problem. Modular shaping on VIP cards requires the BC/CIR interval to be in units of 4 milliseconds.


Adjust the shaping parameters according to the link speed. If you have several rates, you can create a group for each rate. Note that the IP Telephony wizard will assign the interfaces to only one of the groups, and you will have to move the others manually.


No warning for voice role assignments to ASIC.

In the IP Telephony wizard, when you assign an interface for a Catalyst 6000 IOS device with ASIC (Application-Specific Integrated Circuit) interfaces, QPM actually assigns all the interfaces of the ASIC. The IP Telephony wizard displays only the selected interface in the Assignment Summary page, without providing a warning that the other ASIC interfaces will also be assigned. Similarly, if you choose to remove an interface from a voice role, all the interfaces of the ASIC will be removed, but no warning message is given.

Note   You can see the full assignment of interfaces for the voice role in the Assigned Network Elements page. You can also see all the interfaces of the ASIC in the Remove Network Elements page for the voice role.

Workaround: None


Some voice policy groups not displayed in IP Telephony wizard.

When you create a voice policy group using the "Attach Policy Group Template" option in the Policy Group Definition wizard, the voice role is not copied to the created policy group. The IP Telephony wizard does not recognize this voice policy group because it has no voice role. The IP Telephony wizard does not assign interfaces to this policy group and it is not displayed in the Assignment Summary page.


Create the voice policy group using the "Copy from Policy Group Template" option in the Policy Group Definition wizard. The policy group will be displayed in the IP Telephony wizard, but it will not be connected to a template.


Deployment of policy group Acc6K_FEtoAndFromDist6K sometimes fails.

The policy group template, Acc6K_FEtoAndFromDist6K, contains policies using trust-dscp. However, on Cat6k, certain interfaces do not support trust-dscp, but QPM cannot identify these interfaces. When QPM deploys trust-dscp to these interfaces, deployment fails, with the error message—Trust type trust-dscp not supported on this port. Please change your policy configuration.


In the policy group template, Acc6K_FEtoAndFromDist6K, edit the QoS properties using the QoS Properties wizard. In the Traffic Control properties page, change the trust state from "trust-dscp" to "untrusted."


IP Telephony wizard ignores Recommend rules with device roles.

When you use the Recommend option in the IP Telephony wizard to select interfaces for voice roles, the wizard ignores imported device role information. This means that device role information is not used to select interfaces.

Workaround: None



Post traffic graph for packets/sec might be inaccurate.

In some cases, if a policy group contains both a policy that does not have an assigned queue, and a class-default policy, the calculations for post policy traffic for the class-default policy, might result in a negative value for packets/sec. In these cases, the post traffic graph displays a value of zero instead of the negative value.


Do not include both a policy that does not have an assigned queue, and a class-default policy in the same policy group.


Historical monitoring task status remains "In Edit."

A historical monitoring task status will remain "In Edit," and the task will not run, in the following conditions:

  • When the duration of the task is less that the defined polling interval.

Workaround: Ensure that the polling interval is less than the task duration time.

  • When you edit a task with task status "Collector Error."

Workaround: Delete the task and create a new task.


Historical monitoring graphs display spikes.

This problem is due to a known IOS bug, CSCdv87113:

Class Based MIB shows random large values for class of service monitor MIBs.


Use IOS 12.2(11)T or above.


QPM cannot monitor policies on ATM aal5 interfaces.

In QPM, ATM policies are defined for aal5 interfaces, not the ATM main interface, but the deployed policy information is stored in the MIB for the main ATM interface.


In QPM, configure ATM policies for ATM VC network elements.


If QPM server restarts and a monitored device is down, task ends.

When the Collector service is restarted, and a monitored device is unreachable, the collector will give it a finish status.

Workaround: None


Monitoring task window does not keep settings when refreshed.

When you refresh the Monitoring task window, the display settings return to the default settings.

Workaround: None


Historical monitoring graphs do not indicate when device is down.

Historical monitoring graphs do not indicate whether a device was down, or not reachable at any time during the task.

When there is no response from the device, the graphs continues to display the value of the last valid poll for each poll, until the device is reachable, or up again. The means that the graphs display a flat line for the time during which the device was down, or not reachable.

Workaround: None


No new real-time monitoring data displayed after device was down.

Real-time monitoring graphs do not display any new data when a monitored device becomes reachable again, after it has been down or unreachable. Real-time monitoring displays up to the last valid poll before the device became unreachable.


When a device becomes unreachable, stop the monitoring task. Create a new task when the device is reachable.


Chart color not consistent for tasks with same devices and policies.

If you create a monitoring task, then change the policies the task monitored, and redeploy, then create a new task for the same policies, the colors assigned to the policies will not be the same as for the original task.


Monitoring cannot create images on a dual-CPU machine.

In some cases, when running QPM on a dual-CPU machine, java color management crashes when trying to create images.

The problem occurs when running Windows Server.


Configure Tomcat service to use only one CPU:

1. Stop the Tomcat service.

2. Open a command prompt in directory CSCOpx\MDC\tomcat\bin

3. Export two environment variables:

set JAVA_HOME=C:\Progra~1\MDC\JRE

set TOMCAT_HOME=C:\Progra~1\MDC\tomcat

4. Execute the command: tomcat.bat run

5. Open the Task Manager and switch to the Processes tab. In the process "java.exe" that allows you to change "affinity" settings, uncheck all other CPUs except one.

6. Log into QPM. Open and view the monitoring report.

Note   If you restart the QPM server, this setting might need to be configured again.

Obtaining Documentation

These sections explain how to obtain documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:


Translated documentation is available at this URL:


Ordering Documentation

Cisco documentation is available in these ways:

  • Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:


  • Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:


  • Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling
    800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can e-mail your comments to bug-doc@cisco.com.

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.


Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

  • Streamline business processes and improve productivity

  • Resolve technical issues with online support

  • Download and test software packages

  • Order Cisco learning materials and merchandise

  • Register for online skill assessment, training, and certification programs

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to this URL:


Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquires are categorized according to the urgency of the issue:

  • Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

  • Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

  • Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

  • Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:


All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:


If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:


If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:


Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

This document is to be used in conjunction with the documents listed in the "QPM 3.0 Documentation" section.

Copyright © 1998-2002, Cisco Systems, Inc.
All rights reserved.

[an error occurred while processing this directive]