Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
titleImportant 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 Ubuntu 18 and Ubuntu 20 in which systemd-resolved is running, perform the following before deploying a host:

...

  • 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

Deploying Hosts in Docker

To deploy hosts in a Docker environment, complete the following:

...

In the Cloud Services Portal, go to Administration -> Downloads.

...

On the Downloads page, click Download Package for Docker, and then save the .tar.gz file on your system.

...

Set up the Docker environment on your system. Ensure that the Docker version is supported, as described in BloxOne Connectivity and Service Requirements and Port Usage for Bare-Metal HostsFor information about how to install Docker, refer to the Docker Documentation.

Download the Infoblox Docker image tar file to your server, and then execute the following command at root. Note that you must have root privileges to execute Docker commands.


...

The system displays the download process. The following is a sample display:

7cbcbac42c44: Loading layer [====================================>] 5.05 MB/5.05 MB
d6f064e063f6: Loading layer [====================================>] 2.218 MB/2.218 MB
f77e7ee6f8c6: Loading layer [====================================>] 69.11 MB/69.11 MB
fa005789404e: Loading layer [====================================>] 4.096 kB/4.096 kB
4024a9f13d19: Loading layer [====================================>] 12.05 MB/12.05 MB
70fdf570286f: Loading layer [====================================>] 4.608 kB/4.608 kB
e8b22bfeae7a: Loading layer [====================================>] 4.608 kB/4.608 kB
6fabe6521295: Loading layer [====================================>] 4.608 kB/4.608 kB
5f70bf18a086: Loading layer [====================================>] 1.024 kB/1.024 kB
Loaded image: infobloxcto/onprem.agent:x.x.xx

...

Execute the following command to verify that the Infoblox Docker image has been downloaded properly:

# docker images
REPOSITORY                   TAG      IMAGE ID        CREATED         SIZE

infobloxcto/onprem.agent    3.1.xx    68f5ed0a1645    20 hours ago    96.9MB

...

On the Docker system, execute the following command:

No Format
sudo docker run -d \
  --name blox.noa \
  --network=host \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -v /var/lib/infoblox/certs:/var/lib/infoblox/certs \
  -v /etc/onprem.d/:/etc/onprem.d/ \
  -v /etc:/mount/etc:ro \
  -v /usr/share/zoneinfo:/usr/share/zoneinfo:ro \
  infobloxcto/onprem.agent:<VERSION> \
  --jointoken $JOIN_TOKEN

Note:

You must use “blox.noa” as the container name. DO NOT change this. You can capture the onprem.agent Version in the “Loaded image” field when you download the Infoblox Docker image. Note that only Docker image version 19.03.5 or greater supports the join token option.

To be fully compatible with the BloxOne services, you must update the Docker daemon settings and set the log driver to "json-file." For more information, refer to the Docker documentation at https://docs.docker.com/config/containers/logging/configure/.

...

# docker ps

...

Running the BloxOne Install Script

  1. Complete the following steps to download and run the BloxOne install script. 
  2. Go to Administration > Downloads.
  3. Go to the On-Prem Hosts pane and select Download BloxOne install script.
  4. 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.