|
|
Use the commands in this chapter to configure quality of service (QoS), a measure of performance for a transmission system that reflects its transmission quality and service availability. The commands are arranged alphabetically.
For QoS configuration information and examples, refer to the Quality of Service Solutions Configuration Guide.
To configure an access list for use with committed access rate (CAR) policies, use the access-list rate-limit global configuration command. To remove the access list from the configuration, use the no form of this command.
access-list rate-limit acl-index {precedence | mac-address | mask prec-mask}
acl-index | Access list number. Use any number from 1 to 99 to classify packets by precedence or precedence mask, and use any number from 100 to 199 to classify by MAC address. |
precedence | IP precedence. |
mac-address | Address of the MAC. |
mask prec-mask | IP precedence mask; a two-digit hexadecimal number. Use this option when you want to assign multiple precedences to the same rate-limit access list. |
No CAR access lists are configured.
Global configuration
This command first appeared in Cisco IOS Release 11.1 CC.
This command classifies packets by the specified IP precedence or MAC address for a particular CAR access list. You can then apply CAR policies, using the rate-limit command, to individual rate limit access lists. Thus, packets with different IP precedences or MAC addresses are treated differently by the CAR process.
You can specify only one command for each rate limit access list. If you enter this command multiple times with the same access list number, the new command will overwrite the previous command.
Use the mask keyword to assign multiple IP precedences to the same rate-limit list. To determine the mask value, perform the following steps:
Step 1 Decide which precedences you want to assign to this rate-limit access list.
Step 2 Convert the precedences into an 8-bit number with each bit corresponding to one precedence. For example, an IP precedence of 0 corresponds to 00000001, 1 corresponds to 00000010, 6 corresponds to 01000000, and 7 corresponds to 10000000.
Step 3 Add the 8-bit numbers for the selected precedences. For example, the mask for precedences 1 and 6 is 01000010.
Step 4 The command expects hexadecimal format. Convert the binary mask into the corresponding hexadecimal number. For example, 01000010 becomes 42. This value is used in the access-list rate-limit command. Any packets that have an IP precedence of 1 or 6 will match this access list.
A mask of FF matches any precedence, and 00 does not match any precedence.
The following example assigns any packets with a MAC address of 00e0.34b0.7777 to rate-limit access list 100:
router(config)# access-list rate-limit 100 00e0.34b0.7777
The following example assigns packets with an IP precedence of 0, 1, or 2 to the rate-limit access list 25:
router(config)# access-list rate-limit 25 mask 42
You can use the master indexes or search online to find documentation of related commands.
show access-lists rate-limit
show ip cef
To enable Policy Propagation via Border Gateway Protocol (BGP) on the interface, use the bgp-policy interface configuration command. To disable Policy Propagation via BGP, use the no form of this command.
bgp-policy ip-prec-map
ip-prec-map | QoS policy based on the IP precedence. |
Policy Propagation via BGP is disabled.
Interface configuration
This command first appeared in Cisco IOS Release 11.1 CC.
For the Policy Propagation via BGP feature to work, you must enable BGP and CEF/DCEF. In addition, the proper route-map configuration must be in place to specify the IP precedence (for example, set ip precedence route-map configuration command).
To display QoS policy information for the interface, use the show ip interface command.
The following example enables Policy Propagation via BGP on an interface based on the source address and the IP precedence setting:
router# configure terminal router(config)# interface ethernet 4/0/0 router(config-if)# bgp-policy ip-prec-map router(config-if)# end router#
To assign a custom queue list to an interface, use the custom-queue-list interface configuration command. To remove a specific list or all list assignments, use the no form of the command.
custom-queue-list list
list | Any number from 1 to 16 for the custom queue list. |
No custom queue list is assigned.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Only one queue list can be assigned per interface. Use this command in place of the priority-list command (not in addition to it). Custom queueing allows a fairness not provided with priority queueing. With custom queueing, you can control the interface's available bandwidth when it is unable to accommodate the aggregate traffic enqueued. Associated with each output queue is a configurable byte count, which specifies how many bytes of data should be delivered from the current queue by the system before the system moves on to the next queue. When a particular queue is being processed, packets are sent until the number of bytes sent exceeds the queue byte count or until the queue is empty.
Use the show queueing custom and show interface commands to display the current status of the custom output queues.
In the following example, custom queue list number 3 is assigned to serial interface 0:
router(config)# interface serial 0 router(config-if)# custom-queue-list 3
You can use the master indexes or search online to find documentation of related commands.
queue-list default
queue-list interface
queue-list queue byte-count
queue-list queue limit
show interfaces
show queue
show queueing
To enable weighted fair queueing (WFQ) for an interface, use the fair-queue interface configuration command. To disable weighted fair queueing for an interface, use the no form of this command.
fair-queue [congestive-discard-threshold [dynamic-queues [reservable-queues]]]
congestive-discard-threshold | (Optional) Number of messages allowed in each queue. The default is 64 messages, and a new threshold must be a power of 2 in the range 16 to 4096. When a conversation reaches this threshold, new message packets are discarded. |
dynamic-queues | (Optional) Number of dynamic queues used for best-effort conversations (that is, a normal conversation not requiring any special network services). Values are 16, 32, 64, 128, 256, 512, 1024, 2048, and 4096. The default is 256. |
reservable-queues | (Optional) Number of reservable queues used for reserved conversations in the range 0 to 1000. The default is 0. Reservable queues are used for interfaces configured for features such as Resource Reservation Protocol (RSVP). |
Fair queueing is enabled by default for physical interfaces whose bandwidth is less than or equal to 2.048 Mbps and that do not use the following: X.25 and Synchronous Data Link Control (SDLC) encapsulations; Link Access Procedure, Balanced (LAPB); tunnels; loopbacks; dialer; bridges; or virtual interfaces. Fair queueing is not an option for these protocols. However, if custom queueing or priority queueing is enabled for a qualifying link, it overrides fair queueing, effectively disabling it. Additionally, fair queueing is automatically disabled if you enable the autonomous or silicon switching engine mechanisms.
Interface configuration
This command first appeared in Cisco IOS Release 11.0.
The command enables WFQ. With WFQ, packets are classified by flow. For example, packets with the same source IP address, destination IP address, source TCP or UDP port, destination TCP or UDP port, and protocol belong to the same flow; see Table 3 for a full list of protocols and traffic stream discrimination fields.
When enabled for an interface, WFQ provides traffic priority management that automatically sorts among individual traffic streams without requiring that you first define access lists. Enabling WFQ requires use of this command only.
When WFQ is enabled for an interface, new messages for high-bandwidth traffic streams are discarded after the configured or default congestive discard threshold has been met. However, low-bandwidth conversations, which include control message conversations, continue to enqueue data. As a result, the fair queue may occasionally contain more messages than its configured threshold number specifies.
WFQ uses a traffic data stream discrimination registry service to determine which traffic stream a message belongs to. For each forwarding protocol, Table 3 shows the attributes of a message that are used to classify traffic into data streams.
| Forwarder | Fields Used |
|---|---|
AppleTalk |
|
CLNS |
|
DECnet |
|
Frame Relay switching |
|
IP |
|
Transparent bridging |
|
Source-route bridging |
|
VINES |
|
Apollo |
|
XNS |
|
Novell NetWare |
|
All others (default) |
|
It is important to note that IP precedence, congestion in Frame Relay switching, and discard eligibility flags affect the weights used for queueing.
Fair queueing is supported for all LAN and line (WAN) protocols except X.25, including LAPB and SDLC; see the notes in the section "Default." Because tunnels are software interfaces that are themselves routed over physical interfaces, fair queueing is not supported for tunnels. Fair queueing is on by default for interfaces with bandwidth less than or equal to 2 Mbps.
The following example enables use of WFQ on serial interface 0, with a congestive threshold of 300. This threshold means that messages will be discarded from the queueing system only when 300 or more messages have been queued and the message is in a data stream that has more than one message in the queue. The transmit queue limit is set to 2, based on the 384-kilobit (Kb) line set by the bandwidth command:
router(config)# interface serial 0 router(config-if)# bandwidth 384 router(config-if)# fair-queue 300
Unspecified parameters take the default values.
The following example requests a fair queue with a congestive discard threshold of 64 messages,
512 dynamic queues, and 18 RSVP queues:
router(config)# interface Serial 3/0 router(config-if)# ip unnumbered Ethernet 0/0 router(config-if)# fair-queue 64 512 18
You can use the master indexes or search online to find documentation of related commands.
custom-queue-list
priority-group
priority-list default
show interfaces
show queue
show queueing
To enable distributed weighted fair queueing (DWFQ), use the fair-queue interface configuration command. The command enables DWFQ on an interface using a VIP2-40 or greater interface processor. To disable DWFQ, use the no form of this command.
fair-queueThis command has no arguments or keywords.
DWFQ is enabled by default for physical interfaces whose bandwidth is less than or equal to
2.048 Mbps.
Table 4 lists the default queue lengths and thresholds.
| Queue or Threshold | Default |
|---|---|
Congestive discard threshold | 64 messages |
Dynamic queues | 256 |
Reservable queues | 0 |
Interface configuration
This command first appeared in Cisco IOS Release 11.1.
With DWFQ, packets are classified by flow. Packets with the same source IP address, destination IP address, source TCP or UDP port, destination TCP or UDP port, and protocol belong to the same flow.
DWFQ allocates an equal share of the bandwidth to each flow.
The following example enables DWFQ on the HSSI 0/0/0 interface:
router(config)# interface Hssi0/0/0 router(config-if)# description 45Mbps to R2 router(config-if)# ip address 200.200.14.250 255.255.255.252 router(config-if)# fair-queue
show interfaces
show interfaces fair-queue
To enable RSVP for IP on an interface, use the ip rsvp bandwidth interface configuration command. To disable RSVP, use the no form of the command.
ip rsvp bandwidth [interface-kbps [single-flow-kbps]]
interface-kbps | (Optional) Amount of bandwidth (in kbps) on interface to be reserved. The range is 1 to 10000000. |
single-flow-kbps | (Optional) Amount of bandwidth (in kbps) allocated to a single flow. The range is 1 to 10000000. |
RSVP is disabled if this command is not entered. When enabled without the optional arguments, RSVP is enabled and 75 percent of the link bandwidth is reserved for it.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command is not supported on VIP-based routers. RSVP is disabled by default to allow backward compatibility with systems that do not implement RSVP. Weighted Random Early Detection (WRED) or fair queueing must be enabled first.
The following example shows a T1 (1536 kbps) link configured to permit RSVP reservation of up to 1158 kbps, but no more than 100 kbps for any given flow on serial interface 0. Fair queueing is configured with 15 reservable queues to support those reserved flows, should they be required.
router(config)# interface serial 0
router(config-if)# fair-queue 64 256 15 router(config-if)# ip rsvp bandwidth 1158 100
You can use the master indexes or search online to find documentation of related commands.
fair-queue
ip rsvp neighbors
ip rsvp reservation
ip rsvp sender
ip rsvp udp-multicast
random-detect
show ip rsvp installed
show ip rsvp interface
show ip rsvp neighbor
show ip rsvp reservation
show ip rsvp sender
To enable neighbors to request a reservation, use the ip rsvp neighbors interface configuration command. To disable this feature, use the no form of the command.
ip rsvp neighbors access-list-number
access-list-number | Number of a standard or extended access list. It can be any number from 1 to 199. |
The router accepts messages from any neighbor.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
This command is not supported on VIP-based routers. Use this command to allow only specific RSVP neighbors to make a reservation. If no limits are specified, any neighbor can request a reservation. If an access list is specified, only neighbors meeting the specified access list requirements can make a reservation.
The following example allows neighbors meeting access list 1 requirements to request a reservation:
router(config)# interface ethernet 0 router(config-if)# ip rsvp neighbors 1
You can use the master indexes or search online to find documentation of related commands.
fair-queue
ip rsvp bandwidth
ip rsvp reservation
ip rsvp sender
ip rsvp udp-multicast
random-detect
show ip rsvp installed
show ip rsvp interface
show ip rsvp neighbor
show ip rsvp reservation
show ip rsvp sender
To enable a router to generate an RSVP RESV message, use the ip rsvp reservation interface configuration command. To disable this feature, use the no form of the command.
ip rsvp reservation session-ip-address sender-ip-address {tcp | udp | ip-protocol}
session-ip-address | For unicast sessions, this is the address of the intended receiver; for multicast sessions, it is the IP multicast address of the session. |
sender-ip-address | The IP address of the sender. |
tcp | udp | ip-protocol | TCP, UDP, or IP protocol in the range 0 to 255. |
session-dport | Session-dport is the destination port. Sender-sport is the source port. Port numbers are specified in all cases, as the use of 16-bit ports following the IP header is not limited to UDP or TCP. If destination is zero, source must be zero, and the implication is that ports are not checked. If destination is nonzero, source must be nonzero. |
next-hop-ip-address | Host name or address of the receiver or the router closest to the receiver. |
next-hop-interface | Next hop interface or subinterface type and number. Interface type can be ethernet, loopback, null, or serial. |
ff | se | wf | Reservation style: Fixed Filter (ff) is single reservation. Shared Explicit (se) is shared reservation, limited scope. Wild Card Filter (wf) is shared reservation, unlimited scope. |
rate | load | QoS guaranteed bit rate service or controlled load service. |
bandwidth | Average bit rate (kbps) to reserve up to 75 percent of total on interface. The range is 1 to 10000000. |
burst-size | Maximum burst size (kilobytes of data in queue). The range is 1 to 65535. |
The router does not simulate receiving an RSVP RESV message by default.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Use this command to force the router to act like it is generating RSVP RESV messages from the receiver.
This command is not supported on VIP-based routers.
The following example specifies the use of a Shared Explicit Filter style of reservation and the Controlled Load Service, with token buckets of 100 or 150 kbps and 60 or 65 kbps maximum queue depth:
router(config)# interface ethernet 0 router(config-if)# ip rsvp reservation 224.250.0.2 132.240.1.1 UDP 20 30 132.240.4.1 Et1 se load 100 60 router(config-if)# ip rsvp reservation 224.250.0.2 132.240.2.1 TCP 20 30 132.240.4.1 Et1 se load 150 65
The following example specifies the use of a Wild Card Filter style of reservation and the Guaranteed Bit Rate Service, with token buckets of 300 or 350 kbps and 60 or 65 kbps maximum queue depth:
router(config)# interface ethernet 0 router(config-if)# ip rsvp reservation 224.250.0.3 0.0.0.0 UDP 20 0 132.240.4.1 Et1 wf rate 300 60 router(config-if)# ip rsvp reservation 224.250.0.3 0.0.0.0 UDP 20 0 132.240.4.1 Et1 wf rate 350 65
Note that the Wild Card Filter does not admit the specification of the sender; it accepts all senders. This action is denoted by setting the source address and port to zero. If, in any filter style, the destination port is specified to be zero, RSVP does not permit the source port to be anything else; it understands that such protocols do not use ports or that the specification applies to all ports.
You can use the master indexes or search online to find documentation of related commands.
fair-queue
ip rsvp bandwidth
ip rsvp neighbors
ip rsvp sender
ip rsvp udp-multicast
random-detect
show ip rsvp installed
show ip rsvp interface
show ip rsvp neighbor
show ip rsvp reservation
show ip rsvp sender
To enable a router to generate an RSVP PATH message, use the ip rsvp sender interface configuration command. To disable this feature, use the no form of the command.
ip rsvp sender session-ip-address sender-ip-address {tcp | udp | ip-protocol} session-dport
session-ip-address | For unicast sessions, this is the address of the intended receiver; for multicast sessions, it is the IP multicast address of the session. |
sender-ip-address | The IP address of the sender. |
tcp | udp | ip-protocol | TCP, UDP, or IP protocol in the range 0 to 255. |
session-dport sender-sport | Session-dport is the destination port. Sender-sport is the source port. Port numbers are specified in all cases, as the use of 16-bit ports following the IP header is not limited to UDP or TCP. If destination is zero, source must be zero, and the implication is that ports are not checked. If destination is nonzero, source must be nonzero. |
previous-hop-ip-address | Address of the sender or the router closest to the sender. |
previous-hop-interface | Address of the previous hop interface or subinterface. Interface type can be ethernet, loopback, null, or serial. |
bandwidth | Average bit rate (kbps) to reserve up to 75 percent of total on interface. The range is 1 to 10000000. |
burst-size | Maximum burst size (kilobytes of data in queue). The range is 1 to 65535. |
The router does not simulate RSVP PATH message generation by default.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Use this command to force the router to act like it is receiving RSVP PATH messages from the sender.
This command is not supported on VIP-based routers.
The following example sets up the router to act like it is receiving RSVP PATH messages using UDP over the loopback 1 interface:
router(config)# interface ethernet 0 router(config-if)# ip rsvp sender 224.250.0.1 132.240.2.1 udp 20 30 132.240.2.1 loopback 1 50 5 router(config-if)# ip rsvp sender 224.250.0.2 132.240.2.1 udp 20 30 132.240.2.1 loopback 1 50 5 router(config-if)# ip rsvp sender 224.250.0.2 132.240.2.28 udp 20 30 132.240.2.28 loopback 1 50 5
You can use the master indexes or search online to find documentation of related commands.
fair-queue
ip rsvp bandwidth
ip rsvp neighbors
ip rsvp reservation
ip rsvp udp-multicast
random-detect
show ip rsvp installed
show ip rsvp interface
show ip rsvp neighbor
show ip rsvp reservation
show ip rsvp sender
To instruct the router to generate UDP-encapsulated RSVP multicasts whenever it generates an IP-encapsulated multicast packet, use the ip rsvp udp-multicast interface configuration command. To disable this feature, use the no form of the command.
ip rsvp udp-multicast [multicast-address]
multicast-address | (Optional) Host name or UDP multicast address of router. |
The generation of UDP multicasts is disabled. If a system sends a UDP-encapsulated RSVP message to the router, the router begins using UDP for contact with the neighboring system. The router uses multicast address 224.0.0.14 and starts sending to UDP port 1699. If the command is entered without specifying a multicast address, the router uses the same multicast address.
Interface configuration
This command first appeared in Cisco IOS Release 11.2.
Use this command to instruct a router to generate UDP-encapsulated RSVP multicasts whenever it generates an IP-encapsulated multicast packet. Some hosts require this trigger from the router.
The following example reserves up to 7500 kbps on Ethernet interface 2, with up to 1 Mbps per flow. The router is configured to use UDP encapsulation with the multicast address 224.0.0.14.
router(config)# interface ethernet 2 router(config-if)# ip rsvp bandwidth 7500 1000 router(config-if)# ip rsvp udp-multicast 224.0.0.14
You can use the master indexes or search online to find documentation of related commands.
ip rsvp bandwidth
ip rsvp neighbors
ip rsvp reservation
ip rsvp sender
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
list-number | Priority list number assigned to the interface. Any number from 1 to 16. |
This command is disabled by default.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
Only one list can be assigned per interface. Priority output queueing provides a mechanism to prioritize packets transmitted on an interface.
Use the show queueing priority and show interface commands to display the current status of the output queues.
The following example causes packets for transmission on serial interface 0 to be classified by priority list 1:
router(config)# interface serial 0
router(config-if)# priority-group 1
You can use the master indexes or search online to find documentation of related commands.
priority-list default
priority-list interface
priority-list protocol
priority-list queue-limit
show interfaces
show queue
show queueing
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}
list-number | Any number from 1 to 16 that identifies the priority list. |
high | medium | normal | low | Priority queue level. |
This command is not enabled by default.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
When you use multiple rules, remember that the system reads the priority settings in order of appearance. When classifying a packet, the system searches the list of rules specified by priority-list commands for a matching protocol or interface type. When a match is found, the system assigns the packet to the appropriate queue. The system searches the list in the order it is specified, and the first matching rule terminates the search.
router(config)# priority-list 1 default low
You can use the master indexes or search online to find documentation of related commands.
priority-group
priority-list interface
priority-list protocol
priority-list queue-limit
show queue
show queueing
list-number | Arbitrary integer from 1 to 16 that identifies the priority list selected by the user. |
interface-type | The name of the interface. |
interface-number | The number of the interface. |
high | medium | normal | low | Priority queue level. |
No queueing priorities are established by default.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
When you use multiple rules, remember that the system reads the priority settings in order of appearance. When classifying a packet, the system searches the list of rules specified by priority-list commands for a matching protocol or interface type. When a match is found, the system assigns the packet to the appropriate queue. The system searches the list in the order it is specified, and the first matching rule terminates the search.
The following example assigns a list entering on serial interface 0 to a medium priority queue level:
router(config)# interface serial 0 router(config-if)# priority-list 3 interface serial 0 medium
You can use the master indexes or search online to find documentation of related commands.
priority-group
priority-list default
priority-list protocol
priority-list queue-limit
show queue
show queueing
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. See Table 5. |
No queueing priorities are established.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
When you use multiple rules for a single protocol, remember that the system reads the priority settings in order of appearance. When classifying a packet, the system searches the list of rules specified by priority-list commands for a matching protocol type. When a match is found, the system assigns the packet to the appropriate queue. The system searches the list in the order it is specified, and the first matching rule terminates the search.
The decnet_router-l1 keyword refers to the multicast address for all level 1 routers, which are intra-area routers, and the decnet_router-l2 keyword refers to all level 2 routers, which are interarea routers.
The dlsw, rsrb, and stun keywords refer only to direct encapsulation.
Use Table 5, Table 6, and Table 7 to configure the queueing priorities for your system.
| Option | Description |
|---|---|
fragments | Assigns the priority level defined to fragmented IP packets (for use with the IP protocol only). More specifically, this command matches IP packets whose fragment offset field is nonzero. The initial fragment of a fragmented IP packet has a fragment offset of zero, so such packets are not matched by this command. Note Packets with a nonzero fragment offset do not contain TCP or UDP headers, so other instances of this command that use the tcp or udp keyword will always fail to match such packets. |
gt byte-count | Specifies a greater-than count. The priority level assigned goes into effect when a packet size exceeds the value entered for the argument byte-count. Note The size of the packet must also include additional bytes because of MAC encapsulation on the outgoing interface. |
list list-number | Assigns traffic priorities according to a specified list when used with AppleTalk, bridging, IP, IPX, VINES, or XNS. The argument list-number is the access list number as specified by the access-list global configuration command for the specified protocol-name. For example, if the protocol is AppleTalk, list-number should be a valid AppleTalk access list number. |
lt byte-count | Specifies a less-than count. The priority level assigned goes into effect when a packet size is less than the value entered for the argument byte-count. Note The size of the packet must also include additional bytes because of MAC encapsulation on the outgoing interface. |
tcp port | Assigns the priority level defined to TCP segments originating from or destined to a specified port (for use with the IP protocol only). Table 6 lists common TCP services and their port numbers. |
udp port | Assigns the priority level defined to UDP packets originating from or destined to a specified port (for use with the IP protocol only). Table 7 lists common UDP services and their port numbers. |
| Service | Port |
|---|---|
FTP data | 20 |
FTP | 21 |
SMTP | 25 |
Telnet | 23 |
| Service | Port |
|---|---|
DNS | 53 |
NFS | 2049 |
RPC | 111 |
SNMP | 161 |
TFTP | 69 |
The following example assigns 1 as the arbitrary priority list number, specifies DECnet as the protocol type, and assigns a high-priority level to the DECnet packets transmitted on this interface:
router(config)# priority-list 1 protocol decnet high
The following example assigns a medium-priority level to every DECnet packet with a size greater than 200 bytes:
router(config)# priority-list 2 protocol decnet medium gt 200
The following example assigns a medium-priority level to every DECnet packet with a size less than 200 bytes:
router(config)# priority-list 4 protocol decnet medium lt 200
The following example assigns a high-priority level to traffic that matches IP access list 10:
router(config)# priority-list 1 protocol ip high list 10
The following example assigns a medium-priority level to Telnet packets:
router(config)# priority-list 4 protocol ip medium tcp 23
The following example assigns a medium-priority level to UDP Domain Name Service packets:
router(config)# priority-list 4 protocol ip medium udp 53
The following example assigns a high-priority level to traffic that matches Ethernet type code access list 201:
router(config)# priority-list 1 protocol bridge high list 201
The following example assigns a high-priority level to DLSw+ traffic with TCP encapsulation:
router(config)# priority-list 1 protocol ip high tcp 2065
The following example assigns a high-priority level to DLSw+ traffic with direct encapsulation:
router(config)# priority-list 1 protocol dlsw high
You can use the master indexes or search online to find documentation of related commands.
priority-group
priority-list default
priority-list interface
priority-list queue-limit
show queue
show queueing
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]]]]
list-number | Any number from 1 to 16 that identifies the priority list. |
high-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. For default values for these arguments, see Table 8. |
This command is not enabled by default
The default queue limit arguments are listed in Table 8.
| Priority Queue Argument | Packet Limits |
|---|---|
high-limit | 20 |
medium-limit | 40 |
normal-limit | 60 |
low-limit | 80 |
Global configuration
This command first appeared in Cisco IOS Release 10.0.
If a priority queue overflows, excess packets are discarded and quench messages can be sent, if appropriate, for the protocol.
The following example sets the maximum packets in the priority queue to 10:
router(config)# priority-list 2 queue-limit 10 40 60 80
You can use the master indexes or search online to find documentation of related commands.
priority-group
priority-list default
priority-list interface
priority-list protocol
show queue
show queueing
To assign a priority queue for those packets that do not match any other rule in the queue list, use the queue-list default global configuration command. To restore the default value, use the no form of this command.
queue-list list-number default queue-number
list-number | Number of the queue list. Any number from 1 to 16. |
queue-number | Number of the queue. Any number from 1 to 16. The default number of the queue list is queue number 1. |
This command is disabled by default.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
When you use multiple rules, remember that the system reads the queue-list commands in order of appearance. When classifying a packet, the system searches the list of rules specified by queue-list commands for a matching protocol or interface type. When a match is found, the system assigns the packet to the appropriate queue. The system searches the list in the order it is specified, and the first matching rule terminates the search.
Queue number 0 is a system queue. It is emptied before any of the other queues are processed. The system enqueues high-priority packets, such as keepalives, to this queue.
Use the show interfaces command to display the current status of the output queues.
In the following example, the default queue for list 10 is set to queue number 2:
router(config)# queue-list 10 default 2
You can use the master indexes or search online to find documentation of related commands.
custom-queue-list
queue-list interface
queue-list protocol
queue-list queue byte-count
queue-list queue limit
show queue
show queueing
list-number | Number of the queue list. Any number from 1 to 16. |
interface-type | Name of the interface. |
interface-number | Number of the interface. |
queue-number | Number of the queue. Any number from 1 to 16. |
No queueing priorities are established.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
When you use multiple rules, remember that the system reads the queue-list commands in order of appearance. When classifying a packet, the system searches the list of rules specified by queue-list commands for a matching protocol or interface type. When a match is found, the system assigns the packet to the appropriate queue. The list is searched in the order it is specified, and the first matching rule terminates the search.
In the following example, queue list 4 establishes queueing priorities for packets entering on interface tunnel 3. The queue number assigned is 10.
router(config)# queue-list 4 interface tunnel 3 10
You can use the master indexes or search online to find documentation of related commands.
custom-queue-list
queue-list default
queue-list protocol
queue-list queue byte-count
queue-list queue limit
show queue
show queueing
list-number | Number of the queue list. Any number from 1 to 16. |
protocol-name | Required argument that specifies the protocol type: aarp, apollo, appletalk, arp, bridge (transparent), clns, clns_es, clns_is, cmns, compressedtcp, decnet, decnet_node, decnet_routerl1, decnet_routerl2, dlsw, ip, ipx, pad, rsrb, stun, vines, xns, and x25. |
queue-number | Number of the queue. Any number from 1 to 16. |
queue-keyword keyword-value | Possible keywords are gt, list, lt, tcp, and udp. See Table 5. |
No queueing priorities are established.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
When you use multiple rules, remember that the system reads the queue-list commands in order of appearance. When classifying a packet, the system searches the list of rules specified by queue-list commands for a matching protocol or interface type. When a match is found, the packet is assigned to the appropriate queue. The list is searched in the order it is specified, and the first matching rule terminates the search.
The decnet_router-l1 keyword refers to the multicast address for all level 1 routers, which are intra-area routers, and the decnet_router-l2 keyword refers to all level 2 routers, which are interarea routers.
The dlsw, rsrb, and stun keywords refer only to direct encapsulation.
Use Table 5, Table 6, and Table 7 from the priority-list protocol command to configure the queueing priorities for your system.
The following example assigns 1 as the custom queue list, specifies DECnet as the protocol type, and assigns 3 as a queue number to the packets transmitted on this interface:
router(config)# queue-list 1 protocol decnet 3
The following example assigns DECnet packets with a size greater than 200 bytes to queue number 2:
router(config)# queue-list 2 protocol decnet 2 gt 200
The following example assigns DECnet packets with a size less than 200 bytes to queue number 2:
router(config)# queue-list 4 protocol decnet 2 lt 200
The following example assigns traffic that matches IP access list 10 to queue number 1:
router(config)# queue-list 1 protocol ip 1 list 10
The following example assigns Telnet packets to queue number 2:
router(config)# queue-list 4 protocol ip 2 tcp 23
The following example assigns UDP Domain Name Service packets to queue number 2:
router(config)# queue-list 4 protocol ip 2 udp 53
The following example assigns traffic that matches Ethernet type code access list 201 to queue number 1:
router(config)# queue-list 1 protocol bridge 1 list 201
You can use the master indexes or search online to find documentation of related commands.
custom-queue-list
queue-list default
queue-list queue byte-count
queue-list queue limit
show queue
show queueing
To specify how many bytes the system allows to be delivered from a given queue during a particular cycle, use the queue-list queue byte-count global configuration command. To return the byte count to the default value, use the no form of the command.
queue-list list-number queue queue-number byte-count byte-count-number
list-number | Number of the queue list. Any number from 1 to 16. |
queue-number | Number of the queue. Any number from 1 to 16. |
byte-count-number | The lower boundary on how many bytes the system allows to be delivered from a given queue during a particular cycle. The default byte count is 1500 bytes. |
This command is not enabled by default.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
In the following example, queue list 9 establishes the byte count as 1400 for queue number 10:
router(config)# queue-list 9 queue 10 byte-count 1400
You can use the master indexes or search online to find documentation of related commands.
custom-queue-list
queue-list default
queue-list interface
queue-list protocol
queue-list queue byte-count
queue-list queue limit
show queue
show queueing
list-number | Number of the queue list. Any number from 1 to 16. |
queue-number | Number of the queue. Any number from 1 to 16. |
limit-number | Maximum number of packets that can be enqueued at any time. The range is 0 to 32767 queue entries. A value of 0 means that the queue can be of unlimited size. The default queue is 20 entries. |
This command is not enabled by default.
Global configuration
This command first appeared in Cisco IOS Release 10.0.
In the following example, the queue length of queue 10 is increased to 40:
router(config)# queue-list 5 queue 10 limit 40
You can use the master indexes or search online to find documentation of related commands.
custom-queue-list
queue-list default
queue-list interface
queue-list protocol
queue-list queue byte-count
show queue
show queueing
Posted: Thu Jun 3 14:29:25 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.