Partner discovery in control clusters using shared VLAN

• US 9,929,934 B2
• Filed: 06/03/2015
• Issued: 03/27/2018
• Est. Priority Date: 12/09/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chokshi, Shaival J., Qin, Xiaohan, Vo, Patrick T.
• Primary Examiner(s): Cattungal, Ajay
• Application Number:
  US14/730,020
• Publication Number:
  US 20160164740A1
• Time in Patent Office: 1,028 Days
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 45/026 Details of "hello" or keep-alive messages

Abstract

At a first virtual device executing in a data processing system, a determination is made whether a partner list associated with the first virtual device includes a threshold number of partner virtual devices, the first virtual device participating in the control cluster. A first Live packet is unicast over the VLAN to each partner virtual device identified in the partner list. A unicast of a second Live packet from a second virtual device to the first virtual device is received over the VLAN, the second virtual device being identified in the partner list. A Hello packet is broadcast over the VLAN to cause the Hello packet to reach a third virtual device, wherein the Hello packet is configured to discover a new partner virtual device to add to the partner list, discovering the new partner enlarging the control cluster.

Claims

1. A method for partner discovery in a control cluster using a shared virtual local area network (VLAN), the method comprising:

determining, at a first virtual device executing in a data processing system, whether a partner list associated with the first virtual device includes a threshold number of partner virtual devices, the first virtual device participating in the control cluster, and a partner virtual device in the partner list of the first virtual device operates as a redundant backup of the first virtual device, the first virtual device and the partner virtual device forming a control channel in the control cluster, the control cluster including the first virtual device and each partner virtual device from the partner list of the first virtual device, and wherein any virtual device in the control cluster can operate as a control adapter in the control cluster;

unicasting over the VLAN, responsive to the partner list not being empty, to each partner virtual device identified in the partner list, a first Live packet, wherein the first Live packet identifies each partner virtual device already in the partner list of the first virtual device;

receiving over the VLAN, responsive to the partner list not being empty, a unicast of a second Live packet from a second virtual device to the first virtual device, the second virtual device being identified in the partner list; and

broadcasting over the VLAN, a Hello packet, to cause the Hello packet to reach a third virtual device, wherein the Hello packet is configured to discover a new partner virtual device to add to the partner list, discovering the new partner enlarging the control cluster.

2. The method of claim 1, wherein the third virtual device is a member of a plurality of virtual devices that are available in the data processing system but are not on the partner list, further comprising:

constructing, at the first virtual device, the Hello packet, the Hello packet communicating to a virtual device that is not on the partner list (i) that the first virtual device is available in the control cluster, (ii) the condition that has to be satisfied to become a partner virtual device of the first virtual device, and (iii) a list of identifiers comprising identifiers of each partner on the partner list of the first virtual device.

3. The method of claim 1, further comprising:

receiving over the VLAN, responsive to broadcasting the Hello packet, from the third virtual device to the first virtual device, a unicast of a third Live packet; and

adding, responsive to receiving the unicast of the third Live packet, the third virtual device to the partner list.

4. The method of claim 1, further comprising:

constructing, at the first virtual device, the first Live packet, the first Live packet communicating to a partner virtual device on the partner list (i) that the first virtual device remains available in the control cluster, and (ii) a list of identifiers comprising identifiers of each partner on the partner list of the first virtual device.

5. The method of claim 4, wherein the partner virtual device is also identified in the list of identifiers.

6. The method of claim 1, further comprising:

receiving over the VLAN, from the second virtual device to the first virtual device, a unicast of a Bye packet; and

removing, responsive to receiving the Bye packet, the second virtual device from the partner list.

7. The method of claim 1, further comprising:

maintaining a Live timer to establish a periodicity of unicasting the first Live packet.

8. The method of claim 1, wherein the third virtual device is not identified in the partner list.

9. The method of claim 1, further comprising:

maintaining a Hello timer to establish a periodicity of broadcasting the Hello packet.

10. The method of claim 1, further comprising:

resetting, responsive to receiving the second Live packet a Timeout timer, the Timeout timer establishing a timeout period within which the second Live packet should be received from the second virtual device in order to maintain the second virtual device as active in the partner list.

11. The method of claim 10, further comprising:

failing to receive, within the timeout period, a unicast of a third Live packet from a third virtual device, the third virtual device being identified in the partner list; and

marking, responsive to the failing, the third virtual device as inactive in the partner list.

12. The method of claim 1, wherein the control cluster comprises a plurality of virtual devices, each device in the plurality of virtual devices being operable to perform identical functions in the data processing system, wherein the plurality of virtual devices includes the first virtual device the second virtual device and the third virtual device, and wherein the control cluster facilitates one of a (i) failover operation, (ii) a redundancy, and (iii) a load balancing operation, between the first virtual device and another virtual device in the plurality of virtual devices that is identified as a partner of the first virtual device in the first virtual device'"'"'s partner list.

13. The method of claim 1, further comprising:

representing a physical device in a host system as the first virtual device, where the data processing system shares the physical device by using the first virtual device according to a Partner Discovery Protocol (PDP).

14. The method of claim 1, wherein the data processing system comprises a partition of a host system.

15. The method of claim 1, wherein the data processing system comprises a Virtual Input Output Server (VIOS), wherein the first virtual device executes under the VIOS.