08-12-2009 06:34 AM
An IGP is needed to secure connectivity between loopbacks over multiple hop connections. Loopbacks are used for ingress and egress for RSVP LSPs. Besides if you use RSVP and want traffic engineering, traffic engineering database need to be calculated by an IGP.
So in short I woudl say "No", you need an IGP.
08-12-2009 07:13 AM
Thanks, Patrik, for your answer.
The matter concerns the state of mpls and not TE:
once I enable on the both ends RSVP and MPLS having only routes known from protocol "Direct", - will MPLS state come up?
What will show the output "show mpls lsp"?
08-12-2009 02:00 PM
Yes. RSVP and MPLS are not IGPs. RSVP calculates a label per hop going backwards from egress router to ingress router. But on each hop the needs to take best hop towards ingress router loopback. So an IGP route is needed on each hop to point towards the loopback.
And just to be sure I tried this in my lab aswell. I had two routers directly attached to eachother using loopbacks and ISIS, RSVP, MPLS and BGP. To be extra fun, I added a L2VPN circuit and a L3VPN aswell. WHen ISIS was deactivated on one of the routers, RSVP LSPs was torned down after about a minute due to timeouts.
So Yes, the network need an IGP to support RSVP/MPLS based LSPs aswell.
08-13-2009 12:54 AM
IMHO you can establish RSVP tunnel without having IGP protocol by using static routes and ERO (ERO constraints + no-cspf; strict hop does not allow for IGP recursive lookup). However, you would not be able to use any TED-based features (e.g. FFR, link coloring etc).
08-13-2009 02:33 AM
Tested your theory. Used static routes for connectivity between loopbacks. USed consgtraint path and turned of cspf. Still the LSP was tored down when ISIS was deactivated.
So it seems you are dependent on IGP.
08-13-2009 02:36 AM
Sorry, I was to quick.
With a little patient the LSP came up!
So if you make sure there are static routes to accomodate connectivity for loopbacks, go cspf and ERO, you can get RSVP tunnels.
But in a more complex non lab network it doesnt seem like a good solution since you need to maintainm a static route table giving connectivity to all PE:s loopbacks.