<?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: Scrutinizer v7 supports Huawei-3Com NetStream packets</title>
	<atom:link href="http://www.plixer.com/blog/scrutinizer/scrutinizer-v7-supports-huawei-3com-netstream-packets/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.plixer.com/blog/scrutinizer/scrutinizer-v7-supports-huawei-3com-netstream-packets/</link>
	<description>The NetFlow &#38; sFlow Reporting Resource</description>
	<lastBuildDate>Wed, 17 Mar 2010 14:59:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Messed Up Interface names in Scrutinizer - NetFlow &#38; sFlow Network Monitoring - Systrax</title>
		<link>http://www.plixer.com/blog/scrutinizer/scrutinizer-v7-supports-huawei-3com-netstream-packets/comment-page-1/#comment-14946</link>
		<dc:creator>Messed Up Interface names in Scrutinizer - NetFlow &#38; sFlow Network Monitoring - Systrax</dc:creator>
		<pubDate>Thu, 18 Feb 2010 13:31:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.plixer.com/blog/?p=6727#comment-14946</guid>
		<description>[...] actually ‘58’.  From here we were able to map to the correct interface name.  We modified the Huawei script to work with the new OID scheme and [...]</description>
		<content:encoded><![CDATA[<p>[...] actually ‘58’.  From here we were able to map to the correct interface name.  We modified the Huawei script to work with the new OID scheme and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
