We started to experience disconnect issues the following morning. This procedure gives us confirmation that all units are running smoothly with no issues. As with all of our projects, we stay on-site a minimum of 48 hours after installation and programming. Once the equipment was installed, updated, provisioned, and programming, we started our testing. Switch - USW ( USW-Pro-24-PoE) Firmware Version: 5.8 Also required, an IoT network and Guest Portal, which is pretty standard these days.Īccess Point - UAP ( UAP-AC-Pro) Firmware Version: 4.1 We used as much of the existing cabling as possible, and we installed only 300 meters of new cable.
I think I will add my 718 and 918 into the mix with 2.5 or 5G adapters as secondary connections in the near future. 400GB replication task done in 21min 23:20-23:41 with average speed of aabout 350MB/s and peeks at 409MB/s Regarding speed with my current setup speeds are about 350-450MB/s (R/W) with RAID6 and RAID5 arrays (RS3614RPxs in both cases). DIGITUS DAC 10G cables (DN-81221) White light = 10G Unifi controller view, blue light = 10G DIGITUS DN-81221 were detected without any problems at all.
UPGRADE UNIFI CONTROLLER LINUX UPDATE
I have a few NAS models that have dual 10G cards, as well as some that are on 2.5/5G, and getting those speeds of transfer requires a 10G capable switch.Ĭonsidering that the devices are still not connected, the Unifi Controller is not registering anything apart from the uplink (port 16) to the rest of the network.Īdopt and update process to the current latest firmware was executed without any major problems and the switch is stable, silent (so far) and ready to be utilized. The main reason that I will use this controller is to configure and maintain my new US‑16‑XG Unifi switch from UI. Log into your web UI using your NAS IP address and the 8443 port (yes the web UI runs on HTTPS) Setup US‑16‑XG switch Be sure to NOT log in using the Ubiquiti cloud solution but rather choose the advanced setup to create your local account. It's up, now what? Now that you have the controller up and running it is time to log in. By default adopt will be pushed towards port 8080, and if you have it changed, you will not be able to do it until you make the necessary changes. NOTE: would recommend keeping the port 8080 as is considering that you might get into problems when you start adding and adopting new devices using the controller. Make sure to visit the linuxserver hub page for more info on all the ports and configuration parameters.
Image: ghcr.io/linuxserver/unifi-controller Once you have it up and running, make sure to log into your Portainer setup and create a new stack (using docker-compose) with the following compose file (you can of course change it any way you want): version: "2.1" Would recommend running this container via Portainer solution also hosted on your Docker host, and for more info on it, you can read up here, and then come back. To stay on top of all your docker image update you should look into the DIUN solution, and you will not miss a single update, ever. I will be using the linuxserver/unifi-controller image myself as it is always up to date and maintained by a trusted team. Linuxserver team behind this image have done a great job with documentation, so probably there will be nothing unclear.
UPGRADE UNIFI CONTROLLER LINUX HOW TO
Unlike some other articles here, this will be a short one just to see how to get this container up and running.
If you are into Docker you can easily configure and run your own. If you are looking to run your Ubiquiti gear you will need an Unifi Controller at some point unless you want to pay for the cloud-hosted one. UPDATE - added some details on the bottom regarding performance of the Unifi US-16-XG switch