This topic explains about the single network interface instance of vNIOS for GCP and has instructions to deploy the instance. The topic includes the following sections:

Single Network Interface Instance of vNIOS for GCP

The single network interface instance of Infoblox vNIOS for GCP is designed for deployment using VPC and shared VPC networks on GCP. The instance provides core network services such as DNS and IPAM services of a modular Infoblox solution. The network interface in the instance is allocated to the LAN1 interface instead of the MGMT interface. Note that when you deploy vNIOS for GCP with a single network interface configuration, options related to MGMT, LAN2, and HA interfaces are not available in Grid Manager and the NIOS CLI.

When you use Grid Manager to configure the single network interface instance of vNIOS for GCP, options specific to only the LAN1 interface are displayed as follows:

• Grid Member Properties Editor: When you configure the network for a member in the Grid Member Properties Editor on the Network -> Basic tab, options relevant to the LAN1 interface only are available. Options specific to MGMT and LAN2 interfaces are not available.

• Member DNS Properties editor:

  • When you transform the IPv4 or a dual mode Grid to an IPv6 only Grid, on the General tab -> Basic tab, only LAN1 is available as the DNS interface. 

  • When you configure DNS traffic control properties, only LAN1 interface is available as the DTC Health Check Resource on the Traffic Control tab -> Basic tab.

• Traffic Capture dialog box: When you configure traffic capture for Grid members in the Traffic Capture dialog box, you can configure only the LAN1 interface for a selected member.

• System Activity Monitor widget: You can configure the System Activity Monitor widget to measure the traffic on the LAN1 port only. The LAN2 port related options are not available. 

When you use the NIOS CLI to configure the single network interface instance of vNIOS for GCP, you can configure only the LAN1 parameter in the following commands: 

• set interface

• show interface

• set default_route

• set port_mac_addr

• set traffic_capture

For more information on the NIOS CLI commands, see the Infoblox NIOS Documentation.

Deploying the Single Network Interface Instance

You can deploy the vNIOS for GCP instance configured with any of the following:

• A single network interface in a host project.

• A single network interface in a service project that uses a VPC or a shared VPC network in a host project.

To deploy vNIOS for GCP using VM instances, complete the following:

1. Log in to your Google Cloud Console using the URL: https://console.cloud.google.com

2. Navigate to Compute Engine -> VM instances.

3. In the VM instances panel, click Create Instance.
   
   To ensure that your vNIOS for GCP functions properly, update the instance configuration as required. For specifications, see Supported vNIOS for GCP Models.
   

4. In the Create an instance panel, complete the following. Note that GCP automatically populates some field values based on previous configurations. Click a field that you want to make changes to and update the values:

   • Name: Enter a name for the instance.

   • Region: Choose the Google cloud region from the drop-down list.

   • Zone: Choose a zone where you want your data to be stored.

   • Machine type: Choose a value from the drop-down list. For more information, see Supported vNIOS for GCP Models.

   • Boot disk: You can select an image or a snapshot to create a new boot disk, or attach an existing disk to the instance.
     To select the vNIOS image that you created, complete the following:

     1. Click Change.

     2. In the Boot disk panel, click Custom images.

     3. Select the vNIOS for GCP image from the public bucket.

     4. Change the Boot disk type to Standard persistent disk if the vNIOS appliance you are deploying is a Trinzic X5 series model running versions prior to NIOS 9.0.1.
        If you are deploying Trinzic X6 series models that are supported from NIOS 9.0.1 onwards, Infoblox recommends that you select SSD persistent disk as the type for better performance. For the supported vNIOS models, see Supported vNIOS for GCP Models.

     5. Change the Size based on the model you are deploying.

     6. Click Select.

   • Advanced options: Expand the Advanced options menu and complete the following:

     • Networking tab: Set up one interface each for MGMT, LAN1, and HA.
       Note that NIOS instances do not support the GCP Custom Hostname feature.

       1. By default, the GCP instance has a network interface added and allocated to the LAN1 port. Based on the configuration you intend to use, click the Edit icon and modify the values in the Edit network interface dialog box as follows:

          1. Single network interface in a host project:

             1. Network: Change the default network to the correct network.

             2. Subnetwork: Select your subnetwork.

             3. Click Done.

          2. Single network interface in a service project that should use the shared VPC in its host project:
             Note that this configuration is allowed only for the single network interface instance of vNIOS for GCP.

             1. Select Networks shared with me (from host project: <host project name>).

             2. Subnetwork: Select your shared subnetwork of the host project from the drop-down list.

             3. Click Done.

     • Security tab: Add your SSH key string.

     • Identity and API access tab: From the Service account drop-down list, select the service account that has been assigned with role permissions that NIOS requires for authentication. For information about roles, see Configuring a Service Account.

     • Management tab: Go to the Metadata section and add the following key-value pair.
       Note:
       - This metadata will install temporary license keys for the selected services.
       - NIOS does not support DHCP in GCP in NIOS versions prior to 8.6.2.

       1. Add Key: user-data.

       2. Add Value:
          #infoblox-config
temp_license: nios xx-Vxxxx enterprise dns
remote_console_enabled: y

       3. Click Done.

5. Click Create to create the instance.