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.
Explain how customers should think about creating multiple traffic flows on the same 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.