...
- 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,, then 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.
- Make sure to check or enable IPAM Metadata/DHCP Lease Information in the traffic flow LOG TYPE for the traffic flow(s) for NIOS source to When configuring a Traffic Flow Configuration in the Cloud Services Portal with NIOS as a source, you can ensure better correlation and visibility by enabling 'IPAM Metadata/DHCP Lease Information' as a source log type.