Had two separate 4600C links drop registration tonight less than an hour apart for no apparent reason. Both reporting
2024.12.07 20:24:59 kernel: [1917093.154215] SM disassociated from AP[bc:e6:7c:f0:92:f4] F=6795 11axahe160. Reason: 36 (STA INITIATED DISCONNECT)
Great signal level and modulation and no interference. Different frequencies. Both 160 Mhz with full EIRP. One link is running 5.9 and the other 5.9.1 RC2. It looks like it was internally triggered on the SM side in both cases> Anyone else experienced this or have any thoughts on what could have caused it? This took out one of our internet feeds and a primary backhaul, so not good. Both recovered after the customary 3-5 minutes to reregister.
I had something like this happening to a link but it was running an early 5.9.1 beta. I upgraded both sides to the 5.9.1 release and now it’s working fine. Another thing you can do is pair down the channels and channel width to the one you’re using so it will reconnect immediately. I know this isn’t ideal from an agility standpoint, but for our links, we have redundant paths so we can get in and change it from the far side in an emergency.
Yes, but it’d also be good if the firmware could know to check the ‘last known good’ channel first, before checking all other possible channels. We had some old (like 802.11A old) gear back in the day which did that. Reboot the SM and it’d check for the AP on the ‘last known channel’ first, and reconnect almost immediately. Very simple and very good feature.