Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current Restore this Version View Version History

Version 1 Next »

This section details features that are impacted by a NIOS upgrade and guidelines that you must follow before the upgrade.

  • 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.

  • If you are using Ubuntu and a CA certificate of key length 1024 and some unsupported ciphers, after a NIOS upgrade, services that depend on the unsupported ciphers cease to work.

  • If you are logging on to NIOS using SSO, in IDP Configuration you must enter the following
    URL in the SP Entity ID field: <grid_virtual IP address>:8765/metadata. If you are using Okta,
    the SP Entity ID field is also called the Audience URI field.

  • Before you upgrade to NIOS 9.0.x, check the validity of the CA certificates uploaded. If the certificate is invalid, install a new certificate that is in compliance with RFCs (for example RFC 5280). Failure to do so may result in the Grid Manager UI/WAPI not being accessible after the upgrade. However, NIOS will continue to be functional. To check the validity of the certificate, contact Infoblox Support.

  • If there are Threat Protection members in your Grid, for features such as Grid Master Candidate test promotion, forwarding recursive queries to Infoblox Threat Defense Cloud, and CAA records to function properly, ensure that you upload the latest Threat Protection ruleset.