Guest

CiscoWorks QoS Policy Manager

Readme for QoS Policy Manager 4.0.3 on Solaris

  • Viewing Options

  • PDF (440.0 KB)
  • Feedback
Readme for QoS Policy Manager 4.0.3 on Solaris

Table Of Contents

Readme for QoS Policy Manager 4.0.3 on Solaris

Description

Related Documentation

Monitoring of Child Policies

Command Support

Device Support

Hardware and Software Requirements

Downloading and Installing QPM 4.0.3

Downloading from Cisco.com

Downloading From Software Center

Installing QPM 4.0.3

Known Problems

Resolved Problems


Readme for QoS Policy Manager 4.0.3 on Solaris


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

Description

Related Documentation

Monitoring of Child Policies

Command Support

Device Support

Hardware and Software Requirements

Downloading and Installing QPM 4.0.3

Known Problems

Resolved Problems

Description

CiscoWorks QoS Policy Manager 4.0.3 is a maintenance release that enhances the functionality of QoS Policy Manager 4.0, QoS Policy Manager 4.0.1, and QoS Policy Manger 4.0.2, by providing:

Support for monitoring of child policies

Additional command support

Additional device support

Bug fixes from the previous release

QPM 4.0.3 is a cumulative patch release, and you can install it on top of QPM 4.0, QPM 4.0.1, or QPM 4.0.2.

Related Documentation

QPM 4.0.3 is a maintenance release after QPM 4.0.2. The most updated documentation for QPM 4.0.3 and QPM 4.0 can be found on Cisco.com:

Supported Devices and Software Releases for QoS Policy Manager 4.0.3

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 Solaris

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

Getting Started Guide for CiscoWorks QoS Policy Manager 4.0

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.0/
getting_started/guide/qpm40gs.html

Quick Start Guide for CiscoWorks QoS Policy Manager 4.0.

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.0/
quick/guide/qpm40qsg.html

Readme for CS 3.0.5 with QoS Policy Manager 4.0.

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.0/
readme/CS305RMe.html

User Guide for QoS Policy Manager 4.0

http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.0
/user/guide/qpm40ug.html

Monitoring of Child Policies

In QPM 4.0.3, you can monitor the child policies if they are attached to the device interface. These child policies are part of hierarchical QoS (or nested QoS) configuration.

The QoS Report Card displays both the parent and child classes on the policy attached to the interface.

QPM also generates the Historical and Real Time monitoring graphs for both the parent policy and the child policies. The parent and the child policies are listed one after the other (not inline), and the graphs for both policies are displayed on the same chart. The Filters and Actions graphs are displayed for the parent and the child policies.

Command Support

QPM 4.0.3 not only supports the commands supported in QPM 4.0 and QPM 4.0.2, but also the following commands:

set-qos-transmit

set-qos-continue

set-clp-transmit

policed-dscp-transmit

set qos-group

Device Support

QPM 4.0.3 not only supports the devices supported in QPM 4.0 and QPM 4.0.2, but also the following devices and cards:

Cat 6500 Virtual Switching Supervisor (VSS)

Cat 6500 Supervisor Engine 32 PISA

HP BladeSystem - CGESM and 3020

Cisco ASR 1000 Series Aggregation Services Router (ASR)

More routers under Cisco 7600 series

Cisco 7600 Series Ethernet Services 20G

Cisco 1-Port Channelized STM-1/OC-3 Shared Port Adapter (SPA) on 7600 router

Table 1 shows the device OIDs and names of the additional devices supported by QPM 4.0.3.

Table 1 Additional Devices Supported by QPM 4.0.3

Cisco System Device
Device OID
Device Name
Supported OS

Catalyst 6500 Virtual Switching Supervisor

1.3.6.1.4.1.9.1.896

Catalyst 6500 Virtual Switching Supervisor 720-10G

12.2S

Catalyst 6500 Supervisor Engine 32 PISA

1.3.6.1.4.1.9.1.283

Catalyst 6500 Supervisor Engine 32 PISA

12.2 Zy2

HP BladeSystem

1.3.6.1.4.1.9.1.748

Cisco Catalyst Blade Switch 3020 for HP

12.2E

1.3.6.1.4.1.11.2.3.7.11.33.3.1.1

Cisco Gigabit Ethernet Switch Module (CGESM) for HP

12.1E, 12.2S

Cisco ASR 1000 Series Aggregation Services Router

1.3.6.1.4.1.9.1.925

ASR 1006

12.2

Cisco 7600

 

Cisco 7600 Series Route Switch Processor 720 (RSP 720)

12.2S

1.3.6.1.4.1.9.1.862

7603-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.863

7606-S

12.1E, 12.2S

1.3.6.1.4.1.9.1.864

7609-S

12.1E, 12.2S


For details regarding the QoS feature support for these devices, see the detailed Supported Devices Table for QPM 4.0.3 at http://www.cisco.com/en/US/products/sw/cscowork/ps2064/
products_device_support_tables_list.html

Table 2 shows the additional cards supported by QPM 4.0.3.

Table 2 Additional Cards Supported by QPM 4.0.3

Card Name
Type

Cisco 7600 Series Ethernet Services 20G

Line Card


Table 3 shows the new SPAs (Shared Port Adapters) supported by QPM 4.0.3

Table 3 New SPAs Supported by QPM 4.0.3

SPA Product ID 1
SPA Type

SPA-1XCHSTM1/OC3

Channelized SPA

1 QPM 4.0.3 supports SPAs on SIP-200, SIP-400, SIP-600, and SIP-800 carrier cards on the supported Cisco devices.


Hardware and Software Requirements

QoS Policy Manager 4.0.3 requires that you have installed QoS Policy Manager 4.0 or QoS Policy Manager 4.0.x. All of these applications run on Common Services (CS) 3.0.5 server.

The hardware and software requirements for QPM 4.0.3 are the same as for QPM 4.0 and QPM 4.0.x.

For detailed list of requirements and instructions to install CS 3.0.5 and QPM 4.0 on Solaris, see http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_qos_policy_manager/4.0/
installation/guide/solaris/qpm40sol.html

Downloading and Installing QPM 4.0.3

You can download the QPM 4.0.3 installer file, qpm4_0_3_sol.zip, from Cisco.com, or from the Software Center in Common Services (in case you are using QPM 4.0.2), and install it on a machine that has QPM 4.0 or QPM 4.0.x 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.1:

Downloading from Cisco.com

Downloading From Software Center

Installing QPM 4.0.3

Downloading from Cisco.com

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


Step 1 Go to http://www.cisco.com/pcgi-bin/tablebuild.pl/qos-patches.

You should enter your Cisco.com credentials to access this page.

Step 2 Locate the file qpm4_0_3_sol.zip from the list of files to be downloaded.

Step 3 Download the file to a location on your machine.


Downloading From Software Center

If you are installing QPM 4.0.3 on top of QPM 4.0.2, you can also use the Software Updates option in CiscoWorks Common Services Software Center to download the QPM 4.0.3 installer file.

To download the QPM 4.0.3 installer file from Common Services Software Center associated with QPM 4.0.2:


Step 1 Go to the CiscoWorks Home Page associated with QPM 4.0.2, 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.2, 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.3 image for Solaris.

Step 4 Select qpm4_0_3_sol.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.3 installer file is downloaded to the location you selected.


Installing QPM 4.0.3

QPM saves the Historical Monitoring data at every hour of the system clock. Therefore, before you install QPM 4.0.3 over QPM 4.0 or QPM 4.0.x, 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.3 and restart the CiscoWorks daemon.

To install QPM 4.0.3 on a machine that has QPM 4.0 or QPM 4.0.x already installed:


Step 1 Login as root.

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

# unzip qpm4_0_3_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_0_3_sol in the target directory.

Step 3 Enter the following commands:

# cd /target directory/qpm4_0_3_sol

# ./setup.sh

A message appears prompting you to read the license agreement.

Step 4 Press Enter and continue to press Enter until the prompt to accept the license agreement ends.

Step 5 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.

A prompt appears asking you to confirm whether you need to restart the CiscoWorks daemon after this installation.

Step 6 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.0.3 for the first time.


Known Problems

Table 4 describes the known problems in QPM 4.0.3.

Table 4 Known Problems in QPM 4.0.3 

Bug ID
Summary
Explanation

CSCso86875

QPM does not reflect 'Australia,Melbourne' DST changes

This occurs when you:

1. Install CS 3.0.5 + QPM 4.0 + QPM 4.0.3

2. Install the CS patch for CSCsm43797

3. Change the time zone to Australia/Melbourne

4. Create a Historical Monitoring task:

For October 5, 2008, you find that:

Historical job scheduled for 1 to 2 AM runs at 1 to 1 AM. (This should be running at 1 to 3 AM)

Historical job scheduled for 2 to 2:59 AM runs at 1 to 1:59 AM. (This should be running at 3 to 3:59 AM)

For April 06, 2009, you find that:

QPM does not reflect any DST changes

Historical job scheduled for 2 to 3 AM runs at 2 to 3 AM. (This should be running at 3 to 4 AM)

Workaround:

None

CSCso39037

Back button in the QPM Error Web Page Dialog is not working

This occurs when you:

1. Go to the Policy Table page

2. Click the entry under the Assigned Network Elements column, corresponding to a policy.

The Assigned Network Elements page appears.

3. Click Add.

The Add Assignment - Web Page Dialog window opens.

4. Select a Filter Source, enter a value to filter, and press Enter on your keyboard.

The QPM Error window appears with the Back and Close buttons.

5. Click Back.

You find that clicking this button has no effect.

Workaround:

To filter items in the Add Assignment - Web Page Dialog window, use the Filter button.

CSCso64989

IP Telephony feature is not supported in QPM 4.0.3 IDU Devices

The IP Telephony feature is not supported in some of the QPM 4.0.3 IDU devices such as CGESM, MCP ASR1006, 7606-S, and 3020.

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

CSCsh75911

Solaris2.9: Monitoring Graphs are not visible

Sometimes, while working with QPM, you find that the Historical Monitoring graphs are not displayed as they were earlier.

Workaround:

Restart the CiscoWorks daemon.

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 error

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 CRS device (Cisco CRS-1 Carrier Routing System 4-Slot Single Shelf).

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

CSCsk92666

Threshold deployment fails with configuration error 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 does not get 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

CSCso32021

7600: QPM does not generate mls qos command for CBQoS policy

Policy deployment with marking in ES20-GE3C of 7609-S fails with the following warning:

Warning (QoS): MLS QoS is disabled, marking/policing will be done after enabling MLS QoS globally. Please change your policy configuration.

Workaround:

None

CSCsq32006

Parent class-default chart not running if HQoS has two class-defaults

When you monitor a device that has a nested policy with two class-default policies, you find that the monitoring chart of the parent class-default policy is not running.

Workaround:

None

CSCsq31988

Monitoring jobs does not get notified if device goes unreachable

This occurs when you:

1. Create a historical monitoring task on a device

2. Change the device SNMP configuration as unreachable while the task is running

3. View the monitoring chart

You find that no notification is provided by QPM even if the device being minitored is unreachable.

The Historical Monitoring task continues in the `Running' state and finishes only at the scheduled finish time. The monitoring chart shows a straight line from the point the device went unreachable.

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

BugID
Summary
Additional Information

CSCsl57007

Cannot select the IOS version 12.2.T while defining device constraints for the 3700 device

This problem has been resolved.

CSCsl15542

NBAR applications are missing from QPM configuration

This problem has been resolved.

CSCsl08216

Cat4500(IOS): CLI for qos trust device cisco-phone is not generated.

This problem has been resolved.

CSCsl83498

QPM 4.0.2 cannot create priority queue policies

This problem has been resolved.

CSCsm75239

Single ACL translation configuration deletes the ACL that was already created

This problem has been resolved.

CSCsl49787

MPLS support for 2800 and 3800 ISR

This problem has been resolved.

CSCso12618

QPM does not enable the max-reserved-bandwidth command for ATM-PVC

This problem has been resolved.

CSCso16768

QPM does not allow configuring the bandwidth remaining percentage command

This problem has been resolved.

CSCso16799

Historical Trends: Cannot see the report if the task is in Collector Error

This problem has been resolved.