[c-nsp] Cheap BGP router for ~20k prefixes

[Robert Hass]

Hi
Can you give some URL to recommended ESXi tweaking ?
Or just write some recommendations here. I'm happy to test CSR on my
configuration
but I also would like apply tweaking tips first.

Rob


On Wed, May 6, 2015 at 11:17 PM, Pshem Kowalczyk <pshem.k at gmail.com> wrote:

> We've just started to evaluate the CSR1000V as a traffic-carrying router.
> So far we've pushed about 2.2Gb/s through it with no problems. When it
> comes to PPS - we're doing about 450k. The way the load shapes seems to
> indicate that the box should be able to handle about 5Gb/s using the APPX
> licence. Currently we run it on ESX and implemented all the Cisco suggested
> tweaking (in order to get better performance out of it), that roughly
> doubled the performance over the default settings. The devices are
> MPLS-enabled and integrated into our core and do only packet forwarding
> (between IP and MPLS).
> We didn't try VM-FEX just yet (that's suppose to significantly increase the
> PPS).  The physical infrastructure they run on - Cisco UCS, B200M3 blade.
>
> kind regards
> Pshem
>
>
> On Wed, 6 May 2015 at 00:58 Mark Tinka <mark.tinka at seacom.mu> wrote:
>
> >
> >
> > On 5/May/15 14:52, Phil Mayers wrote:
> > >
> > >
> > > Yes. I can't remember where, but I have the impression either the CSR
> > > or vMX had oddly high forwarding latency, even accounting for the fact
> > > it's "just software".
> >
> > Right - I can't recall whether it was on c-nsp or NANOG, but I think the
> > issue was that someone was saying that using CSR1000v as an IP SLA probe
> > had some internal forwarding latency issues, compared to a classic
> > software-based router like a 2800, 3800 or 7200.
> >
> > I can't speak to how true this is. Our CSR1000v's are RR-only, and do
> > not forward any traffic. Handling of exception traffic has been great
> > with no issues so far, which would imply - at least for me, anyway -
> > that it should be fine as an IP SLA probe since the box terminates that
> > type of traffic, it does not transit it.
> >
> > Not sure whether the issue could be related to hardware, choice of
> > hypervisor, e.t.c.
> >
> > Mark.
> > _______________________________________________
> > 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/
> >
> _______________________________________________
> 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/
>