nanog mailing list archives
Re: FRR as Route-Reflector & Scaling stats
From: Vincent Bernat <bernat () luffy cx>
Date: Fri, 15 Nov 2019 13:22:53 +0100
❦ 15 novembre 2019 09:33 +00, ERCIN TORUN <ercin.torun () turkcell com tr>:
Generally chipset is what limits the scale (e.g. trident2 is 128k ipv4 lpm https://docs.cumulusnetworks.com/cumulus-linux/Layer-3/Routing/ ). If you disable "zebra" daemon, FRR works only in control-plane then you would most likely have a limitation with memory/RAM only. (speed is another issue).
To avoid disabling Zebra daemon, you can use "table-map" to choose the routes to send to Zebra: <http://docs.frrouting.org/en/latest/bgp.html#clicmd-table-mapROUTE-MAP-NAME> For example: route-map DENY_ALL deny 10 router bgp 65000 vrf private address-family ipv4 unicast table-map DENY_ALL exit-address-family -- Avoid unnecessary branches. - The Elements of Programming Style (Kernighan & Plauger)
Current thread:
- FRR as Route-Reflector & Scaling stats Rakesh M (Nov 07)
- Re: FRR as Route-Reflector & Scaling stats James Bensley (Nov 07)
- RE: FRR as Route-Reflector & Scaling stats ERCIN TORUN (Nov 15)
- RE: FRR as Route-Reflector & Scaling stats adamv0025 (Nov 15)
- Re: FRR as Route-Reflector & Scaling stats Rakesh M (Nov 15)
- Re: FRR as Route-Reflector & Scaling stats Vincent Bernat (Nov 15)
- RE: FRR as Route-Reflector & Scaling stats ERCIN TORUN (Nov 15)
- Re: FRR as Route-Reflector & Scaling stats James Bensley (Nov 07)