|
Basically, it's what YOU need it to be to meet YOUR
needs.
Aggregating at the router (netflow collector, technically)
reduces the amount of bandwidth consumed for monitoring (and reduces the load on
ntop). But it's more difficult (sometimes) to change the collector
options.
Aggregating in ntop is easy to change (just flip the
dropdown). But it means ntop is processing each flow.
Whichever way you aggregate, that's the level of detail
ntop reports. No drill-down, etc. just the aggregated
data.
-----Burton
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hally Sent: Wednesday, March 09, 2005 4:19 PM To: '[email protected]' Subject: [Ntop] Netflow aggregation Hello
All, Can someone tell me what the
benefits of the different netflow aggregation options are? Is it better to
not aggregate at the router, and then set up aggregation on Ntop, or should they
'line up', meaning, set AS aggregation on the router and also in
ntop? I guess which type of aggregation
you choose will also effect the type of reporting that Ntop is going to produce,
correct? Thanks in
advance! |
_______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
