[c-nsp] Nexus 3064 BGP Scalability

[Mike Hammett]

By route filters, I mean an ACL applied against received and advertised routes. I'm not sure off of the top of my head the terminology Cisco uses. 




----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Paul" <paul at gtcomm.net> 
To: "Mike Hammett" <cisco-nsp at ics-il.net>, cisco-nsp at puck.nether.net 
Sent: Saturday, January 9, 2021 9:51:23 PM 
Subject: Re: [c-nsp] Nexus 3064 BGP Scalability 

It supports 8k ipv4 hosts, 16k ipv4 lpm, 8k ipv6 /64 or less, 8k ipv6 > 
/64 < 128 , 4k ipv6 hosts 

everything shared with the other table. Very limited in capacity but if 
you can fit within these limitations it's fine. 

What do you mean by route filters? (control plane stuff like route maps?) 


On 12/17/2020 10:15 AM, Mike Hammett wrote: 
> https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/scalability/935/cisco-nexus-3000-series-nx-os-verified-scalability-guide-935.html 
> 
> 
> 
> 
> If I'm reading this right (which I may not be), the 3064 can handle 16k IPv4 routes. It looks like it can handle 80k IPv6 routes. That should be more than enough for our needs as we only have a few hundred routes that we need at this time. 
> 
> 
> Any limitations for route filters? Any scalability issues with filters? 
> 
> 
> Any good reason not to use this in a low route count BGP environment? 
> 
> 
> 
> 
> ----- 
> Mike Hammett 
> Intelligent Computing Solutions 
> 
> Midwest Internet Exchange 
> 
> The Brothers WISP 
> 
> _______________________________________________ 
> cisco-nsp mailing list cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp 
> archive at http://puck.nether.net/pipermail/cisco-nsp/