Versions Compared

Key

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

...

  • NIOS Version: Select the NIOS version to run on the selected VM.
  • Virtual Machine Size: Depending on your selected virtual machine model, you may or may not be able to select a VM size. The portal displays the recommended option by default. You can click View all to see all available options. Click Select to save your selection.
Note

The virtual machine series available under US Gov lowa region does not support the launching of vNIOS. For more information on the supported virtual machines, see, Azure Products by Region.

  • Storage account: Click this option to configure the storage account. The Portal opens the Choose storage account panel from which you can select an existing account in the selected location and subscription. This account gives you access to resources in the Azure Storage, which provides a namespace for your DNS data objects. By default, the data in the Azure account is available only to the account owner. You can also click + Create new in the Create storage account panel to create a new account, as follows:
    • Name: Enter a name for the storage account you are about to create. The name must have a minimum of 3 characters and a maximum of 24 characters, and it can contain only lower case alphabetic characters and numeric numbers.
    • Performance: This field indicates the type of storage account for the data storage. For virtual appliances, you must use Premium storage accounts. You cannot change this to Standard. Premium storage accounts are backed by solid-state drives and offer consistent and low-latency performance. They are used only with Azure virtual machine disks, and are best for I/O-intensive appliances such as databases. Standard storage accounts are backed by magnetic drives and provide the lowest cost per GB of memory. They are the best type of storage account for applications that require bulk storage or where data is accessed infrequently. If you want to create a storage account to save all diagnostics files associated with the VM, click Storage account for BootDiagnostics to create the standard account. You can create a new account or select an existing one from the available list.
    • Replications: This field displays the default replication strategy. The data in your Azure storage account is always replicated to ensure durability and high availability. The default replication strategy matches the durability requirements your appliance needs. You might not be able to change this once the storage account is created.
  • Storage account for BootDiagnostics: Click this option to 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, complete the following 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.
  • Subnets: Click this to configure the settings of the network interfaces. 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. 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 information, refer to the Infoblox

     

    NIOS

     Administrator Guide

    Documentation). When you set up the MGMT interface, ensure that you use the same IP address that is currently defined for the NIC card on 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
    titleNote

    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 the VNETs to 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, click here to create a public IP address. In the Choose public IP address panel, you can select an existing public IP address or create a new one by clicking + 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 these 3 appliances - TE-V825, TE-V1425 and TE-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 may coordinate with Infoblox Technical Support to upload files with custom data. Click OK to save the VM configuration.

Anchor
bookmark21
bookmark21
Figure 1.3 Configuring VM Settings

Image RemovedImage Added