[c-nsp] How many maximum routes does Cisco 2900 router support?
Robert Hass
robhass at gmail.com
Mon Jan 11 09:41:16 EST 2016
What was packet size during your test ?
I'm testing now with large packets and filled 1Gbps without problem having
70% CPU usage.
On Sun, Jan 10, 2016 at 11:38 AM, Nick Cutting <ncutting at edgetg.co.uk>
wrote:
> I have tested Pure routing on this platform a few times using iPerf on a
> LAN, and alternatively ookla speedtest on a 1 gig internet handoffs with
> just BGP default route
>
> max speeds are 335 Megabits per second - I cannot get it to go faster.
>
> The physical interfaces speeds are 1 gig
>
> Add NAT / Ipsec / NBAR etc and it goes way down.
> Also Netflow lite - seems to tax the CPU massively on these routers.
> Old-style netflow is fine
>
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> Blake Dunlap
> Sent: 10 January 2016 09:52
> To: Adam Greene
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] How many maximum routes does Cisco 2900 router
> support?
>
> The main I'd be worried about is not cpu average being high, but overruns
> - microbursts that just get tail dropped on the floor because the input
> buffer isn't processed fast enough and it fills. The pps capacity of the
> 2900s is quite low for the interface sizes they support.
>
> On Sat, Jan 9, 2016 at 6:56 AM, Adam Greene <maillist at webjogger.net>
> wrote:
> > Robert,
> >
> >
> >
> > Sure. Running Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M),
> Version 15.4(3)M2, RELEASE SOFTWARE (fc2).
> >
> >
> >
> > We are receiving a single full routing table, but we are also delivering
> it in its entirety to a downstream customer that is multi-homed.
> >
> >
> >
> >
> >
> > 344444333333333333333333333333333333333335555533333444443333
> >
> > 322222999994444400000666666666644444777770000055555222229999
> >
> > 100
> >
> > 90
> >
> > 80
> >
> > 70
> >
> > 60
> >
> > 50 *****
> >
> > 40 ********** ********** ************************
> >
> > 30 ************************************************************
> >
> > 20 ************************************************************
> >
> > 10 ************************************************************
> >
> > 0....5....1....1....2....2....3....3....4....4....5....5....6
> >
> > 0 5 0 5 0 5 0 5 0 5 0
> >
> > CPU% per second (last 60 seconds)
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 565555555464444655644457445554645444454554465555555545454554
> >
> > 071404042543363432374201616909481866807006905851274071868738
> >
> > 100
> >
> > 90
> >
> > 80
> >
> > 70 * *
> >
> > 60 * * * * * ** * **** * * *
> >
> > 50 *********** * ***** *** ****#*****************************
> >
> > 40 ######*#**#************#***#**#**#***#****#########***###**#
> >
> > 30 ############################################################
> >
> > 20 ############################################################
> >
> > 10 ############################################################
> >
> > 0....5....1....1....2....2....3....3....4....4....5....5....6
> >
> > 0 5 0 5 0 5 0 5 0 5 0
> >
> > CPU% per minute (last 60 minutes)
> >
> > * = maximum CPU% # = average CPU%
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > 7768676667979977986798986586977798879897767797766767757975668766679788
> > 87
> >
> >
> > 1916360723555961968895338147974596041336971997505126065922441236475457
> > 74
> >
> > 100 * ** * * * * * * *
> >
> > 90 * * ** ** *** * ** * * * *
> * ***
> >
> > 80 * * * ***** ** ***** * ** **** ***** **** * ** *
> ** ***
> >
> > 70 ** * * * **************** ********************* ** ** *** ** *
> *******
> >
> > 60 ************************* *******************************
> > **************
> >
> > 50
> > **********************************************************************
> > **
> >
> > 40
> > ************#**********************#********#*************************
> > **
> >
> > 30
> > ##*******################**#****#*###############*********############
> > ##
> >
> > 20
> > #####*##############################################***###############
> > ##
> >
> > 10
> > ######################################################################
> > ##
> >
> >
> 0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..
> >
> > 0 5 0 5 0 5 0 5 0 5 0 5
> 0
> >
> > CPU% per hour (last 72 hours)
> >
> > * = maximum CPU% # = average CPU%
> >
> >
> >
> > ROUTER#sh ip bgp sum
> >
> > 607161 network entries using 87431184 bytes of memory
> >
> > 607163 path entries using 48573040 bytes of memory
> >
> > 89290/89249 BGP path/bestpath attribute entries using 14286400 bytes
> > of memory
> >
> > 79236 BGP AS-PATH entries using 3440300 bytes of memory
> >
> > 477 BGP community entries using 23614 bytes of memory
> >
> > 0 BGP route-map cache entries using 0 bytes of memory
> >
> > 0 BGP filter-list cache entries using 0 bytes of memory
> >
> > BGP using 153754538 total bytes of memory
> >
> > BGP activity 7031767/6424603 prefixes, 7707260/7100097 paths, scan
> > interval 60 secs
> >
> >
> >
> > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ
> Up/Down State/PfxRcd
> >
> > <upstream> 4 12271 15142572 641068 82413333 0 0
> 29w0d 607147
> >
> > x.x.x.x 4 20208 144341 144319 82413371 0
> 0 13w0d 1
> >
> > x.x.x.x 4 20208 381849 420157 82413371 0
> 0 37w6d 1
> >
> > <downstream> 4 25669 230082 11237087 82413333 0 0 20w5d
> 1
> >
> >
> >
> > Thanks,
> >
> > Adam
> >
> >
> >
> >
> >
> >
> >
> > From: Robert Hass [mailto:robhass at gmail.com]
> > Sent: Friday, January 8, 2016 11:38 AM
> > To: Adam Greene <maillist at webjogger.net>
> > Cc: cisco-nsp at puck.nether.net
> > Subject: Re: [c-nsp] How many maximum routes does Cisco 2900 router
> support?
> >
> >
> >
> > On Fri, Jan 8, 2016 at 3:23 PM, Adam Greene <maillist at webjogger.net
> <mailto:maillist at webjogger.net> > wrote:
> >
> > Our 2921 with a full routing table, 2GB RAM, and around 60M aggregate
> > throughput hovers around 40-50% CPU utilization, with occasional
> > higher spikes. When we were pushing >100M aggregate through it, the
> > CPU was regularly spiking to near 100%.
> >
> >
> >
> > Can you put 'show proc cpu history' and what IOS you're running ? How
> many full-routing tables you're receiving from neighbors ?
> >
> >
> >
> >
> > We have another one with multiple BGP sessions, 512MB RAM, but only a
> > few actual routes. However, we are also running QoS policies on it,
> > including NBAR. When aggregate throughput gets up near 100M, CPU tends
> > to spike above 90%.
> >
> >
> >
> > NBAR is very CPU consuming operation.
> >
> >
> >
> > Rob
> >
> > _______________________________________________
> > 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/
>
> _______________________________________________
> 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/
>
More information about the cisco-nsp
mailing list