<?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 Crash without reboot in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71629#M6489</link>
    <description>&lt;P&gt;Hello.&lt;/P&gt; &lt;P&gt;We have two RFS7000 with ~90 AP650 on 5.4.0.0-047R firmware.&lt;/P&gt; &lt;P&gt;Link ge1 on the APs doesn’t go down, and up time not goes to zero. But on Flash appears crash dump file with one line (mac-address vary) and useless as for understanding core dump.&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;%USER-0-EMERG: Unspec[4004]: rim: ASSERT FAIL [mgmt.c:515: sending management frame to AC-3F-A4-43-16-E2 when it is in [Roaming] state] Aborting…&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;And onother one strange line in log&lt;/P&gt; &lt;P&gt;%DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 20679) exited. Scheduling for restart.&lt;BR /&gt; &amp;nbsp;&lt;/P&gt; &lt;P&gt;Crashes appears every&amp;nbsp; 10-15 min on one of AP randomly.&lt;/P&gt; &lt;P&gt;Maybe someone had ершы problem?&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 30 Nov 2019 18:53:54 GMT</pubDate>
    <dc:creator>BigAlambic</dc:creator>
    <dc:date>2019-11-30T18:53:54Z</dc:date>
    <item>
      <title>Crash without reboot</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71629#M6489</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt; &lt;P&gt;We have two RFS7000 with ~90 AP650 on 5.4.0.0-047R firmware.&lt;/P&gt; &lt;P&gt;Link ge1 on the APs doesn’t go down, and up time not goes to zero. But on Flash appears crash dump file with one line (mac-address vary) and useless as for understanding core dump.&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;%USER-0-EMERG: Unspec[4004]: rim: ASSERT FAIL [mgmt.c:515: sending management frame to AC-3F-A4-43-16-E2 when it is in [Roaming] state] Aborting…&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;And onother one strange line in log&lt;/P&gt; &lt;P&gt;%DAEMON-1-ALERT: init: process '/usr/sbin/rim -d' (pid 20679) exited. Scheduling for restart.&lt;BR /&gt; &amp;nbsp;&lt;/P&gt; &lt;P&gt;Crashes appears every&amp;nbsp; 10-15 min on one of AP randomly.&lt;/P&gt; &lt;P&gt;Maybe someone had ершы problem?&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Nov 2019 18:53:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71629#M6489</guid>
      <dc:creator>BigAlambic</dc:creator>
      <dc:date>2019-11-30T18:53:54Z</dc:date>
    </item>
    <item>
      <title>Re: Crash without reboot</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71630#M6490</link>
      <description>&lt;P&gt;You are on super old firmware, upgrade is recommended.&amp;nbsp; I believe that fw v:5.8.5 is last firmware for rfs7k.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2019 23:41:08 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71630#M6490</guid>
      <dc:creator>RobertZ</dc:creator>
      <dc:date>2019-12-02T23:41:08Z</dc:date>
    </item>
    <item>
      <title>Re: Crash without reboot</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71631#M6491</link>
      <description>&lt;P&gt;As Rob detailed, you are on very old firmware and strongly advise upgrading to the last firmware release for the EOSL RFS7000, which is &lt;STRONG&gt;v5.8.5.1-003R&lt;/STRONG&gt;. RIM stands for “&lt;STRONG&gt;Radio Interface Module&lt;/STRONG&gt;” and there have been a few fixes to RIM since v5.4.x.x:&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Once upgrade as been completed, you can delete the crash files on the devices using the CLI command from the RFS7000:&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;&lt;STRONG&gt;enable &lt;/STRONG&gt;[enter]&lt;/P&gt; &lt;P&gt;&lt;STRONG&gt;remote-debug clear-crash-info rf-domain xxxxx&lt;/STRONG&gt; [enter] (x represents rf-domain name)&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 03:20:37 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71631#M6491</guid>
      <dc:creator>Christopher_Fra</dc:creator>
      <dc:date>2019-12-04T03:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: Crash without reboot</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71632#M6492</link>
      <description>&lt;P&gt;Thanks for reply.&lt;/P&gt; &lt;P&gt;Agree, it’s high time for upgrade.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Dec 2019 13:26:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/crash-without-reboot/m-p/71632#M6492</guid>
      <dc:creator>BigAlambic</dc:creator>
      <dc:date>2019-12-04T13:26:58Z</dc:date>
    </item>
  </channel>
</rss>

