RSVP Refresh Reduction and Reliable Messaging
First Published: November 25, 2002
Last Updated: May 4, 2009
The RSVP Refresh Reduction and Reliable Messaging feature includes refresh reduction, which improves the scalability, latency, and reliability of Resource Reservation Protocol (RSVP) signaling to enhance network performance and message delivery.
Finding Feature Information
For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for RSVP Refresh Reduction and Reliable Messaging" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE 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 RSVP Refresh Reduction and Reliable Messaging
•Restrictions for RSVP Refresh Reduction and Reliable Messaging
•Information About RSVP Refresh Reduction and Reliable Messaging
•How to Configure RSVP Refresh Reduction and Reliable Messaging
•Configuration Examples for RSVP Refresh Reduction and Reliable Messaging
•Additional References
•Feature Information for RSVP Refresh Reduction and Reliable Messaging
Prerequisites for RSVP Refresh Reduction and Reliable Messaging
RSVP must be configured on two or more routers within the network before you can use the RSVP Refresh Reduction and Reliable Messaging feature.
Restrictions for RSVP Refresh Reduction and Reliable Messaging
Multicast flows are not supported for the reliable messages and summary refresh features.
Information About RSVP Refresh Reduction and Reliable Messaging
To configure the RSVP Refresh Reduction and Reliable Messaging feature, you should understand the following concepts:
•Feature Design of RSVP Refresh Reduction and Reliable Messaging
•Types of Messages in RSVP Refresh Reduction and Reliable Messaging
•Benefits of RSVP Refresh Reduction and Reliable Messaging
Feature Design of RSVP Refresh Reduction and Reliable Messaging
RSVP is a network-control, soft-state protocol that enables Internet applications to obtain special qualities of service (QoS) for their data flows. As a soft-state protocol, RSVP requires that state be periodically refreshed. If refresh messages are not transmitted during a specified interval, RSVP state automatically times out and is deleted.
In a network that uses RSVP signaling, reliability and latency problems occur when an RSVP message is lost in transmission. A lost RSVP setup message can cause a delayed or failed reservation; a lost RSVP refresh message can cause a delay in the modification of a reservation or in a reservation timeout. Intolerant applications can fail as a result.
Reliability problems can also occur when there is excessive RSVP refresh message traffic caused by a large number of reservations in the network. Using summary refresh messages can improve reliability by significantly reducing the amount of RSVP refresh traffic.
Note RSVP packets consist of headers that identify the types of messages, and object fields that contain attributes and properties describing how to interpret and act on the content.
Types of Messages in RSVP Refresh Reduction and Reliable Messaging
The RSVP Refresh Reduction and Reliable Messaging feature (Figure 1) includes refresh reduction, which improves the scalability, latency, and reliability of RSVP signaling by introducing the following extensions:
•Reliable messages (MESSAGE_ID, MESSAGE_ID_ACK objects, and ACK messages)
•Bundle messages (reception and processing only)
•Summary refresh messages (MESSAGE_ID_LIST and MESSAGE_ID_NACK objects)
Figure 1 RSVP Refresh Reduction and Reliable Messaging
Reliable Messages
The reliable messages extension supports dependable message delivery among neighboring routers by implementing an acknowledgment mechanism that consists of a MESSAGE_ID object and a MESSAGE_ID_ACK object. The acknowledgments can be transmitted in an ACK message or piggybacked in other RSVP messages.
Each RSVP message contains one MESSAGE_ID object. If the ACK_Desired flag field is set within the MESSAGE_ID object, the receiver transmits a MESSAGE_ID_ACK object to the sender to confirm delivery.
Bundle Messages
A bundle message consists of several standard RSVP messages that are grouped into a single RSVP message.
A bundle message must contain at least one submessage. A submessage can be any RSVP message type other than another bundle message. Submessage types include Path, PathErr, Resv, ResvTear, ResvErr, ResvConf, and ACK.
Bundle messages are addressed directly to the RSVP neighbor. The bundle header immediately follows the IP header, and there is no intermediate transport header.
When a router receives a bundle message that is not addressed to one of its local IP addresses, it forwards the message.
Note Bundle messages can be received, but not sent.
Summary Refresh Messages
A summary refresh message supports the refreshing of RSVP state without the transmission of conventional Path and Resv messages. Therefore, the amount of information that must be transmitted and processed to maintain RSVP state synchronization is greatly reduced.
A summary refresh message carries a set of MESSAGE_ID objects that identify the Path and Resv states that should be refreshed. When an RSVP node receives a summary refresh message, the node matches each received MESSAGE_ID object with the locally installed Path or Resv state. If the MESSAGE_ID objects match the local state, the state is updated as if a standard RSVP refresh message were received. However, if a MESSAGE_ID object does not match the receiver's local state, the receiver notifies the sender of the summary refresh message by transmitting a MESSAGE_ID_NACK object.
When a summary refresh message is used to refresh the state of an RSVP session, the transmission of conventional refresh messages is suppressed. The summary refresh extension cannot be used for a Path or Resv message that contains changes to a previously advertised state. Also, only a state that was previously advertised in Path or Resv messages containing MESSAGE_ID objects can be refreshed by using a summary refresh message.
Benefits of RSVP Refresh Reduction and Reliable Messaging
Enhanced Network Performance
Refresh reduction reduces the volume of steady-state network traffic generated, the amount of CPU resources used, and the response time, thereby enhancing network performance.
Improved Message Delivery
The MESSAGE_ID and the MESSAGE_ID_ACK objects ensure the reliable delivery of messages and support rapid state refresh when a network problem occurs. For example, MESSAGE_ID_ACK objects are used to detect link transmission losses.
How to Configure RSVP Refresh Reduction and Reliable Messaging
This section contains the following procedures:
•Enabling RSVP on an Interface (required)
•Enabling RSVP Refresh Reduction (required)
•Verifying RSVP Refresh Reduction and Reliable Messaging (optional)
Enabling RSVP on an Interface
To enable RSVP on an interface, complete the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface type slot/subslot/port[.subinterface-number]
4. ip rsvp bandwidth [interface-kbps [sub-pool]]
5. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
interface type slot/subslot/port[.subinterface-number]
Router(config)# interface FastEthernet1/0/0 |
Enters interface configuration mode. •The type and number arguments identify the interface to be configured. |
Step 4 |
ip rsvp bandwidth [interface-kbps [sub-pool]]
Router(config-if)# ip rsvp bandwidth 7500 7500 |
Enables RSVP on an interface. •The optional interface-kbps and sub-pool arguments specify the amount of bandwidth that can be allocated by RSVP flows or to a single flow, respectively. Values are from 1 to 10000000, and from 0 to 10000000, respectively. |
Step 5 |
end
Router(config-if)# end |
Returns to privileged EXEC mode. |
Enabling RSVP Refresh Reduction
To enable RSVP refresh reduction, complete the following steps.
SUMMARY STEPS
1. enable
2. configure terminal
3. ip rsvp signalling refresh reduction
4. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
ip rsvp signalling refresh reduction
Router(config)# ip rsvp signalling refresh reduction |
Enables refresh reduction. |
Step 4 |
end
Router(config)# end |
Returns to privileged EXEC mode. |
Verifying RSVP Refresh Reduction and Reliable Messaging
To verify that the RSVP Refresh Reduction and Reliable Messaging feature is functioning as expected, complete the following steps.
SUMMARY STEPS
1. enable
2. clear ip rsvp counters [confirm]
3. show ip rsvp
4. show ip rsvp counters [interface interface-unit | summary | neighbor]
5. show ip rsvp interface [interface-type interface-number] [detail]
6. show ip rsvp neighbor [detail]
7. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
clear ip rsvp counters [confirm]
Router# clear ip rsvp counters |
(Optional) Clears (sets to zero) all IP RSVP counters that are being maintained by the router. |
Step 3 |
show ip rsvp
Router# show ip rsvp |
(Optional) Displays RSVP rate-limiting, refresh-reduction, and neighbor information. |
Step 4 |
show ip rsvp counters [interface interface-unit | summary | neighbor]
Router# show ip rsvp counters summary |
(Optional) Displays the number of RSVP messages that were sent and received on each interface. •The optional summary keyword displays the cumulative number of RSVP messages sent and received by the router over all interfaces. |
Step 5 |
show ip rsvp interface [interface-type interface-number] [detail]
Router# show ip rsvp interface detail |
(Optional) Displays information about interfaces on which RSVP is enabled including the current allocation budget and maximum available bandwidth. •The optional detail keyword displays the bandwidth and signaling parameters. |
Step 6 |
show ip rsvp neighbor [detail]
Router# show ip rsvp neighbor detail |
(Optional) Displays RSVP-neighbor information including IP addresses. •The optional detail keyword displays the current RSVP neighbors and identifies if the neighbor is using IP, User Datagram Protocol (UDP), or RSVP encapsulation for a specified interface or all interfaces. |
Step 7 |
end
Router# end |
Exits privileged EXEC mode. |
Configuration Examples for RSVP Refresh Reduction and Reliable Messaging
This section provides the following configuration example:
•RSVP Refresh Reduction and Reliable Messaging: Example
RSVP Refresh Reduction and Reliable Messaging: Example
In the following example, RSVP refresh reduction is enabled:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# interface FastEthernet1/0/0
Router(config-if)# ip rsvp bandwidth 7500 7500
Router(config)# ip rsvp signalling refresh reduction
The following example verifies that RSVP refresh reduction is enabled:
Router# show running-config
Building configuration...
Current configuration : 1503 bytes
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
logging rate-limit console 10 except errors
no ip dhcp-client network-discovery
ip address 192.168.1.1 255.255.255.0
ip rsvp bandwidth 1705033 1705033
interface FastEthernet0/0/0
ip address 192.168.0.195 255.0.0.0
interface FastEthernet1/0/0
ip address 192.168.5.2 255.255.255.0
ip rsvp bandwidth 7500 7500
interface FastEthernet2/0/0
ip address 192.168.1.2 255.255.255.0
ip rsvp bandwidth 7500 7500
interface FastEthernet0/3/0
ip address 192.168.2.2 255.255.255.0
no eigrp log-neighbor-changes
ip rsvp signalling refresh reduction
transport input pad v120 telnet rlogin udptn
Additional References
The following sections provide references related to the RSVP Refresh Reduction and Reliable Messaging feature.
Related Documents
Standards
|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs
|
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature. |
To locate and download MIBs for selected platforms, Cisco IOS XE software releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs |
RFCs
|
|
RFC 2205 |
Resource Reservation Protocol |
RFC 2206 |
RSVP Management Information Base Using SMIv2 |
RFC 2209 |
RSVP—Version 1 Message Processing Rules |
RFC 2210 |
The Use of RSVP with IETF Integrated Services |
RFC 2211/2212 |
Specification of the Controlled-Load Network Element Service |
RFC 2702 |
Requirements for Traffic Engineering over MPLS |
RFC 2749 |
Common Open Policy Service (COPS) Usage for RSVP |
RFC 2750 |
RSVP Extensions for Policy Control |
RFC 2814 |
SBM Subnet Bandwidth Manager: A Protocol for RSVP-based Admission Control over IEEE 802-style Networks |
RFC 2961 |
RSVP Refresh Overhead Reduction Extensions |
RFC 2996 |
Format of the RSVP DCLASS Object |
Technical Assistance
|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
http://www.cisco.com/techsupport |
Feature Information for RSVP Refresh Reduction and Reliable Messaging
Table 1 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0903R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2002-2009 Cisco Systems, Inc. All rights reserved.