Abiquo 4.7

Skip to end of metadata
Go to start of metadata

This section describes the implementation details and configuration of network virtualization integrations to offer SDN features.

 Within Abiquo, cloud administrators use logical devices to define the network virtualization systems for datacenters and enterprises. 

Currently, Abiquo integrates with OpenStack Neutron and VMware NSX SDN solutions.

Compatibility table

Abiquo SDN integrations with network managers to provide software defined networking blueprints including firewalls and load balancers in private cloud datacenters.

VendorNetwork managerVersionNotes
OpenStackNeutronKilo +With KVM hypervisors and OpenStack clouds




For firewalls and load balancers use the Advanced edition or higher


CharacteristicsOpenStack NeutronVMware NSX (Gateway)VMware NSX (ECMP)
Firewall policies(tick)(tick) Firewalls will only apply to VMs, not load balancers(tick)
Load balancers(tick)(tick)


Private networks(tick)(tick)(tick)
Static routes(tick)(tick)(tick)
External networks-(tick)(tick)
Public networks - IPs-(tick)(tick)


Abiquo only supports the use of ONE network virtualization system per enterprise and datacenter. Abiquo will always use the most specific device for networking virtualization.


Abiquo supports IPv4 for DHCP and access to the Abiquo console/GUI. Abiquo supports IPv6 for DHCPv6.

Abiquo standard VLAN management requires DHCP and VLAN support on the Service Network. The default DHCP solution is a DHCP Server included in the platform. Or you can provide DHCP services with a DHCP relay server or separate DHCP server. To install your DHCP solution on a VM, the hypervisor must support listening to multiple VLANs (e.g. ESXi, KVM). If you do not use a separate DHCP solution, install the Abiquo Monolithic Server or separate Abiquo Remote Services server on a hypervisor with VLAN support. See Network Configuration for Virtualizing Abiquo