<?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 RFS7000 All Status LED's Blinking in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81213#M7488</link>
    <description>Hi&lt;BR /&gt;
    Not sure what is happening on the RFS, we had some strange activity on the network, with the WIFI, the RFS7k went offline, on the front all the LED's are flashing, when the console cable is connected &lt;BR /&gt;
this what is seen &lt;BR /&gt;
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.&lt;BR /&gt;
&lt;BR /&gt;
 0| ddr2.c:829 configure_ddr2 Using SPD-derived 533MHz DDR parameters&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.&lt;BR /&gt;
RFS7000 version 5.8.4.0-034R&lt;BR /&gt;
Booting from NAND image1&lt;BR /&gt;
*** Switch reset because qchip watchdog timeout expired ***&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
&lt;BR /&gt;
but then the cli is unresponsive, no access via the GUI on the management port&lt;BR /&gt;
the console port is set to 19200 8,N,1&lt;BR /&gt;
After a while you hear the fans spin faster as if its going to try again&lt;BR /&gt;
It looks like its trying to boot from the second image (NAND image 1 ) but it should be the image 5.8.5-016R, &lt;BR /&gt;
How do I get it to beet the correct image ?</description>
    <pubDate>Tue, 18 Dec 2018 21:08:46 GMT</pubDate>
    <dc:creator>Phil_storey</dc:creator>
    <dc:date>2018-12-18T21:08:46Z</dc:date>
    <item>
      <title>RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81213#M7488</link>
      <description>Hi&lt;BR /&gt;
    Not sure what is happening on the RFS, we had some strange activity on the network, with the WIFI, the RFS7k went offline, on the front all the LED's are flashing, when the console cable is connected &lt;BR /&gt;
this what is seen &lt;BR /&gt;
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.&lt;BR /&gt;
&lt;BR /&gt;
 0| ddr2.c:829 configure_ddr2 Using SPD-derived 533MHz DDR parameters&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.&lt;BR /&gt;
RFS7000 version 5.8.4.0-034R&lt;BR /&gt;
Booting from NAND image1&lt;BR /&gt;
*** Switch reset because qchip watchdog timeout expired ***&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
&lt;BR /&gt;
but then the cli is unresponsive, no access via the GUI on the management port&lt;BR /&gt;
the console port is set to 19200 8,N,1&lt;BR /&gt;
After a while you hear the fans spin faster as if its going to try again&lt;BR /&gt;
It looks like its trying to boot from the second image (NAND image 1 ) but it should be the image 5.8.5-016R, &lt;BR /&gt;
How do I get it to beet the correct image ?</description>
      <pubDate>Tue, 18 Dec 2018 21:08:46 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81213#M7488</guid>
      <dc:creator>Phil_storey</dc:creator>
      <dc:date>2018-12-18T21:08:46Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81214#M7489</link>
      <description>Phil, from what I'm reading here, it sounds like the RFS has a problem that GTAC will need to diagnose.  This is not anything I've ever run into or heard of before.</description>
      <pubDate>Tue, 18 Dec 2018 22:10:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81214#M7489</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2018-12-18T22:10:58Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81215#M7490</link>
      <description>This could be a hardware issue, does the RFS eventually boot up or does it perpetually stay in boot loop? &lt;BR /&gt;
&lt;BR /&gt;
if it boots up - get out put of cli command ' show sys boot'</description>
      <pubDate>Tue, 18 Dec 2018 22:42:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81215#M7490</guid>
      <dc:creator>RobertZ</dc:creator>
      <dc:date>2018-12-18T22:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81216#M7491</link>
      <description>If System Status LED's 1 and 2 are alternating blinking green/amber, this is definitely a boot up error (device has an invalid checksum). If you have access to the CLI, after the error:&lt;BR /&gt;
&lt;BR /&gt;
enable [enter]&lt;BR /&gt;
&lt;BR /&gt;
NX7500#show boot&lt;BR /&gt;
--------------------------------------------------------------------------------&lt;BR /&gt;
   IMAGE      BUILD DATE       INSTALL DATE     VERSION&lt;BR /&gt;
--------------------------------------------------------------------------------&lt;BR /&gt;
 Primary        04/10/2018 23:31:36   11/21/2018 11:45:52   5.9.1.5-001R&lt;BR /&gt;
 Secondary   10/31/2018 17:07:38   11/15/2018 10:30:23   5.9.3.0-018R&lt;BR /&gt;
--------------------------------------------------------------------------------&lt;BR /&gt;
Current Boot    : Secondary&lt;BR /&gt;
Next Boot     : Secondary&lt;BR /&gt;
Software Fallback : Enabled&lt;BR /&gt;
&lt;BR /&gt;
To change boot partition:&lt;BR /&gt;
&lt;BR /&gt;
boot system xxxxxxx [enter] (x represents primary/secondary boot partition based on the above)&lt;BR /&gt;
reload [enter]&lt;BR /&gt;
&lt;BR /&gt;
RFS should boot into selected partition. If issue is still persistent, the device will need to be RMA'd.</description>
      <pubDate>Wed, 19 Dec 2018 00:21:31 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81216#M7491</guid>
      <dc:creator>Christopher_Fra</dc:creator>
      <dc:date>2018-12-19T00:21:31Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81217#M7492</link>
      <description>Hello Phil,&lt;BR /&gt;
&lt;BR /&gt;
As my colleagues stated, it's probably a hardware issue, but if you would like to try booting up into the secondary partition where 5.8.5 resides you can try the following:&lt;BR /&gt;
&lt;BR /&gt;
1 - Reboot the controller and as soon as the process starts, press and release the ESC key on your keyboard to get to the &lt;B&gt;boot&amp;gt;&lt;/B&gt; prompt&lt;BR /&gt;
2 - Run the following commands:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;boot&amp;gt;set boot 2&lt;BR /&gt;boot&amp;gt;reset             (this is the reload command in boot&amp;gt;)&lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Of course if 5.8.5 is in the primary partition then the command becomes:&lt;BR /&gt;
&lt;DIV class="threadCode"&gt;&lt;B&gt;code:&lt;/B&gt;&lt;PRE spellcheck="false"&gt;boot&amp;gt;set boot 1&lt;BR /&gt;boot&amp;gt;reset             &lt;BR /&gt;&lt;/PRE&gt;&lt;/DIV&gt;&lt;BR /&gt;
&lt;BR /&gt;
Test to see if the controller boots up into that image, but if still caught in boot loop then the unit needs to be RMA'd.</description>
      <pubDate>Wed, 19 Dec 2018 01:18:58 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81217#M7492</guid>
      <dc:creator>Christoph_S</dc:creator>
      <dc:date>2018-12-19T01:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81218#M7493</link>
      <description>Hi&lt;BR /&gt;
   and thankyou for the replies, I'm taking the RFS out of the rack and putting it on the bench&amp;lt; I will update later on the outcome&lt;BR /&gt;
Phil</description>
      <pubDate>Wed, 19 Dec 2018 17:02:23 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81218#M7493</guid>
      <dc:creator>Phil_storey</dc:creator>
      <dc:date>2018-12-19T17:02:23Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81219#M7494</link>
      <description>Hi&lt;BR /&gt;
   the unit would not boot,  but was showing this&lt;BR /&gt;
*** Switch reset because qchip watchdog timeout expired ***&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
&lt;BR /&gt;
decided to swop the memory module out, and it returned to the command prompt but as the memory was too fast it wouldn't boot but tried&lt;BR /&gt;
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.&lt;BR /&gt;
RFS7000 version 5.8.4.0-034R&lt;BR /&gt;
Booting from NAND image1&lt;BR /&gt;
 0| ddr2.c:675 configure_ddr2 Clamping DIMM 0 speed at 532MHz because errata prevents XLR from operating with it any faster than this&lt;BR /&gt;
 0| ddr2.c:829 configure_ddr2 Using SPD-derived 533MHz DDR parameters&lt;BR /&gt;
 0| ddr2.c:1238 start_init_ddr2 using 224/288 split&lt;BR /&gt;
&lt;BR /&gt;
I should have the replacement module hopefully by tomorrow. I will update this tread again once installed</description>
      <pubDate>Wed, 19 Dec 2018 19:39:16 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81219#M7494</guid>
      <dc:creator>Phil_storey</dc:creator>
      <dc:date>2018-12-19T19:39:16Z</dc:date>
    </item>
    <item>
      <title>Re: RFS7000 All Status LED's Blinking</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81220#M7495</link>
      <description>UPDATE:&lt;BR /&gt;
&lt;BR /&gt;
Fitted the replacement RAM today and the RFS7k lives. It booted first time, Config was all good, or so it seemed . Re-instated it to the LAN, but the cluster would not come up, If was doing my head in, then I walked away had a think, Firmware, the Primary had booted the old image, Rebooted with the new image and all was OK again.&lt;BR /&gt;
&lt;BR /&gt;
Just got to work out why the 2 client AP's in the remote location and not showing in the RFS, they did before the crash, but they are working and clients are connected, so not a major problem&lt;BR /&gt;
&lt;BR /&gt;
Thanks to all that replied &lt;BR /&gt;
Have a good New Year &lt;BR /&gt;
Phil</description>
      <pubDate>Fri, 28 Dec 2018 01:52:27 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/rfs7000-all-status-led-s-blinking/m-p/81220#M7495</guid>
      <dc:creator>Phil_storey</dc:creator>
      <dc:date>2018-12-28T01:52:27Z</dc:date>
    </item>
  </channel>
</rss>

