[j-nsp] auto b/w mpls best practice -- cpu spikes

On 13/Sep/18 19:11, Saku Ytti wrote: > New software is bad, old software is good adage is not data driven. We > also need to understand what vendor is doing, how are they developing, > how are they testing, how are they releasing and when they are > changing something, in which release will the

[j-nsp] vRR/L3VPN/Unusable

So back when I ran RR's on an M120 (anyone remember Junos 10.4), this is how we did it on out-of-path RR's: * routing-options { ...     rib-groups {     IGP-RIB {     import-rib [ inet.0 inet.3 inet6.3 ];     }     } ...     } } protocols { ...     isis { rib-grou