Re: [j-nsp] Many contributing routes

BTW, I personally think that even aggregate routes bring more headache than benefits, let alone generate. Classic case is using aggregate to generate your own public prefixes and at the same time having a loopback address out of this range. Or a static route. Or a connected subnet. Theoretically

Re: [j-nsp] Many contributing routes

aron Gould [mailto:aar...@gvtc.com] Gesendet: Samstag, 12. August 2017 02:03 An: alexander.marh...@gmx.at; 'Vincent Bernat'; juniper-nsp@puck.nether.net Betreff: RE: [j-nsp] Many contributing routes I have a note during a jncis-sp study I did... "generated routes receive the next hop of the prima

Re: [j-nsp] Many contributing routes

I have a note during a jncis-sp study I did... "generated routes receive the next hop of the primary contributing route. primary contributing route is the route with lowest preference of all the contributing routes falling within the aggregate range of prefixes. if there are multiple

Re: [j-nsp] Many contributing routes

On 2017-08-09 09:05, Vincent Bernat wrote: > I am generating a default route to distribute with a policy statement > like that: > > #v+ > policy-statement v4-DEFAULT-ROUTE-GENERATE { [...] > } > #v- > > This works just fine but there are a lot of contributing routes (about > 400k) to

Re: [j-nsp] Many contributing routes

Alexander Marhold Consultant and Trainer -Ursprüngliche Nachricht- Von: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] Im Auftrag von Vincent Bernat Gesendet: Mittwoch, 9. August 2017 09:06 An: juniper-nsp@puck.nether.net Betreff: [j-nsp] Many contributing routes Hey! I am generating

[j-nsp] Many contributing routes

Hey! I am generating a default route to distribute with a policy statement like that: #v+ policy-statement v4-DEFAULT-ROUTE-GENERATE { term v4-TRANSIT-ASX { from { family inet; protocol bgp; neighbor xx.yy.zz.ww;