Unifi Controller Resource Usage?
Hi all,
I'm using a Gold Plus and had a Unifi Controller container up and running on my server before I got my Firewalla to manage my AP's (just two U6 Mesh's at the moment, maybe adding a switch soon).
I'm curious for anyone running their controller on the Firewalla, or maybe moved it to the Firewalla from another system, what kind of hardware strain are you seeing on your firewall? Is it worth moving it to my Gold+ just to have it all in one box, or is the potential performance hit worth keeping them separate?
Thanks in advance for any opinions or shared stats!
-
The Unifi controller should run just fine on Gold Plus. I have a script that makes it very easy to do github.com/mbierman/unifi-installer-for-Firewalla
The controller should not impact Gold Plus in any noticeable way.
github.com/mbierman/unifi-installer-for-Firewalla
Thank you for the resource @Michael Bierman!
I actually came across it once before looking for similar scripts on GitHub. Have you recently tested the script? It looks like your compose file was last modified a few years ago, and I'd been reading that more recent updates to either Docker or the OS has made new requirements necessary (concerning the network driver).
Apologies for the multiple questions, but I also wanted to ask, have you had any experience migrating Unifi Controllers? I'm wondering if I should restore from a backup, assuming this doesn't break anything, modify my settings to fit, then before destroying my old container, update the inform override to that of my Firewalla's container to force current AP's to re-adopt over there. Not a big deal if not, I'm sure I can consult the Unifi forums regarding this process.
Thanks again!
-
Have you recently tested the script? It looks like your compose file was last modified a few years ago, and I'd been reading that more recent updates to either Docker or the OS has made new requirements necessary (concerning the network driver).
Seems to work fine here. The yaml will pull the latest docker image. What is not working?
have you had any experience migrating Unifi Controllers? I'm wondering if I should restore from a backup, assuming this doesn't break anything, modify my settings to fit, then before destroying my old container, update the inform override to that of my Firewalla's container to force current AP's to re-adopt over there. Not a big deal if not, I'm sure I can consult the Unifi forums regarding this process.
That should work fine. Definitely don't delete the container until things are confirmed to be working as expected. I would set the inform first so that when you power up the new controller it can talk to all the devices.
-
Hi Michael,
Apologies. Nothing was not working. I was asking, before trying the script, if changes to the OS image or Docker itself caused the compose file to not work as expected.
I did find however, that the portion of the installation script that allows the container address to be accessible via LAN, did not seem to work in my case, even after restarting or blowing away the image and trying from scratch. I eventually resolved it by just manually running the commands from the Unifi guide here on the forums.
As for migration, it seems Ubiquiti has streamlined the process a bit in recent versions (& the new UI). In case anyone else is migrating similarly, there is now an option in your "old" controller to migrate the site, which prompts you to download a site backup, then it sends your APs & Switches to the new controller.
-
Apologies. Nothing was not working. I was asking, before trying the script, if changes to the OS image or Docker itself caused the compose file to not work as expected.
Not a problem. The YAML hasn't changed because to my knowledge there are no changes required.
I did find however, that the portion of the installation script that allows the container address to be accessible via LAN, did not seem to work in my case, even after restarting or blowing away the image and trying from scratch. I eventually resolved it by just manually running the commands from the Unifi guide here on the forums.
Can you share some pointers to what you mean? The script is designed to install a clean copy of the container, nothing more. Migration of a different controller backup isn't included.
there is now an option in your "old" controller to migrate the site, which prompts you to download a site backup, then it sends your APs & Switches to the new controller.
That sounds nice! Thanks for sharing. -
Can you share some pointers to what you mean? The script is designed to install a clean copy of the container, nothing more. Migration of a different controller backup isn't included.
Sorry, was early for me. I should have found the referenced post and linked it. I'm referring to this command:
sudo ip route add 172.16.1.0/24 dev br-$(sudo docker network ls | awk '$2 == "unifi_default" {print $1}') table lan_routable sudo ip route add 172.16.1.0/24 dev br-$(sudo docker network ls | awk '$2 == "unifi_default" {print $1}') table wan_routableFrom:
https://help.firewalla.com/hc/en-us/articles/360053441074/comments/1500000169141Not anything to do with the migration itself. I saw someone opened a GitHub issue, and in there the command was referenced & I saw it was added to your script (may or may not be this exact command) but weirdly, when running the script without errors, the command did not seem to take effect and the container (WebUI) was not accessible until after running it over SSH.
Please sign in to leave a comment.
Comments
9 comments