Cisco Technology, Inc.

Vmware, Inc.

Nicira, Inc.

Dileep Kumar Devireddy

Chidambareswaran Raman

Sreenivas Duvvuri

Hongwei Zhu

Abhijit Patra

Nagaraj Bagepalli

Subin Cyriac Mathew

Ganesh Sadasivan

Venkateshwar Rao Pullela

Ankit Parmar

Bhushan Mangesh Kanekar

Ganesan Chandrashekhar

Hitesh Patel

Surendra M Kumar

David W Chang

Feng Gu

Shyam N Kapadia

Michael R Smith

Saravanakumar Rajendran

Jeffrey Ym Wang

Gyaneshwar S Saharia

Pradeep Kumar Kathail

Alexander Tessmer

Dipankar Bhattacharya

Chandrashekhar Appanna

William Norman Eatherton

Nilesh Shah

Wenyi Jiang

Nithin Bangalore Raju

Jaushin Lee

Giovanni Meo

Chickayya Naik

Fusun Ertemalp

Hugh Holbrook

Herman Levenson

Priyank Ramesh Warkhede

Harish Manoharan

Ashoka Kallappa

Bangalore Priyadarshan

Qizhong Chen

Suresh Gurajapu

Mingsheng Peng

Hiteshkumar Rameshchandra Patel

Victor Manuel Moreno

Fabio Rodolfo Maino

Yibin Yang

Paul M Quinn

Prashant Gandhi

Vina Ermagan

Minjal Agarwal

Govind Prasad Sharma

Murali Anantha

ChiHsiang Su

Faisal Mushtaq

David Wei-Shen Chang

Ramesh V N Ponnapalli

Shreeram Bhide

Xiaohu Wang

Stephen Francis Scheid

Ambarish Chintamani Kenghe

Atul Rawat

Shyamsundar Pullela

Ritesh Tiwari

Subha Dhesikan

Michael Smith

Bangalore L Priyadarshan

Hugh Weber Holbrook

Prashant P Gandhi

Some embodiments provide a method that receives (i) definition of a group of virtual datacenters and (ii) addition of at least two virtual datacenters to the group. Each virtual datacenter is defined in a public cloud and includes a set of network management components and a set of network endpoints connected by a logical network that is managed by the network management components of the virtual datacenter. Based on the definition of the group, the method configures a gateway router to which each of the virtual datacenters of the group connect. The gateway router is for routing traffic between the virtual datacenters of the group. The method also configures, at each respective virtual datacenter, a respective router to route data traffic between the respective virtual datacenter and the other virtual datacenters to route traffic for the other virtual datacenters to the gateway router.

Connectivity between virtual datacenters

Described herein are systems, methods, and software to manage internet protocol (IP) address allocation for tenants in a computing environment. In one implementation, a logical router associated with a tenant in the computing environment requests a public IP address for a new segment instance from a controller. In response to the request, the controller may select a public IP address from a pool of available IP addresses and update networking address translation (NAT) on the logical router to associate the public IP address with a private IP address allocated to the new segment instance.

Managing internet protocol (IP) address allocation to tenants in a computing environment

In some embodiments, a method adds a specific route for an IP address that is associated with a first workload into a routing table for a first network device in a first site in response to the first workload being migrated from a second site to the first site. The first network device receives a packet from a second workload for the first workload and determines that a destination of the packet matches the specific route in the routing table. The method routes the packet from the second workload to the first workload using the specific route in the routing table without sending the packet to the second site.

Routing using specific routes

The disclosure provides an approach for seamless hand-off of data traffic in public cloud environments. Techniques are provided for activating an edge services gateway (ESG) virtual computing instance (VCI) on a new host. Prior to activating the ESG VCI on the new host, an underlay routing table is reprogrammed to associate a first IP address of a first tunnel endpoint (TEP) with a first network interface of an old host and to associate a second IP address of a second TEP with a second network interface of the new host. The routing table associates a third IP address of the ESG VCI with the first network interface. After activating the ESG VCI, a packet having as a destination address the third IP address is received at the first network interface and is encapsulated, by the first TEP, with an outer header having as a destination address the second IP address.

Seamless hand-off of data traffic in public cloud environments

In an embodiment, a computer-implemented method for providing dynamic mechanisms for resource-path-based, dynamic group membership support for local and external membership groups is described. A method comprises: detecting, by a group resolver implemented in a management and control plane, that information about an object stored in the plane was created or updated; determining whether a URI of the object matches a URI regular expression and other conditions specified in membership criteria created for a membership group; in response to determining that a URI of the object matches a URI regular expression and other conditions specified in membership criteria created for a membership group: distributing the information about the object to network agents implemented in transport nodes to cause the network agents to automatically update a group membership policy associated with the membership group; and wherein the group membership policy affects packet forwarding behavior of a forwarding node.

Resource-path-based, dynamic group membership support for membership groups

In some embodiments, a method configures, at a first host, an overlay channel for sending packets to check whether a failure has occurred at a workload. The first host and a second host are connected via a layer 3 network. The first host generates a packet to check whether the failure has occurred at the workload and encapsulates the packet. The first host sends the encapsulated packet to the second host using the overlay channel via the layer 3 network. The packet is decapsulated and forwarded to the workload at the second host.

Split-brain prevention in a high availability system during workload migration system during workload migration

In some embodiments, a method determines when a packet is fragmented into multiple fragmented packets in a flow between a first workload and a second workload. The method switches from generating an outer source port in the outer header using layer 4 information from the inner header to using layer 3 information from the inner header. A fragmented packet is encapsulated with the outer header that includes an outer source port value that is generated using the layer 3 information. The method initiates a process to determine when to switch back to using layer 4 information from the inner header to generate the outer source port. When it is determined to switch back to using layer 4 information, the method switches back to using layer 4 information from the inner header to generate the source port in the outer header of a packet from the first workload.

Adaptive source port generation in overlay networks

In some embodiments, a method detects a state of a first session between a first workload and a second workload. The first workload and the second workload send packets in the first session via a first path to maintain a state of the first session. When the state of the first session indicates the first workload is down, the method receives information for network metrics of network traffic being sent in the first path. The method determines when the second workload should transition from a standby mode to an active mode to take over as an active workload in an active/standby configuration between the first workload and the second workload based on the information for the network metrics.

Failover prevention in a high availability system during traffic congestion

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. The method in some embodiments receives the request for more bandwidth by first receiving a request to create a traffic group and then receiving a list of network addresses that are associated with the traffic group. In some embodiments, the method receives the list of network addresses associated with the traffic group by receiving a prefix of network addresses and receiving a request to associate the prefix of network addresses with the traffic group. Based on this request, the method then creates an association between the traffic group and the received prefix of network addresses.

Allocating additional bandwidth to resources in a datacenter through deployment of dedicated gateways

Some embodiments provide policy-driven methods for deploying edge forwarding elements in a public or private SDDC for tenants or applications. For instance, the method of some embodiments allows administrators to create different traffic groups for different applications and/or tenants, deploys edge forwarding elements for the different traffic groups, and configures forwarding elements in the SDDC to direct data message flows of the applications and/or tenants through the edge forwarding elements deployed for them. The policy-driven method of some embodiments also dynamically deploys edge forwarding elements in the SDDC for applications and/or tenants after detecting the need for the edge forwarding elements based on monitored traffic flow conditions.

Many hybrid cloud topologies require virtual machines in a public cloud to use a router in a private cloud, even when the virtual machine is transmitting to another virtual machine in the public cloud. Routing data through an enterprise router on the private cloud via the internet is generally inefficient. This problem can be overcome by placing a router within the public cloud that mirrors much of the routing functionality of the enterprise router. A switch configured to intercept address resolution protocol (ARP) request for the enterprise router's address and fabricate a response using the MAC address of the router in the public cloud.

Default gateway extension

Growing community of inventors

San Jose, CA, United States of America

Dileep Kumar Devireddy