Change ER605v2 Omada Controller IP to Another IP without Resetting it.
I have several remote ER605 v2 routers pointed to my Omada Controller using a static public IP.
I have to get a new ISP so I will need to change the static public IP of the Omada Controller.
Is there a way to change the IP that the router has set for the Omada Controller without resetting the TP-Link if it is already managed by a controller?
Thanks,
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I think the easiest/safest way is to do a controller migration, ie spin up a new controller, migrate the config, then migrate the devices. It won't be seamless, but the interruption should be in the order of a few outages of a few minutes each as devices get reprovisioned in their new virtual home.
Have a look here (image below is from p.13) as that's how you 'change' the controller from an IP to a URL remotely:
https://static.tp-link.com/2019/201910/20191023/managing_the_omada_controller.pdf?configurationId=18625
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Use the discovery utility to assign the new IP and let it adopt them again.
- Copy Link
- Report Inappropriate Content
Since the devices in question appear to be remote to the controller, I have found it easiest to change the controller URL on the remote devices to use a dynamic DNS name rather than a numerical IP in order to find and be managed by an offsite controller via the internet.
- Copy Link
- Report Inappropriate Content
Does the Discovery utility work for Routers? I thought it was only for EAPs.
I don't have any devices in these remote locations where I could download and install the Omada Discovery Utility. From my understanding the Omada Discovery Utility can't be used over WAN.
I could be mistaken though.
Thanks.
- Copy Link
- Report Inappropriate Content
I agree. I am planning to do dynamic DNS when I re-configure the TP-Links so I don't have this issue come up again
Is there any way to change the controller setting on the router from an IP to a domain without resetting the router.
Thanks.
- Copy Link
- Report Inappropriate Content
I think the easiest/safest way is to do a controller migration, ie spin up a new controller, migrate the config, then migrate the devices. It won't be seamless, but the interruption should be in the order of a few outages of a few minutes each as devices get reprovisioned in their new virtual home.
Have a look here (image below is from p.13) as that's how you 'change' the controller from an IP to a URL remotely:
https://static.tp-link.com/2019/201910/20191023/managing_the_omada_controller.pdf?configurationId=18625
- Copy Link
- Report Inappropriate Content
That looks like it will work for my situation.
I am going to try that and see how it goes.
Thanks!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 923
Replies: 6