A user of a NetFlow reporting tool shouldn’t concern him or herself with whether or not the router or switch is exporting ingress, egress or both on a specific interface. Proper design of the NetFlow Analysis program should take this into account for the end user. Many NetFlow Analyzers exaggerate traffic if both ingress and egress is enabled. This can cause duplication of data and ultimately lead to trends that exaggerate the truth!

In truth, V6 of Scrutinizer in some configurations could duplicate but, this has been fixed in v7. Many NetFlow solutions still suffer from this problem. Some NetFlow products jump on board to support the latest NetFlow technologies but, lack the discipline to backup and fix issues that the customer will come to realize after they have purchase. Ingress and Egress flows is one of those issues that must be dealt with properly. Ultimately, chasing new features in lieu of fixing existing issues can lead to

consumer frustration.

frustratedCustomer
I believe all vendors including Plixer can learn from this mistake. Good software needs a solid foundation.

flowDirection

Notice above that Scrutinizer detects flow direction and dynamically
switches from displaying inbound or outBound utilization using ingress or egress flows based on what is currently being received from the interface. We feel it has been engineered very well.

Why are ingress and egress flow exports so important?  You should read this blog on WAN optimization with Cisco WAAS.

Mike Patterson author pic

Michael

Michael is one of the Co-founders and the former product manager for Scrutinizer. He enjoys many outdoor winter sports and often takes videos when he is snowmobiling, ice fishing or sledding with his kids. Cold weather and lots of snow make the best winters as far as he is concerned. Prior to starting Somix and Plixer, Mike worked in technical support at Cabletron Systems, acquired his Novell CNE and then moved to the training department for a few years. While in training he finished his Masters in Computer Information Systems from Southern New Hampshire University and then left technical training to pursue a new skill set in Professional Services. In 1998 he left the 'Tron' to start Somix which later became Plixer.

Related

Big Data

Sankey Flow Graph

One of the greatest benefits of NetFlow collection for traffic analysis, is we’re provided with the ability to visualize the…

Leave a Reply