<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic DFE Netflow Not Working on Routed LAGs unless Physical Ports are Enabled in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/dfe-netflow-not-working-on-routed-lags-unless-physical-ports-are/m-p/47569#M463</link>
    <description>Article ID: 11093 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;BR /&gt;
&lt;/B&gt;Matrix N-Series DFE, firmware 5.31.17 through 6.02.03.0002 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured Netflow reporting for LAG ports. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Netflow does not report on flows routed across a LAG port. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;BR /&gt;
&lt;/B&gt;Upgrade to firmware 6.02.05.0001 or higher. &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://extranet.enterasys.com/Downloads/Pages/Platinum.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;Release notes&lt;/A&gt; state, in the 'Software Changes and Enhancements' section:NETFLOW&lt;BR /&gt;
Netflow now always reports routed flows ingressing a LAG&lt;BR /&gt;
port when the LAG port is enabled using the CLI command&lt;BR /&gt;
"set netflow port  enable". Previously you&lt;BR /&gt;
needed to enable the underlying physical ports that were&lt;BR /&gt;
members of the Link Aggregation Group.&lt;BR /&gt;
Pre-upgrade workaround: Enable both the LAG port, and the underlying physical ports, in Netflow. &lt;BR /&gt;
&lt;BR /&gt;
See also: &lt;A href="http://bit.ly/1c73inZ" target="_blank" rel="nofollow noreferrer noopener"&gt;7202&lt;/A&gt; and &lt;A href="http://bit.ly/1isOfO9" target="_blank" rel="nofollow noreferrer noopener"&gt;7485&lt;/A&gt;.</description>
    <pubDate>Tue, 03 Dec 2013 00:29:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-03T00:29:00Z</dc:date>
    <item>
      <title>DFE Netflow Not Working on Routed LAGs unless Physical Ports are Enabled</title>
      <link>https://community.extremenetworks.com/t5/faqs/dfe-netflow-not-working-on-routed-lags-unless-physical-ports-are/m-p/47569#M463</link>
      <description>Article ID: 11093 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;BR /&gt;
&lt;/B&gt;Matrix N-Series DFE, firmware 5.31.17 through 6.02.03.0002 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured Netflow reporting for LAG ports. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Netflow does not report on flows routed across a LAG port. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;BR /&gt;
&lt;/B&gt;Upgrade to firmware 6.02.05.0001 or higher. &lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://extranet.enterasys.com/Downloads/Pages/Platinum.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;Release notes&lt;/A&gt; state, in the 'Software Changes and Enhancements' section:NETFLOW&lt;BR /&gt;
Netflow now always reports routed flows ingressing a LAG&lt;BR /&gt;
port when the LAG port is enabled using the CLI command&lt;BR /&gt;
"set netflow port  enable". Previously you&lt;BR /&gt;
needed to enable the underlying physical ports that were&lt;BR /&gt;
members of the Link Aggregation Group.&lt;BR /&gt;
Pre-upgrade workaround: Enable both the LAG port, and the underlying physical ports, in Netflow. &lt;BR /&gt;
&lt;BR /&gt;
See also: &lt;A href="http://bit.ly/1c73inZ" target="_blank" rel="nofollow noreferrer noopener"&gt;7202&lt;/A&gt; and &lt;A href="http://bit.ly/1isOfO9" target="_blank" rel="nofollow noreferrer noopener"&gt;7485&lt;/A&gt;.</description>
      <pubDate>Tue, 03 Dec 2013 00:29:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/dfe-netflow-not-working-on-routed-lags-unless-physical-ports-are/m-p/47569#M463</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-03T00:29:00Z</dc:date>
    </item>
  </channel>
</rss>

