Heartbeat missed and stability issues for EAP653 after firmware / Cloud controller update
Hi all,
In my home setup I have 3 EAP653's that often show heartbeat missed. When this happens, it appears the clients connected to these AP's loose network connection and try to connect to other AP's. Local ping to these AP's keeps stable during these events, and uptime for the affected AP's in the Omada portal is not reset.
I also have a EAP610 and a EAP225 that work just fine. I have no other Omada gear yet, my PoE switch and router are from other brands. For management of the AP's I'm using Omada Central Essentials (in the EU), so no on-prem controller.
The issues started with either a firmware update of the EAP653's, or the update of Omada Central Essentials to v6, I can't be sure. Before that everything was running smoothly.
I already have tried:
- Power cycling AP's and PoE switch
- Factory reset of EAP653
- Manually trying to downgrade firmware to the latest online version (1.1.3). Strangely enough the AP rejects that firmware.
Has anyone come across something similar?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@coxmin To conclude the issue from my side, after solving the stability issue with 1.1.3, I finally bit the bullet and replaced my other network components with Omada gear. I still had a Netgear PoE switch and Mikrotik gateway. I also moved ahead with upgrading the EAP653's with the latest firmware (1.3.5).
This is my setup now:
I'm using a hardware controller now, which I believe adds a lot of value.
I did have to tinker with a few settings to get it really stable, but everything is rock solid now and roaming works perfectly.I had to turn off the AI roaming and Prohibit Wi-Fi Sharing options.
So I'm a very happy customer now!
- Copy Link
- Report Inappropriate Content
I updated the EAP653 firmware to 1.3.5 and can confirm that everything works: Roaming, VLANs...
- Copy Link
- Report Inappropriate Content
Can anybody please provide me with a link to the 1.3.90 firmware, so that I can use it to downgrade to the older stable one?
I have an open ticket which has not been answered and my users here are getting tired of me rebooting the APs continuously.
- Copy Link
- Report Inappropriate Content
https://we.tl/t-GGOB6BSSKT
First downgrade to 1.3.90, than 1.1.3 (stable)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 3748
Replies: 45
Voters 0
No one has voted for it yet.