Clustering support across geographical boundaries

• US 9,742,877 B2
• Filed: 12/04/2012
• Issued: 08/22/2017
• Est. Priority Date: 12/04/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cruz-Aguilar, Esdras E., Ganesh, Perinkulam I., Kandasamy, Madhusudanan, Wu, Christine J.
• Primary Examiner(s): Chou, Alan S
• Application Number:
  US13/692,803
• Publication Number:
  US 20140156861A1
• Time in Patent Office: 1,722 Days
• Field of Search: 709230
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

An approach is presented that provides computer clustering support across geographical boundaries. Inter-node communications are managed in a cluster by having each node operate at the network device driver (NDD) level within the kernel. Multiple types of NDD are utilized (Ethernet, SAN, DISK etc.) to provide redundancy so that nodes can reliably exchange heartbeat. To align with this architecture, for remote nodes, a pseudo NDD is used over Transmission Control Protocol (TCP) based communication interface to work along side other NDDs. Thus, the same packet which is sprayed over the NDDs pertaining to local nodes can be sprayed over the TCPSOCK NDD interface for remote nodes. Nodes (local or remote) receive the same packet and reassemble and process it in the same manner.

Claims

1. An information handling system comprising:

one or more processors;

a memory coupled to at least one of the processors;

a network interface that connects the information handling system to a computer network;

a set of instructions stored in the memory and executed by at least one of the processors to manage inter-node communications in a cluster wherein the set of instructions perform actions of;

determining that a first set of a plurality of network device drivers operating at a network device driver level corresponds to a plurality of remote nodes and a second set of the plurality of network device drivers operating at the network device driver level corresponds to a plurality of local nodes;

in response to determining that the first set network device drivers corresponds to the plurality of remote nodes, building the first set of network device drivers with a Transmission Control Protocol (TCP)-based interface;

in response to determining that the second set of network device drivers corresponds to the plurality of local nodes, building the second set of network device drivers with an existing interface that is a non-TCP based interface;

storing the plurality of network device drivers comprising the first set of network device drivers and the second set of network device drivers in a driver layer; and

sending one or more packets to a destination node utilizing a selected one of the plurality of network device drivers in the driver layer corresponding to the destination node.

2. The information handling system of claim 1 wherein packets are sent from a cluster communication layer that does not determine whether the destination node is remote prior to the sending.

3. The information handling system of claim 1 wherein the plurality of NDDs are selected from a group consisting of a Storage Area Network (SAN) driver, a disk driver, an Ethernet driver, and a Transmission Control Protocol (TCP) based pseudo NDD driver.

4. The information handling system of claim 1 wherein the TCP based interface utilizes a socket based kernel interface and provides a pseudo NDD layer support by implementing a TCPSOCK NDD framework interface.

5. The information handling system of claim 4 wherein the TCP based interface provides TCP based handlers selected from a group consisting of initialize, allocate, free, control, send and receive.

6. The information handling system of claim 5 wherein the TCP based interface utilizes a plurality of TCP/IPs socket based kernel interfaces.

7. The information handling system of claim 4 wherein the TCP based interface seamlessly operates with other non-TCP based Network Device Driver (NDD) interfaces.

8. A computer program product stored in a non-transitory computer readable medium, comprising computer instructions that, when executed by an information handling system, causes the information handling system to perform actions comprising:

determining that a first set of a plurality of network device drivers operating at a network device driver level corresponds to a plurality of remote nodes and a second set of the plurality of network device drivers operating at the network device driver level corresponds to a plurality of local nodes;

in response to determining that the first set network device drivers corresponds to the plurality of remote nodes, building the first set of network device drivers with a Transmission Control Protocol (TCP)-based interface;

in response to determining that the second set of network device drivers corresponds to the plurality of local nodes, building the second set of network device drivers with an existing interface that is a non-TCP based interface;

storing the plurality of network device drivers comprising the first set of network device drivers and the second set of network device drivers in a driver layer; and

sending one or more packets to a destination node utilizing a selected one of the plurality of network device drivers in the driver layer corresponding to the destination node.

9. The computer program product of claim 8 wherein packets are sent from a cluster communication layer that does not determine whether the destination node is remote prior to the sending.

10. The computer program product of claim 8 wherein the plurality of NDDs are selected from a group consisting of a Storage Area Network (SAN) driver, a disk driver, an Ethernet driver, and a Transmission Control Protocol (TCP) based pseudo NDD driver.

11. The computer program product of claim 8 wherein the TCP based interface utilizes a socket based kernel interface and provides a pseudo NDD layer support by implementing a TCPSOCK NDD framework interface.

12. The computer program product of claim 11 wherein the TCP based interface provides TCP based handlers selected from a group consisting of initialize, allocate, free, control, send and receive.

13. The computer program product of claim 12 wherein the TCP based interface utilizes a plurality of TCP/IPs socket based kernel interfaces.

14. The computer program product of claim 11 wherein the TCP based interface seamlessly operates with other non-TCP based Network Device Driver (NDD) interfaces.