Page tree

Contents

Note

Before you start the deployment, complete the following:

  • Ensure that your Docker environment meets the minimum deployment requirements.
  • Ensure that there are no other processes using port 53 on the host system on which your on-prem host will be deployed. For example, some Ubuntu systems running local DNS cache (system-resolved) might occupy port 53, and your on-prem host might not function properly in this case.
  • Infoblox recommends that you use Docker version 17.09 or below (except for 17.05 and 17.06), or version 18.09 or above, to avoid an issue in which the Docker container might re-deploy continuously, resulting in multiple deployments of the on-prem host. In addition, Kubernetes is not supported.

To deploy on-prem hosts using the Infoblox Docker container, complete the following:

  1. In the Cloud Services Portal, go to Administration -> Downloads.
  2. On the Downloads page, click Download Package for Docker, and then save the .tar.gz file on your system.
  3. Set up the Docker environment on your system. Ensure that the Docker version is supported, as described in Deployment Requirements. For information about how to install Docker, refer to the Docker Documentation.
  4. Download the Infoblox Docker image tar file to your server, and then execute the following command at the root. Note that you must have root privileges to execute Docker commands.
    # docker load -i <BloxOne_OnPrem_Docker_<VERSION>.tar.gz

    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
  5. 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    0.1.xx    68f5ed0a1645    20 hours ago    87.81 MB
  6. On the Docker system, execute 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 version 3.1.11 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/.

  7. You can verify that the Infoblox Docker container images are properly deployed on the system by using the following command:
    # docker ps
  8. You have now successfully deployed your on-prem host. It might take a couple of minutes for the proxy and BloxOne Threat Defense Cloud to connect. Once connected, the host starts collecting information from your on-prem devices and transmit the data to BloxOne Threat Defense Cloud.

  9. To check the current status of the proxy, you can go to Manage -> On-Prem Hosts in the Cloud Services Portal. For more information about the host status see Managing On-Prem Hosts.
  • No labels

This page has no comments.