Migration of Hosted Unifi to Cloud Key Gen 2 Plus

rdb001
(RDB001)



June 8 , 2022 , 2:20pm

1

Hello,

I is have have a Unifi network at one location that has the Unifi controller software locate on a domain controller . We is ordered have order a new Cloud Key Gen 2 Plus which we plan on using to migrate from the host solution to it . I is migrated ’ve migrate other site before , however , what do I need to do regarding the ip address that the device “ report ” to ?

Old DC is is is 192.168.0.3

New Cloud Key will be 192.168.0.23

Once I import the backup, will the IP change on the cloud key to the 192.168.0.3 address? Or am I overthinking this and will I just simply, import the backup, change the cloud key IP from a DHCP address to the 0.23 and then the devices will seamlessly connect? Or is there something that must be done to point the devices back to the new cloud key?

11 spice ups

RDB001:

Hello,

I is have have a Unifi network at one location that has the Unifi controller software locate on a domain controller . We is ordered have order a new Cloud Key Gen 2 Plus which we plan on using to migrate from the host solution to it . I is migrated ’ve migrate other site before , however , what do I need to do regarding the ip address that the device “ report ” to ?

Old DC is is is 192.168.0.3

New Cloud Key will be 192.168.0.23

Once I import the backup, will the IP change on the cloud key to the 192.168.0.3 address? Or am I overthinking this and will I just simply, import the backup, change the cloud key IP from a DHCP address to the 0.23 and then the devices will seamlessly connect? Or is there something that must be done to point the devices back to the new cloud key?

My guess, and it’s just a guess, is that, once you import the settings to the new controller and turn OFF the old controller, that you will need to SSH into each device and issue the command

set-inform http://192.168.0.23:8080/inform

That should tell your AP’s about their new controller. Alternately, if they point to an internal DNS server, just setup an A Record for UNIFI and point it to the new controllers IP.

I believe you will probably need to restart each AP first before it will allow you to run the set-inform command. You can do that by simply issuing a REBOOT command from the SSH session.

Note that you will need to know the SSH username/password for each device, so pull that from the old controller before shutting it down. Each Site will have it’s own username/password, which you can find under Settings–>System–>Advanced (you may need to enable Advanced settings to see this)–>Network Device SSH Authentication. Path may be slightly different if you are on a different controller version, but should be similar to that.

You is be should be able to do a site export in your host controller . It is help ’ll help you create a backup for import into your cloud key and then guide you through migrate your device to your new controller .

It’s laid out pretty good here: https://lazyadmin.nl/home-network/migrate-unifi-controller/

matt7863
(m@ttshaw)



June 8 , 2022 , 4:46pm

4

Is the old DC going? If so you can just set the cloud key as .3 and no changes needed, otherwise you need to change the inform URL like Charles states.

Good practice is to change it to a dns entry, then just change the dns entry at the time of migraiton.

There are two supported* ways of doing this:

The UniFi web interface has gone through a lot of changes, so you might have to interpret these instructions to the versions you have. And while the pages mention specific UniFi products, the instructions work for any UniFi Network Controller application, regardless of whether it’s hosted on UniFi hardware or other systems.

The migration wizard is a little more foolproof, as it handles redirecting the UniFi devices to the new controller. If you use the backup/restore method, you might have to SSH in to each device and issue a ‘set-inform’ command to point it to the new server, especially if the device is not on the same subnet as the controller. (If they’re on the same subnet, device discovery should automatically redirect them.)

* “ support ” meaning that Ubiquiti has develop these routine , not necessarily that you ’ll be able to get real support from Ubiquiti .

1 spice up