Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Abiquo 5.0

Skip to end of metadata
Go to start of metadata


Privilege: Manage datacenter infrastructure elements, Manage datacenter infrastructure elements, Manage network elements, Manage devices

Before you configure your private cloud networks in Abiquo, configure the network infrastructure outside of the platform. You will need ranges of VLAN tags and IP addresses for use in the platform. See Network in the Abiquo Infrastructure Guide.

To manage datacenter networks, go to Infrastructure → Private → select Datacenter → Datacenter details → Network

  • Manage devices that define SDN integrations in the platform. See Manage Devices
  • Create tags for datacenter networks and their corresponding hypervisor network interfaces. See Manage Network Service Types
  • Reserve network ranges for administration networks, see Manage excluded networks
  • View private cloud networks, which users create in virtual datacenters (VDCs). See Manage Networks
  • Manage External networks that belong to a single enterprise and may have public or private IP address ranges used in more than one VDC. See Manage External Networks
  • Manage Unmanaged Networks that are a special type of external network with IP addresses that are allocated outside of Abiquo. See Create Unmanaged Networks
  • Manage public networks that enable the users of VDCs to obtain Internet addressable public IP addresses for their virtual infrastructure. See Manage Public Networks 
  • Manage NAT networks with the NSX integration



Define network virtualization integrations with devices


The platform has integrations with network virtualization systems to offer features such as network blueprints, self-service firewall and load balancer policies, NAT, and VPNs. The platform uses Devices to define integrations with external systems.

Devices do the following:

  • register the endpoint and credentials of the network virtualization system in a private cloud datacenter
  • contain a list of the virtual datacenters that the network virtualization system is managing.

A device can be created:

  1. For a datacenter
  2. For a single enterprise

A device belonging to a specific enterprise has a higher priority than a device for all enterprises.

The device functionality is transparent to the cloud user, who will automatically have self-service access to networks, and firewall and load balancer policies.

Privilege: Manage devices

Devices on KVM

Each KVM hypervisor can only point to one Neutron device but it can be shared by multiple enterprises in the datacenter. So for KVM there are two main configurations:

  • Recommended: for all enterprises to use Neutron, a single global device for all enterprises that configures a single Neutron system
  • Alternative: for selected enterprises to use Neutron, a device for each enterprise that configures a single Neutron system

Related links




Reserve private network ranges with excluded networks

To create an excluded network:
  1. Go to Infrastructure → Private → select a datacenter → Servers view → Network → Excluded
  2. Click the + Add button and enter the network details


    Field

    Value

    Network Name

    The name of the network to exclude of up to 128 characters

    IPv6To exclude an IPv6 network, select this checkbox

    Address

    The network address of the network to exclude

    Netmask

    The network mask in CIDR format. For IPv4, the networks created in the platform the netmask can have a value from 16 to 30 inclusive, and for IPv6, it can have a value of 64, 56, or 48.

  3. Click Save. 
  4. If users already have private networks with this range, the platform will display a warning popup. To force the creation of the excluded range, click Confirm. 

The platform will exclude the network range. Users with existing private networks within the excluded range can continue to work with them. But if the users delete the networks, they will not be able to create them again. 


Manage excluded networks with the API

API Documentation

For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource ExcludedNetworksResource.




View private cloud networks

Administrators can display private cloud networks in Infrastructure view. To manage a private cloud network, go to the virtual datacenter that the network belongs to.

See Manage Networks


Create public networks for internet addressable IPs

Public Networks allow the users of virtual datacenters to use Internet addressable public IP addresses in their virtual infrastructure. Users purchase or reserve public IPs for their enterprises in Virtual datacenters view.

To create a public network:

  1. Go to Infrastructure → Private → select Datacenter → Datacenter details → Network → Public
  2. Complete the dialog


Field

Value

Name

The name of the public VLAN with up to 128 characters

IPv6To create an IPv6 network, select this checkbox
StrictFor IPv6 networks only. If you select Strict, the platform will automatically generate EUI64 IP addresses.

Address

The network address of the VLAN

Netmask

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

Gateway

The gateway of the network that must be within the range defined by the network address and the network mask

Tag*

Enter the VLAN or VXLAN tag to use for this network

Check

Click to check tag availability for all the racks of the Abiquo datacenter.

  • Green: available
  • Yellow: in use by other networks but can be reused
  • Red: not available because it is excluded by rack configuration.
Network service typeChoose the Network Service Type, which assigns the network to network interfaces on the hypervisors
DeviceOptional device that defines a network virtualization system that will manage the IP addresses of this network. They may be assigned using its DHCP service. Ensure that VMs deployed on this network allow traffic to the appropriate ports for a DHCP connection.

Primary DNS

Address of the primary DNS

Secondary DNS

Address of the secondary DNS

DNS suffix

The default DNS suffix

RestrictedSelect to create a Restricted network so that users require privileges to Attach NICs in restricted networks and/or Detach NICs from restricted networks
Excluded from firewallSelect Excluded from firewall to define a network where VM firewalls will not apply

Static Routes

Click "Manage" to add and modify static routes.



Create an external network for cross-platform networking

External networks belong to a single enterprise and may have public or private IP address ranges used in more than one virtual datacenter.

Before you begin:

  • If you are using a network virtualization system to manage external networks, first precreate the networks in the network virtualization systems. You will need the network address, gateway, and VLAN or VXLAN tag.
  • If you are using standard networking, you will need the VLAN tag to use with this network

  • If you are using vCloud Director, you can create or onboard external networks and manage them in the Virtual datacenters view. See VMware vCloud Director

To create an external network:

  1. Go to Infrastructure → Private → select Datacenter → Servers view → Network → External
  2. Click the  add button  and enter the details

Define static routes

Field

Value

Name

The name of the external VLAN with up to 128 characters

IPv6To create an IPv6 network, select this checkbox
StrictFor IPv6 networks only. If you select Strict, the platform will automatically generate EUI64 IP addresses.

Net. Address

The network address of the VLAN

Netmask (CIDR)

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

Gateway

The gateway of the network, which must be within the range defined by the network address and the network mask

Tag*

The tag to use for this network, e.g. VLAN tag

Check

Check tag availability for all racks of the datacenter as you should define each network with the same tag on all racks. Green = available, Yellow = in use, Red = unavailable

Network service typeSelect the Network Service Type, which represents a Network Interface on the hypervisors.

Unmanaged

Select to create an unmanaged network, when you will manage IP addresses outside Abiquo

Enterprise**

Select the owner enterprise that will use the external VLAN

DeviceTo 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

Primary DNS

Address of the Primary DNS server

Secondary DNS

Address of the Secondary DNS server

DNS suffix

The default DNS suffix

RestrictedSelect 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 firewallSelect Excluded from firewall to define a network where VM firewall policies will not apply

Static Routes

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.






Create static routes for external and public networks

To add a Static Route:
  1. When creating or editing an IPv4 network
  2. Select the Define checkbox. 
  3. Enter the details of the static route. For example, to add a static route to the network/netmask 1.1.1.0/24 via the gateway/next hop 192.168.0.250

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

  4. Click Save and the platform will add the static routes to the VM network configuration. To delete a static route, click the delete button ("X") beside the static route details.


Notes:
  • The platform will configure the static routes in VMs using the network configuration method so it may not always be possible to update the static routes in a deployed VM.
  • If you are using DHCP to configure VMs, changes to static routes will be received by the VMs when they reconnect to the DHCP server; for example, after they are restarted. 



Add IP addresses to external and public networks

To add IP addresses to your network:

  1. Go to Infrastructure → Private → select Datacenter → Servers view → Network → External or Public
  2. Click the + Add button in the top right-hand corner
  3. Complete the dialog

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. 
IP Addresses
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.





Make IP addresses available

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.

To edit the available IP addresses:

  1. Go Infrastructure → Private → select datacenter → Servers view → Network → select network type
  2. Click the Available IPs link in the top right-hand corner of the IPs page
  3. The Edit network popup for Available IPs will open and by default, all IPs will be in the Available column
  • To move an IP, select it and click a single arrow button
  • To move all IPs from one column to the other column, use the double arrow buttons to move in the direction indicated by the arrows

Notes
  • 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.




Make a network the default for an enterprise or virtual datacenter

You can make an external network the default for an enterprise in a datacenter (see Configure a location for an enterprise) or a virtual datacenter (See Manage Networks).

You can make a public or external network the default for a virtual datacenter (See Manage Networks)

Display networks

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



Create unmanaged networks

In private cloud datacenters, unmanaged networks are a special type of external network with IP addresses that are allocated outside of the platform. Abiquo does not manage the IP addresses for VMs attached to these networks.

Before you begin, obtain the details of your network in the infrastructure, including the VLAN tag, network address, and gateway.

To create unmanaged networks do these steps:

  1. Go to Infrastructure → Private → select Datacenter → Datacenter details → Network → External.
  2. At the top of the External page, click the Add + button  
  3. Complete the dialog as described, marking the Unmanaged checkbox.

FieldValue

Name

The name of the unmanaged VLAN with up to 128 characters

IPv6To create an IPv6 network, select this checkbox
StrictFor IPv6 networks only. If you select Strict, Abiquo will automatically generate EUI64 IP addresses and you will not be able to manually generate them

Address

The network address of the VLAN

Netmask

The network mask in CIDR format

Gateway

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

Tag

The VLAN tag to use for this VLAN

CheckCheck tag availability for all racks of the datacenter. You should define a VLAN with the same tag on all racks. Green = available, Yellow = in use, Red = unavailable
Network service typeSelect the Network Service Type, which represents a network interface on the hypervisors

Unmanaged

Select to create an unmanaged network, when you will manage IP addresses outside Abiquo

Enterprise

Select the owner enterprise that will use the unmanaged VLAN

DeviceNot used for unmanaged networks

Primary DNS

The IP address of the Primary DNS server

Secondary DNS

The IP address of the Secondary DNS server

DNS suffix

The default DNS suffix

RestrictedMark this checkbox to create a Restricted network. To work with IPs in a restricted network, users require the privileges to Attach NICs in restricted networks and/or Detach NICs from restricted networks
Excluded from firewallSelect Excluded from firewall to define a network where VM firewalls will not apply
Static routes

Not used for unmanaged networks


To display IP addresses of NICS in unmanaged networks, add them:

  • using the API; or
  • during VM capture using the UI or API 

For strict IPv6 networks, you cannot add IP addresses, but the platform retrieves the MAC address from the hypervisor and uses that to generate an IPv6 address for display, which should be the same as the one allocated by the router system.




Configure NAT for datacenters

As part of the Abiquo NSX integration, you can use the NAT blueprint to configure virtual datacenters with NAT.

To configure NAT for a datacenter:

  1. Go to Infrastructure → Private → select datacenter → Network → Devices
  2. To define the NSX integration in Abiquo, create a NAT device




Create a NAT network

To use NAT in private cloud, first configure the NSX integration, then define the NAT device. NAT networks are very similar to public networks.

To use NAT in vCloud Director, you will need the definition of a NAT network that is compatible with an Edge interface network, which connects the Edge to the external networks.

To create a NAT network: 

  1. Go to InfrastructurePrivate or Public → select datacenter or region → Servers view → Network → NAT
  2. Click the + add button

  3. Create networks with ranges of public IPs for NAT

    Field

    Value

    Network Name

    The name of the NAT network

    Net. AddressThe network address of the NAT network

    Netmask

    The network mask in CIDR format. For IPv4, the networks created in the platform the netmask can have a value from 16 to 30 inclusive, and for IPv6, it can have a value of 64, 56, or 48.

    Device

    For NSX, the device that will manage the NAT network

  4. To add IP addresses to your network, click the + add button in the top right-hand corner of the Networks page.

    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. 
    IP Addresses
    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.

The NAT network and IPs will display on the NAT tab. In the same way as for public IPs, you can quarantine NAT IPs as required.

Screenshot: NAT networks and IPs in private cloud with NSX

When users create virtual datacenters, the platform can automatically configure a NAT IP, and users can manage NAT rules, and purchase additional NAT IPs. See Manage NAT for virtual datacenters

API Documentation

For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource NatNetworksResource.