<?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 SecureStack/G/D-Series f/w x.01.06.0007 Policy Consumes the First Packet in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/securestack-g-d-series-f-w-x-01-06-0007-policy-consumes-the/m-p/41009#M25</link>
    <description>Article ID: 10734 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, firmware 1.01.06.0007 and lower&lt;BR /&gt;
SecureStack C2, firmware 5.01.06.0007 and lower&lt;BR /&gt;
SecureStack B3, firmware 1.01.06.0007 and lower&lt;BR /&gt;
SecureStack B2, firmware 4.01.06.0007 and lower&lt;BR /&gt;
G-Series, firmware 1.00.03.0002 and lower&lt;BR /&gt;
D-Series, firmware 1.00.04.0001 and lower &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured Policy on a port. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
The first (possibly ARP) packet ingressing the switch port is lost, not being forwarded for switching or routing.&lt;BR /&gt;
The remainder of ingressed traffic is treated as configured per the policy. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
The first ingressed packet attempting to pass through the policy is consumed by the CPU. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
For the C3, upgrade to firmware 1.02.01.0004 or higher.&lt;BR /&gt;
For the C2, upgrade to firmware 5.02.01.0006 or higher.&lt;BR /&gt;
For the B3, upgrade to firmware 1.02.01.0004 or higher.&lt;BR /&gt;
For the B2, upgrade to firmware 4.02.01.0006 or higher.&lt;BR /&gt;
For the G-Series, upgrade to firmware 1.02.00.0043 or higher.&lt;BR /&gt;
For the D-Series, upgrade to firmware 6.03.01.0008 or higher. &lt;BR /&gt;
&lt;BR /&gt;
Release notes state, in the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Firmware Changes and Enhancements&lt;/PRE&gt;&lt;/DIV&gt;' section:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;10274&lt;/PRE&gt;&lt;/DIV&gt; &amp;amp; &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;10183&lt;/PRE&gt;&lt;/DIV&gt;   &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Corrected an issue where the first packet through the switch is dropped with policy applied, subsequent packet transmissions are successful.&lt;/PRE&gt;&lt;/DIV&gt; &lt;BR /&gt;
&lt;BR /&gt;
Pre-upgrade workaround:&lt;BR /&gt;
This symptom will recur each time the relevant Source Address Table (SAT) entry times out, as it is being relearned. One possible workaround is to increase the MAC Agetime ('&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set mac agetime...&lt;/PRE&gt;&lt;/DIV&gt;', '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show mac agetime&lt;/PRE&gt;&lt;/DIV&gt;') from its default of 300 seconds to a larger value - as high as one million seconds (about 11.5 days). Be aware that, depending upon a number of other factors - including but not restricted to node density, user mobility, and static LAG failover - doing so may have unintended side-effects.</description>
    <pubDate>Sat, 28 Dec 2013 02:50:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-28T02:50:00Z</dc:date>
    <item>
      <title>SecureStack/G/D-Series f/w x.01.06.0007 Policy Consumes the First Packet</title>
      <link>https://community.extremenetworks.com/t5/faqs/securestack-g-d-series-f-w-x-01-06-0007-policy-consumes-the/m-p/41009#M25</link>
      <description>Article ID: 10734 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
SecureStack C3, firmware 1.01.06.0007 and lower&lt;BR /&gt;
SecureStack C2, firmware 5.01.06.0007 and lower&lt;BR /&gt;
SecureStack B3, firmware 1.01.06.0007 and lower&lt;BR /&gt;
SecureStack B2, firmware 4.01.06.0007 and lower&lt;BR /&gt;
G-Series, firmware 1.00.03.0002 and lower&lt;BR /&gt;
D-Series, firmware 1.00.04.0001 and lower &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured Policy on a port. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
The first (possibly ARP) packet ingressing the switch port is lost, not being forwarded for switching or routing.&lt;BR /&gt;
The remainder of ingressed traffic is treated as configured per the policy. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
The first ingressed packet attempting to pass through the policy is consumed by the CPU. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
For the C3, upgrade to firmware 1.02.01.0004 or higher.&lt;BR /&gt;
For the C2, upgrade to firmware 5.02.01.0006 or higher.&lt;BR /&gt;
For the B3, upgrade to firmware 1.02.01.0004 or higher.&lt;BR /&gt;
For the B2, upgrade to firmware 4.02.01.0006 or higher.&lt;BR /&gt;
For the G-Series, upgrade to firmware 1.02.00.0043 or higher.&lt;BR /&gt;
For the D-Series, upgrade to firmware 6.03.01.0008 or higher. &lt;BR /&gt;
&lt;BR /&gt;
Release notes state, in the '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Firmware Changes and Enhancements&lt;/PRE&gt;&lt;/DIV&gt;' section:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;10274&lt;/PRE&gt;&lt;/DIV&gt; &amp;amp; &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;10183&lt;/PRE&gt;&lt;/DIV&gt;   &lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Corrected an issue where the first packet through the switch is dropped with policy applied, subsequent packet transmissions are successful.&lt;/PRE&gt;&lt;/DIV&gt; &lt;BR /&gt;
&lt;BR /&gt;
Pre-upgrade workaround:&lt;BR /&gt;
This symptom will recur each time the relevant Source Address Table (SAT) entry times out, as it is being relearned. One possible workaround is to increase the MAC Agetime ('&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;set mac agetime...&lt;/PRE&gt;&lt;/DIV&gt;', '&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;show mac agetime&lt;/PRE&gt;&lt;/DIV&gt;') from its default of 300 seconds to a larger value - as high as one million seconds (about 11.5 days). Be aware that, depending upon a number of other factors - including but not restricted to node density, user mobility, and static LAG failover - doing so may have unintended side-effects.</description>
      <pubDate>Sat, 28 Dec 2013 02:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/securestack-g-d-series-f-w-x-01-06-0007-policy-consumes-the/m-p/41009#M25</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-28T02:50:00Z</dc:date>
    </item>
  </channel>
</rss>

