| Table of Contents |
|---|
| Info |
|---|
This section describes how to manage networks in virtual datacenters |
Display virtual datacenter networks
...
| Panel |
|---|
Privileges: Manage virtual network elements, Access external networks tab, Access public networks tab |
Go to Virtual datacenters → select virtual datacenter → Network.
The default network is highlighted with a star symbol
A network with an internet gateway is highlighted with a globe symbol
In public cloud, to synchronize networks and IP addresses, click the round arrows synchronize button
In AWS, you can filter the list of private networks by Availability Zone
| Tip |
|---|
API Features Virtual datacenter networks are available in the Abiquo API. For example, see VirtualDatacentersResource and PrivateNetworksResource. |
Screenshot: Private networks in private cloud
...
Screenshot: Private networks in public cloud (AWS)
You can display an inventory of your cloud networks easily in Virtual datacenters view
...
In the Networks list, to view the pool and allocation of IPs:
...
Use the slider at the bottom of the list to move through the pages
Filter the list by entering text in the Search box. The filter works with all the columns of the table including:
IP Address
MAC address
Network name
Virtual appliance using the IP
VM using the IP
Provider ID of the entity using the IP (for example, a load balancer)
...
Create a private network
Private networks are only available within a virtual datacenter. However, your cloud provider may configure an external gateway for your virtual datacenter.
To create See Create a private network:
Go to Virtual datacenters → select virtual datacenter → Network → Private
Click the + add button and complete the dialog
Create private network
...
Create private network Amazon
...
Button
...
Action
...
Name
...
Name of the network (VLAN). The name can contain up to 128 characters
...
IPv6
...
Select checkbox for IPv6 network
The Abiquo NSX-T integration does not support IPv6
...
Network Address
...
Private address range of the network
...
Netmask
...
For IPv4 a network mask with an integer value of between 16 and 30
...
Gateway
...
Gateway of the VLAN. Must be an IP within the range of the network address and mask
...
Internet gateway
...
In AWS, select this option to create a public subnet with a route to an internet gateway
...
Availability zone
...
In AWS, optionally select an Availability zone for high availability. To deploy a group of VMs separately, use a different availability zone for each VM. To assign a VM to an availability zone, assign a private IP address in the network belonging to the required availability zone
...
Primary DNS
...
The primary DNS.
...
Secondary DNS
...
The secondary DNS
...
DNS suffix
...
The DNS suffix. The Abiquo NSX-T integration does not use this attribute but you can enter it for information purposes.
...
Excluded from firewall
...
Select Excluded from firewall to define a network where VM firewalls will not apply
...
Static Routes
...
In supported providers, optionally select Define to create static routes. See Configure Static Routes using DHCP
...
Default network
...
Select to make this network the default network, replacing the existing default network
You can configure static routes when you create or edit a network. However, you should check with your systems administrator about when your VM will receive changes to static routes.
...
Field
...
Description
...
Example
...
Netmask
...
Destination network mask
...
255.255.255.0
...
Network ID
...
Destination network or host
...
1.1.1.0
...
Gateway IP
...
Next hop (on your network)
...
10.10.100.1
IPv6 Strict network
...
IPv6 Non-strict network
...
Field
...
Description
...
Name
...
Name of the VLAN. The name can contain up to 128 characters
...
IPv6
...
Select checkbox for IPv6 network
...
Strict
...
IPv6 only. If you select Strict, Abiquo will automatically generate the network address (ULA) and also the IP addresses. If you do not select strict, you can enter the network address and IP addresses.
...
Netmask
...
Network mask of 48, 56 or 64.
...
Network Address
...
Private address range of the network. Only for non-strict networks
...
Primary DNS
...
The primary DNS
...
Secondary DNS
...
The secondary DNS
...
DNS suffix
...
The DNS suffix
...
Default network
...
Make this network the default network. In a datacenter, this will override the existing default network
Create IP addresses in private networks
To create new IP addresses in a private network do these steps.
Go to Virtual datacenters → optionally select a virtual datacenter
Go to Networks → Private → select a private network
On the Private IPs page, click the add + button and enter details
Or you can add an IP directly to a VM. To do this:
Go to Virtual datacenters → Edit VM → Network
Click the add + button and enter details (or drag the Auto-generated IP label into the Network pane)
...
Enter the Number of IPs to create and the From IP address (the first in the range). The From IP address must be a new address that does not already exist in the network. After creating the first IP address, the platform will try to create the other IPs and it will skip any existing IP addresses.
For example, if you have IP addresses in network 30.30.30.30, which are 30, 33, and 34 and then you request 3 new IPs from 30.30.30.31. The new IPs created should be as follows: 31, 32, 35.
...
30.30.30.30
...
30.30.30.31
...
30.30.30.32
...
30.30.30.33
...
30.30.30.34
...
30.30.30.35
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 a From IP address manually.
Edit a private network
To edit a private network
...
Go to Virtual datacenters → select a virtual datacenter → Network
Add IPs to private networks
...
Edit a private network
To edit a private network
Go to Virtual datacenters and select a virtual datacenter, then go to Network
Select Private and select the network
Click the pencil edit button below the Networks list
If there are no VMs deployed in the network, you can change the Name, Gateway, Static routes, and make the network the new default for the virtual datacenter
The gateway must be an IP address inside the range defined by the network address and the network mask
Optionally, change the DNS settings. The new settings will apply to all VMs deployed after you save the network
Click Save
...
Delete a private network
You can delete a private network if no VMs are using its IPs and it is not the default network for the virtual datacenter.
To delete a private network:
Go to Virtual datacenters
...
and select a virtual datacenter
...
Go to Network → Private
Select the network and click the delete button below the networks list.
...
Display onboarded external networks
...
To display onboarded external networks
Go to Virtual datacenters → Network
Select a vCloud VDC
Go to External
...
Delete an onboarded external network
...
To assign a network as the default for a virtual datacenter do these steps:
Go to Virtual datacenters → select virtual datacenter → Network → network type, e.g. Private
Create or edit a network
Select the Default network checkbox
This default will override the platform default network and any network set for the enterprise in the datacenter
The new default network will apply to all VMs deployed after you set it
For a public network that is the virtual datacenter default, obtain IP addresses for your VMs before you deploy
...
Obtain IP addresses from public networks
In public networks you can reserve or purchase public IP addresses for your VMs. Reserved IPs may be charged while they are reserved, even if they are not used in VMs.
| Panel |
|---|
Privileges: Manage public IPs, Access public networks tab, Manage public network elements |
To add new public IP addresses to your virtual datacenter:
Click the + Add button on the Public IPs page to display the list of available public IPs
To move between pages, use pagination controls such as arrows and page numbers
To filter your search, enter an IP address or Network name in the Search filter box
Select IP addresses to add them to your virtual datacenter
Click Add to reserve the IPs
The platform will add the IPs to your VDC
You can also reserve public IPs directly from the Edit VM dialog.
...
Obtain public IP addresses in public cloud
During onboarding from public cloud, the platform will onboard existing public IP addresses in providers that support them, such as AWS and Azure. You can obtain them from the provider and assign them to your virtual datacenters and VMs.
| Info |
|---|
The provider may charge for public IP addresses as soon as you reserve them for your virtual datacenter. Therefore you should reserve your IP addresses just before you deploy and check they are deleted when you undeploy your VMs. Remember that your provider may also limit the number of public IP addresses that you can use per virtual datacenter. |
To add public IP addresses to your virtual datacenter, so that you can later assign them to your VMs:
| Panel |
|---|
Privileges: Manage virtual network elements, Manage floating IPs, Access public networks tab, Manage public network elements |
Go to Virtual datacenters → Select a public cloud virtual datacenter → Network → Public
On the Allocated public IPs page, click the + add button
To add the public IP to a virtual datacenter, click the Add to VDC link near the IP address
Now when you edit a VM in the VDC and go to Network → Public, the platform will display the public IP address and you can add it to your VM.
...
To obtain a public IP directly for a VM, click Purchase public IPs.
See Obtain public IP addresses.
...
Synchronize public IP addresses with the cloud provider
...
| Panel |
|---|
Privileges: Manage virtual network elements, Manage floating IPs, Access public networks tab, Manage public network elements |
Go to Virtual datacenters → select a public cloud virtual datacenter
Go to Network → Public
Click the double arrow synchronize public IPs button (beside the + add button)
...
Release a reserved public IP address
...
In private cloud with NSX-T, you can delete network resources by deleting the virtual datacenters. The platform will automatically remove VMs, virtual appliances, load balancers, public IPs, and firewalls from the virtual datacenter. The firewalls will remain in the enterprise and you can reuse them. When you delete a virtual datacenter, public IPs that are not used by VMs will remain in the provider and the synchronization process will delete them.
...
Limit network bandwith with QoS
You can limit network bandwidth of public IPs and for VDCs with NAT networks. For more details see the following documentation.
...
Reserve private IPs
Administrators can reserve private IP addresses so that users cannot work with them in the platform.
See Reserve private IPs.
...
Pages related to virtual datacenter networks
Administer virtual resources
Administer and troubleshoot VMsManage persistent storage and VMs
Work with VMs, see the Related pages list in myCloud view
Manage and configure datacenter networks, see Networks
Configure network infrastructure, see Network