 Feedback
|
Table Of Contents
Readme for QoS Policy Manager 4.1.4 on Windows
Devices Supported by Auto Device Support Feature
Configuration for Catalyst 2960, 2970
Configuration for Catalyst 3000, 3550, 3750 and 3560-E
Configuration for Cisco ME 3400 Series Ethernet Access Switch
Configuration for Cisco 1900, 2900, 3900 Series Integrated Services Routers
Hardware and Software Requirements
Downloading and Installing QPM 4.1.4
Readme for QoS Policy Manager 4.1.4 on Windows
This Readme is for CiscoWorks QoS Policy Manager (QPM) 4.1.4 running on Windows platform. It contains the following sections:
•
Devices Supported by Auto Device Support Feature
•
•
Description
QPM 4.1.4 is a maintenance release that enhances the functionality of QPM 4.1, QPM 4.1.1, QPM 4.1.2, and QPM 4.1.3 by providing:
•
•
•
QPM 4.1.4 is a patch release, and you can install it on top of QPM 4.1, QPM 4.1.1, QPM 4.1.2, or QPM 4.1.3.
Related Documentation
QPM 4.1.4 is a maintenance release after QPM 4.1.3. The most updated documentation for QPM 4.1.4 and QPM 4.1 can be found on Cisco.com:
•
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html•
•
•
•
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/readme/
CS32RMe.html•
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/user/guide/
qpm41ug.htmlAdditional Device Support
QPM 4.1.4 not only supports the devices supported in QPM 4.1, QPM 4.1.1, QPM 4.1.2, and QPM 4.1.3, but also the following devices:
Table 1 shows the device OIDs and names of the additional devices supported by QPM 4.1.4.
For details regarding the QoS feature support for these devices, see the Supported Devices and Software Releases for QPM 4.1.4 at http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.htmlTable 2 shows the additional Shared Port Adapters (SPAs) supported in QPM 4.1.4.
Table 2 Additional SPAs Supported by QPM 4.1.4
SPA-2X1GE-V2
Ethernet SPA
SPA-5X1GE-V2
Ethernet SPA
Table 3 shows the additional line cards supported by QPM 4.1.4 for Cisco 7600.
Table 3 Additional Line Cards Supported by QPM 4.1.4 for Cisco 7600
7600-ES+4TG3CXL1
—
1 Only partial support is provided for 7600-ES+4TG3CXL in this release.
Devices Supported by Auto Device Support Feature
QPM 4.1.4 has an Auto Device Support feature that is run as part of the device discovery process, when the device discovery fails for a device.
If the device belongs to a device model that is already supported by QPM, the Auto Device Support feature refers to the CISCO-PRODUCTS-MIB file and maps the SysOID of the device to the appropriate device model. After this mapping, the device is discovered in QPM.
This feature works on both Windows and Solaris platforms.
Note the following points while using the Auto Device Support feature:
•
•
•
install_path\CSCOpx\MDC\qpm\config\autodevice
To update the CISCO-PRODUCTS-MIB file:
Step 1
Step 2
Step 3
Step 4
Table 4 shows the devices that are newly supported in QPM 4.1.4 using the Auto Device Support feature.
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:
•
Or
•
The following sections describe the commands that are additionally supported in QPM 4.1.4:
•
•
•
•
Configuration for Catalyst 2960, 2970
When you map DSCP values to an ingress queue, or to a queue and a threshold ID, the following command is used to configure the device:
mls qos srr-queue input dscp-map queuequeue-id {dscp1...dscp8 | threshold threshold-id dscp1...dscp8}When you map DSCP values to an egress queue, or to a queue and a threshold ID, the following command is used to configure the device:
mls qos srr-queue output dscp-map queuequeue-id {dscp1...dscp8 | threshold threshold-id dscp1...dscp8}Configuration for Catalyst 3000, 3550, 3750 and 3560-E
The following
command is used to define a DSCP-to-DSCP-mutation map:
mls qos map dscp-mutationdscp-mutation-name in-dscp to out-dscpThe following command is used to apply a DSCP-to-DSCP-mutation map to a DSCP-trusted port:
mls qos dscp-mutationdscp-mutation-nameThe following command is used to configure the switch to change (rewrite) the DSCP field of an incoming IP packet:
no mls qos rewrite ip dscpConfiguration for Cisco ME 3400 Series Ethernet Access Switch
The following command is used in class-map configuration mode to configure a specific QoS group value as a match criterion:
match qos-groupqos-group-valueThe following command is used in Policy-map Configuration mode to configure traffic policing using the committed information rate and peak information rate:
police cirpolice-rate[police-bc] [pir pir] [be police-be]conform-actionaction[exceed-actionaction [violate-action action]]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-transmitclp |set-mpls-exp-transmitmpls-exp-value | drop}Configuration for Cisco 1900, 2900, 3900 Series Integrated Services Routers
The following command sequence is used to configure CoS, Precedence, DSCP, or DSCP Markdown mapping settings on Cisco 1900, 2900, and 3900 series Integrated Services Routers (ISR):
1.
mls qos map cos-dscpdscp dscp dscp dscp dscp dscp dscp dscp2.
mls qos map dscp-cosdscp dscp dscp dscp dscp dscp dscp dscp to cosFor 1900 and 2900 series ISRs, the following command is used in policy-map configuration mode to configure traffic policing using the committed information rate and peak information rate:
police cirpolice-rate[police-bc] [pir pir] [be police-be]conform-actionaction[exceed-actionaction[violate-actionaction]]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-transmitclp|set-mpls-exp-transmitmpls-exp-value | drop}For 3900 series ISRs, the following command is used in policy-map configuration mode to configure traffic policing using the committed information rate and peak information rate:
police cirpolice-rate[police-bc] [pir pir] [be police-be]conform-actionaction[exceed-actionaction[violate-actionaction]]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-transmitclp|set-mpls-exp-transmitmpls-exp-value | set-mpls-exp-topmost-transmit mpls-exp-topmost-value | set-mpls-exp-imposition-transmit mpls-exp-imposition-value | drop}For 3900 series ISRs, the following command is used in class-map configuration mode to configure a specific QoS group value as a match criterion:
match qos-groupqos-group-valueThe following command is used in class-map configuration mode to configure a specific match criterion as the successful match criterion for all packets:
match anyPorts Used by QPM
QPM on Windows platform uses the following ports, in addition to the ports used by CiscoWorks Common 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, the first and the consecutive ports to be tried when the original port is used by an external application, by editing the configuration file 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.4 requires that you have installed QPM 4.1, QPM 4.1.1, QPM 4.1.2, or QPM 4.1.3. All of these applications run on Common Services 3.2 server.
The hardware and software requirements for QPM 4.1.4 are the same as for QPM 4.1, QPM 4.1.1, QPM 4.1.2, and QPM 4.1.3.
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.4
You can download the QPM 4.1.4 installer file, qpm4_1_4_win.zip, from Cisco.com, and install it on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, or QPM 4.1.3 already installed.
Note
The following topics describe the download and installation process of QPM 4.1.4:
Downloading from Cisco.com
To download the QPM 4.1.4 installer file from Cisco.com:
Step 1
Step 2
Step 3
Step 4
Installing QPM 4.1.4
To install QPM 4.1.4 on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, or QPM 4.1.3 already installed:
Step 1
Step 2
This extracts a folder called qpm4_1_4_win, which contains an executable file, qpm4_1_4_win.exe.
Step 3
Step 4
•
Or
•
where path is the location of the file in your hard drive.
The Installer window appears.
Step 5
The Welcome window appears.
Step 6
The Software License Agreement window appears.
Step 7
•
Or
•
The System Requirements window appears.
Step 8
The Summary window appears with the summary of settings for the installation.
Step 9
The Daemons Restart Options window appears.
Step 10
•
Or
•
The Setup Complete window appears.
Step 11
You must restart the CiscoWorks daemon before you begin to work with QPM. The QPM services start automatically whenever you start your computer.
Note
Known Problems
Table 5 describes the known problems in QPM 4.1.4.
Table 5 Known Problems in QPM 4.1.4
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.
2.
3.
No graphs are displayed for the device interface, when the unit for data flow rate is in packets per second.
Workaround:
Select the Unit for Data Flow rate as bits per second in the Real Time Charts window. In this way, graphs will be displayed for the device interface.
CSCta68469
Dynamic ports and protocols are not unregistered in QPM 4.1.x.
This occurs when you:
1.
2.
3.
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.
2.
3.
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
CSCtc69323
QPM does not allow you to edit the AutoQoS policy templates.
This occurs when you:
1.
2.
An error message appears.
Workaround:
None.
CSCtd18538
No CLI is generated for H-QoS service policy configured on a 7600 series router.
This occurs when you:
1.
2.
No CLI is generated for H-QoS service.
Workaround:
None.
CSCtg92407
QPM generates unwanted ACLs for some HQoS policies.
This occurs when you:
1.
2.
3.
Unwanted ACL CLI commands are generated for HQoS classifications.
Workaround:
None.
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 some time on a low-end Solaris machine.
This is an inconsistent issue and is seen only on Solaris platforms.
Workaround:
Reinstall QPM to fix this issue.
CSCth52093
Policy deployment sometimes fails on some of the SSHv2-enabled devices.
This occurs when you:
1.
2.
3.
Although the Policy deployment sometimes 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 to resolve this issue.
Resolved Problems
Table 6 describes some of the problems resolved since the last release of QPM.
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)
