This topic is to discuss the following lesson:
Thanks for such good explanation with much debugging messages.
Very clear step by step, like all yours articles.
Comments after each command.
Only issue when I did this lab, it started to work only
after activating eigrp routing because R1 didn’t
Thanks so much.
Glad you liked it! I left routing out of this example but yes, you’ll need something for reachability.
I’ve been searching for an RSVP implementation for linux and haven’t had good luck. Any chance you have come across anything? It seems like there hasn’t been any work since 2000.
I never tried it on Linux (never had to) and even on Cisco devices I don’t see it very often
Hi Rene…thanks for taking time to put this wonderful post together. I’ve got a question. I did not see anywhere in the article you mentioning WFQ or CBWFQ…isn’t WFQ or CBWFQ a prerequisite for RSVP since the flows reservations are based on their QoS weightings?
Your article is really good about RSVP. I have done my own implementation of RSVP into Linux and it works pretty well (I have the same result in R2 and R3 as you when I replace R1 and R4 by my Linux code). However, when I try to use the reservation done it never works. I have two big data flows going through R2 and R3, one matching the RSVP reservation and the other not. But it’s always the flow that I start first which is prioritary even when the reservation is present.
I guess I’m missing a configuration point, but I didn’t see which one (And I have the exact same configuration for R2 and R3 than you have).
Do you have any idea/lead to point me out?
Glad to hear that it is useful to you. It’s hard to tell why the second data flow isn’t working…I’d have to lab it up and try it…
Good comment, RSVP does require WFQ to actually give priority by assigning a low weight. In this tutorial I only focused on RSVP itself and its reservations but this is important to know.
Great article again so clear… Thnx to you !
As long as I read about that, we are able to implement QoS (DSCP or COS) mechanism for MPLS within EXP bits right instead of RSVP. How is the current MPLS network designs with QoS nowadays? RSVP is first precedence for MPLS ?
Intserv (RSVP) isn’t used much to give packets a certain treatment, we use Diffserv (DSCP, COS, MPLS EXP bits) for this. The problem with Intserv is that it’s not scalable.
In MPLS environments however, RSVP can be used for traffic engineering.
I’m not familiar with this protocol but I’ve heard of RSVP-TE. It is used in my job. Do you cover it in this article or is it in another. I could not find it by searching.
RSVP TE is used in MPLS VPN networks, I do have examples for MPLS but I don’t have any RSVP TE examples (yet). I’ll create something and will add it here:
But the concept of RSVP that you explained here is same in MPLS-TE also right ?
I have a question. This configuration sample showed reserve BW between R1 and R4 for telnet traffic, but what if I want to reserve BW for telnet traffic passing though R1 to R4, like I have a host A connecting on R1, and host B connecting on R4, and I’d like to RSVP 64k BW for telnet traffic from A to B which the traffic will passing through R1 and R4, and what if it’s multiple hosts to multiple hosts traffic I want to RSVP? Can you give me an example for that kind of cases?
Thanks a lot.
Hello Y W
In order to understand how RSVP would work with hosts, you can replace R1 and R4 in the topology with two PCs. PCs can also be RSVP hosts and can request or deliver specific levels of QoS. You can even replace them with switches and have several PCs connected to each switch. A PC could still function as an RSVP host and request the bandwidth necessary from end to end.
I hope this has been helpful!
I hope u r doing well!
I want to know what in this command line:
R4(config)#ip rsvp reservation-host 192.168.34.4 192.168.12.1 tcp 23 0 ff rate 64 32
The double ff means please?
I’m doing good, hope you as well!
The “ff” is about the reservation style. There are three options:
• Fixed Filter (ff) is single reservation.
• Shared Explicit (se) is shared reservation, limited scope.
• Wild Card Filter (wf) is shared reservation, unlimited scope.
The fixed filter reservation means that we want to use a reservation for one specific source.