infoblox_uddi:nios_x_servers
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infoblox_uddi:nios_x_servers [2026/02/02 22:57] – [NIOS-X in Public Cloud] bstafford | infoblox_uddi:nios_x_servers [2026/03/07 02:47] (current) – [Repairing NIOS-X Server] bstafford | ||
|---|---|---|---|
| Line 30: | Line 30: | ||
| * VMware OVA = ESXi 5.5, 6.0 and 6.5. VM can be 1 core with 0.5 GB RAM but will default to 4 cores and 8 GB RAM. I run my home lab pair of B1DDI/B1TD on 1 core and 0.5Gb of RAM. | * VMware OVA = ESXi 5.5, 6.0 and 6.5. VM can be 1 core with 0.5 GB RAM but will default to 4 cores and 8 GB RAM. I run my home lab pair of B1DDI/B1TD on 1 core and 0.5Gb of RAM. | ||
| * BloxOne B1-105 Appliance. Compact. Fanless. Zero-Touch Provisioning. Connected back to CSP automatically. Infoblox add them to the appropriate portal as part of the sales process. | * BloxOne B1-105 Appliance. Compact. Fanless. Zero-Touch Provisioning. Connected back to CSP automatically. Infoblox add them to the appropriate portal as part of the sales process. | ||
| + | |||
| + | ===== NIOS-X Server Objects ===== | ||
| + | What gets considered as a Server Object when it comes to sizing the number of objects on a NIOS-X Server | ||
| + | * DNS Views | ||
| + | * DNS Zones | ||
| + | * DNS Authoritative Zones | ||
| + | * DNS Delegation Zones (Feb 2026, currently counted as NS record) | ||
| + | * DNS Forward Zones | ||
| + | * DNS Secondary Zones | ||
| + | * DNS RPZ Zones (Feb 2026, currently counted as Auth Zone) | ||
| + | * DNS Records | ||
| + | * A Records | ||
| + | * AAAA Records | ||
| + | * CAA Records | ||
| + | * CNAME Records | ||
| + | * DHCID Records | ||
| + | * DNAME Records | ||
| + | * HTTPS Records | ||
| + | * MX Records | ||
| + | * NAPTR Records | ||
| + | * NS Records | ||
| + | * PTR Records | ||
| + | * SOA Records | ||
| + | * SRV Records | ||
| + | * SVCB Records | ||
| + | * TXT Records | ||
| + | * UNKNOWN Records | ||
| + | * RPZ Record (Policy Rule) | ||
| + | * Subnets | ||
| + | * DHCP Ranges | ||
| + | * Leases | ||
| + | * Fixed Addresses | ||
| + | * Reservations | ||
| + | * Note: While the network IP address and broadcast IP address of every subnet in the Infoblox Portal counts towards Management Tokens, they are not counted towards server object count on NIOS-X. | ||
| + | * Fingerprints | ||
| + | |||
| + | - DHCP Exclusion Ranges | ||
| + | - Note: DHCP Exclusion Ranges are not counted as server objects directly | ||
| + | - Note: If a DHCP Exclusion Range consists of 20 or fewer IP addresses, then each IP address is represented in the DHCP config as a reservation with a multicast MAC address (03-xx-xx-xx-xx-xx). These reservations are added to the server object count but do NOT get counted for Management Tokens. Only the single Exclusion Range gets counted for Management Tokens. | ||
| + | - Note: If the DHCP Exclusion Range consists of 21 or more IP addresses, then the parent range is split into two ranges either side of the Exclusion Range. Both ranges will be added to the server object count but only the single range seen in the Infoblox Portal will be counted for Management Tokens. Only the single Exclusion Range gets counted for Management Tokens. | ||
| + | |||
| + | A DNS Zone or DNS Record is counted towards the server object count of a NIOS-X server if, and only if, that NIOS-X server is authoritative for that Zone/ | ||
| + | |||
| + | While a secondary zone counts as a “server object”, the contents (records) of that zone do not count towards “server object” of NIOS-X regardless of whether the Infoblox Portal enables visibility of the secondary zone data. Visibility of secondary zone data will impact Management Token count. | ||
| + | |||
| + | A subnet/ | ||
| + | |||
| + | A fixed address, reservation, | ||
| + | For DHCP active-active mode, active-passive mode, advanced active-passive mode, and hub-spoke mode, a lease on the HA pair is added to the server object count on both NIOS-X members in the HA pair. The lease will be considered a single lease when counted as an Active IP address for Management tokens. | ||
| + | |||
| + | Example: 5 “spoke” sites have 100 leases which means they have 100 lease server objects each. The Hub NIOS-X server will have 500 lease server objects. | ||
| ===== Dig Testing ===== | ===== Dig Testing ===== | ||
| Line 38: | Line 89: | ||
| The following will only work when querying from a public IP that is in an External Network definition in your Infoblox Threat Defense Tenant. | The following will only work when querying from a public IP that is in an External Network definition in your Infoblox Threat Defense Tenant. | ||
| < | < | ||
| + | ===== NIOS-X API Monitor ====== | ||
| + | You can monitor NIOS-X servers via API. SNMP is not supported. Docs [[infoblox: | ||
| + | |||
| + | ===== NIOS-X Server Size ===== | ||
| + | Changing the size of a NIOS-X server by editing it has no impact on the operations of that NIOS-X server (i.e. no config changes, no service reboots, etc) | ||
| ===== NIOS-X Server Deployment ===== | ===== NIOS-X Server Deployment ===== | ||
| ==== Best Practice ==== | ==== Best Practice ==== | ||
| Line 76: | Line 132: | ||
| If you are deploying a Data Connector host (VMware), increase the disk size of the BloxOne host to 750 GB before booting it for the first time. | If you are deploying a Data Connector host (VMware), increase the disk size of the BloxOne host to 750 GB before booting it for the first time. | ||
| + | |||
| + | ==== Multiple Interfaces ==== | ||
| + | [[https:// | ||
| + | |||
| + | WAN interface means the interface can be used to phone home to the Infoblox Portal. LAN interface means that the interface will not be used for Infoblox Portal connectivity. | ||
| + | |||
| + | If a physical or virtual server has multiple interfaces configured, syslog traffic will always be sent through the MGMT/WAN interface on the host. You cannot modify this interface. [[https:// | ||
| ==== Enabling Services ==== | ==== Enabling Services ==== | ||
| When you enable services on a NIOS-X host, the docker image is downloaded from the cloud to the NIOS-X hosts. This is why it can take a while to deploy (especially on slow networks). Disabling service will cause the container to be removed. It might be able to use cached image if you restart quickly. If it has been a while, the download image will have been purged. | When you enable services on a NIOS-X host, the docker image is downloaded from the cloud to the NIOS-X hosts. This is why it can take a while to deploy (especially on slow networks). Disabling service will cause the container to be removed. It might be able to use cached image if you restart quickly. If it has been a while, the download image will have been purged. | ||
| Line 139: | Line 202: | ||
| Run PowerShell as administrator and convert the downloaded VHD file from dynmaic-size to fixed-size with: | Run PowerShell as administrator and convert the downloaded VHD file from dynmaic-size to fixed-size with: | ||
| < | < | ||
| + | ===== NIOS-X OS ===== | ||
| + | March 2026 saw the release of NIOS-X 4.0.0 image. This runs Ubuntu 24.04. Older 3.x images run Ubuntu 20.04.3 (with extended security support). | ||
| + | |||
| + | Servers running 3.x cannot upgrade to 4.0. The VM must be redeployed. Hardware must be flashed from USB. B1-105 does not support new image. | ||
| ===== Repairing NIOS-X Server ===== | ===== Repairing NIOS-X Server ===== | ||
| The B1-105 appliance can be rebuilt using the ISO image that is available for the Dell VEP servers. | The B1-105 appliance can be rebuilt using the ISO image that is available for the Dell VEP servers. | ||
infoblox_uddi/nios_x_servers.1770073026.txt.gz · Last modified: by bstafford