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 dvmrp route-limit 7000 |
| |
| |
ip address 172.16.1.1 255.255.255.0 |
| |
| |
ip address 10.1.2.1 255.255.255.0 |
| |
|
| |
Listing 10-2: Initial configuration for single server single
reservation scenarios — router B |
| |
|
| |
hostname B |
| |
| |
ip dvmrp route-limit 7000 |
| |
| |
ip address 172.16.2.1 255.255.255.0 |
| |
| |
ip address 10.1.2.2 255.255.255.0 |
| |
| |
ip address 10.1.3.1 255.255.255.0 |
| |
|
| |
Listing 10-3: Initial configuration for single server single
reservation scenarios — router C |
| |
|
| |
hostname C |
| |
| |
ip dvmrp route-limit 7000 |
| |
| |
ip address 172.16.3.1 255.255.255.0 |
| |
| |
ip igmp join-group 224.250.250.1 |
| |
| |
ip address 10.1.3.2 255.255.255.0 |
| |
|
| |
Router A |
| |
| |
ip address 10.1.1.2 255.255.255.0 |
| |
| |
ip rsvp sender 225.1.1.1 10.1.1.1 udp 20 30 10.1.1.1
ethernet0 50 5 |
| |
| |
ip address 10.1.4.1 255.255.255.0 |
| |
| |
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 |
| |
| |
ip address 172.16.1.1 255.255.255.0 |
| |
| |
ip rsvp bandwidth 1705033 1705033 |
| |
| |
ip address 10.1.2.1 255.255.255.0 |
| |
| |
ip rsvp bandwidth 1158 1158 |
| |
244 times read
|
Related news
|
| No matching news for this article |
|
Did you enjoy this article?
(total 0 votes)
|
Sections
Comments (0 posted)
Syndication
