[j-nsp] Issue with MPLS VPN when using mixed LDP and RSVP Backbone !

[Per Granath]

Hi,

The RR needs routes to all its clients in the inet.3 table, otherwise the RR will not advertise inet-vpn routes to its clients.

If you do not want receive those routes via LDP/RSVP, then you can always do a static route on the RR. This will never be used for forwarding, just route reflection:

set routing-options rib inet.3 static route x.x.x.x/y next-hop reject

The x.x.x.x/y could be either 0/0 or some network that includes all your loopbacks.

Cheers.


> >> COming back to the LSP between the PE and the RR, as I have mentioned
> >> before I do see the PE1 Lo0 in the inet.3 on PE4 but I do not see the
> >> PE2/RR Lo0 in the inet.3 on PE4. How to solve this issue. I suspect
> >> this is the issue. For this I tried to create a static deafult in
> >> inet.3 to resolve hte PE2/RR Loopback but it did not help. Also to
> >> mention on PE2/RR we are using RSVP only and no LDP as its not
> >> allwoed to use it over there.