Abstract: Some embodiments provide a method for deploying edge forwarding elements in a public or private software defined datacenter (SDDC). For an entity, the method deploys a default first edge forwarding element to process data message flows between machines of the entity in a first network of the SDDC and machines external to the first network of the SDDC. The method subsequently receives a request to allocate more bandwidth to a first set of the data message flows entering or exiting the first network of the SDDC. In response, the method deploys a second edge forwarding element to process the first set of data message flows of the entity in order to allocate more bandwidth to the first set of the data message flows, while continuing to process a second set of data message flows of the entity through the default first edge node.

Abstract: Some embodiments provide a method for proxying ARP requests. At an MFE that executes on a host computer operating at a first site to implement a distributed router along with at least one additional MFE at the first site, the method receives, from a router at a remote second site, an ARP request for an IP address associated with a logical switch that spans the first site and the remote second site, and to which both the distributed router and the router at the remote second site connect. The method determines whether a table that includes IP addresses for a set of DCNs that use the distributed router as a default gateway includes the IP address. When the IP address is in the table, the method proxies the request at the host computer. When the particular IP address is not in the table, the MFE does not proxy the request.

Abstract: In some embodiments, a first network device in a first site sets a first IP address for an interface of the first network device to a value of a second IP address of a second network device in a second site. Policies are added in a policy table to cover IP addresses used in the second site and a specific route for a third IP address associated with a first workload migrated from the second site to the first site is added into a routing table. The first workload is on a stretched network that is coupled via a layer 2 channel. The policy table configures the first network device to send a second packet from the first workload to a third workload in the second site via the layer 2 channel when an IP address for the third workload does not match an eligible route in the routing table.

Abstract: In some embodiments, a method receives, by a first network device, a packet from a first workload that is located in first site. The first site includes stretched networks across a second site and a third site. The packet includes a destination IP address for a device in the second site. The method determines that the destination IP address does not match an eligible route in a routing table. The first workload was migrated from the second site to the first site and is located on a stretched network between the first site and the second site. A site identifier associated with the first workload is determined where the site identifier identifies the second site. The method selects a site policy based on the site identifier and uses the site policy to send the packet through a layer 2 channel to the second network device in the second site.

Abstract: Techniques are provided for designating, in an overlay transport virtualization (OTV) network connected to a data center, an edge device to act as a backup authoritative edge device (BAED) for an authoritative edge device (AED) for multicast packet encapsulation and forwarding. Data traffic associated with a given virtual local area network (VLAN) may be detected from a multicast source in the data center addressed to recipients in a site group. A mapping may be generated between the site group and a core data group in the OTV network for traffic from the multicast source. Advertisements may be sent of the mapping to edge devices in another data center across the OTV network. A similar configuration is presented for a BAED for inbound multicast traffic to a data center.

Abstract: Techniques are provided for designating, in an overlay transport virtualization (OTV) network connected to a data center, an edge device to act as a backup authoritative edge device (BAED) for an authoritative edge device (AED) for multicast packet encapsulation and forwarding. Data traffic associated with a given virtual local area network (VLAN) may be detected from a multicast source in the data center addressed to recipients in a site group. A mapping may be generated between the site group and a core data group in the OTV network for traffic from the multicast source. Advertisements may be sent of the mapping to edge devices in another data center across the OTV network. A similar configuration is presented for a BAED for inbound multicast traffic to a data center.