Table Of Contents
Release Notes for CiscoWorks QoS Policy Manager 4.0 on Solaris
New Features
QPM and CiscoWorks Common Services
Product Documentation
Related Documentation
Documentation Updates
Co-existence with LMS 2.6
Server and Client Requirements
Known Problems
Resolved Problems
Closed Problems
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for CiscoWorks QoS Policy Manager 4.0 on Solaris
These release notes are for use with the CiscoWorks QoS Policy Manager 4.0, running on a Solaris platform.
These release notes provide:
•
New Features
•QPM and CiscoWorks Common Services
•Product Documentation
•Related Documentation
•Documentation Updates
•Known Problems
•Resolved Problems
•Closed Problems
•Obtaining Documentation, Obtaining Support, and Security Guidelines
New Features
QPM 4.0 contains the following new features and enhancements:
•Significant Platform Upgrades (support for Solaris 8 and 9, and Windows 2003)
•Compatibility with Common Services 3.0.5 and LMS 2.6
•Support for additional devices in the Catalyst series including Cat 2950, 3560, 3750, 4500, and 4900
•Support for the many new devices including Catalyst 2960, ME-2400 and ME-3400, and AS5xxx
•Device synchronization with CiscoWorks Device Credential Repository (DCR)
•Availability of Monitoring Only mode
•Availability of new QoS features (hierarchical QoS or nested policies, PDLM support, VC Bundle support, additional output scheduling support for Catalyst 6000)
•Support for Time-Based ACL to police applications and class maps that are time-of-the-day sensitive
•Set up of traffic compression properties for class-based RTP and TCP IP header
•Support for configuring SRR mappings for Ingress and Egress queues, based on weighed threshold drop (WTD) percentages, buffer values, and class of service (CoS) values
•Defining Traffic Control settings by enabling CoS override and QoS pre classification, and by changing the Maximum Reserved Bandwidth
•Monitoring of devices for threshold violations, by generating events when low or high threshold values are crossed.
See the complete list of supported devices and QoS features for QPM 4.0 under the following URL:
http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html
QPM and CiscoWorks Common Services
CiscoWorks Qos Policy Manager (QPM) 4.0 runs on the CiscoWorks Common Services (CS) 3.0.5 server, which provides the infrastructure required by QPM to run from the CiscoWorks desktop environment.
Common Services also provides management of user roles and privileges, allowing you to control who gets access to specific tasks in QPM.
QPM 4.0 is packaged as a single DVD, which contains the following:
•Installation files for CiscoWorks Common Services 3.0.5
•Installation files for Common Services DST patch
•Installation files for CiscoWorks QoS Policy Manager 4.0
•Documentation for Common Services 3.0.5, QPM 4.0, and Common Services DST patch.
Product Documentation
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates
Table 1 describes the product documentation that is available.
Related Documentation
Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates
Table 2 describes the related documentation that is available
Documentation Updates
This section provides some additional information, which you can use as updates to the existing QPM 4.0 documentation.
Co-existence with LMS 2.6
QPM 4.0 should be the last application to be installed, if you are planning to install LMS 2.6 and QPM 4.0 on the same server. QPM 4.0 can co-exist with other LMS applications only if it is installed in this manner.
Server and Client Requirements
We have updated the server and client requirements for QPM 4.0 in the Installation Guides and the Quick Start Guide for QPM 4.0, available at http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
prod_installation_guides_list.html. Please refer it before you proceed with the installation of Common Services 3.0.5 and QPM 4.0.
Known Problems
Table 3 describes the problems known to exist in QPM 4.0.
Table 3 Known Problems in QPM 4.0
Bug ID
|
Summary
|
Explanation
|
CSCsa27471
|
After you modify the IP Alias, QPM shows an incorrect Policy Configuration status while deploying policies
|
This occurs when you:
1. Modify an IP Alias from Provision > Macros > IP Aliases.
2. Select Provision > Policy Deployment > Create Job > Device Selection and Preview page
You see that the Policy Configuration status of a device, defined through the IP alias that you just modified, displays no changes
Workaround:
In the Provision > Policy Deployment > Create Job > Device Selection and Preview page, select the device and continue deployment, even if the changed IP Alias status is not displayed.
|
CSCse99781
|
Debug message should be removed from QPM install log
|
After you install QPM 4.0, you see the debug messages in the installation log file. These messages should have been automatically removed after installation.
Workaround:
None
|
CSCse37016
|
QPM applies multiple access-group statements without warnings or errors
|
This occurs when you:
1. Create a policy in QPM with Cat3550 as the device model.
2. Configure a Traffic Rule for that policy by defining the Single ACL Translation rule setting (in the In/Out Traffic Rules Wizard > Filter page)
3. Create multiple rules (access class statements) under one Single ACL Translation name.
QPM does not show any error or warning message.
However, Cat3550 allows only one ACL per class map and only one match class-map configuration command per class map, and this is taken care by QPM in the background.
This means, only after deploying the above policy you will get to know that the multiple access class statements are not saved.
Workaround:
While working with policies with Cat3550 as the device model in QPM, create only one rule (access class statement) under one Single ACL Translation name.
|
CSCsf08999
|
QPM 4.0 uninstallation displays error messages
|
When you uninstall QPM 4.0, QPM displays an error message stating that it failed to remove the configuration from Apache server.
Workaround:
None
|
CSCsf20243
|
QPM inserts incorrect values for IP rtp priority bandwidth
|
This occurs when you:
1. Create a policy in QPM, and define its Congestion Management properties (under the Qos Properties Wizard), by selecting a particular scheduling method.
2. In the Congestion Management page, you select both the `Use Priority' and `Limit Bandwidth' options, and enter a value for the percentage of port speed to which the maximum output (bandwidth) should be limited.
3. Deploy the policy on the device.
The deployment may fail because of invalid policy configuration.
This is because the maximum allowed value for the IP rtp priority bandwidth for the device is less than the value you specified in the Congestion Management page.
Workaround:
Make sure that the value you enter for the bandwidth limit percentage, when multiplied by the interface speed, does not exceed the available limit as defined in the device.
|
CSCsf29161
|
QPM does not show the VLAN-Interface association after device rediscovery
|
This occurs when you:
1. Add a device, with VLAN configured on it, into QPM.
2. Go to its Device Properties > VLANs page to see the Interface association with VLANs.
QPM displays correct data.
3. Rediscover the device.
4. Go to its Device Properties > VLANs page to see the Interface association with VLANs.
QPM displays the No Records Found message.
5. Reopen the VLANs page (of the rediscovered device), and click any VLAN name to go to VLAN Properties page. Expand the VLAN Interfaces Association link.
QPM displays the No Interface Associations Found message.
Workaround:
Delete the device from QPM, and add it again.
|
CSCsf32810
|
4Q1T queue setting is not being imported from 4948
|
You create a policy in QPM, with Cat4948(IOS) as the device constraint, and configure the four queues by selecting 4Q1T as the scheduling method. You deploy this policy on a Cat4948 device.
When you import this policy from the device into QPM, you find that the configured values of the queues are not displayed, eventhough the scheduling is set to 4Q1T.
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. Perform the show run command in the device.
You see that the WRED Precedence Based weight of 1 is not 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 two 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, you see that the service-policy output command is not being 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, you see that the service-policy output command is not being deployed to the mls qos vlan-based command in Cat6509.
Workaround:
None
|
CSCsg94437
|
The first polling interval is always 10 minutes for Historical Monitoring task.
|
This occurs when you:
1. Create a Historical Monitoring task in QPM (Monitor > Historical Trends > Create)
2. In the Monitoring Task Wizard > Task Definition page, select the Polling Interval as 5 minutes.
3. After finishing the Monitoring Task Wizard, in the Historical Trends page, select the task and click View Report.
4. In the Report page, select the graph type as Bar.
5. Analyze the graph and check the start time and first poll time of the Historical job.
You see that the first polling interval is 10 minutes, even though you selected
5 minutes as the Polling Interval.
Workaround:
None
|
CSCsh02823
|
Uploading QoS Config for mls qos vlan based in cat6509 is not working.
|
You create a policy in Cat 6509 using the device CLI, and configure the mls qos vlan-based command in it.
When you try to import this policy from the device into QPM by clicking Import QoS (in Provision > Policy Creation > Select Devices for Import page), QPM shows a wait message that never refreshes. This means, the import is not working.
Workaround:
None
|
CSCsh17738
|
Error while importing hierarchical QoS policy into QPM.
|
Using the device CLI, you configure a hierarchical QoS policy with a policy map (say, parent) and a service policy (say, child).
When you import this policy to QPM and perform the policy preview, you see that the service policy called child has been renamed to parent, and the policy map called parent has been renamed to parent_1.
Workaround:
None
|
CSCsh21728
|
QPM does not allow both shape and share (SRR) on the same interface.
|
This occurs when you create a policy in QPM with a device constraint, so that you can configure the transmit 4Q2T queue for SRR scheduling (in QoS Properties Wizard > Congestion Avoidance page).
However, you find that QPM allows either bandwidth shaping or bandwidth sharing, not both, on the four egress queues mapped to the port.
Workaround:
None
|
CSCsh25085
|
In QPM 3.2.3, QPM does not have report on 7200 with POS OC3 interface
|
You create a policy in QPM 3.2.3, with 7200 as the device constraint. You deploy this policy on a 7200 device with POS OC3 interface.
The deployment is successful, but in the report section of QPM you do not see the POS interface.
Workaround:
None
|
CSCsh28885
|
Import is not supported for a few global srr-queue commands.
|
When you import a policy from a device into QPM, the following commands (if present in the device) are not imported:
•set dscp new-dscp
•set ip-precedence new-precedence
•mls qos srr-queue input dscp-map queue queue-id threshold threshold-id dscp1...dscp8
•mls qos srr-queue output dscp-map queue queue-id threshold threshold-id dscp1...dscp8
•mls qos srr-queue input cos-map queue queue-id threshold threshold-id dscp1...dscp8
•mls qos srr-queue output cos-map queue queue-id threshold threshold-id dscp1...dscp8
•mls qos queue-set output qset-id threshold queue-id drop-threshold1 drop-threshold2 reserved-threshold maximum-threshold
Workaround:
None
|
CSCsh34598
|
CS > Server > Reports > Permission Report does not have full data for QPM
|
This occurs when you:
1. Go to CS > Server > Reports > Permission Report.
2. Click Generate Report.
The Permission Report opens.
3. Under the QPM section of the report, you see that it does not have any entry for Threshold.
Workaround:
In QPM, go to Administration > User Permissions Report page to view all the user permissions related to QPM tasks.
|
CSCsh53244
|
Input check for FRTS parameters
|
This occurs when you:
1. Create a policy in QPM, with 7200/ Frame-relay as the device constraint
2. Go to its QoS Properties Wizard > Congestion Avoidance page. Select Class Based QoS as the scheduling method.
3. Enable FRTS, and enter 0 in the Minimum CIR field.
QPM will accept 0 as a value for Frame-relay minimum CIR, but actually the device 7200 does not accept this value. In the device, we can see the range for this input as from 1000 to 45000000.
Workaround:
None
|
CSCsh64101
|
IP Telephony Wizard does not show interfaces for 3560,3750 & 6500
|
In the IP Telephony Wizard in QPM, you are not able to select some interfaces for Cat3560, Cat 3750, and CatOS6500.
Workaround:
We recommend that you use the AutoQoS Wizard in QPM to attach policies to the interfaces in Cat3560, Cat 3750, and CatOS6500.
|
CSCsh71761
|
DCR Error on Device Import in ACS Mode
|
This occurs when you:
1. Configure the network devices (to be used in QPM) in ACS, and confirm the successful authentication through telnet to each device.
2. Change the CS server AAA Mode Setup to TACACS+ and apply to all installed applications.
3. Restart CS.
4. Login to CS as System Administrator in ACS mode.
5. In QPM, import each device manually.
But you find that some of the devices are not getting imported with the status showing DCR Error.
Workaround:
Delete the device, and add it again into QPM.
|
CSCsh72737
|
Daemon Restart is needed after upgrading the evaluation license to base license
|
When you install the QPM 4.0 base license over the evaluation license (after the expiry date of the evaluation license), you find that the QPM GUI works as if the evaluation license is still being applied.
Workaround:
Restart the CiscoWorks daemon after you install the QPM 4.0 base license.
|
CSCsh75911
|
Solaris2.9: Monitoring Graphs are not visible
|
Sometimes, while working with QPM, you find that the Historical Monitoring graphs are not displayed as it used to be.
Workaround:
Restart the CiscoWorks daemon.
|
CSCsh84271
|
Upload is not working after the upgrade from MO to CO license
|
When you upgrade from the QPM 4.0 Monitoring Only license to the Combined license, you see that the import of policies from devices is not working.
Workaround:
Restart the CiscoWorks daemon after you upgrade the license.
|
CSCsh85667
|
Launching QPM after DB import throws HTTP 500 error
|
This occurs when you:
1. Use the import.pl utility in QPM to import the DB (exported from one Solaris server) into a new Solaris server.
2. After successful completion of the DB import, try to launch QPM in the browser.
However, QPM displays the following error:
HTTP Status 500 - Internal Server Error
Workaround:
Restart the CiscoWorks daemon after you finish the import process, and then launch QPM
|
CSCsh89024
|
QPM 4.0 MO: Reinstall throws HTTP 500 error
|
When you try to re-install QPM 4.0 with Monitoring Only license, on a Solaris machine, QPM throws an HTTP500 error during the re-installation.
Workaround:
None
|
CSCsh90881
|
DST Testing: Historical Monitoring task is not collecting any data
|
This problem occurs when you:
1. Install the Common Services DST patch by following the installation sequence for QPM 4.0.
2. Create a Historical Monitoring task in QPM, by scheduling it on a day when the Daylight Saving is in progress.
However, sometimes, QPM fails to finish the monitoring task successfully, and no monitoring graph is displayed.
Workaround:
None
|
CSCsi02048
|
OLH for the section Resetting the Login Module throws HTTP400 Error
|
You go to QPM OLH, and select
Managing Devices > Integrating QPM with Access Control Server > Resetting the Login Module.
But, QPM throws an HTTP400 error for the page.
Workaround:
Click View PDF below the contents displayed under the Contents tab in the OLH, and navigate to the same section in Chapter 4: Managing Devices.
|
Resolved Problems
Table 4 describes the problems resolved since the last release of QPM.
Table 4 Resolved Problems in QPM 4.0
BugID
|
Summary
|
Additional Information
|
CSCdy27282
|
Committed Burst Size and Excess Burst Size (bc/be) must be defined, although optional in 12.2T.
|
This problem has been resolved.
|
CSCsa36476
|
Cannot open exported monitoring data from WINZIP default in Windows XP
|
This problem has been resolved.
|
CSCsa34572
|
Gigabit Interfaces are shown as Ethernet type
|
This problem has been resolved.
|
CSCec02451
|
Only class-default can be defined for nested service policies
|
There was no option in QPM to specify classes while configuring QoS Properties in a hierarchical service policy configuration.
This problem has been resolved.
|
Closed Problems
Table 5 describes the known bugs from QPM 3.2.3 that were closed.
Table 5 Known Bugs Closed in QPM 3.2.3
BugID
|
Summary
|
Additional Information
|
CSCsa55945
|
Policy deployment fails when you enter a user exec prompt name that ends with a hash (#).
|
Not found in QPM 4.0
|
CSCsa61731
|
Cannot deploy aggregate police commands in 3750 Metro
|
Not found in QPM 4.0
|
CSCsa34581
|
Upload creates different policymap for 805 device
|
Not found in QPM 4.0
|
CSCsa35003
|
Inline power should not be supported for Cat4507(IOS)
|
Not found in QPM 4.0
|
CSCdy27332
|
QPM cannot monitor policies on ATM physical interfaces
|
Not found in QPM 4.0
|
CSCin32807
|
Upload QoS configuration in progress for a long time
|
Not found in QPM 4.0
|
CSCuk36160
|
IP Telephony wizard ignores Recommend rules with device roles
|
Not found in QPM 4.0
|
CSCin33600
|
Deployment fails on 7300 when filter contains DSCP or IPP
|
Not found in QPM 4.0
|
CSCec64123
|
You can trigger historical monitoring during backup
|
Not found in QPM 4.0
|
CSCin61630
|
Cannot import devices with SSH config from RME.
|
Not found in QPM 4.0
|
CSCin56487
|
Values missing in In Policy Wizard - Policing page after import
|
Not found in QPM 4.0
|
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
