Migration of Virtual IP Addresses in a Failover Cluster

• US 20130159487A1
• Filed: 03/09/2012
• Published: 06/20/2013
• Est. Priority Date: 12/14/2011
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Patel, Parveen Kumar, Dion, David A., Petter, Vladimir, Sanders, Corey, Balasubramanian, Santosh, Bansal, Deepak, Benediktson, Daniel Brown
• Application Number:
  US13/415,844
• Publication Number:
  US 20130159487A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06F 2209/503 Resource availability
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer

Abstract

The movement of a Virtual IP (VIP) address from cluster node to cluster node is coordinated via a load balancer. All or a subset of the nodes in a load balancer cluster may be configured as possible hosts for the VIP. The load balancer directs VIP traffic to the Dedicated IP (DIP) address for the cluster node that responds affirmatively to periodic health probe messages. In this way, a VIP failover is executed when a first node stops responding to probe messages, and a second node starts to respond to the periodic health probe messages. In response to an affirmative probe response from a new node, the load balancer immediately directs the VIP traffic to the new node'"'"'s DIP. The probe messages may be configured to identify which nodes are currently responding affirmatively to probes to assist the nodes in determining when to execute a failover.

Claims

1. A method, comprising:

sending health probe messages to a plurality of virtual machines, each of the virtual machines associated with a Dedicated IP (DIP) address;

receiving response messages from one or more of the plurality of virtual machines;

identifying which virtual machine is currently supporting a subscriber application using the response messages, the subscriber application associated with a Virtual IP (VIP) address; and

routing VIP-addressed packets to the DIP associated with the virtual machine currently supporting the subscriber application.

2. The method of claim 1, wherein a load balancer sends the health probe messages, receives the response messages, and routes the VIP-addressed packets to the DIP.

3. The method of claim 1, wherein a load balancer sends the health probe messages, receives the response messages, the method further comprising:

instructing a router how to route the VIP-addressed packets to the DIP.

4. The method of claim 1, wherein one or more response messages indicates that a virtual machine is responsible for the subscriber application.

5. The method of claim 1, wherein a plurality of virtual machines are currently supporting a distributed subscriber application, and wherein VIP-addressed packets are routed to the DIPs associated with each of the virtual machines currently supporting the distributed subscriber application.

6. A method, comprising:

establishing, among two or more devices, a policy that defines which of the devices is responsible for hosting an application;

running the application on a host device identified by the policy;

receiving a health probe message from a load balancer;

sending a response to the health probe message from the host device, the response notifying the load balancer that the host device is responsible for hosting the application.

7. The method of claim 6, wherein the devices are virtual machines.

8. The method of claim 7, further comprising:

determining that a responsible virtual machine should no longer be responsible for the application by means of direct communication between the virtual machines; and

sending an unrequested response to the load balancer, the unrequested response indicating responsibility for hosting the application.

9. The method of claim 6, further comprising:

determining from the health probe message that no response to the health probe message has been sent by another device.

10. The method of claim 6, wherein the health probe message from the load balancer identifies a device that is currently responsible for the application.

11. The method of claim 6, wherein the devices are servers in a local area network.

12. The method of claim 11, further comprising:

monitoring responses to the health probe message sent by other servers; and

evaluating whether to host an application based upon the other servers'"'"' responses to the health probe message.

13. The method of claim 11, further comprising:

determining that no response to the health probe message was sent by another server within a predetermined time; and

sending an unrequested response to the load balancer, the unrequested response indicating responsibility for the application.

14. A system comprising:

a load balancer exposing a Virtual IP (VIP) address to a network;

a plurality of virtual machines hosted on a plurality of servers, each of the virtual machines assigned an address and adapted to receive and respond to health probes from the load balancer; and

a mapping maintained by the load balancer, the mapping indicating a relationship between the VIP and one or more of the addresses;

wherein the load balancer routes packets directed to the VIP address to a virtual machine'"'"'s address based upon the virtual machines'"'"' responses to the health probes.

15. The system of claim 14, wherein the addresses for the virtual machines are Dedicated IP (DIP) addresses.

16. The system of claim 14, wherein the addresses for the virtual machines are Media Access Control (MAC) addresses.

17. The method of claim 14, wherein the VIP address is configured as a local network interface address in the virtual machine currently handling traffic for the VIP address.

18. The system of claim 14, wherein the load balancer adapted to receive and redirect packets directed to the VIP address to a virtual machine'"'"'s address.

19. The system of claim 14, further comprising:

a router coupled to the virtual machines and the load balancer; and

wherein the load balancer is commands the router to redirect packets directed to the VIP address to a virtual machine'"'"'s address.

20. The system of claim 14, wherein the load balancer is a network load balancer comprising a plurality of software modules distributed across the virtual machines.