Warning |
---|
...
Important NoteThe minimum system requirements specified for |
...
NIOS-X servers must be dedicated to the |
...
server you plan to deploy. They cannot be shared with or used for other non-Infoblox |
...
servers. Doing so will negatively affect the performance of your |
...
Infoblox Platform services. For information about the minimum system requirements and port usage, see the following: |
...
...
...
...
To ensure a successful deployment of hostsNIOS-X servers, consider the following best practices:
For
...
Infoblox Platform
When connecting a
hardware applianceNIOS-X physical server to the
Cloud ServicesInfoblox Portal, ensure that you DO NOT enter the join token
inusing the Device UI. Otherwise, the
applianceserver will lose connectivity to the
Cloud ServiceInfoblox Portal when the
hostserver certificate expires. Instead, use the serial number of the
applianceserver to connect to the
Cloud ServiceInfoblox Portal.
When you deploy a
hostNIOS-X server as a container and plan to run DNS forwarding proxy and
BloxOneUniversal DDI on the same
hostserver, ensure that port 1053 is open and available. Otherwise, you might encounter an error if the
hostserver OS is running other applications on port 1053.
When setting up DNS forwarding proxies as
hostsNIOS-X servers for failover purposes, Infoblox recommends that you deploy two DNS forwarding proxies using one as the primary proxy and the other as the secondary.
If you have configured any DNS name servers through the DHCP options or
hostsNIOS-X servers, ensure that you point them to the DNS forwarding proxies.
If you change the IP address or make any configuration changes on the
hostNIOS-X server outside of the
Cloud ServicesInfoblox Portal, you must restart the system for the change to take effect. If the change is made within the
BloxOne CloudInfoblox Platform infrastructure, no restart is required.
For DNS to function properly in OVA deployments on ESXi servers, ensure that you enable
thethe Synchronize guest time with
host optionserver option during the deployment and that your ESXi
hostserver is synchronized with the NTP server. If you do not select
thethe Synchronize guest time with
host optionserver option (or if this option is disabled), the
hostNIOS-X server synchronizes with the Ubuntu NTP servers: ntp.ubuntu.com and ubuntu.pool.ntp.org. When you disable this option, ensure that you open the UDP 123 port for time synchronization with the Ubuntu NTP servers. For more information, see Synchronizing Time with NTP Servers.
When you enable hosts to BloxOne Cloud NIOS-X servers to Infoblox Platform on a NIOS appliance-X physical server, the QPS (query per second) throughput might vary, depending on your appliance server models and the cache hit ratios. You might see a bigger performance impact when the cache hit ratio is lower. In general, NIOS can forward at least 3,500 QPS to BloxOne CloudInfoblox Platform. For standalone installations, the QPS may vary depending on the hardware used and the cache hit. However, the number of queries per second should fall in the range of 3,500 QPS using an OVA with 512 MB memory and 1 CPU.
- BloxOne
Infoblox Platform has configured
hosts52.119.40.100
as the default DNS resolver for allNIOS-X servers, so you are not required to configure a local DNS resolver. However, if you do not want to use
52.119.40.100
as the default DNS resolver and you do not want Docker to resolve DNS queries using8.8.8.8
or8.8.4.4
, you must configure at least one non-local DNS resolver. If you use only local DNS resolvers, Docker will resolve DNS queries using8.8.8.8
or8.8.4.4
. Note that Infoblox does not recommend using the loopback address (127.0.0.1
) when configuring a non-local DNS resolver.
Note |
---|
Note |
For
...
Universal DDI
When connecting a
hardware applianceNIOS-X physical server to the
Cloud ServicesInfoblox Portal, ensure that you DO NOT enter the join token in the Device UI. Otherwise, the
applianceserver will lose connectivity to the
Cloud ServiceInfoblox Portal when the
hostserver certificate expires. Instead, use the serial number of the
applianceserver to connect to the
Cloud ServiceInfoblox Portal.
When you deploy a
hostNIOS-X server as a container and plan to run DNS forwarding proxy and
BloxOneUniveral DDI on the same
hostserver, ensure that port 1053 is open and available. Otherwise, you might encounter an error if the
hostserver OS is running other applications on port 1053.
For any
hostNIOS-X server using the
BloxOneUniversal DDI capabilities, the interface should be reachable through LAN/WAN for queries from external clients to be resolved.
When setting up DNS forwarding proxies as
hostsNIOS-X servers for failover purposes, Infoblox recommends that you deploy two DNS forwarding proxies using one as the primary proxy and the other as the secondary.
If you have configured any DNS name servers through the DHCP options or
hostsNIOS-X servers, ensure that you point them to the DNS forwarding proxies.
If you change the IP address or make any configuration changes on the
hostNIOS-X server outside of the
Cloud ServicesInfoblox Portal, you must restart the system for the change to take effect. If the change is made within the
BloxOne CloudInfoblox Platform infrastructure, no restart is required.
For DNS to function properly in OVA deployments on ESXi servers, ensure that you enable the Synchronize guest time with
hostNIOS-X server option during the deployment and that your ESXi
hostserver is synchronized with the NTP server. If you do not select the Synchronize guest time with
hostNIOS-X server option (or if this option is disabled), the
hostNIOS-X server synchronizes with the Ubuntu NTP servers: ntp.ubuntu.com and ubuntu.pool.ntp.org. When you disable this option, ensure that you open the UDP 123 port for time synchronization with the Ubuntu NTP servers. For more information, see Synchronizing Time with NTP Servers.
- BloxOne
Infoblox Platform has configured
all hosts52.119.40.100
as the default DNS resolver forall NIOS-X servers, so you are not required to configure a local DNS resolver. However, if you do not want to use
52.119.40.100
as the default DNS resolver and you do not want Docker to resolve DNS queries using8.8.8.8
or8.8.4.4
, you must configure at least one non-local DNS resolver. If you use only local DNS resolvers, Docker will resolve DNS queries using8.8.8.8
or8.8.4.4
. Note that Infoblox does not recommend using the loopback address (127.0.0.1
) when configuring a non-local DNS resolver.
Note | |
---|---|
title | NoteDNS uses both TCP and UDP ports. Therefore, the interface must have both TCP and UDP available. |
For Data Connector
When connecting a
...
NIOS-X physical server to the
...
Infoblox Portal, ensure that you DO NOT enter the join token in the Device UI. Otherwise, the
...
server will lose connectivity to the
...
Infoblox Portal when the
...
server certificate expires. Instead, use the serial number of the
...
server to connect to the
...
Infoblox Portal.
To change the IP address of the
...
NIOS-X server 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
...
NIOS-X server on a container and not on a VM, manually clean up the /Infoblox directory on the
...
server 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
...
NIOS-X server through the
...
Infoblox Portal.
To reduce data transfer that takes place when IPAM metadata is synchronized between the Grid, Data Connector, and the
...
Infoblox Platform destination, enable NIOS Object Change Tracking. When you enable this feature, the
...
NIOS-X server 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
...
sever CPU Usage,
...
Server Disk, Usage, and
...
Server Memory Usage should be configured at less than 75%. For details on configuring application notification settings in the
...
Infoblox Portal, see Configuring Notification Settings.