Versions Compared

Old Version 6

changes.mady.by.user Jyothi KP

Saved on

compared with

New Version 7

changes.mady.by.user Jyothi KP

Saved on

Key

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

...

  • Storage account for BootDiagnostics: Select an existing account from the drop-down list or click Create new and create a Standard storage account to save all diagnostics files associated with the VM.
  • Virtual network (VNET): Select an existing virtual network or create a new one in which the virtual appliance resides. To create a new network, click Create new and complete the following steps in the Create virtual network panel:
    • Name: Enter the name of the virtual network.
    • Address space: Enter the range of the IP address space for the virtual network in the CIDR format.
      Example: 10.11.0.0/16.
  • LAN1 interface's subnet: Select the subnet from the drop-down list. By default, only the LAN1 communication is activated, and all traffic goes through the LAN1 interface (including management and protocol services). If you want to change this configuration, you must activate the MGMT port in the Grid configuration. For more information, refer to the Infoblox NIOS Documentation. 

  • MGMT interface's subnet: Select the subnet from the drop-down list. When you set up the MGMT interface, ensure that you use the same IP address that is currently defined for the NIC card in the Azure portal for the Infoblox GUI. Depending on your configuration, you may have the GUI communication going through the MGMT interface only when you activate the MGMT port.
    Note:

    • Infoblox vNIOS virtual appliances require two network interfaces (LAN1 and MGMT) for proper Grid communications. These interfaces must be assigned to separate subnets within the same Azure virtual network.
    • If you need to add or delete a network interface to an existing vNIOS for Azure instance, you must power off the instance, add or delete the interface, and then start the instance. Adding or deleting an interface when the instance is powered on, can result in unexpected behavior.
    • If you create a subnet in your Azure VNET that uses the same address range as for the VNET address space and add new instances to it, NIOS will not discover or recognize resources within that prefix. To populate the IPAM, ensure that all VNETs that must be managed or discovered through NIOS Grid Manager, only use subnets with smaller address range than that of the VNET address space.
      Example: The VNET with an address space mask of /16 and the largest subnet with an address range mask of /18.

  • Public IP address: If you need to communicate with the virtual appliance outside of the virtual network, select an existing public IP address from the drop-down list or create a new one. To create, click Create new, and then enter the IP address in the Create public IP address panel. You can select whether this IP is Dynamic or Static.

    Note that the public IP address can only be associated with the primary interface (LAN1 by default). However, if you change the networking options in NIOS, such as attaching the public IP address to the MGMT interface (because there is no way to change the attachment to another interface), then you must re-map your interfaces so that the current LAN1 is renamed to MGMT and is attached to the MGMT network.
  • Public DNS name: When you create a public IP address, enter the DNS name for the public address.
  • Install temporary licenses: Click yes to install the following temporary licenses on your virtual appliance: vNIOS, Grid, DNS, and CNA (Cloud Network Automation). This also installs temporary license of NIOS for appliances: IB-V825, IB-V1425 and IB-V2225. Installing temporary licenses might prolong the installation time by up to five minutes. Note that the CNA license is active only when the virtual appliance is configured as the Grid Master; the license has no effect on Grid members.
  • Enhanced options: You can upload a .yaml file containing custom data for your vNIOS for Azure instance. To upload, click the Folder icon, locate, and upload the file, and then click OK to save the VM configuration.
    Example of a custom data .yaml file for adding temp licenses for IB-V1425 appliance:
    #infoblox-config
    remote_console_enabled: y
    default_admin_password: password
    temp_license: dns enterprise nios IB-V1425

...