 Feedback
|
Table Of Contents
Readme for CiscoWorks QoS Policy Manager 4.1.5 on Windows
Configuration on Cisco Nexus 7000 Series Switches
Configuration on ME 3400 Series Ethernet Access Switch
Configuration on 7600-ES+4TG3CXL Line Card
Configuration on WS-X6716-10GE Line Card (non-VSS Mode)
Support for Cisco IOS Version 15.x
Hardware and Software Requirements
Downloading and Installing QPM 4.1.5 from Cisco.com
Readme for CiscoWorks QoS Policy Manager 4.1.5 on Windows
This Readme is for CiscoWorks QoS Policy Manager (QPM) 4.1.5 running on Windows platform. It contains the following sections:
•
Support for Cisco IOS Version 15.x
•
Description
QPM 4.1.5 is a maintenance release that enhances the functionality of QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, and QPM 4.1.4 by providing:
•
•
•
QPM 4.1.5 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, or QPM 4.1.4.
Related Documentation
QPM 4.1.5 is a maintenance release after QPM 4.1.4. The most updated documentation for QPM 4.1.5 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/products/sw/cscowork/ps2064/products_user_guide_list.html
Additional Device Support
QPM 4.1.5 not only supports the devices supported in QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, and QPM 4.1.4, but also the following devices:
Table 1 shows the device OIDs and names of the additional devices supported by QPM 4.1.5.
For details regarding the QoS feature support for these devices, see the Supported Devices and Software Releases for QPM 4.1.5 at http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.htmlTable 2 shows the additional line cards supported by QPM 4.1.5 for Cat6k in non-VSS mode.
Table 2 Additional Line Cards Supported by QPM 4.1.5 for Cat6k (non-VSS Mode)
WS-X6716-10GE
1P7Q4T
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.5:
•
•
•
•
Configuration on Cisco Nexus 7000 Series Switches
The following command is used in class-map configuration mode to configure the match criteria for a class map, based on the specified ACL:
match access-group {access-group | nameaccess-group-name}The following command is used in class-map configuration mode to match a packet, based on the Layer 2 CoS marking:
match coscos-value [cos-value cos-value cos-value]The following command is used in class-map configuration mode to configure specific IP DSCP values as the match criteria for a class map:
match dscpdscp-value [dscp-value1 ... dscp-value7]The following command is used to configure IP RTP priority on a device:
ip rtp prioritystart-port port-range bandwidthThe following command is used in class-map configuration mode to configure specific IP precedence values as the match criteria for a class map:
match [ip] precedence{precedence-criteria1|precedence-criteria2 | precedence-criteria3|precedence-criteria4}The following command is used in class-map configuration mode to configure the match criteria for a class map, based on the specified protocol:
match protocolprotocol-nameThe following command is used to set a group ID that can be used later to classify packets:
set qos-groupgroup-idConfiguration on ME 3400 Series Ethernet Access Switch
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-action action [exceed-action action [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-transmit clp |set-mpls-exp-transmitmpls-exp-value | set-cos-transmit value | drop}Configuration on 7600-ES+4TG3CXL Line Card
The following command is used in class-map configuration mode to configure a specific match criterion as the successful match criterion for all packets:
match anyThe following command is used in class-map configuration mode to match a packet, based on the Layer 2 CoS marking:
match coscos-value [cos-value cos-value cos-value]The following command is used in policy-map class configuration mode to set the Layer 2 CoS value of an outgoing packet:
set coscos-valueThe following command is used to set the precedence value in the IP header:
set ip precedencevalueThe following command is used in policy-map class configuration mode to set the MPLS experimental (EXP) field value in the topmost label on either an input or an output interface:
set mpls experimental [topmost]exp-valueThe following
command is used to define the DSCP-to-DSCP-mutation map:
mls qos map dscp-mutationdscp-mutation-name in-dscp to out-dscpThe following command is used in policy-map configuration mode to configure traffic policing ,using the committed information rate:
police [cir] rate bc be conform-action {transmit | set-prec-transmit | set-dscp-transmit | drop} [exceed-action {transmit | set-prec-transmit | set-dscp-transmit | drop}]
[violate-action {transmit | set-prec-transmit | set-dscp-transmit | drop}]The following command is used in policy-map configuration mode to configure the shape rate for average rate traffic shaping:
shape averageshape-rateThe following commands are used to specify the bandwidth allocated for a class that belongs to a policy map:
•
bandwidthbandwidth•
bandwidth percentpercentage•
bandwidth remaining percentpercentageThe following command is used in policy-map configuration mode to configure the Low Latency Queuing (LLQ) bandwidth:
priority bandwidth [burst]The following command is used to specify the maximum number of low-latency or normal priority packets that can be queued before the interface begins dropping packets:
queue-limit queue-limit
The following command is used to configure the WRED and Distributed WRED (DWRED) exponential weight factor for the average queue size calculation:
random-detect exponential-weighting-constantweightConfiguration on WS-X6716-10GE Line Card (non-VSS Mode)
The following command is used to configure the multilayer switching (MLS) QoS port trust state and to classify traffic, based on the CoS value:
mls qos trust cosThe following command is used to configure the MLS QoS port trust state and to classify traffic, based on the DSCP value:
mls qos trust dscpThe following command is used to configure the MLS QoS port trust state and to classify traffic, based on the IP precedence value:
mls qos trust ip precedenceThe following command is used to override the previously configured trust state of the incoming packets and to apply the default port CoS value to all incoming packets:
mls qos cos {default-cos | override}The following commands are used in the class-map configuration mode to configure the match criteria for a class map:
•
match [not] access-groupACLNum•
match [not] ip dscpdscp•
match [not] ip precedenceprecedence•
match [not] coscos•
match [not] ip rtplow_port range•
match [not] protocolprotocol [parametername [value]]•
match [not] mpls experimentalvalue•
match [not] vlanvalue•
match [not] destination-addressdestination-ip-address•
match [not] source-addresssource-ip-address>The following commands are used in policy-map configuration mode to configure traffic policing, using the peak information rate and committed information rate:
•
policepolice-rate [police-bc] [pir pir] [be police-be] conform-action action [exceed-action action [violate-action action]]•
police cir percent [bcconform-burst-in-msec] [pir percent percent] [be peak-burst-in-msec]The following command is used to specify the IP DSCP value of packets within a traffic class:
set ip dscpdscp-valueThe following command is used to set the precedence value in the IP header:
set ip precedencevalueSupport for Cisco IOS Version 15.x
The following IOS versions are newly supported in QPM 4.1.5:
•
•
Cisco IOS 15.x versions are displayed along with the other supported IOS versions for the following device models in the relevant UI pages (such as Device Summary page, Policy View page, Policy Definition wizard, and so on):
•
•
•
•
•
•
•
•
•
•
•
•
•
Ports 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, 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.5 requires that you have installed QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4. All of these applications run on Common Services 3.2 server.
The hardware and software requirements for QPM 4.1.5 are the same as for QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, and QPM 4.1.4.
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
Installing QPM 4.1.5
The following topics describe the download and installation process of QPM 4.1.5:
•
•
Downloading and Installing QPM 4.1.5 from Cisco.com
You can download the QPM 4.1.5 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, or QPM 4.1.4 already installed.
Note
To download the QPM 4.1.5 installer file from Cisco.com:
Step 1
Step 2
Step 3
Step 4
To install QPM 4.1.5 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
Step 2
This extracts a folder called qpm4_1_5_win, which contains an executable file, qpm4_1_5_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
Installing QPM 4.1.5 from DVD
You can use the QPM 4.1.5 DVD to install QPM 4.1.5 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. To do this:
Step 1
Note
Step 2
\QPM_4_1_5_installation\Windows_K9\QPM_4_1_5_K9.exe,
where d is your DVD drive.The Installer window appears.
Step 3
The Welcome window appears.
Step 4
The Software License Agreement window appears.
Step 5
•
Or
•
The System Requirements window appears.
Step 6
The Summary window appears.
Step 7
The Daemons Restart Options window appears.
Step 8
•
Or
•
The Setup Complete window appears.
Step 9
You must restart your computer before you start working with QPM. The QPM services start automatically whenever you start your computer.
Note
Known Problems
Table 3 describes the known problems in QPM 4.1.5.
Table 3 Known Problems in QPM 4.1.5
CSCtk75511
Cannot deploy the policies because of mislabeled interfaces.
This occurs when you:
1.
2.
The Device Summary page appears.
3.
Some of the Packet over SONET (POS) interfaces of the Cisco ASR 1004 router (running on Cisco IOS-XE software) are discovered as pluggable optical module (POM) interfaces. QPM cannot deploy the policies on these interfaces.
Workaround:
None.
CSCtk05106
Real-time graphs are not properly displayed for Cisco GSR IOS-XR devices.
This occurs when you:
1.
The Real-time Monitoring page appears.
2.
QPM displays saw-shaped graphs for the GSR IOS-XR device.
Workaround:
You can use the historical monitoring reports to view the QoS monitoring data.
CSCtk56574
After installing QPM 4.1.5, if you downgrade to QPM 4.1.4 or lower version without uninstalling Common Services 3.2, then device discovery does not work.
This occurs when you:
1.
2.
3.
The devices are not discovered but the device discovery status appears as
In Progressfor these devices.This problem occurs only on Windows platforms.
Workaround:
You can either:
•
or
•
1.
2.
3.
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:
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.
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.
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
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.
CSCth52093
Policy deployment occasionally fails on some of the SSHv2-enabled devices.
This occurs when you:
1.
2.
3.
Although the policy deployment occasionally fails on some of the SSHv2-enabled devices, the deployment job status always appears as
In Progressfor 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 4 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)
