Omada Hardware Controller v5.5.7 issues
I installed the newly released Omada Hardware Controller v5.5.7 firmware on 2 September. It seemed to run Ok until this morning. When I say, 'OK', the OC200 has been losing connection/readopting a device every few days, but not constantly.
Overnight, the OC200 started dropping, reconnecting, and readopting all of my equipment. Then it would do it again a few minutes later. I unplugged the OC200 from its POE switch, waited a few minutes, then replugged it in again. Within an hour, it started the dropping/reconnecting/readopting loop again. I was forced to revert to V5.4.7 and rebuild from my backup from 1 September. It's now been back up for about an hour and 30 minutes without issue.
Here.s my equipment - all except the OC200 now running the latest firmware:
- TP-Link Router (TL-R605) (V1)
- TP-Link Hardware Controller (OC-200) (V1)
- TP-Link 8-Port Gigabit Managed PoE Switch (TL-SG2210P) (V3.20)
- (2) TP-Link Managed 16-Port Switches (TL-SG2218)
- (3) TP-Link EAP245 Access Point (V3)
- TP-Link EAP 225 Outdoor (V1)
Is anyone else experiencing any difficulties with v5.5.7?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@lflorack Not yet. That should be my 1st try. Power everything down and let it rebuild and see what happens. Hopefully your fingers are still crossed!
Will report back once I do that.
- Copy Link
- Report Inappropriate Content
My rebooting effort from yesterday remains successful so far today.(fingers crossed)
Just in case it makes a difference, after reverting to 5.4.7 for the OC200 and 3.20.2 for the SG2210, I have not installed the latest versions of either firmware as I am trying to stabilize everything and then add the latest versions (5.5.7 & 3.20.4) back again.
Since downgrading both devices did not help with the issues, I don't believe those upgrades are the issue but want to be clear on my status, in case some of you have remained at the latest firmware versions and try rebooting everything without success.
If rebooting ends up being the solution for everyone, it points to the potential need to reboot all devices, every time a firmware upgrade is done to any device. Kind of a PITA, but given the potential alternative, not too bad.
Anyway, if this works out, I'll update my SG2210 to 3.20.4, reboot, and wait a while. Then, update my OC200 to 5.5.7, reboot, and wait a while.
- Copy Link
- Report Inappropriate Content
Good to know. I powered down everything and powered up. I am still on 5.5.7 but the switch is still at 3.20.2 (and I am getting the icon that it wants to upgrade but will hold off).
If it still misbehaves, then I will do the downgrade to 5.4.7, power cycle everything, and then we can compare our networks.
Up until now the only problem I had was with the router 1.21 firmware that had DHCP issues. The beta release fixed that. All my other upgrades went smooth. Now all of a sudden this crops up.
Gonna watch it for 24 hours to see what happens. If I get the disconnects today, its back to square one..
- Copy Link
- Report Inappropriate Content
Rebooting everything (all devices) seems to have done the trick - both for me and another person with similar issues on Reddit. It has now been 24 hours since I rebooted everything and there has not been a single error since. I'll mark this as the solution.
I guess that may mean that a reboot is needed for every firmware update (?)
- Copy Link
- Report Inappropriate Content
@lflorack I am approaching 10 hours since the full power down and nothing yet as well. Going to sit tight on 5.5.7 and 3.20.2 for a few days and see if it holds stable . Then I may get adventurous and put 3.20.4 back into the 2210.
Sure beats having to reload or downgrade!
- Copy Link
- Report Inappropriate Content
That's great!! Glad this worked out.
I'll probably update the OC200 tomorrow and wait at least a few hours to update the 2210P.
- Copy Link
- Report Inappropriate Content
Dear @lflorack, @Fleegle61,
Thank you for taking the time to post the issue in TP-Link Community!
The issue has been reported to the support engineers for further investigation. If convenient, could you please help to provide your network diagram for checking? Are you both using the TL-SG2210P v3.20 as the main switch in the network?
- Copy Link
- Report Inappropriate Content
@Fae Here is my map. As noted, I was witnessing different tp-link hardware disconnecting from the network. I upgraded both OC200 and 2210 at the same time and then immediately started noticing the disconnect issues. I downgraded the 2210 from 3.20.4 back to 3.20.2 and that made no difference. I was about to downgrade the OC200 to 5.4.7 but went with the power cycle process of all TP-LINK hardware in my network. That seems to have stabilzed everything for now. If it remains stable I will then attempt to update the 2210 back to 3.20.4 and hope that it continues to remain stable. If there are issues I will try power cycling all TP-LINK hardware again to see if it stabilizes.
- Copy Link
- Report Inappropriate Content
Hi @Fae
I've pasted my LAN diagram below. Yes, the TL-SG2210P is my main switch.
As noted in this thread, the system had become increasingly unstable over the past few days, but after I upgraded the firmware for both the OC200 (5.5.7) and the SG2210P (3.20.4) on the same day, all of the system hardware (all Omada) was almost continually going through disconnect/reconnect/readopt loops from the OC200 controller at an increasing rate. I tried downgrading the firmware for the OC200 (5.4.7) and the SG2210P (3.20.2) without any improvement. I rebooted the OC200 and SG2210P individually without improvement. I tried a few other things also without success. Finally, I rebooted all of the Omada devices simultaneously and everything came back up and is now completely stable again and has been so for about 20 hours at this point. As I mentioned earlier in this thread, at no time during all of this did any of my 39-42 connected clients lose connection to the LAN or the internet.
A similar discussion to this one has also been taking place on Reddit with 5-10 others - all with the same issue. While all of them have the OC200 and some have the SG2210P too, don't know that all of them do. Rebooting everything simultaneously seems to have solved the issues for everyone who has reported back to the thread.
I will upgrade the OC200 and SG2210P back to the newest firmware versions (5.5.7 & 3.20.4) today or tomorrow to see if the network remains stable. I anticipate doing a full hardware reboot after each firmware change to avoid any similar issues.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3509
Replies: 29
Voters 0
No one has voted for it yet.