Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The NIOS 8.6 release includes the following new features and enhancements:

vNIOS for VMware on ESX/ESXi Servers

The Infoblox vNIOS on VMware software can run on ESX or ESXi servers that have DAS (Direct Attached Storage),or iSCSI (Internet Small Computer System Interface) or FC (Fibre Channel) SAN (Storage Area Network) attached.
You can install the vNIOS software package on a host with VMware ESX or ESXi 7.0.3, 7.0.2, 7.0, 6.7, 6.5.x, 6.0.x installed, and then configure it as a virtual appliance. Note that VMware ESX/ESXi 7.0 is not supported on NIOS versions earlier than 8.5.3.
vSphere vMotion is also supported. You can migrate vNIOS virtual appliances from one ESX or ESXi server to another without any service outages. The migration preserves the hardware IDs and licenses of the vNIOS virtual appliances. VMware Tools is automatically installed for each vNIOS virtual appliance. Infoblox supports the controlbfunctions in VMware Tools. For example, through the vSphere client, you can shut down the virtual appliance. You can deploy certain vNIOS virtual appliances with different hard disk capacities. Some vNIOS appliances are not supported as Grid Masters or Grid Master Candidates. For more information about vNIOS on VMware, refer to the /wiki/spaces/NVIGdraft/overview.

vNIOS for Microsoft Server 2019 and 2016 Hyper-V

The Infoblox vNIOS virtual appliance is now available for Windows Server 2019 and Windows Server 2016 that have DAS (Direct Attached Storage). Administrators can install vNIOS virtual appliance on Microsoft Windows® servers using either Hyper-V Manager or SCVMM. A Microsoft Powerscript is available for ease of installation and configuration of the virtual appliance. Note that for optimal performance, vNIOS for Hyper-V is not recommended as a Grid Master or Grid Master Candidate. For more information about vNIOS for Hyper-V, refer to the Infoblox Installation Guide vNIOS for Microsoft Hyper-V.

Note
titleNote

NIOS virtual appliance for Hyper-V is not recommended as a Grid Master or Grid Master Candidate.

vNIOS for KVM Hypervisor

The Infoblox vNIOS for KVM is a virtual appliance designed for KVM (Kernel-based Virtual Machine) hypervisor and KVM-based OpenStack deployments. The Infoblox vNIOS for KVM functions as a hardware virtual machine guest on the Linux system. It provides core network services and a framework for integrating all components of the modular Infoblox solution. You can configure some of the supported vNIOS for KVM appliances as independent or HA (high availability) Grid Masters, Grid Master Candidates, and Grid members. For information about vNIOS for KVM hypervisor, refer to the Infoblox Installation Guide for vNIOS for KVM Hypervisor and KVM-based OpenStack.

Note
titleNote

KVM-based OpenStack deployments are supported on the Wallaby RHOSP 16.2, 16.1, 16.0, Victoria (over Ubuntu), Wallaby (over Ubuntu) platforms.

vNIOS for AWS (Amazon Web Services)

The Infoblox vNIOS for AWS is a virtual Infoblox appliance designed for operation as an AMI (Amazon Machine Instance) in Amazon VPCs (Virtual Private Clouds). You can deploy large, robust, manageable, and cost effective Infoblox Grids in your AWS cloud, or extend your existing private Infoblox NIOS Grid to your virtual private cloud resources in AWS. You can use vNIOS for AWS virtual appliances to provide carrier-grade DNS and IPAM services across your AWS VPCs. Instead of manually provisioning IP addresses and DNS name spaces for network devices and interfaces, an Infoblox vNIOS for AWS instance can act as a standalone Grid appliance to provide DNS services in your Amazon VPC, as a virtual cloud Grid member tied to an on-premises (non-Cloud) NIOS Grid, or as a Grid Master synchronizing with other AWS-hosted vNIOS Grid members in your Amazon VPC; and across VPCs or Availability Zones in different Amazon Regions. For more information about vNIOS for AWS, refer to the

Infoblox Installation Guide for vNIOS for AWS.

vNIOS for Azure

The Infoblox vNIOS for AWS is a virtual Infoblox appliance designed for operation as an AMI (Amazon Machine Instance) in Amazon VPCs (Virtual Private Clouds). You can deploy large, robust, manageable, and cost effective Infoblox Grids in your AWS cloud, or extend your existing private Infoblox NIOS Grid to your virtual private cloud resources in AWS. You can use vNIOS for AWS virtual appliances to provide carrier-grade DNS and IPAM services across your AWS VPCs. Instead of manually provisioning IP addresses and DNS name spaces for network devices.

vNIOS for GCP

Infoblox vNIOS for GCP is an Infoblox virtual appliance that enables you to deploy robust, manageable, and cost effective Infoblox appliances in the Google Cloud. Infoblox vNIOS provides core network services and a framework
for integrating all the components of the modular Infoblox solution. It provides integrated, secure, and easy-to manage DNS (Domain Name System) and IPAM (IP address management) services. For more information, see the Infoblox Installation Guide for vNIOS for GCP.

vNIOS for Nutanix AHV

Infoblox vNIOS for Nutanix enables you to deploy large, robust, manageable, and cost-effective Grids. Infoblox NIOS virtual appliance for Nutanix functions as a hardware virtual machine guest on the Linux system. It provides integrated, secure, and easy-to-manage DNS, DHCP, and IPAM services and a framework for integrating all the components of the modular Infoblox solution. For more information, see the Infoblox Installation Guide vNIOS for Nutanix AHV.

vNIOS for Red Hat OpenShift

Infoblox vNIOS for Red Hat OpenShift is a virtual appliance designed for deployment on Red Hat® OpenShift®, an enterprise-ready Kubernetes container platform. The virtual appliance enables you to deploy large, highperformance,
robust, manageable, and cost-effective Infoblox Grids. The NIOS virtual appliance for Red Hat OpenShift functions as a virtual machine running on KubeVirt virtualization. It provides integrated, secure, and easy to-manage DNS and DHCP services. For more information, see the Infoblox Installation Guide vNIOS for Red Hat OpenShift.

vNIOS for Oracle Cloud Infrastructure

...

Bypassing Subscriber Secure Policy for Allowed Lists (RFE-11652)

NIOS 8.6.3 introduces the Enable Subscriber Secure Policy Bypass for Allowed list and the Set Global Allow List RPZ index range ( 0 to 30) options in which subscriber specific allow domains take priority over category based policies (content-filtering), security policies and blocklist entries. Subscriber specific block domains take priority only over category-based policies (content-filtering).

The Enable Subscriber Secure Policy Bypass for Allowed list checkbox enables NIOS to generate a normal response for all domains in a subscriber’s allowed list. Allowed domains will override RPZ rules if any (for example, NXDOMAIN), and categorization policy rules for the subscriber. This enables subscribers to override all policies for a specific domain.
The Set Global Allow List RPZ index range ( 0 to 30) checkbox adds a domain to an RPZ specified as a passthru RPZ rule, and that domain is also added as a global allowed list. NIOS 8.6.3 also introduces a new report called Daily Report on Subscriber Information and DNS Queries matching with ABLs that displays the overall subscriber information and DNS domain queries that match the queried domains in the allow and block lists. For more information about these options, see the Scaling Subscriber Sites topic in the NIOS 8.6 online documentation.

Validating Certificates (SPTYRFE-52)

NIOS 8.6.3 introduces the Grid > Certificates > Validate Certificates option that validates all certificate uploaded using the Manage Certificates option and also validates DNS Traffic Control HTTPS health monitor certificates. It displays the certificates to be either valid, invalid, or expired. It displays warning messages for expired certificates and for certificates with no SKI (Subject Key Identifier). For more information, see the Validating Certificates topic in the NIOS 8.6 online documentation.

ZVELO Category Database Update Failure Changes (RFE-12140)

If a ZVELO category database update failure occurs for three consecutive days:

  • Grid Manager displays a yellow background with the "Please correct the download credentials or the proxy configuration to get the latest database updates" message and the member status is displayed as "Domain category db is not latest" in the Grid Manager > Subscriber Collection > Services > Service Status column.
  • A new SNMP trap is sent with the message "Domain category db is not latest". Additionally, if email notifications are configured, an email is sent to the configured email address with the "Domain category db is not latest" message.
  • Post this event, if the ZVELO download is successful, a new SNMP clear trap is sent, and an email with the “zvelo SNMP Clear Trap” message is also sent. The Service Status column has a green background and the “Subscriber service is working” message is displayed.

If a ZVELO category database update failure occurs for more than 60 days:

  • Grid Manager displays a red background with the "zvelo database expired. Subscriber secure queries will be fail-open." message and the member status is displayed as "zvelo db has expired" in the Grid Manager > Subscriber Collection > Services > Service Status column.
  • A new SNMP trap is sent with the "zvelo db has expired" message. Additionally, if email notifications are configured, an email is sent to the configured email address, with the "zvelo db has expired" message.
  • Post this event, if the zvelo download is successful, a new SNMP clear trap is sent, and an email with the “zvelo SNMP Clear Trap” message is also sent. The Service Status column has green background and the “Subscriber service is working” message is displayed.

Support for Network Insight on the AWS and Microsoft Azure Public Cloud (RFE-10248)

Starting from NIOS 8.6.3, deployment of Network Insight appliances on Microsoft Azure and AWS public cloud is supported. You can use the discovery feature to detect devices in your network and manage device data from Grid Manager.

Filtering Options for vDiscovery

Starting from NIOS 8.6.3, you can configure vDiscovery jobs with CIDR-based filters to limit vDiscovery only to configured networks or to skip vDiscovery from excluded networks. For more information, see the Configuring vDiscovery Jobs topic in the the NIOS 8.6 online documentation.

Infoblox BloxConnect Changes

From NIOS 8.6.3 onwards, the Infoblox BloxConnect screen that appears when you first log in to Grid Manager will no longer be displayed. To better enhance the NIOS customer experience and for Infoblox to proactively respond to customer issues in a timely manner, BloxConnect data will be collected by default and the same data will be included in the support bundle. For information about the data collected, see https://insights.infoblox.com/resources-datasheets/infoblox-datasheet-infoblox-bloxconnect.

Synchronizing Amazon Route 53 Data from Multiple AWS Accounts (RFE-9382)

vNIOS for AWS is integrated with Amazon Route 53. You can now discover and synchronize Amazon Route 53 DNS data from multiple AWS accounts of an AWS organization to NIOS using a single NIOS admin account. For more information, see the Amazon Route 53 topic in the Installation Guide for vNIOS for AWS at https://docs.infoblox.com.

Support for Route 53 Integration on AWS GOV Cloud (RFE-11806)

Starting from NIOS 8.6.3, the vNIOS for AWS Route 53 integration is supported on AWS GOVCloud. For more information, see the Amazon Route 53 topic in the Installation Guide for vNIOS for AWS at https://docs.infoblox.com.

Support for Amazon EC2 R6i Instance Type (RFE-12312)

vNIOS for AWS instances running on NIOS 8.6.3 or later can be deployed on Amazon EC2 R6i instance types. For information about supported EC2 shapes and models, see the Infoblox vNIOS for AWS AMI Shapes and Regions topic in the Installation Guide for vNIOS for AWS at https://docs.infoblox.com.

Connecting to the Serial Console of an Amazon EC2 Instance (RFE-11803)

You can now connect to the serial console of a vNIOS for AWS EC2 instance that is deployed on an R6i instance type for troubleshooting purposes. For more information, see the Provisioning vNIOS for AWS Using the BYOL Model topic in the Installation Guide for vNIOS for AWS at https://docs.infoblox.com.

Support for EBS Encryption (RFE-11931)

vNIOS for AWS instances running on NIOS 8.6.3 or later versions of 8.6.x, support encryption of Amazon Elastic Block Storage volumes. For more information, see the For more information, see the Provisioning vNIOS for AWS Using the BYOL Model topic in the Installation Guide for vNIOS for AWS at https://docs.infoblox.com.

Enabling the SHA1 Encryption Algorithm for the NTP Key (RFE-8178)

In NIOS 8.6.3, you can add the SHA1 NTP authentication key before enabling the NTP service on the Grid. The key is a 40 character hexadecimal string and it uses a hash-based symmetric encryption algorithm. For more information, see the Using NTP for Time Settings topic in the NIOS 8.6 online documentation.

Exporting to CSV Before Deleting a Network (RFE-11846)

NIOS 8.6.3 introduces the Export & Delete button that allows you to export the network data into a CSV file before deleting a network. For more information, see the Exporting and Deleting Networks section in the Configuring IPv4 Networks topic in the NIOS 8.6 online documentation.

Reconnecting Groups After a Grid Master Candidate Promotion (RFE-4753)

In NIOS 8.6.3, you can reconnect groups after a Grid Master Candidate promotion thus giving you more control over the promotion and minimizing service outages by allowing you to group Grid members and schedule a time for the groups to reconnect to the newly promoted Grid Master. As soon as the scheduled time arrives, members of Grid Master Candidate groups reconnect to the newly promoted master. You can do this by using the Activate GMC Group Promotion Schedule option in the GMC Group Promotion Schedule editor. For more information, see the Managing a Grid topic in the NIOS 8.6 online documentation.

Device Handling Performance Optimization for NIOS Subscriber Cache (RFE-12397)

Device handling performance optimization optimizes the use of NIOS subscriber cache by updating only the provisioned devices to NIOS thereby reducing the number of devices delivered to the NIOS cache. For more information, see the Device Handling Performance Optimization for NIOS Subscriber Cache section in the Infoblox Subscriber Insight and Subscriber Policy Enforcement topic in the NIOS 8.6 online documentation.

Improvements in Internal Cache Handling (RFE-12003)

Fast replication now does not take place for all subscriber site members; instead, it takes place from a single member with a full cache thus greatly improving cache handling.

Discovering Juniper Mist Devices

You can now discover Juniper Mist devices using Network Insight. For more information, see the Configuring Discovery for SDN and SD-WAN topic in the NIOS 8.6 online documentation.

SHA-512 and SHA-256 Support in Network Insight (RFE-12053)

Network Insight now supports the SHA-512 and SHA-256 algorithms for SNMP polling.

AES-256 Support for SNMPv3 Authentication (RFE-10304)

From NIOS 8.6.3 onwards, the AES-256 encryption is supported for SNMPv3 authentication in Network Insight.

Converting Real-Time Alerts to Scheduled Alerts (RFE-12594)

In NIOS 8.6.3, alert types in NIOS Reporting for the new device discovery alert, security alert, and category alert have been converted from Real-time” to “Scheduled.

Enhancements in the DNS Object Count Trend and FLEX Grid Licensing Features Enabled Reports (RFE-11909)

In NIOS 8.6.3, certain changes have been implemented to the following reports:

  • Managed DDI features enabled
  • SPLA Grid Licensing Features Enabled
  • Managed DDI Peak IP Usage Trend
  • Managed Trend DNS Peak Usage
  • DNS Effective Peak Usage Trend for SPLA Grid License

Changes to these reports include:

  • All of these reports now also support non -IB-FLEX appliances.
  • All of these reports have the Members” and the “Reporting SPLA filters.
  • If you want to include a Grid member that does not have an extensible attribute in these reports, you must set the Reporting SPLA extensible attribute to Managed IB-FLEX’ or ‘Managed HW/SW depending on the Grid member type, and the Grid license must be flex_grid_ms.

Support for Microsoft Server 2022 (RFE-12246)

NIOS 8.6.3 supports Microsoft Server 2022.

Support for VMware ESXi 7.0.x (RFE-12555)

vNIOS for VMware is now supported on VMware ESX or ESXi versions 7.0.2 and 7.0.3.

Support for Nutanix AOS 6.x LTS (RFE-12650)

vNIOS for Nutanix™ AHV is now supported on NIOS 8.6.3, NIOS 8.6.2, and NIOS 8.5.5. For more information, see the Infoblox Installation Guide vNIOS for Nutanix AHV at https://docs.infoblox.com.

IB-FLEX Support for Nutanix AHV (RFE-12601)

vNIOS for Nutanix™ AHV is now supported on IB-FLEX appliances. For more information, see the Infoblox Installation Guide vNIOS for Nutanix AHV at https://docs.infoblox.com.

Virtual Advanced DNS Protection Software and Virtual DNS Cache Acceleration Support in vNIOS for Nutanix (RFE-12615)

vNIOS for Nutanix now supports virtual Advanced DNS Protection Software (vADP).

DHCP, IPv6, and HA Support in vNIOS for Red Hat OpenShift (RFE-12835)

vNIOS for Red Hat OpenShift can now manage DHCP, IPv6, and HA configurations. For more information, see the Infoblox Installation Guide vNIOS for Red Hat OpenShift at https://docs.infoblox.com.

Support for Upgraded Splunk Version 8.2.10

NIOS 8.6.3 supports Splunk version 8.2.10.

NIOS Enhancements to Support Consolidated Hotfixes

NIOS 8.6.3 introduces new enhancements to the implementation of hotfixes. NIOS 8.6.3 introduces the manifest file that is generated after the hotfix is successfully applied. The manifest file contains key details such as affected files, RPMs installed, and the best suggested action to activate changes. NIOS 8.6.3 also introduces CLI support to view the best suggested action to activate hotfix changes in the Grid member and to support the download of manifest files using WAPI and support bundles.

Enabling and Disabling DNS Traffic Control Objects (RFE-7088)

NIOS 8.6.2 introduces the Enable Traffic Management Objects and the Disable Traffic Management Objects screens using which you can enable or disable individual DNS Traffic Control objects. You can also disable the health monitoring of a particular object to stop performing health checks. You can access the new screens from the Traffic Control panel on the Data Management > DNS > Traffic Control tab. For more information about enabling and disabling DNS Traffic Control objects, see the Managing DNS Traffic Control Objects.

...

IB-V5005 support is now extended to vNIOS for Azure and vNIOS for AWS. For detailed information see the Infoblox Installation Guide for vNIOS for AWS and the Installation Guide for vNIOS for Microsoft Azure available at docs.infoblox.com.

...