-
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
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 one value or the other, but not both.
Bit Settings
After 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:
•
•
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:
•
•
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 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 command may act upon both types of packets.
Examples
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-map-1" 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-map1Router(config-pmap-c)# exit
Note
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.
set qos-group {group-id | from-field [table table-map-name]}
no set qos-group {group-id | from-field [table table-map-name]}
Syntax Description
Defaults
Disabled
No group ID is specified.
Command Modes
Policy-map class configuration
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. 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 precedence value. For instance, if you configure the set qos-group precedence command, the precedence value will be copied and used as the QoS group value.
Examples
The following example sets the QoS group to 1 for all packets that match the class map called "class1". 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 1Enhanced Packet Marking Example
The following example sets 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)# exit
Note
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
Defaults
Average or peak rate traffic shaping is not specified.
Command Modes
Class-map configuration
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:
•
•
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 sets the uses average rate shaping to ensure a bandwidth of 256 kbps:
shape average 256000The following example uses 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 300shape peak 512000Related 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 percent [bc] [be]
no shape {average | peak} percent percent [bc] [be]
Syntax Description
Defaults
Disabled
Command Modes
Policy-map class configuration
Command History
12.1(2)T
This command was introduced.
12.2(13)T
This command was modified for the Percentage-Based Policing and Shaping feature.
Usage Guidelines
This command calculates the committed information rate (CIR) based on 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 based on 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 154400000 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 based on 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.
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.
The shape (percent) command, when used in "child" (nested) 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 nested 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:
•
•
–
–
For more information on bandwidth allocation, refer to the "Congestion Management Overview" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide.
Examples
The following example configures traffic shaping using an average shaping rate based on a percentage of bandwidth. In this example, 25 percent of the bandwidth has been specified. Additionally, an optional bc value and be value (300 ms and 400 ms, respectively) have been specified.
Router(config)# policy-map policy1
Router(config-pmap)# class-map class1
Router(config-pmap-c)# shape average percent 25 300 ms 400 ms
Router(config-pmap-c)# service-policy child-policy1
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Router(config)# interface serial 3/1
Router(config-if)# service-policy output policy1
Related Commands
shape (policy-map class)
To shape traffic to the indicated bit rate according to the algorithm specified, use the shape command in policy-map class configuration mode. To remove shaping and leaving the traffic unshapped, use the no form of this command.
shape [average | peak] mean-rate [[burst-size] [excess-burst-size]]
no shape [average | peak]
Syntax Description
Defaults
When Be is not configured, the default value is equal to Bc. For more information about burst size defaults, see the "Usage Guidelines" section of this command.
Command Modes
Policy-map class configuration
Command History
12.0(5)XE
This command was introduced.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Usage Guidelines
The measurement interval is Bc divided by 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 Bc and Be, the algorithm decides the default values for the shape entity. The algorithm uses a 4 milliseconds measurement interval, so Bc will be CIR * (4 / 1000).
Burst sizes larger than the default 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 Be is not configured, the default value is equal to Bc.
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-actionclass class-interface-allshape average 1000000interface pos1/0/0service-policy output dts-interface-all-actionRelated Commands
shape adaptive
To configure a Frame Relay interface or a point-to-point subinterface to estimate the available bandwidth by backward explicit congestion notification (BECN) integration while traffic shaping is enabled, use the shape adaptive command in policy-map class configuration mode. To leave the available bandwidth unestimated, use the no form of this command.
shape adaptive mean-rate-lower-bound
no shape adaptive
Syntax Description
Defaults
Bandwidth is not estimated.
Command Modes
Policy-map class configuration
Command History
Usage Guidelines
If traffic shaping is not enabled, this command has no effect.
When continuous BECN messages are received, the shape entity immediately decreases its maximum shape rate by one-fourth for each BECN message received until it reaches the lower bound committed information rate (CIR). If, after several intervals, the interface has not received another BECN and traffic is waiting in the shape queue, the shape entity increases the shape rate back to the maximum rate by 1/16 for each interval. A shape entity configured with the shape adaptive mean-rate-lower-bound command will always be shaped between the mean rate upper bound and the mean rate lower bound.
Examples
The following example configures a shape entity with CIR of 128 kbps and sets the lower bound CIR to 64 kbps when BECNs are received:
policy-map dts-p2p-all-actionclass class-p2p-allshape average 128000shape adaptive 64000shape fecn-adapt
To configure a Frame Relay interface to reflect received forward explicit congestion notification (FECN) bits as backward explicit congestion notification (BECN) bits in Q.922 TEST RESPONSE messages, use the shape fecn-adapt command in policy-map class configuration mode. To configure the Frame Relay interface to not reflect FECN as BECN, use the no form of this command.
shape fecn-adapt
no shape fecn-adapt
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Policy-map class configuration
Command History
Usage Guidelines
When the downstream Frame Relay switch is congested, a Frame Relay interface or point-to-point interface receives a Frame Relay message with the FECN bit on. This message may be an indication that no traffic is waiting to carry a BECN to the far end (voice/multimedia traffic is one-way). When the shape fecn-adapt command is configured, a small buffer is allocated and a Frame Relay TEST RESPONSE is built on behalf of the Frame Relay switch. The Frame Relay TEST RESPONSE is equipped with the triggering data-link connection identifier (DLCI) of the triggering mechanism. It also sets the BECN bit and sends it out to the wire.
Examples
The following example configures a shape entity with a committed information rate (CIR) of 1 Mbps and adapts the Frame Relay message with FECN to BECN:
policy-map dts-p2p-all-actionclass class-p2p-allshape average 1000000shape fecn-adaptRelated Commands
shape max-buffers
To specify the maximum number of buffers allowed on shaping queues, use the shape max-buffers command in class-map configuration mode. To remove the maximum number of buffers, use the no form of this command.
shape max-buffers number-of-buffers
no shape max-buffers number-of-buffers
Syntax Description
number-of-buffers
Specifies the maximum number of buffers. The minimum number of buffers is 1; the maximum number of buffers is 4096.
Defaults
1000 buffers
Command Modes
Class-map configuration
Command History
Usage Guidelines
You can specify the maximum number of buffers allowed on shaping queues for each class configured to use Generic Traffic Shaping (GTS).
Examples
The following example configures shaping and sets the maximum buffer limit to 100:
shape average 350000shape max-buffers 100Related Commands
show access-lists rate-limit
To display information about rate-limit access lists, use the show access-lists rate-limit command in EXEC mode.
show access-lists rate-limit [acl-index]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show access-lists rate-limit command:
Router# show access-lists rate-limitRate-limit access list 10Rate-limit access list 21Rate-limit access list 32Rate-limit access list 43Rate-limit access list 54Rate-limit access list 65Rate-limit access list 9mask FFRate-limit access list 10mask 0FRate-limit access list 11mask F0Rate-limit access list 1001001.0110.1111Rate-limit access list 10100E0.34B8.D840Rate-limit access list 1991111.1111.1111The following is sample output from the show access-lists rate-limit command when specific rate-limit access lists are specified:
Router# show access-lists rate-limit 1Rate-limit access list 10Router# show access-lists rate-limit 9Rate-limit access list 9mask FFRouter# show access-lists rate-limit 101Rate-limit access list 10100E0.34B8.D840Table 17 describes the significant fields shown in the displays.
Related Commands
access-list rate-limit
Configures an access list for use with CAR policies.
show access-lists
Displays the contents of current IP and rate-limit access lists.
show atm bundle
To display the bundle attributes assigned to each bundle virtual circuit (VC) member and the current working status of the VC members, use the show atm bundle command in privileged EXEC mode.
show atm bundle bundle-name
Syntax Description
bundle-name
The name of the bundle whose member information is displayed. This is the bundle name specified by the bundle command when the bundle was created.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show atm bundle command (* indicates that this VC is the VC for all precedence levels not explicitly configured):
Router# show atm bundlenew-york on atm1/0.1 Status: UP Config. Active Bumping PG/ Peak Avg/Min Burst Name VPI/VCI Preced. Preced. Predec./ PV kbps kbps Cells Status Acceptny-control 0/207 7 7 4 /Yes pv 10000 5000 32 UP ny-premium 0/206 6-5 6-5 7 /No pg 20000 10000 32 UP ny-priority 0/204 4-2 4-2 1 /Yes pg 10000 3000 UP ny-basic* 0/201 1-0 1-0 - /Yes pg 10000 UPlos-angeles on atm1/0.1 - Status: UPConfig. Active Bumping pg/ Peak Avg/Min Burst Name VPI/VCI Preced. Preced. Predec./ pv kbps kbps Cells Status Accept la-high 0/407 7-5 7-5 4 /Yes pv 20000 5000 32 UP la-med 0/404 4-2 4-2 1 /Yes pg 10000 3000 UP la-low* 0/401 1-0 1-0 - /Yes pg 10000 UPsan-francisco on atm1/0.1 Status: UP Config. Active Bumping PG/ Peak Avg/Min Burst Name VPI/VCI Preced. Preced. Predec./ PV kbps kbps Cells StatusAcceptsf-control 0/307 7 7 4 /Yes pv 10000 5000 32 UP sf-premium 0/306 6-5 6-5 7 /No pg 20000 10000 32 UP sf-priority 0/304 4-2 4-2 1 /Yes pg 10000 3000 UP sf-basic* 0/301 1-0 1-0 - /Yes pg 10000 UPRelated Commands
Displays statistics on the specified bundle.
show atm map
Displays the list of all configured ATM static maps to remote hosts on an ATM network.
show atm bundle statistics
To display statistics or detailed statistics on the specified bundle, use the show atm bundle statistics command in privileged EXEC mode.
show atm bundle bundle-name statistics [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show atm bundle statistics command:
Router# show atm bundle san-jose statisticsBundle Name: Bundle State: UPAAL5-NLPID OAM frequency : 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5BUNDLE is not managed.InARP frequency: 15 minute(s)InPkts: 3, OutPkts: 3, Inbytes: 1836, Outbytes: 1836 InPRoc: 3, OutPRoc: 0, Broadcasts: 3InFast: 0, OutFast: 0, InAS: 0, OutAS: 0Router# show atm bundle san-jose statistics detailBundle Name: Bundle State: UPAAL5-NLPIDOAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5BUNDLE is not managed.InARP frequency: 15 minute(s)InPkts: 3, OutPkts: 3, InBytes; 1836, OutBytes: 1836InPRoc: 3, OutPRoc: 0, Broadcasts: 3InFast: 0, OutFast: 0, InAS: 0, OutAS: 0ATM1/0.52: VCD: 6, VPI: 0 VCI: 218, Connection Name: sj-basic UBR, PeakRate: 155000 AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0xE00OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM Loopbavk status: OAM DisabledOMA VC state: Not ManagedILMI VC state: Not ManagedInARP frequency: 15 minute(s)InPkts: 3, OutPkts: 3, InBytes; 1836, OutBytes: 1836InPRoc: 3, OutPRoc: 0,Broadcasts: 3InFast: 0, OutFast: 0, InAS: 0, OututAS: 0OAM cells received: 0F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0F4 InEndloop: 0, F4 OutSegloop:0, F4 InAIS: 0, F4 InRDI: 0OAM cells sent: 0F5 OutEndloop: 0. F5 OutSegloop: 0, f5 Out RDI:0F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OUtRDI: 0OAM cell drops: 0Status; UPATM1/0.52: VCD: 4, VPI: 0 VCI: 216, Connection Name: sj-premiumUBR, PeakRate: 155000AAL5-LLC/SNAP, etype: 0x0, Flags: 0xC20, VCmode: 0xE000OAM frequency: 0 second(s), OAM retry frequency: 1 second(s)OAM up retry count: 3, OAM down retry count: 5OAM Loopback status: OAM DisabledOAM VC state: Not ManagedILMI VC state: Not Managed InARP frequency: 15 minute(s)InPkts: 0, OutPkts: 0, InBytes; 0, OutBytes: 0InPRoc: 0, OutPRoc: 0, Broadcasts: 0InFast: 0, OutFast: 0, InAS: 0 OAM cells received: 0F5 InEndloop: 0, F4 InSegloop: 0, F4InAIS; 0, F4 InRDI: 0F4 OutEndloop: 0, F4 OutSegloop: F4 OutRDI: 0OAM cell drops: 0Status: UPRelated Commands
show atm bundle svc
To display the bundle attributes assigned to each bundle virtual circuit (VC) member and the current working status of the VC members, use the show atm bundle svc command in privileged EXEC mode.
show atm bundle svc [bundle-name]
Syntax Description
bundle-name
(Optional) Name of the switched virtual circuit (SVC) bundle to be displayed, as identified by the bundle svc command.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If no bundle name is specified, all SVC bundles configured on the system are displayed.
Examples
The following example provides output for the show atm bundle svc command. The bundle named "finance" is configured on ATM interface 1/0.1 with eight members. All of the members are up except bundle member zero. Bundle member zero is the default member, which if initiated once will always be on and used as the default for all traffic.
Router# show atm bundle svc financefinance on ATM1/0.1:UPConfig Current Peak Avg/Min BurstVC Name VPI/VCI Preced. Preced. Kbps kbps Cells Stsseven 0/37 7 7 10000 5000 32 UPsix 0/36 6 6 6000 UPfive 0/40 5 5 5000 UPfour 0/41 4 4 4000 UPthree 0/42 3 3 3000 UPtwo 0/43 2 2 2000 UPone 0/44 1 1 1000 UPzero* 0Table 18 describes the significant fields in the display.
Related Commands
show atm bundle svc statistics
To display the statistics of a switched virtual circuit (SVC) bundle, use the show atm bundle svc statistics command in privileged EXEC mode.
show atm bundle svc bundle-name statistics
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example provides output for the show atm bundle svc statistics command using a bundle named "city":
Router# show atm bundle svc city statisticsBundle Name:Bundle State:INITIALIZINGAAL5-NLPIDOAM frequency:0 second(s), OAM retry frequency:10 second(s)OAM up retry count:4, OAM down retry count:3BUNDLE is managed by.InARP frequency:15 minutes(s)InPkts:0, OutPkts:0, InBytes:0, OutBytes:0InPRoc:0, OutPRoc:0, Broadcasts:0InFast:0, OutFast:0, InAS:0, OutAS:0InPktDrops:0, OutPktDrops:0CrcErrors:0, SarTimeOuts:0, OverSizedSDUs:0,LengthViolation:0, CPIErrors:0Table 19 describes the significant fields in the display.
Related Commands
show auto qos
To display the configurations created by the AutoQoS — VoIP feature on a specific interface or all interfaces, use the show auto qos command in EXEC mode.
show auto qos [interface [interface-type]]
Syntax Description
interface
(Optional) Indicates that the configurations for a specific interface type will be displayed.
interface-type
(Optional) Specifies the interface type.
Command Modes
EXEC
Command History
Usage Guidelines
The auto qos voip command displays the configurations created for all interface types.
When the auto qos voip command is used to configure the AutoQoS — VoIP feature, configurations are generated for each interface or permanent virtual circuit (PVC). These configurations are then used to create the interface configurations, policy maps, class maps, and access control lists (ACLs). The show auto qos command can be used to verify the contents of the interface configurations, policy maps, class maps, and ACLs.
The show auto qos interface command can be used with Frame Relay data-link connection identifiers (DLCIs) and ATM PVCs.
Examples
The following section contains sample output of the show auto qos command when the various optional keywords are specified.
Note
show auto qos interface Command Example
When the interface keyword is configured along with the corresponding interface-type argument, the show auto qos interface [interface-type] command displays the configurations created by the AutoQoS — VoIP feature on the specified interface.
In the following example, the serial subinterface serial6/1.1 has been specified:
Router# show auto qos interface serial6/1.1S6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640When the interface keyword is configured but an interface type is not specified, the show auto qos interface command displays the configurations created by the AutoQoS — VoIP feature on all the interfaces or PVCs on which the AutoQoS — VoIP feature is enabled.
Router# show auto qos interfaceSerial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640ATM2/0.1: PVC 1/100 -!interface ATM2/0.1 point-to-pointpvc 1/100tx-ring-limit 3encapsulation aal5mux ppp Virtual-Template200!interface Virtual-Template200bandwidth 512ip address 10.10.107.1 255.255.255.0service-policy output AutoQoS-Policy-UnTrustppp multilinkppp multilink fragment-delay 10ppp multilink interleaveThe following example displays all of the configurations created by the AutoQoS — VoIP feature:
Router# show auto qosSerial6/1.1: DLCI 100 -!interface Serial6/1frame-relay traffic-shaping!interface Serial6/1.1 point-to-pointframe-relay interface-dlci 100class AutoQoS-VoIP-FR-Serial6/1-100frame-relay ip rtp header-compression!map-class frame-relay AutoQoS-VoIP-FR-Serial6/1-100frame-relay cir 512000frame-relay bc 5120frame-relay be 0frame-relay mincir 512000service-policy output AutoQoS-Policy-UnTrustframe-relay fragment 640Table 20 describes the significant fields shown in the display.
Related Commands
show class-map
To display all class maps and their matching criteria, use the show class-map command in EXEC mode.
show class-map [class-map-name]
Syntax Description
class-map-name
(Optional) Name of the class map. The class map name can be a maximum of 40 alphanumeric characters.
Command Modes
EXEC
Command History
Usage Guidelines
You can use the show class-map command to display all class maps and their matching criteria. If you enter the optional class-map-name argument, the specified class map and its matching criteria will be displayed.
Examples
In the following example, three class maps are defined. Packets that match access list 103 belong to class c3, IP packets belong to class c2, and packets that come through input Ethernet interface 1/0 belong to class c1. The output from the show class-map command shows the three defined class maps.
Router# show class-mapClass Map c3Match access-group 103Class Map c2Match protocol ipClass Map c1Match input-interface Ethernet1/0In the following example, a class map called "c1" has been defined, and the Frame Relay DLCI number of 500 has been specified as a match criterion:
Router# show class-mapclass map match-all c1match fr-dlci 500Table 21 describes the significant fields shown in the display.
Table 21 show class-map Field Descriptions1
Class-map
Class of traffic being displayed. Output is displayed for each configured class map in the policy. The choice for implementing class matches (for example, match-all or match-any) can also appear next to the traffic class.
Match
Match criteria specified for the class map. Choices include criteria such as the Frame Relay DLCI number, Layer 3 packet length, IP precedence, IP differentiated services code point (DSCP) value, Multiprotocol Label Switching (MPLS) experimental value, access groups, and quality of service (QoS) groups.
1 A number in parentheses may appear next to the class-map name, and match criteria information. The number is for Cisco internal use only and can be disregarded.
Related Commands
show cops servers
To display the IP address and connection status of the policy servers for which the router is configured, use the show cops servers command in EXEC mode. The display also tells you about the Common Open Policy Service (COPS) client on the router.
show cops servers
Syntax Description
This command has no keywords or arguments.
Command Modes
EXEC
Command History
Examples
In the following example, information is displayed about the current policy server and client. When Client Type appears followed by an integer, 1 stands for Resource Reservation Protocol (RSVP) and 2 stands for Differentiated Services Provisioning. (0 indicates keepalive.)
Router# show cops serversCOPS SERVER: Address: 161.44.135.172. Port: 3288. State: 0. Keepalive: 120 secNumber of clients: 1. Number of sessions: 1.COPS CLIENT: Client type: 1. State: 0.Related Commands
show ip rsvp policy cops
Displays policy server address(es), ACL IDs, and current state of the router-server connection.
show frame-relay ip rtp header-compression
To show Frame Relay Real-Time Transport Protocol (RTP) header compression statistics, use the show frame-relay ip rtp header-compression command in user EXEC or privileged EXEC mode.
show frame-relay ip rtp header-compression [interface type number]
Syntax Description
interface type number
(Optional) Specifies the interface type and number. A space is not needed between the type and number.
Command Modes
User EXEC
Privileged EXEC
Command History
Examples
The following is sample output from the show frame-relay ip rtp header-compression command:
Router# show frame-relay ip rtp header-compressionDLCI 17 Link/Destination info: ip 10.1.1.1Interface Serial0:Rcvd: 0 total, 0 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 6000 total, 5998 compressed,227922 bytes saved, 251918 bytes sent1.90 efficiency improvement factorConnect: 16 rx slots, 16 tx slots, 2 long searches, 2 misses99% hit ratio, five minute miss rate 0 misses/sec, 0 maxThe following sample output from the show frame-relay ip rtp header-compression command shows statistics for a PVC bundle called MP-3-static:
Router# show frame-relay ip rtp header-compression interface Serial1/4vc-bundle MP-3-static Link/Destination info:ip 10.1.1.1Interface Serial1/4:Rcvd: 14 total, 13 compressed, 0 errors0 dropped, 0 buffer copies, 0 buffer failuresSent: 15 total, 14 compressed,474 bytes saved, 119 bytes sent4.98 efficiency improvement factorConnect:256 rx slots, 256 tx slots,1 long searches, 1 misses 0 collisions, 0 negative cache hits93% hit ratio, five minute miss rate 0 misses/sec, 0 maxTable 22 describes the significant fields shown in the display.
Related Commands
show interfaces fair-queue
To display information and statistics about weighted fair queueing (WFQ) for a Versatile Interface Processor (VIP)-based interface, use the show interfaces fair-queue command in EXEC mode.
show interfaces [interface-type interface-number] fair-queue
Syntax Description
interface-type
(Optional) The type of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show interfaces fair-queue command for VIP-distributed WFQ (DWFQ):
Router# show interfaces fair-queueHssi0/0/0 queue size 0packets output 1417079, drops 2WFQ: aggregate queue limit 54, individual queue limit 27max available buffers 54Class 0: weight 10 limit 27 qsize 0 packets output 1150 drops 0Class 1: weight 20 limit 27 qsize 0 packets output 0 drops 0Class 2: weight 30 limit 27 qsize 0 packets output 775482 drops 1Class 3: weight 40 limit 27 qsize 0 packets output 0 drops 0Table 23 describes the significant fields shown in the display.
Related Commands
show interfaces
Displays statistics for all interfaces configured on the router or access server.
show interfaces random-detect
To display information about Weighted Random Early Detection (WRED) for a Versatile Interface Processor (VIP)-based interface, use the show interfaces random-detect command in EXEC mode.
show interfaces [interface-type interface-number] random-detect
Syntax Description
interface-type
(Optional) The type of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show interfaces random-detect command for VIP-distributed WRED (DWRED):
Router# show interfaces random-detectFastEthernet1/0/0 queue size 0packets output 29692, drops 0WRED: queue average 0weight 1/512Precedence 0: 109 min threshold, 218 max threshold, 1/10 mark weight1 packets output, drops: 0 random, 0 thresholdPrecedence 1: 122 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 2: 135 min threshold, 218 max threshold, 1/10 mark weight14845 packets output, drops: 0 random, 0 thresholdPrecedence 3: 148 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 4: 161 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 5: 174 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 6: 187 min threshold, 218 max threshold, 1/10 mark weight14846 packets output, drops: 0 random, 0 thresholdPrecedence 7: 200 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Table 24 describes the significant fields shown in the display.
Related Commands
show interfaces rate-limit
To display information about committed access rate (CAR) for an interface, use the show interfaces rate-limit command in EXEC mode.
show interfaces [interface-type interface-number] rate-limit
Syntax Description
interface-type
(Optional) The type of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show interfaces rate-limit command:
Router# show interfaces fddi2/1/0 rate-limitFddi2/1/0Inputmatches: access-group rate-limit 100params: 800000000 bps, 64000 limit, 80000 extended limitconformed 0 packets, 0 bytes; action: set-prec-continue 1exceeded 0 packets, 0 bytes; action: set-prec-continue 0last packet: 4737508ms ago, current burst: 0 byteslast cleared 01:05:47 ago, conformed 0 bps, exceeded 0 bpsmatches: access-group 101params: 80000000 bps, 56000 limit, 72000 extended limitconformed 0 packets, 0 bytes; action: set-prec-transmit 5exceeded 0 packets, 0 bytes; action: set-prec-transmit 0last packet: 4738036ms ago, current burst: 0 byteslast cleared 01:02:05 ago, conformed 0 bps, exceeded 0 bpsmatches: all trafficparams: 50000000 bps, 48000 limit, 64000 extended limitconformed 0 packets, 0 bytes; action: set-prec-transmit 5exceeded 0 packets, 0 bytes; action: set-prec-transmit 0last packet: 4738036ms ago, current burst: 0 byteslast cleared 01:00:22 ago, conformed 0 bps, exceeded 0 bpsOutputmatches: all trafficparams: 80000000 bps, 64000 limit, 80000 extended limitconformed 0 packets, 0 bytes; action: transmitexceeded 0 packets, 0 bytes; action: droplast packet: 4809528ms ago, current burst: 0 byteslast cleared 00:59:42 ago, conformed 0 bps, exceeded 0 bpsTable 25 describes the significant fields shown in the display.
Related Commands
show ip nbar pdlm
To display the Packet Description Language Module (PDLM) in use by network-based application recognition (NBAR), use the show ip nbar pdlm command in privileged EXEC mode.
show ip nbar pdlm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to display a list of all the PDLMs that have been loaded into NBAR using the ip nbar pdlm command.
Examples
In this example of the show ip nbar pdlm command, the citrix.pdlm PDLM has been loaded from Flash memory:
Router# show ip nbar pdlmThe following PDLMs have been loaded:flash://citrix.pdlmRelated Commands
ip nbar pdlm
Extends or enhances the list of protocols recognized by NBAR through a Cisco-provided PDLM.
