Hi ! No problem as the generated route gets its info and next-hop address from exactly one contributing route, that is okay
If you would use an aggregated route with 100k of routes instead then you would have the problem of aggregation of all AS numbers which lead to an overflow Regards 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 a default route to distribute with a policy statement like that: #v+ policy-statement v4-DEFAULT-ROUTE-GENERATE { term v4-TRANSIT-ASXXXXX { from { family inet; protocol bgp; neighbor xx.yy.zz.ww; as-path LONG-AS-PATH; } then accept; } term v4-TRANSIT-ASYYYYY { from { family inet; protocol bgp; neighbor xx.yy.zz.ww; as-path LONG-AS-PATH; } then accept; } then reject; } #v- This works just fine but there are a lot of contributing routes (about 400k) to the generated route. Is it harmless or will I run into trouble for that? Thanks! -- A classic is something that everyone wants to have read and nobody wants to read. -- Mark Twain, "The Disappearance of Literature" _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
