|
|
This readme contains information about all the new features and QoS support that have been added since QPM 2.1:
QPM 2.1.2 contains new features, and QoS support for additional devices, as well as all the features and support that were included in the QPM 2.1.1 patch.This patch enhances the functionality of QoS Policy Manager 2.1 by providing:
Detailed documentation for QPM 2.1 can be found at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/qos/qpm21/index.htm
The following sections list the requirements for installing the patch and provide installation instructions:
 |
Note This release installs all features in the QPM 2.1.1 patch. |
Use the following procedure to download and install the patch.
1. Go to the following location on Cisco.com: http://www.cisco.com/cgi-bin/tablebuild.pl/qos-patches
2. Click on QoSPolicyManager-Patch2.1.2.exe to download the patch to your hard drive.
3. If you have the Policy Manager or Distribution Manager windows open, you are recommended to close them.
4. Locate the downloaded file on your hard drive and double-click it. This will start the installation on your system. Before replacing files, the installation will stop the Cisco QoS Manager service and will restart it after the installation completes.
QPM 2.1.2 provides support for the following additional devices:
| Device Support Added | First release |
|---|---|
Catalyst 4000 Layer 2 | QPM 2.1.1 |
Catalyst 6000 with PFC2 (running CatOS) | QPM 2.1.1 |
Catalyst 6000 with PFC2 (running IOS) | QPM 2.1.1 |
Catalyst 6000 with no PFC | QPM 2.1.1 |
VG200 | QPM 2.1.1 |
GGSN | QPM 2.1.2 |
Note For detailed information about QPM 2.1.2 device and QoS feature support, go to: | |
QPM 2.1.2 provides the following new features since QPM 2.1:
| New Feature | First Release |
|---|---|
QPM 2.1.1 | |
QPM 2.1.1 | |
QPM 2.1.1 and QPM 2.1.2 | |
QPM 2.1.1 | |
QPM 2.1.1 | |
QPM 2.1.1 | |
QPM 2.1.1 | |
QPM 2.1.2 | |
QPM 2.1.2 | |
QPM 2.1.2 | |
QPM 2.1.2 | |
QPM 2.1.2 | |
QPM 2.1.2 | |
QPM 2.1.2 |
On Catalyst 4000 Layer 2 switches, you can:
Access these features as follows:
1. In the Device Properties dialog box for the switch, click QoS Property.
2. In the displayed Properties of Cat4000 Queuing dialog box, select the Enable Custom CoS Mapping check box.
3. CoS Mapping: For each pair of CoS values, select the queue to which packets with those CoS values will be directed.
4. Default CoS Value: In the Default CoS Value field, select the required value from the dropdown list.
5. Click OK to return to the Device Properties dialog box.
On Catalyst 6000 devices with PFC2, you can create a dual-rate aggregate limiting (policing) rule with a normal rate and an excess rate.
The parameters that can be defined for an aggregate limiting policy (or a cross-interface aggregate limiting policy on a device group) are the same as for the Catalyst 6000 device, with the following additions:
|
Note For Catalyst 6000 PFC2 devices running IOS, the Violate Action cannot be less severe than the Exceed Action. |
|
Note For Catalyst 6000 PFC2 devices running CatOS, if the Excess Rate and Violate Action parameters are used, the Exceed Action will always be Markdown (policed-dscp). |
New voice templates have been added to the IP_Telephony_Template database, and some existing voice templates have been changed, to provide improved support for QoS configuration for IP telephony networks. (Most of these templates were added in QPM 2.1.1. New templates in QPM 2.1.2 are indicated.)
|
Note After you install the patch, you need to make sure that your voice templates are up to date in all relevant databases. To copy the new and updated templates to your databases, open the IP_Telephony_Template database and follow the procedure in Copying All Device Groups in a Database to Other Databases. |
The following new voice templates have been added for ports on Catalyst 6000 switches with a PFC2 card:
|
Note Because the QoS style in this template is VLAN based, you should also use the AccDistPFC2VoiceVLAN template. |
|
Note For more information about the corresponding voice templates for the Catalyst 6000, see the user guide for QoS Policy Manager 2.1, Chapter 9, Configuring QoS for IP Telephony. |
The following new voice templates have been added for ports on Catalyst 6000 Layer 2 switches without a PFC card:
The following new voice template has been added for ports on Catalyst 4000 WS-X4232 with layer 3 capabilities:
The following new templates have been added for high speed point-to-point WAN links on VIP cards. These templates are similar to the corresponding group for non VIP cards, but use Distributed Low Latency Queuing (dLLQ) instead of LLQ.
The following new template has been added for high speed ATM interfaces:
|
Note When you use this template, it is recommended to adjust the TX-ring limit according to the interface rate. See Tx-Ring Limit Adjustment for more details. |
The following new template has been added for router interfaces that support L3 to L2 mapping, and are configured with 802.1q, or ISL:
QoS scheduling properties and CoS to DSCP mapping for Catalyst switches are configured on a device basis, and therefore cannot be included in the QoS templates. These QoS properties are set automatically by QPM when the device is added to the IP Telephony QoS database.
The following properties have been added for the Catalyst 4000 devices:
|
Note For more information about the QPM voice templates, see the user guide for QoS Policy Manager 2.1, Chapter 9, Configuring QoS for IP Telephony. |
This feature enables you to copy device groups from one QPM database to other QPM databases. In addition, if you have the same device group in several databases, you can update the device group once, and then apply your updates in all other databases in which the device group is present.
|
Note In the QPM 2.1.2 patch, new IP telephony templates have been added and some existing templates have been modified. Therefore, after you install the patch, you are recommended to use this feature to make sure that your voice templates are up-to-date in all the relevant databases. |
After you have created a new device group in one database, you can copy the device group (including its name, QoS properties and QoS policies) to other databases. You can also copy updates you have made to an existing device group to the same device group in other databases, as long as the device group has the identical name and constraints (device model, software version, interface type, card type, interfaces/sub-interfaces and QoS property).
|
Note Device groups with policies that use application services or host groups in their filters, cannot be added or updated to other databases. |
1. Right-click on the device group in the tree view pane or select Devices>Device Groups.
2. Select the relevant option, either Add Device Group to Other Databases or Update Device Group In Other Databases. A message is displayed requesting confirmation of this action for each of your existing databases in turn.
3. Click Yes to confirm that you want to add the selected device group to the specified database. Click Yes to All to add the device group to all your databases.
|
Note If you are adding a device group to other databases and a device group with the same name exists in any of the databases, the device group will not be copied to that database and you will receive a message informing you of this. |
|
Note QPM 2.1.2 cannot read databases from previous QPM versions. If any of your target databases is from an older version, you will be prompted to upgrade the database, otherwise the device group will not be added/updated to that database. |
You can copy all the device groups in a database to other databases. All new device groups will be added to other databases as long as no device group with the same name exists in the other databases. Modifications made to device groups will be copied to device groups with the identical name and constraints in other databases.
|
Note Device groups with policies that use application services or host groups in their filters, cannot be added or updated to other databases. |
1. Right-click anywhere in the tree view pane or select Devices>Device Groups.
2. Select the relevant option, either Add All Device Groups To Other Databases or Update All Device Groups In Other Databases. A message is displayed requesting confirmation of this action for each of your existing databases in turn.
3. Click Yes to confirm that you want to add all the device groups to the specified database. Click Yes to All to add all the device groups to all your databases.
When you add/update device groups in other databases, QPM makes a backup copy of each database before it is changed by your action. This backup file is located in the Database directory under the QPM root directory (for example, new_database.epd.bak).
To go back to the previous version of a database, delete the current .epd file and rename the .epd.bak file.
On Catalyst 6000 devices, you can define a single limiting policy, with a single filter, that includes both microflow and aggregate limiting (or cross-interface aggregate limiting for device groups).
The Limiting page of the Policy Wizard provides two columns of fields, one for microflow limiting and one for aggregate limiting. Select the check box(es) at the top of the column(s) to enable the fields, and fill in the values accordingly.
|
Note You can define cross-interface aggregate limiting on device groups by selecting Cross-Int Aggregate in the Limiting Type field. |
You can define a default ACL on a Catalyst 6000 device running CatOS, to be used for traffic that does not match any named ACL on the device. You can color this traffic with a DSCP value, or you can trust it by CoS, DSCP or IP Precedence.
To use this feature:
1. Click the Default ACL button in the Device Properties dialog box.
2. Select the Enable Default ACL check box.
3. Select the action to be performed on the traffic.
4. Click OK to return to the Device Properties dialog box.
QPM now supports the import of CSV or DIF Version 2.0 files from RME.
The Multiprotocol Label Switching (MPLS) experimental value defines the priority for packets as they travel through the MPLS network. The MPLS experimental value does not overwrite the IP precedence value in the IP header. There are eight experimental values (0-7).
You can now filter by MPLS experimental value on devices with IOS versions that support this feature.
To filter by MPLS experimental value:
1. Open the Filter page of the Policy wizard, and select the MPLS tab.
2. Select the MPLS experimental value by which you want to filter.
The discard eligibility (DE) bit in the address field of a frame relay frame is used as a method for prioritizing the discarding of frames in congested frame relay networks. The frame relay DE bit has only one bit and can therefore only have two settings, 0 or 1. If congestion occurs in a frame relay network, frames with the DE bit set at 1 are discarded before frames with the DE bit set at 0. Therefore, important traffic should have the DE bit set at 0 while less important traffic should be forwarded with the DE bit set at 1.
You can now use the frame relay DE bit marking to prioritize frames in a frame relay network on devices with IOS versions that support this feature.The default DE bit setting is 0.
To change the DE Bit setting:
1. In the Policy Wizard, choose DE Bit in the left pane. The DE Bit page opens.
2. In the DE Bit page, select the Set DE Bit check box.
QPM 2.1.2 recognizes routers that are configured as a Gateway General Packet Radio Service (GPRS) Service Node (GGSN). You can map GPRS QoS settings to IP ToS values.
To configure GGSN QoS properties:
1. In the Device Properties dialog box, click GGSN Properties. The GGSN Properties dialog box opens displaying the default mappings.
2. Select the Enable GPRS QoS check box.
3. To change the default settings, select the Delay Class Mapping radio button, and enter ToS values to which the GPRS delay classes should be mapped. The mapped ToS value for a delay class should be greater than the mapped ToS value for the next delay class.
4. To configure the GGSN to set its default QoS values in the response message exactly as requested in the create PDP context request message, select the Default Response Requested radio button.
You can now specify a burst parameter when you define Priority (LLQ) queuing with CBWFQ.
To define an LLQ burst parameter:
1. In the Policy Wizard, choose CBWFQ in the left pane. The Queuing Properties page opens.
2. Select the Queuing Properties check box.
3. Select the Priority check box. The Burst Parameter field appears.
4. Enter a value for the burst (between 32 and 2000000).
On ATM subinterfaces, you can configure the size of the transmit rings (Tx-ring), which are buffer control structures for transmitting packets.
The primary reason to adjust the transmit ring is to reduce latency caused by queueing. When configuring the transmit ring, consider the following:
In other words, the size of the transmit ring needs to be small enough to avoid introducing latency due to queueing, and it needs to be large enough to avoid drops and a resulting impact to TCP-based flows.
|
Note This feature is currently available only for PA-A3 port adapters. |
To configure Tx-ring limit on ATM PVCs that are defined as subinterfaces:
1. In the Interface Properties dialog box, select Class Based QoS in the QoS Property list box. The Tx-ring limit option appears.
2. Click on the plus sign by Tx-ring limit, to expand the Tx-ring limit field.
3. Select the Enable Tx-ring limit check box.
4. In the Tx-ring limit text box, enter a value for the Tx-ring limit between 3 and 6000.
You can now create policies to color traffic with a CoS value, on devices with IOS versions that support this feature.
To color traffic with a CoS value:
1. In the Policy Wizard, choose Coloring in the left pane. The Coloring Properties page opens.
2. Select the Coloring Properties check box.
3. In the Coloring Mechanism list box, select CoS.
4. Choose a CoS value in the CoS list box.
You can export the contents of a database to an XML file. The XML file will be required if you want to import information from QPM 2.x databases into future versions of QPM.
The XML file contains all the device and policy information in the database.
To export a database to an XML file:
1. Choose File > Export Database to XML File. The Export Database to XML File dialog box opens. QPM assigns a default name to the XML file based on the database name.
2. Navigate to the folder in which you want to save the XML file. Change the default name, if required.
3. Click Save. A message appears in the Status bar when the database has been exported to the XML file.
The following problems that existed in QPM 2.1, have been resolved.
| Bug ID | Summary | Additional Information | Resolved in release |
|---|---|---|---|
CSCdu57179 | If the QoS property on a Catalyst 6000 (IOS) device was changed to Do Not Change, QPM only removed the policies on the current interface, and did not remove the policies on the rest of the interfaces in the ASIC group. | QPM now removes all policies on all the interfaces in the ASIC group, if the QoS property is changed to Do Not Change, since the policies are no longer valid. | QPM2.1.1 |
CSCdu36423 | QPM did not recognize PBR coloring policy on a subinterface without FRTS. | You no longer need to configure FRTS on the subinterface or upgrade the IOS software on the device to a version that supports CAR coloring (IOS 12.0 and higher) to work around this problem. | QPM2.1.1 |
CSCdu39495 | FRF bandwidth percentage was calculated according to interface rate and not minCIR. | You can now leave the Minimum Rate field in the Interface Properties dialog box blank if you want to use the default minCIR value. | QPM2.1.1 |
CSCdu39627 | QPM uploaded trust policies on Catalyst 6000(IOS) with Trust CoS, even if the policies specified Trust DSCP or Trust IP Precedence. | None. | QPM2.1.1 |
CSCdu39744 | QPM deployed adjusted rate values for limiting policies on Catalyst 4000-L3 devices | None. | QPM2.1.1 |
CSCdu39761 | Duplicate class-map naming on device groups with FRTS and Class Based QoS. | You can now define policies with different directions on this device group. | QPM2.1.1 |
CSCdu40749 | QPM did not upload dFRF on a 7500 VIP device with 12.1(6)E and CBWFQ. | None. | QPM2.1.1 |
CSCdv29919 | Uploading the device configuration on Catalyst 6000 devices without PFC does not show Trust state. | Uploading the device configuration now works correctly on Catalyst 6000 devices without PFC. | QPM2.1.2 |
CSCdv29924 | Default ACL is not uploaded on Catalyst 6000 devices. | Uploading the device configuration now works correctly on Catalyst 6000 devices. | QPM2.1.2 |
The following problems are known to exist in QPM 2.1.2.
You can track problems using the Cisco bug tracking tool, Bug Navigator II. To access Bug Navigator II, log into Cisco.com and select Service & Support> Technical Support Help—Cisco TAC>Tools>Software Bug Toolkit>
Bug Navigator II, or enter the following URL in your web browser: http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdu72386 | Access Violation error when saving a DB with Cat8K device. | Attempts to save a database that contains a Catalyst 8500 device may be unsuccessful and the policy configurations in that database may be lost. Workaround: Save Catalyst 8500 devices in a separate database. |
CSCdv20264 | Deploy error on Cat6K-IOS/PFC2 DGs with QoS property "Defined by Interface." | If the QoS Property for Catalyst 6000 (IOS) or Catalyst 6000 (PFC2-IOS) device groups is Defined by Interface and you edit a policy and redeploy, the deployment fails. Workaround: Do not use Defined by Interface as the QoS Property for these device groups. |
Posted: Tue Oct 1 16:55:44 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.