...
| Note | ||
|---|---|---|
| ||
DNS uses both TCP and UDP ports. Therefore, the interface must have both TCP and UDP available. |
For Data Connector
- To change the IP address of the host after configuring it on a VM, restart the system; this is necessary for the change to take effect.
- To redeploy Data Connector on the same host on a container and not on a VM, manually clean up the /Infoblox directory on the host before redeploying Data Connector.
- For Data Connector to function properly in OVA deployments on ESXi servers, specify the NTP server during deployment. If you do not specify the NTP server, then open the UDP 123 port for time synchronization with the Ubuntu NTP servers. For more information, see Synchronizing Time on the ESXi Servers.
- Before deploying Data Connector, prepare your environment according to the requirements for the supported platforms, and open all ports necessary for unrestricted outbound access. When deploying Data Connector, configure it as a host through the Cloud Services Portal.
- To reduce data transfer that takes place when IPAM metadata is synchronized between the Grid, Data Connector, and the BloxOne destination, enable NIOS Object Change Tracking. When you enable this feature, the appliance tracks the changes made to NIOS objects and periodically synchronizes changed objects. For more information on NIOS, see the Infoblox NIOS Guide.
Threshold levels for Host CPU Usage, Host Disk, Usage, and Host Memory Usage should be configured at less than 75%. For details on configuring application notification settings in the Cloud Services Portal, see Configuring Notification Settings.