06-19-2019 03:17 PM
We just upgraded our AP250's from 7.1 to 10.0r5 and are getting a ton of high interference alerts. Both radios on almost all AP's are set for 5ghz and auto power and channel. Has anyone else run into this?
12-10-2019 12:47 AM
We are seeing the same thing on AP250's. We will have one start to act up, the cpu will spike, and it will start to drop pings and have high latency. Eventually it becomes more and more unresponsive. Pinging the device internally at 127.0.0.1 shows latency issues as well.
Found others having issues when beamforming was on which we do not.
Turning off wifi1 appears to fix the issue, at least on the one below.
sh cpu detail
CPU total utilization: 39.923%
CPU user utilization: 0.760%
CPU system utilization: 1.901%
Number of interrupt in last second: 2982
Interrupt utilization: 0.000%
Soft interrupt utilization: 37.262%
------------------------------------------------------------
CPU0 utilization:
CPU total utilization: 31.818%
CPU user utilization: 0.757%
CPU system utilization: 1.515%
Interrupt utilization: 0.000%
Soft interrupt utilization: 29.545%
------------------------------------------------------------
CPU1 utilization:
CPU total utilization: 48.091%
CPU user utilization: 0.763%
CPU system utilization: 1.526%
Interrupt utilization: 0.000%
Soft interrupt utilization: 45.801%
2019-12-09 19:40:14 info kernel: [wifi]: wl_add_timer: Already set. Name: wnm_bss_idle_timer, per 1
2019-12-09 19:40:14 info kernel: [wifi]: wl1: fatal error, reinitializing
2019-12-09 19:40:14 info kernel: [wifi]: wl1: wlc_dpc HAMMERING: MI_GP0 set
2019-12-09 19:40:14 info last message repeated 7 times
10-08-2019 12:05 AM
Thanks for the info all. We are having DFS issues also, probably goes along with the bug in the code. I may kick it back down to v7
09-30-2019 09:51 PM
How could you tell the radio was rebooting?
09-30-2019 08:49 PM
yes had one of those so far, weirdest thing as it was not software, needed a complete replacement AP to fix, was just sitting on 98% cpu constantly despite full resets and reconfigs and no clients. Unfortunately the 250 has been nothing but trouble for us, our rma counts are through the roof because they just refuse to boot sporadically. There is something very wrong in the basic boot level that bricks them where a reset does not even register. Pity because the 330 was very reliable.
Seems unbelievable they haven't squashed this bug by now though as its been reported for at least 6 months now and numerous updates have been released. All energies seem to be in reporting and graphing not backbone.