Guest

CiscoWorks QoS Policy Manager

Readme for QoS Policy Manager 4.1.6 on Windows

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

Readme for CiscoWorks QoS Policy Manager 4.1.6 on Windows

Description

Related Documentation

Additional Device Support

Additional Command Support

Configuration on Catalyst 2360

Configuration on Catalyst 2360, 2950, and 2960

Configuration on Cisco 2010 Connected Grid Router

Configuration on Cisco 2520 Connected Grid Switch

Configuration on Cisco Nexus 5000 Series Switches

Configuration on Cisco ME 3600X and 3800X Series Carrier Ethernet Switch Routers

Configuration on Catalyst 4500 Supervisor Engine 7E

Ports Used by QPM

Hardware and Software Requirements

Downloading and Installing QPM 4.1.6 from Cisco.com

Device Packages

Device Package Updates

Known Problems

Resolved Problems


Readme for CiscoWorks QoS Policy Manager 4.1.6 on Windows

This Readme is for CiscoWorks QoS Policy Manager (QPM) 4.1.6 running on Windows platform. It contains the following sections:

•Description

•Related Documentation

•Additional Device Support

•Additional Command Support

•Ports Used by QPM

•Hardware and Software Requirements

•Downloading and Installing QPM 4.1.6 from Cisco.com

•Device Packages

•Known Problems

•Resolved Problems

Description

QPM 4.1.6 is a maintenance release that enhances the functionality of QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, QPM 4.1.4, and QPM 4.1.5 by providing:

•Additional device support

•Additional command support

•Bug fixes

QPM 4.1.6 is a patch release, and you can install it on top of QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, QPM 4.1.4, or QPM 4.1.5.

Related Documentation

QPM 4.1.6 is a maintenance release after QPM 4.1.5. The most updated documentation for QPM 4.1.6 and QPM 4.1 can be found on Cisco.com:

•Supported Devices and Software Releases for QPM 4.1.6

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

•Installation Guide for QPM 4.1 on Windows

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/installation/
guide/windows/QPM41WIN.html

•Getting Started Guide for QPM 4.1

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/
getting_started/guide/qpm41gsg.html

•Quick Start Guide for QPM 4.1.

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/quick_start/
guide/qpm41qsg.html

•Readme for CS 3.2 with QPM 4.1.

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/readme/
CS32RMe.html

•User Guide for QPM 4.1.6

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

Additional Device Support

QPM 4.1.6 not only supports the devices supported in QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, QPM 4.1.4, and QPM 4.1.5, but also the following devices:

Table 1 shows the device OIDs and names of the additional devices supported by QPM 4.1.6.

Table 1 Additional Devices Supported by QPM 4.1.6 

Cisco System Device
Device OID
Device Name
Supported OS

ME3600X

1.3.6.1.4.1.9.1.1250

Cisco ME 3600X-24FS-M

12.2S

1.3.6.1.4.1.9.1.1251

Cisco ME 3600X-24TS-M

12.2S

ME3800X

1.3.6.1.4.1.9.1.1252

Cisco ME 3800X-24FSM

12.2S

Cisco Catalyst 2360

1.3.6.1.4.1.9.1.1292

Catalyst 2360-48TD-S

12.1E, 12.2S

Cisco Catalyst 2960 Series

1.3.6.1.4.1.9.1.697

Catalyst 2960G-48TC

12.1E, 12.2S

1.3.6.1.4.1.9.1.717

Catalyst 2960-48TT

12.1E, 12.2S

1.3.6.1.4.1.9.1.1016

Catalyst 2960-48PST-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1208

Catalyst 29xxStack

12.1E, 12.2S

Cisco Catalyst 3750 Series

1.3.6.1.4.1.9.1.656

Catalyst 3750-24FS

12.1E, 12.2S

1.3.6.1.4.1.9.1.688

Catalyst 3750G-12S-SD

12.1E, 12.2S

1.3.6.1.4.1.9.1.778

Catalyst 3750G-24WS-S25

12.1E, 12.2S

1.3.6.1.4.1.9.1.779

Catalyst 3750G-24WS-S50

12.1E, 12.2S

1.3.6.1.4.1.9.1.1022

Catalyst 3750V2-24TS

12.1E, 12.2S

1.3.6.1.4.1.9.1.1023

Catalyst 3750V2-24PS

12.1E, 12.2S

1.3.6.1.4.1.9.1.1026

Catalyst 3750V2-48TS

12.1E, 12.2S

1.3.6.1.4.1.9.1.1027

Catalyst 3750V2-48PS

12.1E, 12.2S

Cisco Catalyst 3560 Series

1.3.6.1.4.1.9.1.930

Catalyst 3560E-12D-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.956

Catalyst 3560E-12SD-E

12.1E, 12.2S

1.3.6.1.4.1.9.1.1015

Catalyst 3560-12PC-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1019

Catalyst 3560V2-24DC

12.1E, 12.2S

1.3.6.1.4.1.9.1.1020

Catalyst 3560V2-24TS

12.1E, 12.2S

1.3.6.1.4.1.9.1.1021

Catalyst 3560V2-24PS

12.1E, 12.2S

1.3.6.1.4.1.9.1.1024

Catalyst 3560V2-48TS

12.1E, 12.2S

1.3.6.1.4.1.9.1.1025

Catalyst 3560V2-48PS

12.1E, 12.2S

Cisco Catalyst 4500 Supervisor Engine 7-E

1.3.6.1.4.1.9.1.1286

Cisco Catalyst 4507R+E Switch

12.1E, 12.2S

Cisco Nexus 5000 Series Switches

1.3.6.1.4.1.9.12.3.1.3.1008

Cisco Nexus 5548P Switch

4.2, 5.0(NX-OS)

Cisco 2000 Series Connected Grid Router

1.3.6.1.4.1.9.1.1253

Cisco 2010 Connected Grid Router

12.0, 12.1, 12.2, 12.1E, 12.2S, 12.2T, 12.3, 12.3T, 12.4, 12.4T,15.0, 15.1

Cisco 2500 Series Connected Grid Switch

1.3.6.1.4.1.9.1.1246

Cisco 2520 Connected Grid Switch

12.2

Cisco ASR90001

1.3.6.1.4.1.9.1.1018

Cisco ASR 9000 Series Aggregation Services Router

4.0.1(IOS-XR)

1 Automatic device support for ASR9k device.


For details regarding the QoS feature support for these devices, see the Supported Devices and Software Releases for QPM 4.1.6 at http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html

Table 2 shows the additional line cards supported by QPM 4.1.6.

Table 2 Additional Line Cards Supported by QPM 4.1.6

Card Name
Supported QoS Output Scheduling

WS-X45-SUP7-E

Class-based and default scheduling

WS-X4748-RJ45V+E

Class-based and default scheduling

WS-X4712-SFP+E

Class-based and default scheduling


Additional Command Support

QPM provides a web-based, intuitive user interface to define QoS policies for network devices. It translates those policies into command line interface (CLI) commands. For more information about policy configuration, see Chapter 8 in CiscoWorks QoS Policy Manager 4.1 User Guide.

When you deploy these QoS policies on the network devices, QPM automatically configures the devices using these commands. You need not manually enter these commands to deploy the QoS policies.

If you want to preview the commands that are used to configure the network devices:

•Choose Provisioning > Policy Management > Policy Preview > Local Preview

Or

•Choose Provisioning > Policy Management > Policy Preview > Online Preview

The following sections describe the commands that are additionally supported in QPM 4.1.6:

•Configuration on Catalyst 2360

•Configuration on Catalyst 2360, 2950, and 2960

•Configuration on Cisco 2010 Connected Grid Router

•Configuration on Cisco 2520 Connected Grid Switch

•Configuration on Cisco Nexus 5000 Series Switches

•Configuration on Cisco ME 3600X and 3800X Series Carrier Ethernet Switch Routers

•Configuration on Catalyst 4500 Supervisor Engine 7E

Configuration on Catalyst 2360

The following command is used to limit the maximum output on a port to a percentage of the port speed:

srr-queue bandwidth limit weight1

The following command is used to enable bandwidth shaping on the four egress queues mapped to a port:

srr-queue bandwidth shape weight1 weight2 weight3 weight4

The following command is used to enable bandwidth sharing on the four egress queues mapped to a port:

srr-queue bandwidth share weight1 weight2 weight3 weight4

The following command is used to enable the egress expedite queue on a Gigabit-capable or a 10/100 Ethernet interface:

priority-queue out

The following command is used to map the CoS values to an egress queue, or to map the CoS values to a queue and to a threshold ID:

mls qos srr-queue output cos-map queue queue-id threshold threshold-id cos1...cos8

The following command is used to assign weighted tail-drop (WTD) threshold percentages to an egress queue:

mls qos queue-set output qset-id threshold queue-id drop-threshold1 drop-threshold2 reserved-threshold maximum-threshold

The following command is used to assign a fixed number of buffers to a queue-set:

mls qos queue-set output qset-id buffers allocation1 ... allocation4

Configuration on Catalyst 2360, 2950, and 2960

The following command sequence is used to configure trust state on Catalyst 2360, 2950, and 2960 series switches with Supervisor IOS:

1. mls qos

2. interface interfacename

3. mls qos

4. mls qos trust {cos | dscp | device cisco-phone}

Configuration on Cisco 2010 Connected Grid Router

The following commands are used in class map configuration mode to define the match criteria for a class map:

•match access-group ACLNum

•match any

•match ip dscp dscp

•match ip precedence precedence

•match cos cos

•match ip rtp low_port range

•match protocol protocol [parametername [value]]

•match class-map classname

•match mpls experimental exp-value

•match qos-group qos-group-value

•match VLAN value

The following commands are used in policy map configuration mode to enable specific QoS features on Cisco 2010 Connected Grid Router (CGR):

•set ip precedence precedence

•set ip dscp dscp

•set cos cos-value

•set fr-de

•set mpls experimental value

•set qos-group qos-group-value

•bandwidth bandwidth

•priority bandwidth [burst]

•queue-limit queue-limit

•random-detect

•shape average shape-rate [shape-bc shape-be]

•shape peak shape-rate [shape-bc shape-be]

•shape adaptive shape-adaptive-rate

•shape fecn-adapt

•police police-rate [police-bc] [pir pir] [be police-be] conform-action action [exceed-action action [violate-action action]]

•police cir percent percent [bc conform-burst-in-msec] [pir percent]
[be peak-burst-in-msec]

where action is:

{transmit | continue | set-prec-transmit precedence | set-dscp-transmit dscp | set-prec-continue precedence | set-dscp-continue dscp | set-qos-transmit qos | set-qos-continue qos | policed-dscp-transmit dscp | set-clp-transmit clp | drop}

•service-policy direction policy-map-name

•ip rtp header-compression [passive]

The following command is used to configure ACLs on Cisco 2010 CGR:

ip access-list extended name

The following command is used to configure NBAR protocol discovery on Cisco 2010 CGR:

ip nbar protocol-discovery

The following commands are used to configure custom queuing policies on Cisco 2010 CGR:

•fair queue number-of-queues

•fair queue queue-limit individual-queue-limit

•max-reserved-bandwidth bandwidth

The following commands are used to configure queuing policies on Cisco 2010 CGR:

•random-detect

•rate-limit output access-group ACLNum rate bc be conform-action set-qos-transmit qos-group-num exceed-action set-qos-transmit qos-group-num

•traffic-shape rate rate [burst]

•tx-ring-limit ring-limit

•no fair-queue

•ip rsvp bandwidth [interface-kbps [single-flow-kbps]]

•ip rtp priority start-port port-range bandwidth

Configuration on Cisco 2520 Connected Grid Switch

The following commands are used in class map configuration mode to define the match criteria for a class map:

•class-map [match all | match any] class-map-name

•match ip dscp dscp

•match ip precedence precedence

•match cos cos

•match qos-group qos-group-value

•match VLAN value

•match access-group ACLNum

The following commands are used in policy map configuration mode to enable specific QoS feature on Cisco 2520 Connected Grid Switch (CGS):

•set cos cos-value

•set qos-group qos-group-value

•priority bandwidth [burst]

•bandwidth bandwidth

•bandwidth percent percent

•bandwidth remaining percent percent

•set ip dscp dscp

•set ip precedence precedence

•queue-limit queue-limit

•shape average shape-rate [shape-bc shape-be]

•police {rate-bps | cir {cir-bps} [burst-bytes] [bc [conform-burst] [pir pir-bps [be peak-burst]]

The following command is used to define aggregate policing policy:

mls qos aggregate-policer aggregate-policer-name rate-bps burst-byte exceed-action
{drop | policed-dscp-transmit}

The following commands are used to create filters for class-based policies:

•access-list access-list-number permit source [source-wildcard]

•ip access-list standard name

The following command is used to specify the maximum reserved bandwidth for an interface:

max-reserved-bandwidth bandwidth

The following command is used to set the TX-ring limit on an interface:

tx-ring-limit ring-limit

Configuration on Cisco Nexus 5000 Series Switches

The following command is used to create or modify a QoS class map:

class-map [type qos] [match-all | match-any] class-map-name

The following command is used to create or modify a queuing class map:

class-map type queuing class_map_name

The following command is used to add a reference to an existing QoS class map in a policy map:

class [type qos] class-map-name

The following command is used to add a reference to an existing queuing class map in a policy map:

class type queuing class-map-name

The following command is used to create or modify a QoS policy map:

policy-map [type qos] qos-policy-map-name

The following command is used to create or modify a queuing policy map:

policy-map type queuing queuing-policy-map-name

The following command is used to attach a policy map to an interface:

service-policy {input | type {qos input | queuing {input | output}}} policy-map-name

The following command is used to attach a policy map to a system policy:

service-policy {input | type {network-qos | qos input | queuing {input | output}}} policy-map-name

The following command is used to assign a CoS value for a traffic class:

set cos cos-value

The following command is used to configure tail drop on both ingress and egress queues:

queue-limit queue-size bytes

The following command is used to configure the bandwidth on both ingress and egress queues:

bandwidth percent percent

The following command is used to configure a specific QoS group value as a match criterion:

match qos-group qos-group-value

The following command is used to assign a priority to a traffic class in a policy map:

priority

Configuration on Cisco ME 3600X and 3800X Series Carrier Ethernet Switch Routers

The following command sequence is used to configure time-of-day QoS policies on Cisco ME 3600X and 3800X series carrier ethernet switch routers:

1. time-range time-range-name

2. Either

a. absolute [start time date] [end time date]

Or

b. periodic [days-of-the-week] hh:mm to [days-of-the-week] hh:mm

The following commands are used to create filters for class-based policies:

•ip access-list extended name

•deny | permit protocol source source-wildcard [{eq src-port | range src-port-from src-port-to}] destination destination-wildcard [{eq dest-port | range dest-port-from dest-port-to}] [precedence precedence] [dscp dscp]

•deny | permit protocol source source-wildcard destination destination-wildcard [precedence precedence] [tos tos] [log | log-input] [time-range time-range-name] [fragments]

The following commands are used to create class-based policies for an interface.

1. Class-based classification

–class-map [match all | match any] classname

–match [not] access-group ACLNum

–match [not] ip dscp dscp

–match [not] ip precedence precedence

–match [not] cos cos

–match VLAN value

2. Marking

–set ip precedence precedence

–set ip dscp dscp

–set cos cos-value

–set mpls experimental {imposition | topmost} value

–set qos-group value

3. Policing

–police rate bc be [pir pir] conform-action action [exceed-action action [violate-action action]]

where action is

{set-cos-transmit | set-dscp-transmit | set-mpls-exp-imposition-transmit | set-mpls-exp-topmost-transmit |set-prec-transmit | set-qos-transmit | transmit | drop}

–police rate burst conform-action action [exceed-action action [violate-action action]]

where action is

{set-cos-transmit | set-dscp-transmit | set-mpls-exp-imposition-transmit | set-mpls-exp-topmost-transmit |set-prec-transmit | set-qos-transmit | transmit | drop}

–police cir police-rate [bc police-bc] [pir pir] [be police-be] conform-action action [exceed-action action [violate-action action]]

where action is

{set-cos-transmit | set-dscp-transmit | set-mpls-exp-imposition-transmit | set-mpls-exp-topmost-transmit |set-prec-transmit | set-qos-transmit | transmit | drop}

4. Shaping

–shape average shape-rate [shape-bc shape-be]

5. Queuing

–bandwidth bandwidth

–bandwidth percent percent

–bandwidth remaining percent percent

–priority bandwidth [burst]

–priority percent percent [burst]

6. Congestion Avoidance

–queue-limit queue-limit

The following command is used to specify the maximum reserved bandwidth for an interface:

max-reserved-bandwidth bandwidth

The following command is used to set the TX-ring limit on an interface:

tx-ring-limit ring-limit

The following commands are used to enable resource reservation protocol (RSVP) on an interface:

•ip rsvp bandwidth [interface-kbps [single-flow-kbps]]

•ip rsvp udp-multicast

The following command is used to change the minimum and maximum packet thresholds for the DSCP value:

random-detect dscp dscp-value min-threshold max-threshold

The following command is used in interface configuration mode to configure the WRED and distributed WRED (DWRED) parameters for a particular IP precedence:

random-detect precedence precedence-value min-threshold max-threshold

The following commands are used to configure queuing policies on an interface:

•fair-queue

•no fair-queue

The following command is used to enable IP RTP priority:

ip rtp priority start-port port-range bandwidth

Configuration on Catalyst 4500 Supervisor Engine 7E

The following command sequence is used to configure time-of-day QoS policies on Catalyst 4500 Supervisor Engine 7E:

1. time-range time-range-name

2. Either

a. absolute [start time date] [end time date]

Or

b. periodic [days-of-the-week] hh:mm to [days-of-the-week] hh:mm

The following commands are used to create filters for class-based policies:

•ip access-list extended name

•deny | permit protocol source source-wildcard [{eq src-port | range src-port-from src-port-to}] destination destination-wildcard [{eq dest-port | range dest-port-from dest-port-to}] [precedence precedence] [dscp dscp]

•deny | permit protocol source source-wildcard destination destination-wildcard [precedence precedence] [tos tos] [log | log-input] [time-range time-range-name] [fragments]

The following commands are used to create class-based policies for an interface.

1. Class-based classification

–class-map [match all | match any] classname

–match [not] access-group ACLNum

–match [not] ip dscp dscp

–match [not] ip precedence precedence

–match [not] cos cos

–match [not] protocol protocol

2. Marking

–set cos cos-value

–set qos-group value

3. Policing

–police rate bc be [pir pir] conform-action action [exceed-action action [violate-action action]]

where action is

{set-cos-transmit | set-dscp-transmit | set-mpls-exp-imposition-transmit | set-mpls-exp-topmost-transmit |set-prec-transmit | set-qos-transmit | transmit | drop}

–police rate burst conform-action action [exceed-action action [violate-action action]]

where action is

{set-cos-transmit | set-dscp-transmit | set-mpls-exp-imposition-transmit | set-mpls-exp-topmost-transmit |set-prec-transmit | set-qos-transmit | transmit | drop}

4. Shaping

–shape average shape-rate [shape-bc shape-be]

5. Queuing

–bandwidth bandwidth

–bandwidth percent percent

–bandwidth remaining percent percent

–priority bandwidth [burst]

–priority percent percent [burst]

6. Congestion Avoidance

–queue-limit queue-limit

The following command is used to configure AutoQoS on Catalyst 4500 Supervisor Engine 7E:

auto qos voip {cisco-phone | trust}

The following commands are used to configure marking policies for a class-default filter:

•switchport priority extend {none | trust}

•switchport priority extend cos cos

Ports Used by QPM

QPM on Windows platform uses the following ports, in addition to the ports used by CiscoWorks Common Services:

•51099—JNDI lookup port

•51199—JRMP lookup port

•51299—Admin page port

•43460—Database port

•49156—EMS database port

•51399—PDP port

•61162—SNMP port for RMON traps

•57001—RMI port for EMS

•57002—RMI port for Collector Services

If the PDP port (port 51399) is already occupied by other processes or applications, QPM will automatically bind to the next available port.

You can configure the maximum number of retries, and the first and the consecutive ports to be tried when the original ports are used by an external application. You can do this by editing the configuration files placed at the following location:

CSCOpx/MDC/qpm/config/server/jndi.properties

For information about the ports used by CiscoWorks Common Services, see Installing and Getting Started With CiscoWorks LAN Management Solution 3.1.

Hardware and Software Requirements

QPM 4.1.6 requires that you have installed QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, QPM 4.1.4, or QPM 4.1.5. All of these applications run on Common Services 3.2 server.

The hardware and software requirements for QPM 4.1.6 are the same as for QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, QPM 4.1.4, and QPM 4.1.5.

For detailed list of requirements and instructions to install CiscoWorks Common Services 3.2 and QPM 4.1 on Windows, see http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/installation/guide/windows/QPM41WIN.html

Downloading and Installing QPM 4.1.6 from Cisco.com

You can download the QPM 4.1.6 installer file, qpm4_1_5_win.zip, from Cisco.com, and install it on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, QPM 4.1.4, or QPM 4.1.5 already installed.

Note You should have a valid Cisco.com username and password to download the installer file.

To download the QPM 4.1.6 installer file from Cisco.com:

Step 1 Go to http://www.cisco.com/cisco/software/navigator.html

Step 2 Enter your Cisco.com credentials to access this page.

Step 3 Locate the file, qpm4_1_6_win.zip from the list of files to be downloaded.

Step 4 Right-click the file, choose Save Target As or Save Link As, and specify the location to download the file to your machine.

To install QPM 4.1.6 on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4 already installed:

Step 1 Go to the folder where you have downloaded the installer file, qpm4_1_6_win.zip.

Step 2 Unzip the file qpm4_1_6_win.zip.

This extracts a folder called qpm4_1_5_win, which contains an executable file, qpm4_1_6_win.exe.

Step 3 Go to qpm4_1_6_win.

Step 4 Launch the installer. Either:

•Double click the executable file, qpm4_1_6_win.exe.

Or

•Choose Start > Run, and enter path\qpm4_1_6_win.exe

where path is the location of the file in your hard drive.

The Installer window appears.

Step 5 Click Install to continue.

The Welcome window appears.

Step 6 Click Next to continue.

The Software License Agreement window appears.

Step 7 Click either:

•Accept to accept the license agreement and proceed with the installation

Or

•Do not Accept to deny and stop the installation.

The System Requirements window appears.

Step 8 Check whether your system meets the requirements and click Next to continue.

The Summary window appears with the summary of settings for the installation.

Step 9 Click Next to continue.

The Daemons Restart Options window appears.

Step 10 Click either:

•Yes to restart the CiscoWorks daemon after this installation

Or

•No to deny restart of CiscoWorks daemon after this installation (to allow installation of any other CiscoWorks applications).

The Setup Complete window appears.

Step 11 Click Finish to complete the installation.

You must restart the CiscoWorks daemon before you begin to work with QPM. The QPM services start automatically whenever you start your computer.

Note The monitoring tasks are resumed after you install QPM 4.1.6 and restart the CiscoWorks daemon.

Device Packages

Cisco's routers and switches are referred to as network devices. Routers and switches must be physically installed in the appropriate chassis and connected to your network (using each specific device's hardware installation guide). A software update that enables QoS Policy Manager to support new features for a particular device is called a device package.

Device Package Updates

QoS Policy Manager provides support for a considerable range of devices by installing device packages. Additional device packages can be added to QoS Policy Manager anytime after the initial product release or installation. When new device packages become available, they are placed on Cisco.com.

Check, http://www.cisco.com/cisco/software/navigator.html, and navigate to Products > Network Management and Automation > Routing and Switching Management > CiscoWorks QoS Policy Manager > CiscoWorks QoS Policy Manager 4.1. Select QoS Policy Manager Device Package Updates and QPM version to ensure that you have the latest device release. You can add or update device packages using Software Center. Software Center is a component of Common Services.

For more information on using Software Center, see User Guide for Common Services 3.x.

Known Problems

Table 3 describes the known problems in QPM 4.1.6.

Table 3 Known Problems in QPM 4.1.6 

BugID
Summary
Explanation

CSCtq63984

ASR 9000 model import and deployment fails.

This problem occurs when you import from ASR 9000 device to QPM.

If you import from ASR device that are configured with matching qos-groups and police commands, it fails.

Workaround:

None

CSCto90685

Micro-flow policing for 2500 CGS model is disabled.

Microflow option is not enabled for 2500 CGS model.

Workaround:

None

CSCto90790

CLIs such as auto qos voip, switchport priority are not supported for SUP7E.

The following CLIs cannot be configured in QPM for SUP7E:

•auto qos voip {cisco-phone}

•auto qos voip {trust}

•switchport priority extend {none | trust}

•switchport priority extend cos cos

•priority

•queue-limit

Workaround:

None

CSCta05484

CLASS-BASED-QOS MIB does not return traffic statistics in packets per second for Catalyst 6000 series devices in VSS mode.

This occurs when you:

1. Select Monitoring > QoS Monitoring > Real Time.

2. Select a device interface of the Catalyst 6000 series device in VSS mode.

3. Click Show Real Time Chart.

No graphs are displayed for the device interface, when the unit for data flow rate is in packets per second.

Workaround:

To display graphs for the device interface, select the Unit for Data Flow rate, as bits per second in the Real Time Charts window.

CSCta68469

Dynamic ports and protocols are not unregistered in QPM 4.1.x.

This occurs when you:

1. Install Common Services 3.0.5 and QPM 4.0, and move to the HTTPS mode.

2. Upgrade to the QPM 4.1 release and install the QPM 4.1.1 patch.

3. Launch the Common Services application.

Two QPM links are displayed in the Common Services home page.

Workaround:

None.

CSCta08532

Cannot launch the QPM Dashboard, if a hyphen is included in the install folder name of the Common Services application.

This occurs when you:

1. Install Common Service 3.2 from an install folder that has a hyphen in its name.

2. Install QPM 4.1.

3. Launch QPM from the Common Services home page.

An HTTP Status 404 error is displayed.

Workaround:

You can directly launch the QPM application by using the URL: http://Server IP Address:1741/qpm/qpm.jsp

CSCth13131

QPM links are sometimes disabled in Solaris platform.

Some of the links in the QPM user interface are disabled, when QPM is left unused for sometime on a low-end Solaris machine.

This is an inconsistent issue and is seen only on Solaris platforms.

Workaround:

Reinstall QPM.

CSCth52093

Policy deployment occasionally fails on some of the SSHv2-enabled devices.

This occurs when you:

1. Add an SSHv2-enabled device to QPM.

2. Create a policy for the SSHv2-enabled device.

3. Deploy the policy on the SSHv2-enabled device.

Although the Policy deployment occasionally fails on some of the SSHv2-enabled devices, the deployment job status always appears as In Progress for these devices.

This problem is caused by the Common Services bug, "CSCsu39222: Could not log into many platforms using the SSHv2 protocol."

Workaround:

The patch for this Common Services bug is available at the following location on Cisco.com:

http://www.cisco.com/cisco/software/navigator.html

Install the Common Services 3.2 patch on the QPM server.


Resolved Problems

Table 4 describes some of the problems resolved since the last release of QPM.

Table 4 Resolved Problems in QPM 4.1.6 

BugID
Summary
Additional Information

CSCtk75511

QPM 4.1.4 discovered POS interface to POM interface.

This problem has been resolved.

CSCtk05106

Real-time reports did not work with ios-xr (GSR).

This problem has been resolved.

CSCtd18538

CLI was not generated for hqosService-policy.

This problem has been resolved.


Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)