Guest

CiscoWorks QoS Policy Manager

Readme File for QPM 3.0.1 Patch

  • Viewing Options

  • PDF (132.5 KB)
  • Feedback
Readme File for QPM 3.0.1 Patch

Table Of Contents

Readme File for QPM 3.0.1 Patch

Description

Related Documentation

Documentation Update

Ports Configuration for Common Services

Downloading and Installing the Patch

New Device Support and QoS Support

New and Enhanced Features

Additional NBAR Protocols

Configuring Queuing on ASIC Interfaces

Resolved Problems

Known Problems


Readme File for QPM 3.0.1 Patch


This readme contains the following sections:

Description

Related Documentation

Documentation Update

Downloading and Installing the Patch

New Device Support and QoS Support

New and Enhanced Features

Resolved Problems

Known Problems

Description

The QPM 3.0.1 patch enhances the functionality of QoS Policy Manager 3.0 by providing:

QoS support for additional devices

Bug fixes

Related Documentation

The most updated documentation for QPM 3.0 can be found on Cisco.com:

Quick Start Guide for QoS Policy Manager 3.0

http://www.cisco.com/en/US/products/sw/cscowork/ps2064/products_quick_start09186a00800e09e2.html

Installation Guide for QoS Policy Manager 3.0

http://www.cisco.com/en/US/products/sw/cscowork/ps2064/products_installation_guide_book09186a00800e09ec.html

Getting Started Guide for QoS Policy Manager 3.0

http://www.cisco.com/en/US/products/sw/cscowork/ps2064/products_getting_started_guide_book09186a00800e09e6.html

User Guide for QoS Policy Manager 3.0

http://www.cisco.com/en/US/products/sw/cscowork/ps2064/products_user_guide_book09186a00800e09f6.html

Documentation Update

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

Ports Configuration for Common Services

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 QPM 3.0 product package.

Downloading and Installing the Patch


Note QoS Policy Manager 3.0 must be installed before you install this patch.


Use the following procedure to download and install the patch.

Procedure

1. Go to the following location on Cisco.com: http://www.cisco.com/cgi-bin/tablebuild.pl/qos-patches

2. Click on QoSPolicyManager-Patch3.0.1.exe to download the patch to your hard drive.

3. If you have QoS Policy Manager windows open, you are recommended to close them.

4. Locate the downloaded file on your hard drive and double-click it. This will start the installation on your system. Before replacing files, the installation will stop all CiscoWorks and QPM services, and will restart them after the installation completes.

New Device Support and QoS Support

QPM 3.0.1 provides the following new device support:

Catalyst 6513, 6503

Catalyst 4503, 4506 with Supervisor II, running CatOS.

Catalyst 3550-12G, 3550-24DC, 3550-24FX

Cisco 1760

xDSL interfaces on Cisco 1760, 2600, and 3600 devices

QPM 3.0.1 provides the following new QoS support:

Class-based QoS on Catalyst 5000 RSM

NBAR on Cisco 7600 and Catalyst 6000 devices running IOS version 12.1(13)E

Note For detailed information about QPM 3.0.1 device and QoS feature support, go to:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/qos/qpm3_0/qpm30dev/qpm301dv.htm

New and Enhanced Features

QPM 3.0.1 provides the following new and enhanced features:

Additional NBAR Protocols

Configuring Queuing on ASIC Interfaces

Additional NBAR Protocols

The following NBAR protocols are now supported in QPM:

RTSP—including the parameters: quicktime, realplayer, url

SAP protocols—SAP-APP, SAP-MSG, SAP-PGM

Configuring Queuing on ASIC Interfaces

This section is relevant for Catalyst 6000 IOS and Cisco 7600 devices.

When you assign an interface that belongs to an ASIC (Application-Specific Integrated Circuit) to a policy group, QPM now assigns only the selected interface, and not all the interfaces controlled by the same ASIC. If you have configured 1P2Q2T or 2Q2T queuing on the assigned ASIC interface, on deployment, the device applies this queuing configuration to all the interfaces on the ASIC.

Similarly, when you remove an ASIC interface assignment from a policy group, only the selected interface is removed. On deployment, any change to the interface's 1P2Q2T or 2Q2T queuing configuration, will be applied by the device to all the ASIC's interfaces.

Resolved Problems

Table 1 describes problems resolved since the last release of QPM.

Table 1 Resolved Problems from the last release of QPM 

Bug ID
Summary
Additional Information

CSCdy44880

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

CSCdx85557

No warning for voice role assignments to ASIC.

No longer relevant. QPM no longer assigns all the interfaces of the ASIC.

See CSCdz46908.

CSCdy12974

Some voice policy groups not displayed in IP Telephony wizard.

All new policy groups will now be displayed. Policy groups that were created in QPM 3.0 using the "Attach Policy Group Template" option in the Policy Group Definition wizard will still not be displayed in the Assignment Summary page, and you should recreate these policy groups.

CSCdy53000

Collector crashes when adding large number of tasks

You can now run tasks for up to 600 interfaces concurrently with one hour polling interval.

CSCdz48019

QPM 3.0 configures outbound policing incorrectly for the 3550.

QPM now configures all current and new policies correctly.

CSCdz45989

QPM 3.0 does not sync ACS device groups correctly.

QPM 3.0 now syncs ACS device groups correctly.

When using ACS device groups, you should sync after adding or importing new devices. For more details, see CSCdz53333.

CSCdz46908

Cat6K ASIC assignment - sometimes not required, but still done.

When you assign an interface for a Catalyst 6000 IOS or Cisco 7600 device with ASIC (Application-Specific Integrated Circuit) interfaces, QPM no longer assigns all the interfaces of the ASIC. However the device will apply the 1P2Q2T/2Q2T queuing definition to all the interfaces controlled by the same ASICs as the assigned interfaces. Similarly, if you choose to remove an interface from a policy group, the 1P2Q2T/2Q2T queuing definition will be removed from all the interfaces of the ASIC.

See Configuring Queuing on ASIC Interfaces for more details.

CSCdz34484

QPM 3.0 cannot configure FastEthernet ISL subinterfaces.

QPM can now configure and deploy to FastEthernet ISL subinterfaces.

CSCdz46833

Importing devices using long DNS may result in "SNMP Error"

There is no longer a problem importing devices with long DNS names. All DNS names can now be resolved.

CSCdy66305

Bandwidth type constraint is too strict

When configuring class-based QoS priority queuing, you can use either absolute values or ratios, irrespective of the units used for bandwidth configurations in other policies.

CSCdy66391

Corrupted filter when defining rules.

New filters will not be corrupted.

To fix QPM 3.0 policies with corrupted filters, select the policy, and open the Filters page in the Policy Definition wizard:

If the filter rules are in the correct order, click Finish.

If the filter rules are not in the correct order, delete all the filter rules and redefine them.

If there are duplicate rules:

For class-based policies, select Class Default in the Filters page, save the policy, then reopen the policy and configure the filter again. If this does not work, try the next solution.

For all other policies, remove the assigned network elements from the policy group. Create a new policy group and reassign the network elements to the new policy group.

CSCdz41287

Class-Map not parsed correctly if it contains a description.

Parsing of class maps and policy maps containing descriptions is now performed correctly.

CSCdz41693

NBAR protocols that have PDLMs should not be constrained by IOS.

NBAR protocols that have a PDLM (Packet Description Language Module) will be available for configuration in QPM for all IOS versions that support NBAR, even if they are not native to that version. If you deploy an NBAR configuration to a device that does not support the configured NBAR protocol, the deployment will fail.

CSCdz59260

QPM upload views only one policy map

This problem has been fixed, and QPM can now parse any given string as the ACL name in a match statement.


Known Problems

Table 2 describes problems know to exist in this release.


Note To obtain more information about known problems, access the Cisco Software Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. (You will be prompted to log into Cisco.com.)


Table 2 QPM 3.0.1 Known Problems 

Bug ID
Summary
Explanation

CSCdz53333

Devices aren't added to the correct device group.

When working with ACS device groups, QPM does not correctly identify the ACS device groups, and devices are assigned to the default device group.

Workaround for QPM 3.0.1: After adding or importing devices, synchronize with ACS manually in QPM. Choose Devices->Options->Sync Privileges page, and click the Sync button.

Workaround for QPM 3.0: Define devices in QPM with IP names, not DNS names.

CSCdy79290

Interfaces on Flexwan modules are not detected as VIP interfaces.

Interfaces on VIP modules are detected as type VIP. This includes ATM, Serial or any other interfaces and their subinterfaces. However, when the ATM parent is of type SONET and its subinterface is type AAL5, the parent interface is marked as VIP but the subinterface is not.

CSCdz58091

ATM ima sub-interfaces detected as ATM1/IMA0.1-aal5 layer

Some ATM IMA subinterfaces are detected with a "-aal5 layer" suffix to their name (for example, ATM1/IMA0.1 is detected as "ATM1/IMA0.1-aal5 layer"). Deployment to these subinterfaces will fail, since the device does not recognize the command: "interface ATM1/IMA0.1-aal5 layer".

Workaround: Configure QoS for an ATM VC instead of for the subinterface.