Re: [j-nsp] Optimizing the FIB on MX

2016-02-20 Thread Raphael Mazelier
Le 19/02/2016 14:08, Adam Vitkovsky a écrit : No Multipath between iBGP paths would be similar to 'protect core' Multipath between eBGP and iBGP paths would be similar to 'unicast protection' Whereas in protection mode you use one active path and the other path is backup and in multipath both

Re: [j-nsp] Enable EVPN on existing mpls l3vpn network

2016-02-20 Thread Raphael Mazelier
Le 19/02/2016 17:44, Aaron a écrit : I love my bgp route reflector cluster... all my pe's neighbor with 2 bgp rr cluster members... anytime I want to add an address family to a pe, I add it to one rr cluster neighbor session, it bounces, once routes have been relearned over it, I add the af to

Re: [j-nsp] Optimizing the FIB on MX

2016-02-20 Thread Dragan Jovicic
I had a peek at JunOS documentation; regarding "protect core" and newer unicast/labeled "protection" commands - they seem to do the same thing. Both methods rely on having additional backup route(s) in table and being installed into FIB, albeit with greater weight. I see one issue with convergence

Re: [j-nsp] PLP Bit

2016-02-20 Thread Saku Ytti
On 20 February 2016 at 14:48, wrote: Hey, > This is a very basic question, but i can't find a clear statement about. > > As per my understanding JunOS has two different congestion avoidance > mechanisms: RED and WRED. > And the main difference is that RED relies only on PLP, while WRED let you

[j-nsp] PLP Bit

2016-02-20 Thread marco
Hello, This is a very basic question, but i can't find a clear statement about. As per my understanding JunOS has two different congestion avoidance mechanisms: RED and WRED. And the main difference is that RED relies only on PLP, while WRED let you drop at different rates on a per "color" bas

Re: [j-nsp] leak routes between L3VPN VRF's

2016-02-20 Thread Saku Ytti
On 20 February 2016 at 13:21, tim tiriche wrote: Hey, > How can i leak routes between VRF1 and VRF2 on the same PE and across PE > > a) Can i do it only using RT (vrf-import)? or do i need to also implement > rib-groups? > b) can i do auto-export with policies on PE1 for exchanging routes only >

Re: [j-nsp] leak routes between L3VPN VRF's

2016-02-20 Thread Dave Bell
Hi Tim, The only additional config to import routes between VRFs on the same PE, as opposed to between VRFs on different PEs is the auto-export knob. No rib-groups required. Just configure the required RTs for import under the vrf-import config. If you want to have a bit more control about what y

[j-nsp] leak routes between L3VPN VRF's

2016-02-20 Thread tim tiriche
Hello, I am looking for a clean and simple way to leak routes between VRF's on the same PE and across different PE? For eg: On PE1 and PE2, if i have 3 VRF's. (VRF1, VRF2, VRF3). These are mpls l3vpn vrf's. How can i leak routes between VRF1 and VRF2 on the same PE and across PE a) Can i do i