Author: Unlicensed user
Every time a VDC is deployed, Abiquo will create a NSX edge and connect it the uplink network to provide gateway, router, firewall, load balancing and SNAT services to the VMs inside the VDC.
Limitations
- Maximum 9 private networks per VDC as per NSX limitation
- Load balancing do not support firewalls.
Abiquo properties
The following properties are global to the platform and must be configured in the DC Remote Services appliance:
| Name | Description |
|---|---|
| abiquo.nsx.transport-zone | The transport zone where the networks created by Abiquo will be attached. |
| abiquo.nsx.edge.cluster-id | Identifier (in VCenter) of the cluster where Abiquo will deploy the ESG. |
| abiquo.nsx.edge.datastore-id | Identifier (in VCenter) of the datastore where Abiquo will deploy the ESG. |
abiquo.nsx.edge.dvportgroup-id | Id of the port group where Abiquo will attach the ESG uplink. |
| abiquo.nsx.edge.public-network-cidr | Network range where the ESG uplink IP and the "public" load balancer IPs will be taken from. It must be a range dedicated to Abiquo. |
| abiquo.nsx.load-balancer-reserved-ips | Number of IP addresses that are reserved for NSX in each private network to allocate to load balancers. Default: 20 |
abiquo.nsx.virtualwire.teaming | Set the teaming policy for the portGroup that is the backing for the VirtualWire when it is created.  This value is required and you cannot change it after creation. It can be set as an enterprise property without the abiquo prefix.Suggested default: "failover_explicit" Values: "failover_explicit", "loadbalance_ip", "loadbalance_loadbased", "loadbalance_srcid", or "loadbalance_srcmac" |