[j-nsp] VPLS route reflection
James Jun
james at towardex.com
Tue Jul 2 00:07:44 EDT 2013
Hey all,
So, I've been trying to google for some sample configuration of BGP-signalled VPLS setup using route-reflectors, and having some trouble finding one. All of the sample BGP-signaled examples on Juniper site are using full-mesh iBGP between PE's with no RR's in the middle.
A pretty simple and straight-forward iBGP topology like this, that we're all used to in a typical SP network:
CE -- PE (rr client) ----- P (route-reflector) ------ P (route-reflector ) ----- PE (rr client) -- CE
So, lacking any config examples, I've just enabled 'family l2vpn signaling;' on existing iBGP sessions that are using the above topology.
Unfortunately, the route-reflector / P-router does not reflect the route received from PE and vice versa -- it is behaving like non-RR client peer that wants full mesh.
When viewing bgp.l2vpn.0 RIB, routers can only see l2vpn NLRI's received from directly configured / meshed peer, but cannot see thru a route-reflector (i.e. P router cannot see NLRIs from a PE that's attached thru another P serving as route-reflector). Please note that unicast inet.0 and inet6.0 RIBs are also carried by same iBGP session transports across the topology -- and those routes obviously work flawlessly using route-reflectors.
Setup looks like this on a P router:
bgp {
group teh-core {
type internal;
family inet {
unicast;
}
family inet6 {
unicast;
}
family l2vpn {
signaling;
}
export mp64-ibgp-export-policy;
peer-as 64552;
neighbor 10.0.0.2 {
description core1.lab2;
}
neighbor 10.0.0.3 {
description core1.lab3;
}
}
group PE-edge-routers__RR-clients {
type internal;
family inet {
unicast;
}
family inet6 {
unicast;
}
family l2vpn {
signaling;
}
export mp64-ibgp-export-policy;
cluster 10.0.0.1;
peer-as 64552;
neighbor 10.0.1.1 {
description edge1.lab1;
}
neighbor 10.0.1.2 {
description edge2.lab1;
}
}
}
Thanks in advance!
james
More information about the juniper-nsp
mailing list