Display virtual datacenter networks
To display the networks available to a virtual datacenter:
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
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)
In the Networks list, to view the pool and allocation of IPs:
To display all the IPs in the virtual datacenter, click the All button at the top of the list
To display the IPs in a network, click the Network name
You can then:
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 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
|
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
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 → select a virtual datacenter → Network → Private
Select the network and click the delete button below the networks list.
Display onboarded external networks
The platform automatically onboards external networks when you onboard virtual datacenters from vCloud Director.
Privileges: Manage virtual network elements, Access external networks tab, Manage external network elements
To display onboarded external networks
Go to Virtual datacenters → Network
Select a vCloud VDC
Go to External
Delete an onboarded external network
Set the default network for a virtual datacenter
Obtain IP addresses from public networks
Obtain public IP addresses in public cloud
Synchronize public IP addresses with the cloud provider
Release a reserved public IP address
Limit Public IP bandwidths for a VDC
Reserve private IPs
The private IP reservation feature will prevent users from assigning reserved IPs to VMs within the platform. The platform does not display reserved IPs to allow users to select them for VMs. You can only assign reserved IPs to VMs from outside of Abiquo, for example, using a script. If you onboard a VM with a reserved IP, the platform logs a warning message.
Privileges: Manage private IP reservation
To reserve private IPs:
Go to Virtual datacenters → Networks → Private
Select the IPs and click the lock button
Enter the reason for the reservation
The platform will list the VMs in the virtual datacenter. Optionally select VMs to indicate where the IPs might be used. Note that you must check that the VMs are able to use these IPs. This selection does not assign the IPs to VMs.
The platform will display a padlock symbol and the reason beside the IP reserved addresses.
Pages related to virtual datacenter networks
Administer virtual resources
Work with VMs, see the Related pages list in myCloud view
Manage and configure datacenter networks, see Networks
Configure network infrastructure, see Network