[dev] A question about the # of vrf per router or switch can support by FRR?

Vivek Venkatraman vivek at cumulusnetworks.com
Thu Nov 2 23:45:53 EDT 2017


In the Linux kernel model, the VRF is a netdevice. So, for PE-scale scaling
of VRFs, that is also a factor in the mix.

On Wed, Nov 1, 2017 at 12:28 PM, Donald Sharp <sharpd at cumulusnetworks.com>
wrote:

> Jeff -
>
> I thought I was pretty careful in my reply.  I've seen testing of 64
> vrf's and I consider that many vrf's hard to operationally deploy.  I
> don't disagree with you that some PE's will deploy thousands of VRF's.
> I was/am unwilling to claim vrf scaling until we get someone who
> actually tries it out and possibly runs into some data structure
> design flaw in FRR/kernel that we did not consider.  I actually think
> it would be really interesting for someone to give it a shot, though!
> It would provide valuable feedback to us!
>
> donald
>
> On Wed, Nov 1, 2017 at 2:31 PM, Jeff Tantsura <jefftant at gmail.com> wrote:
> > Donald,
> >
> > Is it?
> > In my previous life. I had 5k VRFs supported with many live deployments
> > around 2k.
> > Obviously edge routers is quite a different market, still...
> >
> > All things are relative...
> > Jeff
> >
> > On Wed, Nov 1, 2017 at 06:16 Donald Sharp <sharpd at cumulusnetworks.com>
> > wrote:
> >>
> >> Jay -
> >>
> >> There is no hard limit.  Having said that I am not aware of serious
> >> testing beyond like 64 vrf's.  But that is allot of vrf's to have to
> >> maintain at one time..
> >>
> >> donald
> >>
> >> On Tue, Oct 31, 2017 at 10:39 PM, Jay Chen <jchen1 at paloaltonetworks.com
> >
> >> wrote:
> >> > Is there a limit that the # of vrf can support for a single switch or
> >> > router
> >> > by using FRR?
> >> >
> >> >
> >> >
> >> > Thanks,
> >> >
> >> > Jay
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > dev mailing list
> >> > dev at lists.frrouting.org
> >> > https://lists.frrouting.org/listinfo/dev
> >> >
> >>
> >> _______________________________________________
> >> dev mailing list
> >> dev at lists.frrouting.org
> >> https://lists.frrouting.org/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev at lists.frrouting.org
> https://lists.frrouting.org/listinfo/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20171102/bf5365c9/attachment.html>


More information about the dev mailing list