Microsoft Technology Licensing, LLC

Ranjit Puri

Madhan Sivakumar

Vikas Bhardwaj

Manish Tiwari

Benjamin M Schultz

David G Thaler

Daniel Max Firestone

Harish Kumar Chandrappa

Mahmoud S Elhaddad

Keith Loren Mange

Deepak Narula

Xuan Zou

Keerthi Shankar

An overlay network refers to a network that is implemented as various different virtual resources on a physical network referred to as an underlay network. Diagnostics are performed on the overlay network by injecting diagnostic packets from a source endpoint targeting a target endpoint. These endpoints can be in the overlay network, on-premises with the other endpoint but in a different overlay network, or off-premises form the other endpoint. The diagnostic packets include a data packet encapsulated with a diagnostic encapsulation header that can be removed by a network element in the underlay network to allow processing of the data packet, and then added back on. The network element maintains trace information that is a record of receipt of the diagnostic packet and operations performed on the diagnostic packet. A tracing service collects and analyzes this trace information from the various network elements.

Active flow diagnostics for cloud-hosted networks

A load balancer receives a client request from a client device for a connection to an application. The load balancer queries a monitoring server for a list of one or more application servers associated with the application. The monitoring server determines, based on cache state information of the plurality of application servers, the list of one or more application servers. The load balancer establishes a connection on behalf of the client device to one of the application servers.

State-aware load balancing of application servers

Methods, systems, and devices are described herein for modifying the monitoring of the health of a data center IP endpoint (such as VM) during live migration of the data center IP endpoint from a source host to a destination host. In one example, the described techniques may include receiving an indication that a virtual machine is going to be live migrated from a source host to a destination host. Next, evaluation of health probe responses originating from the virtual machine may be suspended for a time period. The time period may be selected based on the live migration. The evaluation of the probe responses originating from the virtual machine may be resumed upon completion of the time period. In some cases, a health probe status of the virtual machine may be migrated from the source host to the destination host.

Live migration of probe enabled load balanced endpoints in a software defined network

Methods, systems, and devices are described herein for managing a load balancer bypass between two virtual machines through live migration of at least one of the virtual machines. In one aspect, a load balancer bypass may be established between a source virtual machine associated with a source host and a destination virtual machine associated with a destination host. The source virtual machine identification information, source host identification information, destination virtual machine identification information, and destination host identification information may be associated with an indication of whether the bypass is active, for example, in a bypass data structure. Upon a determination that live migration of at least one of the source virtual machine or the destination virtual machine has been completed to a third host, the bypass data structure may be updated with identification information of the third host to maintain the load balancer bypass after completion of the live migration.

Live migration of load balanced virtual machines via traffic bypass

Growing community of inventors

Bothell, WA, United States of America

Ranjit Puri