Table Of Contents
random-detect exponential-weighting-constant
random-detect
To enable WRED or Distributed WRED (DWRED), use the random-detect interface configuration command. To disable WRED or DWRED, use the no form of this command.
random-detect [weighting]
no random-detect
Syntax Description
Defaults
WRED and DWRED are disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
WRED is a congestion avoidance mechanism that slows traffic by randomly dropping packets when there is congestion. WRED is only useful with protocols like TCP that respond to dropped packets by decreasing the transmission rate.
The router automatically determines parameters to use in the WRED calculations. To change these parameters, use the random-detect precedence command.
The WRED feature is supported on these Cisco router platforms:
•
Cisco 1600 series
•
•
•
•
•
The DWRED feature is only supported on Cisco 7000 series routers with an RSP7000 card and Cisco 7500 series routers with a VIP2-40 or greater interface processor. A VIP2-50 interface processor is strongly recommended when the aggregate line rate of the port adapters on the VIP is greater than DS3. A VIP2-50 interface processor is required for OC-3 rates. To use DWRED, distributed Cisco Express Forwarding (DCEF) switching must first be enabled on the interface. For more information on DCEF, refer to the Cisco IOS Switching Services Configuration Guide and the Cisco IOS Switching Services Command Reference.
Examples
The following example configures WRED on the HSSI 0/0/0 interface:
router(config)# interface Hssi0/0/0router(config-if)# random-detectRelated Commands
random-detect exponential-weighting-constant
To configure the Weighted Random Early Detection (WRED) and Distributed WRED (DWRED) exponential weight factor for the average queue size calculation, use the random-detect exponential-weighting-constant interface configuration command. To return the value to the default, use the no form of this command.
random-detect exponential-weighting-constant exponent
no random-detect exponential-weighting-constant
Syntax Description
exponent
Exponent from 1 to 16 used in the average queue size calculation. The default exponential weight factor is 9.
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
WRED is a congestion avoidance mechanism that slows traffic by randomly dropping packets when there is congestion. WRED is only useful with protocols like TCP, which respond to dropped packets by decreasing the transmission rate.
Use this command to change the exponent used in the average queue size calculation for the WRED and DWRED services.
Note
The WRED feature is supported on these Cisco router platforms:
•
•
•
•
•
•
The DWRED feature is only supported on Cisco 7000 series routers with an RSP7000 card and Cisco 7500 series routers with a VIP2-40 or greater interface processor. A VIP2-50 interface processor is strongly recommended when the aggregate line rate of the port adapters on the VIP is greater than DS3. A VIP2-50 interface processor is required for OC-3 rates. To use DWRED, Distributed Cisco Express Forwarding (DCEF) switching must first be enabled on the interface. For more information on DCEF, refer to the Cisco IOS Switching Services Configuration Guide and the Cisco IOS Switching Services Command Reference.
Examples
The following example configures WRED on an interface with a weight factor of 10:
router(config)# interface Hssi0/0/0router(config-if)# description 45Mbps to R1router(config-if)# ip address 200.200.14.250 255.255.255.252router(config-if)# random-detectrouter(config-if)# random-detect exponential-weighting-constant 10Related Commands
random-detect precedence
To configure Weighted Random Early Detection (WRED) and Distributed WRED (DWRED) parameters for a particular IP precedence, use the random-detect precedence interface configuration command. To return the values to the default for the precedence, use the no form of this command.
random-detect precedence precedence min-threshold max-threshold mark-prob-denominator
no random-detect precedence precedence min-threshold max-threshold
mark-prob-denominatorSyntax Description
precedence
IP precedence number. The value range is 0 to 7 and RSVP. For Cisco 7000 series routers with an RSP7000 interface processor and Cisco 7500 series routers with a VIP2-40 interface processor (VIP2-50 interface processor strongly recommended), the precedence value ranges from 0 to 7 only; see Table 379.
min-threshold
Minimum threshold in number of packets. The value range of this argument is 1 to 4096. When the average queue length reaches the minimum threshold, WRED drops all packets with the specified IP precedence.
max-threshold
Maximum threshold in number of packets. The value range of this argument is the value of the min-threshold argument to 4096. When the average queue length exceeds the maximum threshold, WRED drops all packets with the specified IP precedence.
mark-prob-denominator
Denominator for the fraction of packets dropped when the average queue depth is at the maximum threshold. For example, if the denominator is 512, one out of every 512 packets is dropped when the average queue is at the maximum threshold. The value range is 1 to 65536. The default is 10; one out of every ten packets is dropped at the maximum threshold.
Defaults
For all precedences, the mark-prob-denominator is 10, and the max-threshold is based on the output buffering capacity and the transmission speed for the interface.
The default min-threshold depends on the precedence. The min-threshold for IP precedence 0 corresponds to half of the max-threshold. The values for the remaining precedences fall between half the max-threshold and the max-threshold at evenly spaced intervals.
Table 379 lists the default minimum threshold value for each IP precedence.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you configure the random-detect command on an interface, packets are given preferential treatment based on the IP precedence of the packet. Use the random-detect precedence command to adjust the treatment for different IP precedences.
If you want WRED to ignore the precedence when determining which packets to drop, enter this command with the same parameters for each precedence. Remember to use reasonable values for the minimum and maximum thresholds.
Note
The WRED feature is supported on these Cisco router platforms:
•
•
•
•
•
•
The DWRED feature is only supported on Cisco 7000 series routers with an RSP7000 card and Cisco 7500 series routers with a VIP2-40 or greater interface processor. A VIP2-50 interface processor is strongly recommended when the aggregate line rate of the port adapters on the VIP is greater than DS3. A VIP2-50 interface processor is required for OC-3 rates. To use DWRED, Distributed Cisco Express Forwarding (DCEF) switching must first be enabled on the interface. For more information on DCEF, refer to the Cisco IOS Switching Services Configuration Guide and the Cisco IOS Switching Services Command Reference.
Examples
The following example enables WRED on the interface and specifies parameters for the different IP precedences:
router(config)# interface Hssi0/0/0router(config-if)# description 45Mbps to R1router(config-if)# ip address 200.200.14.250 255.255.255.252router(config-if)# random-detectrouter(config-if)# random-detect precedence 0 32 256 100router(config-if)# random-detect precedence 1 64 256 100router(config-if)# random-detect precedence 2 96 256 100router(config-if)# random-detect precedence 3 120 256 100router(config-if)# random-detect precedence 4 140 256 100router(config-if)# random-detect precedence 5 170 256 100router(config-if)# random-detect precedence 6 290 256 100router(config-if)# random-detect precedence 7 210 256 100router(config-if)# random-detect precedence rsvp 230 256 100Related Commands
rate-limit
To configure committed access rate (CAR) and Distributed CAR (DCAR) policies, use the rate-limit interface configuration command. To remove the rate limit from the configuration, use the no form of this command.
rate-limit {input | output} [access-group [rate-limit] acl-index] bps burst-normal burst-max conform-action action exceed-action action
no rate-limit {input | output} [access-group [rate-limit] acl-index] bps burst-normal burst-max conform-action action exceed-action action
Syntax Description
Defaults
CAR and DCAR are disabled on the interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command to configure your CAR policy on an interface. To specify multiple policies, enter this command once for each policy.
Distributed CAR is only supported on Cisco 7000 series routers with an RSP7000 or Cisco 7500 series routers with VIP2-40 or greater interface processor. A VIP2-50 interface processor is strongly recommended when the aggregate line rate of the port adapters on the VIP is greater than DS3. A VIP2-50 interface processor is required for OC-3 rates.
CAR and DCAR can only be used with IP traffic. Non-IP traffic is not rate limited.
CAR and DCAR can be configured on an interface or subinterface. However, CAR and DCAR are not supported on the Fast EtherChannel, tunnel, or PRI interfaces, nor on any interface that does not support Cisco Express Forwarding (CEF).
CEF must be enabled on the interface before you configure CAR or DCAR.
Examples
The example illustrated below limits the rate by application:
•
•
•
Notice that two access lists are created to classify the Web and FTP traffic so that they can be handled separately by the CAR feature.
router(config)# interface Hssi0/0/0router(config-if)# description 45Mbps to R2router(config-if)# rate-limit input access-group 101 20000000 24000 32000 conform-action set-prec-transmit 5 exceed-action set-prec-transmit 0router(config-if)# rate-limit input access-group 102 10000000 24000 32000 conform-action set-prec-transmit 5 exceed-action droprouter(config-if)# rate-limit input 8000000 16000 24000 conform-action set-prec-transmit 5 exceed-action droprouter(config-if)# ip address 200.200.14.250 255.255.255.252!router(config-if)# access-list 101 permit tcp any any eq wwwrouter(config-if)# access-list 102 permit tcp any any eq ftpRelated Commands
set ip precedence
To set the precedence value in the IP header, use the set ip precedence route-map configuration command. To leave the precedence value alone, use the no form of this command.
set ip precedence [number | name]
no set ip precedence
Syntax Description
(Optional) A number or name that sets the precedence bits in the IP header. The values for number and the corresponding name are as follows, listed from least to most important:
number name
0 routine
1 priority
2 immediate
3 flash
4 flash-override
5 critical
6 internet
7 network
Defaults
This command is disabled by default.
Command Modes
Route-map configuration
Command History
Usage Guidelines
You can set the precedence using either a number or the corresponding name. Once the IP precedence bits are set, other QoS services such as weighted fair queueing (WFQ) and Weighted Random Early Detection (WRED) then operate on the bit settings.
The network gives priority (or some type of expedited handling) to the marked traffic through the application of WFQ or WRED at points downstream in the network. Typically, you would set IP precedence at the edge of the network (or administrative domain) and have queueing act on it thereafter. WFQ can speed up handling for high precedence traffic at congestion points. WRED ensures high precedence traffic has lower loss rates than other traffic during times of congestion.
The mapping from keywords such as routine and priority to a precedence value is useful only in some instances. That is, the use of the precedence bit is evolving. You can define the meaning of a precedence value by enabling other features that use the value. In the case of Cisco's high-end Internet QoS, IP precedences can be used to establish classes of service that do not necessarily correspond numerically to better or worse handling in the network.
Use the route-map (IP) global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another, or for policy routing. Each route-map command has an associated list of match and set commands. The match commands specify the match criteria—the conditions under which redistribution or policy routing is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution or policy routing actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
The set route-map configuration commands specify the redistribution set actions to be performed when all of a route map's match criteria are met.
Examples
The following example sets the IP precedence to 5 (critical) for packets that pass the route-map match:
router(config)# interface serial 0router(config-if)# ip policy route-map texasrouter(config)# route-map texasrouter(config)# match length 68 128router(config)# set ip precedence 5Related Commands
set ip qos-group
To set a group ID that can be used later to classify packets, use the set ip qos-group route-map configuration command. To remove the group ID, use the no form of this command.
set ip qos-group group-id
no set ip qos-group group-id
Syntax Description
Defaults
This command is disabled by default. No group ID is specified.
Command Modes
Route-map configuration
Command History
Usage Guidelines
This command allows you to set a group ID in the routing table that can be used later to classify packets into QoS groups based on prefix, autonomous system, and community string. These packets can then be rate limited or weighted fair queued based on the QoS group ID.
To display QoS group information, use the show ip cef command.
Examples
The following example sets the QoS group to 1 for all packets that match community 1. These packets are then rate limited based on the QoS group ID.
router# configure terminalrouter(config)# route-map precedence-map permit 10router(config)# match community 1router(config)# set ip qos-group 1router(config)# interface hssi0/0/0router(config-if)# bgp-policy source qos-grouprouter(config-if)# endshow access-lists rate-limit
To display information about rate-limit access lists, use the show access-lists rate-limit EXEC command.
show access-lists rate-limit [acl-index]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show access-lists rate-limit command:
Router# show access-lists rate-limitRate-limit access list 10Rate-limit access list 21Rate-limit access list 32Rate-limit access list 43Rate-limit access list 54Rate-limit access list 65Rate-limit access list 9mask FFRate-limit access list 10mask 0FRate-limit access list 11mask F0Rate-limit access list 1001001.0110.1111Rate-limit access list 10100E0.34B8.D840Rate-limit access list 1991111.1111.1111The following is sample output from the show access-lists rate-limit command when specific rate-limit access lists are specified:
Router# show access-lists rate-limit 1Rate-limit access list 10Router# show access-lists rate-limit 9Rate-limit access list 9mask FFRouter# show access-lists rate-limit 101Rate-limit access list 10100E0.34B8.D840Table 380 describes the fields shown in these displays.
Related Commands
access-list rate-limit
Configures an access list for use with CAR policies.
show access-lists
Displays the contents of current IP and rate-limit access lists.
show interfaces fair-queue
To display information and all statistics about weighted fair queueing for a VIP-based interface, use the show interfaces fair-queue EXEC command.
show interfaces [interface-type interface-number] fair-queue
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show interfaces fair-queue command:
Router# show interfaces fair-queueHssi0/0/0 queue size 0packets output 1417079, drops 2WFQ: aggregate queue limit 54, individual queue limit 27max available buffers 54Class 0: weight 10 limit 27 qsize 0 packets output 1150 drops 0Class 1: weight 20 limit 27 qsize 0 packets output 0 drops 0Class 2: weight 30 limit 27 qsize 0 packets output 775482 drops 1Class 3: weight 40 limit 27 qsize 0 packets output 0 drops 0Table 381 describes the fields and statistics shown in this display.
Related Commands
show interfaces
Displays statistics for all interfaces configured on the router or access server.
show interfaces random-detect
To display information about Weighted Random Early Detection (WRED) for a VIP-based interface, use the show interfaces random-detect EXEC command.
show interfaces [interface-type interface-number] random-detect
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show interfaces random-detect command:
Router# show interfaces random-detectFastEthernet1/0/0 queue size 0packets output 29692, drops 0WRED: queue average 0weight 1/512Precedence 0: 109 min threshold, 218 max threshold, 1/10 mark weight1 packets output, drops: 0 random, 0 thresholdPrecedence 1: 122 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 2: 135 min threshold, 218 max threshold, 1/10 mark weight14845 packets output, drops: 0 random, 0 thresholdPrecedence 3: 148 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 4: 161 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 5: 174 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Precedence 6: 187 min threshold, 218 max threshold, 1/10 mark weight14846 packets output, drops: 0 random, 0 thresholdPrecedence 7: 200 min threshold, 218 max threshold, 1/10 mark weight(no traffic)Table 382 describes the fields shown in this display.
Related Commands
show interfaces rate-limit
To display information about committed access rate (CAR) for an interface, use the show interfaces rate-limit EXEC command.
show interfaces [interface-type interface-number] rate-limit
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show interfaces rate-limit command:
Router# show interfaces fddi2/1/0 rate-limitFddi2/1/0Inputmatches: access-group rate-limit 100params: 800000000 bps, 64000 limit, 80000 extended limitconformed 0 packets, 0 bytes; action: set-prec-continue 1exceeded 0 packets, 0 bytes; action: set-prec-continue 0last packet: 4737508ms ago, current burst: 0 byteslast cleared 01:05:47 ago, conformed 0 bps, exceeded 0 bpsmatches: access-group 101params: 80000000 bps, 56000 limit, 72000 extended limitconformed 0 packets, 0 bytes; action: set-prec-transmit 5exceeded 0 packets, 0 bytes; action: set-prec-transmit 0last packet: 4738036ms ago, current burst: 0 byteslast cleared 01:02:05 ago, conformed 0 bps, exceeded 0 bpsmatches: all trafficparams: 50000000 bps, 48000 limit, 64000 extended limitconformed 0 packets, 0 bytes; action: set-prec-transmit 5exceeded 0 packets, 0 bytes; action: set-prec-transmit 0last packet: 4738036ms ago, current burst: 0 byteslast cleared 01:00:22 ago, conformed 0 bps, exceeded 0 bpsOutputmatches: all trafficparams: 80000000 bps, 64000 limit, 80000 extended limitconformed 0 packets, 0 bytes; action: transmitexceeded 0 packets, 0 bytes; action: droplast packet: 4809528ms ago, current burst: 0 byteslast cleared 00:59:42 ago, conformed 0 bps, exceeded 0 bpsTable 383 describes the fields shown in this display.
Related Commands
show ip rsvp installed
To display RSVP-related installed filters and corresponding bandwidth information, use the show ip rsvp installed EXEC command.
show ip rsvp installed [interface-type interface-number]
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Usage Guidelines
The command displays the current installed RSVP filters and the corresponding bandwidth information for a specified interface or all interfaces.
Examples
The following is sample output from the show ip rsvp installed command:
Router# show ip rsvp installedRSVP:RSVP: Ethernet1: has no installed reservationsRSVP: Serial0:kbps To From Protocol DPort Sport Weight Conversation0 224.250.250.1 132.240.2.28 UDP 20 30 128 270150 224.250.250.1 132.240.2.1 UDP 20 30 128 268100 224.250.250.1 132.240.1.1 UDP 20 30 128 267200 224.250.250.1 132.240.1.25 UDP 20 30 256 265200 224.250.250.2 132.240.1.25 UDP 20 30 128 2710 224.250.250.2 132.240.2.28 UDP 20 30 128 269150 224.250.250.2 132.240.2.1 UDP 20 30 128 266350 224.250.250.3 0.0.0.0 UDP 20 0 128 26Table 384 describes significant fields shown in this display.
show ip rsvp interface
To display RSVP-related interface information, use the show ip rsvp interface EXEC command.
show ip rsvp interface [interface-type interface-number]
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to show the current allocation budget and maximum allocatable bandwidth.
Examples
The following is sample output from the show ip rsvp interface command:
Router# show ip rsvp interfaceinterfac allocate i/f max flow max per/255 UDP IP UDP_IP UDP M/CEt1 0M 7500K 7500K 0 /255 0 0 0 0Se0 0M 1158K 1158K 0 /255 0 0 0 0Se1 30K 1158K 1158K 6 /255 0 1 0 0Table 385 describes significant fields shown in this display.
show ip rsvp neighbor
To display current RSVP neighbors, use the show ip rsvp neighbor EXEC command.
show ip rsvp neighbor [interface-type interface-number]
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to show the current RSVP neighbors and identify if the neighbor is using IP, UDP, or RSVP encapsulation for a specified interface or all interfaces.
Examples
The following is sample output from the show ip rsvp neighbor command:
Router# show ip rsvp neighborInterface Neighbor EncapsulationSe1 132.240.1.49 RSVPTable 386 describes significant fields shown in this display.
show ip rsvp request
To display RSVP-related request information being requested upstream, use the show ip rsvp request EXEC command.
show ip rsvp request [interface-type interface-number]
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to show the RSVP reservations currently being requested upstream for a specified interface or all interfaces. The received reservations may differ from requests because of aggregated or refused reservations.
Examples
The following is sample output from the show ip rsvp request command:
Router# show ip rsvp requestTo From Pro DPort Sport Next Hop I/F Fi Serv132.240.1.49 132.240.4.53 1 0 0 132.240.3.53 Et1 FF LOADTable 387 describes significant fields shown in this display.
show ip rsvp reservation
To display RSVP-related receiver information currently in the database, use the show ip rsvp reservation EXEC command.
show ip rsvp reservation [interface-type interface-number]
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to show the current receiver (RESV) information currently in the database for a specified interface or all interfaces. This information includes reservations aggregated and forwarded from other RSVP routers.
Examples
The following is sample output from the show ip rsvp reservation command:
Router# show ip rsvp reservationTo From Pro DPort Sport Next Hop I/F Fi Serv132.240.1.49 132.240.4.53 1 0 0 132.240.1.49 Se1 FF LOADTable 388 describes significant fields shown in this display.
show ip rsvp sender
To display RSVP PATH-related sender information currently in the database, use the show ip rsvp sender EXEC command.
show ip rsvp sender [interface-type interface-number]
Syntax Description
interface-type
(Optional) The name of the interface.
interface-number
(Optional) The number of the interface.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to show the RSVP sender (PATH) information currently in the database for a specified interface or all interfaces.
Examples
The following is sample output from the show ip rsvp sender command:
Router# show ip rsvp senderTo From Pro DPort Sport Prev Hop I/F132.240.1.49 132.240.4.53 1 0 0 132.240.3.53 Et1132.240.2.51 132.240.5.54 1 0 0 132.240.3.54 Et1Table 389 describes the fields shown in this display.
show queue
To list fair queueing configuration and statistics for a particular interface, use the show queue privileged EXEC command.
show queue interface-type interface-number
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command displays statistics for interfaces configured with the fair queueing strategy.
Examples
The following is sample output from the show queue command. There are two active conversations on the serial 1 interface. Weighted fair queueing ensures that both of these IP data streams, one TCP and other UDP, receive equal bandwidth on the interface while they have messages in the pipeline.
Router# show queue serial1Input queue: 0/75/0 (size/max/drops); Total output drops: 303628Queueing strategy: weighted fairOutput queue: 64/1000/64/303628 (size/max total/threshold/drops)Conversations 2/2/256 (active/max active/max total)Reserved Conversations 0/0 (allocated/max allocated)(depth/weight/discards/tail drops/interleaves) 45/4096/1123/0/0Conversation 244, linktype: ip, length: 50source: 55.1.1.1, destination: 66.1.1.2, id: 0x0000, ttl: 59,TOS: 0 prot: 6, source port 55, destination port 55(depth/weight/discards/tail drops/interleaves) 19/4096/302541/0/0Conversation 185, linktype: ip, length: 118source: 55.1.1.1, destination: 66.1.1.2, id: 0x0000, ttl: 59,TOS: 0 prot: 17, source port 20, destination port 20Table 390 describes the fields shown in this display.
.
show queueing
To list all or selected configured queueing strategies, use the show queueing privileged EXEC command.
show queueing [custom | fair | priority | red]
Syntax Description
Defaults
If no keyword is entered, this command shows the configuration of all interfaces.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show queueing custom command:
Router# show queueing customCurrent custom queue configuration:List Queue Args3 10 default3 3 interface Tunnel33 3 protocol ip3 3 byte-count 444 limit 3The following is sample output from the show queueing command. There are two active conversations in the serial interface 0. Weighted fair queueing ensures that both of these IP data streams—both using TCP—receive equal bandwidth on the interface while they have messages in the pipeline, even though there is more FTP data in the queue than RCP data.
Router# show queueingCurrent fair queue configuration:Interface Discard Dynamic Reservedthreshold queue count queue countSerial0 64 256 0Serial1 64 256 0Serial2 64 256 0Serial3 64 256 0Current priority queue configuration:List Queue Args1 high protocol cdp2 medium interface Ethernet1Current custom queue configuration:Current RED queue configuration:Interface: Ethernet3 Exp-weight-constant: 9Class Min-th Max-th Mark-prob0 20 40 1/101 22 40 1/102 24 40 1/103 26 40 1/104 28 40 1/105 31 40 1/106 33 40 1/107 35 40 1/10rsvp 37 40 1/10Related Commands
show tech-support rsvp
To generate a report of all RSVP-related information, use the show tech-support rsvp command.
show tech-support rsvp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command is not required for normal use of the operating system. This command is useful when contacting technical support personnel with questions regarding RSVP. The show tech-support rsvp command generates a series of reports that can be useful to technical support personnel attempting to solve problems.
Any issues or caveats that apply to the show tech-support command also apply to this command. For example, the enable password, if configured, is not displayed in the output of the show running-config command.
The show tech-support rsvp command is equivalent to issuing the following commands:
show ip rsvp installed
show ip rsvp interface
show ip rsvp neighbor
show ip rsvp request
show ip rsvp reservation
show ip rsvp sender
show running-config
show versionRefer to the displays and descriptions for these commands for information about the show tech-support rsvp command display.
show traffic-shape
To display the current traffic-shaping configuration, use the show traffic-shape EXEC command.
show traffic-shape [interface-type]
Syntax Description
interface-type
(Optional) The name of the interface. If no interface is specified, traffic shaping details for all configured interfaces are shown.
Command Modes
EXEC
Command History
Usage Guidelines
You must have first enabled traffic shaping using the traffic-shape rate, traffic-shape group, or frame-relay traffic-shaping command to display traffic-shaping information.
Examples
The following is sample output from the show traffic-shape command:
Router# show traffic-shapeaccess Target Byte Sustain Excess Interval Increment AdaptI/F list Rate Limit bits/int bits/int (ms) (bytes) ActiveEt0 101 1000000 23437 125000 125000 63 7813 -Et1 5000000 87889 625000 625000 16 9766 -Table 391 describes the fields shown in this display.
Related Commands
show traffic-shape statistics
To display the current traffic-shaping statistics, use the show traffic-shape statistics EXEC command.
show traffic-shape statistics [interface-type]
Syntax Description
interface-type
(Optional) The name of the interface. If no interface is specified, traffic shaping statistics for all configured interfaces are shown.
Command Modes
EXEC
Command History
Usage Guidelines
You must have first enabled traffic shaping using the traffic-shape rate, traffic-shape group, or frame-relay traffic-shaping command to display traffic-shaping information.
Examples
The following is sample output from the show traffic-shape statistics command:
Router# show traffic-shape statisticsAccess Queue Packets Bytes Packets Bytes ShapingI/F List Depth Delayed Delayed ActiveEt0 101 0 2 180 0 0 noEt1 0 0 0 0 0 noTable 392 describes the fields shown in this display.
Related Commands
traffic-shape adaptive
To configure a Frame Relay subinterface to estimate the available bandwidth when backward explicit congestion notifications (BECNs) are received, use the traffic-shape adaptive interface configuration command. To stop adapting to congestion signals, use the no form of this command.
traffic-shape adaptive bit-rate
no traffic-shape adaptive
Syntax Description
bit-rate
Lowest bit rate that traffic is shaped to, in bits per second. The default bit rate value is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command specifies the boundaries in which traffic will be shaped when BECNs are received. You must enable traffic shaping on the interface with the traffic-shape rate or traffic-shape group command before you can use the traffic-shape adaptive command.
The bit rate specified for the traffic-shape rate command is the upper limit, and the bit rate specified for the traffic-shape adaptive command is the lower limit to which traffic is shaped when BECNs are received on the interface. The rate actually shaped to will be between these two bit rates.
You should configure this command and the traffic-shape fecn-adapt command on both ends of the connection to ensure adaptive traffic shaping over the connection, even when traffic is flowing primarily in one direction. The traffic-shape fecn-adapt command configures the router to reflect forward explicit congestion notification (FECN) signals as BECNs.
Examples
The following example configures traffic shaping on serial interface 0.1 with an upper limit of 128 kbps and a lower limit of 64 kbps. This configuration allows the link to run from 64 to 128 kbps, depending on the congestion level.
router(config)# interface serial 0router(config-if)# encapsulation-frame-relayrouter(config)# interface serial 0.1router(config-if)# traffic-shape rate 128000router(config-if)# traffic-shape adaptive 64000router(config-if)# traffic-shape fecn-adaptRelated Commands
traffic-shape fecn-adapt
To reply to messages with the forward explicit congestion notification (FECN) bit, (which are set with TEST RESPONSE messages with the BECN bit set), use the traffic-shape fecn-adapt interface configuration command. To stop backward explicit congestion notification (BECN) message generation, use the no form of this command.
traffic-shape fecn-adapt
no traffic-shape fecn-adapt
Syntax Description
This command has no arguments or keywords.
Defaults
Traffic shaping is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Enable traffic shaping on the interface with the traffic-shape rate or traffic-shape group command. FECN is available only when traffic shaping is configured.
Use this command to reflect FECN bits as BECN bits to notify the other data terminal equipment (DTE) that it is transmitting too fast. Use the traffic-shape adaptive command to configure the router to adapt its transmission rate when it receives BECNs.
You should configure this command and the traffic-shape adaptive command on both ends of the connection to ensure adaptive traffic shaping over the connection, even when traffic is flowing primarily in one direction.
Examples
The following example configures traffic shaping on serial interface 0.1 with an upper limit of 128 kbps and a lower limit of 64 kbps. This configuration allows the link to run from 64 to 128 kbps, depending on the congestion level. The router reflects FECNs as BECNs.
router(config)# interface serial 0router(config-if)# encapsulation-frame-relayrouter(config)# interface serial 0.1router(config-if)# traffic-shape rate 128000router(config-if)# traffic-shape adaptive 64000router(config-if)# traffic-shape fecn-adaptRelated Commands
traffic-shape group
To enable traffic shaping based on a specific access list for outbound traffic on an interface, use the traffic-shape group interface configuration command. To disable traffic shaping on the interface for the access list, use the no form of this command.
traffic-shape group access-list bit-rate [burst-size [excess-burst-size]]
no traffic-shape group access-list
Syntax Description
Defaults
This command is not on by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
Traffic shaping is not supported with optimum, distributed, or flow switching. If you enable this command, all interfaces will revert to fast switching.
Traffic shaping uses queues to limit surges that can congest a network. Data is buffered and then sent into the network in regulated amounts to ensure that traffic will fit within the promised traffic envelope for the particular connection.
The traffic-shape group command allows you to specify one or more previously defined access list to shape traffic to on the interface. You must specify one traffic-shape group command for each access list on the interface.
The traffic-shape group command supports both standard and extended access lists.
Use traffic shaping if you have a network with differing access rates or if you are offering a subrate service. You can configure the values according to your contract with your service provider or the service levels you intend to maintain.
An interval is calculated as follows:
•
•
Traffic shaping is supported on all media and encapsulation types on the router. To perform traffic shaping on Frame Relay virtual circuits, you can also use the frame-relay traffic-shaping command. For more information on Frame Relay traffic shaping, refer to the "Configuring Frame Relay" chapter in the Wide-Area Network Configuration Guide.
If traffic shaping is performed on a Frame Relay network with the traffic-shape rate command, you can also use the traffic-shape adaptive command to specify the minimum bit rate the traffic is shaped to.
Examples
The following example enables traffic that matches access list 101 to be shaped to a certain rate and traffic matching access list 102 to be shaped to another rate on the interface:
router(config)# interface serial 1router(config-if)# traffic-shape group 101 128000 16000 8000router(config-if)# traffic-shape group 102 130000 10000 1000Related Commands
traffic-shape rate
To enable traffic shaping for outbound traffic on an interface, use the traffic-shape rate interface configuration command. To disable traffic shaping on the interface, use the no form of this command.
traffic-shape rate bit-rate [burst-size [excess-burst-size]]
no traffic-shape rate
Syntax Description
Defaults
Traffic shaping is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Traffic shaping is not supported with optimum, distributed, or flow switching. If you enable this command, all interfaces will revert to fast switching.
Traffic shaping uses queues to limit surges that can congest a network. Data is buffered and then sent into the network in regulated amounts to ensure that traffic will fit within the promised traffic envelope for the particular connection.
Use traffic shaping if you have a network with differing access rates or if you are offering a subrate service. You can configure the values according to your contract with your service provider or the service levels you intend to maintain.
An interval is calculated as follows:
•
•
Traffic shaping is supported on all media and encapsulation types on the router. To perform traffic shaping on Frame Relay virtual circuits, you can also use the frame-relay traffic-shaping command. For more information on Frame Relay traffic shaping, refer to the "Configuring Frame Relay" chapter in the Wide-Area Network Configuration Guide.
If traffic shaping is performed on a Frame Relay network with the traffic-shape rate command, you can also use the traffic-shape adaptive command to specify the minimum bit rate to which the traffic is shaped.
Examples
The following example enables traffic shaping on serial interface 0 using the bandwidth required by the service provider:
router(config)# interface serial 0router(config-if)# traffic-shape rate 128000 16000 8000Related Commands
