This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Wireless
- ExtremeWireless (WiNG)
- RFS7000 All Status LED's Blinking
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
RFS7000 All Status LED's Blinking
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
12-18-2018 01:08 PM
Hi
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
this what is seen
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.
0| ddr2.c:829 configure_ddr2 Using SPD-derived 533MHz DDR parameters
0| ddr2.c:1238 start_init_ddr2 using 224/288 split
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.
RFS7000 version 5.8.4.0-034R
Booting from NAND image1
*** Switch reset because qchip watchdog timeout expired ***
0| ddr2.c:1238 start_init_ddr2 using 224/288 split
0| ddr2.c:1238 start_init_ddr2 using 224/288 split
but then the cli is unresponsive, no access via the GUI on the management port
the console port is set to 19200 8,N,1
After a while you hear the fans spin faster as if its going to try again
It looks like its trying to boot from the second image (NAND image 1 ) but it should be the image 5.8.5-016R,
How do I get it to beet the correct image ?
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
this what is seen
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.
0| ddr2.c:829 configure_ddr2 Using SPD-derived 533MHz DDR parameters
0| ddr2.c:1238 start_init_ddr2 using 224/288 split
BootOS (c) 2004-2016 Symbol Technologies, Inc. All rights reserved.
RFS7000 version 5.8.4.0-034R
Booting from NAND image1
*** Switch reset because qchip watchdog timeout expired ***
0| ddr2.c:1238 start_init_ddr2 using 224/288 split
0| ddr2.c:1238 start_init_ddr2 using 224/288 split
but then the cli is unresponsive, no access via the GUI on the management port
the console port is set to 19200 8,N,1
After a while you hear the fans spin faster as if its going to try again
It looks like its trying to boot from the second image (NAND image 1 ) but it should be the image 5.8.5-016R,
How do I get it to beet the correct image ?
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
12-27-2018 05:52 PM
UPDATE:
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.
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
Thanks to all that replied
Have a good New Year
Phil
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.
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
Thanks to all that replied
Have a good New Year
Phil
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
12-18-2018 04:21 PM
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:
enable [enter]
NX7500#show boot
--------------------------------------------------------------------------------
IMAGE BUILD DATE INSTALL DATE VERSION
--------------------------------------------------------------------------------
Primary 04/10/2018 23:31:36 11/21/2018 11:45:52 5.9.1.5-001R
Secondary 10/31/2018 17:07:38 11/15/2018 10:30:23 5.9.3.0-018R
--------------------------------------------------------------------------------
Current Boot : Secondary
Next Boot : Secondary
Software Fallback : Enabled
To change boot partition:
boot system xxxxxxx [enter] (x represents primary/secondary boot partition based on the above)
reload [enter]
RFS should boot into selected partition. If issue is still persistent, the device will need to be RMA'd.
enable [enter]
NX7500#show boot
--------------------------------------------------------------------------------
IMAGE BUILD DATE INSTALL DATE VERSION
--------------------------------------------------------------------------------
Primary 04/10/2018 23:31:36 11/21/2018 11:45:52 5.9.1.5-001R
Secondary 10/31/2018 17:07:38 11/15/2018 10:30:23 5.9.3.0-018R
--------------------------------------------------------------------------------
Current Boot : Secondary
Next Boot : Secondary
Software Fallback : Enabled
To change boot partition:
boot system xxxxxxx [enter] (x represents primary/secondary boot partition based on the above)
reload [enter]
RFS should boot into selected partition. If issue is still persistent, the device will need to be RMA'd.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
12-18-2018 02:42 PM
This could be a hardware issue, does the RFS eventually boot up or does it perpetually stay in boot loop?
if it boots up - get out put of cli command ' show sys boot'
if it boots up - get out put of cli command ' show sys boot'
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
12-18-2018 02:10 PM
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.
