[c-nsp] Sup2T - poor netflow performance

Gert Doering gert at greenie.muc.de
Wed Mar 27 08:59:50 EDT 2013


Hi,

On Wed, Mar 27, 2013 at 12:50:39PM +0100, Jiri Prochazka wrote:
> I'll try this today and will let you know the result. I thought the 
> majority of CPU usage is consumed by 'match' statements, so I have 
> already tried just 'match source ip' and 'match destination ip', which 
> had no effect.

"match" should be relevant for "setting up the flow in hardware".

"collect" is "when exporting the flow from hardware, what other data do
we need to collect for the final export packet" - like source-AS, which
is *then* looked up in the BGP table.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
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: not available
Type: application/pgp-signature
Size: 305 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20130327/861c41ec/attachment.sig>


More information about the cisco-nsp mailing list