Quick question Denny. Does this summary change also affect the way the IP Address groups can be used. In 1.0 I was able to view an aggregation of all interfaces based on IP Address groups. Now I can only view an IP group while looking at an interface.
I liked the aggregation capability because we use equal cost multipath links for each of our sites and the groups gave me a way to see all the traffic coming from a site. Is there a way I can "hack" this back in? For instance, specify two interfaces (across different nodes) instead of just one. I tried many different things but I've had no such luck.
--Dan
I don't think you can hack it. We are considering putting this back in for a future release.
What if we were to add back only the Top XX IP Address groups to the NetFlow Summary views? Would that solve your issue?
If I could then drill down into the group that would be great. The issue I have is determining our "bandwidth" hogs across the two equal paths.
OK. I'll see what we can do.
Another part of the reason they were pulled from Netflow 2.0 is that these resources were often subject to double-counting, depending on the network topology. Would it be acceptable if summary resources were made available, but required you to choose either a Netflow router or an interface on a Netflow router?
I would have to look at the results. Would it be possbile to display summary views based on IP Address groups as well?
We may be able to get summary views of IP Address groups into the next release, but there's no promise that the performance will be very scalable.
How was the TopXX views constructed? Was it possible to combine the netflow statistics from several netflow sources to get a better overview? I understand that could cause the data being calculated for twice, but configured correctly it would be very good to have.