Page Comparison

Display virtual datacenter networks

To display the networks available to a virtual datacenter:

1. 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

Screenshot: Private networks in private cloud

Image Removed

Screenshot: Private networks in public cloud (AWS)

Image Removed

...

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.

1. Go to Virtual datacenters → select virtual datacenter → Network → Private

2. Click the + add button  and complete the dialog

Create private network

Image Removed

Create private network Amazon

Image Removed

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.

Image Removed

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

Image Removed

IPv6 Non-strict network

Image Removed

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.

1. Go to Virtual datacenters → optionally select a virtual datacenter

2. Go to Networks → Private → select a private network

3. 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:

1. Go to Virtual datacenters → Edit VM → Network

2. Click the add + button and enter details (or drag the Auto-generated IP label into the Network pane)

Image Removed

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

Add IPs to private networks

See Create a network IP

...

Edit a private network

To edit a private network

1. Go to Virtual datacenters and select a virtual datacenter, then go to Network

2. Select Private and select the network

3. Click the pencil edit button below the Networks list

4. 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

   1. The gateway must be an IP address inside the range defined by the network address and the network mask

5. Optionally, change the DNS settings. The new settings will apply to all VMs deployed after you save the network

6. 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:

1. Go to Virtual datacenters

...

1. and select a virtual datacenter

...

2. Go to Network → Private

3. 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.

To display onboarded external networks

1. Go to Virtual datacenters → Network

2. Select a vCloud VDC

3. Go to External

...

Delete an onboarded external network

If an onboarded network has been deleted in the provider, its name will display in light gray text. If a VM is using an IP from this network, then you cannot deploy the VM.

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.

...

Set the default network for a virtual datacenter

Each virtual datacenter requires a default network. If you deploy a VM without assigning a NIC, the platform will add one from the default network. You cannot unselect the default network, instead you must assign a new default network to replace it.

To set a network as the default, you will require privileges to access this network in the virtual infrastructure.

To assign a network as the default for a virtual datacenter do these steps:

1. Go to Virtual datacenters → select virtual datacenter → Network → network type, e.g. Private

2. Create or edit a network

3. 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. 

To add new public IP addresses to your virtual datacenter:

1. Click the + Add button on the Public IPs page to display the list of available public IPs

   1. To move between pages, use pagination controls such as arrows and page numbers

   2. To filter your search, enter an IP address or Network name in the Search filter box

2. Select IP addresses to add them to your virtual datacenter 

3. 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.

Image Removed

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.

To add public IP addresses to your virtual datacenter, so that you can later assign them to your VMs:

1. Go to Virtual datacenters → Select a public cloud virtual datacenter → Network → Public

2. On the Allocated public IPs page, click the + add button

3. 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.

Image Removed

To obtain a public IP directly for a VM, click Purchase public IPs.

...

Synchronize public IP addresses with the cloud provider

To onboard any public IP addresses that were already created in your cloud provider, or update changes made directly in the provider:

1. Go to Virtual datacenters → select a public cloud virtual datacenter

...

2. Go to Network → Public

3. Click the double arrow synchronize public IPs button (beside the + add button)

...

Release a reserved public IP address

You can release a public IP if it is not assigned to a VM.

In private cloud, to release a public IP that belongs to a public network, select the IP in the IP list and click the delete button.

In public cloud, click the link to Remove from VDC and then click the delete button.

Limit Public IP bandwidths for a VDC

You can use Quality of Service (QoS) traffic shaping parameters to limit the bandwidth for each public IP in a virtual datacenter.  

This feature applies to public IPs in infrastructure and managed by NSX in vCenter and vCenter clusters.

When you upgrade the platform or create a virtual datacenter, the public IPs bandwidth limit is disabled. To enable the limit for the public IPs of the VDC, edit the bandwidth limit. 

To edit the bandwidth limit and enable it in the platform:

1. Select the virtual datacenter and go to Network → QoS

2. Click the pencil edit button 

   1. To set the bandwidth limit in a specific direction, select the Enabled checkbox for that direction

   2. Set QoS values to apply to each public IP in virtual datacenter. This bandwidth will be set for each public IP in the virtual datacenter.

...

Enabled

...

To enable traffic shaping in a specific direction, select this checkbox

...

Average

...

The average amount of bandwidth, in bits per second, that each public IP in the virtual datacenter can use

...

Peak

...

The maximum bandwidth in bits per second that each public IP in the virtual datacenter can use

...

Burst size

...

The amount of data that can be transmitted at the peak bandwidth rate in bytes. A burst bonus accumulates when traffic is below the Average value and this bandwidth can be used for bursts

For more details see: 

• Limit bandwidth of Public IPs with QoS

To register changes that were made outside the platform, save existing public IP bandwidth values. In the API, to register changes, send a POST request with the existing values.

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.

To reserve private IPs:

1. Go to Virtual datacenters → Networks → Private

2. Select the IPs and click the lock button

3. Enter the reason for the reservation

4. 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.

   Image Removed

The platform will display a padlock symbol and the reason beside the IP reserved addresses.

...

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.

• Limit bandwidth of public IPs with QoS

• Manage NAT QoS

...

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

  • Manage virtual datacenters

  • Manage firewalls

  • Manage load balancers

  • Administer and troubleshoot VMsManage persistent storage and VMs

• Work with VMs, see the Related pages list in myCloud view

  • VM network

• Manage and configure datacenter networks, see Networks   

• Configure network infrastructure, see Network