Issue with Remote Device Adoption & Firmware Upgrade (Omada Software Controller with Public IP)
Issue with Remote Device Adoption & Firmware Upgrade (Omada Software Controller with Public IP)
Tags:
#Controller
Dear TP-Link Omada Team, I am facing an issue with my Omada Software Controller (running with a public IP). When I add any TP-Link switch or AP from a remote location, the devices are not automatically showing up on the Device page for adoption. I have to manually log in to each device and configure the Controller URL in the device settings; only then does the Software Controller detect the device for adoption. Additionally, I recently added a switch at a remote location:
-
Model: SG2210P v5.20
-
Current Version: 5.20.5
-
Target Upgrade Version: 5.20.10
-
However, the device fails to upgrade both online and manually, showing errors (screenshot attached for reference). Could you please help me resolve:
-
Why remote devices are not appearing automatically for adoption?
-
Why the firmware upgrade (both online & manual) is failing?
Please note: remote locations are fully reachable from the controller network (both ways: remote → controller and controller → remote).
Looking forward to your guidance.
Omada & VIGI | Using at 3 Locations | Controller: V6.0.0.19 (Linux) | GW: ER7206 | SW: SG2428P & SG2210P | APs: 2 × EAP610 | WAN: Jio&Airtel | NVR2016H & 8 Cam's.
2 Accepted Solutions