Important Note
The minimum system requirements specified for hosts must be dedicated to the host you plan to deploy. They cannot be shared with or used for other non-Infoblox applications. Doing so will negatively affect the performance of your BloxOne services. For information about the minimum system requirements and port usage, see the following:
Prerequisites for Bare-Metal Deployment
Before you start the deployment, complete the following:
- Ensure that your Docker or Containerd environment meets the minimum deployment requirements.
- Open all required ports on the hosts, as list in Port Usage for Bare-Metal Hosts, in addition to the ports required for firewalls.
- Ensure that there are no other processes using port 53 on the host system on which your host will be deployed. For example, some Ubuntu systems running local DNS cache (system-resolved) might occupy port 53, and your host might not function properly in this case.
- Dind (Docker-in-Docker) configuration is not supported for host deployments.
- For Red Hat 8.x and 9.x versions disable nm-cloud-setup.service with the command:
sudo systemctl disable nm-cloud-setup.service
- For Ubuntu 18 and Ubuntu 20 in which
systemd-resolved
is running, perform the following before deploying a host:
Stop systemd-resolved
and remove the corresponding resolv.conf
, as follows:
systemctl disable systemd-resolved.service
systemctl stop systemd-resolved
rm -f /etc/resolv.conf
Check and verify if the NetworkManager
service exists by performing the following on the host:
systemctl status the NetworkManager
If the NetworkManager
service exists, whether it is in the running or non-running state, stop the service by performing the following:
sudo systemctl stop NetworkManager.service
sudo systemctl disable NetworkManager.service
sudo systemctl stop NetworkManager-wait-online.service
sudo systemctl disable NetworkManager-wait-online.service
sudo systemctl stop NetworkManager-dispatcher.service
sudo systemctl disable NetworkManager-dispatcher.service
sudo systemctl stop network-manager.service
sudo systemctl disable network-manager.service
Set resolver, as follows:
tee /etc/resolv.conf << END
nameserver 8.8.8.8
END
Disable unattended upgrades on Ubuntu. The unattended upgrades feature is enabled by default, and it runs at system boot without user's permission. Unattended upgrades could cause all containers to be terminated and new containers to be created. When this happens, the host will stay in a bad state and cannot be recovered. To disable unattended upgrades on Ubuntu and its derivatives, run the following command:
$ sudo dpkg-reconfigure unattended-upgrades
- Install
net-tools
on the host using the following commands:- For Ubuntu:
$ sudo apt-get install -y net-tools
- For CentOS and Redhat:
$ sudo yum install net-tools -y
- For Ubuntu:
For Ubuntu 22 only:
- Edit the file
–sudo vi
/etc/default/grub
:- Modify the values from
GRUB_CMDLINE_LINUX=””
toGRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=no"
- If the above default values are not there, add the line
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=no"
- Modify the values from
- Execute the following commands:
sudo update-grub
sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
sudo reboot
Running the BloxOne Install Script
Complete the following steps to download and run the BloxOne install script:
- Go to Administration > Downloads.
- Go to the On-Prem Hosts pane and select Download BloxOne install script.
- Execute the downloaded script on Bare-Metal with the following command:
./bloxone.sh -j <JOIN_TOKEN>
Optional Parameters:
-p | --proxy Proxy in the format http://<proxy_host>:<proxy_port>
-r | --remove Remove BloxOne from the host.