Restarting the Software SDN controller causes network disconnect
Hi,
I am running the Omada SDN software controller under Docker in a NAS, and I have a process to update the docker containers daily. Whenever a new release is found for the Omada container, the container is updated. The problem is that after restarting the container, the controller will re-adopt the devices (according to the event log), and in the process cause network disconnects and alerts.
Is there a way to restart the controller without causing disruption to the devices? Thanks
For reference:
Gateway: TL-ER7126 Firmware: 1.0.1
Switch: TL-SG3428 Firmware: 2.0.3
Omada SDN controller: 4.4.3
Docker container being used: https://hub.docker.com/r/mbentley/omada-controller
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
yes this is quite annoying. it feels like there should be a document rev system of some type so that the devices dont always get reprovisioned when the controller comes back online.
- Copy Link
- Report Inappropriate Content
Ok, I looked around the forums and it looks like this issue might have been fixed.
I had not set the DST options for the site (or the controller). I have updated this setting, and I will test if this issue is solved when it's convenient to restart the controller.
- Copy Link
- Report Inappropriate Content
Well, I restarted the container this morning after making sure the DST settings were correct, and the gateway still lost the connection, so it hasn't been fixed. I even see this in the logs:
2021-07-28 08:34:42 [net-event-handler-pool-1] [INFO]-[SourceFile:112] - config version is same, reply rebuild[NOT_RESET_CONFIG] to device[<Router_MAC>]
- Copy Link
- Report Inappropriate Content
Due to the reboot of the controller, the WAN of several sites is down, so it is very inconvenient to use.
A new firmware should fix this issue.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Unraider,
Unraider wrote
I have updated the gateway to the 1.1.1 firmware version, and I’m still seeing this issue
The issue will be fixed in the subsequent firmware update on the Omada Controller v4.4.4, it's not been released yet.
I'll update this post when the new release is available. Thank you for your great cooperation and patience!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3770
Replies: 9
Voters 0
No one has voted for it yet.