-
Cisco IOS Quality of Service Solutions Command Reference, Release 12.3 T
-
Introduction
-
Quality of Service Commands: A through F
-
Quality of Service Commands: I
-
Quality of Sevice Commands: M
-
Quality of Service Commands: O through P
-
Quality of Service Commands: Q through R
-
Quality of Service Commands: send qdm message through show ip nbar pdlm
-
Quality of Service Commands: show ip nbar port-map through show qdm status
-
Quality of Service Commands: show queue through vc-hold-queue
-
Table Of Contents
match mpls experimental topmost
match packet length (class-map)
match access-group
To configure the match criteria for a class map on the basis of the specified access control list (ACL), use the match access-group command in class-map configuration mode. To remove ACL match criteria from a class map, use the no form of this command.
match access-group {access-group | name access-group-name}
no match access-group access-group
Syntax Description
Defaults
No match criteria are configured.
Command Modes
Class-map configuration
Command History
Usage Guidelines
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria including ACLs, protocols, input interfaces, QoS labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match access-group command specifies a numbered or named ACL whose contents are used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match access-group command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
match access-group
•
•
•
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
Note
Examples
The following example specifies a class map called acl144 and configures the ACL numbered 144 to be used as the match criteria for this class:
class-map acl144match access-group 144Related Commands
match any
To configure the match criteria for a class map to be successful match criteria for all packets, use the match any command in class-map configuration mode. To remove all criteria as successful match criteria, use the no form of this command.
match any
no match any
Syntax Description
This command has no arguments or keywords.
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
12.0(5)XE
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0(5)T.
12.1(1)E
This command was integrated into Cisco IOS Release 12.1(1)E.
Examples
In the following configuration, all packets leaving Ethernet interface 1/1 will be policed based on the parameters specified in policy-map class configuration mode.
Router(config)# class-map matchanyRouter(config-cmap)# match anyRouter(config-cmap)# exitRouter(config)# policy-map policy1Router(config-pmap)# class class4Router(config-pmap-c)# police 8100 1500 2504 conform-action transmit exceed-action set-qos-transmit 4Router(config-pmap-c)# exitRouter(config)# interface ethernet1/1Router(config-if)# service-policy output policy1Related Commands
match class-map
To use a traffic class as a classification policy, use the match class-map command in class-map configuration mode. To remove a specific traffic class as a match criterion, use the no form of this command.
match class-map class-map-name
no match class-map class-map-name
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
12.0(5)XE
This command was introduced.
12.1(1)E
This command was integrated into Cisco IOS Release 12.1(1)E.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Usage Guidelines
The only method of including both match-any and match-all characteristics in a single traffic class is to use the match class-map command. To combine match-any and match-all characteristics into a single class, a traffic class created with the match-any instruction must use a class configured with the match-all instruction as a match criterion (through the match class-map command), or vice versa.
You can also use the match class-map command to nest traffic classes within one another, saving users the overhead of re-creating a new traffic class when most of the information exists in a previously configured traffic class.
Examples
In the following example, the traffic class called class1 has the same characteristics as traffic class called class2, with the exception that traffic class class1 has added a destination address as a match criterion. Rather than configuring traffic class class1 line by line, a user can enter the match class-map class2 command. This command allows all of the characteristics in the traffic class called class2 to be included in the traffic class called class1, and the user can simply add the new destination address match criterion without reconfiguring the entire traffic class.
Router(config)# class-map match-any class2Router(config-cmap)# match protocol ipRouter(config-cmap)# match qos-group 3Router(config-cmap)# match access-group 2Router(config-cmap)# exitRouter(config)# class-map match-all class1Router(config-cmap)# match class-map class2Router(config-cmap)# match destination-address mac 1.1.1Router(config-cmap)# exitThe following example shows how to combine the characteristics of two traffic classes, one with match-any and one with match-all characteristics, into one traffic class with the match class-map command. The result of traffic class called class4 requires a packet to match one of the following three match criteria to be considered a member of traffic class called class 4: IP protocol and QoS group 4, destination MAC address 1.1.1, or access group 2.
In this example, only the traffic class called class4 is used with the service policy called policy1.
Router(config)# class-map match-all class3Router(config-cmap)# match protocol ipRouter(config-cmap)# match qos-group 4Router(config-cmap)# exitRouter(config)# class-map match-any class4Router(config-cmap)# match class-map class3Router(config-cmap)# match destination-address mac 1.1.1Router(config-cmap)# match access-group 2Router(config-cmap)# exitRouter(config)# policy-map policy1Router(config-pmap)# class class4Router(config-pmap-c)# police 8100 1500 2504 conform-action transmit exceed-action set-qos-transmit 4Router(config-pmap-c)# exitRelated Commands
class-map
Creates a class map to be used for matching packets to a specified class.
match cos
To match a packet based on a Layer 2 class of service (CoS) marking, use the match cos command in class-map configuration mode. To remove a specific Layer 2 CoS/Inter-Switch Link (ISL) marking, use the no form of this command:
match cos cos-value [cos-value cos-value cos-value]
no match cos cos-value [cos-value cos-value cos-value]
Syntax Description
cos-value
(Optional) Specific IEEE 802.1Q/ISL CoS value. The cos-value is from 0 to 7; up to four CoS values can be specified in one match cos statement.
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Examples
In the following example, the CoS-values of 1, 2, and 3 are successful match criteria for the interface containing the classification policy called cos:
Router(config)# class-map cos Router(config-cmap)# match cos 1 2 3In the following example, classes called voice and video-n-data are created to classify traffic based on the CoS values. QoS treatment is then given to the appropriate packets (in this case, the QoS treatment is priority 64 and bandwidth 512) in the CoS-based-treatment policy map.
Router(config)# class-map voiceRouter(config-cmap)# match cos 7Router(config)# class-map video-n-dataRouter(config-cmap)# match cos 5Router(config)# policy-map cos-based-treatmentRouter(config-pmap)# class voiceRouter(config-pmap-c)# priority 64Router(config-pmap-c)# exitRouter(config-pmap)# class video-n-dataRouter(config-pmap-c)# bandwidth 512Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet0/0.1Router(config-if)# service-policy output cos-based-treatmentThe service policy configured in this section is attached to all packets leaving Fast Ethernet interface 0/0.1. The service policy can be attached to any interface that supports service policies.
Related Commands
match destination-address mac
To use the destination MAC address as a match criterion, use the match destination-address mac command in class-map configuration mode. To remove a previously specified destination MAC address as a match criterion, use the no form of this command.
match destination-address mac address
no match destination-address mac address
Syntax Description
Defaults
No destination MAC address is specified.
Command Modes
Class-map configuration
Command History
12.0(5)XE
This command was introduced.
12.1(1)E
This command was integrated into Cisco IOS Release 12.1(1)E.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Examples
The following example specifies a class map called macaddress and specifies the destination MAC address to be used as the match criterion for this class:
class-map macaddressmatch destination-address mac 00:00:00:00:00:00Related Commands
class-map
Creates a class map to be used for matching packets to a specified class.
match discard-class
To match packets of a certain discard class, use the match discard-class command in class-map configuration mode.
match discard-class class-number
Syntax Description
Defaults
Packets will not be classified as expected.
Command Modes
Class-map configuration
Command History
Examples
The following example shows that packets in discard class 2 are matched:
match discard-class 2Related Commands
match dscp
To identify a specific IP differentiated service code point (DSCP) value as a match criterion, use the match dscp command in class-map configuration mode. To remove a specific DSCP value from a class map, use the no form of this command.
match [ip] dscp dscp-value [dscp-value dscp-value dscp-value dscp-value dscp-value dscp-value dscp-value]
no match [ip] dscp dscp-value [dscp-value dscp-value dscp-value dscp-value dscp-value dscp-value dscp-value]
Syntax Description
Defaults
Matching on both IPv4 and IPv6 packets is the default.
Command Modes
Class-map configuration
Command History
12.2(13)T
This command was introduced. This command replaces the match ip dscp command.
Usage Guidelines
DSCP Values
Up to eight DSCP values can be matched in one match statement. For example, if you wanted the DCSP values of 0, 1, 2, 3, 4, 5, 6, or 7 (note that only one of the IP DSCP values must be a successful match criterion, not all of the specified DSCP values), enter the match dscp 0 1 2 3 4 5 6 7 command.
This command is used by the class map to identify a specific DSCP value marking on a packet. In this context, dscp-value arguments are used as markings only and have no mathematical significance. For instance, the dscp-value of 2 is not greater than 1. The value simply indicates that a packet marked with the dscp-value of 2 is different from a packet marked with the dscp-value of 1. The treatment of these marked packets is defined by the user through the setting of QoS policies in policy-map class configuration mode.
Match IPv6 Packets on DSCP Values
To match DSCP values for IPv6 packets only, the match protocol ipv6 command must also be used. Without that command, the DSCP match defaults to match both IPv4 and IPv6 packets.
Match IPv4 Packets on DSCP Values
To match DSCP values for IPv4 packets only, use the ip keyword. Without the ip keyword, the match occurs on both IPv4 and IPv6 packets. Alternatively, the match protocol ip command can be used with the match dscp command to classify only IPv4 packets.
Examples
Priority50 Service Policy Matching DSCP Value
The following example shows how to configure the service policy called "priority50" and attach service policy "priority50" to an interface. In this example, the class map called "ipdscp15" will evaluate all packets entering interface Fast Ethernet 1/0/0 for an IP DSCP value of 15. If the incoming packet has been marked with the IP DSCP value of 15, the packet will be treated as priority traffic and will be allocated with bandwidth of 50 kbps.
Router(config)# class-map ipdscp15Router(config-cmap)# match ip dscp 15Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class ipdscp15Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet1/0/0Router(config-if)# service-policy output priority50Related Commands
match fr-dlci
To specify the Frame Relay data-link connection identifier (DLCI) number as a match criterion in a class map, use the match fr-dlci command in class-map configuration mode. To remove a previously specified DLCI number as a match criterion, use the no form of this command.
match fr-dlci dlci-number
no match fr-dlci dlci-number
Syntax Description
Defaults
No DLCI number is specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
This match criterion can be used in main interfaces and point-to-multipoint subinterfaces in Frame Relay networks, and it can also be used in hierarchical policy maps.
Examples
In the following example a class map called "class1" has been created and the Frame Relay DLCI number of 500 has been specified as a match criterion. Packets matching this criterion are placed in class1.
Router(config)# class-map class1Router(config-cmap)# match fr-dlci 500Router(config-cmap)# endRelated Commands
match input-interface
To configure a class map to use the specified input interface as a match criterion, use the match input-interface command in class-map configuration mode. To remove the input interface match criterion from a class map, use the no form of this command.
match input-interface interface-name
no match input-interface interface-name
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria including input interfaces, access control lists (ACLs), protocols, QoS labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match input-interface command specifies the name of an input interface to be used as the match criterion against which packets are checked to determine if they belong to the class specified by the class map.
To use the match input-interface command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
•
•
•
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
Examples
The following example specifies a class map called eth1 and configures the input interface named ethernet1to be used as the match criterion for this class:
class-map ethernet1match input-interface ethernet1Related Commands
match ip dscp
The match ip dscp command is replaced by the match dscp command. See the match dscp command for more information.
match ip precedence
The match ip precedence command is replaced by the match precedence command. See the match precedence command for more information.
match ip rtp
To configure a class map to use the Real-Time Protocol (RTP) protocol port as the match criterion, use the match ip rtp command in class-map configuration mode. To remove the RTP protocol port match criterion, use the no form of this command.
match ip rtp starting-port-number port-range
no match ip rtp
Syntax Description
starting-port-number
The starting RTP port number. Values range from 2000 to 65535.
port-range
The RTP port number range. Values range from 0 to 16383.
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
This command is used to match IP RTP packets that fall within the specified port range. It matches packets destined to all even User Datagram Port (UDP) port numbers in the range <starting port range> <starting port range + port range>.
Use of an RTP port range as the match criterion is particularly effective for applications that use RTP, such as voice or video.
Examples
The following example specifies a class map called eth1 and configures the RTP port number 2024 and range 1000 to be used as the match criteria for this class:
class-map ethernet1match ip rtp 2024 1000Related Commands
match mpls experimental
To configure a class map to use the specified value of the experimental (EXP) field as a match criterion, use the match mpls experimental command in class-map configuration mode. To remove the EXP field match criterion from a class map, use the no form of this command.
match mpls experimental number
no match mpls experimental number
Syntax Description
number
EXP field value (any number from 0 through 7) to be used as a match criterion. Numbers can be space delimited (for example, 3 4 7).
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria including input interfaces, access control lists (ACLs), protocols, quality of service (QoS) labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match mpls experimental command specifies the name of an EXP field value to be used as the match criterion against which packets are checked to determine if they belong to the class specified by the class map.
To use the match mpls experimental command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
•
•
•
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
Examples
The following example specifies a class map called eth1 and configures the Multiprotocol Label Switching (MPLS) experimental values of 1 and 2 to be used as the match criterion for this class:
Router(config)# class-map ethernet1Router(config-cmap)# match mpls experimental 1 2Related Commands
match mpls experimental topmost
To match the experimental (EXP) value in the topmost label, use the match mpls experimental topmost command in class-map configuration mode.
match mpls experimental topmost value
Syntax Description
value
Value of the Multiprotocol Label Switching (MPLS) EXP field in the topmost label header. Valid values are 0 to 7.
Defaults
Packets will not be classified as expected.
Command Modes
Class-map configuration
Command History
Usage Guidelines
You can enter this command on the input and the output interfaces. It will match only on MPLS packets.
Examples
The following example shows that the EXP value 3 in the topmost label is matched:
match mpls experimental topmost 3Related Commands
set mpls experimental topmost
Sets the MPLS EXP field value in the topmost MPLS label header at the input and/or output interfaces.
match not
To specify the single match criterion value to use as an unsuccessful match criterion, use the match not command in class-map configuration mode. To remove a previously specified source value to not use as a match criterion, use the no form of this command.
match not match-criteria
no match not match-criteria
Syntax Description
match-criteria
Specifies the match criterion value that is an unsuccessful match criterion. All other values of the specified match criterion will be considered successful match criteria.
Defaults
No default behavior or values
Command Modes
Class-map configuration
Command History
12.0(5)XE
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0(5)T.
12.1(1)E
This command was integrated into Cisco IOS Release 12.1(1)E.
Usage Guidelines
The match not command is used to specify a QoS policy value that is not used as a match criterion. When the match not command is used, all other values of that QoS policy become successful match criteria.
For instance, if the match not qos-group 4 command is issued in class-map configuration mode, the specified class will accept all QoS group values except 4 as successful match criteria.
Examples
In the following traffic class, all protocols except IP are considered successful match criteria:
Router(config)# class-map noipRouter(config-cmap)# match not protocol ipRouter(config-cmap)# exitRelated Commands
class-map
Creates a class map to be used for matching packets to a specified class.
match packet length (class-map)
To specify the Layer 3 packet length in the IP header as a match criterion in a class map, use the match packet length command in class-map configuration mode. To remove a previously specified Layer 3 packet length as a match criterion, use the no form of this command.
match packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]}
no match packet length {max maximum-length-value [min minimum-length-value] | min minimum-length-value [max maximum-length-value]}
Syntax Description
Defaults
If only the minimum value is specified, a packet with a Layer 3 length greater than the minimum is viewed as matching the criterion.
If only the maximum value is specified, a packet with a Layer 3 length less than the maximum is viewed as matching the criterion.
Command Modes
Class-map configuration
Command History
Usage Guidelines
This command considers only the Layer 3 packet length in the IP header. It does not consider the Layer 2 packet length in the IP header.
When using this command, you must at least specify the maximum or minimum value. However, you do have the option of entering both values.
Examples
In the following example a class map called "class 1" has been created, and the Layer 3 packet length has been specified as a match criterion. In this example, packets with a minimum Layer 3 packet length of 100 and a maximum Layer 3 packet length of 300 are viewed as meeting the match criteria.
Router(config)# class map match-all class1Router(config-cmap)# match packet length min 100 max 300Related Commands
match precedence
To identify IP precedence values as match criteria, use the match precedence command in class-map configuration mode. To remove IP precedence values from a class map, use the no form of this command.
match [ip] precedence precedence-value [precedence-value precedence-value precedence-value]
no match [ip] precedence precedence value [precedence-value precedence-value precedence-value]
Syntax Description
Defaults
Matching on both IPv4 and IPv6 packets is the default.
Command Modes
Class-map configuration
Command History
Usage Guidelines
Precedence Value Arguments
Up to four precedence values can be matched in one match statement. For example, if you wanted the precedence values of 0, 1, 2, or 3 (note that only one of the precedence values must be a successful match criterion, not all of the specified precedence values), enter the match ip precedence 0 1 2 3 command.
The precedence-value arguments are used as markings only. In this context, the IP precedence values have no mathematical significance. For instance, the precedence-value of 2 is not greater than 1. The value simply indicates that a packet marked with the precedence-value of 2 is different from a packet marked with the precedence-value of 1. The treatment of these different packets is defined by the user through the setting of QoS policies in policy-map class configuration mode.
Match on Precedence for IPv6 Only
To match on precedence values for IPv6 packets only, the match protocol ipv6 command must also be used. Without that command, the precedence match defaults to match both IPv4 and IPv6 packets.
Match on Precedence for IPv4 Packets Only
To match on precedence values for IPv4 packets only, use the ip keyword. Without the ip keyword, the match occurs on both IPv4 and IPv6 packets.
Examples
IPv4-Specific Traffic Match
The following example shows how to configure the service policy called "priority50" and attach service policy "priority50" to an interface, matching for IPv4 traffic only. In a network where both IPv4 and IPv6 are running, you might find it necessary to distinguish between the protocols for matching and traffic segregation. In this example, the class map called "ipprec5" will evaluate all IPv4 packets entering Fast Ethernet interface 1/0/0 for a precedence value of 5. If the incoming IPv4 packet has been marked with the precedence value of 5, the packet will be treated as priority traffic and will be allocated with bandwidth of 50 kbps.
Router(config)# class-map ipprec5Router(config-cmap)# match ip precedence 5Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class ipprec5Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet1/0/0Router(config-if)# service-policy input priority50IPv6-Specific Traffic Match
The following example shows the same service policy matching on precedence for IPv6 traffic only. Notice that the match protocol command with the ipv6 keyword precedes the match precedence command. The match protocol command is required to perform matches on IPv6 traffic alone.
Router(config)# class-map ipprec5Router(config-cmap)# match protocol ipv6Router(config-cmap)# match precedence 5Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class ipprec5Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet1/0/0Router(config-if)# service-policy input priority50Related Commands
match protocol
To configure the match criteria for a class map on the basis of the specified protocol, use the match protocol command in class-map configuration mode. To remove protocol-based match criteria from a class map, use the no form of this command.
match protocol protocol-name
no match protocol protocol-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Class-map configuration
Command History
Usage Guidelines
For class-based weighted fair queueing (CBWFQ), you define traffic classes based on match criteria including protocols, access control lists (ACLs), input interfaces, QoS labels, and EXP field values. Packets satisfying the match criteria for a class constitute the traffic for that class.
The match protocol command specifies the name of a protocol to be used as the match criteria against which packets are checked to determine if they belong to the class specified by the class map.
To use the match protocol command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use one of the following commands to configure its match criteria:
•
•
•
•
If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
To match protocols known to network-based application recognition (NBAR), use the match protocol (NBAR) command.
Examples
The following example specifies a class map called ipx and configures the Internetwork Packet Exchange (IPX) protocol as a match criterion for it:
class-map ipxmatch protocol ipxRelated Commands
match protocol (NBAR)
To configure network-based application recognition (NBAR) to match traffic by a protocol type known to NBAR, use the match protocol command in class- map configuration mode. To disable NBAR from matching traffic by a known protocol type, use the no form of this command.
match protocol protocol-name [variable-field-name value]
no match protocol protocol-name [variable-field-name value]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class-map configuration
Command History
Usage Guidelines
Use the match protocol (NBAR) command to match protocol types that are known to NBAR. NBAR is capable of classifying the following types of protocols:
•
•
•
Table 7 lists the non-UDP and non-TCP IP protocols NBAR can classify.
Table 7 Non-UDP and Non-TCP Protocols
EGP
IP
8
Exterior Gateway Protocol
egp
12.0(5)XE2
12.1(1)E
12.1(5)TEIGRP
IP
88
Enhanced Interior Gateway Routing Protocol
eigrp
12.0(5)XE2
12.1(1)E
12.1(5)TGRE
IP
47
Generic Routing Encapsulation
gre
12.0(5)XE2
12.1(1)E
12.1(5)TICMP
IP
1
Internet Control Message Protocol
icmp
12.0(5)XE2
12.1(1)E
12.1(5)TIPINIP
IP
4
IP in IP
ipinip
12.0(5)XE2
12.1(1)E
12.1(5)TIPSec
IP
50, 51
IP Encapsulating Security Payload/Authentication Header
ipsec
12.0(5)XE2
12.1(1)E
12.1(5)T
1 Indicates the Cisco IOS maintenance release that first supported the protocol. This table is updated when a protocol is added to a new Cisco IOS release train.
Table 8 lists the TCP and UDP static port protocols NBAR can classify.
Table 8 TCP and UDP Static Port Protocols
BGP
TCP/UDP
179
Border Gateway Protocol
bgp
12.0(5)XE2
12.1(1)E
12.1(5)TCU-SeeMe
TCP/UDP
7648, 7649
Desktop videoconferencing
cuseeme
12.0(5)XE2
12.1(1)E
12.1(5)TCU-SeeMe
UDP
24032
Desktop video conferencing
cuseeme
12.0(5)XE2
12.1(1)E
12.1(5)TDHCP/
BOOTPUDP
67, 68
Dynamic Host Configuration Protocol/ Bootstrap Protocol
dhcp
12.0(5)XE2
12.1(1)E
12.1(5)TDNS
TCP/UDP
53
Domain Name System
dns
12.0(5)XE2
12.1(1)E
12.1(5)TFinger
TCP
79
Finger user information protocol
finger
12.0(5)XE2
12.1(1)E
12.1(5)TGopher
TCP/UDP
70
Internet Gopher Protocol
gopher
12.0(5)XE2
12.1(1)E
12.1(5)THTTP
TCP
802
Hypertext Transfer Protocol
http
12.0(5)XE2
12.1(1)E
12.1(5)THTTPS
TCP
443
Secured HTTP
secure-http
12.0(5)XE2
12.1(1)E
12.1(5)TIMAP
TCP/UDP
143, 220
Internet Message Access Protocol
imap
12.0(5)XE2
12.1(1)E
12.1(5)TIRC
TCP/UDP
194
Internet Relay Chat
irc
12.0(5)XE2
12.1(1)E
12.1(5)TKerberos
TCP/UDP
88, 749
Kerberos Network Authentication Service
kerberos
12.0(5)XE2
12.1(1)E
12.1(5)TL2TP
UDP
1701
L2F/L2TP tunnel
l2tp
12.0(5)XE2
12.1(1)E
12.1(5)TLDAP
TCP/UDP
389
Lightweight Directory Access Protocol
ldap
12.0(5)XE2
12.1(1)E
12.1(5)TMS-PPTP
TCP
1723
Microsoft Point-to-Point Tunneling Protocol for VPN
pptp
12.0(5)XE2
12.1(1)E
12.1(5)TMS-
SQLServerTCP
1433
Microsoft SQL Server Desktop Videoconferencing
sqlserver
12.0(5)XE2
12.1(1)E
12.1(5)TNetBIOS
TCP
137, 139
NetBIOS over IP (MS Windows)
netbios
12.0(5)XE2
12.1(1)E
12.1(5)TNetBIOS
UDP
137, 138
NetBIOS over IP (MS Windows)
netbios
12.0(5)XE2
12.1(1)E
12.1(5)TNFS
TCP/UDP
2049
Network File System
nfs
12.0(5)XE2
12.1(1)E
12.1(5)TNNTP
TCP/UDP
119
Network News Transfer Protocol
nntp
12.0(5)XE2
12.1(1)E
12.1(5)TNotes
TCP/UDP
1352
Lotus Notes
notes
12.0(5)XE2
12.1(1)E
12.1(5)TNovadigm
TCP/UDP
3460-3465
Novadigm Enterprise Desktop Manager (EDM)
novadigm
12.1(2)E
12.1(5)TNTP
TCP/UDP
123
Network Time Protocol
ntp
12.0(5)XE2
12.1(1)E
12.1(5)TPCAnywhere
TCP
5631, 65301
Symantec PCAnywhere
pcanywhere
12.0(5)XE2
12.1(1)E
12.1(5)TPCAnywhere
UDP
22, 5632
Symantec PCAnywhere
pcanywhere
12.0(5)XE2
12.1(1)E
12.1(5)TPOP3
TCP/UDP
110
Post Office Protocol
pop3
12.0(5)XE2
12.1(1)E
12.1(5)TPrinter
TCP/UDP
515
Printer
printer
12.1(2)E
12.1(5)TRIP
UDP
520
Routing Information Protocol
rip
12.0(5)XE2
12.1(1)E
12.1(5)TRSVP
UDP
1698, 1699
Resource Reservation Protocol
rsvp
12.0(5)XE2
12.1(1)E
12.1(5)TSFTP
TCP
990
Secure FTP
secure-ftp
12.0(5)XE2
12.1(1)E
12.1(5)TSHTTP
TCP
443
Secure HTTP
secure-http
12.0(5)XE2
12.1(1)E
12.1(5)TSIMAP
TCP/UDP
585, 993
Secure IMAP
secure-imap
12.0(5)XE2
12.1(1)E
12.1(5)TSIRC
TCP/UDP
994
Secure IRC
secure-irc
12.0(5)XE2
12.1(1)E
12.1(5)TSLDAP
TCP/UDP
636
Secure LDAP
secure-ldap
12.0(5)XE2
12.1(1)E
12.1(5)TSMTP
TCP
25
Simple Mail Transfer Protocol
smtp
12.0(5)XE2
12.1(1)E
12.1(5)TSNMP
TCP/UDP
161, 162
Simple Network Management Protocol
snmp
12.0(5)XE2
12.1(1)E
12.1(5)TSNNTP
TCP/UDP
563
Secure NNTP
secure-nntp
12.0(5)XE2
12.1(1)E
12.1(5)TSOCKS
TCP
1080
Firewall security protocol
socks
12.0(5)XE2
12.1(1)E
12.1(5)TSPOP3
TCP/UDP
995
Secure POP3
secure-pop3
12.0(5)XE2
12.1(1)E
12.1(5)TSSH
TCP
22
Secured Shell
ssh
12.0(5)XE2
12.1(1)E
12.1(5)TSTELNET
TCP
992
Secure Telnet
secure-telnet
12.0(5)XE2
12.1(1)E
12.1(5)TSyslog
UDP
514
System Logging Utility
syslog
12.0(5)XE2
12.1(1)E
12.1(5)TTelnet
TCP
23
Telnet Protocol
telnet
12.0(5)XE2
12.1(1)E
12.1(5)TX Windows
TCP
6000-6003
X11, X Windows
xwindows
12.0(5)XE2
12.1(1)E
12.1(5)T
1 Indicates the Cisco IOS maintenance release that first supported the protocol. This table is updated when a protocol is added to a new Cisco IOS release train.
2 In Release 12.3(4)T, the NBAR Extended Inspection for Hypertext Transfer Protocol (HTTP) Traffic feature was introduced. This feature allows NBAR to scan TCP ports that are not well-known and identify HTTP traffic traversing these ports.
Table 9 lists the TCP and UDP stateful protocols NBAR can classify. This table includes packets that require sub-port classification and classification based on deep packet inspection
Table 9 TCP and UDP Stateful Protocols
Citrix ICA
TCP/UDP
Citrix ICA traffic by application name
citrix
citrix app12.1(2)E
12.1(5)TFTP
TCP
File Transfer Protocol
ftp
12.0(5)XE2
12.1(1)E
12.1(5)TExchange
TCP
MS-RPC for Exchange
exchange
12.0(5)XE2
12.1(1)E
12.1(5)TFastTrack
FastTrack
For a list of common FastTrack applications, see the NBAR chapter of the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.3.
fasttrack
12.1(12c)E
Gnutella
TCP
Gnutella
For a list of common Gnutella applications, see the NBAR chapter of the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.3.
gnutella
12.1(12c)E
HTTP
TCP
HTTP with URL, MIME, or host classification
http
12.0(5)XE2
12.1(1)E
12.1(5)T
(HTTP host classification is not available on the 12.0 XE release train)Napster
TCP
Napster traffic
napster
12.1(5)T
Netshow
TCP/UDP
Microsoft Netshow
netshow
12.0(5)XE2
12.1(1)E
12.1(5)Tr-commands
TCP
rsh, rlogin, rexec
rcmd
12.0(5)XE2
12.1(1)E
12.1(5)TRealAudio
TCP/UDP
RealAudio Streaming Protocol
realaudio
12.0(5)XE2
12.1(1)E
12.1(5)TRTP
TCP/UDP
Real-Time Transport Protocol Payload Classification
rtp
12.2(8)T
SQL*NET
TCP/UDP
SQL*NET for Oracle
sqlnet
12.0(5)XE2
12.1(1)E
12.1(5)TStreamWorks
UDP
Xing Technology Stream Works audio and video
streamwork
12.0(5)XE2
12.1(1)E
12.1(5)TSunRPC
TCP/UDP
Sun Remote Procedure Call
sunrpc
12.0(5)XE2
12.1(1)E
12.1(5)TTFTP
UDP
Trivial File Transfer Protocol
tftp
12.0(5)XE2
12.1(1)E
12.1(5)TVDOLive
TCP/UDP
VDOLive Streaming Video
vdolive
12.0(5)XE2
12.1(1)E
12.1(5)T
1 Indicates the Cisco IOS maintenance release that first supported the protocol. This table is updated when a protocol is added to a new Cisco IOS release train.
Custom Protocols Created with the ip nbar custom Command
The variable-field-name value is used in conjunction with the variable field-name field-length options that are entered when you create a custom protocol using the ip nbar custom command. The variable option allows NBAR to match based on a specific value of a custom protocol. For instance, if ip nbar custom ftdd 125 variable scid 2 tcp range 5001 5005 is entered to create a custom protocol, and then a class map using the match protocol ftdd scid 804 is created, the created class map will match all traffic entering or leaving TCP ports 5001-5005 that have value "804" at byte 125.
Up to 24 variable values per custom protocol can be expressed in class maps. For instance, in the following configuration, 4 variables are used and 20 more "scid" values could be used.
ip nbar custom ftdd field scid 125 variable 1 tcp range 5001 5005class-map active-craftmatch protocol ftdd scid 0x15match protocol ftdd scid 0x21class-map passive-craftmatch protocol ftdd scid 0x11match protocol ftdd scid 0x22Examples
The following example configures NBAR to match File Transfer Protocol (FTP) traffic:
match protocol ftpIn the following example, custom protocol ftdd is created using a variable. A class map matching this custom protocol based on the variable is also created. In this example, class map matchscidinftdd will match all traffic entering or leaving TCP ports 5001-5005 that has the value "804" at byte 125. The variable scid is 2 bytes in length.
ip nbar custom ftdd 125 variable scid 2 tcp range 5001 5005class-map matchscidinftdd match protocol ftdd scid 804The same example above can also be done using hexadecimal values in the class map as follows:
ip nbar custom ftdd 125 variable scid 2 tcp range 5001 5005class-map matchscidinftdd
match protocol ftdd scid 0x324In the following example, the variable keyword is used while creating a custom protocol, and class maps are configured to classify different values within the variable field into different traffic classes. Specifically, in the example below, variable scid values 0x15, 0x21, and 0x27 will be classified into class map active-craft while scid values 0x11, 0x22, and 0x25 will be classified into class map passive-craft.
ip nbar custom ftdd field scid 125 variable 1 tcp range 5001 5005class-map active-craftmatch protocol ftdd scid 0x15match protocol ftdd scid 0x21match protocol ftdd scid 0x27class-map passive-craftmatch protocol ftdd scid 0x11match protocol ftdd scid 0x22match protocol ftdd scid 0x25Related Commands
match protocol citrix
To configure network-based application recognition (NBAR) to match Citrix traffic, use the match protocol citrix command in class-map configuration mode. To disable NBAR from matching Citrix traffic, use the no form of this command.
match protocol citrix [app application-name-string]
no match protocol citrix [app application-name-string]
Syntax Description
app
(Optional) Specifies matching of an application name string.
application-name-string
(Optional) Specifies string to be used as the subprotocol parameter.
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
Entering the match protocol citrix command without the app keyword establishes all Citrix traffic as successful match criteria.
Examples
The following example configures NBAR to match all Citrix traffic:
match protocol citrixThe following example configures NBAR to match Citrix traffic with the application name of packet1:
match protocol citrix app packet1match protocol fasttrack
To configure network-based application recognition (NBAR) to match FastTrack peer-to-peer traffic, use the match protocol fasttrack command in class-map configuration mode. To disable NBAR from matching FastTrack traffic, use the no form of this command.
match protocol fasttrack file-transfer "regular-expression"
no match protocol fasttrack file-transfer "regular-expression"
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class-map configuration
Command History
Usage Guidelines
To specify that all FastTrack traffic be identified by the traffic class, use "*" as the regular expression.
Some applications that use FastTrack include KaZaA, Grokster, and Morpheus (although newer versions of Morpheus use Gnutella).
Examples
The following example configures NBAR to match all FastTrack traffic:
match protocol fasttrack file-transfer "*"In the following example, all FastTrack files that have the ".mpeg" extension will be classified into class map nbar:
class-map match-all nbar match protocol fasttrack file-transfer "*.mpeg"The following example configures NBAR to match FastTrack traffic that contains the string "cisco":
match protocol fasttrack file-transfer "*cisco*"
match protocol gnutella
To configure network-based application recognition (NBAR) to match Gnutella peer-to-peer traffic, use the match protocol gnutella command in class-map configuration mode. To disable NBAR from matching Gnutella traffic, use the no form of this command.
match protocol gnutella file-transfer "regular-expression"
no match protocol gnutella file-transfer "regular-expression"
Syntax Description
Defaults
No default behavior or values.
Command Modes
Class-map configuration
Command History
Usage Guidelines
To specify that all Gnutella traffic be identified by the traffic class, use "*" as the regular expression.
Applications that use Gnutella include the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
Examples
The following example configures NBAR to match all Gnutella traffic:
match protocol gnutella file-transfer "*"In the following example, all Gnutella files that have the ".mpeg" extension will be classified into class map nbar:
class-map match-all nbar match protocol gnutella file-transfer "*.mpeg"In the following example, only Gnutella traffic that contains the characters "cisco" is classified:
class-map match-all nbar match protocol gnutella file-transfer "*cisco*"match protocol http
To configure network-based application recognition (NBAR) to match Hypertext Transfer Protocol (HTT) traffic by URL, HOST, or Multipurpose Internet Mail Extension (MIME)-type, use the match protocol http command in class-map configuration mode. To disable NBAR from matching HTTP traffic by URL, HOST, or MIME-type, use the no form of this command.
match protocol http [url url-string | host hostname-string | mime MIME-type]
no match protocol http [url url-string | host hostname-string | mime MIME-type]
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
In Cisco IOS Release 12.3(4)T, the NBAR Extended Inspection for HTTP Traffic feature was introduced. This feature allows NBAR to scan TCP ports that are not well-known and identify HTTP traffic traversing these ports. This feature is enabled automatically when a service policy containing the match protocol http command is attached to an interface.
When matching by MIME-type, the MIME-type can contain any user-specified text string. Refer to the the Internet Assigned Numbers Authority (IANA) web page (www.iana.com) for a list of the IANA-registered MIME types.
When matching by MIME-type is performed, NBAR matches a packet containing the MIME-type and all subsequent packets until the next HTTP transaction.
When matching by HOST is performed, NBAR performs a regular expression match on the host field contents inside an HTTP packet and classifies all packets from that host.
HTTP URL matching supports GET, PUT, HEAD, POST, DELETE, and TRACE. When matching by URL, NBAR recognizes the HTTP packets containing the URL, and then matches all packets that are part of the HTTP request. When specifying a URL for classification, include only the portion of the URL following the www.hostname.domain in the match statement. For example, in the URL www.anydomain.com/latest/whatsnew.html include only /latest/whatsnew.html.
To match the www.anydomain.com portion, use the host name matching feature. The URL or host specification strings can take the form of a regular expression with options shown in Table 10.
Examples
The following example classifies, within the class map called "class1," HTTP packets based on any URL containing the string "whatsnew/latest" followed by zero or more characters:
class-map class1match protocol http url whatsnew/latest*The following example classifies, within the class map called "class2," packets based on any host name containing the string "cisco" followed by zero or more characters:
class-map class2match protocol http host cisco*The following example classifies, within the class map called "class3," packets based on the Joint Photographics Expert Group (JPEG) MIME type:
class-map class3match protocol http mime "*jpeg"match protocol rtp
To configure network-based application recognition (NBAR) to match Real-Time Transfer Protocol (RTP) traffic, use the match protocol rtp command in class-map configuration mode. To disable NBAR from matching RTP traffic, use the no form of this command.
match protocol rtp [audio | video | payload-type payload-string]
no match protocol rtp [audio | video | payload-type payload-string]
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
Entering the match protocol rtp command without any other keywords establishes all RTP traffic as successful match criteria.
RTP is a packet format for multimedia data streams. It can be used for media-on-demand as well as interactive services such as Internet telephony. RTP consists of a data and a control part. The control part is called Real-Time Transport Control Protocol (RTCP). It is important to note that the NBAR RTP Payload Classification feature does not identify RTCP packets and that RTCP packets run on odd-numbered ports while RTP packets run on even-numbered ports.
The payload type field of an RTP packet identifies the format of the RTP payload and is represented by a number. NBAR matches RTP traffic on the basis of this field in the RTP packet. A working knowledge of RTP and RTP payload types is helpful if you want to configure NBAR to match RTP traffic. For more information about RTP and RTP payload types, refer to RFC 1889, RTP: A Transport Protocol for Real-Time Applications.
Examples
The following example configures NBAR to match all RTP traffic:
class-map class1match protocol rtpThe following example configures NBAR to match RTP traffic with the payload-types 0, 1, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, and 64:
class-map class2match protocol rtp payload-type "0, 1, 4-0x10, 10001b-10010b, 64"match qos-group
To identify a specific quality of service (QoS) group value as a match criterion, use the match qos-group command in class-map configuration mode. To remove a specific QoS group value from a class map, use the no form of this command.
match qos-group qos-group-value
no match qos-group qos-group-value
Syntax Description
Defaults
No match criteria are specified.
Command Modes
Class-map configuration
Command History
Usage Guidelines
The match qos-group command is used by the class map to identify a specific QoS group value marking on a packet. This command can also be used to convey the received Multiprotocol Label Switching (MPLS) experimental (EXP) field value to the output interface.
The qos-group-value arguments are used as markings only. The QoS group values have no mathematical significance. For instance, the qos-group-value of 2 is not greater than 1. The value simply indicates that a packet marked with the qos-group-value of 2 is different than a packet marked with the qos-group-value of 1. The treatment of these packets is defined by the user through the setting of QoS policies in policy-map class configuration mode.
The QoS group value is local to the router, meaning that the QoS group value that is marked on a packet does not leave the router when the packet leaves the router. If you need a marking that resides in the packet, use IP precedence setting, IP differentiated services code point (DSCP) setting, or another method of packet marking.
Examples
The following example shows how to configure the service policy called "priority50" and attach service policy "priority50" to an interface. In this example, the class map called "qosgroup5" will evaluate all packets entering Fast Ethernet interface 1/0/0 for a QoS group value of 5. If the incoming packet has been marked with the QoS group value of 5, the packet will be treated with a priority level of 50.
Router(config)# class-map qosgroup5Router(config-cmap)# match qos-group 5Router(config)# exitRouter(config)# policy-map priority50Router(config-pmap)# class qosgroup5Router(config-pmap-c)# priority 50Router(config-pmap-c)# exitRouter(config-pmap)# exitRouter(config)# interface fastethernet1/0/0Router(config-if)# service-policy output priority50The following example shows that the packet named "qos-group 1" belongs to a particular class:
match qos-group 1Related Commands
match source-address mac
To use the source MAC address as a match criterion, use the match source-address mac command in class-map configuration mode. To remove a previously specified source MAC address as a match criterion in class-map configuration mode, use the no form of this command.
match source-address mac address-destination
no match source-address mac address-destination
Syntax Description
Defaults
No default behavior or values
Command Modes
Class-map configuration
Command History
12.0(5)XE
This command was introduced.
12.1(1)E
This command was integrated into Cisco IOS Release 12.1(1)E.
12.1(5)T
This command was integrated into Cisco IOS Release 12.1(5)T.
Usage Guidelines
This command can be used only on an input interface with a MAC address. These interfaces include Fast Ethernet and Ethernet interfaces.
This command cannot be used on output interfaces with no MAC address, such as serial and ATM interfaces.
Examples
The following example uses the MAC address mac 0.0.0 as a match criterion:
class-map matchsrcmac match source-address mac 0.0.0Related Commands
class-map
Creates a class map to be used for matching packets to a specified class.
max-reserved-bandwidth
To change the percent of interface bandwidth allocated for Resource Reservation Protocol (RSVP), class-based weighted fair queueing (CBWFQ), low latency queueing (LLQ), IP RTP Priority, Frame Relay IP RTP Priority, and Frame Relay PVC Interface Priority Queueing (PIPQ), use the max-reserved bandwidth command in interface configuration mode. To restore the default value, use the no form of this command.
max-reserved-bandwidth percent
no max-reserved-bandwidth
Syntax Description
percent
Percent of interface bandwidth allocated for RSVP, CBWFQ, LLQ, IP RTP Priority, Frame Relay IP RTP Priority, and Frame Relay PIPQ.
Defaults
75 percent
Command Modes
Interface configuration
Command History
Usage Guidelines
The sum of all bandwidth allocation on an interface should not exceed 75 percent of the available bandwidth on an interface. The remaining 25 percent of bandwidth is used for overhead, including Layer 2 overhead, control traffic, and best-effort traffic.
If you need to allocate more than 75 percent for RSVP, CBWFQ, LLQ, IP RTP Priority, Frame Relay IP RTP Priority, and Frame Relay PIPQ, you can use the max-reserved-bandwidth command. The percent argument specifies the maximum percentage of the total interface bandwidth that can be used.
Examples
In the following example, the policy map called policy1 is configured for three classes with a total of 8 Mbps configured bandwidth, as shown in the output from the show policy-map command:
Router# show policy-map policy1Policy Map policy1Weighted Fair QueueingClass class1Bandwidth 2500 (kbps) Max Threshold 64 (packets)Class class2Bandwidth 2500 (kbps) Max Threshold 64 (packets)Class class3Bandwidth 3000 (kbps) Max Threshold 64 (packets)When you enter the service-policy command in an attempt to attach the policy map on a 10-Mbps Ethernet interface, an error message such as the following is produced:
I/f Ethernet1/1 class class3 requested bandwidth 3000 (kbps) Available only 2500 (kbps)The error message is produced because the default maximum configurable bandwidth is 75 percent of the available interface bandwidth, which in this example is 7.5 Mbps. To change the maximum configurable bandwidth to 80 percent, use the max-reserved-bandwidth command in interface configuration mode, as follows:
max-reserved-bandwidth 80service output policy1endTo verify that the policy map was attached, enter the show policy-map interface command:
Router# show policy-map interface e1/1Ethernet1/1 output :policy1Weighted Fair QueueingClass class1Output Queue:Conversation 265Bandwidth 2500 (kbps) Packets Matched 0 Max Threshold 64 (packets)(discards/tail drops) 0/0Class class2Output Queue:Conversation 266Bandwidth 2500 (kbps) Packets Matched 0 Max Threshold 64 (packets)(discards/tail drops) 0/0Class class3Output Queue:Conversation 267Bandwidth 3000 (kbps) Packets Matched 0 Max Threshold 64 (packets)(discards/tail drops) 0/0Virtual Template Configuration Example
The following example configures a strict priority queue in a virtual template configuration with CBWFQ. The max-reserved-bandwidth command changes the maximum bandwidth allocated between CBWFQ and IP RTP Priority from the default (75 percent) to 80 percent.
multilink virtual-template 1interface virtual-template 1ip address 172.16.1.1 255.255.255.0no ip directed-broadcastip rtp priority 16384 16383 25service-policy output policy1ppp multilinkppp multilink fragment-delay 20ppp multilink interleavemax-reserved-bandwidth 80endinterface Serial0/1bandwidth 64ip address 10.1.1.2 255.255.255.0no ip directed-broadcastencapsulation pppppp multilinkend
Note
Related Commands
mpls experimental
To configure Multiprotocol Label Switching (MPLS) experimental (EXP) levels for a virtual circuit (VC) class that can be assigned to a VC bundle and thus applied to all VC members of that bundle, use the mpls experimental command in vc-class configuration mode. To remove the MPLS EXP levels from the VC class, use the no form of this command.
To configure the MPLS EXP levels for a VC member of a bundle, use the mpls experimental command in bundle-vc configuration mode. To remove the MPLS EXP levels from the VC, use the no form of this command.
mpls experimental [other | range]
no mpls experimental
Syntax Description
Defaults
Defaults to other, that is, any MPLS EXP levels that are not explicitly configured.
Command Modes
VC-class configuration (for a VC class)
Bundle-vc configuration (for ATM VC bundle members)
Command History
Usage Guidelines
Assignment of MPLS EXP levels to VC bundle members allows you to create differentiated service because you can distribute the MPLS EXP levels over the different VC bundle members. You can map a single level or a range of levels to each discrete VC in the bundle, thereby enabling VCs in the bundle to carry packets marked with different levels. Alternatively, you can configure a VC with the mpls experimental other command to indicate that it can carry traffic marked with levels not specifically configured for it. Only one VC in the bundle can be configured with the mpls experimental other command to carry all levels not specified. This VC is considered the default one.
To use this command in vc-class configuration mode, enter the vc-class atm global configuration command before you enter this command. This command has no effect if the VC class that contains the command is attached to a standalone VC, that is, if the VC is not a bundle member.
To use this command to configure an individual bundle member in bundle-vc configuration mode, first enter the bundle command to enact bundle configuration mode for the bundle to which you want to add or modify the VC member to be configured. Then, use the pvc-bundle command to specify the VC to be created or modified and enter bundle-vc configuration mode.
VCs in a VC bundle are subject to the following configuration inheritance guidelines (listed in order of next highest MPLS EXP level):
•
•
•
Note
Examples
The following example configures a class called "control-class" that includes the mpls experimental command that, when applied to a bundle, configures all VC members of that bundle to carry MPLS EXP level 7 traffic. Note, however, that VC members of that bundle can be individually configured with the mpls experimental command at the bundle-vc level, which would supervene.
vc-class atm control-classmpls experimental 7The following example configures permanent virtual circuit (PVC) 401 (with the name "control-class") to carry traffic with MPLS EXP levels in the range of 4 to 2, overriding the level mapping set for the VC through vc-class configuration:
pvc-bundle control-class 401mpls experimental 4-2Related Commands
