Cisco IOS Quality of Service Solutions Command Reference

send qdm message

To send a text message to all Quality Device Manager (QDM) clients, use the send qdm message command in EXEC mode.

send qdm [client client-id] message message-text

Syntax Description

Command Default

No text messages are sent.

Command Modes

EXEC

Command History

Usage Guidelines

Use the send qdm command to send a message to a specific QDM client. For example, entering the send qdm client 9 message hello command will send the message "hello" to client ID 9.

Use the send qdm message message-text command to send a message to all QDM clients. For example, entering the send qdm message hello command sends the message "hello" to all open QDM clients.

Examples

The following example sends the text message "how are you?" to client ID 12:

send qdm client 12 message how are you?

The following example sends the text message "how is everybody?" to all QDM clients connected to the router:

send qdm message how is everybody?

Related Commands

service-group

To create a service group, use the service-group command in global configuration mode. To remove a service group, use the no form of this command.

service-group service-group-identifier

no service-group service-group-identifier

Syntax Description

Command Default

A service group is not created.

Command Modes

Global configuration (config)

Command History

Usage Guidelines

The maximum number of service groups that are supported on a router is determined by the router at system-startup time. For the Cisco 7600 series router, the valid entry range for the service-group-identifier argument is 1 to 32768.

Examples

In the following example, service group 750 is created.

Router> enable

Router# configure terminal

Router(config)# service-group 750

Router(config)# end

service-policy

To attach a policy map to an input interface, a virtual circuit (VC), an output interface, or a VC that will be used as the service policy for the interface or VC, use the service-policy command in the appropriate configuration mode. To remove a service policy from an input or output interface or from an input or output VC, use the no form of this command.

service-policy [type access-control] {input | output} policy-map-name

no service-policy [type access-control] {input | output} policy-map-name

Cisco 10000 Series and Cisco 7600 Series Routers

service-policy [history | {input | output} policy-map-name | type control control-policy-name]

no service-policy [history | {input | output} policy-map-name | type control control-policy-name]

Syntax Description

Command Default

No service policy is specified.
A control policy is not applied to a context.
No policy map is attached.

Command Modes

ATM bundle-VC configuration (config-atm-bundle)
ATM PVP configuration (config-if-atm-l2trans-pvp)
ATM VC mode (config-if-atm-vc)
Ethernet service configuration (config-if-srv)
Global configuration (config)
Interface configuration (config-if)
Map-class configuration (config-map-class)
PVC-in-range configuration (cfg-if-atm-range-pvc)
PVC range subinterface configuration (config-subif)

Command History

Usage Guidelines

Choose the command mode according to the intended use of the command, as follows:

You can attach a single policy map to one or more interfaces or to one or more VCs to specify the service policy for those interfaces or VCs.

A service policy specifies class-based weighted fair queueing (CBWFQ). The class policies that make up the policy map are then applied to packets that satisfy the class map match criteria for the class.

To successfully attach a policy map to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the classes that make up the policy map must be less than or equal to 75 percent (99 percent on the Cisco 10008 router) of the interface bandwidth or the bandwidth allocated to the VC.

To enable Low Latency queueing (LLQ) for Frame Relay (priority queueing [PQ]/CBWFQ), you must first enable Frame Relay Traffic Shaping (FRTS) on the interface using the frame-relay traffic-shaping command in interface configuration mode. You then attach an output service policy to the Frame Relay VC using the service-policy command in map-class configuration mode.

For a policy map to be successfully attached to an interface or ATM VC, the aggregate of the configured minimum bandwidths of the classes that make up the policy map must be less than or equal to 75 percent of the interface bandwidth or the bandwidth allocated to the VC. For a Frame Relay VC, the total amount of bandwidth allocated must not exceed the minimum committed information rate (CIR) configured for the VC less any bandwidth reserved by the frame-relay voice bandwidth or frame-relay ip rtp priority map-class commands. If these values are not configured, the minimum CIR defaults to half of the CIR.

Configuring CBWFQ on a physical interface is possible only if the interface is in the default queueing mode. Serial interfaces at E1 (2.048 Mbps) and below use weighted fair queueing (WFQ) by default. Other interfaces use first-in first-out (FIFO) by default. Enabling CBWFQ on a physical interface overrides the default interface queueing method. Enabling CBWFQ on an ATM permanent virtual circuit (PVC) does not override the default queueing method.

When you attach a service policy with CBWFQ enabled to an interface, commands related to fancy queueing such as those pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED) are available using the modular quality of service command-line interface (MQC). However, you cannot configure these features directly on the interface until you remove the policy map from the interface.

Note Beginning in Cisco IOS Release 12.4(18e), you cannot configure the traffic-shape rate and MQC shaping on the same interface at the same time. You must remove the traffic-shape rate configured on the interface before you attach the service policy. For example, if you try to enter the service-policy {input | output} policy-map-name command when the traffic-shape rate command is already in effect, this message is displayed: Remove traffic-shape rate configured on the interface before attaching the service-policy.

If the MQC shaper is attached first, and you enter the legacy traffic-shape rate command on the same interface, the command is rejected and an error message is displayed.

You can modify a policy map attached to an interface or VC, changing the bandwidth of any of the classes that make up the map. Bandwidth changes that you make to an attached policy map are effective only if the aggregate of the bandwidth amount for all classes that make up the policy map, including the modified class bandwidth, is less than or equal to 75 percent of the interface bandwidth or the VC bandwidth. If the new aggregate bandwidth amount exceeds 75 percent of the interface bandwidth or VC bandwidth, the policy map is not modified.

After you apply the service-policy command to set a class of service (CoS) bit to an Ethernet interface, the policy is set in motion as long as there is a subinterface that is performing 8021.Q or Inter-Switch Link (ISL) trunking. Upon reload, however, the service policy is removed from the configuration with the following error message:

Process `set' action associated with class-map voip failed: Set cos supported only with 
IEEE 802.1Q/ISL interfaces.

Cisco 10000 Series Router Usage Guidelines

The Cisco 10000 series router does not support applying CBWFQ policies to unspecified bit rate (UBR) VCs.

For a policy map to be successfully attached to an interface or a VC, the aggregate of the configured minimum bandwidth of the classes that make up the policy map must be less than or equal to 99 percent of the interface bandwidth or the bandwidth allocated to the VC. If you attempt to attach a policy map to an interface when the sum of the bandwidth assigned to classes is greater than 99 percent of the available bandwidth, the router logs a warning message and does not allocate the requested bandwidth to all of the classes. If the policy map is already attached to other interfaces, it is removed from them.

The total bandwidth is the speed (rate) of the ATM layer of the physical interface. The router converts the minimum bandwidth that you specify to the nearest multiple of 1/255 (ESR-PRE1) or 1/65535 (ESR-PRE2) of the interface speed. When you request a value that is not a multiple of 1/255 or 1/65535, the router chooses the nearest multiple.

The bandwidth percentage is based on the interface bandwidth. In a hierarchical policy, the bandwidth percentage is based on the nearest parent shape rate.

By default, a minimum bandwidth guaranteed queue has buffers for up to 50 milliseconds of 256-byte packets at line rate, but not less than 32 packets.

For Cisco IOS Release 12.0(22)S and later releases, to enable LLQ for Frame Relay (priority queueing (PQ)/CBWFQ) on the Cisco 10000 series router, first create a policy map and then assign priority to a defined traffic class using the priority command. For example, the following sample configuration shows how to configure a priority queue with a guaranteed bandwidth of 8000 kbps. In the example, the Business class in the policy map named "map1" is configured as the priority queue. The map1 policy also includes the Non-Business class with a minimum bandwidth guarantee of 48 kbps. The map1 policy is attached to serial interface 2/0/0 in the outbound direction.

class-map Business

	match ip precedence 3

policy-map map1

	class Business

	priority 

	police 8000

	class Non-Business

	bandwidth 48

interface serial 2/0/0

	frame-relay encapsulation

	service-policy output map1

On the PRE2, you can use the service-policy command to attach a QoS policy to an ATM subinterface or to a PVC. However, on the PRE3, you can attach a QoS policy only to a PVC.

Cisco 7600 Series Routers

The output keyword is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2.

Do not attach a service policy to a port that is a member of an EtherChannel.

Although the CLI allows you to configure QoS based on policy feature cards (PFCs) on the WAN ports on the OC-12 ATM optical services modules (OSM) and on the WAN ports on the channelized OSMs, PFC-based QoS is not supported on the WAN ports on these OSMs. OSMs are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.

PFC QoS supports the optional output keyword only on VLAN interfaces. You can attach both an input policy map and an output-policy map to a VLAN interface.

Cisco 10000 Series Routers Control Policy Maps

A control policy map must be activated by applying it to a context. A control policy map can be applied to one or more of the following types of contexts, which are listed in order of precedence:

1. Global

2. Interface

3. Subinterface

4. Virtual template

5. VC class

6. PVC

In general, control policy maps that are applied to more specific contexts take precedence over policy maps applied to more general contexts. In the list, the context types are numbered in order of precedence. For example, a control policy map that is applied to a permanent virtual circuit (PVC) takes precedence over a control policy map that is applied to an interface.

Control policies apply to all sessions hosted on the context. Only one control policy map can be applied to a given context.

In Cisco IOS Release 12.2(33)SB and later releases, the router no longer accepts the abbreviated form (ser) of the service-policy command. Instead, you must spell out the command name service- before the router accepts the command.

For example, the following error message displays when you attempt to use the abbreviated form of the service-policy command:

interface GigabitEthernet1/1/0

 ser out ?

% Unrecognized command

 ser ?

% Unrecognized command

As shown in the following example, when you enter the command as service- followed by a space, the router parses the command as service-policy. Entering the question mark causes the router to display the command options for the service-policy command.

service- ?

input	Assign policy-map to the input of an interface

output	Assign policy-map to the output of an interface

type	Configure CPL Service Policy

In releases prior to Cisco IOS Release 12.2(33)SB, the router accepts the abbreviated form of the service-policy command. For example, the router accepts the following commands:

interface GigabitEthernet1/1/0

 ser out test

Examples

The following example shows how to attach a policy map to a Fast Ethernet interface:

interface fastethernet 5/20

 service-policy input pmap1

The following example shows how to attach the service policy map named "policy9" to DLCI 100 on output serial interface 1 and enables LLQ for Frame Relay:

interface Serial1/0.1 point-to-point

 frame-relay interface-dlci 100

 class fragment

 map-class frame-relay fragment

 service-policy output policy9

The following example shows how to attach the service policy map named "policy9" to input serial interface 1:

interface Serial1

 service-policy input policy9

The following example attaches the service policy map named "policy9" to the input PVC named "cisco":

pvc cisco 0/34  
service-policy input policy9

vbr-nt 5000 3000 500 
precedence 4-7

The following example shows how to attach the policy named "policy9" to output serial interface 1 to specify the service policy for the interface and enable CBWFQ on it:

interface serial1

 service-policy output policy9

The following example attaches the service policy map named "policy9" to the output PVC named "cisco":

pvc cisco 0/5  
service-policy output policy9 
vbr-nt 4000 2000 500 
precedence 2-3

Cisco 10000 Series Router Examples

The following example shows how to attach the service policy named "userpolicy" to DLCI 100 on serial subinterface 1/0/0.1 for outbound packets:

interface serial 1/0/0.1 point-to-point

 frame-relay interface-dlci 100

 service-policy output userpolicy

Note You must be running Cisco IOS Release 12.0(22)S or a later release to attach a policy to a DLCI in this way. If you are running a release prior to Cisco IOS Release 12.0(22)S, attach the service policy as described in the previous configuration examples using the legacy Frame Relay commands.

The following example shows how to attach a QoS service policy named "map2" to PVC 0/101 on the ATM subinterface 3/0/0.1 for inbound traffic:

interface atm 3/0/0

 atm pxf queuing

interface atm 3/0/0.1

 pvc 0/101

 service-policy input map2

Note The atm pxf queuing command is not supported on the PRE3 or PRE4.

The following example shows how to attach a service policy named "myQoS" to physical Gigabit Ethernet interface 1/0/0 for inbound traffic. VLAN 4, configured on Gigabit Ethernet subinterface 1/0/0.3, inherits the service policy of physical Gigabit Ethernet interface 1/0/0.

interface GigabitEthernet 1/0/0

 service-policy input myQoS

interface GigabitEthernet 1/0/0.3

 encapsulation dot1q 4

The following example shows how to attach the service policy map named "voice" to ATM VC 2/0/0 within a PVC range of a total of three PVCs and enable PVC range configuration mode where a point-to-point subinterface is created for each PVC in the range. Each PVC created as part of the range has the voice service policy attached to it.

configure terminal

 interface atm 2/0/0

 range pvc 1/50 1/52

 service-policy input voice

The following example shows how to attach the service policy map named "voice" to ATM VC 2/0/0 within a PVC range, where every VC created as part of the range has the voice service policy attached to it. The exception is PVC 1/51, which is configured as an individual PVC within the range and has a different service policy named "data" attached to it in PVC-in-range configuration mode.

configure terminal

 interface atm 2/0/0

 range pvc 1/50 1/52

 service-policy input voice

 pvc-in-range 1/51

 service-policy input data

The following example shows how to configure a service group named "PREMIUM-SERVICE" and apply the input policy named "PREMIUM-MARK-IN" and the output policy named "PREMIUM-OUT" to the service group:

policy-map type service PREMIUM-SERVICE

 service-policy input PREMIUM-MARK-IN

 service-policy output PREMIUM-OUT

Related Commands

service-policy (class-map)

To attach a policy map to a class, use the service-policy command in class-map configuration mode. To remove a service policy from a class, use the no form of this command.

service-policy policy-map

no service-policy

Syntax Description

Command Default

No service policy is specified.

Command Modes

Class-map configuration

Command History

Usage Guidelines

You can attach a single policy map to one or more classes to specify the service policy for those classes. This command is only available for the output interface, which is assumed.

Examples

In the following example, three policy maps are defined—cust1-classes, cust2-classes, and cust-policy. The policy maps cust1-classes and cust2-classes have three classes defined—gold, silver, and bronze.

For cust1-classes, gold is configured to use 50 percent of the bandwidth. Silver is configured to use 20 percent of the bandwidth, and bronze is configured to use 15 percent of the bandwidth.

For cust2-classes, gold is configured to use 30 percent of the bandwidth. Silver is configured to use 15 percent of the bandwidth, and bronze is configured to use 10 percent of the bandwidth.

The policy map cust-policy specifies average rate shaping of 384 kbps and assigns the service policy called cust1-classes to the policy map called cust1-classes. The policy map called cust-policy specifies peak rate shaping of 512 kbps and assigns the service policy called cust2-classes to the policy map called cust2-classes.

To configure classes for cust1-classes, use the following commands:

Router(config)# policy-map cust1-classes

Router(config-pmap)# class gold

Router(config-pmap-c)# bandwidth percent 50

Router(config-pmap-c)# exit

Router(config-pmap)# class silver

Router(config-pmap-c)# bandwidth percent 20

Router(config-pmap-c)# exit

Router(config-pmap)# class bronze

Router(config-pmap-c)# bandwidth percent 15

To configure classes for cust2, use the following commands:

Router(config)# policy-map cust2-classes

Router(config-pmap)# class gold

Router(config-pmap-c)# bandwidth percent 30

Router(config-pmap-c)# exit

Router(config-pmap)# class silver

Router(config-pmap-c)# bandwidth percent 15

Router(config-pmap-c)# exit

Router(config-pmap)# class bronze

Router(config-pmap-c)# bandwidth percent 10

To define the customer policy with cust1-classes and cust2-classes and QoS features, use the following commands:

Router(config)# policy-map cust-policy

Router(config-pmap)# class cust1

Router(config-pmap-c)# shape average 38400

Router(config-pmap-c)# service-policy cust1-classes

Router(config-pmap-c)# exit

Router(config-pmap)# class cust2

Router(config-pmap-c)# shape peak 51200

Router(config-pmap-c)# service-policy cust2-classes

Router(config-pmap-c)# interface Serial 3/2

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# exit

Router(config)# interface serial0/0

Router(config-if)# service out cust-policy

Related Commands

service-policy (control-plane)

To attach a policy map to a control plane for aggregate or distributed control plane services, use the service-policy command in control-plane configuration mode. To remove a service policy from a control plane, use the no form of this command.

service-policy {input | output} policy-map-name

no service-policy {input | output} policy-map-name

Syntax Description

Command Default

No service policy is specified.

Command Modes

Control-plane configuration (config-cp)

Command History

Usage Guidelines

After entering the control-plane command, use the service-policy command to configure a quality of service (QoS) policy. This policy is attached to the control plane interface for aggregate or distributed control plane services and controls the number or rate of packets that are going to the process level.

When you configure output policing on control-plane traffic, using the service-policy output policy-map-name command, a router is automatically enabled to silently discard packets. Output policing is supported as follows:

•Supported only in:

–Cisco IOS Release 12.2(25)S and later Cisco IOS 12.2S releases.

–Cisco IOS Release 12.3(4)T and later Cisco IOS 12.3T releases.

–Cisco IOS Release 12.2(18)SXD1 and later Cisco IOS 12.2SX releases.

–Cisco IOS XE Release 2.2 and later Cisco IOS XE releases.

•Not supported for attaching a QoS policy for distributed control-plane services.

•Not supported on the Cisco 6500 router, Cisco 7500 series, and Cisco 10720 Internet router.

The service-policy output command configures output policing, which is performed in silent mode to silently discard packets exiting from the control plane according to the attached QoS policy. Silent mode allows a router that is running Cisco IOS software to operate without sending any system messages. If a packet that is exiting from the control plane is discarded for output policing, you do not receive an error message.

Silent mode allows a router that is running Cisco IOS software to operate without sending any system messages. If a packet that is destined for the router is discarded for any reason, users will not receive an error message. Some events that will not generate error messages are as follows:

•Traffic that is being transmitted to a port to which the router is not listening

•A connection to a legitimate address and port that is rejected because of a malformed request

Examples

The following example shows how to configure trusted hosts with source addresses 10.1.1.1 and 10.1.1.2 to forward Telnet packets to the control plane without constraint, while allowing all remaining Telnet packets to be policed at the specified rate:

! Allow 10.1.1.1 trusted host traffic.

Router(config)# access-list 140 deny tcp host 10.1.1.1 any eq telnet 

! Allow 10.1.1.2 trusted host traffic. 

Router(config)# access-list 140 deny tcp host 10.1.1.2 any eq telnet 

! Rate-limit all other Telnet traffic.

Router(config)# access-list 140 permit tcp any any eq telnet

! Define class-map "telnet-class."

Router(config)# class-map telnet-class 

Router(config-cmap)# match access-group 140

Router(config-cmap)# exit

Router(config)# policy-map control-plane-policy

Router(config-pmap)# class telnet-class

Router(config-pmap-c)# police 80000 conform transmit exceed drop

Router(config-pmap-c)# exit

Router(config-pmap)# exit

! Define aggregate control plane service for the active route processor.

Router(config)# control-plane

Router(config-cp)# service-policy input control-plane-policy

Router(config-cp)# end

The next example shows how to configure trusted networks with source addresses 10.0.0.0 and 10.0.0.2 to receive Internet Control Message Protocol (ICMP) port-unreachable responses without constraint, while allowing all remaining ICMP port-unreachable responses to be dropped:

! Allow 10.0.0.0 trusted network traffic.

Router(config)# access-list 141 deny icmp host 10.0.0.0 255.255.255.224 any 
port-unreachable 

! Allow 10.0.0.2 trusted network traffic.

Router(config)# access-list 141 deny icmp host 10.0.0.2 255.255.255.224 any 
port-unreachable 

! Rate-limit all other ICMP traffic. 

Router(config)# access-list 141 permit icmp any any port-unreachable

Router(config)# class-map icmp-class 

Router(config-cmap)# match access-group 141

Router(config-cmap)# exit

Router(config)# policy-map control-plane-out-policy

! Drop all traffic that matches the class "icmp-class."

Router(config-pmap)# class icmp-class

Router(config-pmap-c)# drop

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# control-plane

! Define aggregate control plane service for the active route processor.

Router(config-cp)# service-policy output control-plane-out-policy 

Router(config-cp)# end

Related Commands

service-policy (policy-map class)

To use a service policy as a QoS policy within a policy map (called a hierarchical service policy), use the service-policy command in policy-map class configuration mode. To disable a particular service policy as a QoS policy within a policy map, use the no form of this command.

service-policy policy-map-name

no service-policy policy-map-name

Syntax Description

Command Default

No service policies are used.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

This command is used to create hierarchical service policies in policy-map class configuration mode.

This command is different from the service-policy [input | output] policy-map-name command used in interface configuration mode. The purpose of the service-policy [input | output] policy-map-name is to attach service policies to interfaces.

The child policy is the previously defined service policy that is being associated with the new service policy through the use of the service-policy command. The new service policy using the preexisting service policy is the parent policy.

This command has the following restrictions:

•The set command is not supported on the child policy.

•The priority command can be used in either the parent or the child policy, but not both policies simultaneously.

•The shape command can be used in either the parent or the child policy, but not both polices simultaneously on a subinterface.

•The fair-queue command cannot be defined in the parent policy.

•If the bandwidth command is used in the child policy, the bandwidth command must also be used in the parent policy. The one exception is for policies using the default class.

Examples

The following example creates a hierarchical service policy in the service policy called parent:

Router(config)# policy-map child

Router(config-pmap)# class voice

Router(config-pmap-c)# priority 50

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# policy-map parent

Router(config-pmap)# class class-default

Router(config-pmap-c)# shape average 10000000

Router(config-pmap-c)# service-policy child

FRF.11 and FRF.12 configurations on a Versatile Interface Processor (VIP)-enabled Cisco 7500 series router often require a hierarchical service policy for configuration. A hierarchical service policy for FRF.11 and FRF.12 requires the following elements:

1. A traffic class that uses the Voice over Frame Relay (VoFR) protocol as the only match criterion.

2. A traffic policy that insures low latency queueing (LLQ), which is achieved using the priority command, for all VoFR protocol traffic

3. A traffic policy that defines the shaping parameters and includes the elements listed in element 2.

Element 3 can only be fulfilled through the use of a hierarchical service policy, which is configured using the service-policy command.

In the following example, element 1 is configured in the traffic class called frf, element 2 is configured in the traffic policy called llq, and element 3 is configured in the traffic policy called llq-shape.

Router(config)# class-map frf

Router(config-cmap)# match protocol vofr

Router(config-cmap)# exit

Router(config)# policy-map llq

Router(config-pmap)# class frf

Router(config-pmap-c)# priority 2000

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# policy-map llq-shape

Router(config-pmap)# class class-default

Router(config-pmap-c)# shape average 1000 128000

Router(config-pmap-c)# service-policy llq

The final step in using a hierarchical service policy for FRF.11 and FRF.12 is using the service policy in map-class configuration mode. In the following example, the traffic policy called llq-shape is attached to the map class called frag:

Router(config)# map-class frame-relay frag

Router(config-map-class)# frame-relay fragment 40

Router(config-map-class)# service-policy llq-shape

Related Commands

service-policy (service group)

To attach a policy map to a service group, use the service-policy command in service-group configuration mode. To remove a policy map from a service group, use the no form of this command.

service-policy {input | output} policy-map-name

no service-policy {input | output} policy-map-name

Syntax Description

Command Default

A policy map is not attached to a service group.

Command Modes

Service-group configuration (config-service-group)

Command History

Usage Guidelines

The policy map must already exist and must contain the Quality of Service (QoS) feature to be applied to the service group, according to the provisions specified by the Service Level Agreement (SLA). To create and configure the policy map, use the Modular Quality of Service Command-Line Interface (CLI) (MQC). For more information about the MQC, see the Cisco IOS Quality of Service Solutions Configuration Guide.

Examples

In the following example, a policy map called 3-customer-in is attached to service group 1:

Router> enable 

Router# configure terminal 

Router(config)# service-group 1 

Router(config-service-group)# service-policy input 3-customer-in 

Router(config-service-group)# end 

service-policy type qos

To apply a quality of service (QoS) policy map to an identity, use the service-policy type qos command in identity policy configuration mode. To remove the QoS policy map, use the no form of this command.

service-policy type qos {input | output} policy-map-name

no service-policy type qos {input | output} policy-map-name

Syntax Description

Command Default

No QoS policy map is applied to an identity.

Command Modes

Identity policy configuration (config-identity-policy)

Command History

Usage Guidelines

The input and output keywords indicate the direction in which the policy map will be applied.

The value for the policy-map-name argument represents a QoS policy map configured on the switch using the policy-map policy-map-name global configuration command.

Examples

The following example applies an ingress QoS policy map to an identity:

Router(config)# identity policy policy1

Router(config-identity-policy)# service-policy type qos input my-in-policy 

Related Commands

set atm-clp

To set the ATM cell loss priority (CLP) bit when a policy map is configured, use the set atm-clp command in policy-map class configuration mode. To remove a specific ATM CLP bit setting, use the no form of this command.

set atm-clp

no set atm-clp

Syntax Description

This command has no arguments or keywords.

Command Default

The ATM CLP bit is automatically set to 0 by Cisco router interfaces, when Cisco routers convert IP packets into ATM cells for transmission through Multiprotocol Label Switching (MPLS)-aware ATM networks.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

To disable this command, remove the service policy from the interface using the no service-policy command.

The set atm-clp command works only on platforms that support one of the following adapters: the Enhanced ATM Port Adapter (PA-A3), the ATM Inverse Multiplexer over ATM Port Adapter with eight T1 ports (PA-A3-8T1IMA), or the ATM Inverse Multiplexer over ATM Port Adapter with eight E1 ports (PA-A3-8E1IMA). For more information, refer to the documentation for your specific router.

A policy map containing the set atm-clp command can be attached as an output policy only. The set atm-clp command does not support packets that originate from the router.

The following example shows how to set the CLP bit by using the set atm-clp command in a policy map:

Router(config)# class-map ip-precedence

Router(config-cmap)# match ip precedence 0 1

Router(config-cmap)# exit

Router(config)# policy-map atm-clp-set

Router(config-pmap)# class ip-precedence

Router(config-pmap-c)# set atm-clp

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# interface atm 1/0/0.1

Router(config-if)# service-policy output policy1 

Related Commands

set cos

To set the Layer 2 class of service (CoS) value of an outgoing packet, use the set cos command in policy-map class configuration mode. To remove a specific CoS value setting, use the no form of this command.

set cos {cos-value | from-field [table table-map-name]}

no set cos {cos-value | from-field [table table-map-name]}

Cisco 10000 Series Router

set cos cos-value

Syntax Description

Command Default

No CoS value is set for the outgoing packet.

Command Modes

Policy-map class configuration

Command History

Usage Guidelines

CoS packet marking is supported only in the Cisco Express Forwarding switching path.

The set cos command should be used by a router if a user wants to mark a packet that is being sent to a switch. Switches can leverage Layer 2 header information, including a CoS value marking.

The set cos command can be used only in service policies that are attached in the output direction of an interface. Packets entering an interface cannot be set with a CoS value.

The match cos and set cos commands can be used together to allow routers and switches to interoperate and provide quality of service (QoS) based on the CoS markings.

Layer 2 to Layer 3 mapping can be configured by matching on the CoS value because switches already can match and set CoS values. If a packet that needs to be marked to differentiate user-defined QoS services is leaving a router and entering a switch, the router should set the CoS value of the packet because the switch can process the Layer 2 header.

Using This Command with the Enhanced Packet Marking Feature

You can use this command as part of the Enhanced Packet Marking feature to specify the "from-field" packet-marking category to be used for mapping and setting the CoS value. The "from-field" packet-marking categories are as follows:

•Precedence

•Differentiated services code point (DSCP)

If you specify a "from-field" category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the "from-field" category as the CoS value. For instance, if you configure the set cos precedence command, the precedence value will be copied and used as the CoS value.

You can do the same for the DSCP marking category. That is, you can configure the set cos dscp command, and the DSCP value will be copied and used as the CoS value.

Note If you configure the set cos dscp command, only the first three bits (the class selector bits) of the DSCP field are used.

Examples

In the following example, the policy map called "cos-set" is created to assign different CoS values for different types of traffic. This example assumes that the class maps called "voice" and "video-data" have already been created.

Router(config)# policy-map cos-set 
Router(config-pmap)# class voice 
Router(config-pmap-c)# set cos 1 
Router(config-pmap-c)# exit 
Router(config-pmap)# class video-data 
Router(config-pmap-c)# set cos 2 
Router(config-pmap-c)# end

Enhanced Packet Marking Example

In the following example, the policy map called "policy-cos" is created to use the values defined in a table map called "table-map1". The table map called "table-map1" was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.

In this example, the setting of the CoS value is based on the precedence value defined in "table-map1":

Router(config)# policy-map policy-cos 
Router(config-pmap)# class class-default 
Router(config-pmap-c)# set cos precedence table table-map1

Router(config-pmap-c)# end

Note The set cos command is applied when you create a service policy in QoS policy-map configuration mode and attach the service policy to an interface or ATM virtual circuit (VC). For information on attaching a service policy, refer to the "Modular Quality of Service Command-Line Interface Overview" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.

Related Commands

set cos cos-inner (policy-map configuration)

To set the 802.1Q prioritization bits in the trunk VLAN tag of a QinQ-translated outgoing packet with the priority value from the inner customer-edge VLAN tag, use the set cos cos-inner command in policy-map class configuration mode. To return to the default settings, use the no form of this command.

set cos cos-inner

no set cos cos-inner

Syntax Description

This command has no arguments or keywords.

Command Default

P bits are copied from the outer provider-edge VLAN tag.

Command Modes

Policy-map class configuration

Command History

Usage Guidelines

This command is supported on the Gigabit Ethernet WAN interfaces on Cisco 7600 series routers that are configured with an Optical Service Module (OSM)-2+4GE-WAN+ OSM module only.

OSMs are not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.

The 802.1P prioritization bits are used in the VLAN tag for QoS processing.

When the router copies the double-tagged QinQ packets to the destination interface, by default it uses the P bits from the outer (provider) VLAN tag. To preserve the P bits that are in the inner (customer) VLAN tag, use the set cos cos-inner command.

For the set cos cos-inner command to be effective, you must configure the appropriate interface or subinterface as a trusted interface using the mls qos trust command. Otherwise, the interface or subinterface defaults to being untrusted, where the Layer 2 interface zeroes out the P bits of the incoming packets before the set cos cos-inner command can copy them to the outer VLAN tag.

The set cos cos-inner command is supported only for the subinterfaces that are configured with an inner (customer) VLAN. The set cos cos-inner command is not supported for the subinterfaces that use the out-range keyword on the bridge-domain (subinterface configuration) command or that are not configured with any form of the bridge-domain (subinterface configuration) command.

This behavior remains when you configure the set cos cos-inner command on a policy that is applied to a main interface. The set cos cos-inner command affects the subinterfaces that are configured with a specific inner VLAN but it does not affect the subinterfaces that are not configured with any VLAN or that are configured with the out-range keyword.

Examples

This example shows how to configure a policy map for voice traffic that uses the P bits from the inner VLAN tag:

Router(config-cmap)# set cos cos-inner 

This example shows how to configure the default policy map class to reset to its default value:

Router(config-cmap)# no set cos cos-inner 

This example shows the system message that appears when you attempt to apply a policy to a subinterface that is configured with the bridge-domain (subinterface configuration) command:

Router(config-if)# bridge-vlan 32 dot1q-tunnel out-range 

Router(config-if)# service-policy output cos1 

%bridge-vlan 32 does not have any inner-vlan configured. 'set cos cos-inner' is not 
supported

Related Commands

set cos-inner

To mark the inner class of service field in a bridged frame, use the set cos-inner command in policy-map class configuration mode. To remove marking of the inner CoS field, use the no form of this command.

set cos-inner cos-value

no set cos-inner cos-value

Syntax Description

Defaults

No default behavior or values.

Command Modes

Policy-map class configuration

Command History

Usage Guidelines

This command was introduced in Cisco IOS Release 12.2(33)SRA to support marking of the inner CoS value when using multipoint bridging (MPB) features on the Enhanced FlexWAN module, and when using MPB features on SPAs with the Cisco 7600 SIP-200 and Cisco 7600 SIP-400 on the Cisco 7600 series router.

This command is not supported on the Cisco 7600 SIP-600.

On the Cisco 7600 SIP-200, this command is not supported with the set cos command on the same interface.

For more information about QoS and the forms of marking commands supported by the SIPs on the Cisco 7600 series router, refer to the Cisco 7600 Series SIP, SSC, and SPA Software Configuration Guide.

Examples

The following example shows configuration of a QoS class that filters all traffic matching on VLAN 100 into a class named "vlan-inner-100." The configuration shows the definition of a policy-map (also named "vlan-inner-100") that marks the inner CoS with a value of 3 for traffic in the vlan-inner-100 class. Since marking of the inner CoS value is only supported with bridging features, the configuration also shows the service policy being applied as an output policy to a serial SPA interface that bridges traffic into VLAN 100 using the bridge-domain command:

Router(config)# class-map match-all vlan-inner-100

Router(config-cmap)# match vlan inner 100

Router(config-cmap)# exit

Router(config)# policy-map vlan-inner-100

Router(config-pmap)# class vlan-inner-100

Router(config-pmap-c)# set cos-inner 3

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# interface serial3/0/0

Router(config-if)# no ip address

Router(config_if)# encapsulation ppp

Router(config-if)# bridge-domain 100 dot1q

Router(config-if)# service-policy output vlan-inner-100

Router(config-if)# shutdown

Router(config-if)# no shutdown

Router(config-if)# end

Related Commands

set cos-inner cos

To copy the outer COS to the inner COS for double-tagged packets, use the set cos-inner cos command in policy-map class configuration mode. To remove the outer COS copied to the inner COS for double-tagged packets, use the no form of this command.

set cos-inner cos cos-value

no set cos-inner cos cos-value

Syntax Description

Defaults

No default behavior or values.

Command Modes

Policy-map class configuration

Command History

Usage Guidelines

This command was introduced in Cisco IOS Release 12.2(33)SRB and is limited to policies that are applied to the EVC service instances.

For classification, the reference to the outer and inner tags is made to the frames as seen on the wire - that is, for ingress frames, tags prior to the "rewrite", while the for egress, it is after the "rewrite" of the tags, if any.

For marking, the reference to the outer COS at the ingress is to the DBUS-COS and reference to the inner is to the COS in the first tag on the frame; while, at the egress, the reference to outer and inner COS is to the ones in the frame.

Examples

The following example matches on outer COS 3 and 4 and copies the outer COS to the inner COS.

Router(config)# class-map cos3_4        

Router(config-cmap)# match cos 3 4

Router(config)# policy-map mark-it-in

Router(config-pmap)# class cos3_4 

Router(config-pmap-c)# set cos-inner cos 

Related Commands

set discard-class

To mark a packet with a discard-class value, use the set discard-class command in QoS policy-map configuration mode. To prevent the discard-class value of a packet from being altered, use the no form of this command.

set discard-class value

no set discard-class value

Syntax Description

Command Default

If you do not enter this command, the packet has a discard-class value of 0.

Command Modes

QoS policy-map configuration

Command History

Usage Guidelines

The discard class value indicates the discard portion of the PHB. Use the set discard-class command only in DiffServ Tunneling Pipe mode. The discard class value is required when the input PHB marking will be used to classify packets on the output interface.

You can also use this command to specify the type of traffic that will be dropped when there is congestion.

Cisco 10000 Series Router

This command is supported only on the ESR-PRE2.

Examples

The following example shows that traffic will be set to the discard-class value of 2:

set discard-class 2

Related Commands

set dscp

To mark a packet by setting the differentiated services code point (DSCP) value in the type of service (ToS) byte, use the set dscp command in QoS policy-map class configuration mode. To remove a previously set DSCP value, use the no form of this command.

set dscp {dscp-value | from-field [table table-map-name]}

no set dscp {dscp-value | from-field [table table-map-name]}

Syntax Description

Command Default

The DSCP value in the ToS byte is not set.

Command Modes

QoS policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

Once the DSCP bit is set, other quality of service (QoS) features can then operate on the bit settings.

DSCP and Precedence Values Are Mutually Exclusive

The set dscp command cannot be used with the set precedence command to mark the same packet. The two values, DSCP and precedence, are mutually exclusive. A packet can have one value or the other, but not both.

Precedence Value and Queueing

The network gives priority (or some type of expedited handling) to marked traffic. Typically, you set the precedence value at the edge of the network (or administrative domain); data then is queued according to the precedence. Weighted fair queueing (WFQ) can speed up handling for high-precedence traffic at congestion points. Weighted Random Early Detection (WRED) ensures that high-precedence traffic has lower loss rates than other traffic during times of congestion.

Use of the "from-field" Packet-marking Category

If you are using this command as part of the Enhanced Packet Marking feature, it can specify the "from-field" packet-marking category to be used for mapping and setting the DSCP value. The "from-field" packet-marking categories are as follows:

•Class of service (CoS)

•QoS group

If you specify a "from-field" category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the "from-field" category as the DSCP value. For instance, if you configure the set dscp cos command, the CoS value will be copied and used as the DSCP value.

Note The CoS field is a three-bit field, and the DSCP field is a six-bit field. If you configure the set dscp cos command, only the three bits of the CoS field will be used.

If you configure the set dscp qos-group command, the QoS group value will be copied and used as the DSCP value.

The valid value range for the DSCP is a number from 0 to 63. The valid value range for the QoS group is a number from 0 to 99. Therefore, when configuring the set dscp qos-group command, note the following points:

•If a QoS group value falls within both value ranges (for example, 44), the packet-marking value will be copied and the packets will be marked.

•If QoS group value exceeds the DSCP range (for example, 77), the packet-marking value will not be copied and the packet will not be marked. No action is taken.

Set DSCP Values in IPv6 Environments

When this command is used in IPv6 environments, the default match occurs on both IP and IPv6 packets. However, the actual packets set by this function are only those that meet the match criteria of the class map containing this function.

Set DSCP Values for IPv6 Packets Only

To set DSCP values for IPv6 values only, you must also use the match protocol ipv6 command. Without that command, the precedence match defaults to match both IPv4 and IPv6 packets.

Set DSCP Values for IPv4 Packets Only

To set DSCP values for IPv4 values only, you must use the appropriate match ip command. Without this command, the class map may match both IPv6 and IPv4 packets, depending on the other match criteria, and the DSCP values may act upon both types of packets.

Examples

Packet-marking Values and Table Map

In the following example, the policy map called "policy1" is created to use the packet-marking values defined in a table map called "table-map1". The table map was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.

In this example, the DSCP value will be set according to the CoS value defined in the table map called "table-map1".

Router(config)# policy-map policy1 
Router(config-pmap)# class class-default 
Router(config-pmap-c)# set dscp cos table table-map1

Router(config-pmap-c)# end

The set dscp command is applied when you create a service policy in QoS policy-map configuration mode. This service policy is not yet attached to an interface. For information on attaching a service policy to an interface, see the "Modular Quality of Service Command-Line Interface" section of the Cisco IOS Quality of Service Solutions Configuration Guide.

Related Commands

set fr-de

To change the discard eligible (DE) bit setting in the address field of a Frame Relay frame to 1 for all traffic leaving an interface, use the set fr-de command in policy-map class command. To remove the DE bit setting, use the no form of this command.

set fr-de

no set fr-de

Syntax Description

This command has no arguments or keywords.

Defaults

The DE bit is usually set to 0. This command changes the DE bit setting to 1.

Command Modes

Policy-map class

Command History

Usage Guidelines

To disable this command in a traffic policy, use the no set fr-de command in policy-map class configuration mode of the traffic policy.

If the DE bit is already set to 1, no changes are made to the frame.

Examples

The following example shows how to set the DE bit using the set fr-de command in the traffic policy. The router sets the DE bit of outbound packets belonging to the ip-precedence class.

Router(config)# class-map ip-precedence

Router(config-cmap)# match ip precedence 0 1

Router(config-cmap)# exit

Router(config)# policy-map set-de

Router(config-pmap)# class ip-precedence

Router(config-pmap-c)# set fr-de

Router(config-pmap-c)# exit

Router(config-pmap)# exit

Router(config)# interface serial 1/0/0

Router(config-if)# no ip address

Router(config-if)# encapsulation frame-relay

Router(config-if)# interface serial 1/0/0.1

Router(config-subif)# ip address 10.1.1.1 255.255.255.252

Router(config-subif)# no ip directed-broadcast

Router(config-subif)# service-policy output set-de

Related Commands

set ip dscp

The set ip dscp command is replaced by the set dscp command. See the set dscp command for more information.

set ip dscp (policy-map configuration)

To mark a packet by setting the IP differentiated services code point (DSCP) value in the type of service (ToS) byte, use the set ip dscp command in policy-map configuration mode. To remove a previously set IP DSCP value, use the no form of this command.

set ip dscp ip-dscp-value

no set ip dscp ip-dscp-value

Syntax Description

Command Default

This command has no default settings.

Command Modes

Policy-map configuration

Command History

Usage Guidelines

You can enter reserved keywords EF (expedited forwarding), AF11 (assured forwarding class AF11), and AF12 (assured forwarding class AF12) instead of numeric values for ip-dscp-value.

After the IP DSCP bit is set, other quality of service (QoS) features can operate on the bit settings.

You cannot mark a packet by the IP precedence using the set ip precedence (policy-map configuration) command and then mark the same packet with an IP DSCP value using the set ip dscp command.

The network gives priority (or some type of expedited handling) to marked traffic. Typically, you set IP precedence at the edge of the network (or administrative domain); data is queued based on the precedence. Weighted Fair Queueing (WFQ) can speed up handling for high-precedence traffic at congestion points. Weighted Random Early Detection (WRED) ensures that high-precedence traffic has lower loss rates than other traffic during traffic congestion.

The set ip precedence (policy-map configuration) command is applied when you create a service policy in QoS policy-map configuration mode. This service policy is not attached to an interface or to an ATM virtual circuit. See the service-policy command for information on attaching a service policy to an interface.

When configuring policy-map class actions, note the following:

•For hardware-switched traffic, Policy Feature Card (PFC) QoS does not support the bandwidth, priority, queue-limit, or random-detect policy-map class commands. You can configure these commands because they can be used for software-switched traffic.

•PFC QoS does not support the set mpls or set qos-group policy-map class commands.

•PFC QoS supports the set ip dscp and set ip precedence policy-map class commands (see the "Configuring Policy Map Class Marking" section in the Cisco 7600 Series Router Cisco IOS Software Configuration Guide).

•You cannot do all three of the following in a policy-map class:

–Mark traffic with the set ip dscp or set ip precedence (policy-map configuration) commands

–Configure the trust state

–Configure policing

In a policy-map class, you can either mark traffic with the set ip dscp or set ip precedence (policy-map configuration) commands or do one or both of the following:

–Configure the trust state

–Configure policing

Examples

This example shows how to set the IP DSCP ToS byte to 8 in the policy map called policy1:

Router(config)# policy-map policy1 
Router(config-cmap)# class class1 
Router(config-cmap)# set ip dscp 8

All packets that satisfy the match criteria of class1 are marked with the IP DSCP value of 8. How packets that are marked with the IP DSCP value of 8 are treated is determined by the network configuration.

This example shows that after you configure the settings that are shown for voice packets at the edge of the network, all intermediate routers are then configured to provide low-latency treatment to the voice packets:

Router(config)# class-map voice

Router(config-cmap)# match ip dscp ef

Router(config)# policy qos-policy

Router(config-cmap)# class voice

Router(config-cmap)# priority 24

Related Commands

set ip dscp tunnel

To set the differentiated services code point (DSCP) value in the tunnel header of a Layer 2 Tunnel Protocol Version 3 (L2TPv3) or Generic Routing Encapsulation (GRE) tunneled packet for tunnel marking, use the set ip dscp tunnel command in policy-map class configuration mode. To disable this functionality, use the no form of this command.

set ip dscp tunnel dscp-value

no set ip dscp tunnel dscp-value

Syntax Description

Command Default

The DSCP value is not set.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

It is possible to configure L2TPv3 (or GRE) tunnel marking and the ip tos command at the same time. However, Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC) (L2TPv3 or GRE) tunnel marking has higher priority over ip tos commands, meaning that tunnel marking always rewrites the IP header of the tunnel packet and overwrites the values set by ip tos commands. The order of enforcement is as follows when these commands are used simultaneously:

1. set ip dscp tunnel or set ip precedence tunnel (L2TPv3 or GRE tunnel marking)

2. ip tos reflect

3. ip tos tos-value

This is the designed behavior. We recommend that you configure only L2TPv3 (or GRE) tunnel marking and reconfigure any peers configured with the ip tos command to use L2TPv3 (or GRE) tunnel marking.

Note For Cisco IOS Release 12.4(15)T2, marking GRE-tunneled packets is supported only on platforms equipped with a Cisco RPM-XF.

Examples

The following example shows the set ip dscp tunnel command used in a tunnel marking configuration. In this example, a class map called "class-cl" has been configured to match traffic on the basis of the Frame Relay discard eligible (DE) bit setting. Also, a policy map called "policy1" has been created within which the set ip dscp tunnel command has been configured.

Router> enable

Router# configure terminal

Router(config)# class-map class-c1 

Router(config-cmap)# match fr-de

Router(config-cmap)# exit

Router(config)# policy-map policy1

Router(config-pmap)# class tunnel

Router(config-pmap-c)# set ip dscp tunnel 5

Router(config-pmap-c)# end

Note You must still attach a policy map to an interface or ATM PVC using the service-policy command. Policy maps with this tunnel marking are not accepted in the output direction. For more information about attaching a policy map to an interface or ATM PVC, see the "Applying QoS Features Using the MQC" module of the Cisco IOS Quality of Service Solutions Configuration Guide.

Related Commands

set ip precedence (policy-map configuration)

To set the precedence value in the IP header, use the set ip precedence command in policy-map configuration mode. To leave the precedence value at the current setting, use the no form of this command.

set ip precedence ip-precedence-value

no set ip precedence

Syntax Description

Command Default

This command is disabled by default.

Command Modes

Policy-map configuration

Command History

Usage Guidelines

Table 33 lists the value definitions for precedence values in the IP header. They are listed from least to most important.

After the IP precedence bits are set, other quality of service (QoS) features, such as Weighted Fair Queueing (WFQ) and Weighted Random Early Detection (WRED), operate on the bit settings.

The network priorities (or some type of expedited handling) mark traffic through the application of WFQ or WRED at points downstream in the network. Typically, you set IP precedence at the edge of the network (or administrative domain); data is queued based on the precedence. WFQ can speed up handling for certain precedence traffic at congestion points. WRED can ensure that certain precedence traffic has lower loss rates than other traffic during traffic congestion.

The set ip precedence command is applied when you create a service policy in policy-map configuration mode. This service policy is not attached to an interface or to an ATM virtual circuit. See the service-policy command for information on attaching a service policy to an interface.

Examples

This example shows how to set the IP precedence to 5 for packets that satisfy the match criteria of the class map called class1:

Router(config)# policy-map policy1 
Router(config-pmap)# class class1 
Router(config-pmap-c)# set ip precedence 5

All packets that satisfy the match criteria of class1 are marked with the IP precedence value of 5. How packets that are marked with the IP-precedence value of 5 are treated is determined by the network configuration.

Related Commands

set ip precedence (policy-map)

The set ip precedence (policy-map) command is replaced by the set precedence command. See the set precedence command for more information.

set ip precedence (route-map)

To set the precedence value (and an optional IP number or IP name) in the IP header, use the set ip precedence command in route-map configuration mode. To leave the precedence value unchanged, use the no form of this command.

set ip precedence [number | name]

no set ip precedence

Syntax Description

Command Default

Disabled

Command Modes

Route-map configuration

Command History

Usage Guidelines

Table 34 lists the values for the number argument and the corresponding name argument for precedence values in the IP header. They are listed from least to most important.

You can set the precedence using either a number or the corresponding name. Once the IP Precedence bits are set, other QoS services such as weighted fair queueing (WFQ) and Weighted Random Early Detection (WRED) then operate on the bit settings.

The network gives priority (or some type of expedited handling) to marked traffic through the application of WFQ or WRED at points downstream in the network. Typically, you set IP Precedence at the edge of the network (or administrative domain); data then is queued based on the precedence. WFQ can speed up handling for certain precedence traffic at congestion points. WRED can ensure that certain precedence traffic has lower loss rates than other traffic during times of congestion.

The mapping from arguments such as routine and priority to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. You can define the meaning of a precedence value by enabling other features that use the value. In the case of the high-end Internet QoS available from Cisco, IP Precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network.

Use the route-map (IP) global configuration command with the match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. Each route-map command has an associated list of match and set commands. The match commands specify the match criteria—the conditions under which redistribution or policy routing is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.

The set route-map configuration commands specify the redistribution set actions to be performed when all of the match criteria of a route map are met.

Examples

The following example sets the IP Precedence to 5 (critical) for packets that pass the route map match:

interface serial 0

 ip policy route-map texas

route-map texas

match length 68 128

set ip precedence 5

Related Commands

set ip precedence tunnel

To set the precedence value in the header of a Layer 2 Tunnel Protocol Version 3 (L2TPv3) or Generic Routing Encapsulation (GRE) tunneled packet for tunnel marking, use the set ip precedence tunnel command in policy-map class configuration mode. To disable this functionality, use the no form of this command.

set ip precedence tunnel precedence-value

no set ip precedence tunnel precedence-value

Syntax Description

Command Default

The precedence value is not set.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

It is possible to configure L2TPv3 (or GRE) tunnel marking and the ip tos command at the same time. However, Modular Quality of Service (QoS) Command-Line Interface (CLI) (MQC) (L2TPv3 or GRE) tunnel marking has higher priority over ip tos commands, meaning that tunnel marking always rewrites the IP header of the tunnel packet and overwrites the values set by ip tos commands. The order of enforcement is as follows when these commands are used simultaneously:

1. set ip dscp tunnel or set ip precedence tunnel (L2TPv3 or GRE tunnel marking)

2. ip tos reflect

3. ip tos tos-value

This is the designed behavior. We recommend that you configure only L2TPv3 (or GRE) tunnel marking and reconfigure any peers configured with the ip tos command to use L2TPv3 (or GRE) tunnel marking.

Note For Cisco IOS Release 12.4(15)T2, marking GRE-tunneled packets is supported only on platforms equipped with a Cisco RPM-XF.

Examples

The following example shows the set ip precedence tunnel command used in a tunnel marking configuration. In this example, a class map called "MATCH_FRDE" has been configured to match traffic on the basis of the Frame Relay discard eligible (DE) bit setting. Also, a policy map called "policy1" has been created within which the set ip precedence tunnel command has been configured.

Router> enable

Router# configure terminal

Router(config)# class-map MATCH_FRDE 

Router(config-cmap)# match fr-de

Router(config-cmap)# exit

Router(config)# policy-map policy1

Router(config-pmap)# class tunnel

Router(config-pmap-c)# set ip precedence tunnel 7

Router(config-pmap-c)# end

Note You must still attach a policy map to an interface or ATM PVC using the service-policy command. Policy maps with this tunnel marking are not accepted in the output direction. For more information about attaching a policy map to an interface or ATM PVC, see the "Applying QoS Features Using the MQC" module of the Cisco IOS Quality of Service Solutions Configuration Guide.

Related Commands

set ip tos (route-map)

To set the type of service (ToS) bits in the header of an IP packet, use the set ip tos command in route-map configuration mode. To leave the ToS bits unchanged, use the no form of this command.

set ip tos [tos-bit-value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal]

no set ip tos

Syntax Description

Command Default

Disabled

Command Modes

Route-map configuration

Command History

Usage Guidelines

This command allows you to set four bits in the ToS byte header. Table 35 shows the format of the four bits in binary form.

The T3 bit sets the delay. Setting T3 to 0 equals normal delay, and setting it to 1 equals low delay.

The T2 bit sets the throughput. Setting this bit to 0 equals normal throughput, and setting it to 1 equals maximum throughput. Similarly, the T1 and T0 bits set reliability and cost, respectively. Therefore, as an example, if you want to set a packet with the following requirements:

minimum delay T3 = 1

normal throughput T2 = 0

normal reliability T1 = 0

minimum monetary cost T0 = 1

You would set the ToS to 9, which is 1001 in binary format.

Use the route-map (IP) global configuration command with the match and set (route-map) configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. Each route-map command has an associated list of match and set commands. The match commands specify the match criteria—the conditions under which redistribution or policy routing is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.

The set (route-map) commands specify the redistribution set actions to be performed when all of the match criteria of a route map are met.

Examples

The following example sets the IP ToS bits to 8 (minimum delay as shown in Table 35) for packets that pass the route-map match:

interface serial 0 

 ip policy route-map texas 

!

route-map texas 

  match length 68 128 

  set ip tos 8 

! 

Related Commands

set precedence

To set the precedence value in the packet header, use the set precedence command in policy-map class configuration mode. To remove the precedence value, use the no form of this command.

Supported Platforms Other Than Cisco 10000 Series Routers

set precedence {precedence-value | from-field [table table-map-name]}

no set precedence {precedence-value | from-field [table table-map-name]}

Cisco 10000 Series Routers

set precedence precedence-value

no set precedence precedence-value

Syntax Description

Command Default

Disabled

Command Modes

Policy-map class configuration

Command History

Usage Guidelines

Command Compatibility

If a router is loaded with an image from this version (that is, Cisco IOS Release 12.2(13)T) that contained an old configuration, the set ip precedence command is still recognized. However, the set precedence command will be used in place of the set ip precedence command.

The set precedence command cannot be used with the set dscp command to mark the same packet. The two values, DSCP and precedence, are mutually exclusive. A packet can be one value or the other, but not both.

Bit Settings

Once the precedence bits are set, other quality of service (QoS) features such as weighted fair queueing (WFQ) and Weighted Random Early Detection (WRED) then operate on the bit settings.

Precedence Value

The network gives priority (or some type of expedited handling) to marked traffic through the application of WFQ or WRED at points downstream in the network. Typically, you set the precedence value at the edge of the network (or administrative domain); data then is queued according to the specified precedence. WFQ can speed up handling for certain precedence traffic at congestion points. WRED can ensure that certain precedence traffic has lower loss rates than other traffic during times of congestion.

The set precedence command cannot be used with the set dscp command to mark the same packet. The two values, differentiated services code point (DSCP) and precedence, are mutually exclusive. A packet can have one value or the other, but not both.

Using This Command with the Enhanced Packet Marking Feature

If you are using this command as part of the Enhanced Packet Marking feature, you can use this command to specify the "from-field" packet-marking category to be used for mapping and setting the precedence value. The "from-field" packet-marking categories are as follows:

•CoS

•QoS group

If you specify a "from-field" category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the "from-field" category as the precedence value. For instance, if you configure the set precedence cos command, the CoS value will be copied and used as the precedence value.

You can do the same for the QoS group-marking category. That is, you can configure the set precedence qos-group command, and the QoS group value will be copied and used as the precedence value.

The valid value range for the precedence value is a number from 0 to 7. The valid value range for the QoS group is a number from 0 to 99. Therefore, when configuring the set precedence qos-group command, note the following points:

•If a QoS group value falls within both value ranges (for example, 6), the packet-marking value will be copied and the packets will be marked.

•If QoS group value exceeds the precedence range (for example, 10), the packet-marking value will not be copied, and the packet will not be marked. No action is taken.

Precedence Values in IPv6 Environments

When this command is used in IPv6 environments it can set the value in both IPv4 and IPv6 packets. However, the actual packets set by this function are only those that meet the match criteria of the class-map containing this function.

Setting Precedence Values for IPv6 Packets Only

To set the precedence values for IPv6 packets only, the match protocol ipv6 command must also be used in the class-map that classified packets for this action. Without the match protocol ipv6 command, the class-map may classify both IPv6 and IPv4 packets, (depending on other match criteria) and the set precedence command will act upon both types of packets.

Setting Precedence Values for IPv4 Packets Only

To set the precedence values for IPv4 packets only, use a command involving the ip keyword like the match ip precedence or match ip dscp command or include the match protocol ip command along with the others in the class map. Without the additional ip keyword, the class-map may match both IPv6 and IPv4 packets (depending on the other match criteria) and the set precedence or set dscp command may act upon both types of packets.

Examples

In the following example, the policy map named policy-cos is created to use the values defined in a table map named table-map1. The table map named table-map1 was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.

In this example, the precedence value will be set according to the CoS value defined in table-map1.

Router(config)# policy-map policy-cos 
Router(config-pmap)# class class-default 
Router(config-pmap-c)# set precedence cos table table-map1

Router(config-pmap-c)# end

The set precedence command is applied when you create a service policy in QoS policy-map configuration mode. This service policy is not yet attached to an interface or to an ATM virtual circuit. For information on attaching a service policy to an interface, refer to the "Modular Quality of Service Command-Line Interface Overview" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.

Related Commands

set qos-group

To set a quality of service (QoS) group identifier (ID) that can be used later to classify packets, use the set qos-group command in policy-map class configuration mode. To remove the group ID, use the no form of this command.

Supported Platforms Except the Cisco 10000 Series Router

set qos-group {group-id | from-field [table table-map-name]}

no set qos-group {group-id | from-field [table table-map-name]}

Cisco 10000 Series Router

set qos-group group-id

no set qos-group group-id

Syntax Description

Command Default

No group ID is specified.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

The set qos-group command allows you to associate a group ID with a packet. The group ID can be used later to classify packets into QoS groups based as prefix, autonomous system, and community string.

A QoS group and discard class are required when the input per-hop behavior (PHB) marking will be used for classifying packets on the output interface.

Using This Command with the Enhanced Packet Marking Feature

If you are using this command as part of the Enhanced Packet Marking feature, you can use this command to specify the "from-field" packet-marking category to be used for mapping and setting the precedence value.

If you specify a "from-field" category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the "from-field" category as the precedence value. For instance, if you enter set qos-group precedence, the precedence value will be copied and used as the QoS group value.

A packet is marked with a QoS group value only while it is being processed within the router. The QoS group value is not included in the packet's header when the packet is transmitted over the output interface. However, the QoS group value can be used to set the value of a Layer 2 or Layer 3 field that is included as part of the packet's headers (such as the MPLS EXP, CoS, and DSCP fields).

Note The set qos-group cos and set qos-group precedence commands are equivalent to the mls qos trust cos and mls qos trust prec commands.

Tip The set qos-group command cannot be applied until you create a service policy in policy-map configuration mode and then attach the service policy to an interface or ATM virtual circuit (VC). For information on attaching a service policy, refer to the "Modular Quality of Service Command-Line Interface Overview" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.

Examples

The following example shows how to set the QoS group to 1 for all packets that match the class map called class 1. These packets are then rate limited on the basis of the QoS group ID.

Router(config)# policy-map policy1

Router(config-pmap)# class class1

Router(config-pmap-c)# set qos-group 1

Router(config-pmap-c)# end

The following example shows how to set the QoS group value based on the packet's original 802.1P CoS value:

Router(config)# policy map policy1 

Router(config-pmap)# class class-default 

Router(config-pmap-c)# set qos-group cos 

Router(config-pmap-c)# end 

Enhanced Packet Marking Example

The following example shows how to set the QoS group value based on the values defined in a table map called table-map1. This table map is configured in a policy map called policy1. Policy map policy1 converts and propagates the QoS value according to the values defined in table-map1.

In this example, the QoS group value will be set according to the precedence value defined in table-map1.

Router(config)# policy map policy1

Router(config-pmap)# class class-default

Router(config-pmap-c)# set qos-group precedence table table-map1

Router(config-pmap-c)# end

Related Commands

set vlan inner

To mark the bridged packets in the permanent virtual circuit (PVC) with a specific virtual LAN identifier (VLAN ID), use the set vlan inner command in policy-map class configuration mode. To disable this configuration, use the no form of this command.

set vlan inner vlan-number

no set vlan inner vlan-number

Syntax Description

Command Default

The bridged packets are marked with the default VLAN ID as configured using the bridge-dot1q encap command.

Command Modes

Policy-map class configuration mode (config-pmap-c)

Command History

Usage Guidelines

Although multiple VLANs are allowed under a single PVC, the locally generated packets including the Address Resolution Protocol (ARP) packets are sent out with the class default VLAN ID only. The set vlan inner command must be applied within the class default.

Examples

The following example shows how to mark the inner VLAN ID as 2 for bridged packets in the 802.1Q tag:

Router(config)# policy-map egress-policy

Router(config-pmap)# class egress

Router(config-pmap-c)# set vlan inner 2

Related Commands

shape

To specify average or peak rate traffic shaping, use the shape command in class-map configuration mode. To remove traffic shaping, use the no form of this command.

shape {average | peak} cir [bc] [be]

no shape {average | peak} cir [bc] [be]

Syntax Description

Command Default

Average or peak rate traffic shaping is not specified.

Command Modes

Class-map configuration (config-cmap)

Command History

Usage Guidelines

Traffic shaping limits the rate of transmission of data. In addition to using a specifically configured transmission rate, you can use Generic Traffic Shaping (GTS) to specify a derived transmission rate based on the level of congestion.

You can specify two types of traffic shaping; average rate shaping and peak rate shaping. Average rate shaping limits the transmission rate to the CIR. Using the CIR ensures that the average amount of traffic being sent conforms to the rate expected by the network.

Peak rate shaping configures the router to send more traffic than the CIR. To determine the peak rate, the router uses the following formula:

peak rate = CIR(1 + Be / Bc)

where:

•Be is the Excess Burst size.

•Bc is the Committed Burst size.

Peak rate shaping allows the router to burst higher than average rate shaping. However, using peak rate shaping, the traffic sent above the CIR (the delta) could be dropped if the network becomes congested.

If your network has additional bandwidth available (over the provisioned CIR) and the application or class can tolerate occasional packet loss, that extra bandwidth can be exploited through the use of peak rate shaping. However, there may be occasional packet drops when network congestion occurs. If the traffic being sent to the network must strictly conform to the configured network provisioned CIR, then you should use average traffic shaping.

Examples

The following example shows how to configure average rate shaping to ensure a bandwidth of 256 kbps:

shape average 256000

The following example shows how to configure peak rate shaping to ensure a bandwidth of 300 kbps but allow throughput up to 512 kbps if enough bandwidth is available on the interface:

bandwidth 300

shape peak 512000

Related Commands

shape (percent)

To specify average or peak rate traffic shaping on the basis of a percentage of bandwidth available on an interface, use the shape command in policy-map class configuration mode. To remove traffic shaping, use the no form of this command.

shape {average | peak} percent percentage [sustained-burst-in-msec ms] [be excess-burst-in-msec ms] [bc committed-burst-in-msec ms]

no shape {average | peak} percent percentage [sustained-burst-in-msec ms] [be excess-burst-in-msec ms] [bc committed-burst-in-msec ms]

Syntax Description

Command Default

The default bc and be is 4 ms.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

Committed Information Rate

This command calculates the committed information rate (CIR) on the basis of a percentage of the available bandwidth on the interface. Once a policy map is attached to the interface, the equivalent CIR value in bits per second (bps) is calculated on the basis of the interface bandwidth and the percent value entered with this command. The show policy-map interface command can then be used to verify the CIR bps value calculated.

The calculated CIR bps rate must be in the range of 8000 and 154,400,000 bps. If the rate is less than 8000 bps, the associated policy map cannot be attached to the interface. If the interface bandwidth changes (for example, more is added), the CIR bps values are recalculated on the basis of the revised amount of bandwidth. If the CIR percentage is changed after the policy map is attached to the interface, the bps value of the CIR is recalculated.

Conform Burst and Peak Burst Sizes in Milliseconds

This command also allows you to specify the values for the conform burst size and the peak burst size in milliseconds. If you want bandwidth to be calculated as a percentage, the conform burst size and the peak burst size must be specified in milliseconds (ms).

The traffic shape converge rate depends on the traffic pattern and the time slice (Tc) parameter, which is directly affected by the bc that you configured. The Tc and the average rate configured are used to calculate bits per interval sustained. Therefore, to ensure that the shape rate is enforced, use a bc that results in a Tc greater than 10 ms.

Hierarchical Policy Maps

The shape (percent) command, when used in "child" (hierarchical) policy maps, is not supported on the Cisco 7500, the Cisco 7200, or lower series routers. Therefore, the shape (percent) command cannot be configured for use in hierarchical policy maps on these routers.

How Bandwidth Is Calculated

The shape (percent) command is often used in conjunction with the bandwidth and priority commands. The bandwidth and priority commands can be used to calculate the total amount of bandwidth available on an entity (for example, a physical interface). When the bandwidth and priority commands calculate the total amount of bandwidth available on an entity, the following guidelines are invoked:

•If the entity is a physical interface, the total bandwidth is the bandwidth on the physical interface.

•If the entity is a shaped ATM permanent virtual circuit (PVC), the total bandwidth is calculated as follows:

–For a variable bit rate (VBR) virtual circuit (VC), the sustained cell rate (SCR) is used in the calculation.

–For an available bit rate (ABR) VC, the minimum cell rate (MCR) is used in the calculation.

For more information on bandwidth allocation, see the "Congestion Management Overview" chapter in the Cisco IOS Quality of Service Solutions Configuration Guide.

Note This command cannot be used with the shape adaptive command.

Examples

The following example configures traffic shaping using an average shaping rate on the basis of a percentage of bandwidth. In this example, 25 percent of the bandwidth has been specified. Additionally, an optional be value and bc value (100 ms and 400 ms, respectively) have been specified.

Router> enable

Router# configure terminal

Router(config)# policy-map policy1

Router(config-pmap)# class-map class1

Router(config-pmap-c)# shape average percent 25 20 ms be 100 ms bc 400 ms

Router(config-pmap-c)# end 

After the policy map and class maps are configured, the policy map is attached to interface as shown in the following example.

Router> enable

Router# configure terminal

Router(config)# interface serial4/0 

Router(config-if)# service-policy input policy1

Router(config-if)# end

Related Commands

shape (policy-map class)

To shape traffic to the indicated bit rate according to the algorithm specified or to enable ATM overhead accounting, use the shape command in policy-map class configuration mode. To remove shaping and leave the traffic unshaped, use the no form of this command.

shape {average | peak} {mean-rate [burst-size [excess-burst-size]] | percent percentage [burst-size ms [excess-burst-size ms]]}

no shape [average | peak]

Cisco 7300 Series Router and Cisco 7600 Series Router

shape [average | peak] mean-rate [burst-size] [excess-burst-size] account {qinq | dot1q} aal5 {subscriber-encapsulation | user-defined offset}

no shape [average | peak] mean-rate [burst-size] [excess-burst-size] account {qinq | dot1q} aal5 {subscriber-encapsulation | user-defined offset}

Cisco 10000 Series Router (PRE1)

shape [average | peak] mean-rate [burst-size] [excess-burst-size] [account {qinq | dot1q} aal5 subscriber-encap]

no shape [average | peak] mean-rate [burst-size] [excess-burst-size] [account {qinq | dot1q} aal5 subscriber-encap]

Cisco 10000 Series Router (PRE2)

shape [average] mean-rate [unit] [burst-size] [excess-burst-size] [account {qinq | dot1q} aal5 subscriber-encapsulation]

no shape [average] mean-rate [unit] [burst-size] [excess-burst-size] [account {qinq | dot1q} aal5 subscriber-encapsulation]

Cisco 10000 Series Router (PRE3)

shape [average] mean-rate [burst-size] [excess-burst-size] account {{qinq | dot1q} {aal5 | aal3} subscriber-encapsulation | user-defined offset [atm]}

no shape [average] mean-rate [burst-size] [excess-burst-size] account {{qinq | dot1q} {aal5 | aal3} subscriber-encapsulation | user-defined offset [atm]}

Syntax Description

Command Default

When the excess burst size (Be) is not configured, the default Be value is equal to the committed burst size (Bc). For more information about burst size defaults, see the "Usage Guidelines" section.

Traffic shaping overhead accounting for ATM is disabled.

Command Modes

Policy-map class configuration (config-pmap-c)

Command History

Usage Guidelines

The measurement interval is the committed burst size (Bc) divided by committed information rate (CIR). Bc cannot be set to 0. If the measurement interval is too large (greater than 128 milliseconds), the system subdivides it into smaller intervals.

If you do not specify the committed burst size (Bc) and the excess burst size (Be), the algorithm decides the default values for the shape entity. The algorithm uses a 4 milliseconds measurement interval, so Bc is CIR * (4 / 1000).

Burst sizes larger than the default committed burst size (Bc) need to be explicitly specified. The larger the Bc, the longer the measurement interval. A long measurement interval may affect voice traffic latency, if applicable.

When the excess burst size (Be) is not configured, the default value is equal to the committed burst size (Bc).

Traffic Shaping on the Cisco 10000 Series Performance Routing Engine

The Cisco 10000 series router does not support the peak keyword.

On the PRE2, you specify a shape rate and a unit for the rate. Valid values for the rate are from 1 to 2488320000 and units are bps, kbps, mbps, gbps. The default unit is kbps. For example:

shape 128000 bps

On the PRE3, you only need to specify a shape rate. Because the unit is always bps on the PRE3, the unit argument is not available. Valid values for the shape rate are from 1000 to 2488320000.

shape 1000

The PRE3 accepts the PRE2 shape command as a hidden command. However, the PRE3 rejects the PRE2 shape command if the specified rate is outside the valid PRE3 shape rate range (1000 to 2488320000).

Traffic Shaping Overhead Accounting for ATM (Cisco 7300 Series Router, Cisco 7600 Series Router, and Cisco 10000 Series Router)

When configuring ATM overhead accounting on the Cisco 7300 series router, the Cisco 7600 series router, or the Cisco 10000 series router, you must specify the BRAS-DSLAM, DSLAM-CPE, and subscriber line encapsulation types. The router supports the following subscriber line encapsulation types:

•snap-rbe

•mux-rbe

•snap-dot1q-rbe

•mux-dot1q-rbe

•snap-pppoa

•mux-pppoa

•snap-1483routed

•mux-1483routed

For hierarchical policies, configure ATM overhead accounting in the following ways:

•Enabled on parent—If you enable ATM overhead accounting on a parent policy, you are not required to enable accounting on the child policy.

•Enabled on child and parent—If you enable ATM overhead accounting on a child policy, then you must enable ATM overhead accounting on the parent policy.

The encapsulation types must match for the child and parent policies.

The user-defined offset values must match for the child and parent policies.

Examples

The following example configures a shape entity with a CIR of 1 Mbps and attaches the policy map called dts-interface-all-action to interface pos1/0/0:

policy-map dts-interface-all-action

 class class-interface-all

  shape average 1000000

interface pos1/0/0

 service-policy output dts-interface-all-action

Traffic Shaping Overhead Accounting for ATM

When a parent policy has ATM overhead accounting enabled for shaping, you are not required to enable accounting at the child level using the police command. In the following configuration example, ATM overhead accounting is enabled for bandwidth on the gaming and class-default class of the child policy map named subscriber_classes and on the class-default class of the parent policy map named subscriber_line. The voip and video classes do not have ATM overhead accounting explicitly enabled. These priority classes have ATM overhead accounting implicitly enabled because the parent policy has ATM overhead accounting enabled. Notice that the features in the parent and child policies use the same encapsulation type.

policy-map subscriber_classes

 class voip

  priority level 1 

  police 8000

 class video

  priority level 2

  police 20000

 class gaming

  bandwidth remaining percent 80 account dot1q aal5 snap-dot1q-rbe

 class class-default

  bandwidth remaining percent 20 account dot1q aal5 snap-dot1q-rbe

policy-map subscriber_line

 class class-default

  shape average 8000 account dot1q aal5 snap-dot1q-rbe