Table Of Contents
Readme for QoS Policy Manager 4.0.2 on Windows
Description
Related Documentation
Device Support
Hardware and Software Requirements
Downloading and Installing QPM 4.0.2
Downloading from Cisco.com
Downloading From Software Center
Installing QPM 4.0.2
Known Problems
Resolved Problems
Readme for QoS Policy Manager 4.0.2 on Windows
This Readme is for Ciscoworks QoS Policy Manager (QPM) 4.0.2 running on a Windows platform. This Readme contains the following sections:
•
Description
•Related Documentation
•Device Support
•Hardware and Software Requirements
•Downloading and Installing QPM 4.0.2
•Known Problems
•Resolved Problems
Description
CiscoWorks QoS Policy Manager 4.0.2 is a maintanence release that enhances the functionality of QoS Policy Manager 4.0 and QoS Policy Manger 4.0.1, by providing:
•Additional device support
•Bug fixes from the previous release
•Updates to Online help based on the bug fixes
QPM 4.0.2 is a cumulative patch release, and you can install it on top of both QPM 4.0 and QPM 4.0.1.
Related Documentation
QPM 4.0.2 is a maintenance release after QPM 4.0.1. The most updated documentation for QPM 4.0 can be found on Cisco.com:
•Supported Devices and Software Releases for QoS Policy Manager 4.0.2
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html
•Installation Guide for CiscoWorks QoS Policy Manager 4.0 on Windows
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/prod_installation_guides_list.html
•Getting Started Guide for CiscoWorks QoS Policy Manager 4.0
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/prod_installation_guides_list.html
•Quick Start Guide for CiscoWorks QoS Policy Manager 4.0.
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/prod_installation_guides_list.html
•Readme for CS 3.0.5 with QoS Policy Manager 4.0.
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/prod_installation_guides_list.html
•User Guide for QoS Policy Manager 4.0
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/products_user_guide_list.html
Device Support
QPM 4.0.2 not only supports the devices supported in QPM 4.0 and QPM 4.0.1, but also the following devices and cards:
•CRS 8-slot Single-shelf and 16-slot Single-shelf, and CRS Multi-shelf
•7200 Series NPE-G2 Engine
•SIP/SPA Module
•Cat4500 Line Card
•Cat6000 Line Card/Module
Table 1 shows the device OIDs and names of the additional devices supported by QPM 4.0.1.
Table 1 Additional Devices Supported by QPM 4.0.2
Cisco System Device
|
Device OID
|
Device Name
|
Supported OS
|
Cisco Carrier Routing System (CRS)
|
1.3.6.1.4.1.9.1.643
|
Cisco CRS-1 8-Slot Single-shelf System
|
3.3, 3.4
|
1.3.6.1.4.1.9.1.613
|
Cisco CRS-1 16-slot Single-shelf System
|
3.3, 3.4
|
1.3.6.1.4.1.9.1.738
|
Cisco CRS-1 16-Slot Line-Card Chassis Route Processor (Multi-shelf System)
|
3.3, 3.4
|
1.3.6.1.4.1.9.1.739
|
Cisco CRS-1 24-Slot Fabric-Card Chassis (Multi-shelf System)
|
3.3, 3.4
|
Cisco 7200 Series
|
1.3.6.1.4.1.9.1.222
|
Cisco 7200VXR NPE-G2 Engine
|
12.4(4)XD
|
For details regarding the QoS feature support for these devices, see the detailed Supported Devices Table for QPM 4.0.2 at http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html
Table 2 shows the QoS scheduling associated with additional cards supported by QPM 4.0.2.
Table 2 Additional Cards Supported by QPM 4.0.2
Card Name
|
Type
|
Supported QoS Output Scheduling
|
WS-4013+
|
Cat4500 Line Card Support
|
4Q1T
|
WS-4013+TS
|
Cat4500 Line Card Support
|
4Q1T
|
WS-4013+10GE
|
Cat4500 Line Card Support
|
4Q1T
|
WS-X6708-10GE-3C
|
Cat6000 Line Card/Module Support
|
1P7Q4T
|
WS-X6708-10GE-3CXL
|
Cat6000 Line Card/Module Support
|
1P7Q4T
|
6582-2PA
|
Cat6000 Line Card/Module Support
|
N/A
|
WS-SUP720-3B
|
Cat6000 Line Card/Module Support
|
1P3Q8T
|
Table 3 shows the new SPAs (Shared Port Adapters) supported by QPM 4.0.2
Table 3 New SPAs Supported by QPM 4.0.2
|
|
SPA Type
|
SPA-2XT3/E3
|
Serial SPA
|
SPA-2XCT3/DS0
|
Serial SPA
|
SPA-8XCHT1/E1
|
Serial SPA
|
SPA-1XTENGE-XFP
|
Ethernet SPA
|
SPA-5X1GE
|
Ethernet SPA
|
SPA-2XOC3-POS
|
POS SPA
|
SPA-4XOC3-POS
|
POS SPA
|
SPA-2XOC3-ATM
|
ATM SPA
|
Hardware and Software Requirements
QoS Policy Manager 4.0.2 requires that you have installed QoS Policy Manager 4.0 or QoS Policy Manager 4.0.1. Both of these applications run on Common Services (CS) 3.0.5 server.
The hardware and software requirements for QPM 4.0.2 are the same as for QPM 4.0 and QPM 4.0.1.
For detailed list of requirements and instructions to install CS 3.0.5 and QPM 4.0 on Windows, see http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_installation_guide_book09186a00807fc56f.html
Downloading and Installing QPM 4.0.2
You can download the QPM 4.0.2 installer file, qpm4_0_2_win.zip, from Cisco.com, or from the Software Center in Common Services (in case of QPM 4.0.1), and install it on a server that has QPM 4.0 or QPM 4.0.1 already installed.
Note You should have a valid Cisco.com username and password to download the installer file.
The following topics describe the download and installation process of QPM 4.0.2:
•Downloading from Cisco.com
•Downloading From Software Center
•Installing QPM 4.0.2
Downloading from Cisco.com
To download the QPM 4.0.2 installer file from Cisco.com:
Step 1 Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/qos-patches.
You should provide your Cisco.com credentials to access this page.
Step 2 Locate the file qpm4_0_2_win.zip from the list of files to be downloaded.
Step 3 Right-click the file, select Save Target As or Save Link As, and specify the location to download the file to your machine.
Downloading From Software Center
If you are installing QPM 4.0.2 on top of QPM 4.0.1, you can also use the Software Updates option in CiscoWorks Common Services Software Center to download the QPM 4.0.2 installer file.
To download the QPM 4.0.2 installer file from Common Services Software Center associated with QPM 4.0.1:
Step 1 Go to the CiscoWorks Home Page associated with QPM 4.0.1, and select Common Services > Software Center > Software Update.
The Software Updates page appears.
Step 2 In the Products Installed table, select CiscoWorks QoS Policy Manager 4.0.1, and click Select Updates.
The CCO and Proxy Server Credentials page appears.
You are prompted to enter your Cisco.com user name and password.
If you have configured proxy settings, you are prompted to enter the Proxy Server User credentials.
You can configure your Proxy Server User credentials from the Proxy Server Setup page. To access the Proxy Server Setup page:
a. Go to the CiscoWorks Homepage and select Common Services > Server > Security > Cisco.com Connection Management > Proxy Server Setup.
The Proxy Server Setup page appears.
b. Enter the required information in the page to configure your Proxy Server settings.
Step 3 Enter the required credentials in the CCO and Proxy Server Credentials page, and click Next.
The Available Images page appears with the available QPM 4.0.2 images for both Solaris and Windows (qpm4_0_2_sol.zip and qpm4_0_2_win.zip).
Step 4 Select qpm4_0_2_win.zip and click Next.
The Destination Location page appears.
Step 5 Enter the location to save the zip file, or browse to the location using the Browse button.
Step 6 Click Next.
The Summary page appears. The Summary window displays a summary of your inputs.
Step 7 Click Finish to confirm the download operations.
The QPM 4.0.2 installer file is downloaded to the location you selected.
Installing QPM 4.0.2
QPM saves the Historical Monitoring data at every hour of the system clock. Therefore, before you install QPM 4.0.2 over QPM 4.0 or QPM 4.0.1, wait till the end of the hour to allow QPM to save the data associated with any Historical Monitoring tasks that are running.
The monitoring tasks will be resumed after you install QPM 4.0.2 and restart the CiscoWorks daemon.
To install QPM 4.0.2 on the machine that has QPM 4.0 or QPM 4.0.1 already installed:
Step 1 Go to the folder where you have downloaded the installer file, qpm4_0_2_win.zip
Step 2 Unzip the file qpm4_0_2_win.zip
This extracts a folder called qpm4_0_2_win.
Step 3 Go to qpm4_0_2_win, which contains the executable file.
Step 4 Launch the installer. Either:
•Double click the executable file, qpm4_0_2_win.exe.
Or
•Select Start > Run, and enter path\qpm4_0_2_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.
Known Problems
Table 4 describes the problems known to exist in QPM 4.0.2.
Table 4 Known Problems in QPM 4.0.2
Bug ID
|
Summary
|
Explanation
|
CSCse99974
|
QPM 4.0 and Common Services 3.0.5 uninstallation is not complete
|
This occurs when you uninstall CS 3.0.5 and QPM 4.0 through Program Files > Cisco QoS Policy Manager > Uninstall Cisco QoS Policy Manager.
After you uninstall, the path Program Files > CiscoWorks > Uninstall CiscoWorks, is not removed.
This results in the following error message when you select Program Files > CiscoWorks > Uninstall CiscoWorks, after the uninstallation:
C:\Program Files\CSCOpx\setup is not accessible. This folder was moved or removed.
Workaround:
None
|
CSCsg91563
|
WRED Precedence-based weight 1 was not deployed into Router 7200
|
This occurs when you:
1. Create a policy in QPM, with 7200 (12.4) as the device constraint.
2. Define the WRED Precedence Based weight as 1 (under its QoS Properties Wizard > Congestion Avoidance page)
3. Deploy this policy on a 7200 (12.4) router.
4. Run the show run command in the device.
The WRED Precedence Based weight of 1 does not appear as deployed on the device.
Workaround:
None
|
CSCsg92053
|
The service-policy output command from QPM is not deployed to the ATM subinterface.
|
This occurs in the following cases:
•When you create a policy in QPM, with 7200 (12.4) as the device constraint, and then deploy the policy on a 7200 (12.4) router, the service-policy output command is not deployed to the ATM3/0.2 sub-interface of the device.
•When you create a policy in QPM, with Cat6509(Cat6000_PFC3) as the device constraint, and then deploy the policy on a Cat6509, the service-policy output command is not deployed to the mls qos vlan-based command in Cat6509.
Workaround:
None
|
CSCsh02823
|
Cannot upload QoS Config for MLS QOS VLAN based in cat6509
|
This occurs when you:
1. Create a policy in Cat 6509 using the device CLI, and configure the mls qos vlan-based command in it.
2. Try to import this policy from the device into QPM by clicking Import QoS (in Provision > Policy Creation > Select Devices for Import page)
A Wait message appears and this message does not refresh. This means, the import is not working.
Workaround:
None
|
CSCsh25085
|
QPM does not display a report on 7200 with POS OC3 interface
|
This occurs when you:
1. Create a policy in QPM, with 7200 as the device constraint.
2. Deploy this policy on a 7200 device with POS OC3 interface.
The deployment is successful, but in the Monitoring section of QPM, the POS interface is not displayed.
Workaround:
None
|
CSCsh64379
|
Uploading Policy Map(Macros) creates duplicate Policy Map entries
|
This occurs when you:
1. Create a three level nested policy using two Policy Maps (created under Provision > Macros > Policy Maps) in QPM
2. Deploy the policy on a device.
3. Import the policy from the device to QPM.
However, QPM displays four Policy Maps (including two duplicate Policy Maps) in the imported policy.
Workaround:
None
|
CSCsi94714
|
OS field in the Managed Devices page is wrong for CRS device
|
This occurs when you add a CRS device (Cisco CRS-1 Carrier Routing System 4-Slot Single Shelf) with the 3.4 OS version, into QPM device inventory.
However, in the Managed Devices page, the OS is displayed as 3.3 corresponding to the CRS device you added.
Workaround:
None
|
CSCsj14285
|
Cisco10008: Threshold deployment fails with configuration errror
|
This occurs when you define a threshold configuration in QPM for monitoring a Cisco 10008 Router.
When you try to deploy this threshold configuration on the device, the deployment fails displaying a configuration error.
This is because the Cisco 10008 device CLI does not accept the CBQoS 64 bit counter defined in the Threshold Configuration page in QPM.
Workaround:
None
|
CSCsj25265
|
Cannot launch Real-time and Historical monitoring for CRS
|
This occurs when you deploy a monitorable policy on a supported CRS device.
When you try to monitor this policy through QPM, you find the policy displayed in the QoS Report Card page.
However, QPM does not launch Real Time charts for this policy, and any Historical Monitoring task that you schedule on the device displays a Collector Error.
Workaround:
None
|
CSCsl02542
|
Cat 4500 (IOS): Threshold Deployment is not working
|
This occurs when you try to deploy the Threshold Sets, which you configured in QPM, on Cat 4500 (IOS). You find that the threshold commands are not being deployed on the device CLI.
This occurs even if the Threshold Deployment job status appears as Completed on the Completed Jobs page.
Workaround:
None
|
CSCsl04423
|
Cat 4500 (IOS): Policy with policing and class-Default class is not discovered
|
This occurs when you:
1. Configure a policy in Cat 4500 (IOS) through the device CLI, using policing and class-default commands
2. Import the policy into QPM.
The policy is not displayed in the QoS Report Card page.
This means that QPM does not discover such a policy imported from Cat 4500 (IOS).
Workaround:
None
|
CSCsl08216
|
Cat4500 (IOS): CLI for qos trust device <cisco-phone> is not generated
|
This occurs when you:
1. Create a policy with Cat 4500 (IOS) as the device constraint.
2. In the QoS Properties Wizard > Congestion Management page, select the scheduling as 4Q1T or Default
3. In the QoS Properties Wizard > Traffic Control Settings page, select Enable Trust for Cisco Phone
4. Assign this policy to an interface, and check the CLI preview.
You find that no CLI is getting displayed for qos trust device <cisco-phone>
Workaround:
None
|
CSCsk92666
|
Threshold deployment fails with configuration errror for WS-C6509-E with 12.2 (33) SXH.
|
This occurs when you configure a Threshold Set in QPM by entering the ClassMapMetrics, and deploy it on a WS-C6509-E running on 12.2 (33) SXH.
The deployment fails, throwing the following error:
Unknown object: cbQosCMPrePolicyPkt64.
Workaround:
None
|
CSCsl00063
|
QPM does not support WRED for CRS
|
This occurs when you configure a policy in QPM, with CRS as the device constraint.
After you define the WRED mappings for the policy in the In/Out Traffic Rule Wizard > Actions >
Congestion Avoidance page, and perform a CLI preview, you find that QPM does not support WRED commands for CRS.
Workaround:
None
|
CSCsl11579
|
WS-C6509-E: IP Telephony does not discover 1P7Q4T card type
|
The IP Telephony Wizard in QPM does not discover the WS-6708-10GE-3CXL and WS-6708-10GE-3C modules, which support 1P7Q4T scheduling, in a WS-C6509-E device.
Workaround:
None
|
CSCsl13386
|
Time-based ACL created under nested policy is not getting imported into QPM
|
This occurs when you:
1. Create a nested policy in the device CLI, with Time-based ACL attached to the nested policy.
2. Import this policy into QPM.
3. Perform a CLI preview of the policy.
The Time-based ACL command is shown in the preview.
4. Go to Macros > Time Based ACL page
The Time-based ACL that you imported does not appear in the table.
After you import such a nested policy with Time-based ACL attached to it, QPM does not support any further import of Time-based ACL commands in a policy.
This means that QPM does not support the import of Time-based ACL created under a nested policy.
Workaround:
None
|
Resolved Problems
Table 5 describes some of the problems resolved since the last release of QPM.
Table 5 Resolved Problems in QPM 4.0.2
BugID
|
Summary
|
Additional Information
|
CSCsg75733
|
The DSCP Value option in the Marking page for Cat 2950 gives unsupported values
|
This problem has been resolved
|
CSCse22947
|
QPM does not support bandwidth percent command for Cat 4000 4Q1T shape
|
This problem has been resolved
|
CSCsh25418
|
The match dscp command is not supported by QPM
|
This problem has been resolved
|
CSCsj14247
|
Cisco10008: Real-time and Historical Monitoring Data is not collected
|
This problem has been resolved
|
CSCsj73761
|
During Selection of WFQ in Output traffic, script error is thrown for MSFC
|
This problem has been resolved
|
CSCsj76593
|
Policy Creation - Filter section should mention Traffic Classification
|
This problem has been resolved
|
CSCsh64101
|
IP Telephony Wizard is not showing interfaces for 3560,3750 & 6500
|
This problem has been resolved
|
CSCse22947
|
QPM does not support bandwidth percent command for Cat4000 4Q1T shape
|
This problem has been resolved
|
CSCsj70456
|
Selecting the SSH option while adding devices throws error on page displayed in Internet Explorer
|
This problem has been resolved
|
CSCsj70462
|
Unable to create policy from template for custom created policy group
|
This problem has been resolved
|
CSCsk62490
|
QPM 4.0.1 failed to import policy due to dbl configuration
|
This problem has been resolved
|
CSCsk90845
|
Cat4500 (IOS): Real time monitoring is not running properly
|
This problem has been resolved
|
CSCsk88488
|
Cat6000: QPM import fails for 'Police' command
|
This problem has been resolved
|
CSCsk94050
|
Port-channel is not recognized on Cat6000
|
This problem has been resolved
|
Feedback
