Versions Compared

Old Version 27

changes.mady.by.user Jyothi KP

Saved on

compared with

New Version 28

changes.mady.by.user Jyothi KP

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed about the HA support limitation on IB-V825 as it would be valid from 9.0.4 onwards.

...

  • DHCP failover does not work in environments with NAT configuration. When configuring a DHCP failover, ensure that the primary and secondary DHCP servers are not in NAT-configured environments.

  • The GMC (Grid Master Candidate) promotion test does not work in NAT-configured environments. Although the promotion fails the test, the GMC promotion operation completes successfully. For the promotion to pass the test, the GMC member and the other members in the Grid must not include the NAT configuration.

  • If you need to set a static IP address on the MGMT interface when configuring a vNIOS instance with multiple interfaces (LAN1 and MGMT), set it from the Grid Manager UI; for steps, refer to the Infoblox NIOS documentation. If you try to set the IP address from the NIOS CLI, the set interface mgmt command will fail to enable the MGMT interface, because NIOS assumes that the LAN1 IP address of a vNIOS instance deployed on any cloud platform is always dynamic.

  • Use the vNIOS for Azure appliances to provide DHCP services for networks on platforms other than Azure (Azure Public Cloud and Azure Stack Hub) because networks on Azure obtain their IP leases from the native DHCP servers even though NIOS is configured to provide DHCP services.

  • vNIOS for Azure instances do not support HA configuration and LAN2 interfaces.

  • vNIOS for Azure does not support the use of Weighted Random Early Detection (WRED) mechanism in network schedulers because the Elastic Network Adapter (ENA) poll-mode driver does not provide the API required for 100 Gbps ENA interfaces and also because the ixgbevf driver for the Intel NIC 82599 SR-IOV on Azure does not provide the API required for the 10 Gbps SR-IOV interfaces.

  • vNIOS for Azure Public Cloud:

    • Azure Public Cloud does not support IPv6 network configuration.

  • vNIOS for Azure

    Public Cloud on IB-V825 appliances does not support high availability (HA).

    vNIOS for Azure Stack Hub:

    • Azure Stack Hub is supported only from NIOS 8.6.1 onwards. Ensure that you do not downgrade or auto-sync to a NIOS version that is earlier than 8.6.1.

    • Azure Stack Hub does not support IPv6 network configuration.

    • vNIOS for Azure Stack Hub appliances are not available for deployment from the Microsoft Azure Stack Hub Marketplace.

    • vNIOS for Azure Stack Hub appliances do not support vDiscovery.

    • In the current release, in Grid Manager, the Platform column on the Members tab displays the platform of a vNIOS for Azure Stack Hub member as Azure instead of Azure Stack Hub.

    • If you are using an Azure Stack Hub version earlier than 1.2102.28.87, sometimes, a vNIOS for Azure Stack Hub instance deployed from the Azure CLI might go to a Failed state. To fix this, redeploy the instance from the Azure Stack Hub portal. For more information, see Deploying a VM instance from the Microsoft Azure Stack Hub portal.

    • When deploying vNIOS for Azure Stack Hub, you might notice that some characters are missing in the messages displayed in the serial console log. This occurs because the default baud rate in Azure Stack Hub is 115200 and the default baud rate in NIOS is 9600.