[c-nsp] SUP720's memory, looking at options..

Gert Doering gert at greenie.muc.de
Tue Jul 5 16:38:34 EDT 2016


On Tue, Jul 05, 2016 at 08:15:41PM +0000, Mack McBride wrote:
> The Sup6T is still TCAM limited.
> We are moving to ASR9Ks.

This was our plan, but right now the platform annoys me somewhat
(MAC accounting is not reliable, and no MAC addresses in netflow 
whatsoever - you want at least one of them if you peer at IXPs... - and
IOS XR train planning seems to be totally secret lore, like, why is
XR 6.0 for ASR9k totally different from XR 6.0 for NCS6k, but still given
the same version number [not mentioning the two releases of 6.0.1])

> But we have used the ASR1Ks where we need full netflow capture with great success.

Does ASR1k do netflow with src MAC?

I know it does MAC accounting, but limited to 512 entries - which is too
limited for larger IXPs (like DECIX).  I wonder how it would cope with
"more MACs" - like, do the first 512 addresses that show up correctly,
and ignore the rest, whether it can be tweaked to expire entries after
<x> minutes without traffic, or whether it's as bad and ill-documented 
as ASR9k...

> The port density and total throughput is not as high as the 6500 though.

Understood.  This is the problem with the 6500 - it's just too reliable,
too many ports, and so small money - hard to justify getting boxes with
less ports, less throughput for much more money.


USENET is *not* the non-clickable part of WWW!
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 291 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20160705/d1b4222d/attachment.sig>

More information about the cisco-nsp mailing list