<?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 S-Series with &amp;quot;Fuji RX MAIN&amp;quot; errors seen in the Logs in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/s-series-with-quot-fuji-rx-main-quot-errors-seen-in-the-logs/m-p/47802#M478</link>
    <description>Article ID: 13512 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
"FUJI RX MAIN" errors seen in the 'show support' output's logging buffer and messageLog sections. &lt;BR /&gt;
&lt;BR /&gt;
For example:&amp;lt;163&amp;gt;Oct 22 21:43:48 10.1.232.7 Fuji[1.tNimIntr]Fuji RX MAIN intr:&lt;BR /&gt;
Fuji=0, Adr=0, Reg=0x00200040&lt;BR /&gt;
&amp;lt;163&amp;gt;Oct 22 21:44:55 10.1.232.7 Fuji[1.tNimIntr]Fuji RX MAIN intr:&lt;BR /&gt;
Fuji=0, Adr=0, Reg=0x00200040This is not known to cause performance issues. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Upgrade to firmware 7.21.02.0002 or higher.&lt;BR /&gt;
&lt;A href="https://extranet.enterasys.com/downloads/Pages/S.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;Release notes&lt;/A&gt; state, in the 'Firmware Changes and Enhancements' section:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Platform&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;If ports are receiving traffic while their MAC chip is being initialized the MAC may mishandle these packets and cause errors similar to "1. Fuji RX MAIN intr: Fuji=8, Adr=0, Reg=0x00200040", "2. Fuji MAC MAIN intr: Fuji=0, Adr=0, Reg=0x00080000", "3. MEM_FAIL interrupt occurred on chip" (which resets blade), or one of several bcmstrat memory system parity errors sometimes reported as "bcmStrat[3.bcmDPC]unit 0 (null) asserted ". The "parity" and "null" messages are displayed constantly and result in high CPU utilization.&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
If the issue persists after upgrade, please &lt;A href="http://www.enterasys.com/support/contact-support.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;contact the GTAC&lt;/A&gt; for assistance.</description>
    <pubDate>Tue, 03 Dec 2013 01:50:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-12-03T01:50:00Z</dc:date>
    <item>
      <title>S-Series with "Fuji RX MAIN" errors seen in the Logs</title>
      <link>https://community.extremenetworks.com/t5/faqs/s-series-with-quot-fuji-rx-main-quot-errors-seen-in-the-logs/m-p/47802#M478</link>
      <description>Article ID: 13512 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
S-Series &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
"FUJI RX MAIN" errors seen in the 'show support' output's logging buffer and messageLog sections. &lt;BR /&gt;
&lt;BR /&gt;
For example:&amp;lt;163&amp;gt;Oct 22 21:43:48 10.1.232.7 Fuji[1.tNimIntr]Fuji RX MAIN intr:&lt;BR /&gt;
Fuji=0, Adr=0, Reg=0x00200040&lt;BR /&gt;
&amp;lt;163&amp;gt;Oct 22 21:44:55 10.1.232.7 Fuji[1.tNimIntr]Fuji RX MAIN intr:&lt;BR /&gt;
Fuji=0, Adr=0, Reg=0x00200040This is not known to cause performance issues. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution&lt;/B&gt;&lt;BR /&gt;
Upgrade to firmware 7.21.02.0002 or higher.&lt;BR /&gt;
&lt;A href="https://extranet.enterasys.com/downloads/Pages/S.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;Release notes&lt;/A&gt; state, in the 'Firmware Changes and Enhancements' section:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;Platform&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;If ports are receiving traffic while their MAC chip is being initialized the MAC may mishandle these packets and cause errors similar to "1. Fuji RX MAIN intr: Fuji=8, Adr=0, Reg=0x00200040", "2. Fuji MAC MAIN intr: Fuji=0, Adr=0, Reg=0x00080000", "3. MEM_FAIL interrupt occurred on chip" (which resets blade), or one of several bcmstrat memory system parity errors sometimes reported as "bcmStrat[3.bcmDPC]unit 0 (null) asserted ". The "parity" and "null" messages are displayed constantly and result in high CPU utilization.&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
If the issue persists after upgrade, please &lt;A href="http://www.enterasys.com/support/contact-support.aspx" target="_blank" rel="nofollow noreferrer noopener"&gt;contact the GTAC&lt;/A&gt; for assistance.</description>
      <pubDate>Tue, 03 Dec 2013 01:50:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/s-series-with-quot-fuji-rx-main-quot-errors-seen-in-the-logs/m-p/47802#M478</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-12-03T01:50:00Z</dc:date>
    </item>
  </channel>
</rss>

