/
VM Hypervisor (Hyper-V and KVM) Docker Deployment
Document toolboxDocument toolbox

VM Hypervisor (Hyper-V and KVM) Docker Deployment

Owned by Shirly Tsang
Last updated: Oct 25, 2023 by Gary Leicht

To deploy on-prem hosts by using Microsoft Hyper-V or KVM, do the following:

Note

Infoblox recommends that you use Docker version 19.03.5, to avoid an issue in which the Docker container might redeploy continuously, resulting in multiple deployments of the on-prem host. In addition, Kubernetes is not supported.

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

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

3. Install Linux on a hypervisor, such as Hyper-V or KVM.

4. Set up the Docker environment on Linux. For information about installing Docker, refer to the appropriate documentation for your system.

5. Download the Infoblox Docker image .tar file, and run the following command at the root:

Note

To run Docker commands, you must have root privileges. If you do not have them, you might encounter error messages while executing the commands.

# docker load -i <ActiveTrust_DFP_Docker_<VERSION>>.tar.gz
The system displays the download process. The following is an example:

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

6. to verify that the Infoblox Docker image has been downloaded properly, run the following command:

# docker images

REPOSITORY                   TAG       IMAGE ID        CREATED         SIZE
infobloxcto/onprem.agent    0.1.xx    68f5ed0a1645    20 hours ago    87.81 MB

7. On the docker system, run the following command:

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/ \
  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 19.03.5 or greater supports the jointoken option.

8. To verify that the Infoblox Docker container images are properly deployed on the system, run the following command:

# docker ps

You have now successfully deployed the on-prem host. It might take a couple of minutes for the proxy and BloxOne Cloud to connect. Once connected, the host starts collecting information from your on-prem devices and transmitting the data to BloxOne Cloud.

10. To check the current status of the proxy, go to Manage > On-Prem Hosts in the Cloud Services Portal. For more information, see Viewing On-Prem Host Status.

Related content