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 9 Next »

Author: Unlicensed user

This guide describes how to configure Abiquo to create the NSX infrastructure for each Virtual Datacenter according to the following blueprint.

Every time a VDC is deployed, Abiquo will create the DLRs and ESGs, and connect them to the tenant network to provide gateway, DHCP, routing and firewall services to the VMs inside the VDC.

 NSX ECMP diagram

Limitations

  • NSX ECMP does not support load balancers.
  • Maximum 1 VDC per tenant.

Abiquo properties

 

The following properties are global to the platform and you must configure them in the DC Remote Services appliance:

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 DLRs and ESGs
abiquo.nsx.edge.datastore-idIdentifier (in VCenter) of the datastore where Abiquo will deploy the DLRs and ESGs

The following properties can be configured globally or per tenant. See Manage tenant properties to configure them as tenant properties.

To configure properties globally in the DC Remote Server properties, use them with an abiquo. prefix:

NameDescription
nsx.gateway.network-idVLAN tag of the tenant network where the ESGs will be connected. Abiquo will create a distributed port group if none exists for that VLAN
nsx.gateway.networkNetwork CIDR of the tenant network
nsx.gateway.datacenterThe Datacenter where Abiquo will create the distributed port group for the tenant VLAN, if missing

nsx.gateway.dvs

The distributed virtual switch where Abiquo will create the distributed port group for the tenant VLAN, if missing

nsx.gateway.bgp.as

Identifier of the AS used in the tenant network

nsx.gateway.bgp.from-edge-password

BGP password for gateway from Edge
nsx.edge.uplink.ipsComma separated list of the IP addresses to assign to the uplink interfaces of the ESGs. The number of IP addresses here will determine the number of ESGs Abiquo will deploy when creating a Virtual datacenter
nsx.edge.bgp.peersComma separated list of the IP addresses to be configured as BGP neighbor of each ESG uplink
nsx.edge.bgp.asIdentifier of the AS used by the ESGs

nsx.edge.bgp.from-local-password

BGP password from local
nsx.edge.bgp.hold-down-timerHold down timer value for the BGP between the ESGs and the tenant network
nsx.edge.bgp.keep-alive-timerKeep alive timer or the BGP between the ESGs and the tenant network
nsx.edge.bgp.weightWeight of each neighbor in the BGP between the ESGs and the tenant network
nsx.local.bgp.asIdentifier of the AS used by the local DLR
nsx.local.bgp.hold-down-timerHold down timer value for the BGP between the DLR and the ESGs
nsx.local.bgp.keep-alive-timerKeep alive timer for the BGP between the DLR and the ESGs
nsx.local.bgp.weightWeight of each neighbor in the BGP between the DLR and the ESGs

nsx.transit.network

Network CIDR of the transit network

nsx.virtualwire.teaming  

Use this property to set the teaming policy for the portGroup that is the backing for the VirtualWire when it is created. This value cannot be changed after it is created.
Default: "failover_explicit"
Values: "failover_explicit", "loadbalance_ip", "loadbalance_loadbased", "loadbalance_srcid", or "loadbalance_srcmac"

  • No labels