Display case for my projects and writeups. Most of my work involve automotive and robotics builds, infosec projects, as well as the disobey badges and KouvostoTelecom hardware.
I could not find proper guide for this type of migration, so here are my notes of it. My goal for this change was to increase throughput of the Internet-connection, while keeping the UniFi Protect working.
I expected that this may be an issue, as Protect is running on the Cloud Key, which is also used as network controller. With change to UDM, controller has to move to the integrated one in UDM.
In the end Protect worked perfectly in the new setup, but the challenge in this move was not in Protect, but in firmware revisions.
To configure your UDM, just plug its WAN-port to your LAN.
This way it won’t interfere with your existing network setup, but allows you to configure it.
Connect to UDM via one of the LAN-ports or with the unifi network mobile app. The setup wizard will run on first boot-up.
Login with our unifi credentials to adopt the unit and go with default settings, as these will be changed when your existing site config will be resored into the unit.
This was the hardest part of the setup.
You need to ensure that Unifi Controller and the controller integrated in the UDM are on the same software version (in some cases named “UniFi Network”), or that UDM has more recent version.
Thing that was not apparent for me, was that the controller firmware was integrated in the UDM firmware, so you need updated UDM firmware binary to update the controller software.
This means that you need to look for UDM firmware update. In the example below, we will find UDM firmware at version 1.8.0, which contains controller version 5.14.22
The first issue was that my USG was updated recently, so it was on version 5.13.32, while UDM had the controller on version 5.12.20.
You would expect to see a button called “Update” on UDM-side, but no. UDM was saying that was the most recent version and that’s it.
I tried to backup my USG and recover it on UDM, but no, it just would refuse to work as the UDM controller revision was older.
Solution: After googling a bit, I found that you can download the most recent firmware versions from https://community.ui.com/releases
So, all you need to do is to get the URL of the latest UDM firmware. Just select the latest firmware for UDM and copy the URL for the binary, for example: https://fw-download.ubnt.com/data/udm/bf6a-udm-1.8.0-rc.16-be8c43d6d3524b9d9198053fce49bef3.bin
Now you need to log in to your UDM via SSH. Notice that the username is
ubnt like in EdgeOS devices. Password defaults to your unifi password.
After logging in, run following command with the binary url:
Verify that the binary you select is for the correct UDM. According to Ubiquiti, updating non-Pro UDM with Pro firmware will brick it.
Now you should have an updated controller running same or newer version compared to USG.
Backup your controller via the web UI.
Settings -> Backup -> Download Backup
Now go to unifi.ui.com and select your UDM. This should take you into the network controller config.
Settings -> Backup -> Restore Backup
It will take a while and reboot the UDM. Refresh the page after a minute or so. After reload, ensure that you have correct wireless network configs in UDM and settings seem to have restored.
If you have Cloud Key 2+ and you are using Unifi Protect
Go to your Cloud Key web UI and disable Unifi Network
Cloud Key settings -> Controllers -> Stop Network
This will keep Protect enabled, while controller will be running on UDM.
Otherwise you can now unplug the Unifi Controller, as UDM will take over the control of the network.
DONE UDM should now start adopting your network