IP address assignment — VNETs
This section covers the considerations
Take into account the following when filling out the worksheet table for VNET IP address assignment:
VNET IP Ranges
For VNET that you plan to configure, it is recommended that you record the following parameters, which will be required for configuring each VNET: vnet_range_start, vnet_range_end, vnet_range_netmask, and vnet_range_gw. It is important to stress that the IP ranges allocated to the VNTEs must be completely separate and isolated from the internal networks (e.g. hypervisor, out-of-band management, hardware management network, and MLAG).
VNET with Outside Interface in VLAN Mode Configured for Non-Default VLAN
This is optional, and only applicable if you are planning to extend some of the VLANs configured in your network into the stack, and configure the outside interface of one of more VNETs in such VLANs. Note that this is only applicable if we configure the outside interface if the NFV VNET to use a non-default VLAN. If all the previous conditions are met, you recommend that you write down the set of VLANs in the variables [vnet_outside_vlan1 - vnet_outside_vlanN]. In addition, the outside interfaces of the VNETs must be assigned IP addresses, net masks, and default gateways (i.e. vnet_outside_ip1 - vnet_outside_ipN, vnet_outside_netmask1 - vnet_outside_netmaskN, vnet_outside_gw1 - vnet_outside_gwN). This assignment can be static upon VNET configuration, or dynamic by configuring DHCP servers/relays in the customer data center network to serve each corresponding VLAN (recommended).
Application VM with vNIC in VLAN Mode Configured for Non-Default VLAN
This is optional, and only applicable if you are planning to extend some of the VLANs configured in your network into the stack, and configure at least one of the vNICs of an application VM in such VLANs. Note that this is only applicable if we configure the VM’s vNIC to use a non-default VLAN. In this case, you must write down the set of VLANs in the variables [vm_vlan1 - vm_vlanN]. In addition, the VM’s vNICs must be assigned IP addresses, net masks, and default gateways (i.e. vm_ip1 – vm_ipN, vm_netmask1 - vm_netmaskN, vm_gw1 - vm_gwN). Application VMs typically do not support static IP assignments on VLANs that extend to the customer data center network. As a result, dynamic assignment by configuring DHCP servers/relays in the customer data center network to serve each corresponding VLAN is required.
Variable names
Variable names are shown in italics in worksheet tables. Those names correspond to parameters that you need to specify when deploying the ThinkAgile CP solution (using the ThinkAgile CP Deployment Guide).
Network masks
In worksheet tables, network masks must be entered in the Netmask or Prefix column using dotted decimal format X.X.X.X (for example: 10.1.1.2).
Network prefixes
In worksheet tables, network prefixes must be entered in the Netmask or Prefix column in prefix format /<number of bits> (for example: /23).
Name | IP Range | Netmask or Prefix | Gateway | VLAN ID (Tag) |
VNET IP Ranges | vnet_range_subnet1 vnet_range_start1 vnet_range_end1 ... vnet_range_subnetN vnet_range_startN vnet_range_endN | vnet_range_netmask1 ... vnet_range_netmaskN | vnet_range_gw1 ... vnet_range_gwN | N/A |
VNET with Outside Interface in VLAN Mode Configured for Non-Default VLAN (optional) | vnet_outside_ip1 ... vnet_outside_ipN | vnet_outside_netmask1 ... vnet_outside_netmaskN | vnet_outside_gw1 ... vnet_outside_gwN | vnet_outside_vlan1 ... vnet_outside_vlanN |
Application VM with vNIC in VLAN Mode Configured for Non-Default VLAN (optional) | vm_ip1 ... vm_ipN | vm_netmask1 ... vm_netmaskN | vm_gw1 ... vm_gwN | vm_vlan1 ... vm_vlanN |