bug: upgrade switch firmware does not initiate switch reboot/reset
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Controller: Omada Software Controller on Linux v5.5.6
After upgrading from v1.0.3 to v1.0.7 switch did not reboot and stayed in disconnected status. However, network was not broken and switch was responding on the same ip as well as logging into device with device username and password worked, here a screenshot of webgui after upgrade when it was for hours in disconnected status on controller:
All this means that omada upgrade for some reason did not initiate reboot.
One has ability to click reset, but no button for "reboot" which in this case would resolve the issue.
@Fae @Hank21 can we have "reboot" button on device's interface too for the cases when it is reachable by IP, in disconnected status and requires just reboot. I have made backup of all logs before restarting device, just in case tp-link would like to examine it.
Solution to bug described above: simply restart device (unplug power for around 10 seconds to give it and all devices receiving power from it time to proper shutdown).
Info: Do not upgrade if you have no possibility to restart switch with as example unplugging power.
Dear @btx,
btx wrote
It was running for a day, next day in logs it says device disconnected and appears as disconnected:
Something seems to be wrong with controller/firmware combination. Device has same IP, still managed by same controller and nothing else change, now reboot is not possible as nobody is on site.
Is the switch located in a different location from the controller?
If convenient, could you please upload your network diagram for further checking?
Edit: Would you mind helping our support engineers to look into the issue? I've created a support ticket via your registered email address, and the ticket ID is TKID220906237, if you are willing to help, please check your email box and give it a reply for follow-up. Thanks!
In addition, something needs to be clarified here.
The Reset button will be provided on its standalone web UI only when the switch loses communication with the controller.
Once the switch is being managed by the controller, the Reset button won't be provided to allow anyone to reset the device from its standalone web UI. Otherwise, the administrator might be at risk of losing control of the devices without notice.
So it's normal that you get two different pages when accessing its standalone web UI in different stages.