<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Free NetFlow Resources &#187; egress flows</title>
	<atom:link href="http://www.freenetflow.com/tag/egress-flows/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freenetflow.com</link>
	<description>NetFlow and sFlow guides and information</description>
	<lastBuildDate>Tue, 07 Sep 2010 00:55:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Best Practices when enabling Ingress and or Egress NetFlow</title>
		<link>http://www.freenetflow.com/netflow/best-practices-when-enabling-ingress-and-or-egress-netflow/</link>
		<comments>http://www.freenetflow.com/netflow/best-practices-when-enabling-ingress-and-or-egress-netflow/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 18:21:12 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[NetFlow]]></category>
		<category><![CDATA[NetFlow Analyzer]]></category>
		<category><![CDATA[Network Traffic Analysis]]></category>
		<category><![CDATA[Cisco WAAS]]></category>
		<category><![CDATA[egress flows]]></category>
		<category><![CDATA[netflow analysis]]></category>
		<category><![CDATA[NetFlow analyzers]]></category>
		<category><![CDATA[NetFlow products]]></category>
		<category><![CDATA[NetFlow reporting]]></category>
		<category><![CDATA[NetFlow solutions]]></category>
		<category><![CDATA[wan optimization]]></category>

		<guid isPermaLink="false">http://www.freenetflow.com/?p=3</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>A user of a <a title="learn more about NetFlow" href="http://en.wikipedia.org/wiki/Netflow" target="_blank">NetFlow</a> 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!</p>
<p>In truth, V6 of <a title="learn more about Scrutinizer" href="http://www.plixer.com/products/netflow-sflow/scrutinizer-netflow-sflow.php" target="_blank">Scrutinizer</a> 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.</p>
<p><a href="http://www.plixer.com/blog/wp-content/uploads/2009/11/frustratedCustomer.jpg"><img title="frustratedCustomer" src="http://www.plixer.com/blog/wp-content/uploads/2009/11/frustratedCustomer.jpg" alt="frustratedCustomer" width="450" height="291" /></a></p>
<p><span id="more-3"></span> <br />
I believe all vendors including Plixer can learn from this mistake. Good software needs a solid foundation.</p>
<p> <a href="http://www.plixer.com/blog/wp-content/uploads/2009/11/flowDirection.jpg"><img title="flowDirection" src="http://www.plixer.com/blog/wp-content/uploads/2009/11/flowDirection.jpg" alt="flowDirection" width="450" height="161" /></a></p>
<p>Notice above that Scrutinizer detects flow direction and dynamically<br />
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.</p>
<p>Why are ingress and egress flow exports so important?  You should read this blog on <a title="Wan optimization with Cisco WAAS" href="http://www.plixer.com/blog/netflow/best-practices-for-cisco-waas-reporting-using-netflow/" target="_blank">WAN optimization with Cisco WAAS</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freenetflow.com/netflow/best-practices-when-enabling-ingress-and-or-egress-netflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

