|
These sections provide a quick reference for QPM menu options, tool bar buttons, and policy action translations:
Menu | Option | Toolbar Button | Description |
---|---|---|---|
File | New>Database |
| Creates a new QoS database. |
File | New>AVVID Database |
| Opens the AVVID database that contains templates for IP telephony QoS configuration. |
File | New>Device | None | Adds a device to the QoS database. |
File | New>Interface | None | Adds an interface for the selected device to the QoS database. To add an interface to an existing device, it is easier to select the device and select Devices>Device>Properties, and click the Detect Interfaces button in the Device Properties window. QPM queries the device for a list of interfaces and displays them in the Detect Interfaces window. You can select the interfaces you want to add from this window. |
File | New>Device Group | None | Creates a device group, which is a grouping of interfaces to which you want to apply the same policies. |
File | New>Policy |
| Creates a new QoS policy for the selected interface, device, or device group. |
File | Open |
| Opens a QoS database. |
File | Save |
| Saves the currently open database without changing its file name. |
File | Save As | None | Saves the currently open database using a different file name. |
File | Description | None | Adds a description to the currently open database. |
File | Close | None | Closes Policy Manager without closing Distribution Manager. |
File | Exit | None | Closes Policy Manager and Distribution Manager. |
Edit | Cut | None | Copies the selected policy to the Windows clipboard and removes it from the interface, device, or device group. |
Edit | Copy | None | Copies the selected policy to the Windows clipboard without removing it from the interface, device, or device group. |
Edit | Paste | None | Pastes the policy in the clipboard to the selected interface, device, or device group if the policy's action is supported on that item. |
Edit | Delete | None | Deletes the selected element in the Policy Manager window. |
View | Tool Bar | None | Displays (when checked) or hides the tool bar, which contains shortcut buttons for some menu commands. |
View | Status Bar | None | Displays (when checked) or hides the status bar tray at the bottom of the main window. |
View | Properties Preview | None | Displays (when checked) or hides the preview pane at the bottom right of the main Policy Manager window. The summary shows details of the selected database, policy, device, device group, or interface. |
View | Device Name | None | Displays (when checked) the device names instead of their IP addresses. |
Devices | Device>New | None | Adds a device to the QoS database, so that you can manage policies on that device through Policy Manager. |
Devices | Device>View Configuration | None | Displays the selected device's settings, including SNMP communities and Cisco IOS software version numbers. |
Devices | Device>Delete | None | Removes the selected device from the QoS database. |
Devices | Device> Find |
| Finds and highlights the specified device in the tree view. |
Devices | Device>Properties | None | Displays the selected device's properties as defined in the QoS database. |
Devices | Interface>New | None | Adds an interface for the selected device to the QoS database. It is easier to have QPM detect the device's interfaces by clicking Detect Interfaces when viewing the device's properties for previously-defined devices (Devices>Device>Properties), or when adding a new device. |
Devices | Interface>Delete | None | Removes the selected interface from the QoS database. |
Devices | Interface>Properties | None | Displays the interface settings for the selected interface. |
Devices | Device Group>New | None | Creates a device group, which is a grouping of interfaces to which you want to apply the same policies. |
Devices | Device Group>Add/Remove Members | None | Adds interfaces to the selected device group, or removes them from the selected device group. |
Devices | Device Group>Delete | None | Deletes the selected device group from the QoS database. |
Device | Device Group>Properties | None | Displays the device group properties for the selected device group. |
Devices | Policy>New QoS Policy |
| Creates a new QoS policy for the selected device, interface or device group. |
Devices | Policy>New Access Control Policy |
| Creates a new Access Control policy for the selected device, interface or device group. |
Devices | Policy>Disable Policy>Enable | None | Disables the selected policy without deleting it from the database, or enables the selected policy, depending on the status of the policy. However, the policy is not disabled or enabled on the device until you save and distribute the database. |
Devices | Policy>Delete | None | Deletes the selected policy from the database. However, the policy is not deleted from the device until you save and distribute the database. |
Devices | Policy>Properties | None | Displays the selected policy's properties. |
Devices | Import | None | Imports devices from an inventory list exported from Cisco Resource Manager (CRM) or CiscoWorks2000 Resource Manager Essentials. |
Tools | Distribution Manager |
| Starts the Distribution Manager application, which you use to distribute policies to network devices. |
Tools | Reports>All Policies | None | Displays a report of all the policies defined in the open database. |
Tools | Reports>Device Policies | None | Displays a report of the policies defined for the selected device. |
Tools | Reports>Interface Policies | None | Displays a report of the policies defined for the selected interface. |
Tools | Reports>Device Group Policies | None | Displays a report of the policies defined for the selected device group. |
Tools | Reports>Upload | None | Displays a report of the errors that occurred when uploading the QoS configuration from a device. QPM creates a separate report for each database, and after each upload operation, the list of errors is added to the report. |
Tools | Reset Upload Report | None | Deletes the contents of the upload report for the currently open database. |
Tools | Application Services |
| Creates or edits application service aliases. Application services are a defined set of characteristics that identify the source of traffic, so that you can more easily write policies that target the defined traffic. |
Tools | Host Groups |
| Creates or edits host groups. Host groups are collections of hosts or subnets that you can use when creating QoS statements, so that you do not have to retype long lists for multiple statements. |
Tools | DNS Resolution>Resolve Unresolved Host Names | None | Resolves only those host names that have not previously been resolved. Does not check previously resolved host names to determine if the IP address is correct. |
Tools | DNS Resolution>Resolve All Host Names | None | Resolves all host names, even those that have previously been resolved. This ensures that the QoS database contains all current IP addresses for the hosts on the network. |
Tools | Telnet |
| Starts Telnet and attempts to connected to the selected device, if any. |
Tools | User Manager |
| Opens Windows NT or Windows 2000 User Manager, so that you can change the membership in the QPM user and guest groups. These groups manage user authentication for QPM, and are defined as local groups on the machine running the QoS Manager service. |
Help | Topics |
| Opens the online help. |
Help | About | None | Displays the version and copyright information for the program. |
(None) | (None) |
| Moves the selected policy up in the list of policies. |
(None) | (None) |
| Moves the selected policy down in the list of policies. |
(None) | (None) | Filter box | Filters which policy statements are displayed based on your selection. |
Menu | Command | Toolbar Button | Description |
---|---|---|---|
File | Close | None | Closes Distribution Manager without closing Policy Manager. |
File | Exit | None | Closes Distribution Manager and Policy Manager. |
View | Toolbar | None | Displays (when checked) or hides the toolbar, which contains shortcut buttons for some menu commands. |
View | Log | None | Displays (when checked) the log pane at the bottom of the main window. |
View | Status Bar | None | Displays (when checked) or hides the status bar tray at the bottom of the main window. |
Devices | Create Job | None | Creates a distribution job. You are prompted to select the QoS database that contains the configuration that you want to deploy to the network. |
Devices | Apply |
| Applies the job the first valid Not-Applied job (created with the Devices>Create Job command) in the tree view to the network, if there is one. If there is no valid Not-Applied job, QPM asks you to select the database from which to create the job, and then applies the job without allowing you to inspect the job contents. The job contains the configuration commands required to deploy your QoS policies and settings to the network. Use the Devices>Create Job command to create a job that you can inspect before applying it. |
Devices | Apply to All |
| Generates an apply process to all the devices of the selected job, regardless of their status (Not-Applied, Unchanged, and so on). The status of each device is changed to Not-Applied, and then the deployment process starts. Because the deployment is incremental, if nothing has been changed on the device and the database has not been changed, no configuration will be deployed. Apply to All has the same behavior as Apply. |
Devices | Stop |
| Stops the deployment of the current job to the network. The job is stopped after the changes to the device currently being configured are complete. |
Devices | Resume |
| Resumes the deployment of the job that you previously stopped. |
Devices | View Commands | None | Displays the commands that will be used to configure the device selected in the list pane. |
Devices | View Backup Configuration File | None | Displays the configuration that has been deployed on the selected device. |
Devices | View Full Deployment File | None | Displays the contents of the full deployment file that is created after deployment to file. This file contains the complete device configuration after deployment, and can be sent via TFTP to configure the device. |
Devices | View Incremental Deployment File | None | Displays the contents of the incremental deployment file that is created after deployment to file. This file contains the incremental commands that need to be sent to the device to update its configuration. |
Devices | View Job Logging | None | Displays the log for the selected job. |
Devices | Verify Device Configuration |
| Verifies if the policies in the most recently distributed job match the configuration on the devices. There might be cases where CLI changes were made on the device, creating a mismatch between the database and the device configuration. This function has the same behavior as Apply and Apply to All. If a Not-Applied job exists this job is verified, otherwise a new job is created and verified. The verification process contains two steps, DNS resolution check, and device configuration check. |
Devices | Restore to Current |
| Restores the previously created job as the current database. You will be prompted to create a job for the current database, if it has not been saved as a job. |
Devices | Restore to Current and Apply |
| Restores the previously created job as the current database and applies it to the network. |
Devices | Options | None | Opens the Options dialog, which allows you to configure some characteristics of Distribution Manager operation. |
Tools | Policy Manager |
| Starts the Policy Manager application, which lets you create and edit policy statements. |
Tools | Reports>All Jobs | None | Displays the summary information for each job, along with the device details for each job. |
Tools | Reports>System Log | None | Displays the system log, which contains messages concerning the functioning of Distribution Manager. |
Tools | Reports>Device Log | None | Displays the log of the selected device, which contains Telnet and device messages produced while the device was being configured. |
Tools | Reports>Job Log | None | Displays the log of the selected job, which contains Telnet and device messages produced while the job was being applied to the network. |
Tools | User Manager |
| Opens Windows NT or Windows 2000 User Manager, so that you can change the membership in the QPM user and guest groups. These groups manage user authentication for QPM, and are defined as local groups on the machine running the QoS Manager service. |
Help | Topics |
| Opens the online help. |
Help | About | None | Displays the version and copyright information for the program. |
QPM uses device commands to configure your QoS policies and configurations on the devices. These are the same commands you can use on the device's command line interface (CLI), and they are described in the device's documentation.
This section shows the command sequences used to configure each type of abstract policy action that you can create using QPM. You can use this information to help you understand how QPM configures your devices. See the device's documentation for complete information on the commands and their parameters. (See More Information About Quality of Service for a partial list of product documentation.)
These sections show the full command translation, including optional parameters. If you do not configure an optional setting, the associated command or parameter is not included in the command sequence QPM uses to configure the device.
Note The notation in the translation is bold for the device's key words, italic for variables. Some of the variables are parameters you enter into QPM. Other variables are managed by QPM, for example, the ACL number. |
These sections describe QPM abstract actions:
When you select Class Based QoS for an interface's QoS property, and create CBWFQ queuing policies on the interface, QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. class-map [match all | match any] classname
a. match access-group ACLNum
b. match ip dscp dscp
c. match ip precedence precedence
d. match ip rtp low_port range
e. match protocol protocol [parametername [value]]
3. policy-map policy-map-name
a. class classname
b. class class-default
4. interface interfacename
a. service-policy direction policy-map-name
Note Some commands are for CBWFQ on a device that supports NBAR or IPRTP. |
On ATM VCs, this command sequence is used:
1. interface interfacename
2. pvc pvc-name
a. service-policy direction policy-map-name
On frame-relay interfaces, this command sequence is used:
1. map-class frame-relay classname
a. service-policy direction policy-map-name
2. interface interfacename
a. frame-relay class classname
When you select Class Based QoS for an interface's QoS property, and create coloring policies on the interface, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. class classname
b. set ip coloring-mechanism value
When you select Class Based QoS for an interface's QoS property, and create limiting policies on the interface, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. class classname
b. police rate bc be conform-action conform-priority exceed-action exceed-priority
When you select Class Based QoS for an interface's QoS property, and create shaping policies on the interface, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. class classname
b. shape shaping-type rate bc be
c. shape adaptive adaptive-rate
d. shape fecn-adapt
When you select WFQ for an interface's QoS property, QPM uses this command sequence to configure the device:
1. interface interfacename
2. fair-queue
When you select WFQ for an interface's QoS property, and you enable Frame Relay traffic shaping (FRTS) on an interface, QPM uses this command sequence to configure the device:
1. map-class frame-relay classname
2. frame-relay fair-queue congestive-discard-threshold number-dynamic-conversation-queues number-reservable-conversation-queues max-buffer-size-for-fair-queues
3. interface interfacename
4. frame-relay class classname
5. frame-relay traffic-shaping
When you select WFQ or FQ for an interface's QoS property, and that interface is on a VIP card, QPM uses this command sequence to configure the device:
1. access-list ACLNum condition
2. rate-limit input access-group ACLNum rate bc be conform-action set-qos-transmit qos-group no exceed-action set-qos-transmit qos-group no
3. interface interfacename
4. fair-queue qos-group
5. fair-queue qos-group qos-group weight weight
6. fair-queue qos-group qos-group limit limit
7. fair-queue aggregate-limit aggregate-packet
8. fair-queue individual-limit individual-packet
When you select WRED for an interface's QoS property, or select WRED for the drop mechanism for a CBWFQ policy or interface QoS property, QPM uses this command sequence to configure the device:
1. interface interfacename
2. random-detect weight
When you use advanced WRED the following commands are also available:
When you enable Frame Relay traffic shaping (FRTS) on an interface, QPM uses this command sequence to configure the device:
1. map-class frame-relay classname
2. frame-relay cir cir
3. frame-relay mincir mincir
4. frame-relay bc bc
5. frame-relay be be
6. frame-relay adaptive-shaping becn
7. frame-relay ip rtp header-compression [passive]
8. frame-relay ip rtp priority low range bandwidth
9. no frame-relay adaptive shaping
10. no frame-relay becn-response-enable
11. interface interfacename
a. frame-relay class classname
b. frame-relay traffic-shaping
If you are using FRTS with CBWFQ, the following command is also available:
If you are using FRTS on DLCI, the following commands are used:
When you enable Frame Relay traffic shaping (FRTS) on an interface, and configure the voice fields, QPM uses this command sequence to configure the device:
1. map-class frame-relay classname
2. frame-relay fragment fragment-size
3. frame-relay voice bandwidth bps-reserved
4. interface interfacename
5. frame-relay class classname
6. frame-relay traffic-shaping
When you select Priority Queuing for an interface's QoS property, and create priority queuing policies on the interface, QPM uses this command sequence to configure the device (except for Frame Relay interfaces on which you have enabled FRTS):
1. access-list ACLNum filter
2. priority-list priorityNum protocol ip level list ACLNum
3. priority-list priorityNum default level
4. priority-list priorityNum queue-limit high-limit medium-limit normal-limit low-limit
5. interface interfacename
6. priority-group priorityNum
If the interface is Frame Relay using FRTS, QPM uses this command sequence to configure the device:
1. map-class frame-relay classname
2. frame-relay priority-group priorityNum
3. interface interfacename
4. frame-relay class classname
When you select Custom Queuing for an interface's QoS property, and create custom queuing policies on the interface, QPM uses this command sequence to configure the device (except for Frame Relay interfaces on which you have enabled FRTS):
1. access-list ACLNum filter
2. queue-list qListNum protocol ip qNum list ACLNum
3. queue-list qListNum queue qNum byte-count bytes limit limit
4. queue-list qListNum default qNum
5. interface interfacename
6. custom-queue-list qListNum
If the interface is Frame Relay using FRTS, QPM uses this command sequence to configure the device:
1. map-class frame-relay classname
2. frame-relay custom-queue-list qListNum
3. interface interfacename
4. frame-relay class classname
When you select FIFO for an interface's QoS property, QPM uses this command sequence to configure the device:
1. interface interfacename
2. no fair-queue
When you enable NBAR port mapping on an interface, QPM uses this command sequence to configure the device:
1. ip nbar port-map protocol tcp|udp portnumbers
When you enable resource reservation protocol (RSVP) on an interface, QPM uses this command sequence to configure the device:
1. ip rsvp bandwidth [interface-kbps [single-flow-kbps]]
2. ip rsvp udp-multicast
When you enable IP RTP priority on an interface, QPM uses this command sequence to configure the device:
1. ip rtp priority start-port port-range bandwidth
When you enable CRTP on an interface, QPM uses this command sequence to configure the device:
1. interface interfacename
2. ip rtp header-compression [passive]
3. frame-relay ip rtp header-compression [passive]
When you enable LFI on an interface, QPM uses this command sequence to configure the device:
1. interface interfacename
2. ppp multilink interleave
3. ppp multilink fragment-delay delay
When you create shaping policies on an interface, QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. interface interfacename
3. traffic-shape group ACLNum rate [bc be]
When you create limiting policies on an interface, QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. interface interfacename
3. rate-limit input | output access-group ACLNum rate bc be conform-action transmit | continue | set-prec-transmit precedence | set-dscp-transmit dscp | set-prec-continue precedence | set-dscp-continue dscp exceed-action drop
When you create queue weight policies on a layer 3 switch, QPM uses this command sequence to configure the device:
1. qos switching
2. qos mapping [source Fastethernet name] [destination Fastethernet name] precedence precedence wrr-weight weight
When you create coloring policies on an interface, QPM uses a different command sequence depending on whether the device supports committed access rate (CAR) classification.
For devices that do support CAR (typically those running IOS software releases 11.1cc, and 12.0 and later), QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. interface interfacename
a. rate-limit input access-group ACLNum rate bc be conform-action set-prec-transmit precedence exceed-action set-prec-transmit precedence
b. rate-limit input|output access-group ACLNum rate bc be conform-action set-prec-transmit precedence | set-dscp-transmit dscp exceed-action set-prec-transmit precedence | set-dscp-transmit dscp
For devices that do not support CAR, QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. route-map tag
3. match ip address ACLNum
4. set ip precedence precedence
5. interface interfacename
6. ip policy route-map tag
When you create access control policies, QPM uses this command sequence to configure the device:
1. interface interfacename
2. ip access-group ACLNum direction
When you create coloring policies on a LocalDirector, QPM uses this command sequence to configure the device:
1. color virtualIp : portNo : bindId : protocolName precedence
When you create coloring policies on a Catalyst 5000 family switch, QPM uses this command sequence to configure the device:
1. set qos enable
2. set qos ip-filter precedence protocol source source-port destination destination-port
When you create coloring policies on a Catalyst 6000 family switch, QPM uses this command sequence to configure the device:
1. dscp=precedence*8 or dscp
2. dscp=precedence*8
3. set port qos module/port port-based | vlan-based
4. set qos acl ip acl-name dscp dscp protocol source eq port port destination eq port port
5. commit qos acl acl-name
6. set qos acl map acl-name module/port-or-vlan
Note When you enter precedence, the DSCP value is calculated as precedence*8. |
When you create limiting (policing) policies on a Catalyst 6000 family switch, QPM uses this command sequence to configure the device:
1. set port qos module/port port-based
2. set qos policer aggregate|micro-flow policer-name rate rate burst burst drop
3. set qos acl ip acl-name dscp dscp aggregate|micro-flow policer-name protocol source eq port port destination eq port port
4. set qos acl ip acl-name trust aggregate|micro-flow policer-name protocol source eq port port destination eq port port
5. commit qos acl acl-name
6. set qos acl map acl-name module/port
When you configure the trust state on a Catalyst 6000 family switch port, QPM uses this command sequence to configure the device:
1. set port qos module|port trust trust
2. set port qos mod-num|port-num qos-type
On Catalyst 6000 switches with Supervisor IOS, QPM uses the following command sequence:
1. mls qos
2. interface interfacename
3. mls qos
4. mls qos trust trust
5. mls qos vlan-based
When you configure 2Q2T and 1P2Q2T queuing on a Catalyst 6000 family switch, QPM uses this command sequence to configure the device:
1. set qos enable
2. set qos map 2q2t tx queue-number threshold-number cos coslist
3. set qos map 1p2q2t tx queue-number threshold-number cos coslist
4. set qos drop-threshold 2q2t tx queue queue-number threshold-1 threshold-2
5. set qos wrr 2q2t queue-weight-1 queue-weight-2
6. set qos txq-ratio 2q2t queue-ratio-1 queue-ratio-2
7. set qos wred 1p2q2t tx queue queue-number threshold-1 threshold-2
8. set qos wrr 1p2q2t queue-weight-1 queue-weight-2
9. set qos txq-ratio 1p2q2t queue-ratio-1 queue-ratio-2 queue-ratio-3
On Catalyst 6000 switches with Supervisor IOS, QPM uses the following command sequence:
1. mls qos
2. interface interfacename
3. mls qos
4. wrr-queue cos-map queue-number threshold-number coslist
5. wrr-queue queue-limit 1p2q2t queue-ratio-1 queue-ratio-2
6. wrr-queue bandwidth queue-weight-1 queue-weight-2
7. wrr-queue threshold queue-number threshold-1 threshold-2
8. wrr-queue random-detect max-threshold queue-number threshold-1 threshold-2
When you configure coloring (policing) policies on a Catalyst 6000 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. mls qos flow-policing (to enable flow policing).
a. policy-map policy-map-name
When you configure limiting (policing) policies on a Catalyst 6000 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. mls qos flow-policing (to enable flow policing).
a. policy-map policy-map-name
b. mls qos aggregate-policer policer-name rate bc be conform-action conform-priority exceed-action drop
When you configure these mapping settings on a Catalyst 6000, QPM uses this command sequence to configure the device:
1. set qos cos-dscp-map dscp dscp dscp dscp dscp dscp dscp dscp
2. set qos dscp-cos-map dscp, dscp, dscp, dscp, dscp, dscp, dscp, dscp:cos
3. set qos policed-dscp-map dscp, dscp, dscp, dscp, dscp, dscp, dscp, dscp:dscp
4. set qos ipprec-dscp-map dscp dscp dscp dscp dscp dscp dscp dscp
On Catalyst 6000 devices with Supervisor IOS, QPM uses this command sequence:
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
3. mls qos map ip-prec-dscp dscp dscp dscp dscp dscp dscp dscp dscp
4. mls qos map policed-dscp dscp dscp dscp dscp dscp dscp dscp dscp to dscp
When you configure Catalyst 3500XL and Catalyst 2900XL coloring policies, QPM uses this command sequence to configure the device:
1. Switchport priority default cos cos
2. Switchport priority extend trust
3. Switchport priority extend cos cos
When you configure Catalyst 4003 and Catalyst 4006 limiting policies, QPM uses this command sequence to configure the device:
When you configure Catalyst 4003 and Catalyst 4006 shaping policies, QPM uses this command sequence to configure the device:
Posted: Tue Nov 12 12:26:56 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.