Versions Compared

Version Old Version 1 New Version 2
Changes made by

Panna .

Panna .

Saved on

Key

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

...

COVER PORT INFORMATION. CAPTURE DETAILS FROM UPGRADE FAILED CUSTOMER TICKETS. AJITH AND SANTHOSH TO PROVIDE.

NIOS 9.0.

...

4 Upgrade Prerequisites

Read the following prerequisites before upgrading to NIOS 9.0.5:

...

nameNIOS 9.0.5 Upgrade Prerequisites

...

NIOS 9.0.5 and later is on an average 178% larger than NIOS 8.6 and 67% larger than earlier NIOS 9.0.x versions because of the new features/enhancements (such as Threat Insight). Uploading the .bin file may take a while and if you have set a default session timeout, the session can expire when the upload is taking place in the background. Infoblox recommends that you change the default session timeout setting from 600 seconds to 1800 seconds.  You can update the setting in the Security tab > Session Timeout(s) field. LINK TO KB ARTICLE.

...

If the Threat Insight service is enabled, before upgrading to NIOS 9.0.5 and later, read the KB article 000010304 to understand how to manage the feature functioning correctly post upgrade.

...

In NIOS 9.0.5 and later, upgrade fails if the listen-on, notify-source, and query-source options are configured with port 53 for both IPv4 and IPv6 addresses.

...

Accelerated networking can be enabled for NIOS members in Microsoft Azure from version 9.0.5 onwards. This resolves an issue where accelerated networks had to be disabled on NIOS members in Microsoft Azure before upgrading to NIOS 9.0.0, 9.0.1, 9.0.2, 9.0.3, or 9.0.4.

...

If you have enabled Accelerated networking or enabled SRIOV on NIOS members in Microsoft Azure, Infoblox requires you to upgrade to NIOS 9.0.5 or later.

...

There will be an impact on the CPU and DNS performance when Threat Insight is enabled. 

...

You can only run Threat Insight when a minimum disk size of 250 GB is set on the Grid member; the size includes upgrading with Threat Insight enabled on the member. Failing to do so may result in functionality issues.

...

If you have used the ZSK or KSK algorithm key size 640 (which is invalid in BIND 9.16), the upgrade may fail.

...

4:

Excerpt
nameNIOS 9.0.4 Upgrade Prerequisites

  • From NIOS 9.0.4 onwards, the CPUID hypervisor bit (CPUID(1)ECX:31 must be enabled for VM guests. It is the default for all VM hypervisors, but can be disabled in some hosting configurations.  Do not disable it.

  • Splunk does not support TLS version 1.3 and therefore NIOS reporting will not work if you disable all other TLS versions and enable only TLS version 1.3. A warning to this effect is displayed if you enable only TLS version 1.3.

  • Accelerated networking must be disabled in Microsoft Azure for NIOS members before upgrading to 9.0.0, 9.0.1, 9.0.2, 9.0,3 or 9.0.4 as it may cause the member to not rejoin the Grid after upgrading. The VM or, if applicable, all VMs within the availability set may need to be stopped or deallocated before accelerated networking is disabled. This issue does not affect NIOS 9.0.5 or later versions.

  • After an upgrade to NIOS 9.0.4 or later, the Cloud Sync service starts automatically on members that have AWS and GCP vDiscovery jobs configured.

  • After an upgrade to NIOS 9.0.4 or later, the Cloud Sync service will not start automatically on members that have VMWare, Azure, and Openstack vDiscovery jobs configured.

  • Before upgrading to NIOS 9.0.4 or later, Amazon Route 53 requires the AmazonRoute53ReadOnlyAccess permission for synchronization of data. Otherwise, add the following actions explicitly to the permission:

    • route53:GetHostedZone

    • route53:ListHostedZones

    • route53:ListResourceRecordSets

    • route53:ListTagsForResources

    • route53:ListQueryLoggingConfigs

    • route53:GetHealthCheck

...