In private cloud, an administrator defines the external network in the network infrastructure (VLANs in the switch or network manager), and then a cloud administrator creates the corresponding network in the platform, supplying the VLAN tag or VXLAN tag. In vCloud Director, an administrator may onboard and synchronize external networks, but they may not manage them in the platform.
To display external networks:
Or in vCloud Director, go to Virtual datacenters → Network → External. The platform displays networks that have been deleted in the provider in gray text.
You can scroll through the network list using the page number and arrow buttons at the bottom of the list. And you can filter the list by entering text and wildcards to search for in network names.
On the External IPs page, click on the header of a column to sort by that column, use the Search box to filter the results by any field, and navigate through the pages with the page scroll.
Before you begin:
If you are using standard networking, you will need the VLAN tag to use with this network
To create an external network:
Click thebutton and enter the details
The name of the external VLAN with up to 128 characters
|IPv6||To create an IPv6 network, select this checkbox|
|Strict||For IPv6 networks only. If you select Strict, the platform will automatically generate EUI64 IP addresses.|
The network address of the VLAN
The network mask in CIDR format. For IPv4, the value can be from 16 to 30 inclusive, and for IPv6, enter a value of 64, 56, or 48
The gateway of the network, which must be within the range defined by the network address and the network mask
The tag to use for this VLAN
Check tag availability for all racks of the datacenter as you should define each VLAN with the same tag on all racks. Green = available, Yellow = in use, Red = unavailable
|Network service type||Select the Network Service Type, which represents a Network Interface on the hypervisors.|
Select to create an unmanaged network, when you will manage IP addresses outside Abiquo
Select the owner enterprise that will use the external VLAN
|Device||To manage IP addresses with a network virtualization system, select the device that defines this system in the cloud platform. VMs deployed on this network must allow traffic to the appropriate ports for the virtualization system's connection, e.g. DHCP|
Address of the Primary DNS server
Address of the Secondary DNS server
The default DNS suffix
|Restricted||Select to create a Restricted network so that users require the privileges to Attach NICs in restricted networks and/or Detach NICs from restricted networks|
|Excluded from firewall||Select Excluded from firewall to define a network where VM firewall policies will not apply|
Select the Define checkbox to add and modify static routes
When you create an IPv4 network, the platform will create an IP address for the gateway. When you create an IPv6 network, the platform does not create IP addresses.
To add a Static Route: Field Description Example Netmask Destination network mask 255.255.255.0 Network ID Destination network or host 220.127.116.11 Gateway IP Next hop (on your network) 10.10.10.100
To add a Static Route:
Destination network mask
Destination network or host
Next hop (on your network)
When you add IPv6 addresses on strict networks, you don't need to set the starting address.
On non-strict IPv6 networks, Abiquo recommends that you create an automatic IP address, or you can enter an IP address manually as shown here.
After you create public, external, or NAT IP addresses, they will automatically be available to all users to purchase or reserve for their virtual datacenters. Abiquo recommends that you should make unavailable any IP addresses that will be used for administration purposes, for example, the IPv4 gateway network address. Public or NAT IPs that have been purchased or reserved by the users of an enterprise will not display in the Available list and you cannot make these IPs unavailable. To edit the available IP addresses:
Abiquo recommends that you should make unavailable any IP addresses that will be used for administration purposes, for example, the IPv4 gateway network address.
Public or NAT IPs that have been purchased or reserved by the users of an enterprise will not display in the Available list and you cannot make these IPs unavailable.
To edit the available IP addresses:
You can modify the following fields if there are no VMs deployed in the network.
The name of the external or unmanaged VLAN
|Gateway||IPv4 only. The gateway of the network must be an IP address inside the range defined by the network address and the network mask|
The VLAN tag to use for this VLAN
|Network service type||The Network Service Type is a group of network interfaces on the hypervisors that this network will use.|
|Enterprise||The enterprise that will use this network|
|Device||The device pointing to the network virtualization system for the SDN integration|
|Restricted||Select to restrict this network so that only users with the privileges to manage NICs in restricted networks can use these addresses on VMs|
You can modify these fields at any time but the changes will only apply to VMs deployed after the changes are made.
The address of the primary DNS server for your network
|Secondary DNS||The address of the secondary DNS server for your network|
The DNS suffix for your network
To delete an external network:
If there are no VMs using the IPs of an external network that was already deleted in the provider, to delete the network in the platform, select it and click the Delete button.
The platform will toggle the quarantine status of the selected IPs.