-
Cisco IOS Quality of Service Solutions Command Reference, Release 12.3
-
Introduction for the QoS Command Reference, 12.3
-
Quality of Service Commands, 12.3: a through f
-
Quality of Service Commands, 12.3: ip nbar pdlm through ip rtp priority
-
Quality of Service Commands, 12.3: m through n
-
Quality of Service Commands, 12.3: o through p
-
Quality of Service Commands, 12.3: q through r
-
Quality of Service Commands 12.3: send qdm message through show ip nbar pdlm
-
Quality of Service Commands, 12.3: show ip nbar port-map through show qdm status
-
Quality of Service Commands, 12.3: show queue through vc-hold-queue
-
Table Of Contents
service-policy (policy-map class)
set ip precedence (policy-map)
show atm bundle svc statistics
show frame-relay ip rtp header-compression
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
Defaults
No text messages are sent.
Command Modes
EXEC
Command History
12.1(1)E
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
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-policy
To attach a policy map to an input interface or virtual circuit (VC), or an output interface or VC, to be used as the service policy for that interface or VC, use the service-policy command in interface configuration command. To remove a service policy from an input or output interface or input or output VC, use the no form of this command.
service-policy {input | output} policy-map-name
no service-policy {input | output} policy-map-name
Syntax Description
Defaults
No service policy is specified.
Command Modes
Interface configuration
VC submode (for a standalone VC)
Bundle-vc configuration (for ATM VC bundle members)
Map-class configuration (for Frame Relay VCs)
Command History
Usage Guidelines
You can attach a single policy map to one or more interfaces or one or more VCs to specify the service policy for those interfaces or VCs.
Currently a service policy specifies class-based weighted fair queueing (CBWFQ). The class policies comprising 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 a VC, the aggregate of the configured minimum bandwidths of the classes comprising the policy map must be less than or equal to 75 percent of the interface bandwidth or the bandwidth allocated to the VC.
To enable 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 will 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 not configured, the minimum CIR defaults to half of the CIR.
Configuring CBWFQ on a physical interface is only possible if the interface is in the default queueing mode. Serial interfaces at E1 (2.048 Mbps) and below use WFQ by default. Other interfaces use 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.
Attaching a service policy and enabling CBWFQ on an interface renders ineffective any commands related to fancy queueing such as commands pertaining to fair queueing, custom queueing, priority queueing, and Weighted Random Early Detection (WRED). You can configure these features only after you remove the policy map from the interface.
You can modify a policy map attached to an interface or a VC, changing the bandwidth of any of the classes comprising the map. Bandwidth changes that you make to an attached policy map are effective only if the aggregate of the bandwidth amounts for all classes comprising the policy map, including the modified class bandwidth, 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 InterSwitch Link (ISL) trunking. Upon reload, however, the service policy is removed from the configuration due to the following error message:
Process `set' action associated with class-map voip failed: Set cos supported only with IEEE 802.1Q/ISL interfaces.
Examples
The following example shows how to attache the service policy map called policy9 to data-link connection identifier (DLCI) 100 on output serial interface 1 and enables LLQ for Frame Relay:
interface Serial1/0.1 point-to-pointframe-relay interface-dlci 100class fragment!map-class frame-relay fragmentservice-policy output policy9The following example attaches the service policy map called policy9 to input serial interface 1:
interface Serial1service-policy input policy9The following example attaches the service policy map called policy9 to the input PVC called cisco:
pvc cisco 0/34 service-policy input policy9vbr-nt 5000 3000 500 precedence 4-7The following example attaches the policy called policy9 to output serial interface 1 to specify the service policy for the interface and enable CBWFQ on it:
interface serial1service-policy output policy9The following example attaches the service policy map called policy9 to the output PVC called cisco:
pvc cisco 0/5 service-policy output policy9 vbr-nt 4000 2000 500 precedence 2-3Related 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
policy-map
The name of a service policy map (created using the policy-map command) to be attached. The name can be a maximum of 40 alphanumeric characters.
Defaults
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-classesRouter(config-pmap)# class goldRouter(config-pmap-c)# bandwidth percent 50Router(config-pmap-c)# exitRouter(config-pmap)# class silverRouter(config-pmap-c)# bandwidth percent 20Router(config-pmap-c)# exitRouter(config-pmap)# class bronzeRouter(config-pmap-c)# bandwidth percent 15To configure classes for cust2, use the following commands:
Router(config)# policy-map cust2-classesRouter(config-pmap)# class goldRouter(config-pmap-c)# bandwidth percent 30Router(config-pmap-c)# exitRouter(config-pmap)# class silverRouter(config-pmap-c)# bandwidth percent 15Router(config-pmap-c)# exitRouter(config-pmap)# class bronzeRouter(config-pmap-c)# bandwidth percent 10To define the customer policy with cust1-classes and cust2-classes and QoS features, use the following commands:
Router(config)# policy-map cust-policyRouter(config-pmap)# class cust1Router(config-pmap-c)# shape average 38400Router(config-pmap-c)# service-policy cust1-classesRouter(config-pmap-c)# exitRouter(config-pmap)# class cust2Router(config-pmap-c)# shape peak 51200Router(config-pmap-c)# service-policy cust2-classesRouter(config-pmap-c)# interface Serial 3/2Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# exitRouter(config)# interface serial0/0Router(config-if)# service out cust-policyRelated 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
policy-map-name
Specifies the name of the predefined policy map to be used as a QoS policy. The name can be a maximum of 40 alphanumeric characters.
Defaults
No service policies are used.
Command Modes
Policy-map class configuration
Command History
12.1(2)E
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
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.
•
•
•
•
Examples
The following example creates a hierarchical service policy in the service policy called parent:
Router(config)# policy-map childRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# policy-map parentRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 10000000Router(config-pmap-c)# service-policy childFRF.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.
2.
3.
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 frfRouter(config-cmap)# match protocol vofrRouter(config-cmap)# exitRouter(config)# policy-map llqRouter(config-pmap)# class frfRouter(config-pmap-c)# priority 2000Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# policy-map llq-shapeRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 1000 128000Router(config-pmap-c)# service-policy llqThe 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 fragRouter(config-map-class)# frame-relay fragment 40Router(config-map-class)# service-policy llq-shapeRelated Commands
set atm-clp
To set the 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 CLP bit setting, use the no form of this command.
set atm-clp
Syntax Description
This command has no arguments or keywords.
Defaults
The CLP bit is automatically set to 0 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
Command History
Usage Guidelines
To disable this command, remove the service policy from the interface.
To use the set atm-clp command, you must have one of the following adapters: the Enhanced ATM Port Adapter (PA-A3), the ATM Inverse Multiplexer over ATM Port Adapter with 8 T1 Ports (PA-A3-8T1IMA), or the ATM Inverse Multiplexer over ATM Port Adapter with 8 E1 Ports (PA-A3-8E1IMA). Therefore, the set atm-clp command is not supported on any platform that does not support these adapters. 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.
Examples
The following example illustrates setting the CLP bit using the set atm-clp command in the policy map:
Router(config)# class-map ip-precedenceRouter(config-cmap)# match ip precedence 0 1Router(config-cmap)# exitRouter(config)# policy-map atm-clp-setRouter(config-pmap)# class ip-precedenceRouter(config-pmap-c)# set atm-clpRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm 1/0/0.1Router(config-if)# service-policy output bearRelated 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]}
Syntax Description
Defaults
Disabled
Command Modes
Policy-map class configuration
Command History
Usage Guidelines
CoS packet marking is supported only in the Cisco Express Forwarding (CEF)-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
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 CoS value. The "from-field" packet-marking categories are as follows:
•
•
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
Examples
In the following example, the policy map called "cos-set" is created to assign different CoSs 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)# exit Router(config-pmap)# exitEnhanced 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)# exit
Note
Related Commands
set discard-class
To mark a packet with a discard-class value, use the set discard-class command in 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
value
Per-hop behavior (PHB) for dropping traffic. The priority of a type of traffic. Valid values are numbers from 0 to 7.
Defaults
If you do not enter this command, the packet has a discard-class value of zero.
Command Modes
Policy-map configuration
Command History
Usage Guidelines
Discard-class indicates the discard portion of the PHB. Use the set discard-class command only in Pipe mode. Discard-class 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.
Examples
The following example shows that traffic will be set to the discard-class value of 2:
set discard-class 2Related Commands
match discard-class
Matches packets of a certain discard class.
random-detect discard-class-based
Bases WRED on the discard class value of a packet.
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 policy-map class configuration mode. To remove a previously set DSCP value, use the no form of this command.
set [ip] dscp {dscp-value | from-field [table table-map-name]}
no set [ip] dscp {dscp-value | from-field [table table-map-name]}
Syntax Description
Defaults
No packets are marked by setting the DSCP value in the ToS byte.
Command Modes
Policy-map class configuration
Command History
12.2(13)T
This command was introduced. This command replaces the set ip dscp command.
Usage Guidelines
After the DSCP bit is set, other quality of service (QoS) features can then operate on the bit settings.
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.
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.
The value of the dscp-value argument can be specified by the reserved keywords EF, AF11, and AF12 instead of numeric values.
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 DSCP value. The "from-field" packet-marking categories are as follows:
•
•
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
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:
•
•
Setting DSCP Values for IPv6 Packets Only
To set the DSCP values for IPv6 values only, the match protocol ipv6 command must also be used. Without the match protocol ipv6 command, the match defaults to match both IPv4 and IPv6 packets.
Setting DSCP Values for IPv4 Packets Only
To set the DSCP values for IPv4 packets only, use the ip keyword. Without the ip keyword the match occurs on both IPv4 and IPv6 packets.
Examples
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-map1Router(config-pmap-c)# exit
Note
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 will be made to the frame.
Examples
The following example illustrates a DE bit that was set using the set fr-de command in the traffic policy:
Router(config)# class-map ip-precedencRouter(config-cmap)# match ip precedence 0 1Router(config-cmap)# exitRouter(config)# policy-map atm-clp-setRouter(config-pmap)# class ip-precedenceRouter(config-pmap-c)# set fr-deRouter(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface atm 1/0/0Router(config-if)# service-policy output bearRelated 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 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
number | name
(Optional) A number or name that sets the precedence bits in the IP header. The values for the number argument and the corresponding name argument are listed in Table 15 from least to most important.
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Usage Guidelines
Table 15 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.
Table 15 Number and Name Values for IP Precedence
0
routine
1
priority
2
immediate
3
flash
4
flash-override
5
critical
6
internet
7
network
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 0ip policy route-map texasroute-map texasmatch length 68 128set ip precedence 5Related 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 [number]
no set ip tos
Syntax Description
number
(Optional) A number from 0 to 15 that sets the TOS bits in the IP header.
See Table 16 for more information.
Defaults
Disabled
Command Modes
Route-map configuration
Command History
Usage Guidelines
This command allows you to set four bits in the TOS byte header. Table 16 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 throughout 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 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 TOS bits to 8 (minimum delay as shown in Table 16) for packets that pass the route-map match:
interface serial 0ip policy route-map texas!route-map texasmatch length 68 128set 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.
set precedence {precedence-value | from-field [table table-map-name]}
no set precedence {precedence-value | from-field [table table-map-name]}
Syntax Description
Defaults
Disabled
Command Modes
Policy-map class configuration
Command History
12.2(13)T
This command was introduced. This command replaces the set ip precedence command.
Usage Guidelines
Command Compatibility
