Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

For the successful deployment of a Data Connector consider the following best practices:

  • Before you deploy the Data Connector, ensure that the host that you intend to attach the Data Connector service to meets the minimum system requirements, and has access to the appropriate ports and IPs as specified in the prerequisites section of this guide.

  • For Bare-metal deployments, make sure that the Secure Shell SSH port on the host is changed from default port 22 to a different port address as the default port is used internally by Data Connector when NIOS is the source.

  • Do not run any other services on the host where the Data Connector service is running.

  • Always use high capacity - 750 GB BloxOne image for Data Connector.

  • The Data Connector VM has two hard disk drives. Hard Disk 2 is used for data storage, and you may substitute it for a larger drive to expand the data storage space.
  • Infoblox recommends that customers use the list of publicly used IP addresses found on the Data Connector Admin guide to determine the needed access to the internet.
  • If you need to change the IP address of the host after the configuration, you must restart the system for the change to take effect.
  • For the Data Connector service to function properly in OVA deployments on ESXi servers, ensure that you specify the NTP server during deployment. If you do not specify the NTP server, ensure that you open the UDP 123 port for time synchronization with the Ubuntu NTP servers.
  • If you need to re-deploy a Data Connector service as a container on the same host, you must manually clean up the /Infoblox directory on the host before re-deploying Data Connector.

  • Optionally, you can add ETL (Extract, Transform, Load) filters to extract specific source data before Data Connector sends the data to the configured destinations, or sends specific data to the destination depending on the ETL expression added in traffic flow.

Best practices when using Data Connector with NIOS:

  • The NIOS Grid User added in the Data Connector configuration should have API access and we recommend adding a Superuser as the Data Connector would send WAPI calls to the NIOS Grid Master to fetch some data depending on the configuration.
  • Make sure that Object Tracking is enabled in the NIOS Grid if the Data Connector is configured to pull IPAM metadata /DHCP lease information from NIOS.
  • When using FQDN instead of the IP address in either NIOS source/Destination, make sure that BloxOne host as a local resolver is added that can resolve the FQDN.
  • Multiple Data Connector deployments can be used to balance the load and optimize data transfer to Infoblox NIOS Reporting. Note that NIOS version 8.5.0 or higher is required.
  • If the Data Connector is transferring IPAM data from NIOS, to,, enable the NIOS Object Change Tracking feature to reduce the quantity of data transferred. When you enable this feature, the appliance tracks the changes that are made to NIOS objects and periodically synchronizes changed objects.


  • No labels