<?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 I/G/C/B-Series with Failing Ports and &amp;quot;timeout draining packets&amp;quot; Error Messages in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/i-g-c-b-series-with-failing-ports-and-quot-timeout-draining/m-p/46911#M425</link>
    <description>Article ID: 13852 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
I-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
G-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
C5-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
C3-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
B5-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
B3-Series, firmware 6.42.02.0006 through 6.42.08.0007 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
One or more "timeout draining packets" errors seen in the current.log (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;); for example:&lt;BR /&gt;
&amp;lt;160&amp;gt;Apr 5 17:31:42 0.0.0.0-8 SIM[86228792]: broad_hpc_drv.c(2689) 219 %% ERROR: port 0:ge5: timeout draining packets (2377 cells remain) &lt;BR /&gt;
&lt;BR /&gt;
Corresponding ports fail to pass traffic, though the port is up and its status otherwise looks fine. &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;Note:&lt;/U&gt; This condition is typically detected by the txqmonitor function, which may then issue messages including &lt;BR /&gt;
"... Tx queue for interface &amp;lt;&lt;I&gt;port#&lt;/I&gt;&amp;gt; is in stalled mode". &lt;BR /&gt;
These txqmonitor messages can be helpful here because they report the affected port number in the conventional format. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Upgrade to firmware 6.42.09.0005 or higher.&lt;BR /&gt;
&lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;Release notes&lt;/A&gt; state, in the 'Firmware Changes and Enhancements' section: &lt;BR /&gt;
15297  Addressed an issue associated with the switch port state machine which could potentially cause device ports to lockup. &lt;BR /&gt;
&lt;BR /&gt;
Pre-upgrade workaround: Reboot the switch.</description>
    <pubDate>Thu, 05 Sep 2013 06:03:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-09-05T06:03:00Z</dc:date>
    <item>
      <title>I/G/C/B-Series with Failing Ports and "timeout draining packets" Error Messages</title>
      <link>https://community.extremenetworks.com/t5/faqs/i-g-c-b-series-with-failing-ports-and-quot-timeout-draining/m-p/46911#M425</link>
      <description>Article ID: 13852 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
I-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
G-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
C5-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
C3-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
B5-Series, firmware 6.42.02.0006 through 6.42.08.0007&lt;BR /&gt;
B3-Series, firmware 6.42.02.0006 through 6.42.08.0007 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
One or more "timeout draining packets" errors seen in the current.log (&lt;A href="http://bit.ly/1pOU3VK" target="_blank" rel="nofollow noreferrer noopener"&gt;5487&lt;/A&gt;); for example:&lt;BR /&gt;
&amp;lt;160&amp;gt;Apr 5 17:31:42 0.0.0.0-8 SIM[86228792]: broad_hpc_drv.c(2689) 219 %% ERROR: port 0:ge5: timeout draining packets (2377 cells remain) &lt;BR /&gt;
&lt;BR /&gt;
Corresponding ports fail to pass traffic, though the port is up and its status otherwise looks fine. &lt;BR /&gt;
&lt;BR /&gt;
&lt;U&gt;Note:&lt;/U&gt; This condition is typically detected by the txqmonitor function, which may then issue messages including &lt;BR /&gt;
"... Tx queue for interface &amp;lt;&lt;I&gt;port#&lt;/I&gt;&amp;gt; is in stalled mode". &lt;BR /&gt;
These txqmonitor messages can be helpful here because they report the affected port number in the conventional format. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Upgrade to firmware 6.42.09.0005 or higher.&lt;BR /&gt;
&lt;A href="http://extranet.enterasys.com/downloads/" target="_blank" rel="nofollow noreferrer noopener"&gt;Release notes&lt;/A&gt; state, in the 'Firmware Changes and Enhancements' section: &lt;BR /&gt;
15297  Addressed an issue associated with the switch port state machine which could potentially cause device ports to lockup. &lt;BR /&gt;
&lt;BR /&gt;
Pre-upgrade workaround: Reboot the switch.</description>
      <pubDate>Thu, 05 Sep 2013 06:03:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/i-g-c-b-series-with-failing-ports-and-quot-timeout-draining/m-p/46911#M425</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-09-05T06:03:00Z</dc:date>
    </item>
  </channel>
</rss>

