[c-nsp] Usage Billing w/ Netflow / Implementation Pitfalls

Łukasz Bromirski lukasz at bromirski.net
Sat Jun 7 15:19:00 EDT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Simon Leinen wrote:
| Peter Rathlev writes:
|>> Think I'll see any issues from turning on the exports?
|
|> It shouldn't have any impact on the hardware forwarding of the box,
|> but the export uses some CPU on the MSFC.
|
| Note that in newer NDE implementations, most of the work is done by
| the Sup (SP), not the MSFC.

Technically speaking, MSFC is a daughterboard holding both SP and RP.

Whether SP or RP is doing the export, is another story.

Starting from 12.2(18)SXE, Netflow v5/v9 is done via SP. Additionally,
6708-10GE CPU is doing the Netflow export by itself. For the
linecards with DFC (excluding 6708-10GE) the export is managed by
RP.

| At least on the Sup720, but I assume this is the same for the Sup32.

The architecture itself is identical, minus the fact that the Sup32
doesn't support linecards with DFCs.

And BTW, starting from 12.2(33)SXH you can use 'mls exclude acl-deny'
to skip creating flows for denied traffic - which can spare some space
in PFC/DFC.

- --
"Don't expect me to cry for all the     |               Łukasz Bromirski
~ reasons you had to die" -- Kurt Cobain |    http://lukasz.bromirski.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhK3yQACgkQLw97dwC8RwNduACgup9EBec1fw6yEGLD/N4eLVTo
FwEAn2ntwprVh4cpgV8Ztz2TQktRwmkG
=2sc3
-----END PGP SIGNATURE-----


More information about the cisco-nsp mailing list