Table of Contents
Quality of Service Commands: match access-group Through pvc-bundle
This chapter explains the function and syntax of the quality of service commands from match access-group through pvc-bundle. For more information about defaults and usage guidelines, see the corresponding chapter of the Cisco IOS Quality of Service Solutions Command Reference, Release 12.1.
To configure the match criteria for a class map based on the specified Access Control List (ACL) number or name, use the match access-group class map configuration command. 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
access-group
| A numbered ACL whose contents are used as the match criteria against which packets are checked to determine if they belong to this class.
|
name access-group-name
| A named ACL whose contents are used as the match criteria against which packets are checked to determine if they belong to this class.
|
To configure a class map to use the specified input interface as a match criterion, use the match input-interface class map configuration command. 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
interface-name
| Name of the input interface to be used as match criteria
|
To configure a class map to use the specified value of the EXP field as a match criterion, use the match mpls experimental class map configuration command. 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
| The EXP field value to be used as match criteria. Any number from 0 to 7.
|
To configure the match criteria for a class map based on the specified protocol, use the match protocol class map configuration command. To remove protocol-based match criteria from a class map, use the no form of this command.
match protocol protocol
no match protocol protocol
Syntax Description
protocol
| Name of the protocol to match against. The following protocols are supported:
aarp---AppleTalk ARP
apollo---Apollo Domain
arp---IP ARP
bridge---Bridging
bstun---Block Serial Tunnel
cdp---Cisco Discovery Tunnel
clns---ISO CLNS
clns_es---ISO CLNS End System
clns_is---ISO CLNS Intermediate System
cmns---ISO CMNS
compressedtcp---Compressed TCP
decnet---DECnet
decnet_node---DECnet Node
decnet_router-I1---DECnet Router L1
decnet_router-I2---DECnet Router L2
dlsw---Data Link Switching
ip---IP
ipx---Novell IPX
llc2---llc2
pad---PAD links
qllc---qllc protocol
rsrb---Remote Source-Route Bridging
snapshot---Snapshot routing support
stun---Serial Tunnel
vines---Banyan Vines
xns---Xerox Network Services
|
To change the percent of interface bandwidth allocated for class-based weighted fair queueing (CBWFQ), low latency queueing (LLQ), and IP RTP Priority, use the max-reserved bandwidth interface configuration command. 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 CBWFQ, LLQ, and IP RTP Priority.
|
To enable end-to-end F5 operation, administration, and maintenance (OAM) loopback cell generation and OAM management for a virtual circuit (VC) class that can be applied to a VC bundle, use the oam-bundle vc-class configuration command. To remove OAM management from the class configuration, use the no form of this command.
To enable end-to-end F5 OAM loopback cell generation and OAM management for all VC members of a bundle, use the oam-bundle bundle configuration command. To remove OAM management from the bundle, use the no form of this command.
oam-bundle [manage] [frequency]
no oam-bundle [manage] [frequency]
Syntax Description
manage
| (Optional) Enables OAM management. If omitted, loopback cells are sent but the bundle is not managed.
|
frequency
| (Optional) Number of seconds between sending OAM loopback cells. Values range from 0 to 600 seconds.
|
To create or modify a policy map that can be attached to one or more interfaces to specify a service policy, use the policy-map global configuration command. To delete a policy map, use the no form of this command.
policy-map policy-map
no policy-map policy-map
Syntax Description
policy-map
| Name of the policy map.
|
To configure precedence 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 precedence vc-class configuration command. To remove the precedence levels from the VC class, use the no form of this command.
To configure the precedence levels for a VC member of a bundle, use the precedence bundle-vc configuration command. To remove the precedence levels from the VC, use the no form of this command.
precedence [other | range]
no precedence
Syntax Description
other
| (Optional) Any precedence levels in the range of 0 to 7 that are not explicitly configured. This is the default.
|
range
| (Optional) A single precedence level specified as a number, or a range of precedence levels, specified as a hyphenated range.
|
To configure a Weighted Random Early Detection (WRED) or VIP-Distributed WRED (DWRED) group for a particular IP Precedence, use the precedence random-detect-group configuration command. To return the values for each IP Precedence for the group to the default values, use the no form of this command.
precedence precedence min-threshold max-threshold mark-probability-denominator
no precedence precedence min-threshold max-threshold mark-probability-denominator
Syntax Description
precedence
| IP precedence number. The value range is from 0 to 7.
|
min-threshold
| Minimum threshold in number of packets. The value ranges from 1 to 4096. When the average queue length reaches this number, WRED/DWRED begins to drop packets with the specified IP Precedence.
|
max-threshold
| Maximum threshold in number of packets. The value range is min-threshold to 4096. When the average queue length exceeds this number, WRED/DWRED drops all packets with the specified IP Precedence.
|
mark-probability-denominator
| Denominator for the fraction of packets dropped when the average queue depth is max-threshold. For example, if the denominator is 512, one out of every 512 packets is dropped when the average queue is at the max-threshold. The value is 1 to 65536. The default is 10; one out of every ten packets is dropped at the max-threshold.
|
To give priority to a class within a policy map, use the priority policy-map class configuration command. To disable the strict priority queue, use the no form of this command.
priority bandwidth
no priority [bandwidth]
Syntax Description
bandwidth
| Guaranteed allowed bandwidth (in kbps) for the priority traffic. Beyond the guaranteed bandwidth, the priority traffic will be dropped in the event of congestion to ensure that the nonpriority traffic is not starved.
|
To assign the specified priority list to an interface, use the priority-group interface configuration command. To remove the specified priority group assignment, use the no form of this command.
priority-group list-number
no priority-group list-number
Syntax Description
list-number
| Priority list number assigned to the interface. Any number from 1 to 16.
|
To assign a priority queue for those packets that do not match any other rule in the priority list, use the priority-list default global configuration command. To return to the default or assign normal as the default, use the no form of this command.
priority-list list-number default {high | medium | normal | low}
no priority-list list-number
Syntax Description
list-number
| Any number from 1 to 16 that identifies the priority list.
|
high | medium | normal | low
| Priority queue level. The normal queue is used, if you use the no form of this command.
|
To establish queueing priorities on packets entering from a given interface, use the priority-list interface global configuration command. To remove an entry from the list, use the no form of this command with the appropriate arguments.
priority-list list-number interface interface-type interface-number {high | medium | normal | low}
no priority-list list-number
Syntax Description
list-number
| Arbitrary integer from 1 to 16 that identifies the priority list selected by the user.
|
interface-type
| The type of the interface.
|
interface-number
| The number of the interface.
|
high | medium | normal | low
| Priority queue level.
|
To establish queueing priorities based upon the protocol type, use the priority-list protocol global configuration command. To remove a priority list entry assigned by protocol type, use the no form of this command followed by the appropriate list-number argument and the protocol keyword.
priority-list list-number protocol protocol-name {high | medium | normal | low} queue-keyword keyword-value
no priority-list list-number protocol [protocol-name {high | medium | normal | low} queue-keyword keyword-value]
Syntax Description
list-number
| Any number from 1 to 16 that identifies the priority list selected by the user.
|
protocol-name
| Protocol type: aarp, apollo, appletalk, arp, bridge (transparent), clns, clns_es, clns_is, compressedtcp, cmns, decnet, decnet_node, decnet_router-l1, decnet_router-l2, dlsw, ip, ipx, pad, rsrb, stun, vines, xns, and x25.
|
high | medium | normal | low
| Priority queue level.
|
queue-keyword keyword-value
| Possible keywords are fragments, gt, list, lt, tcp, and udp.
|
To specify the maximum number of packets that can be waiting in each of the priority queues, use the priority-list queue-limit global configuration command. To select the normal queue, use the no form of this command.
priority-list list-number queue-limit [high-limit [medium-limit [normal-limit [low-limit]]]]
no priority-list list-number queue-limit
Syntax Description
list-number
| Any number from 1 to 16 that identifies the priority list.
|
high-limit
medium-limit
normal-limit
low-limit
| (Optional) Priority queue maximum length. A value of 0 for any of the four arguments means that the queue can be of unlimited size for that particular queue.
|
To configure a virtual circuit (VC) class with protected group or protected VC status for application to a VC bundle member, use the protect command in vc-class configuration mode. To remove the protected status from the VC class, use the no form of this command.
To configure a specific VC as part of the bundle's protected group or configure it as an individually protected VC bundle member, use the protect command in bundle-vc configuration mode. To remove the protected status from the VC, use the no form of this command.
protect {group | vc}
no protect {group | vc}
Syntax Description
group
| Configures the VC bundle member to be part of the bundle's protected group.
|
vc
| Configures the VC member as individually protected.
|
To add a virtual circuit (VC) to a bundle as a member of the bundle and enter bundle-vc configuration mode in order to configure that VC bundle member, use the pvc-bundle bundle configuration command. To remove the VC from the bundle, use the no form of this command.
pvc-bundle pvc-name [vpi/] [vci]
no pvc-bundle pvc-name [vpi/] [vci]
Syntax Description
pvc-name
| The name of the VC.
|
vpi/
| (Optional) ATM network virtual path identifier (VPI) for this permanent virtual circuit (PVC). The absence of the "/" and a vpi value defaults the vpi value to 0.
On the Cisco 7200 and 7500 series routers, this value ranges from 0 to 255; on the Cisco 4500 and 4700 routers, this value ranges from 0 to 1 less than the quotient of 8192 divided by the value set by the atm vc-per-vp command.
The arguments vpi and vci cannot both be set to 0; if one is 0, the other cannot be 0.
|
vci
| (Optional) ATM network virtual channel identifier (VCI) for this PVC. This value ranges from 0 to 1 less than the maximum value set for this interface by the atm vc-per-vp command. Typically, lower values 0 to 31 are reserved for specific traffic (for example, F4 OAM, SVC signalling, ILMI, and so on) and should not be used.
The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single link, not throughout the ATM network, because it has local significance only.
The arguments vpi and vci cannot both be set to 0; if one is 0, the other cannot be 0.
|
Posted: Wed Jul 26 13:36:01 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.
