|
|
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 create filters for non class-based policies, QPM translates the filter definitions to ACLs using this command sequence:
When you create filters for class-based policies, QPM uses this command sequence to configure ACLs on the device, if it supports filter names:
1. ip access-list extended name
2. deny | permit protocol source source-wildcard [{eq src-port | range src-port-from src-port-to}] destination destination-wildcard [{eq dest-port | range dest-port-from dest-port-to}] [precedence precedence] [dscp dscp]
When you select Class Based QoS as a QoS property, and create class-based 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 [not] access-group ACLNum
b. match [not] ip dscp dscp
c. match [not] ip precedence precedence
d. match [not] cos cos
e. match [not] ip rtp low_port range
f. match [not] protocol protocol [parametername [value]]
g. match [not] class-map classname
h. match [not] mpls experimental value
3. policy-map policy-map-name
a. class {classname | class-default}
4. interface interfacename
a. service-policy direction policy-map-name
|
Note Some commands are for class-based QoS 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 [input | output] policyname
2. interface interfacename
a. frame-relay class classname
When you select Class Based QoS as a QoS property, and create marking policies on the interface, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. class classname
When you select Class Based QoS as a QoS property, and create policing policies on the interface, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. class classname
When you select Class Based QoS as a 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
When you select modular shaping as a QoS property, and create shaping policies, QPM uses this command sequence to configure the device:
1. policy-map out_policies
2. policy-map policy-map-name
a. shape {average | peak} shape-rate [shape-bc shape-be]
b. service-policy out_policies
3. interface interfacename
When you select FIFO as a QoS property, QPM uses this command sequence to configure the device:
1. interface interfacename
2. no fair-queue
When you select WFQ as a QoS property, QPM uses this command sequence to configure the device:
1. interface interfacename
2. fair-queue
When you select WFQ or FQ as a 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-num exceed-action set-qos-transmit qos-group-num
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 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 | foresight}
7. frame-relay ip rtp priority low range bandwidth
8. no frame-relay adaptive shaping
9. no frame-relay {adaptive-shaping becn | adaptive-shaping foresight}
10. interface interfacename
a. frame-relay traffic-shaping
b. frame-relay class classname
c. frame-relay ip rtp header-compression [passive]
|
Note If you are using FRTS with different queuing types, additional commands are available. See the relevant queuing commands for information about these commands. |
If you are using FRTS on DLCI, the following commands are used:
When you select WFQ as a 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 traffic-shaping
5. frame-relay class classname
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 traffic-shaping
6. frame-relay class classname
When you select WRED as a QoS property, or select WRED for the drop mechanism for a class-based 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 select Priority Queuing as a 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 as a 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 create queue weight policies for 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 enable NBAR port mapping, QPM uses this command sequence to configure the device:
When you enable resource reservation protocol (RSVP), 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, QPM uses this command sequence to configure the device:
When you enable CRTP (RTP header compression), QPM uses this command sequence to configure the device:
1. interface interfacename
2. ip rtp header-compression [passive]
If the interface is Frame Relay, QPM uses this command sequence to configure the device:
When you enable LFI, QPM uses this command sequence to configure the device:
1. interface interfacename
2. ppp multilink interleave
3. ppp multilink fragment-delay delay
When you enable a TX-ring limit on a PVC, QPM uses this command sequence to configure the device:
1. interface interfacename
2. pvc pvc-name
3. tx-ring-limit ring-limit
When you enable inline power, QPM uses this command sequence to configure the device:
When you create access control policies, QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. interface interfacename
3. ip access-group ACLNum direction
When you create marking policies, QPM uses this command sequence to configure the device:
1. access-list ACLNum filter
2. route-map tag permit [sequence]
3. match ip address ACLNum
4. set ip precedence precedence
5. interface interfacename
6. ip policy route-map tag
When you create policing policies, 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 | drop} exceed-action {transmit | continue | set-prec-transmit precedence | set-dscp-transmit dscp | set-prec-continue precedence | set-dscp-continue dscp | drop}
When you create shaping policies, 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 marking policies for 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 configure 2Q2T and 1P2Q2T queuing for a Catalyst 6000 family switch, QPM uses this command sequence to configure the device:
1. set qos enable
2. set qos map 1p2q2t | 2q2t tx queue-number threshold-number cos cos-list
3. set qos drop-threshold 2q2t tx queue queue-number threshold-1 threshold-2
4. set qos wrr 1p2q2t | 2q2t queue-weight-1 queue-weight-2
5. set qos txq-ratio 1p2q2t | 2q2t queue-ratio-1 queue-ratio-2 [queue-ratio-3]
6. set qos wred 1p2q2t tx queue queue-number threshold-1 threshold-2
When you configure these mapping settings for 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 ipprec-dscp-map dscp dscp dscp dscp dscp dscp dscp dscp
4. set qos policed-dscp-map dscp, dscp, dscp, dscp, dscp, dscp, dscp, dscp:dscp
5. set qos policed-dscp-map excess-rate dscp, dscp, dscp, dscp, dscp, dscp, dscp, dscp:dscp
When you configure the trust state for a Catalyst 6000 family switch port, QPM uses this command sequence to configure the device:
1. set port qos module/port trust {trust-cos | trust-ipprec | trust-dscp}
2. set port qos module/port trust-ext {trust-cos | untrusted}
3. set port qos module/port {port-based | vlan-based}
When you create marking policies for a Catalyst 6000 family switch, QPM uses this command sequence to configure the device:
1. set qos acl ip acl-name dscp {dscp | trust-cos | trust-ipprec | trust-dscp} protocol source [{eq port | range port port}] destination [{eq port | range port port}] [{precedence precedence | dscp-field dscp}]
2. commit qos acl acl-name
3. set qos acl map acl-name {module/port | vlan}
When you create policing policies for a Catalyst 6000 family switch, QPM uses this command sequence to configure the device:
1. set qos policer {aggregate | microflow} policer-name rate rate [policed-dscp erate rate {policed-dscp | drop}] burst burst [{policed-dscp | drop}]
2. set qos acl [default-action] ip acl-name dscp {dscp | trust-cos | trust-ipprec | trust-dscp} {aggregate | microflow} policer-name [protocol source [{eq port | range port port}] destination [{eq port | range port port}]]
3. commit qos acl acl-name
4. set qos acl map acl-name {module/port | vlan}
When you configure the trust state for Catalyst 6000 switches with Supervisor IOS, QPM uses this command sequence to configure the device:
1. mls qos
2. interface interfacename
3. mls qos
4. mls qos trust {cos | ip-precedence | dscp}
5. mls qos vlan-based
When you configure the trust state for Catalyst 2950 switches with Supervisor IOS, QPM uses this command sequence to configure the device:
1. mls qos
2. interface interfacename
3. mls qos
4. mls qos trust {cos | dscp}
When you configure the trust state for Catalyst 3550 switches with Supervisor IOS (no VLAN-based QoS), QPM uses this command sequence to configure the device:
1. mls qos
2. interface interfacename
3. mls qos
4. mls qos trust {cos | ip-precedence | dscp}
When you configure marking policies for a Catalyst 6000 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. class-map [match all | match any] classname
a. match [not] access-group ACLNum
2. policy-map policy-map-name
When you configure marking policies for a class-default filter for a Catalyst 2950 with Supervisor IOS, or Catalyst 3550 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. Switchport priority extend trust
2. Switchport priority extend cos cos
When you configure marking policies for a user-defined filter for a Catalyst 2950 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. class-map [match all | match any] classname
a. match [not] access-group ACLNum
2. policy-map policy-map-name
3. class classname
4. set ip dscp dscp
When you configure marking (policing) policies for a user-defined filter for a Catalyst 3550 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. class-map [match all | match any] classname
a. match [not] access-group ACLNum
2. policy-map policy-map-name
3. class classname
4. set ip dscp dscp
5. set ip precedence precedence
6. trust {cos | ip-precedence | dscp}
When you configure policing policies for a Catalyst 6000 with Supervisor IOS or Catalyst 3550 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. police [flow] rate bc be [pir pir] conform-action {set-prec-transmit | set-dscp-transmit | drop} exceed-action {transmit | policed-dscp-transmit | drop} [violate-action {transmit | policed-dscp-transmit | drop}]
b. police aggregate policer-name
If you define an aggregate policing policy, the following command is used:
When you configure policing policies for a Catalyst 2950 with Supervisor IOS, QPM uses this command sequence to configure the device:
1. policy-map policy-map-name
a. police rate bc [exceed-action {dscp dscp | drop}]
b. police aggregate policer-name
If you define an aggregate policing policy, the following command is used:
When you configure 2Q2T or 1P2Q2T queuing for 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 cos-list
5. priority-queue cos-map queue-id cos-list
6. wrr-queue queue-limit queue-ratio-1 queue-ratio-2
7. wrr-queue bandwidth queue-weight-1 queue-weight-2
8. wrr-queue threshold queue-number threshold-1 threshold-2
9. wrr-queue random-detect max-threshold queue-number threshold-1 threshold-2
When you configure 4Q2T queuing for Catalyst 3550 switches with Supervisor IOS, QPM uses the following command sequence:
1. wrr-queue cos-map queue-number cos-list
2. priority-queue out
3. wrr-queue dscp-map threshold-id dscp-list
4. wrr-queue queue-limit queue-ratio-1 queue-ratio-2 queue-ratio-3 queue-ratio-4
5. wrr-queue bandwidth queue-weight-1 queue-weight-2 queue-weight-3 queue-weight-4
6. wrr-queue threshold queue-number threshold-1 threshold-2
7. wrr-queue random-detect max-threshold queue-number threshold-1 threshold-2
When you configure 4Q1T queuing for Catalyst 2950 switches with Supervisor IOS, QPM uses the following command sequence:
1. wrr-queue bandwidth queue-weight-1 queue-weight-2 queue-weight-3 queue-weight-4
2. wrr-queue cos-map queue-number cos-list
When you configure these mapping settings for a Catalyst 6000 with Supervisor IOS or Catalyst 3550 with Supervisor IOS, QPM uses this command sequence to configure the device:
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 [{normal-burst | max-burst}] dscp dscp dscp dscp dscp dscp dscp dscp to dscp
When you configure these mapping settings for a Catalyst 2950 with Supervisor IOS, QPM uses this command sequence to configure the device:
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
When you configure Catalyst 2900XL and Catalyst 3500XL marking policies, QPM uses this command sequence to configure the device:
1. interface interfacename
2. Switchport priority default cos cos
3. Switchport priority extend {none | trust}
4. Switchport priority extend cos cos
When you configure Layer 3 policing policies, QPM uses this command sequence to configure the device:
1. interface interfacename
2. rate-limit {input | output} rate [burst]
When you configure Layer 3 shaping policies, QPM uses this command sequence to configure the device:
1. interface interfacename
2. traffic-shape rate rate [burst]
When you configure 2Q1T queuing policies for Catalyst 4000 switches, QPM uses this command sequence to configure the device:
When you configure marking policies for Catalyst 4000 switches, QPM uses this command sequence to configure the device:
Posted: Tue Nov 12 12:28:56 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.