nanog mailing list archives
RE: FRR as Route-Reflector & Scaling stats
From: <adamv0025 () netconsultings com>
Date: Fri, 15 Nov 2019 11:04:12 -0000
ERCIN TORUN Sent: Friday, November 15, 2019 9:34 AM Hello Rakesh, As James said, better to ask it at FRR mailing list. 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).
Data-plane lookup memory limitations have nothing to do with the scale of a RR function, as you eluded to (if the RR is in path then it has to act as any other routing node so FIB scaling limitations apply -but that is completely orthogonal to the RR function). One would assume that NOS to be used for a crucial role in the overall BGP infrastructure would feature the essential ability to limit the installation (complete/selective) of routes to FIB/data-plane. (or in the modern virtual deployments lack the data-plane altogether). adam
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)