RSVP Interface-Based Receiver Proxy

Last Updated: December 9, 2011

The RSVP Interface-Based Receiver Proxy feature lets you configure a proxy router by outbound interface instead of configuring a destination address for each flow going through the same interface.

Finding Feature Information

Your software release may not support all the features documented in this module. 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 Table at the end of this document.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Prerequisites for RSVP Interface-Based Receiver Proxy

You must configure an IP address and enable Resource Reservation Protocol (RSVP) on one or more interfaces on at least two neighboring routers that share a link within the network.

Restrictions for RSVP Interface-Based Receiver Proxy

  • Filtering using access control lists (ACLs), application IDs, or other mechanisms is not supported.
  • A provider edge (PE) router cannot switch from being a proxy node to a transit node for a given flow during the lifetime of the flow.

Information About RSVP Interface-Based Receiver Proxy

Feature Overview of RSVP Interface-Based Receiver Proxy

The RSVP Interface-Based Receiver Proxy feature allows you to use RSVP to signal reservations and guarantee bandwidth on behalf of a receiver that does not support RSVP by terminating the PATH message and generating a RESV message in the upstream direction on an RSVP-capable router on the path to the endpoint. An example is a video-on-demand flow from a video server to a set-top box, which is a computer that acts as a receiver and decodes the incoming video signal from the video server.

Because set-top boxes may not support RSVP natively, you cannot configure end-to-end RSVP reservations between a video server and a set-top box. Instead, you can enable the RSVP interface-based receiver proxy on the router that is closest to that set-top box.

The router terminates the end-to-end sessions for many set-top boxes and performs admission control on the outbound (or egress) interface of the PATH message, where the receiver proxy is configured, as a proxy for Call Admission Control (CAC) on the router-to-set-top link. The RSVP interface-based receiver proxy determines which PATH messages to terminate by looking at the outbound interface to be used by the traffic flow.

You can configure an RSVP interface-based receiver proxy to terminate PATH messages going out a specified interface with a specific action (reply with RESV, or reject). The most common application is to configure the receiver proxy on the edge of an administrative domain on interdomain interfaces. The router then terminates PATH messages going out the administrative domain while still permitting PATH messages transitioning through the router within the same administrative domain to continue downstream.

The router terminates the end-to-end sessions for many set-top boxes, with the assumption that the links further downstream (for example, from the DSLAM to the set-top box) never become congested or, more likely, in the case of congestion, that the voice and video traffic from the router gets the highest priority and access to the bandwidth.

Benefits of RSVP Interface-Based Receiver Proxy

Before the RSVP Interface-Based Receiver Proxy feature was introduced, you had to configure a receiver proxy for every separate RSVP stream or set-top box. The RSVP Interface-Based Receiver Proxy feature allows you to configure the proxy by outbound interface. For example, if there were 100 set-top boxes downstream from the proxy router, you had to configure 100 proxies. With this enhancement, you configure only the outbound interfaces. In addition, the receiver proxy is guaranteed to terminate the reservation only on the last hop within the core network. Nodes that may function as transit nodes for some PATH messages but should proxy others depending on their placement in the network can perform the correct functions on a flow-by-flow basis.

How to Configure RSVP Interface-Based Receiver Proxy

Enabling RSVP on an Interface

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    interface type slot / subslot / port

4.    ip rsvp bandwidth [interface-kbps [single-flow-kbps[bc1 kbps | sub-pool kbps]]| percent percent-bandwidth [single-flow-kbps]]

5.    end


DETAILED STEPS
  Command or Action Purpose
Step 1
enable


Example:

Router> enable

 

Enables privileged EXEC mode.

  • Enter your password if prompted.
 
Step 2
configure terminal


Example:

Router# configure terminal

 

Enters global configuration mode.

 
Step 3
interface type slot / subslot / port


Example:

Router(config)# interface gigabitEthernet0/0/0

 

Configures the interface type and enters interface configuration mode.

 
Step 4
ip rsvp bandwidth [interface-kbps [single-flow-kbps[bc1 kbps | sub-pool kbps]]| percent percent-bandwidth [single-flow-kbps]]


Example:



Example:



Example:



Example:



Example:



Example:



Example:



Example:



Example:

Router(config-if)# ip rsvp bandwidth 7500 7500

 

Enables RSVP on an interface.

  • The optional interface-kbps and single-flow-kbps arguments specify the amount of bandwidth that can be allocated by RSVP flows or to a single flow, respectively. Range is from 1 to 10000000.
  • The optional sub-pooland sub-pool-kbpskeyword and argument specify subpool traffic and the amount of bandwidth that can be allocated by RSVP flows. Range is from 1 to 10000000.
Note    Repeat this command for each interface on which you want to enable RSVP.
 
Step 5
end


Example:

Router(config-if)# end

 

(Optional) Returns to privileged EXEC mode.

 

Configuring a Receiver Proxy on an Outbound Interface

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    interface type slot / subslot / port

4.    ip rsvp listener outbound {reply | reject}

5.    end


DETAILED STEPS
  Command or Action Purpose
Step 1
enable


Example:

Router> enable

 

Enables privileged EXEC mode.

  • Enter your password if prompted.
 
Step 2
configure terminal


Example:

Router# configure terminal

 

Enters global configuration mode.

 
Step 3
interface type slot / subslot / port


Example:

Router(config)# interface gigabitEthernet 0/0/0

 

Configures the interface type and enters interface configuration mode.

 
Step 4
ip rsvp listener outbound {reply | reject}


Example:

Router(config-if)# ip rsvp listener outbound reject

 

Configures an RSVP router to listen for PATH messages sent through a specified interface.

  • Enter the reply keyword or the reject keyword to specify the response that you want to PATH messages.
 
Step 5
end


Example:

Router(config-if)# end

 

(Optional) Returns to privileged EXEC mode.

 

Verifying the RSVP Interface-Based Receiver Proxy Configuration

Perform the following task to verify the configuration. You can use these commands in any order.


Note
You can use the following show commands in user EXEC or privileged EXEC mode.
SUMMARY STEPS

1.    enable

2.    show ip rsvp listeners [ip-address| any] [udp | tcp | any | protocol][dst-port | any]

3.    show ip rsvp sender [detail] [filter [destination address] [dst-port port-number] [source address] [src-port port-number]]

4.    show ip rsvp reservation [detail] [filter [destination address] [dst-port port-number] [source address] [src-port port-number]]

5.    exit


DETAILED STEPS
  Command or Action Purpose
Step 1
enable


Example:

Router> enable

 

(Optional) Enables privileged EXEC mode.

  • Enter your password if prompted.
Note    Omit this step if you are using the show commands in user EXEC mode.
 
Step 2
show ip rsvp listeners [ip-address| any] [udp | tcp | any | protocol][dst-port | any]


Example:

Router# show ip rsvp listeners

 

Displays RSVP listeners for a specified port or protocol.

 
Step 3
show ip rsvp sender [detail] [filter [destination address] [dst-port port-number] [source address] [src-port port-number]]


Example:

Router# show ip rsvp sender detail

 

Displays RSVP PATH-related sender information currently in the database.

 
Step 4
show ip rsvp reservation [detail] [filter [destination address] [dst-port port-number] [source address] [src-port port-number]]


Example:

Router# show ip rsvp reservation detail

 

Displays RSVP-related receiver information currently in the database.

 
Step 5
exit


Example:

Router# exit

 

(Optional) Exits privileged EXEC mode and returns to user EXEC mode.

 

Configuration Examples for RSVP Interface-Based Receiver Proxy

Examples Configuring RSVP Interface-Based Receiver Proxy

The four-router network in the figure below contains the configurations for the examples shown in the following sections:

Figure 1 Sample Network with an Interface-Based Receiver Proxy Configured


Configuring a Receiver Proxy on a Middle Router on Behalf of Tailend Routers

The following example configures a receiver proxy, also called a listener, on the middle router (Router 2) on behalf of the two tailend routers (Routers 3 and 4): 

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# interface gigabitEthernet 2/0/0
Router(config-if)# ip rsvp listener outbound reply
Router(config-if)# exit
Router(config)# interface gigabitethernet 3/0/0
Router(config-if)# ip rsvp listener outbound reject
Router(config-if)# end

Configuring PATH Messages from a Headend Router to Tailend Routers to Test the Receiver Proxy


Note
If you do not have another headend router generating RSVP PATH messages available, configure one in the network for the specific purpose of testing RSVP features such as the receiver proxy. Note that these commands are not expected (or supported) in a final deployment.

The following example configures four PATH messages from the headend router (Router 1) to the tailend routers (Routers 3 and 4): 

Router# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# ip rsvp sender-host 10.0.0.5 10.0.0.1 TCP 2 2 100 10
Router(config)# ip rsvp sender-host 10.0.0.5 10.0.0.1 UDP 1 1 100 10
Router(config)# ip rsvp sender-host 10.0.0.7 10.0.0.1 TCP 4 4 100 10
Router(config)# ip rsvp sender-host 10.0.0.7 10.0.0.1 UDP 3 3 100 10
Router(config)# end

Examples Verifying RSVP Interface-Based Receiver Proxy

This section contains the following verification examples:

Verifying the PATH Messages in the Database

The following example verifies that the PATH messages you configured are in the database:

Router# show ip rsvp sender
To              From            Pro DPort Sport Prev Hop        I/F      BPS
10.0.0.5        10.0.0.1        TCP 2     2     none            none     100K
10.0.0.5        10.0.0.1        UDP 1     1     none            none     100K
10.0.0.7        10.0.0.1        TCP 4     4     none            none     100K
10.0.0.7        10.0.0.1        UDP 3     3     none            none     100K

The following example verifies that a PATH message has been terminated by a receiver proxy configured to reply.


Note
A receiver proxy that is configured to reject does not cause any state to be stored in the RSVP database; therefore, this show command does not display these PATH messages. Only one PATH message is shown. 
Router# show ip rsvp sender detail
PATH:
  Destination 10.0.0.5, Protocol_Id 17, Don't Police , DstPort 1
  Sender address: 10.0.0.1, port: 1
  Path refreshes:
    arriving: from PHOP 10.1.2.1 on Et0/0 every 30000 msecs
  Traffic params - Rate: 100K bits/sec, Max. burst: 10K bytes
    Min Policed Unit: 0 bytes, Max Pkt Size 2147483647 bytes
  Path ID handle: 01000402.
  Incoming policy: Accepted. Policy source(s): Default
  Status: Proxy-terminated
  Output on Ethernet2/0. Policy status: NOT Forwarding. Handle: 02000401
    Policy source(s):
  Path FLR: Never repaired

Verifying the Running Configuration

The following example verifies the configuration for GigabitEthernet interface 2/0/0:

Router# show running-config interface gigbitEthernet 2/0/0
Building configuration...
Current configuration : 132 bytes
!
interface gigabitEthernet2/0/0
 ip address 172.16.0.1 255.0.0.0
 no cdp enable
 ip rsvp bandwidth 2000
 ip rsvp listener outbound reply
end

The following example verifies the configuration for GigabitEthernet interface 3/0/0:

Router# show running-config interface gigbitEthernet 3/0/0
Building configuration...
Current configuration : 133 bytes
!
interface gigabitEthernet3/0/0
 ip address 172.16.0.2 255.0.0.0
 no cdp enable
 ip rsvp bandwidth 2000
 ip rsvp listener outbound reject
end

Verifying the Listeners

The following example verifies the listeners (proxies) that you configured on the middle router (Router 2) on behalf of the two tailend routers (Routers 3 and 4):

Router# show ip rsvp listener
To                 Protocol   DPort   Description                 Action    OutIf
10.0.0.0           0          0       RSVP Proxy                  reply     Et2/0
10.0.0.0           0          0       RSVP Proxy                  reject    Et3/0

Verifying the Reservations

The following example displays reservations established by the middle router (Router 2) on behalf of the tailend routers (Routers 3 and 4) as seen from the headend router (Router 1):

Router# show ip rsvp reservation
To            From          Pro DPort Sport Next Hop      I/F      Fi Serv BPS
10.0.0.7      10.0.0.1      TCP 4     4     10.0.0.2      Gi1/0    FF RATE 100K
10.0.0.7      10.0.0.1      UDP 3     3     10.0.0.2      Gi1/0    FF RATE 100K

The following example verifies that a reservation is locally generated (proxied). Only one reservation is shown:

Router# show ip rsvp reservation detail
RSVP Reservation. Destination is 10.0.0.7, Source is 10.0.0.1, 
  Protocol is UDP, Destination port is 1, Source port is 1
  Next Hop: 10.2.3.3 on GigabitEthernet2/0/0
  Reservation Style is Fixed-Filter, QoS Service is Guaranteed-Rate
  Resv ID handle: 01000405.
  Created: 09:24:24 EST Fri Jun 2 2006
  Average Bitrate is 100K bits/sec, Maximum Burst is 10K bytes
  Min Policed Unit: 0 bytes, Max Pkt Size: 0 bytes
  Status: Proxied
  Policy: Forwarding. Policy source(s): Default

Verifying CAC on an Outbound Interface

The following example verifies that the proxied reservation performed CAC on the local outbound interface:

Router# show ip rsvp installed
RSVP: GigabitEthernet2/0/0 has no installed reservations
RSVP: GigabitEthernet3/0/0
BPS    To              From            Protoc DPort  Sport  
100K   10.0.0.7        10.0.0.1        UDP    1       1

Additional References

The following sections provide references related to the RSVP Interface-Based Receiver Proxy feature.

Related Documents

Related Topic

Document Title

QoS commands: complete command syntax, command modes, command history, defaults, usage guidelines, and examples

Cisco IOS Quality of Service Solutions Command Reference

QoS configuration tasks related to RSVP

"Configuring RSVP" module

Internet draft

RSVP Proxy Approaches , Internet draft, October 2006 [draft-lefaucheur-tsvwg-rsvp-proxy-00.txt]

Standards

Standard

Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

--

MIBs

MIB

MIBs Link

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 software releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

RFCs

RFC

Title

RFC 2205

Resource ReSerVation Protocol (RSVP)

Technical Assistance

Description

Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html

Feature Information for RSVP Interface-Based Receiver Proxy

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 1 Feature Information for RSVP Interface-Based Receiver Proxy

Feature Name

Releases

Feature Information

RSVP Interface-Based Receiver Proxy

Cisco IOS XE Release 2.6

The RSVP Interface-Based Receiver Proxy feature lets you configure a proxy router by outbound interface instead of configuring a destination address for each flow going through the same interface.

The following commands were introduced or modified: ip rsvp bandwidth, ip rsvp listener outbound, show ip rsvp listeners, show ip rsvp reservation, show ip rsvp sender.

Glossary

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.

PE router --provider edge router. A router that is part of a service provider's network and is connected to a customer edge (CE) router.

proxy --A component of RSVP that manages all locally originated and terminated state.

receiver proxy --A configurable feature that allows a router to proxy RSVP RESV messages for local or remote destinations.

RSVP --Resource Reservation Protocol. A protocol for reserving network resources to provide quality of service guarantees to application flows.

set-top box--A computer that acts as a receiver and decodes the incoming signal from a satellite dish, a cable network, or a telephone line.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)

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.

© 2011 Cisco Systems, Inc. All rights reserved.