Vmware, Inc.

Avinash Nigam

Ambarish Prashant Pande

Rohan Gandhi

Amol Manohar Vaikar

Prahalad Gowardhan Deshpande

Vishal Ranjan

Abhijit Sharma

Ravi Singhal

Philip Brighten Godfrey

Shashank Ranjan

Devraj Narendra Baheti

Somil Bhandari

Gourab Ghosh

Prashant Jain

Gaurav Agarwal

Rohit Toshniwal

Madan Singhal

Amarjit Gupta

Gyan Sagar Sinha

Example methods and systems for packet flow monitoring are described. In one example, a first computer system may detect a flow of packets along a datapath between a source and a destination and determine source attribute information associated with the source and destination attribute information associated with the destination. The first computer system may perform attribute-to-identifier mapping by (a) mapping the source attribute information to a source identifier having a reduced size compared to the source attribute information, and/or (b) mapping the destination attribute information to a destination identifier having a reduced size compared to the destination attribute information. The first computer system may generate flow information that includes (a) the source identifier identifying the source and/or (b) the destination identifier identifying the destination; and interact with a second computer system, or storage accessible by the second computer system, to enable the second computer system to obtain the flow information.

Packet flow monitoring with attribute-to-identifier mapping

Embodiments described herein generally involve identifying workloads in a multi-site networking environment. Embodiments include determining that a given network is stretched across a first network segment at a first site and a second network segment at a second site. Embodiments include creating a stretched administrative domain for the given network and mapping an address of the given network to the stretched administrative domain in a lookup table for an administrative domain associated with the first network segment. Embodiments include receiving a flow record from an observation point in the first network segment, the flow record having a source IP address associated with the second network segment and a destination IP address associated with the first network segment. Embodiments include identifying a source workload and destination workload of the flow record using the lookup table and a workload identification table that maps combinations of IP addresses and administrative domains to workloads.

Workload identification for network flows over stretched layer 2 networks

Some embodiments provide a novel method for assessing the suitability of network links for connecting compute nodes located at different geographic sites. The method of some embodiments identifies and analyzes sample packets from a set of flows exchanged between first and second compute sites that are connected through a first network link in order to identify attributes of the sampled packets. The method also computes attributes of predicted packets between the identified samples in order to identify attributes of each flow in the set of flows. The method then uses the identified and computed attributes of each flow in the set of flows to emulate the set of flows passing between the two compute sites through the second network link in order to assess whether a second network link should be used for future flows (e.g., future flows exchanged between the first and second compute sites).

Emulating packet flows to assess network links for SD-WAN

A method for alleviating flow congestion at forwarding elements is provided. The method receives traffic related data from a plurality of forwarding elements of a network, and based on the traffic related data, determines congestion at a first forwarding element of the plurality of forwarding elements caused by at least one flow passing through the first forwarding element at a first rate. The method calculates, based on a burst size of the at least one flow, a second rate for the at least one flow such that when the at least one flow passes through the first forwarding element at the second rate the congestion at the first forwarding element is alleviated. The method rate limits the at least one flow by passing the at least one flow through a flow rate manager at the calculated second rate before transmitting the at least one flow to the first forwarding element.

Alleviating flow congestion at forwarding elements

Some embodiments provide a novel method of tracking connections in a network. The method receives an identification of a first network endpoint and a second network endpoint. The method then determines that the first network endpoint cannot directly address a packet flow to the second network endpoint. The method identifies an address translation rule of a network device that translates an address of the second network endpoint into a translated address. The method then determines that the first network endpoint can directly address a packet flow to the translated address. The method then identifies a route from the first network endpoint to the second endpoint through the network device that translates the address and displays the route including an identifier of the network device.

Identifying routes with indirect addressing in a datacenter

A computer network optimization methodology is disclosed. In a computer-implemented method, components of a computing environment are automatically monitored, and have a feature selection analysis performed thereon. Provided the feature selection analysis determines that features of the components are in frequent communication and generating network latency. Provided the feature selection analysis determines that features of the components are not well defined, a similarity analysis of the features is performed. Results of the feature selection methodology are generated, and the components involved in the network traffic latency are reassigned to migrate the latency.

System and method for optimizing network topology in a virtual computing environment

An example method of identifying a hybrid connection associated with a network flow in a multi-cloud computing system includes: obtaining, by a network analyzer, network information from a plurality of data centers in the multi-cloud computing system, the plurality of data centers corresponding to a respective plurality of namespaces; identifying Internet Protocol (IP) subnetworks associated with the hybrid connection from the network information; generating connection indexes for the namespaces relating source IP subnetworks of the IP subnetworks, destination IP subnetworks of the IP subnetworks, and an identifier for the hybrid connection; searching a source IP address and a destination IP address of a flow record for the network flow in the connection indexes to obtain the identifier for the hybrid connection; and tagging the flow record with the identifier for the hybrid connection.

Identifying hybrid connectivity for traffic flows in a multi-cloud environment

The disclosure provides an approach for service deployment. Embodiments include receiving an indication of user intent for deployment of one or more services in a network from a user that is not an administrator of the network, wherein the indication of the user intent comprises a domain specific language (DSL). Embodiments include parsing the indication of the user intent to determine one or more constraints for deploying the one or more services. Embodiments include receiving topology information for the network, wherein the topology information comprises associations between racks and machines in the network. Embodiments include receiving network performance information for the network. Embodiments include determining one or more deployment rules for the one or more services based on the one or more constraints, the topology information, and the network performance information. Embodiments include deploying the one or more services in the network based on the one or more deployment rules.

Rack-aware and network performance-aware service deployment

A system and method for topology construction in hybrid cloud environments includes receiving connection information from a local perimeter edge router of a local network that has a known topology and receiving connection information from a remote perimeter edge router of a remote network that is provided by a cloud provider. The received local perimeter edge router connection information is associated with the received remote perimeter edge router connection information. The associated connection information is normalized to a generic model, the generic model representing connections having different link layer policies in a generic way and the normalized connection information is applied to a network topology of the local network and the remote network.

System and method for topology construction in hybrid cloud environments

A method for creating a flow profile is provided. The method identifies a first plurality of flow measurements, each of which corresponding to one of a plurality of flows exchanged between a computing entity and a service during a first time period. The method, for each of a first plurality of buckets each of which has a pair of lower and upper bounds, increments a counter of the corresponding bucket for each of the plurality of flow measurements that falls within the pair of bounds of that bucket. The method generates a second plurality of buckets by merging and splitting at least some of the first plurality of buckets, identifies a second plurality of flow measurements for the computing entity during a second time period, and distributes these measurements into the second plurality of buckets. The method generate the flow profile by aggregating the first and second pluralities of buckets.

Generating network flow profiles for computing entities

Embodiments described herein generally involve identifying workloads in a networking environment based on a flow record from an observation point. In one embodiment, network data is received from one or more endpoints and used to determine a plurality of administrative domains. Each administrative domain comprises a distinct section of the networking environment within which every Internet Protocol (IP) address is unique. The network data may be used to generate observation point mapping information that maps each observation point to an administrative domain, lookup tables associated with each of the plurality of administrative domains that map IP addresses to administrative domains, and a workload identification table that maps combinations of IP addresses and administrative domains to workloads. The flow record is received from the observation point and a source and destination workload of the flow record are identified using the observation point mapping information, applicable lookup table, and workload identification table.

Growing community of inventors

Pune, India

Avinash Nigam