Versions Compared

Version Old Version 8 New Version 9
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: If properties are not present in the API NSX is not used

...

The following properties are global to the platform and must be configured in the DC Server and Remote Services applianceappliances:

NameDescription
abiquo.nsx.transport-zoneThe transport zone where the networks created by Abiquo will be attached.
abiquo.nsx.edge.cluster-idIdentifier (in VCenter) of the cluster where Abiquo will deploy the ESG.
abiquo.nsx.edge.datastore-idIdentifier (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
The gateway can be address 1. The reserved IPs range starts from address 2 for the number of IPs configured by the user, by default, up to address 21
Users should work with automatic IP allocation. In any case, the system administrator should inform the users of the range and by default, the first free address is address 22 

abiquo.nsx.virtualwire.teaming  

Set the teaming policy for the portGroup that is the backing for the VirtualWire when it is created. (minus) 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"