Omada Hardware Controller v5.5.7 issues
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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
At 16:39 (EDT), I updated my TLSG2210P to firmware 3.20.4. I have not rebooted anything and will see if the devices remain stable.
- Copy Link
- Report Inappropriate Content
After updating my TLSG2210P switch to firmware 3.20.4 earlier today, I noted that the switch CPU loading went from 5% to 6% and its memory usage went from 36% to 53%. Both of those new levels are steady. So far, there have been no issues like I saw before with the dropping, reconnecting, readopting cycles, but I'll keep watching this.
- Copy Link
- Report Inappropriate Content
@lflorack same here. Upgraded the switch to 3.20.4 and appears everything is holding stable on my end.
- Copy Link
- Report Inappropriate Content
@lflorack appears there is now a 3.20.5 for the 2210 switch. They pulled back the 3.20.4
Who is up for another upgrade to see if we have to power cycle all the hardware???
- Copy Link
- Report Inappropriate Content
It seems that firmware 3.20.5 is available for the TL-SG2210p v1 but not yet for my TL-SG2210p v3.20. I'll keep an eye out for it. Thanks for the heads up.
- Copy Link
- Report Inappropriate Content
@lflorack double check. I have a 3.20 2210P and it prompted me to go to 3.20.5
I just did it this morning so I will give it 24 hours to see if it works without any problems or requiring a power cycle.
- Copy Link
- Report Inappropriate Content
@Fleegle61 wasn't there last night, but checked this morning and it showed up. Will update in a few minutes. Thanks!
- Copy Link
- Report Inappropriate Content
Hello,
I also had problems after the update to V5.5.7, but of a different nature. Due to external circumstances, I only noticed the problem later when I had to go online. I suddenly had DNS errors on some websites and all intranet addresses. Since I had previously installed the update, I wanted to downgrade. Autobackup writes backups to a USB stick every day, so I wasn't worried. I then restored yesterday's backup, which was about 2MB in size. After the successful restore nothing changed. The home page was the same as it was after the downgrade and my switches and EAPs showed up as devices being controlled by another controller.
I was starting to panic. I already saw myself having to redo the entire network. I then started looking at the backup files. I noticed the following: Up to OC200 firmware 5.3.2, the backup files were about 14MB in size. After the update to V5.4.7 they were suddenly only about 2MB in size. I then tried the restore with the last backup of V5.3.2 and BINGO, the OC200 started again with all my config and connected hardware.
Last night the first backup was created under V5.5.7, which is now only 1MB in size. Is it possible that since V5.4.7 only faulty backups are created? None of the small backups worked for me, only the V5.3.2 ones.
After this experience, I can no longer rely on the new backups when they are created with this small size. Apparently they will be restored successfully, but that's about it.
I don't have the same problems as the posts before me, but since these are also problems after updating to the latest OC200 firmware, I didn't want to open a new threat and write my experiences here.
After the downgrade, I restarted all devices once. Everything worked again, I then tried the update again and since then V5.5.7 seems to be running here too.
- Copy Link
- Report Inappropriate Content
Thanks for your information. It adds to the overall storyline.
Somewhere in the upgrade chain of the OC200 and my TL-SG2210P main switch, things got "a bit" messed up for me and several others. As we have all discovered, a reboot of all network devices became necessary to restore proper functionality. I am now on the latest versions of all firmware, and everything is running fine again. The key was the reboot of everything. Not sure which device or firmware version - or combination of those things, made the mass reboot a requirement, but for many of us, it was.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3931
Replies: 29
Voters 0
No one has voted for it yet.