Create a VNET

A virtual network (VNET) in Cloudistics enables application instances to migrate seamlessly among compute nodes without changing networking configurations.

When you create a VNET, the Cloudistics Ignite management console manages all DHCP and NAT services via an auto-deployed application instance called the network function virtualization (NFV) instance. There is one NFV instance per VNET. This NFV instance acts like any application instance in your cloud infrastructure. It resides in a virtual datacenter and consumes migration zone and storage pool resources, and it uses the gateway IP address for your VNET.

You can also choose your own application instance to act as a VNET NFV instance. This allows load balancer and firewall applications, such as Netscaler, to run in Cloudistics and act as the VNET gateway.

NOTE

At least one VLAN must be created before a VNET can be deployed.

Refer to the following topics for instructions on how to create a VNET.

Prerequisites

Before you create a VNET, do the following:

  1. Determine how large your subnet should be.
  2. Determine how many CPU cores you will need and how much memory you would like to allocate to your VNET’s Network Function Virtualization (NFV) instance. (The NFV instance acts as a DHCP server and gateway for instances in the VNET.)
  3. Create a migration zone.
  4. Create a storage pool.
  5. Create a virtual datacenter.
  6. Create a firewall profile (if needed)
NOTE

At least one VLAN must be created before a VNET can be deployed. It is possible to create an "incomplete" VNET, which you can deploy later.

Create a VNET

To create a virtual network in Cloudistics Ignite, follow these steps.

  1. In the left navigation menu of Cloudistics Ignite, select Networks under Networking.
  2. Click New Network and then select New VNET.

     

    The New VNET page opens with the Properties section at the top of the page.

    Defining VNET properties when creating a new VNET

  3. In the Properties section, enter the following information:
    • VNET Name - Enter a name for the VNET.
    • Network Address - Enter a network address (This should be an IP address preceding your usable IP range.)
    • Netmask - Enter the netmask address for this network.
      NOTE

      The Usable IP Range automatically populates after your IP address and netmask have been added.

    • Default Gateway - Enter the default gateway address for this network.
  4. In the DHCP Settings section, enter the following information. (Click Show Advanced Settings to configure advanced DHCP settings.)
    NOTE

    You need to enter DHCP information if you will use an auto-deployed NFV instance.

    Entering DHCP Settings for new VNET

    • DHCP Range - Enter the part of this VNET’s IP address range that should be served by DHCP. The DHCP range must be within the usable IP range but does not include your default gateway.
    • DHCP Lease Time - Enter the amount of time in seconds for how long the DHCP lease is retained on your client. The default is set to one day (86400 seconds), but you can override it.
    • Domain Name (optional) - Enter the domain name for DHCP as applicable.
    • Primary DNS Server (optional) - Enter the primary DNS server for DHCP as applicable.
    • Secondary DNS Server (optional) -Enter the secondary (redundant) DNS server for DHCP as applicable.
    • Static Binding (optional) - To assign fixed IP addresses via DHCP, use Static Binding. Once instances using your VNET have been created, you can enter their MAC addresses and IP addresses in the Static Binding section. These IP addresses must be in your DHCP range. The specified instances will request the specified IP addresses from DHCP. You can click Add Row or click the ellipsis action menu and click Remove Row to add or remove rows as needed. To avoid issues with any outstanding DHCP leases, make sure you also set the IP address specified in this section as the static IP address within the instance's guest OS.
  5. In the Network Services section, select the type of network service to deploy for this VNET.

    Selecting Network Services Deployment for new VNET

    • Automatic - A network functional virtualization (NFV) instance for this VNET will be created for you. An auto-deployed NFV instance will act as a DHCP server and gateway for instances in the corresponding VNET. It will be assigned two IP addresses: the internal interface IP address specified as the VNET’s gateway, and the outside interface IP address that will be determined by the Routing Service settings. If you select Automatic, you need to define the DHCP settings for this VNET as described in the previous step. Also, see the topic, Define Settings for Auto-Deployed VNET, for defining other settings, including NFV settings and routing service settings.
    • Manual - You will need to create and configure an NFV instance to provide network services for this VNET. See the topic, .Create and Deploy Custom NFV Instance, for more information.

Define Settings for Auto-Deployed VNET

  1. If you selected Automatic for the Network Service, you need to define the DHCP settings for this VNET as described in the previous section in Step 4.
  2. Next, you should define NFV Instance settings as described below.
  3. NFV Settings for auto-deployed NFV instance

    • Virtual Datacenter - Select the virtual datacenter where this VNET's auto-deployed NFV instance should run. This VNET will be available to all instances running in this virtual datacenter.
      NOTE

      If there are no VLANs, and you are creating an auto-deployed VNET, you will not be able to select a virtual datacenter here; the only option to select is Deploy NFV Instance Later. You can still create the VNET (as incomplete), but it will work only after the NFV instance is fully deployed.

    • Storage Pool - Select the Storage Pool where this VNET's auto-deployed NFV instance should run.
    • Migration Zone - Select the Migration Zone where this VNET’s auto-deployed NFV instance should run.
    • Provisioning - Specify CPU, memory, and other optional compute constraints for the NFV instance.( Click Compute Constraints to view and select compute categories and compute tags as applicable.)
    • Automatic Recovery - Select the Enable Automatic Recovery option as needed. In the event of node failure, this option restarts the instance elsewhere when resources are available.
  4. Configure the routing service for the auto-deployed VNET. The Outside Interface (Routing Service) settings define the external network through which all traffic of this VNET will communicate. You can select the outside interface only after a migration zone has been selected for the NFV.
    NOTE

    This Outside Interface section is not available if you selected to deploy the NFV later.

    Outside Interface (Routing Service) settings for auto-deployed NFV

    • Networking Mode - You can select either VLAN or VNET as the external networking mode.
    • Network - Select the network to use for the external network. This setting is disabled until a virtual datacenter is selected for the NFV, and this list is populated only by only the networks to which the NFV virtual datacenter has permissions.

      NOTE

      If you choose a VLAN network for the external network, a static route needs to be created on your core router.

    • Firewall Profile - This field shows any associated firewall profiles for this external network.
    • Firewall Override - Select a firewall override for this external network if needed.
    • Address Mode - Select the address mode as either DHCP (IP address will be automatically assigned) or Static (to assign an IP address of your choosing).
      • IP Address - If you selected the Static Address mode, enter the external IP address for this external network.
      • Netmask - If you selected the Static Address mode, enter the netmask for this external network.
      • Gateway - If you selected the Static Address Mode, enter the gateway address for this external network. The gateway should be within the usable IP range for the external network.

Create and Deploy Custom NFV Instance

If you selected the Manual option in the Network Services section to use your own NFV instance for the VNET, you will need to create and configure your NFV instance. At least one of the vNICs for this instance must use this VNET.

  1. Click Create VNET to create the VNET. But, note that the VNET will be considered "incomplete" and will work only when an associated NFV instance with necessary network services has been deployed.
  2. Create the NFV instance. See the topic, Create and Deploy Applications, for instructions on creating an application instance. See this topic for specific instructions for using Netscaler as an NFV.
  3. After creating the instance, go to the Networks section in the Cloudistics Ignite UI, and select the VNET to open the network details page.
  4. On the VNET's page, click Deploy NFV Instance next to Network Function Virtualization (NFV) or select Deploy NFV Instance from the Actions menu.

    “Deploy NFV instance” option on a VNET with custom NFV instance.

    The Deploy NFV Instance dialog opens.

    Deploy NFV Instance

  5. Enter the following information for the NFV instance as needed, and then click Save.
    • Virtual Datacenter - Select the virtual datacenter where the NFV instance is to be deployed. This VNET will be available to all instances in the selected virtual datacenter.
    • Storage Pool - Select the storage pool for the NFV instance.
    • Migration Zone - Select the migration zone for the NFV instance.
    • Provisioning - Specify CPU, memory, and other optional compute constraints for the NFV instance.( Click Compute Constraints to view and select compute categories and compute tags as applicable.)
    • Automatic Recovery - Select the option, Enable Automatic Recovery, to specify that if the node fails, the instance will restart elsewhere when resources are available
    • Routing Service/Outside Interface Details (The Outside Interface is used by the Routing Service.)
      • Networking Mode - Select the networking mode for external traffic as either VLAN or VNET.
      • Network - Select the network for the outside interface.
      • Address Mode - Select the address mode as either DHCP (IP address will be automatically assigned) or Static (to assign an IP address of your choosing). If you select Static, you will then need to add the IP Address, Netmask, and Gateway.
      • Firewall Profile - To apply a firewall profile, select a firewall profile from the drop-down menu.
      • Firewall Override - To apply a firewall override, select an override from the drop-down menu.
  6. Start the custom NFV instance to complete the VNET creation.

Configure VNET for External Routing Service

When creating a virtual network (VNET) in Cloudistics version 3.3 and later, additional configuration is required if you select Virtual Networking for the external Routing Service. A static route must be added to the Interconnect and the Network Function Virtualization (NFV) instance of the VNET acting as the routing service.

NOTE

If you choose a VLAN network for the external network, a static route needs to be created on your core router.

To illustrate creating a VNET for the external routing service, refer to the following example. In this example, a user is creating Vnet2, which will use Vnet1 as the Routing Service (external) interface.

Vnet1:

  • Vnet IP Range: 10.104.14.0/24
  • External Routing Service IP (bridged): 10.102.14.200
  • Internal IP: 10.104.14.1

Vnet2:

  • Vnet IP Range: 10.6.200.0/24
  • External Routing Service IP (Vnet1): 10.104.14.100
  • Internal IP: 10.6.200.1

Configuring the Interconnect

Follow these steps to add a static route to the Interconnect.

  1. SSH into the Interconnect with the username, manager, and the password that was set when the hardware was registered.
  2. Run the command, sudo su, and retype your manager password to become root
  3. Run the command:
    > /usr/share/cloudistics/export_bgp_route.sh "add <network address of Vnet2> <subnet mask of Vnet2> <external IP of Vnet1>"

In this example, the command would be:
/usr/share/cloudistics/export_bgp_route.sh "add 10.6.200.0 24 10.102.14.200"

Configuring the vnet1 NFV instance

Follow these steps to add a static route to the NFV instance of the VNET acting as a routing service.

  1. Open the console to the NFV instance for Vnet1.
  2. Log in as root with password: cloudistics.
  3. Enter the command:
    vi /etc/sysconfig/network-scripts/route-internal
    and type i to edit the file.
  4. Enter the command:
    <vnet IP range of Vnet2> via <external IP of Vnet2> dev internal
    In this example, the entry would be:
    10.6.200.0/24 via 10.104.14.100 dev internal
  1. Press ESC and enter :wq to write changes and close the file.
  2. Run: ifup internal.

Alternatively, you can use an application instance as a NFV. Learn more here.

Configure a Firewall for a VNET (optional)

You can easily specify firewall settings for a VNET.

  1. On the New VNET page under Firewall Settings, to apply a firewall profile, select a firewall profile from the drop-down menu. (You can click View Rules to view the detailed rules for the selected profile. Or, to create a new firewall profile, click the Firewall profiles link. )
  2. To apply a firewall override, select an override from the drop-down menu. (You can click View Rules to view the detailed rules for the selected profile.)

Specifying firewall settings for the new VNET

Create the VNET

  1. When you have configured all required settings for your new VNET and are ready to create the VNET, click Create VNET at the bottom of the page. It may take a few minutes to deploy and configure the VNET.

Create VNET

NOTE

An incomplete auto-deployed VNET can be created only if there are no existing networks.

Configure Core Router

The Core Router is required to be configured when VNETs are created. For virtual networking to work successfully in infrastructures without BGP, the core router must be configured to recognize the IP addresses in each virtual network.

NOTE

Ensure that the core router has a rule to route all traffic coming to each virtual network’s IP address range to the appropriate Network Interconnect’s IP address.

Once your core router is configured, you are ready to deploy application instances within the VNET.

Previous

Next

Still need help?

Submit a request