EAP655-Wall access point repeatedly gives "was connected" alert
I keep getting repeated "xxx was connected" events on my EAP655-Wall. Firmward has been updated. No actual connection issues in use as far as I can make out. And not getting any disconnected alerts inbetween the connected alerts.
Any ideas what's going on please?
I've seen similar issues with other APs being solved by firmware updates so I was hoping this would also be the case for mine, but alas not...
Anything else I can look at, settings etc?
Cheers!
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @LincolnDJ
Your SDN devices (gateway routers, switches, or EAP) may have lost contact with the controller if your controller log is filled with messages stating that they are often disconnecting and reconnecting. The following procedures can be used to verify that the controller and SDN devices are connected, even while the internet is unaffected:
1) Examine the quality of the wire that is plugged into the controller;
2) Examine the controller's hardware;
3) Replace the controller's power source to ensure a steady power spply;
4) Update the firmware version to the latest.
- Copy Link
- Report Inappropriate Content
@LincolnDJ You have any POE devices connected to the 655-WALL? I had something similiar when I had POE enabled and had a POE power adapter connected.
- Copy Link
- Report Inappropriate Content
hi thanks for the reply. The AP is powered via PoE from a ER7212PC router/switch, and there's nothing connected to any of the 3 ports on the AP itself.
I could try powering it from the AC adapter - but I'd rather not long-term lol
- Copy Link
- Report Inappropriate Content
Hi @LincolnDJ
Your SDN devices (gateway routers, switches, or EAP) may have lost contact with the controller if your controller log is filled with messages stating that they are often disconnecting and reconnecting. The following procedures can be used to verify that the controller and SDN devices are connected, even while the internet is unaffected:
1) Examine the quality of the wire that is plugged into the controller;
2) Examine the controller's hardware;
3) Replace the controller's power source to ensure a steady power spply;
4) Update the firmware version to the latest.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 93
Replies: 3
Voters 0
No one has voted for it yet.