Add Book to My BookshelfPurchase This Book Online

Chapter 10 - Resource Reservation Protocol

Cisco Multicast Routing & Switching
William R. Parkhurst
  Copyright © 1999 The McGraw-Hill Companies

RSVP Scenarios
In this section, various RSVP scenarios are presented to illustrate the use of the RSVP configuration and monitoring commands. Another purpose is to present examples of different combinations of RSVP styles and verify that the router that is the merge point does indeed merge, as presented earlier in the chapter. The first scenarios involve one receiver and one sender, with the receiver requesting either a WF, FF, or SE style reservation. The configurations used do not need any actual multicast senders or receivers. These configurations are meant for you to configure in your own lab for the purpose of practicing and understanding the commands. Senders and receivers will be simulated using the IP_RSVP_SENDER and IP_RSVP_RESERVATION commands. The initial configuration for the network in Figure 10-38 is shown in Listings 10-1 through 10-3.
Figure 10-38: Network for RSVP configuration examples containing a single source and a single reservation
Listing 10-1: Initial configuration for single server single reservation scenarios — router A
hostname A
!
ip multicast-routing
ip dvmrp route-limit 7000
!
interface Loopback0
ip address 172.16.1.1 255.255.255.0
ip pim dense-mode
!
interface Serial0
ip address 10.1.2.1 255.255.255.0
ip pim dense-mode
!
router eigrp 100
network 10.0.0.0
network 172.16.0.0
Listing 10-2: Initial configuration for single server single reservation scenarios — router B
hostname B
!
ip multicast-routing
ip dvmrp route-limit 7000
!
interface Loopback0
ip address 172.16.2.1 255.255.255.0
ip pim dense-mode
!
interface Serial0
ip address 10.1.2.2 255.255.255.0
ip pim dense-mode
clockrate 1544000
!
interface Serial1
ip address 10.1.3.1 255.255.255.0
ip pim dense-mode
clockrate 15440000
!
router eigrp 100
network 10.0.0.0
Listing 10-3: Initial configuration for single server single reservation scenarios — router C
hostname C
ip multicast-routing
ip dvmrp route-limit 7000
!
interface Loopback0
ip address 172.16.3.1 255.255.255.0
ip pim dense-mode
ip igmp join-group 224.250.250.1
!
interface Serial1
ip address 10.1.3.2 255.255.255.0
ip pim dense-mode
bandwidth 1544
no fair-queue
!
router eigrp 100
network 10.0.0.0
network 172.16.0.0
Router A
interface Ethernet0
ip address 10.1.1.2 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth
ip rsvp sender 225.1.1.1 10.1.1.1 udp 20 30 10.1.1.1 ethernet0 50 5
Router C
interface Ethernet0
ip address 10.1.4.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth
ip rsvp reservation 225.1.1.1 10.1.4.2 udp 30 20 10.1.4.2 ethernet0 ff rate 300 60
The initial configurations for routers A, B, and C do not contain any RSVP configuration commands. Initially ip multicast routing and PIM-DM has been configured. Also, the simulated sender and receiver will be located on the loopback interfaces. Since both RSVP and PIM-DM relay on the ip unicast routing table, EIGRP has been enabled on all routers. The first RSVP configuration step is to enable RSVP on all interfaces using the command
ip rsvp bandwidth interface-kbps single-flow-kbps
For these examples we will not use the optional parameters so the form of the command is
ip rsvp bandwidth <CR>
When we use this command on each interface and then list the configuration we can see that the default bandwidth reserved for RSVP is 75 percent of the interface bandwidth. The serial interfaces have been configured for T1 bandwidth, 1.544 Mbits, and 75 percent of 1.544 Mbits is 1.158 Mbit as shown in Listing 10-4. The next step is to simulate the sender on router A with the command
Listing 10-4: Enabling RSVP on the router interfaces
hostname A
!
interface Loopback0
ip address 172.16.1.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
interface Serial0
ip address 10.1.2.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1158 1158
fair-queue 64 256 1000
hostname B
!
interface Serial0
ip address 10.1.2.2 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1158 1158
fair-queue 64 256 1000
clockrate 1544000
!
interface Serial1
ip address 10.1.3.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1158 1158
fair-queue 64 256 1000
clockrate 1544000
hostname C
!
interface Loopback0
ip address 172.16.3.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip igmp join-group 224.250.250.1
interface Serial1
ip address 10.1.3.2 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1500 1500
bandwidth 1544
no fair-queue
ip rsvp sender 224.250.250.1 172.16.1.2 UDP 20 30 172.16.1.2 Lo0 50 10.
To verify that RSVP Path messages are being sent by router A use the command show ip rsvp sender on routers A, B, and C as shown.
A#sh ip rsvp sender
To
From
Pro
Dport
Sport
Prev Hop
I/F
BPS
Bytes
224.250
.250.1
172.16.
1.2
UDP
20
30
172.16.1.2
Lo0
50K
10K
B#show ip rsvp sender
To
From
Pro
Dport
Sport
Prev Hop
I/F
BPS
Bytes
224.250
.250.1
172.16.
1.2
UDP
20
30
10.1.2.1
Se0
50K
10K
C#show ip rsvp sender
To
From
Pro
Dport
Sport
Prev Hop
I/F
BPS
Bytes
224.250.
250.1
172.16.
1.2
UDP
20
30
10.1.3.1
Se1
50K
10K
where
To
IP addresses of the receiver
From
IP Address of the sender
Pro
Protocol code
Dport
Destination port number
Sport
Source port number
Prev Hop
IP address of the previous hop
I/F
Interface of the previous hop
BPS
Reservation rate in bits per second the sender is advertising it might achieve
Bytes
Bytes of the burst size the sender is advertising it might achieve
The final step for the single sender single receiver scenarios is to simulate RSVP Resv messages from the receiver attached to router C using the global command
ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 30 172.16.3.4 Lo0 WF RATE 100 200
The first scenario requests a WF style reservation. The effect of this command can be seen by using the commands show ip rsvp reservation and show ip rsvp request on routers A, B, and C.
A#sh ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
172.16.
1.2
Lo0
WF
RATE
100K
200K
A#sh ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
0.0.0.0
UDP
20
0
10.1.2.2
Se0
WF
RATE
100K
200K
B#sh ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
10.1.2.1
Se0
WF
RATE
100K
200K
B#sh ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
10.1.3.2
Se1
WF
RATE
100K
200K
C#show ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
10.1.3.1
Se1
WF
RATE
100K
200K
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
172.16.3.4
Lo0
WF
RATE
100K
200K
The second scenario for the single sender single receiver group is when the receiver requests a FF style reservation. First, remove the WF reservation from router C using the command
no ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 30 172.16.3.4 Lo0 WF RATE 100 200
Install the FF Style Reservation on Router C with the Global Command
ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 30 172.16.3.4 Lo0 FF RATE 100 200
The only change in the command was to replace WF with FF. Verify the reservation by examining routers A, B, and C.
A#sh ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
172.16.
1.2
UDP
20
30
172.16.1.2
Lo0
FF
RATE
100K
200K
A#sh ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16
.1.2
UDP
20
30
10.1.2.2
Se0
FF
RATE
100K
200K
B#sh ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.250.1
172.16
.1.2
UDP
20
30
10.1.2.1
Se0
FF
RATE
100K
200K
Bash ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
172.16
.1.2
UDP
20
30
10.1.3.2
Se1
FF
RATE
100K
200K
C#show ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16.
1.2
UDP
20
30
10.1.3.1
Se1
FF
RATE
100K
200K
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
172.16
.1.2
UDP
20
30
172.16.3.4
Lo0
FF
RATE
100K
200K
Notice that three fields have changed. The most obvious is the reservation style which has changed from WF to FF. The from address was 0.0.0.0 with a source port of 0 for the WF style. With the FF style the from address is 172.16.1.2 with a source port of 30. The WF filter style did not care about the source of the traffic but the FF style does. Finally replace the FF style reservation with the SE style reservation and examine the effect.
ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 30 172.16.3.4 Lo0 SE RATE 100 200.
A#sh ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16
.1.2
UDP
20
30
172.16.1.2
Lo0
SE
RATE
100K
200K
A#sh ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16
.1.2
UDP
20
30
10.1.2.2
Se0
SE
RATE
100K
200K
B#sh ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
172.16
.1.2
UDP
20
30
10.1.2.1
Se0
SE
RATE
100K
200K
B#sh ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16
.1.2
UDP
20
30
10.1.3.2
Se1
SE
RATE
100K
200K
C#show ip rsvp request
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16.
1.2
UDP
20
30
10.1.3.1
Se1
SE
RATE
100K
200K
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
172.16
.1.2
UDP
20
30
172.16.3.4
Lo0
FF
RATE
100K
200K
Notice that the only change is that FF has changed to SE. Before moving on to the scenarios involving multiple senders and receivers, the rest of the rsvp show commands will be presented. All of the ip rsvp show commands can be listed by executing
B#show ip rsvp ?
installedRSVP installed reservations
interfaceRSVP interface information
neighborRSVP neighbor information
requestRSVP Reservations Upstream
reservationRSVP Reservation Requests from Downstream
senderRSVP Path State information
The show commands listed above will be demonstrated on router B for the previous scenario.
B#show ip rsvp installed ?
Loopback Loopback interface
Null Null interface
Serial Serial
<cr>
The show ip rsvp installed command has the option of showing all interfaces, if <cr> is chosen, or a particular interface as shown below.
B#show ip rsvp installed serial1
RSVP: Serial1
BPS
To
From
Protoc
DPort
Sport
Weight
Conver
sation
100K
224.
250.
250.1
172.16
.1.2
UDP
20
30
4
264
The weight and conversion entries are Weighed Fair Queueing (WFQ) parameters. If WFQ is not configured on the interface then these parameters will be zero.
B#show ip rsvp interface ?
Loopback Loopback interface
Null Null interface
Serial Serial
<cr>
B#show ip rsvp interface Serial1
interfac
allocate
i/f max
flow max
per/255
UDP IP
UDP_IP
UDP M/C
Se1
100K
1158K
1158K
22 /255
0     1
0
0
The fields for the show ip rsvp interface command are
interfac
interface name
allocate
current allocation
i/f max
maximum bandwidth that can be allocated
flow max
maximum flow possible on the interface
per/255
percent of the bandwidth utilized (22/255  = 8.6 percent)
UDP
number of neighbors sending UDP encapsulated RSVP
IP
number of neighbors sending IP encapsulated RSVP
UDP_IP
number of neighbors sending both UDP and IP encapsulated RSVP
UDP M/C
IS UDP configured on this interface? 0 = no 1 = yes
Figure 10-39: RSVP scenario with multiple receivers and a single source
B#show ip rsvp neighbor ?
Loopback Loopback interface
Null Null interface
Serial Serial
<cr>
B#show ip rsvp neighbor
Interfac
Neighbor
Encapsulation
Se0
10.1.2.1
RSVP
Se1
10.1.3.2
RSVP
The show ip rsvp neighbor command simply displays the routers current rsvp neighbors.
Now configure and examine scenarios with multiple receivers and multiple senders for the three RSVP reservation styles. The scenarios that will be configured are listed.
  1. Multiple WF requests with a single source.
  2. Multiple FF requests with a single source.
  3. Multiple SE requests with a single source.
  4. Multiple WF requests with multiple sources.
  5. Multiple FF requests with multiple sources.
  6. Multiple SE requests with multiple sources.
For the first three scenarios involving multiple receivers we need to configure two more receivers on router C.
Router C
interface Loopback0
ip address 172.16.3.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip rsvp udp-multicasts 224.0.0.14
ip igmp join-group 224.250.250.1
!
interface Loopback1
ip address 172.16.5.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip rsvp udp-multicasts 224.0.0.14
ip igmp join-group 224.250.250.1
!
interface Loopback2
ip address 172.16.4.1
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip rsvp udp-multicasts 224.0.0.14
ip igmp join-group 224.250.250.1
!
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.3.2 Lo0 WF RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.5.2 Lo1 WF RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.4.2 Lo2 WF RATE 100 200
There are now three WF reservations for the multicast group 224.250.250.1 installed on router C.
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
172.16.3.2
Lo0
WF
RATE
100K
200K
224.250.
250.1
0.0.0.0
UDP
20
0
172.16.5.2
Lo1
WF
RATE
100K
200K
224.250.
250.1
0.0.0.0
UDP
20
0
172.16.4.2
Lo2
WF
RATE
100K
200K
C#show ip rsvp installed
RSVP: Loopback0
BPS
To
From
Protoc
DPort
Sport
100K
224.250.
250.1
0.0.0.0
UDP
20
0
RSVP: Loopback1
BPS
To
From
Protoc
DPort
Sport
100K
224.250.
250.1
0.0.0.0
UDP
20
0
RSVP: Loopback2
BPS
To
From
Protoc
DPort
Sport
100K
224.250.
250.1
0.0.0.0
UDP
20
0
What reservations do you expect to see installed on router B?
B#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
10.1.3.2
Se1
WF
RATE
100K
200K
R4#show ip rsvp installed
RSVP: Serial1
BPS
To
From
Protoc
Dport
Sport
Weight
Conver-
sation
100K
224.
250.250.1
0.0.0.0
UDP
20
0
4
264
Router B has a reservation that has merged the three WF reservations from router C.
For the FF case remove the WF reservations and install the FF reservations on router C.
no ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.3.2 Lo0 WF RATE 100 200
no ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.5.2 Lo1 WF RATE 100 200
no ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.4.2 Lo2 WF RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.3.2 Lo0 FF RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.5.2 Lo1 FF RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.4.2 Lo2 FF RATE 100 200
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16
.1.2
UDP
20
0
172.16
.3.2
Lo0
FF
RATE
100K
200K
224.250.
250.1
172.16
.1.2
UDP
20
0
172.16
.5.2
Lo1
FF
RATE
100K
200K
224.250.
250.1
172.16
.1.2
UDP
20
0
172.16
.4.2
Lo2
FF
RATE
100K
200K
C#show ip rsvp installed
RSVP: Loopback0
BPS
To
From
Protoc
Dport
Sport
100K
224.250.250.1
172.16.1.2
UDP
20
0
RSVP: Loopback1
BPS
To
From
Protoc
Dport
Sport
100K
224.250.250.1
172.16.1.2
UDP
20
0
RSVP: Loopback2
BPS
To
From
Protoc
Dport
Sport
100K
224.250.250.1
172.16.1.2
UDP
20
0
B#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.16
.1.2
UDP
20
0
10.1.
3.2
Se1
FF
RATE
100K
200K
R4#show ip rsvp installed
RSVP: Serial1
BPS
To
From
Protoc
DPort
Sport
Weight
Conver
sation
100K
224.250
.250.1
172.16.
1.2
UDP
20
0
4
264
As with the WF case, the three FF reservations have been merged into one FF reservation since all reference the same source.
The final single-source multiple-receiver case is the SE style reservation. Configure the SE style on router C using the following commands to verify that the reservations have been installed.
no ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.3.2 Lo0 FF RATE 100 200
no ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.5.2 Lo1 FF RATE 100 200
no ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.4.2 Lo2 FF RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.3.2 Lo0 SE RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.5.2 Lo1 SE RATE 100 200
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.4.2 Lo2 SE RATE 100 200
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250
.250.1
172.16.
1.2
UDP
20
0
172.16.3.2
Lo0
SE
RATE
100K
200K
224.250
.250.1
172.16.
1.2
UDP
20
0
172.16.5.2
Lo1
SE
RATE
100K
200K
224.250
.250.1
172.16.
1.2
UDP
20
0
172.16.4.2
Lo2
SE
RATE
100K
200K
C#show ip rsvp installed
RSVP: Loopback0
BPS
To
From
Protoc
DPort
Sport
100K
224.25
0.250.1
172.16.1.2
UDP
20
0
RSVP: Loopback1
BPS
To
From
Protoc
DPort
Sport
100K
224.25
0.250.1
172.16.1.2
UDP
20
0
RSVP: Loopback2
BPS
To
From
Protoc
DPort
Sport
100K
224.25
0.250.1
172.16.1.2
UDP
20
0
B#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
172.1
6.1.2
UDP
20
0
10.1.3.2
Se1
SE
RATE
100K
200K
B#sh ip rsvp installed
RSVP: Serial0 has no installed reservations
RSVP: Serial1
BPS
To
From
Protoc
Dport
Sport
Weight
Conver
sation
100K
224.250.
250.1
172.16
.1.2
UDP
20
0
4
264
The final three RSVP scenarios involve multiple senders and multiple receivers as shown in Figure 10-40.
Figure 10-40: Multiple sender and multiple receiver RSVP scenario
The loopback interfaces and reservation requests on router C need to be reconfigured, as do the senders on router A.
Router C
interface Loopback0
ip address 172.16.3.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip rsvp udp-multicasts 224.0.0.14
ip igmp join-group 224.250.250.1
!
interface Loopback1
ip address 172.16.5.1 255.255.255.0
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip rsvp udp-multicasts 224.0.0.14
ip igmp join-group 224.250.250.2
!
interface Loopback2
no ip address
ip pim dense-mode
ip rsvp bandwidth 1705033 1705033
ip rsvp udp-multicasts 224.0.0.14
ip igmp join-group 224.250.250.3
ip rsvp reservation 224.250.250.1 0.0.0.0 UDP 20 0 172.16.3.2 Lo0 WF RATE 100 200
ip rsvp reservation 224.250.250.2 0.0.0.0 UDP 20 0 172.16.4.2 Lo1 WF RATE 100 200
ip rsvp reservation 224.250.250.3 0.0.0.0 UDP 20 0 172.16.5.2 Lo2 WF RATE 100 200
Router A
ip rsvp sender 224.250.250.1 172.16.1.2 UDP 20 30 172.16.1.2 Lo0 50 10
ip rsvp sender 224.250.250.2 172.16.1.2 UDP 20 30 172.16.1.2 Lo0 50 10
ip rsvp sender 224.250.250.3 172.16.1.2 UDP 20 30 172.16.1.2 Lo0 50 10
A#show ip rsvp sender
To
From
Pro
Dport
Sport
Prev Hop
I/F
BPS
Bytes
224.250.
250.1
172.16.
1.2
UDP
20
30
172.16.1.2
Lo0
50K
10K
224.250.
250.2
172.16.
1.2
UDP
20
30
172.16.1.2
Lo0
50K
10K
224.250.
250.3
172.16.
1.2
UDP
20
30
172.16.1.2
Lo0
50K
10K
C#show ip rsvp reservation
To
From
Pro
DPort
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
172.16.3.2
Lo0
WF
RATE
100K
200K
224.250.
250.2
0.0.0.0
UDP
20
0
172.16.4.2
Lo1
WF
RATE
100K
200K
224.250.
250.3
0.0.0.0
UDP
20
0
172.16.5.2
Lo2
WF
RATE
100K
200K
B#show ip rsvp reservation
To
From
Pro
DPort
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.250.
250.1
0.0.0.0
UDP
20
0
10.1.3.2
Se1
WF
RATE
100K
200K
224.250.
250.2
0.0.0.0
UDP
20
0
10.1.3.2
Se1
WF
RATE
100K
200K
224.250.
250.3
0.0.0.0
UDP
20
0
10.1.3.2
Se1
WF
RATE
100K
200K
B#sh ip rsvp installed
RSVP: Serial1
BPS
To
From
Protoc
DPort
Sport
Weight
Conver
sation
100K
224.250
.250.3
0.0.0.0
UDP
20
0
4
266
100K
224.250
.250.2
0.0.0.0
UDP
20
0
4
265
100K
224.250
.250.1
0.0.0.0
UDP
20
0
4
264
ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 0 172.16.3.2 Lo0 FF RATE 100 200
ip rsvp reservation 224.250.250.2 172.16.1.2 UDP 20 0 172.16.4.2 Lo1 FF RATE 100 200
ip rsvp reservation 224.250.250.3 172.16.1.2 UDP 20 0 172.16.5.2 Lo2 FF RATE 100 200
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.
250.
250.1
172.16
.1.2
UDP
20
0
172.16.3.2
Lo0
FF
RATE
100K
200K
224.
250.
250.2
172.16
.1.2
UDP
20
0
172.16.3.2
Lo1
FF
RATE
100K
200K
224.
250.
250.3
172.16
.1.2
UDP
20
0
172.16.3.2
Lo2
FF
RATE
100K
200K
C#show ip rsvp installed
RSVP:Loopback0
BPS
To
From
Protoc
Dport
Sport
100K
224.250
.250.1
172.16.1.2
UDP
20
0
RSVP:Loopback1
BPS
To
From
Protoc
Dport
Sport
100K
224.250
.250.2
172.16.1.2
UDP
20
0
RSVP:Loopback2
BPS
To
From
Protoc
DPort
Sport
100K
224.250
.250.3
172.16.1.2
UDP
20
0
B#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.
250.
250.1
172.16
.1.2
UDP
20
0
10.1.3.2
Se1
FF
RATE
100K
200K
224.
250.
250.2
172.16
.1.2
UDP
20
0
10.1.3.2
Se1
FF
RATE
100K
200K
224.
250.
250.3
172.16
.1.2
UDP
20
0
10.1.3.2
Se1
FF
RATE
100K
200K
B#show ip rsvp installed
RSVP: Serial1
BPS
To
From
Protoc
Dport
Sport
Weight
Conver
sation
100K
224.250.
250.3
172.16.
1.2
UDP
20
0
4
266
100K
224.250.
250.2
172.16
.1.2
UDP
20
0
4
265
100K
224.250.
250.1
172.16
.1.2
UDP
20
0
4
264
ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 0 172.16.3.2 Lo0 SE RATE 100 200
ip rsvp reservation 224.250.250.2 172.16.1.2 UDP 20 0 172.16.3.2 Lo1 SE RATE 100 200
ip rsvp reservation 224.250.250.3 172.16.1.2 UDP 20 0 172.16.3.2 Lo2 SE RATE 100 200
C#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.
250.
250.1
172.16
.1.2
UDP
20
0
172.16.3.2
Lo0
SE
RATE
100K
200K
224.
250.
250.2
172.16
.1.2
UDP
20
0
172.16.3.2
Lo1
SE
RATE
100K
200K
224.
250.
250.3
172.16
.1.2
UDP
20
0
172.16.3.2
Lo2
SE
RATE
100K
200K
C#show ip rsvp installed
RSVP:Loopback0
BPS
To
From
Protoc
Dport
Sport
100K
224.250
.250.1
172.16.1.2
UDP
20
0
RSVP:Loopback1
BPS
To
From
Protoc
Dport
Sport
100K
224.250
.250.2
172.16.1.2
UDP
20
0
RSVP:Loopback2
BPS
To
From
Protoc
Dport
Sport
100K
224.250
.250.3
172.16.1.2
UDP
20
0
B#show ip rsvp reservation
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.
250.
250.1
172.16
.1.2
UDP
20
0
10.1.3.2
Se1
SE
RATE
100K
200K
224.
250.
250.2
172.16
.1.2
UDP
20
0
10.1.3.2
Se1
SE
RATE
100K
200K
224.
250.
250.3
172.16
.1.2
UDP
20
0
10.1.3.2
Se1
SE
RATE
100K
200K
B#show ip rsvp installed
RSVP: Serial1
BPS
To
From
Protoc
DPort
Sport
Weight
Conver
sation
100K
224.250.
250.3
172.16
.1.2
UDP
20
0
4
266
100K
224.250.
250.2
172.16
.1.2
UDP
20
0
4
265
100K
224.250.
250.1
172.16
.1.2
UDP
20
0
4
264
B#show ip rsvp res
To
From
Pro
Dport
Sport
Next Hop
I/F
Fi
Serv
BPS
Bytes
224.
250.
250.1
172.16
.1.2
UDP
20
0
172.16.3.2
Lo0
SE
RATE
100K
200K
224.
250.
250.2
172.16
.1.2
UDP
20
0
172.16.3.2
Lo1
FF
RATE
100K
200K
224.
250.
250.3
0.0.0.0
UDP
20
0
172.16.3.2
Lo2
WF
RATE
100K
200K
RSVP: Serial0 has no installed reservations
RSVP: Serial1
BPS
To
From
Protoc
Dport
Sport
Weight
Convers
ation
100K
224.250
.250.3
0.0.0.0
UDP
20
0
4
266
100K
224.250
.250.2
172.16.1.2
UDP
20
0
4
265
100K
224.250
.250.1
172.16.1.2
UDP
20
0
4
264
ip rsvp reservation 224.250.250.1 172.16.1.2 UDP 20 0 172.16.3.2 Lo0 SE RATE 100 200
ip rsvp reservation 224.250.250.2 172.16.1.2 UDP 20 0 172.16.3.2 Lo1 FF RATE 100 200
ip rsvp reservation 224.250.250.3 0.0.0.0 UDP 20 0 172.16.3.2 Lo2 WF RATE 100 200
Debugging RSVP
To verify the operation of RSVP use the following debug commands.
B#debug ip rsvp
RSVP debugging is on
B#
RSVP: Sending RESV message for 224.250.250.3
RSVP: send reservation to 10.1.2.1 about 224.250.250.3
RSVP: IP to 10.1.2.1 length=108 checksum=4DA7 (null)
RSVP: send path multicast about 224.250.250.2 on Serial1
RSVP: IP to 224.250.250.2 length=172 checksum=567F (Serial1)
RSVP: RESV message for 224.250.250.2 (Serial1) from 10.1.3.2
RSVP: PATH message for 224.250.250.2(Serial0) from 10.1.2.1
RSVP: send path multicast about 224.250.250.2 on Serial1
RSVP: IP to 224.250.250.2 length=172 checksum=567F (Serial1)
RSVP: Sending RESV message for 224.250.250.1
RSVP: send reservation to 10.1.2.1 about 224.250.250.1
RSVP: IP to 10.1.2.1 length=108 checksum=5393 (null)
RSVP: Sending RESV message for 224.250.250.2
RSVP: send reservation to 10.1.2.1 about 224.250.250.2
RSVP: IP to 10.1.2.1 length=108 checksum=4DA8 (null)
RSVP: send path multicast about 224.250.250.3 on Serial1
RSVP: IP to 224.250.250.3 length=172 checksum=567E (Serial1)
RSVP: PATH message for 224.250.250.3(Serial0) from 10.1.2.1
RSVP: send path multicast about 224.250.250.3 on Serial1
RSVP: IP to 224.250.250.3 length=172 checksum=567E (Serial1)
RSVP: send path multicast about 224.250.250.1 on Serial1
RSVP: IP to 224.250.250.1 length=172 checksum=5680 (Serial1)
RSVP: PATH message for 224.250.250.1(Serial0) from 10.1.2.1
RSVP: send path multicast about 224.250.250.1 on Serial1
RSVP: IP to 224.250.250.1 length=172 checksum=5680 (Serial1)
RSVP: RESV message for 224.250.250.1 (Serial1) from 10.1.3.2
RSVP: RESV message for 224.250.250.3 (Serial1) from 10.1.3.2
B#debug ip rsvp detail ?
<1—99> Access list
path RSVP packet contents (PATH only)
resv RSVP packet contents (RESV only)
<cr>
B#debug ip rsvp detail path ?
<1—99> Access list
<cr>
Detailed debug information can be gathered using the detail form of the RSVP debug command for either Path or RESV debugging.
B#debug ip rsvp detail path
RSVP debugging is on
B#
RSVP: IP to 10.1.2.1 length=108 checksum=4DA8 (null)
RSVP: IP to 10.1.2.1 length=108 checksum=5393 (null)
RSVP: message received from 172.16.1.2
RSVP: version:1 flags:0000 type:PATH cksum:0000 ttl:62 reserved:0 length:172
SESSION
type 1 length 12: E0FAFA03
: 11000014
HOP
type 1 length 12: 0A010201
: 00000000
TIME_VALUES
type 1 length 8 : 00007530
SENDER_TEMPLATE
type 1 length 12: AC100102
: 0000001E
SENDER_TSPEC type 2 length 36:
version=0 length in words=7
service id=1 service length=6
parameter id=127 flags=0 parameter length=5
average rate=6250 bytes/sec burst depth=10000 bytes peak rate=193000 bytes/sec
min unit=0 bytes max unit=1514 bytes
ADSPEC type 2 length 84:
version=0 length in words=19
General Parameters break bit=0 service length=8
IS Hops:1
Minimum Path Bandwidth (bytes/sec):193000
Path Latency (microseconds):0
Path MTU:1500
Guaranteed Service break bit=0 service length=8
Path Delay (microseconds):3000
Path Jitter (microseconds):7772
Path delay since shaping (microseconds):3000
Path Jitter since shaping (microseconds):7772
Controlled Load Service break bit=0 service length=0
B#debug ip rsvp detail resv
RSVP debugging is on
B#
RSVP: Sending RESV message for 224.250.250.1
RSVP: send reservation to 10.1.2.1 about 224.250.250.1
RSVP: IP to 10.1.2.1 length=108 checksum=5393 (null)
RSVP: version:1 flags:0000 type:RESV cksum:5393 ttl:255 reserved:0 length:108
SESSION type 1 length 12: E0FAFA01
: 11000014
HOP type 1 length 12: 0A010202
: 00000000
TIME_VALUES type 1 length 8 : 00007530
STYLE type 1 length 8 : 00000012
FLOWSPEC type 2 length 48:
  version = 0 length in words = 10
  service id = 2 service length = 9
  tspec parameter id = 127 tspec flags = 0 tspec length = 5
  average rate = 12500 bytes/sec burst depth = 200000 bytes peak rate = 12
500 bytes/sec
  min unit = 0 bytes max unit = 65535 bytes
rspec parameter id=130 rspec flags=0 rspec length=2
requested rate=12500 slack=0
FILTER_SPEC type 1 length 12: AC100102
: 00000000
Finally, reservations on a router can be cleared by using the clear ip rsvp command.
B#clear ip rsvp ?
reservation Clear RSVP reservations
sender Clear RSVP path state information
B#clear ip rsvp res ?
* Clear all reservations
Hostname or A.B.C.D Destination address
B#clear ip rsvp res *

 


 
Books24x7.com, Inc © 2000 –  Feedback