Follow

Virtual Network Creation

To create a Virtual Network (VNET) you will need to navigate to the networking –> virtual networks tab in Ignite. In the upper right-hand corner, you will see the option “new virtual network”. From here you will need to fill out the appropriate fields. Please reference the screenshots for assistance.

A few things to obtain before creating your VNET:

  • How large you would like your subnet
  • How many CPU cores you will need and how much memory you would like to allocate to your VNET's NFV instance
  • Virtual datacenter
  • Storage pool
  • Migration zone
  • If needed, a firewall profile

Properties:

In properties you will need to input your VNET name, network address (IP address before your usable IP range), netmask, and default gateway. This website can be a useful tool in calculating subnets and determining netmasks.

Properties.PNG

Network Services:network_services.PNG

  • If Automatic is selected, the NFV instance will be created for you.
  • If Manual is selected, you will need to create and configure an instance to provide network services. At least one of the vNICs for this instance must use this vnet.
    • After configuring the instance, click on the vnet and click "Link NFV Instance".vnet_link_nfv.PNG
    • Select the virtual datacenter and NFV instance that you created, then click Save. link_nfv.PNG

DHCP Service:

  • You will be able to choose advanced DHCP services such as lease time. This is how long your DHCP lease is retained on your client. It will automatically be set to one day (86400 seconds), but you will have the option to alter it.
  • You may also choose a domain name, static binding, and primary and secondary (redundant) DNS servers for DHCP. These are all optional and can be altered later. Cloudistics recommends entering a Primary DNS server and keeping the other default settings.
  • Once instances using your vnet have been created, you can enter their MAC addresses and desired IP addresses in the Static Binding section. These IPs must be in your DHCP range. The specified instances will request the specified IPs from DHCP.
  • To assign a static IP to an instance in the vnet, remove the static IP from the vnet's DHCP Range, then set the static IP within the instance's OS.

DHCP_service.PNG

Routing Service (Outside Interface):

The Routing Service settings specify the external network for the NFV instance that allows instances on the vnet to communicate outside the vnet. You will have the option to choose between DHCP (IP will be automatically assigned) or Static (to assign an IP of your choosing). Routing_service.PNG

If you select Virtual Networking for the Routing Service Networking Mode, see here for additional configuration instructions.

Network Function Virtualization (NFV) Instance: 

The NFV instance will act as a DHCP server and gateway for instances in the vnet. It will be assigned two IPs: the internal interface IP specified as the vnet's gateway, and the outside interface IP that will be determined by the Routing Service settings.

Organizations with multiple locations should review these guidelines for selecting a location for the NFV instance.

NFV.PNG

Firewall Settings:

For more information on configuring firewalls, see here.

Firewall.PNG

Creation:create.PNG

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments