cancel
Showing results for 
Search instead for 
Did you mean: 

Issues with Hidden SSID connectivity / Stuck Beacon?

michael_katzung
New Contributor II
I used to install Ruckus APs for one of Ruckus's bigdogs that uses ruckus aps in hotels (i've done a bunch of the training online, done wireless installs for 4+ years so I'm no expert like Mike, but not new to the subject). Anyways... I started a new job and am trying to get them to switch from using these terrible Engenius aps to using ruckus (since they are awesome).

I'm demoing a 7372 and having a few issues, and hoping to get some help here.

Basic config:
No Zone director
No Vlans
2.4 and 5ghz radios both set to the same SSID
Not broadcasting SSID
WPA2 PSK, AES
ACL to only allow approved MACs (Although the problems I am having I was having BEFORE I implemented this feature so that is unrelated AFAIK)

Issues I'm having, and how I've been working through them.

1) 5Ghz was giving me some invalid channel errors until I changed to 20mhz and set a static channel of 36. (Found that solution on the forums here).

2) 2.4 will work for a second few seconds after boot up, then stop broadcasting, INSSIDer records the MAC, and then the radio stops broadcasting. Cannot connect to SSID
I enable broadcasting of the SSID and it works fine, can connect, can see the SSID.
Switch back to hidden SSID, it's gone again.

3) Shut off 5 ghz radio, can suddenly connect to 2.4 after reboot. Connection appears to work fine for a few minutes but eventually I get limited connectivity that comes and goes.
Switching to static channel on 2.4 doesnt seem to help (Was worried this was a similar issue to the 5ghz.)

Absolutely stumped here guys... Never had any issues like this working with the 7363s...

Did I just get a Lemon AP?

Also, weird error messages in the logs, I've copied pasted below.

Nov 5 21:08:11 RuckusAP user.warn kernel: wifi0: 1347445 : stuck beacon (missed 11) scanning 0, syncbeacon 0, sc_beacons 1
Nov 5 21:08:12 RuckusAP user.warn kernel: NF Channel 2437 Chain 0 measured latest ctl:-101 ext:-50 capped median ctl:-101 ext:-55
Nov 5 21:08:12 RuckusAP user.warn kernel: NF Channel 2437 Chain 1 measured latest ctl:-100 ext:-50 capped median ctl:-99 ext:-55
Nov 5 21:08:12 RuckusAP user.warn kernel: NF Channel 2437 Chain 2 measured latest ctl:0 ext:0 capped median ctl:-55 ext:-55
Nov 5 21:08:12 RuckusAP user.warn kernel: wifi0: 1348679 : stuck beacon (missed 11) scanning 0, syncbeacon 0, sc_beacons 1
Nov 5 21:08:13 RuckusAP user.warn kernel: NF Channel 2437 Chain 0 measured latest ctl:-101 ext:-50 capped median ctl:-101 ext:-55
Nov 5 21:08:13 RuckusAP user.warn kernel: NF Channel 2437 Chain 1 measured latest ctl:-98 ext:-50 capped median ctl:-99 ext:-55
Nov 5 21:08:13 RuckusAP user.warn kernel: NF Channel 2437 Chain 2 measured latest ctl:0 ext:1 capped median ctl:-55 ext:-55
Nov 5 21:08:13 RuckusAP user.warn kernel: wifi0: 1349914 : stuck beacon (missed 11) scanning 0, syncbeacon 0, sc_beacons 1
Nov 5 21:08:14 RuckusAP user.warn kernel: NF Channel 2437 Chain 0 measured latest ctl:-98 ext:-50 capped median ctl:-101 ext:-55
Nov 5 21:08:14 RuckusAP user.warn kernel: NF Channel 2437 Chain 1 measured latest ctl:-98 ext:-50 capped median ctl:-99 ext:-55
Nov 5 21:08:14 RuckusAP user.warn kernel: NF Channel 2437 Chain 2 measured latest ctl:-32710 ext:18080 capped median ctl:-55 ext:-55
Nov 5 21:08:14 RuckusAP user.warn kernel: wifi0: 1351148 : stuck beacon (missed 11) scanning 0, syncbeacon 0, sc_beacons 1
Nov 5 21:08:15 RuckusAP user.warn kernel: nodestats used greatest stack depth: 7004 bytes left
Nov 5 21:08:15 RuckusAP user.warn kernel: NF Channel 2437 Chain 0 measured latest ctl:-99 ext:-50 capped median ctl:-101 ext:-55
Nov 5 21:08:15 RuckusAP user.warn kernel: NF Channel 2437 Chain 1 measured latest ctl:-97 ext:-50 capped median ctl:-99 ext:-55
Nov 5 21:08:16 RuckusAP user.warn kernel: NF Channel 2437 Chain 2 measured latest ctl:0 ext:-16328 capped median ctl:-55 ext:-55
Nov 5 21:08:16 RuckusAP user.warn kernel: wifi0: 1352382 : stuck beacon (missed 11) scanning 0, syncbeacon 0, sc_beacons 1
Nov 5 21:08:17 RuckusAP user.warn kernel: NF Channel 2437 Chain 0 measured latest ctl:-101 ext:-50 capped median ctl:-101 ext:-55
Nov 5 21:08:17 RuckusAP user.warn kernel: NF Channel 2437 Chain 1 measured latest ctl:-99 ext:-50 capped median ctl:-99 ext:-55
Nov 5 21:08:17 RuckusAP user.warn kernel: NF Channel 2437 Chain 2 measured latest ctl:-31019 ext:0 capped median ctl:-55 ext:-55
Nov 5 21:08:17 RuckusAP user.warn kernel: wifi0: 1353616 : stuck beacon (missed 11) scanning 0, syncbeacon 0, sc_beacons 1
18 REPLIES 18

keith_redfield
Valued Contributor II
Is anything other than your backhaul plugged in?
What version of ZoneFlex is loaded?

michael_katzung
New Contributor II
Downloaded and installed 9.6.1.0.15

As for the backhaul It's a big mixed environment on a /20. So servers, workstations etc, Fed Via a PoE brick, nothing plugged into the non poe port.

keith_redfield
Valued Contributor II
I think you might very well be seeing a hardware failure. Easy test if you have another unit handy. But, these are fairly subtle symptoms, and usually hardware is a "go big or go home" fail.

Other things to try:

Set the AP to factory reset (ssh in, "set factory/reboot") and maybe power cycle it as well.

Unplug the AP from ethernet while running the tests (to eliminate odd broadcast, etc as culpable)

keith_redfield
Valued Contributor II
Update - I ran a quick test in our lab on the same AP - no issues. I think you got a bum unit 😞
Labels