Guest

CiscoWorks QoS Policy Manager

Readme for QoS Policy Manager 4.1.4 on Solaris

  • Viewing Options

  • PDF (235.9 KB)
  • Feedback
Readme for QoS Policy Manager 4.1.4 on Solaris

Table Of Contents

Readme for QoS Policy Manager 4.1.4 on Solaris

Description

Related Documentation

Additional Device Support

Devices Supported by Auto Device Support Feature

Additional Command Support

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

Ports Used by QPM

Hardware and Software Requirements

Downloading and Installing QPM 4.1.4

Downloading from Cisco.com

Installing QPM 4.1.4

Known Problems

Resolved Problems


Readme for QoS Policy Manager 4.1.4 on Solaris


This Readme is for CiscoWorks QoS Policy Manager (QPM) 4.1.4 running on Solaris platform. It contains the following sections:

Description

Related Documentation

Additional Device Support

Devices Supported by Auto Device Support Feature

Additional Command Support

Ports Used by QPM

Hardware and Software Requirements

Downloading and Installing QPM 4.1.4

Known Problems

Resolved Problems

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:

Additional device support

Additional command support

Bug fixes

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:

Supported Devices and Software Releases for QPM 4.1.4

http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html

Installation Guide for QPM 4.1 on Solaris

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/installation/
guide/solaris/QPM41SOL.html

Getting Started Guide for QPM 4.1

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/
getting_started/guide/qpm41gsg.html

Quick Start Guide for QPM 4.1.

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/quick_start/
guide/qpm41qsg.html

Readme for CS 3.2 with QPM 4.1.

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/readme/
CS32RMe.html

User Guide for QPM 4.1

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/user/guide/
qpm41ug.html

Additional 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.

Table 1 Additional Devices Supported by QPM 4.1.4 

Cisco System Device
Device OID
Device Name
Supported OS

Cisco Catalyst 2960 Series

1.3.6.1.4.1.9.1.1258

Catalyst 2960S-48FPD-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1259

Catalyst 2960S-48LPD-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1260

Catalyst 2960S-48TD-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1261

Catalyst 2960S-24PD-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1262

Catalyst 2960S-24TD-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1263

Catalyst 2960S-48FPS-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1264

Catalyst 2960S-48LPS-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1265

Catalyst 2960S-24PS-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1266

Catalyst 2960S-48TS-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1267

Catalyst 2960S-24TS-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.1208

Catalyst 29xxStack

12.1E, 12.2S

1.3.6.1.4.1.9.1.950

Catalyst 2960-24PC-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.951

Catalyst 2960-24LT-L

12.1E, 12.2S

1.3.6.1.4.1.9.1.952

Catalyst 2960-24PD-8TT-L

12.1E, 12.2S

Catalyst 2960 LAN Lite

1.3.6.1.4.1.9.1.927

Catalyst 2960-48TC-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.928

Catalyst 2960-24TC-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.929

Catalyst 2960-24-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1005

Catalyst 2960-48TT-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1006

Catalyst 2960-8TC-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1146

Catalyst 2960-24LC-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1147

Catalyst 2960-24PC-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1148

Catalyst 2960-48PST-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1256

Catalyst 2960S-48TS-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.1257

Catalyst 2960S-24TS-S

12.1E, 12.2S

Cisco Catalyst 3560 Series

1.3.6.1.4.1.9.1.1226

Catalyst 3560X-24

12.1E, 12.2S

1.3.6.1.4.1.9.1.1227

Catalyst 3560X-48

12.1E, 12.2S

1.3.6.1.4.1.9.1.1228

Catalyst 3560X-24P

12.1E, 12.2S

1.3.6.1.4.1.9.1.1229

Catalyst 3560X-48P

12.1E, 12.2S

Cisco Catalyst 3750 Series

1.3.6.1.4.1.9.1.663

Cisco NME-16ES-1G-P

12.1E, 12.2S

1.3.6.1.4.1.9.1.1222

Catalyst 3750X-24

12.1E, 12.2S

1.3.6.1.4.1.9.1.1223

Catalyst 3750X-48

12.1E, 12.2S

1.3.6.1.4.1.9.1.1224

Catalyst 3750X-24P

12.1E, 12.2S

1.3.6.1.4.1.9.1.1225

Catalyst 3750X-48P

12.1E, 12.2S

Catalyst 6500 Supervisor Engine 32 PISA

1.3.6.1.4.1.9.1.657

Catalyst 6504-E Switch

12.2S

Cisco 3900 Series Integrated Services Router

1.3.6.1.4.1.9.1.1144

Cisco 3945E Integrated Services Router

12.4, 12.4T

1.3.6.1.4.1.9.1.1145

Cisco 3925E Integrated Services Router

12.4, 12.4T


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.html

Table 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 Product ID
SPA Type

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

Card Name
Supported QoS Output Scheduling

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, if 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:

The Auto Device Support feature can discover only the devices that belong to the device models or device families that are already supported by QPM. If a new device from an unsupported model is discovered, an error message will be displayed.

The Auto Device Support feature is limited to the device families that are included in the CISCO-PRODUCTS-MIB file, such as Cisco IOS and IOS-XR devices. CatOS devices are not included in the CISCO-PRODUCTS-MIB file and hence are not supported by this feature.

This feature is not related to the device QoS CLI or MIB support in QPM. You must update the CISCO-PRODUCTS-MIB file located at the following location to discover the new devices that belong to supported device models, when you upgrade to QPM 4.1.4 or higher:

install_path/CSCOpx/MDC/qpm/config/autodevice

To update the CISCO-PRODUCTS-MIB file:


Step 1 Go to http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&mibName=CISCO-PRODUCTS-MIB

Step 2 Click the Download link next to the CISCO-PRODUCT-MIB file to download the latest file.

Step 3 Save the file to your local hard drive.

Step 4 Replace the CISCO-PRODUCTS-MIB file located at install_path/CSCOpx/MDC/qpm/config/autodevice, with the latest CISCO-PRODUCTS-MIB file.


Table 4 shows the devices that are newly supported in QPM 4.1.4 using the Auto Device Support feature.

Table 4 Devices Supported by Auto Device Support Feature 

Device Type
Device Name

800

Cisco802J

Cisco804J

CiscoAp801agn

CiscoAp801gn

Cisco811

Cisco813

Cisco815

820

Cisco827

Cisco826QuadV

860

Cisco860Ap

870

Cisco877M

880

Cisco887Vdsl2

Cisco881G

Cisco IAD881F

Cisco IAD881B

Cisco IAD888F

Cisco IAD888B

Cisco 888 SRST

Cisco880Ap

890

Cisco892

Cisco890Ap

1700

Cisco1710

1800_ISR

Cisco1861

Cisco1801M

Cisco1805

2500

CiscoPro2521

2600

Cisco2610M

Cisco2611M

CiscoCE2636

CiscoFE2636

3200

Cisco3220

Cisco 3200 Series Wireless MIC

Cisco3205WirelessMic

Cisco3202

Cisco3204

3600

CiscoPro3620

CiscoPro3640

CiscoSC3640

Cisco3631Co

3700

Cisco371098HP001

CiscoWsC3750g24ps

3800_ISR

Cisco3845nv

Cisco3825nv

4000

Cisco4224

4700

Cisco ACE-4710-K9

7100

Cisco7140Octt1

Cisco uBR7111

Cisco uBR7111E

Cisco uBR7114

Cisco uBR7114E

Cisco7150Dualfe

Cisco7150Octt1

Cisco7150Dualt3

7200

Cisco uBR7225VXR

7500

Cisco7506

10000

Cisco10400

Cisco uBR10012

AS5300

Cisco AS5350

Cisco AS5350XM

AS5800

Cisco AS5850

ASR1000

Cisco ASR 1002-F

Cat2900

Catalyst2924LREXL

Catalyst2912LREXL

Cat2960

Catalyst 2960-48TC-S

Catalyst 2960-24TC-S

Catalyst 2960-24-S

Catalyst 2960-24-PC

Catalyst 2960-24-LT

Catalyst 2960PD-8TT

Catalyst 2960-48TT-S

Catalyst 2960-8TC-S

Catalyst 2960-48PST-L

Catalyst 2960-24LC-S

Catalyst 2960-24PC-S

Catalyst 2960-48PST-S

Cat3000

CiscoWs3030Del

Cat3560

Catalyst 3560E-12D

Catalyst 3560E-12SD

Catalyst 3560-12PC-S

Catalyst 3560V2-24TSD

Catalyst 3560V2-24TS

Catalyst 3560V2-24PS

Catalyst 3560V2-48TS

Catalyst 3560V2-48PS

Cat3750

Cisco CVA122

Cisco CVA124

Catalyst 3750-24FS

Catalyst3750Ge12SfpDc

Catalyst 3750G-24WS-25

Catalyst 3750G-24WS-50

Catalyst 3750V2-24TS

Catalyst 3750V2-24PS

Catalyst 3750V2-48TS

Catalyst 3750V2-48PS

Cat4000_IOS

Catalyst4000NAM

Cat4500_IOS

Catalyst 4510R-E

Cat6000_PFC1_IOS

Catalyst6500SslSm

Catalyst6500FirewallSm

CiscoCat6000

Cat8500

Catalyst 8515 MSR

GSR_12000

Cisco12004

Cisco12008

IAD2400

Cisco2435Iad8fxs

ME3400

CiscoMe3400g12CsA

CiscoMe3400g12CsD

CiscoMe3400g2csA

Cisco340024FSA

CiscoMe3400eg2csA

CiscoMe3400eg12csM

CiscoMe3400e24tsM

ME6524

CiscoMEC6524gs8s

UGAS5xxx

Cisco AS5200

Cisco AS5300

Cisco AS5800

Cisco AS5350XM

VG200

Cisco VG248

Cisco VG204

Cisco VG202


Additional Command Support

QPM provides a web-based, intuitive user interface to define QoS policies for network devices. It translates these 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:

Choose Provisioning > Policy Management > Policy Preview > Local Preview

Or

Choose Provisioning > Policy Management > Policy Preview > Online Preview.

The following sections describe the commands that are additionally supported in QPM 4.1.4:

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

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 queue queue-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 queue queue-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-mutation dscp-mutation-name in-dscp to out-dscp

The following command is used to apply a DSCP-to-DSCP-mutation map to a DSCP-trusted port:

mls qos dscp-mutation dscp-mutation-name

The following command is used to configure the switch to change (rewrite) the DSCP field of an incoming IP packet:

no mls qos rewrite ip dscp

Configuration 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-group qos-group-value

The following command is used in Policy-map Configuration mode to configure traffic policing using the committed information rate and peak information rate:

police cir police-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-transmit mpls-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-dscp dscp dscp dscp dscp dscp dscp dscp dscp

2. mls qos map dscp-cos dscp dscp dscp dscp dscp dscp dscp dscp to cos

For 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 cir police-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-transmit mpls-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 cir police-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-transmit mpls-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-group qos-group-value

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 any

Ports Used by QPM

QPM on Solaris platform uses the following ports, in addition to the ports used by CiscoWorks Common Services:

51099—JNDI lookup port

51199—JRMP lookup port

51299—Admin page port

43460—Database port

49156—EMS database port

51399—PDP port

61162—SNMP port for RMON traps

57001—RMI port for EMS

57002—RMI port for Collector Services

If the PDP, EMS, and Collector Services ports are 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 ports are used by an external application, by editing the configuration files placed at the following locations:

PDP: CSCOpx/MDC/qpm/config/server/jndi.properties

EMS: CSCOpx/MDC/ems/bin/ems_server.sh

Collector services: CSCOpx/MDC/qpm/bin/services/collector/collector.sh

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 Solaris, see http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.1/installation/guide/
solaris/QPM41SOL.html

Downloading and Installing QPM 4.1.4

You can download the QPM 4.1.4 installer file, qpm4_1_4_sol.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 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.1.4:

Downloading from Cisco.com

Installing QPM 4.1.4

Downloading from Cisco.com

To download the QPM 4.1.4 installer file from Cisco.com:


Step 1 Go to http://www.cisco.com/cisco/software/navigator.html

Step 2 Enter your Cisco.com credentials to access this page.

Step 3 Locate the file, qpm4_1_4_sol.zip from the list of files to be downloaded.

Step 4 Right-click the file, choose Save Target As or Save Link As, and specify the location to download the file to your machine.


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 Login as root.

Step 2 Go to the directory where you have downloaded the installer file, qpm4_1_4_sol.zip, and enter the following command to unzip the file:

# unzip qpm4_1_4_sol.zip -d /target directory

where target directory is the directory where you want to extract the installer file. This creates a directory called qpm4_1_4_sol in the target directory.

Step 3 Enter the following commands:

# cd /target directory/qpm4_1_4_sol

# ./setup.sh

A message appears prompting you to read the license agreement.

Step 4 Press Enter.

The license agreement scrolls up in your display screen.

Step 5 Continue to press Enter at the end of each subsequent screen until the prompt to accept the license agreement appears.

Step 6 Enter either:

y to accept the license and proceed with the installation

Or

n to deny and stop the installation.

The installation proceeds if you have entered y.

You are prompted to confirm whether you need to restart the CiscoWorks daemon after this installation.

Step 7 Enter either:

y to restart the daemon after you finish the installation

Or

n to deny the restart of CiscoWorks daemon (to allow installation of any other CiscoWorks applications).

After the installation is complete, you should restart the CiscoWorks daemon before running QPM 4.1.4 for the first time.


Note The monitoring tasks will be resumed after you install QPM 4.1.4 and restart the CiscoWorks daemon.



Known Problems

Table 5 describes the known problems in QPM 4.1.4.

Table 5 Known Problems in QPM 4.1.4

BugID
Summary
Explanation

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. Choose Monitoring > QoS Monitoring > Real Time.

2. Select a device interface of Catalyst 6000 series device in VSS mode.

3. Click the Show Real Time Chart button.

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. Install Common Services 3.0.5 and QPM 4.0, and move to the HTTPS mode.

2. Upgrade to the QPM 4.1 release and install the QPM 4.1.1 patch.

3. Launch the Common Services application.

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. Install Common Service 3.2 from an install folder that has a hyphen in its name.

2. Install QPM 4.1.

3. Launch QPM from the Common Services home page.

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. Choose Provisioning > Pre-Configuration > Policy Templates.

2. Check the check box next to the AutoQoS policy template that you want to edit, and click Edit.

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. Create a policy with H-QoS service for a 7600 series router.

2. Choose Provisioning > Policy Management > Policy Preview > Local Preview.

No CLI is generated for H-QoS service.

Workaround:

None.

CSCtg92407

QPM generates unwanted ACLs for some HQoS policies.

This occurs when you:

1. Create a CBQoS interface policy with H-QoS service for any device model.

2. Create one or more classifications with DSCP or precedence in the HQoS policy.

3. Choose Provisioning > Policy Management > Policy Preview > Local Preview.

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. Add an SSHv2-enabled device to QPM.

2. Create a policy for the SSHv2-enabled device.

3. Deploy the policy on the SSHv2-enabled device.

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.

Table 6 Resolved Problems in QPM 4.1.4 

BugID
Summary
Additional Information

CSCtd15616

When a CRS device had more than one class in a policy map, only the first class in the policy map was imported to QPM.

This problem has been resolved.

CSCtg07959

Real-time and historical monitoring charts were not displayed for an interface, when a service policy with more than 12 classes was configured on the interface.

This problem has been resolved.

CSCtf08373

Local and Online CLI preview did not work, when DSCP, precedence, or WRED traffic classification was used in the interface-level policy.

This problem has been resolved.

CSCte97005

Real-time and historical monitoring charts were not displayed for Cisco 3800 Series Integrated Services Routers with SNMPV3 credentials.

This problem has been resolved.

CSCtd53912

Could not monitor the Frame Relay interfaces with modular QoS CLI (MQC) configuration.

This problem has been resolved.