|
Thanks What I'm looking to do is to gather
usage stats based on AS. I'm currently aggregating based on AS at the
border routers and doing no aggregation via Ntop, and I think that's
working out ok. One question I have is, is there a way to
keep the AS Info stats (RRD?) so that when the process gets restarted I don't
lose what's reported under Summary/AS Info? Thanks! From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burton Strauss 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. ----- From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hally 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
