Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »


Abiquo SDN integrations work with NSX-V and NSX-T network managers to provide blueprints for software defined networking that include features such as firewalls, load balancers, VPNs, and NAT in private cloud datacenters.

For compatible versions of VMware NSX and NSX-T, see VMware.

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


Features 

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.


Context properties

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.

Abiquo standard VLAN management requires DHCP and VLAN support on the Service Network. Abiquo includes a basic DHCP Server in the platform and it also offers dnsmasq. To provide DHCP services you can also use a DHCP relay server or separate DHCP server. If you are using an SDN solution, Abiquo can use its DHCP system. 

To install a 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

It is also possible to assign VM network addresses using cloud-init.


  • No labels