Guest

CiscoWorks QoS Policy Manager

Readme for QoS Policy Manager 4.1.5 on Solaris

  • Viewing Options

  • PDF (213.5 KB)
  • Feedback
Readme for CiscoWorks QoS Policy Manager 4.1.5 on Solaris

Table Of Contents

Readme for CiscoWorks QoS Policy Manager 4.1.5 on Solaris

Description

Related Documentation

Additional Device Support

Additional Command Support

Configuration on Cisco Nexus 7000 Series Switches

Configuration on ME 3400 Series Ethernet Access Switch

Configuration on 7600-ES+4TG3CXL Line Card

Configuration on WS-X6716-10GE Line Card (non-VSS mode)

Support for Cisco IOS Version 15.x

Ports Used by QPM

Hardware and Software Requirements

Installing QPM 4.1.5

Downloading and installing from Cisco.com

Installing QPM 4.1.5 from DVD

Known Problems

Resolved Problems


Readme for CiscoWorks QoS Policy Manager 4.1.5 on Solaris


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

Description

Related Documentation

Additional Device Support

Additional Command Support

Support for Cisco IOS Version 15.x

Ports Used by QPM

Hardware and Software Requirements

Installing QPM 4.1.5

Known Problems

Resolved Problems

Description

QPM 4.1.5 is a maintenance release that enhances the functionality of QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, and QPM 4.1.4 by providing:

Additional device support

Additional command support

Bug fixes

QPM 4.1.5 is a patch release, and you can install it on top of QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4.

Related Documentation

QPM 4.1.5 is a maintenance release after QPM 4.1.4. The most updated documentation for QPM 4.1.5 and QPM 4.1 can be found on Cisco.com:

Supported Devices and Software Releases for QPM 4.1.5

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

http://www.cisco.com/en/US/products/sw/cascara/ps2064/products_user_guide_list.html

Additional Device Support

QPM 4.1.5 not only supports the devices supported in QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, and QPM 4.1.4, but also the following devices:

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

Table 1 Additional Devices Supported by QPM 4.1.5 

Cisco System Device
Device OID
Device Name
Supported OS

Cisco ME 3400 Series Ethernet Access Switch

1.3.6.1.4.1.9.1.1008

Cisco ME 3400EG-12CS-M

12.2S

1.3.6.1.4.1.9.1.1009

Cisco ME 3400E-24TS-M

12.2S

Cisco Catalyst 4900 Series Switches

1.3.6.1.4.1.9.1.1178

Cisco Catalyst 4948E Ethernet Switch (WS-C4948E-10GE)

12.2S

Cisco Nexus 7000 Series Switches

1.3.6.1.4.1.9.12.3.1.3.612

Cisco Nexus 7000 10-Slot Switch (N7K-C7010)

4.2


For details regarding the QoS feature support for these devices, see the Supported Devices and Software Releases for QPM 4.1.5 at http://www.cisco.com/en/US/products/sw/cascara/ps2064/
products_device_support_tables_list.html

Table 2 shows the additional line cards supported by QPM 4.1.5 for Cat6k in non-VSS mode.

Table 2 Additional Line Cards Supported by QPM 4.1.5 for Cat6k (non-VSS mode)

Card Name
Supported QoS Output Scheduling

WS-X6716-10GE

1P7Q4T


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

Configuration on Cisco Nexus 7000 Series Switches

Configuration on ME 3400 Series Ethernet Access Switch

Configuration on 7600-ES+4TG3CXL Line Card

Configuration on WS-X6716-10GE Line Card (non-VSS mode)

Configuration on Cisco Nexus 7000 Series Switches

The following command is used in class-map configuration mode to configure the match criteria for a class map, based on the specified ACL:

match access-group {access-group | name access-group-name}

The following command is used in class-map configuration mode to match a packet, based on the Layer 2 CoS marking:

match cos cos-value [cos-value cos-value cos-value]

The following command is used in class-map configuration mode to configure specific IP DSCP values as the match criteria for a class map:

match dscp dscp-value [dscp-value1... dscp-value7]

The following command is used to configure IP RTP priority on a device:

ip rtp priority start-port port-range bandwidth

The following command is used in class-map configuration mode to configure specific IP precedence values, as the match criteria for a class map:

match [ip] precedence {precedence-criteria1 | precedence-criteria2 | precedence-criteria3 | precedence-criteria4}

The following command is used in class-map configuration mode to configure the match criteria for a class map, based on the specified protocol:

match protocol protocol-name

The following command is used to set a group ID that can be used later to classify packets:

set qos-group group-id

Configuration on ME 3400 Series Ethernet Access Switch

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-cos-transmit value | drop}

Configuration on 7600-ES+4TG3CXL Line Card

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

The following command is used in class-map configuration mode to match a packet, based on the Layer 2 CoS marking:

match cos cos-value [cos-value cos-value cos-value]

The following command is used in policy-map class configuration mode to set the Layer 2 CoS value of an outgoing packet:

set cos cos-value

The following command is used to set the precedence value in the IP header:

set ip precedence value

The following command is used in policy-map class configuration mode to set the MPLS experimental (EXP) field value in the topmost label on either an input or an output interface:

set mpls experimental [topmost] exp-value

The following command is used to define the DSCP-to-DSCP-mutation map:

mls qos map dscp-mutation dscp-mutation-name in-dscp to out-dscp

The following command is used in policy-map configuration mode to configure traffic policing ,using the committed information rate:

police [cir] rate bc be conform-action {transmit | set-prec-transmit | set-dscp-transmit | drop} [exceed-action {transmit | set-prec-transmit | set-dscp-transmit | drop}]
[violate-action {transmit | set-prec-transmit | set-dscp-transmit | drop}]

The following command is used in policy-map configuration mode to configure the shape rate for average rate traffic shaping:

shape average shape-rate

The following commands are used to specify the bandwidth allocated for a class that belongs to a policy map:

bandwidth bandwidth

bandwidth percent percentage

bandwidth remaining percent percentage

The following command is used in policy-map configuration mode to configure the Low Latency Queuing (LLQ) bandwidth:

priority bandwidth [burst]

The following command is used to specify the maximum number of low-latency or normal priority packets that can be queued before the interface begins dropping packets:

queue-limit queue-limit

The following command is used to configure the WRED and Distributed WRED (DWRED) exponential weight factor for the average queue size calculation:

random-detect exponential-weighting-constant weight

Configuration on WS-X6716-10GE Line Card (non-VSS mode)

The following command is used to configure the multilayer switching (MLS) QoS port trust state and to classify traffic, based on the CoS value:

mls qos trust cos

The following command is used to configure the MLS QoS port trust state and to classify traffic, based on the DSCP value:

mls qos trust dscp

The following command is used to configure the MLS QoS port trust state and to classify traffic, based on the IP precedence value:

mls qos trust ip precedence

The following command is used to override the previously configured trust state of the incoming packets and to apply the default port CoS value to all incoming packets:

mls qos cos {default-cos | override}

The following commands are used in the class-map configuration mode to configure the match criteria for a class map:

match [not] access-group ACLNum

match [not] ip dscp dscp

match [not] ip precedence precedence

match [not] cos cos

match [not] ip rtp low_port range

match [not] protocol protocol [parametername [value]]

match [not] mpls experimental value

match [not] vlan value

match [not] destination-address destination-ip-address

match [not] source-address source-ip-address>

The following commands are used in policy-map configuration mode to configure traffic policing, using the peak information rate and committed information rate:

police police-rate [police-bc] [pir pir] [be police-be] conform-action action [exceed-action action [violate-action action]]

police cir percent [bc conform-burst-in-msec] [pir percent percent] [be peak-burst-in-msec]

The following command is used to specify the IP DSCP value of packets within a traffic class:

set ip dscp dscp-value

The following command is used to set the precedence value in the IP header:

set ip precedence value

Support for Cisco IOS Version 15.x

The following IOS versions are newly supported in QPM 4.1.5:

Cisco IOS version 15.0

Cisco IOS version 15.1

Cisco IOS 15.x versions are displayed along with the other supported IOS versions for the following device models in the relevant UI pages (such as Device Summary page, Policy View page, Policy Definition wizard, and so on):

Cisco 800 Series Routers

Cisco 850 Series Routers

Cisco 860 Series Routers

Cisco 870 Series Routers

Cisco 880 Series Routers

Cisco 890 Series Routers

Cisco 1900 Series Integrated Services Routers

Cisco 2600 Series Routers

Cisco 2800 Series Integrated Services Routers

Cisco 2900 Series Integrated Services Routers

Cisco 3800 Series Integrated Services Routers

Cisco 3900 Series Integrated Services Routers

Cisco 7200 Series Routers

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, and the first and the consecutive ports to be tried when the original ports are used by an external application. You can do this 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.5 requires that you have installed QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4. All of these applications run on Common Services 3.2 server.

The hardware and software requirements for QPM 4.1.5 are the same as for QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, and QPM 4.1.4.

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

Installing QPM 4.1.5

The following topics describe the download and installation process of QPM 4.1.5:

Downloading and installing from Cisco.com

Installing QPM 4.1.5 from DVD

Downloading and installing from Cisco.com

You can download the QPM 4.1.5 installer file, qpm4_1_5_sol.zip, from Cisco.com, and install it on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4 already installed.


Note You should have a valid Cisco.com username and password to download the installer file.


To download the QPM 4.1.5 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_5_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.


To install QPM 4.1.5 on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4 already installed:


Step 1 Login as root.

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

# unzip qpm4_1_5_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_5_sol in the target directory.

Step 3 Enter the following commands:

# cd /target directory/qpm4_1_5_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 CiscoWorks 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.5 for the first time.


Note The monitoring tasks are resumed after you install QPM 4.1.5 and restart the CiscoWorks daemon.



Installing QPM 4.1.5 from DVD

You can use the QPM 4.1.5 DVD to install QPM 4.1.5 on a machine that has QPM 4.1, QPM 4.1.1, QPM 4.1.2, QPM 4.1.3, or QPM 4.1.4 already installed. To do this:


Step 1 Go to the root directory and mount the QPM 4.1.5 DVD on the CiscoWorks Common Services server.


Note We recommend that you do not install QPM from a network DVD drive.


Step 2 Enter the following commands at the prompt:

# cd /dvd/qpm4_1_5/QPM_4_1_5_installation/Solaris_K9

# ./setup.sh

where dvd is the mount point for your DVD drive.

A message appears prompting you to read the license agreement.

Step 3 Press Enter.

The license agreement scrolls up in your display screen.

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

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.

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

Step 6 Enter either:

y to restart the CiscoWorks daemon after you finish the installation

Or

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

Step 7 Unmount the DVD after installation is complete.

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


Known Problems

Table 3 describes the known problems in QPM 4.1.5.

Table 3 Known Problems in QPM 4.1.5 

BugID
Summary
Explanation

CSCtk75511

Cannot deploy the policies because of mislabeled interfaces.

This occurs when you:

1. Install QPM 4.1.4 on Windows platform.

2. Choose Devices > Device Management > Device Summary.

The Device Summary page appears.

3. Choose Populate DCR > By Network Discovery.

Some of the Packet over SONET (POS) interfaces of the Cisco ASR 1004 router (running on Cisco IOS-XE software) are discovered as pluggable optical module (POM) interfaces. QPM cannot deploy the policies on these interfaces.

Workaround:

None.

CSCtk05106

Real-time graphs are not properly displayed for Cisco GSR IOS-XR devices.

This occurs when you:

1. Choose Monitoring > Real Time Monitoring.

The Real-time Monitoring page appears.

2. Select the GSR IOS-XR device from the active device group and click Show Real Time Chart.

QPM displays saw-shaped graphs for the GSR IOS-XR device.

Workaround:

You can use the historical monitoring reports to view the QoS monitoring data.

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 the Catalyst 6000 series device in VSS mode.

3. Click Show Real Time Chart.

No graphs are displayed for the device interface, when the unit for data flow rate is in packets per second.

Workaround:

To display graphs for the device interface, select the Unit for Data Flow rate as bits per second in the Real Time Charts window.

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.

An 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

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.

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 sometime 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 occasionally 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 occasionally 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 4 describes some of the problems resolved since the last release of QPM.

Table 4 Resolved Problems in QPM 4.1.5 

BugID
Summary
Additional Information

CSCtc69323

Could not edit the AutoQoS policy templates.

This problem has been resolved.

CSCtg92407

QPM generated unwanted ACLs for some HQoS policies.

This problem has been resolved.

CSCti90537

Could not launch QPM, if text was included in the Host IP of the devices in ACS device group.

This problem has been resolved.

CSCti47254

The exported historical job zip file of HQoS policy was corrupted.

This problem has been resolved.

CSCti50412

DCR device group configurations were lost in QPM 4.1.4, if the display name of the devices in DCR device group was different from the device IP value.

This problem has been resolved.

CSCti01785

Historical monitoring jobs were moved to the Finished state, when CiscoWorks daemon was restarted.

This problem has been resolved.

CSCth95711

Lack of consistency in listing the new QoS Import jobs.

This problem has been resolved.

CSCth30646

Child policy name was reset to null, when a parent policy with multiple rules was edited.

This problem has been resolved.

CSCth95682

QPM did not identify failures of Tenet or SSH sessions because of command authorization problems.

This problem has been resolved.