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