No, i’m confusing you with my language. It is a WPA2 fail. I suspect that a key/cert refresh in the backend of the WPA encryption is failing. The symptom is that it is like the secret has changed. The master shows this error: “Reason: INVALID SECURITY KEY. SM mac: BC:E6:7C:20:E9:DA”
Last time it happened was on the 14th so it will be a couple weeks before it does it again. To resolve we do nothing other then a simple reboot of the Master. No config changes happen.
It is in CnMaestro, I grabbed a support file today. I will try to remember the next time it happens, since it is not a actively used link leaving it down is also a possibility if you like. We still have access to both sides since it is a backup.
1 Like
INVALID SECURITY KEY can pop up under interference as well. The key itself can come corrupted.
Agreed, interference could be the cause, but that is not what’s happening in this case. Digging into this further it appears likely I have a failing piece of hardware. I suspect the memory sectors are progressively failing as the occurrences over the last year started at every couple months and has gotten worse over time to now it is at less then a week.
1 Like
3 posts were split to a new topic: Strange behaviour on 5.10.1 with hardware acceleration
I started updating some of my ePMP 425 PTP’s to 5.10.1 and I noticed that after updating the SM output power gets reduced from 30 to 23. If you set it back to 30 then reboot it will go back to 23. I haven’t tested any PTMP yet, but it’s repeatable on 425’s in ePTP.
2 posts were split to a new topic: Error running link capacity tool on 5.10
Hi,
I would want more details on this one, we had customers call in because we had the Access point in migration mode with older SMs, would they not notice it anymore or is there still a hit on performance for these older SM?
AXG-11713 (All): Improved performance for backward compatibility mode with N-gen SMs
Thanks!!
Patrice
There are still some issues with legacy N clients with an e4k AP set to “migration mode”. Sometimes all clients across the AP will experience high latency/jitter and poor throughput, despite having excellent modulation. A reboot of the AP & SM’s temporarily resolves the issue. Migration mode is not intended for long-term use. We typically will swap out these legacy N clients for F4525’s as soon as possible so that way we can disable migration mode.
I read somewhere that MU-MIMO isn’t available or doesn’t work in split-sector mode? Is this still the case? Will that ever change? Could you elaborate as to why>? Thanks
Also, do 300 series clients cause overall ap performance to suffer?
Yes, MU-MIMO does work in 2x 4x4 split sector mode. See this post for more details:
I saw some private test results along with a public customer testimonial from @DigitalMan2020 regarding running e3k SM’s with an e4k 5GHz AP in backwards compatibility mode. I seem to recall that there was actually an overall slight performance increase. I’ve searched quite a bit and I cannot find the posts. Maybe @DigitalMan2020 can share their experiences?
We have a mix of force 300 25 and 4525 and everything is operating great. We are seeing some link tests not matching up with speed tests but cambium is investigating. We have been really happy with the ability to have backward compatibility and we are eventually going to have all SMs as 4525.
Based off screenshots, some of the speed tests do show mu-mimo throughput in omni mode according to @terintamel testing. If those are accurate readings it would seem it works some?? I’ll probably stick with what’s officially supported though. So 2x 4x4 mode should work with mu-mimo? I have some 4x4 mimosa sectors I can try.
Actually, just got notice from a Cambium developer that they expected MU-MIMO to start working with FW 5.10.1, which my tests did confirm.
I can’t find pdf of this firmware. what I found only release notes.
can u gimme the link. something like User Guide.
Hi @nbctcp ,
as for now a user guide for AX platform is not ready. You can use AC User Guide for reference.
Also filter this thread with knowledge-base tag for unique features description.