Abiquo 5.1

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Introduction to the NSX integration

Abiquo offers support for NSX with blueprints for:

  • NAT
  • Gateway
  • ECMP

Supported versions

  • Abiquo supports NSX version 6.1.x and version 6.2.x and version 6.3.x 
  • To use the firewall and load balancer functionality, NSX Advanced edition or higher is required.


  • Abiquo supports only one vCenter when working with NSX.
  • You will need a vCenter user with NSX administrator rights to use it from Abiquo.
  • Ensure the vCenter is managing all hosts so NSX can use vCenter to manage them.
    If there are unregistered hosts, the plugin will not work. Abiquo does not validate this.
  • Each NSX blueprint requires a separate Abiquo license.


  • Chef is not supported because the NSX DHCP does not support the required vendor-encapsulated-options.
  • Load balancers are only available through the NSX Gateway blueprint and the NAT blueprint
  • Abiquo does not currently support firewalls applied to load balancers.


  • We recommend using a cluster not managed by Abiquo to deploy the Edge appliances. This cluster is defined in the Remote Services appliance properties in each DC.

Include Page
Introduction to the NSX integration
Introduction to the NSX integration

Configure the integration

To configure the integration, Abiquo will supply a tool

  1. Use the tool supplied by Abiquo to get the values of the NSX configuration properties


  1. from the vCenter.


    • Later you can also


    • use this tool to check that the Abiquo properties are properly configured.


  1. Follow the specific steps for the chosen blueprint as described in the guides below:In a nutshell, you will need to perform the steps below:
    1. Set the NSX global properties and the enterprise defaults in the Remote Services properties.
    2. Set the NSX enterprise properties in Abiquo as necessary.
    3. In Abiquo, create the NSX devices for the configured plugin type. The endpoint will usually be something like  https://ADDRESS/api , where ADDRESS is the NSX appliance IP address. See Manage Devices

Integration details

This section describes the integration, but you should also see the documentation for individual elements, such as firewalls and load balancers.


Do not make changes to Abiquo NSX assets directly because Abiquo may not recognise the changed configuration and the integration won't work as expected.


It is not necessary to synchronize the NSX integration elements. Abiquo synchronization in NSX only applies to configurations that conform to Abiquo specifications with 1 x routing rule, identifier in comment field, and so on.


For the NAT plugin, the platform configures the same gateway for all vNICs of a VM (through the Edge / DHCP / static bindings). For the ECMP plugin, the platform only configures the default gateway in DHCP for the first vNIC.

For private networks, Abiquo will manage DHCP through the provisioned NSX appliances during VDC creation: