- In OpenStack, run
source keystonerc_adminto set up the OpenStack environment.
- Upload the qcow2 file for the specified vNIOS for KVM model to OpenStack. For more information, see Requirements.
- Set up the OpenStack flavors, as described in Setting Up vNIOS OpenStack Flavors.
- Import the vNIOS instance into OpenStack, as described in Importing vNIOS Instance into OpenStack.
- Start an instance, as described in Starting a vNIOS Instance in OpenStack Environment.
- Ensure that you have already specified the vNIOS flavors and provided a unique name for the instance you want to spin up. For the list of available flavors, see Table 1.2.
- Execute the neutron port-create command to create port IDs for the network interfaces (MGMT and LAN1/HA). You can use the security-group option to associate the vNIOS instance with the security group(s) you have created. For information, see Setting Up Security Groups. (Optionally, you can associate the vNIOS instance with a security group when you execute the nova boot command.)
Note: Do not reuse the OpenStack neutron port of the deleted instances. When you reuse the neutron port of a deleted instance, a mismatch in the MAC address between the VM interface and the host VF might happen during NIC bonding. Also, the neutron port does not function properly when you reuse it repeatedly.
Following is a neutron example:
$ neutron port-create --security-group <name of the security group>
For an HA pair, you must also execute the allowed-address-pairs option to define the VIP port for the HA configuration, using the VRRP MAC address and the Virtual Router ID you use. Following is an example:
$ neutron port-create VIP –-allowed-address-pairs list=true mac_address= 00:00:5e:00:01:c8 ip_address=10.0.0.22
- For an HA pair configuration only, ensure that you set allow_duplicate_networks=true in the nova.conf file to remove the restriction of allowing only one interface for each network in OpenStack.
- Run the
neutron port listcommand to view the network and port IDs generated for all network interfaces so you can copy and paste them into the nova boot command.
- Execute the
nova bootcommand in OpenStack to spin up the vNIOS instance. (Note: Use the custom name you came up with when creating flavors).
Following is an example:
nova boot --config-drive False --image
<nios-7.3.0-314352-2016-01-29-05-02-02-160G-1420-disk1.qcow2> --flavor <vnios1410.160>
– security-groups <name of the security group> --nic net-id=<the network ID for the MGMT interface> --nic net-id=<the network ID for the LAN1/HA interface only if you are configuring an HA pair> --nic port-id=<the IP address ID for the LAN1 interface>
flavorspecifies the flavors of the vNIOS for KVM instance. For information about how to define flavors, see Setting Up vNIOS OpenStack Flavors.
security-groupsdefines the security group with which this vNIOS instance associates. For information about how to create rules for security groups, see Setting Up Security Groups.
nic net-idspecifies the network ID for the MGMT interface. Note that when provisioning an HA pair, you must also specify the network ID for the LAN1/HA interface. For more information, see Sample Commands for Provisioning an HA Pair.
nic port-idspecifies the IP address ID for the LAN1/HA interface.
Note: For the vNIOS appliance to run in OpenStack, you must specify at least two networks, MGMT and LAN1. To remove networks, use the neutron net-delete command. If some of the networks remain, use OpenStack Horizon to manually remove them.
my-vm-namedefines the unique name of the VM.
The vNIOS for KVM instance automatically spins up after the
nova bootcommand is executed.
- Go to OpenStack Horizon and select the previously launched instance.
- Click the Console tab.
- When the Infoblox login prompt appears, log in with the default user name and password.
The Infoblox prompt appears:
- You must have valid licenses before you can configure the vNIOS appliance. To obtain permanent licenses, first use the Infoblox > show version command to obtain the serial number of the vNIOS appliance, and then visit the Infoblox Support web site at https://support.infoblox.com. Log in with the user ID and password you receive when you register your product online at
If the vNIOS virtual appliance does not have the Infoblox licenses required to run NIOS services and to join a Grid, you can use the set temp_license command to generate and install a temporary 60-day license.
- From the list of licenses, select the Grid, vNIOS, and other relevant licenses for your vNIOS virtual appliance.
Note: You must have both the Grid and vNIOS licenses for the vNIOS virtual appliance to join a Grid (2 and 8 from the list).
- In OpenStack Horizon, go to InstanceOverview and copy the floating IP address of the instance.
- Go back to the console and run the
set networkcommand. Not required for Elastic Scaling.
- Go to the Infoblox Grid Manager and enable the NAT mode for the Grid member:
- Click Grid -> Grid Manager -> Members -> Network.
- Select the Grid member and click Edit.
- Click Network -> Advanced.
- Click Enable NAT Compatibility and enter the floating IP address.
- Click Save & Close.
Note: For an HA Grid Master, ensure that you specify these settings for both nodes.
After you confirm your network settings, the Infoblox Grid Manager automatically restarts. You can then proceed to set up a Grid, as described in Setting Up a Grid.