[j-nsp] redistributing label between rsvp and ldp

[Keegan Holley]

Labels aren't like routes per se.  They only point to a next hop and not a
destination so you don't have to exchange labels between two routing
protocols in the same way you would routes.  You only have to configure the
routers at the edge of each topology so that it runs both protocols.  That
being said RSVP adds a caveat.  If you try to form a RSVP LSP that
traverses a router that isn't running RSVP it will either fail to form or
re-route.

LDP does not have this constraint and just advertises labels to directly
connected peers.  To bridge between the two protocols I would configure p3
(and every router at the edge of your RSVP domain) as a PE running both LDP
and RSVP.  You can terminate the RSVP LSP's there.  Since it's a PE it
should be able to match the L3VPN information advertised by pe2 via BGP
with the LDP labels it's advertising.

You could also turn on LDP on all of your routers.  Any IP that doesn't
have an RSVP next hop failover to LDP and vise versa.  This is easier to
manage since it will be obvious which paths use LDP and which ones use
RSVP.  The ultimate solution is probably to run only one label protocol
though.



2012/4/29 Uzi Be <good1 at live.com>

>
> hi,
> I was just testing out to swap labels between two different signaling
> protocols (ldp and rsvp). lets say we have two different network, one is
> running ldp and the other one is running rsvp (same AS, so no inter-as
> options).
> ce - pe1 - p1 - p2 - p3 -p4 -pe2 - ce
> so pe1 - p1 - p2 -p3 are running rsvp and p4-pe2 are running ldp, and edge
> ce's are using l3vpn. what are the options to have a labeled path from pe2
> to pe1 (considering that pe1 is not going to run ldp protocol, and pe2
> can't use rsvp so ldp tunneling is not an option here).
> thanks in advance for your comments.
> Andrew
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>