RSVP DSBM (Designated Subnetwork Bandwidth Manager)

RSVP will work fine when you need to make a reservation on the link between two routers, but what if you have a shared segment? An example could be a couple of routers that is connected to the same half-duplex Ethernet network. These routers will share the bandwidth so when multiple routers make an RSVP reservation it’s possible that we oversubscribe.

The routers should know about all RSVP reservations that are made on this shared segment and that’s exactly why we have the DSBM (Designated Subnetwork Bandwidth Manager).

One of the routers on the shared segment will be elected as the DSBM and all other RSVP routers will proxy their RSVP PATH and RESV messages through the DSBM. This way we will have centralized admission control and we won’t risk oversubscribing the shared segment.

Besides being in charge of admission control, the DSBM can also distribute other information to RSVP routers, for example the amount of non-reservable traffic that is allowed in the shared segment or the average/peak rate and burst size for non-RSVP traffic.

The election to become the RSVP DSBM uses the following rules:

  • The router with the highest priority becomes the DSBM.
  • In case the priority is the same, the highest IP address is the tie-breaker.

Multiple DSBMs can be configured for a shared segment but DSBM is non-preemptive. This means that once the election is over, the router that was elected will stay as the DSBM even if you configure another router later with a higher priority.

Configuration-wise it’s easy to implement DSBM, let’s use the following topology to see how it works:

RSVP DSBM

Just 3 routers connected to the same switch. First we will enable RSVP on all interfaces:

R1(config)#interface FastEthernet 0/0
R1(config-if)#ip rsvp bandwidth 
R2(config)#interface FastEthernet 0/0
R2(config-if)#ip rsvp bandwidth 
R3(config)#interface FastEthernet 0/0
R3(config-if)#ip rsvp bandwidth

Now we’ll configure R3 as the DSBM for this segment:

R3(config)#interface FastEthernet 0/0
R3(config-if)#ip rsvp dsbm candidate 

If you want, you can configure the DSBM to tell other RSVP routers to limit the reservations:

We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 651 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

555 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Forum Replies

  1. Dear Rene,

    Could you explain where practically (Scenario) this would be used?

    Regards,

    Rajiv R

  2. Hello,

    I would like to ask if any non-resv-send-limit was configured on R3. I can see some Non Resv Send Limit values for current DSBM outputs. Also on R3 output there is no Non Resv Send Limit displayed for Local Configuration.

    One small remark is for the Configuration tab / R3 at the end of the chapter. There should be an ip rsvp dsbm candidate.

    Many thanks,
    Stefanita

  3. Hi Stefanita,

    I didn’t configure anything on purpose, but there are some default RSVP commands. Here are all rsvp commands we configured:

    R3#show run | include rsvp 
     ip rsvp bandwidth 2048

    And here are all default commands and values:

    R
    ... Continue reading in our forum

Ask a question or join the discussion by visiting our Community Forum