Versions Compared

Key

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

...

Characteristics

VMware NSX (gateway)

VMware NSX (NAT)

VMware NSX (ECMP)

VMware NSX-T

Firewall policies

(tick) Firewalls will apply to VMs
only, not load balancers

(tick) Firewalls will apply to VMs
only, not load balancers

(tick)

(tick)

Load balancers

(tick)


(tick)


 -

(tick)

Private networks

(tick)

(tick)

(tick)

(tick)

Static routes

(tick)

(tick)

(tick)

(tick)

External networks

(tick)

(tick)

(tick)

-

Public networks - IPs

(tick)

(tick)

(tick)

-

NAT

(tick)

(tick)

VPNs

(tick)

(tick)

(tick)


Limitations

By default, 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 uses context properties to enable the administrator to enter configuration values when creating a resource. For example, for the NSX-T plugin, to use more than one Tier-0 configuration per tenant, register the Tier-0 configuration when you are creating each virtual datacenter. See Configure the Abiquo NSX-T integration#Tintegration-ConfigurationtousemorethanoneTier-0configurationpertenant.

For NSX ECMP, to enable the administrator to create more than one VDC per enterprise, you can use context properties to configure the uplink IPs for each virtual datacenter. If you set Uplink IPs with enterprise properties, you have to change the enterprise properties after creating each VDC in an enterprise. See Create multiple VDCs with NSX ECMP.


DHCP

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

...