<div dir="ltr">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.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 1, 2017 at 12:28 PM, Donald Sharp <span dir="ltr"><<a href="mailto:sharpd@cumulusnetworks.com" target="_blank">sharpd@cumulusnetworks.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jeff -<br>
<br>
I thought I was pretty careful in my reply. I've seen testing of 64<br>
vrf's and I consider that many vrf's hard to operationally deploy. I<br>
don't disagree with you that some PE's will deploy thousands of VRF's.<br>
I was/am unwilling to claim vrf scaling until we get someone who<br>
actually tries it out and possibly runs into some data structure<br>
design flaw in FRR/kernel that we did not consider. I actually think<br>
it would be really interesting for someone to give it a shot, though!<br>
It would provide valuable feedback to us!<br>
<br>
donald<br>
<br>
On Wed, Nov 1, 2017 at 2:31 PM, Jeff Tantsura <<a href="mailto:jefftant@gmail.com">jefftant@gmail.com</a>> wrote:<br>
> Donald,<br>
><br>
> Is it?<br>
> In my previous life. I had 5k VRFs supported with many live deployments<br>
> around 2k.<br>
> Obviously edge routers is quite a different market, still...<br>
><br>
> All things are relative...<br>
> Jeff<br>
><br>
> On Wed, Nov 1, 2017 at 06:16 Donald Sharp <<a href="mailto:sharpd@cumulusnetworks.com">sharpd@cumulusnetworks.com</a>><br>
> wrote:<br>
>><br>
>> Jay -<br>
>><br>
>> There is no hard limit. Having said that I am not aware of serious<br>
>> testing beyond like 64 vrf's. But that is allot of vrf's to have to<br>
>> maintain at one time..<br>
>><br>
>> donald<br>
>><br>
>> On Tue, Oct 31, 2017 at 10:39 PM, Jay Chen <<a href="mailto:jchen1@paloaltonetworks.com">jchen1@paloaltonetworks.com</a>><br>
>> wrote:<br>
>> > Is there a limit that the # of vrf can support for a single switch or<br>
>> > router<br>
>> > by using FRR?<br>
>> ><br>
>> ><br>
>> ><br>
>> > Thanks,<br>
>> ><br>
>> > Jay<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > ______________________________<wbr>_________________<br>
>> > dev mailing list<br>
>> > <a href="mailto:dev@lists.frrouting.org">dev@lists.frrouting.org</a><br>
>> > <a href="https://lists.frrouting.org/listinfo/dev" rel="noreferrer" target="_blank">https://lists.frrouting.org/<wbr>listinfo/dev</a><br>
>> ><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> dev mailing list<br>
>> <a href="mailto:dev@lists.frrouting.org">dev@lists.frrouting.org</a><br>
>> <a href="https://lists.frrouting.org/listinfo/dev" rel="noreferrer" target="_blank">https://lists.frrouting.org/<wbr>listinfo/dev</a><br>
<br>
______________________________<wbr>_________________<br>
dev mailing list<br>
<a href="mailto:dev@lists.frrouting.org">dev@lists.frrouting.org</a><br>
<a href="https://lists.frrouting.org/listinfo/dev" rel="noreferrer" target="_blank">https://lists.frrouting.org/<wbr>listinfo/dev</a><br>
</blockquote></div><br></div>