<?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: Wireshark needs templates to decipher Cisco NetFlow v9</title>
	<atom:link href="http://www.plixer.com/blog/general/wireshark-needs-templates-to-decipher-netflow-v9/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.plixer.com/blog/general/wireshark-needs-templates-to-decipher-netflow-v9/</link>
	<description>The NetFlow &#38; sFlow Reporting Resource</description>
	<lastBuildDate>Sat, 13 Mar 2010 23:00:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Nate</title>
		<link>http://www.plixer.com/blog/general/wireshark-needs-templates-to-decipher-netflow-v9/comment-page-1/#comment-12403</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.plixer.com/blog/?p=4104#comment-12403</guid>
		<description>Good question. I haven&#039;t seen a PCAP from a Nexus yet, but I do know that it should be exporting the standard NetFlow v9 template. So I would guess that it would still be considered CFLOW.

I know that some devices can also export a template as infrequently as once every 30 mins, so it might take a few minutes before Wireshark gets the template to decode those packets.</description>
		<content:encoded><![CDATA[<p>Good question. I haven&#8217;t seen a PCAP from a Nexus yet, but I do know that it should be exporting the standard NetFlow v9 template. So I would guess that it would still be considered CFLOW.</p>
<p>I know that some devices can also export a template as infrequently as once every 30 mins, so it might take a few minutes before Wireshark gets the template to decode those packets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dennis</title>
		<link>http://www.plixer.com/blog/general/wireshark-needs-templates-to-decipher-netflow-v9/comment-page-1/#comment-12399</link>
		<dc:creator>Dennis</dc:creator>
		<pubDate>Wed, 13 Jan 2010 18:36:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.plixer.com/blog/?p=4104#comment-12399</guid>
		<description>Nate,  thanks for the good information.  I&#039;m seeing this &quot;no template found&quot; on a v9 capture from a Nexus 7000 router even after a 5 min capture as you&#039;ve suggested.  Any ideas?  Is there a another decode than cflow in Wireshark I should be using?

-Dennis</description>
		<content:encoded><![CDATA[<p>Nate,  thanks for the good information.  I&#8217;m seeing this &#8220;no template found&#8221; on a v9 capture from a Nexus 7000 router even after a 5 min capture as you&#8217;ve suggested.  Any ideas?  Is there a another decode than cflow in Wireshark I should be using?</p>
<p>-Dennis</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NetFlow v9 vs. NetFlow v5 - NetFlow &#38; sFlow Network Monitoring - Systrax Blog</title>
		<link>http://www.plixer.com/blog/general/wireshark-needs-templates-to-decipher-netflow-v9/comment-page-1/#comment-4167</link>
		<dc:creator>NetFlow v9 vs. NetFlow v5 - NetFlow &#38; sFlow Network Monitoring - Systrax Blog</dc:creator>
		<pubDate>Thu, 18 Jun 2009 13:07:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.plixer.com/blog/?p=4104#comment-4167</guid>
		<description>[...] NetFlow v5 is by far the most popular version of NetFlow. I would say over 90% of our customer base uses NetFlow v5. The NetFlow v5 packet format is fixed and is always the same and ultimately easy to decipher for most NetFlow collection and network traffic reporting packages. All flows are calculated when they come into an interface (i.e. inBound). OutBound traffic is reported using inBound flows from the other interfaces. Because of this, it is generally advised that NetFlow v5 be enabled on all interfaces of the device, else outBound utilization on some interfaces may be understated. NetFlow v9 is gaining market share, albeit slowly, and isn&#8217;t as deterministic as NetFlow v5. NetFlow v9 templates are the big differentiators here. Read what happens when WireShark doesn’t receive a template before receiving the NetFlow v9 packets. [...]</description>
		<content:encoded><![CDATA[<p>[...] NetFlow v5 is by far the most popular version of NetFlow. I would say over 90% of our customer base uses NetFlow v5. The NetFlow v5 packet format is fixed and is always the same and ultimately easy to decipher for most NetFlow collection and network traffic reporting packages. All flows are calculated when they come into an interface (i.e. inBound). OutBound traffic is reported using inBound flows from the other interfaces. Because of this, it is generally advised that NetFlow v5 be enabled on all interfaces of the device, else outBound utilization on some interfaces may be understated. NetFlow v9 is gaining market share, albeit slowly, and isn&#8217;t as deterministic as NetFlow v5. NetFlow v9 templates are the big differentiators here. Read what happens when WireShark doesn’t receive a template before receiving the NetFlow v9 packets. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
