There are two options to mitigate looping. Either the NSX Edges and VMs can be on different ESXi hosts, or the NSX Edges and VMs can be on the same ESXi host.

About this task

  • Option 1: Separate ESXi hosts for the L2VPN Edges and the VMs

    1. Deploy the Edges and the VMs on separate ESXi hosts.

    2. Configure the Teaming and Failover Policy for the Distributed Port Group associated with the Edge’s Trunk vNic as follows:

      1. Load balancing as “Route based on originating virtual port.”

      2. Configure only one uplink as Active and the other uplink as Standby.

    3. Configure the teaming and failover policy for the distributed port group associated with the VMs as follows:

      1. Any teaming policy is okay.

      2. Multiple active uplinks can be configured.

    4. Configure Edges to use sink port mode and disable promiscuous mode on the trunk vNic.

  • Option 2: Edges and VMs on the same ESXi host

    1. Configure the teaming and failover policy for the distributed port group associated with Edge’s trunk vNic as follows:

      1. Load balancing as “Route based on originating virtual port.”

      2. Configure one uplink as active and the other uplink as standby.

    2. Configure the teaming and failover policy for the distributed port group associated with the VMs as follows:

      1. Any teaming policy is okay.

      2. Only one uplink can be active.

      3. The order of the active/standby uplinks must be the same for the VMs' distributed port group and the Edge’s trunk vNic distributed port group.

    3. Configure the client-side standalone edge to use sink port mode and disable promiscuous mode on the trunk vNic.