These instructions will detail how to install TP-Link Omada software controller onto Ubuntu 20.04. I am starting with a freshly built Ubuntu 20.04 instance that is fully up to date.
Install misc software
Install OpenSSH (optional – but necessary if you want to connect to the server remotely via SSH):
sudo apt update && sudo apt install openssh-server -y
You should now be able to connect to your Ubuntu server remotely via SSH. You can use the command ‘ip a’ to see your IP address if you do not know what it is.
Install dependencies (OpenJDK 8, curl, jsvc):
sudo apt update && sudo apt install openjdk-8-jre-headless jsvc curl -y
Install MongoDB
To install MongoDB, I followed the excellent instructions from Digital Ocean located here: https://www.digitalocean.com/community/tutorials/how-to-install-mongodb-on-ubuntu-20-04
curl -fsSL https://www.mongodb.org/static/pgp/server-4.4.asc | sudo apt-key add -
echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/4.4 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-4.4.list
sudo apt update && sudo apt install mongodb-org
Start the MongoDB service:
sudo systemctl start mongod.service
Check MongoDB service status (optional):
sudo systemctl status mongod
You should see that the service is running.
Enable MongoDB on startup:
sudo systemctl enable mongod
Download and install latest TP-Link Omada software controller:
sudo wget https://static.tp-link.com/upload/software/2022/202203/20220322/Omada_SDN_Controller_v5.1.7_Linux_x64.tar.gz tar zxvf Omada_SDN_Controller_v5.1.7_Linux_x64.tar.gz cd Omada_SDN_Controller_v5.1.7_Linux_x64/ sudo bash ./install.sh
That’s it! Once the server has been installed, you can connect to your instance of Omada software controller by navigating to http://[server IP]:8088
Comments 11
Hi Chris!
Golden one.
Very simple, very straight forward. Thanks a lot.
Hi,
the upgrade procedure can be run like the installation?
Thanks
Yes, this is what i would like to know as well!
How to upgrade to next controller versions.
Thanks a lot
sudo wget https://download.tplinkcloud.com/firmware/Omada_SDN_Controller_v5.3.1_linux_x64_202204221_1651910342427.gz
tar zxvf Omada_SDN_Controller_v5.3.1_linux_x64_202204221_1651910342427.gz
cd Omada_SDN_Controller_v5.3.1_linux_x64
sudo bash ./install.sh
Can you upgrade without uninstalling?
wget -qO – https://www.mongodb.org/static/pgp/server-6.0.asc | gpg –dearmor | tee /usr/share/keyrings/mongodb.gpg > /dev/null
echo “deb [ arch=amd64,arm64 signed-by=/usr/share/keyrings/mongodb.gpg ] https://repo.mongodb.org/apt/ubuntu jammy/mongodb-org/6.0 multiverse” | tee /etc/apt/sources.list.d/mongodb-org-6.0.list
apt update
apt install mongodb-org
Thx for the intro and tutorial to omada. I would like to add though , that when the ccontrolller is unable to discover any device it might be worthwhile to disable the firewall (ufw) anf check port forwarding.
I ran this using much of the install tips in https://www.crosstalksolutions.com/definitive-guide-to-hosted-unifi-2021/ and it works. The one thing I am struggling is with the lack of a script to automate SSL. I presume the one from Steve Jenkins will only work with the Unifi instructions as it refers to the Unifi Keystore
Tried going through this guide and I am constantly stuck at “sudo systemctl status mongod”. Every time I get the same output:
● mongod.service – MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: failed (Result: core-dump) since Thu 2023-06-29 17:34:42 EDT; 20s ago
Docs: https://docs.mongodb.org/manual
Process: 2517 ExecStart=/usr/bin/mongod –config /etc/mongod.conf (code=dumped, signal>
Main PID: 2517 (code=dumped, signal=ILL)
Jun 29 17:34:41 piratepi systemd[1]: Started MongoDB Database Server.
Jun 29 17:34:42 piratepi systemd[1]: mongod.service: Main process exited, code=dumped, sta>
Jun 29 17:34:42 piratepi systemd[1]: mongod.service: Failed with result ‘core-dump’.
I had the same issue. For me it was because i was running it in Proxmox. The hit was to set the CPU to host in the VM in proxmox. worked after that