We're using VPLS and L2VPN on Juniper MX for L2 connections. Signaling is done via BGP and label distribution via LDP.
Now we want one l2vpn to use a specific path trough the network and not follow the IGP.
I already asked this on the stackexchange site: http://networkengineering.stackexchange.com/questions/449/how-to-force-vpls-l2vpn-to-use-a-specific-path
We came to the conclusion that it would be best to use l2circuit and bind the circuit to a special path with a community, like described here:
http://kb.juniper.net/InfoCenter/index?page=content&id=KB22700&smlogin=true
To do that I enabled RSVP and configured a specific path:
[protocols mpls]
label-switched-path lsp-l2circuit {
to 10.0.0.1;
no-cspf;
preference 10;
primary path-l2circut;
}
path path-l2circuit {
10.0.0.2 strict;
10.0.0.1 strict;
}
Note the "preference 10". This was done so that the rest (l2vpn, vpls) still follows LDP instead of this path.
Then we set up the l2circuit with a community:
[protocols l2circuit]
neighbor 10.0.0.1 {
interface xe-1/3/0.3 {
virtual-circuit-id 1;
community l2circuit-community;
}
}
And lastly we configured a policy to map this community to the lsp in the forwarding-table:
[policy-options policy-statement l2circuit-mapping]
term l2circuit-mapping {
from community l2circuit-community;
then {
install-nexthop lsp lsp-l2circuit;
}
}
[routing-options forwarding-table]
export [ ecmp l2circuit-mapping ];
Now this looks good but sadly it doesn't work. 🙂
The l2circuit stays down with error "OL" (no outgoing label).
In the mpls.0 table I see that the RSVP route is there but not active and I assume that that might be the problem:
10.0.0.1/32 *[LDP/9] 1d 20:23:23, metric 1
> to 10.0.0.81 via ae4.0, Push 357888
[RSVP/10/1] 1d 20:23:08, metric 2001
> to 10.0.0.81 via ae4.0, label-switched-path lsp-l2circuit
So.. my question is: Is it possible to use RSVP only for a specific l2circuit while using LDP for all other connections? If so, how do I have to configure it to make it work?