<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Best Practices when enabling Ingress and or Egress NetFlow</title>
	<atom:link href="http://www.plixer.com/blog/netflow/best-practices-when-enabling-ingress-and-or-egress-netflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.plixer.com/blog/netflow/best-practices-when-enabling-ingress-and-or-egress-netflow/</link>
	<description>The NetFlow &#38; sFlow Reporting Resource</description>
	<lastBuildDate>Tue, 09 Mar 2010 18:22:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: NetFlow Configuration Cheat &#8211; Interface configs killing you? Let us help! - NetFlow &#38; sFlow Network Monitoring - Systrax</title>
		<link>http://www.plixer.com/blog/netflow/best-practices-when-enabling-ingress-and-or-egress-netflow/comment-page-1/#comment-9905</link>
		<dc:creator>NetFlow Configuration Cheat &#8211; Interface configs killing you? Let us help! - NetFlow &#38; sFlow Network Monitoring - Systrax</dc:creator>
		<pubDate>Fri, 04 Dec 2009 15:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.plixer.com/blog/?p=6908#comment-9905</guid>
		<description>[...] NetFlow export enabled on his Cisco 3800 routers. When I was explaining the concept of using the ip flow ingress command in enabling NetFlow per interface, he [...]</description>
		<content:encoded><![CDATA[<p>[...] NetFlow export enabled on his Cisco 3800 routers. When I was explaining the concept of using the ip flow ingress command in enabling NetFlow per interface, he [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
