Table Of Contents
Control Plane DSCP Support for RSVP
Prerequisites for Control Plane DSCP Support for RSVP
Restrictions for Control Plane DSCP Support for RSVP
Information About Control Plane DSCP Support for RSVP
Feature Overview of Control Plane DSCP Support for RSVP
Benefits of Control Plane DSCP Support for RSVP
How to Configure Control Plane DSCP Support for RSVP
Configuration Examples for Control Plane DSCP Support for RSVP
Verifying Control Plane DSCP Support for RSVP: Example
Control Plane DSCP Support for RSVP
First Published: June 7, 2001Last Updated: February 19, 2007The Control Plane DSCP Support for RSVP feature lets you prioritize Resource Reservation Protocol (RSVP) messages to improve delivery by decreasing the likelihood of high priority messages being dropped.
History for the Control Plane DSCP Support for RSVP Feature
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Control Plane DSCP Support for RSVP
•
Restrictions for Control Plane DSCP Support for RSVP
•
Information About Control Plane DSCP Support for RSVP
•
How to Configure Control Plane DSCP Support for RSVP
•
Configuration Examples for Control Plane DSCP Support for RSVP
Prerequisites for Control Plane DSCP Support for RSVP
The network must support RSVP before you can enable the Control Plane DSCP Support for RSVP feature.
Restrictions for Control Plane DSCP Support for RSVP
You can configure the Control Plane DSCP Support for RSVP feature on interfaces and subinterfaces only. This feature affects all RSVP messages that are sent out the interface or that are on any logical circuit of the interface, including subinterfaces, permanent virtual circuits (PVCs), and switched virtual circuits (SVCs).
Information About Control Plane DSCP Support for RSVP
To use the Control Plane DSCP Support for RSVP feature, you need to understand the following concepts:
•
Feature Overview of Control Plane DSCP Support for RSVP
•
Benefits of Control Plane DSCP Support for RSVP
Feature Overview of Control Plane DSCP Support for RSVP
Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an equal chance of being dropped.
Before traffic can be handled according to its unique requirements, it must be identified or labeled (that is, classified). There are numerous classification techniques for doing this. These include Layer 3 schemes such as IP precedence or the differentiated services code point (DSCP), Layer 2 schemes such as 802.1P, and implicit characteristics of the data itself, such as the traffic type using the Real-Time Transport Protocol (RTP) and a defined port range.
The Control Plane DSCP Support for RSVP feature allows you to set the priority value in the type of service (ToS) byte/differentiated services (DiffServ) field in the Internet Protocol (IP) header for RSVP messages. The IP header functions with resource providers such as weighted fair queueing (WFQ), so that voice frames have priority over data fragments and data frames. When packets arrive in a router's output queue, the voice packets are placed ahead of the data frames.
Figure 1 shows a path message originating from a sender with a DSCP value of 0 (the default) that is changed to 5 to give the message a higher priority and a reservation (resv) message originating from a receiver with a DSCP of 3.
Figure 1 Control Plane DSCP Support for RSVP
Raising the DSCP value reduces the possibility of packets being dropped, thereby improving call setup time in VoIP environments.
Benefits of Control Plane DSCP Support for RSVP
Faster Call Setup Time
The Control Plane DSCP Support for RSVP feature allows you to set the priority for RSVP messages. In a DiffServ QoS environment, higher priority packets get serviced before lower priority packets, thereby improving the call setup time for RSVP sessions.
Improved Message Delivery
During periods of congestion, routers drop lower priority traffic before they drop higher priority traffic. Since RSVP messages can now be marked with higher priority, the likelihood of these messages being dropped is significantly reduced.
Faster Recovery After Failure Conditions
When heavy congestion occurs, many packets are dropped. Network resources attempt to retransmit almost instantaneously resulting in further congestion. This leads to a considerable reduction in throughput.
Previously, RSVP messages were marked best effort and subject to being dropped by congestion avoidance mechanisms such as weighted random early detection (WRED). However, with the Control Plane DSCP Support for RSVP feature, RSVP messages are likely to be dropped later, if at all, thereby providing faster recovery of RSVP reservations.
How to Configure Control Plane DSCP Support for RSVP
This section contains the following procedures:
•
Enabling RSVP on an Interface (required)
•
Specifying the DSCP (required)
•
Verifying the Configuration (optional)
Enabling RSVP on an Interface
Perform this task to enable RSVP on an interface.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number [name-tag]
4.
ip rsvp bandwidth [interface-kbps] [single-flow-kbps]
5.
end
DETAILED STEPS
Specifying the DSCP
Perform this task to specify the DSCP.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number [name-tag]
4.
ip rsvp signalling dscp value
5.
end
DETAILED STEPS
Verifying the Configuration
Perform the following task to verify that the Control Plane DSCP Support for RSVP feature has been configured.
SUMMARY STEPS
1.
enable
2.
show ip rsvp interface [interface-type interface-number] [detail]
3.
exit
DETAILED STEPS
Examples
This section provides the following example output:
Sample Output for the show ip rsvp interface detail Command
In the following sample output from the show ip rsvp interface detail command, only the serial interface 2/0 has DSCP configured. Interfaces that are not configured for DSCP do not show the DSCP value, which is 0 by default.
Router# show ip rsvp interface detailEt1/1:Bandwidth:Curr allocated:0M bits/secMax. allowed (total):7500K bits/secMax. allowed (per flow):7500K bits/secNeighbors:Using IP enacp:1. Using UDP encaps:0Et1/2:Bandwidth:Curr allocated:0M bits/secMax. allowed (total):7500K bits/secMax. allowed (per flow):7500K bits/secNeighbors:Using IP enacp:0. Using UDP encaps:0Se2/0:Bandwidth:Curr allocated:10K bits/secMax. allowed (total):1536K bits/secMax. allowed (per flow):1536K bits/secNeighbors:Using IP enacp:1. Using UDP encaps:0DSCP value used in Path/Resv msgs:0x6Burst Police Factor:300%RSVP:Data Packet Classification provided by: noneConfiguration Examples for Control Plane DSCP Support for RSVP
This section provides the following configuration examples:
•
Verifying Control Plane DSCP Support for RSVP: Example
Configuring a DSCP: Example
The following example configures a DSCP value on an interface:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface Serial2/0Router(config-if)# ip rsvp signalling dscp 48Verifying Control Plane DSCP Support for RSVP: Example
The following example verifies that the Control Plane DSCP Support for RSVP feature has been configured:
Router# show running-config interface Serial2/0interface Serial2/0ip address 10.1.1.1 255.255.255.0fair-queue 64 256 235ip rsvp signalling dscp 48ip rsvp bandwidth 7500 7500Additional References
The following sections provide references related to the Control Plane DSCP Support for RSVP Scalability feature.
Related Documents
Related Topic Document TitleQoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples.
•
Cisco IOS Quality of Service Solutions Command Reference, Release 12.4T
•
Cisco IOS Quality of Service Solutions Command Reference, Release 12.2SR
QoS features including signaling, classification, and congestion management
Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.4T
Standards
Standard TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFC TitleRFC 2205
Resource Reservation Protocol
RFC 2206
RSVP Management Information Base Using SMIv
Technical Assistance
Command Reference
This section documents only commands that are modified.
ip rsvp signalling dscp
To specify the differentiated services code point (DSCP) value to be used on all Resource Reservation Protocol (RSVP) messages transmitted on an interface, use the ip rsvp signalling dscp command in interface configuration mode. To disable this function, use the no form of this command.
ip rsvp signalling dscp value
no ip rsvp signalling dscp
Syntax Description
Defaults
The default value is 0.
Command Modes
Interface configuration.
Command History
Usage Guidelines
You configure the DSCP per interface, not per flow. The DSCP determines the priority that a packet receives from various hops as it travels to its destination.
The DSCP applies to all RSVP flows installed on a specific interface. You can configure each interface independently for DSCP.
Examples
Here is an example of the ip rsvp signalling dscp command with a DSCP value of 6
Router(config-if)# ip rsvp signalling dscp 6Router(config-if)# endTo verify the DSCP value, enter the show ip rsvp interface detail command:
Router# show ip rsvp interface serial2/0 detailSe2/0:Bandwidth:Curr allocated:10K bits/secMax. allowed (total):1536K bits/secMax. allowed (per flow):1536K bits/secNeighbors:Using IP enacp:1. Using UDP encaps:0DSCP value used in Path/Resv msgs:0x6Burst Police Factor:300%RSVP:Data Packet Classification provided by: noneshow ip rsvp interface
To display Resource Reservation Protocol (RSVP)-related information, use the show ip rsvp interface command in privileged EXEC mode.
show ip rsvp interface [interface-type interface-number] [detail]
Syntax Description
interface-type
(Optional) Type of the interface.
interface-number
(Optional) Number of the interface.
detail
(Optional) Additional information about interfaces.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show ip rsvp interface command to display information about interfaces on which RSVP is enabled, including the current allocation budget and maximum available bandwidth. Enter the optional detail keyword for additional information, including bandwidth and signaling parameters and blockade state.
Use the show ip rsvp interface detail command to display information about the RSVP parameters associated with an interface. These parameters include the following:
•
Total RSVP bandwidth
•
RSVP bandwidth allocated to existing flows
•
Maximum RSVP bandwidth that can be allocated to a single flow
•
The type of admission control supported (header compression methods)
•
The compression methods supported by RSVP compression prediction
Examples
The following command shows information for each interface on which RSVP is enabled:
Router# show ip rsvp interfaceinterface allocated i/f max flow max sub maxPO0/0 0 200M 200M 0PO1/0 0 50M 50M 0PO1/1 0 50M 50M 0PO1/2 0 50M 50M 0PO1/3 0 50M 50M 0Lo0 0 200M 200M 0Table 1 describes the fields shown in the display.
Detailed RSVP Information Example
The following command shows detailed RSVP information for each interface on which RSVP is enabled:
Router# show ip rsvp interface detailPO0/0:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):200M bits/secMax. allowed (per flow):200M bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secSignalling:DSCP value used in RSVP msgs:0x3FNumber of refresh intervals to enforce blockade state:4Number of missed refresh messages:4Refresh interval:30PO1/0:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):50M bits/secMax. allowed (per flow):50M bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secSignalling:DSCP value used in RSVP msgs:0x3FNumber of refresh intervals to enforce blockade state:4Number of missed refresh messages:4Refresh interval:30PO1/1:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):50M bits/secMax. allowed (per flow):50M bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secSignalling:DSCP value used in RSVP msgs:0x3FNumber of refresh intervals to enforce blockade state:4Number of missed refresh messages:4Refresh interval:30PO1/2:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):50M bits/secMax. allowed (per flow):50M bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secSignalling:DSCP value used in RSVP msgs:0x3FNumber of refresh intervals to enforce blockade state:4Number of missed refresh messages:4Refresh interval:30PO1/3:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):50M bits/secMax. allowed (per flow):50M bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secSignalling:DSCP value used in RSVP msgs:0x3FNumber of refresh intervals to enforce blockade state:4Number of missed refresh messages:4Refresh interval:30Lo0:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):200M bits/secMax. allowed (per flow):200M bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secSignalling:DSCP value used in RSVP msgs:0x3FNumber of refresh intervals to enforce blockade state:4Number of missed refresh messages:4Refresh interval:30Table 2 describes the significant fields shown in the detailed display for interface PO0/0. The fields for the other interfaces are similar.
RSVP Compression Method Prediction Example
The following example from the show ip rsvp interface detail command shows the RSVP compression method prediction configuration for each interface on which RSVP is configured:
Router# show ip rsvp interface detailEt2/1:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):1158K bits/secMax. allowed (per flow):128K bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secAdmission Control:Header Compression methods supported:rtp (36 bytes-saved), udp (20 bytes-saved)Neighbors:Using IP encap:0. Using UDP encap:0Signalling:Refresh reduction:disabledAuthentication:disabledSe3/0:Bandwidth:Curr allocated:0 bits/secMax. allowed (total):1158K bits/secMax. allowed (per flow):128K bits/secMax. allowed for LSP tunnels using sub-pools:0 bits/secSet aside by policy (total):0 bits/secAdmission Control:Header Compression methods supported:rtp (36 bytes-saved), udp (20 bytes-saved)Neighbors:Using IP encap:1. Using UDP encap:0Signalling:Refresh reduction:disabledAuthentication:disabledTable 3 describes the significant fields shown in the display for Ethernet interface 2/1. The fields for serial interface 3/0 are similar.
Cryptographic Authentication Example
The following example of the show ip rsvp interface detail command displays detailed information, including the cryptographic authentication parameters, for all RSVP-configured interfaces on the router:
Router# show ip rsvp interface detailEt0/0:Bandwidth:Curr allocated: 0 bits/secMax. allowed (total): 7500K bits/secMax. allowed (per flow): 7500K bits/secMax. allowed for LSP tunnels using sub-pools: 0 bits/secSet aside by policy (total):0 bits/secNeighbors:Using IP encap: 0. Using UDP encap: 0Signalling:Refresh reduction: disabledAuthentication: enabledKey: 11223344Type: sha-1Window size: 2Challenge: enabledTable 4 describes the significant fields shown in the display.
Related Commands
Command Descriptionshow ip rsvp installed
Displays RSVP-related installed filters and corresponding bandwidth information.
show ip rsvp neighbor
Displays current RSVP neighbors.
Glossary
admission control—The process in which an RSVP reservation is accepted or rejected based on end-to-end available network resources.
aggregate—A collection of packets with the same DSCP.
bandwidth—The difference between the highest and lowest frequencies available for network signals. This term also describes the rated throughput capacity of a given network medium or protocol.
CBWFQ—class-based weighted fair queueing. A queueing mechanism that extends the standard WFQ functionality to provide support for user-defined traffic classes.
DiffServ—An architecture based on a simple model where traffic entering a network is classified and possibly conditioned at the boundaries of the network. The class of traffic is then identified with a DS code point or bit marking in the IP header. Within the core of the network, packets are forwarded according to the per-hop behavior associated with the DS code point.
DSCP—differentiated services code point. The six most significant bits of the 1-byte IP type of service (ToS) field. The per-hop behavior represented by a particular DSCP value is configurable. DSCP values range between 0 and 63.
enterprise network—A large and diverse network connecting most major points in a company or other organization.
flow—A stream of data traveling between two endpoints across a network (for example, from one LAN station to another). Multiple flows can be transmitted on a single circuit.
packet—A logical grouping of information that includes a header containing control information and (usually) user data. Packets most often refer to network layer units of data.
PBX—private branch exchange. A digital or analog telephone switchboard located on the subscriber premises and used to connect private and public telephone networks.
PHB—per-hop behavior. A DiffServ concept that specifies how specifically marked packets are to be treated by each DiffServ router.
QoS—quality of service. A measure of performance for a transmission system that reflects its transmission quality and service availability.
RSVP—Resource Reservation Protocol. A protocol for reserving network resources to provide quality of service guarantees to application flows.
VoIP—Voice over IP. The ability to carry normal telephony-style voice over an IP-based internet maintaining telephone-like functionality, reliability, and voice quality.
WFQ—weighted fair queueing. A queue management algorithm that provides a certain fraction of link bandwidth to each of several queues, based on relative bandwidth applied to each of the queues.
Note
See Internetworking Terms and Acronyms for terms not included in this glossary.
CCVP, the Cisco Logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0612R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2001, 2007 Cisco Systems, Inc. All rights reserved.


