Issues with Hidden SSID connectivity / Stuck Beacon?

[michael_katzung]

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

[michael_katzung]

Thanks for the quick replies guys. I'll be swapping this out on Saturday, I'll inform if a new AP fixes the issue.

[michael_katzung]

Confirmed, it was not a bad AP, swapped it out and had the same results.

One of our senior admins happened to have a wispy 2.0 so I tried that. Guys, I've been in hotels in downtown Seattle where I could actively see 200+ APs I have NEVER in my life seen wireless interference like this.

Check this out (Forgive me, the fact this is from my phone, I did it on his computer and asked him for a screen shot but he never sent it to me, luckily I took this pic in the event he didn't)



This is in down town Chicago, right next to the L, it looks like every time a train passes the interference would spike.

Is there anything I can do here guys? It seems to work so long as the SSID isn't hidden, but that's connected directly to our LAN and my boss is against broadcasting that ssid unless absolutely necessary.

[michael_katzung]

Also Ignore the solid bar in the middle, that was me showing a co-worker what a microwave does to wireless signal.

[michael_katzung]

Also switching to channel 11 didn't help. Later on in the test (not pictured) that band also got flooded

[keith_redfield]

I'll betcha those trains are using conventional brushed electric motors. So you've basically got a lightening storm (electric arcs) passing by. It's a bit odd that hidden vs visible SSID makes a difference, but that's likely client-driven. (Are you using DPSK?)