US6535990B1 - Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system - Google Patents

Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system Download PDF

Info

Publication number
US6535990B1
US6535990B1 US09480148 US48014800A US6535990B1 US 6535990 B1 US6535990 B1 US 6535990B1 US 09480148 US09480148 US 09480148 US 48014800 A US48014800 A US 48014800A US 6535990 B1 US6535990 B1 US 6535990B1
Authority
US
Grant status
Grant
Patent type
Prior art keywords
node
logical
pathway
path
physical
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US09480148
Inventor
Skef F. Iterum
Ying Xie
Madhusudhan K. Talluri
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Oracle America Inc
Original Assignee
Oracle America Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Grant date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12018Mapping of addresses of different types; address resolution
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16Error detection or correction of the data by redundancy in hardware
    • G06F11/20Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2002Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant
    • G06F11/2007Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where interconnections or communication control functionality are redundant using redundant communication media
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12792Details
    • H04L29/12801Details about the structures and formats of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance or administration or management of packet switching networks
    • H04L41/06Arrangements for maintenance or administration or management of packet switching networks involving management of faults or events or alarms
    • H04L41/0654Network fault recovery
    • H04L41/0659Network fault recovery by isolating the faulty entity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/22Alternate routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/28Route fault recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/10Mapping of addresses of different types; Address resolution
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/60Details
    • H04L61/6004Structures or formats of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/40Techniques for recovering from a failure of a protocol instance or entity, e.g. failover routines, service redundancy protocols, protocol state redundancy or protocol service redirection in case of a failure or disaster recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing packet switching networks
    • H04L43/50Testing arrangements

Abstract

One embodiment of the present invention provides a system that facilitates communications between a cluster of nodes within a clustered computing system in a manner that tolerates failures of communication pathways between the nodes. The system operates by configuring a distinct logical pathway between each possible source node and each possible destination node in the cluster, so that each distinct logical pathway is routed across one of at least two disjoint physical pathways between each possible source node and each possible destination node. In doing so, the system configures a first logical pathway between a first node and a second node across a first physical pathway of at least two disjoint physical pathways between the first node and the second node. Upon detecting a failure of the first physical pathway, the system reroutes the first logical pathway across a second physical pathway from the at least two disjoint physical pathways between the first node and the second node. In one embodiment of the present invention, the system associates a distinct per-node logical address with each node in the cluster. For each source node, the system associates the per-node logical address of each possible destination node with a corresponding logical pathway to the destination node. In this way, a communication from a given source node to a per-node logical address of a given destination node is directed across the corresponding logical pathway to the given destination node.

Description

BACKGROUND

1. Field of the Invention

The present invention relates to computer networks and clustered computing systems. More specifically, the present invention relates to a method and an apparatus for providing per-node addresses in a clustered computing system that can tolerate failures of communication pathways between the nodes in the clustered computing system.

2. Related Art

Clustered computing systems allow multiple computing nodes to work together in accomplishing a computational task. In a clustered computing system, a plurality of computing nodes are typically coupled together through one or more computing networks so that each node in the cluster is able to communicate with every other node.

Clustered computing systems are often designed to be fault-tolerant so that a clustered computing system can continue to function if individual components within the clustered computing system fail. One particular problem in providing fault-tolerance is to design a system that can tolerate failures on the communication pathways that link together the nodes of the clustered computing system. Such failures can occur, for example, in cables, in network interface cards (NICs) within the computing nodes, and within intermediate networking equipment, such as a hub or a switch.

In designing a fault-tolerant communication mechanism, it is desirable to use an industry standard communication protocol, such as the Transmission control Protocol Internet Protocol (TCP/IP), so that existing components, which make use of these industry standard protocols, can be used within the clustered computing system. More specifically, it is desirable for each machine in a cluster have its own IP address that can be used to contact the machine from any other machine in the cluster.

It is also desirable for the fault-tolerant communication mechanism to provide at least two disjoint physical communication pathways between each pair of nodes in the clustered computing system. In this way, if a single communication pathway fails, the system is able to provide an alternative communication pathway.

Providing a fault-tolerant TCP/IP network is relatively easy in the case where there are multiple redundant networks, and where all of the nodes in the computing system are attached to each of the redundant networks. In this case, fault-tolerance can be provided by assigning each machine its own IP address on a primary network. If a path fails within the primary network network, the system simply moves all of the IP addresses to an alternative functioning network.

Unfortunately, in many clustered computing systems the computing nodes are not all attached to all of the networks. For example, each machine may have a point-to-point connection to every other machine, or there may exist multiple hubs or switches that only connect to a subset of the nodes in the cluster. If this is the case, it is not possible to create a single IP network that spans all of the nodes in the cluster because of a limitation of TCP/IP. In TCP/IP, a unique IP number can only be hosted on at most one network adapter on a single machine at any given time. This restriction prevents configuring a single IP address on multiple network interfaces in order to span arbitrary network configurations.

Hence, what is needed is a method and an apparatus that provides a fault-tolerant communication mechanism for nodes within a clustered computing system that supports arbitrary fault-tolerant interconnection topologies and allows each node in the cluster to be accessible through its own address.

SUMMARY

One embodiment of the present invention provides a system that facilitates communications between a cluster of nodes within a clustered computing system in a manner that tolerates failures of communication pathways between the nodes. The system operates by configuring a distinct logical pathway between each possible source node and each possible destination node in the cluster, so that each distinct logical pathway is routed across one of at least two disjoint physical pathways between each possible source node and each possible destination node. In doing so, the system configures a first logical pathway between a first node and a second node across a first physical pathway of at least two disjoint physical pathways between the first node and the second node. Upon detecting a failure of the first physical pathway, the system reroutes the first logical pathway across a second physical pathway from the at least two disjoint physical pathways between the first node and the second node.

In one embodiment of the present invention, the system associates a distinct per-node logical address with each node in the cluster. For each source node, the system associates the per-node logical address of each possible destination node with a corresponding logical pathway to the destination node. In this way, a communication from a given source node to a per-node logical address of a given destination node is directed across the corresponding logical pathway to the given destination node. In a variation on this embodiment, the distinct pernode logical address includes a distinct Internet Protocol (IP) address. In a variation on this embodiment, associating the distinct per-node logical address with each node in the cluster involves hosting the distinct per-node logical address on a loop-back interface within each node in the cluster.

In one embodiment of the present invention, the system associates two distinct Internet Protocol (IP) addresses with each distinct logical pathway, one for each of two nodes located on opposite ends of the pathway.

In one embodiment of the present invention, the system associates a distinct Internet Protocol (IP) network with each distinct logical pathway, wherein the two distinct IP addresses associated with each distinct logical pathway are located on the associated distinct IP network.

In one embodiment of the present invention, detecting the failure of the first physical pathway involves using a monitor to periodically test physical pathways in the cluster.

In one embodiment of the present invention, rerouting the first logical pathway involves: bringing down the first logical pathway over the first physical pathway without bringing down connections through the first logical pathway; and bringing up the first logical pathway over the second physical pathway.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a clustered computing system in accordance with an embodiment of the present invention.

FIG. 2 illustrates the process of shifting a logical path to an alternative physical path when a physical path fails in accordance with an embodiment of the present invention.

FIG. 3A illustrates an example interconnection topology for a clustered computing system in accordance with an embodiment of the present invention.

FIG. 3B illustrates a routing table for the example interconnection topology illustrated in FIG. 3A in accordance with an embodiment of the present invention.

FIG. 4 illustrates the example interconnection topology after a failure of a communication link in accordance with an embodiment of the present invention.

FIG. 5 presents a flow chart illustrating the process of configuring and operating a fault-tolerant communication mechanism in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

The data structures and code described in this detailed description are typically stored on a computer readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital video discs), and computer instruction signals embodied in a transmission medium (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, such as the Internet.

Clustered Computing System

FIG. 1 illustrates a clustered computing system 100 in accordance with an embodiment of the present invention. In FIG. 1, clustered computing system 100 is coupled to clients 112-113 through network 110. Clients 112-113 can include any node on network 110 including computational capability and including a mechanism for communicating across network 110. In one embodiment of the present invention, clients 112-113 communicate with clustered computing system 100 by sending packets to clustered computing system 100 in order to request services from clustered computing system 100.

Network 110 can include any type of wire or wireless communication channel capable of coupling together computing nodes. This includes, but is not limited to, a local area network, a wide area network, or a combination of networks. In one embodiment of the present invention, network 110 includes the Internet.

Clustered computing system 100 includes a set of nodes 104-107 that are coupled together through network 102. Network 102 can include any type of wire or wireless communication channel capable of coupling together computing nodes. This includes, but is not limited to, a local area network, a wide area network, or a combination of networks. In one embodiment of the present invention, network 102 supports communications adhering to the Ethernet or the scalable coherent interconnect (SCI) standards, as well as the TCP/IP protocol.

Note that network 102 provides at least two disjoint communication pathways between any two nodes in clustered computing system 100. In this way if a communication pathway fails, another communication pathway is available to take its place. Also note that network 102 can include a number of separate networks that couple together subsets of the nodes within clustered computing system 100. These separate networks can include any type of physical interconnections, including bus connections, switch-based connections and point to-point connections.

In one embodiment of the present invention, path manager 108 operates in a distributed fashion through a local component residing within each node in clustered computing system 100. Path manager 108 knows about the interconnection topology of clustered computing system 100 and monitors the status of communication pathways through clustered computing system 100. Path manager 108 also provides an interface registry through which other components interested in the status of the interconnect can register. This provides a mechanism for path manager 108 to make callbacks to the interested components when the status of a path changes, if a new path comes up, or if a path is removed.

Nodes 104-107 can include any type of computer system, including a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a personal organizer, a device controller, and a computational engine within an appliance.

In one embodiment of the present invention, nodes 104-107 function as server nodes including a mechanism for servicing requests from clients 112-113 for computational or data storage resources within nodes 104-107.

Shifting a Logical Path to an Alternative Physical Path

FIG. 2 illustrates the process of shifting a logical path to an alternative physical path when a physical path fails in accordance with an embodiment of the present invention. The top portion of FIG. 2 illustrates communication pathways between nodes 104 and 105 within clustered computing system 100. Nodes 104 and 105 are coupled together through physical path 204 and physical path 206, which are disjoint from each other so that if one of physical paths 204 or 206 fails, the other one can take its place.

In the top portion of FIG. 2, a logical path 202 is configured so that it is associated with physical path 204. In this way, a communication from node 104 to node 105 passes through logical path 202, which actually transfers the communication across physical path 204. (Note that logical path 202 actually represents two logical pathways, a first logical path from node 104 to node 105 and a second logical path from node 105 to node 104.)

In the middle portion of FIG. 2, a failure of physical path 204 is detected by path manager 108 from FIG. 1. (Note that this detection process involves periodically sending “heartbeats” across all of the physical pathways in network 102.)

When a failure is detected, the system reroutes logical path 202 so that it is associated with physical path 206. This allows communications through logical path 202 to continue through physical path 206 in spite of the failure of physical path 204.

In one embodiment of the present invention, this rerouting is accomplished by bringing down logical path 202 over physical path 204, without bringing down connections through logical path 202, and then bringing up logical path 202 over physical path 206. In this way, connections through logical path 202 are preserved during the rerouting process.

Example Interconnection Topology

FIG. 3A illustrates an example interconnection topology for clustered computing system 100 in accordance with an embodiment of the present invention. As in FIG. 1, clustered computing system 100 includes nodes 104-107, which are coupled together by network 102.

In the example interconnection topology illustrated in FIG. 3A, network 102 includes four switches, including switch A 301, switch B 302, switch C 303 and switch D 304, which couple together nodes 104-107. More specifically, switch A 301 provides a communication pathway between interface P1:A on node 104, interface P2:A on node 105 and interface P3:A on node 106. Switch B 302 provides a communication pathway between interface P1:B on node 104, interface P2:B on node 105 and interface P4:B on node 107. Switch C 303 provides a communication pathway between interface P1:C on node 104, interface P3:C on node 106 and interface P4:C on node 107. Finally, switch D 304 provides a communication pathway between interface P2:D on node 105, interface P3:D on node 106 and interface P4:D on node 107.

Note that there exist at least two disjoint communication pathways between each pair of nodes in clustered computing system 100. For example, Node 104 is coupled to node 105 through a pathway through interface P1:A on node 104, switch A 301 and interface P2:A on node 105. Node 104 is also coupled to node 105 through an alternative pathway through interface P1:B on node 104, switch B 302 and interface P2:B on node 105.

In this embodiment of the present invention, also note that none of switches 301-304 are coupled to all of nodes 104-107 in clustered computing system 100.

Nodes 104-107 host per-node IP addresses on their internal loopback interfaces. Recall that a loopback interface is a pseudo-device implemented on the IP stack of a computer system that acts like a software network adapter. A loopback interface is generally used to form IP connections between applications on the same machine. Also note that a loop back interface is not associated with underlying hardware components that can fail. Referring to FIG. 3A, per-node IP address L1 is hosted on the loop-back interface of node 104. Per-node IP address L2 is hosted on the loop-back interface of node 105. Per-node IP address L3 is hosted on the loop-back interface of node 106. Finally, per-node IP address L4 is hosted on the loop-back interface of node 107.

As in the example illustrated in FIG. 2, logical paths between nodes 104-107 are associated with various physical paths between nodes 104-107. More specifically, logical path L1,2 from node 104 to node 105 is associated with a physical path through switch B 302. In the opposite direction, logical path L2,1 from node 105 to node 104 is also associated with the physical path through switch B 302.

Logical path L1,3 from node 104 to node 106 is associated with a physical path through switch C 303. In the opposite direction, logical path L3,1 from node 106 to node 104 is also associated with the physical path through switch C 303.

Logical path L1,4 from node 104 to node 107 is associated with a physical path through switch B 302. In the opposite direction, logical path L4,1 from node 107 to node 104 is also associated with the physical path through switch B 302.

Note that FIG. 3A illustrates only logical paths involving node 104. Other logical paths between nodes 105-107 are not shown.

Routing Table

FIG. 3B illustrates the contents of a routing table for the example interconnection topology illustrated in FIG. 3A in accordance with an embodiment of the present invention. This table illustrates how destination per-node IP addresses are associated with logical paths involving node 104. Within node 104, destination per-node IP address L2 is associated with logical path L1,2, destination per-node IP address L3 is associated with logical path L1,3, and destination per-node IP address L4 is associated with logical path L1,4.

In the reverse direction, within node 105, destination per-node IP address L1 is associated with logical path L2,1. Within node 106, destination per-node IP address L1 is associated with logical path L3,1. Within node 107, destination per-node IP address L1 is associated with logical path L4,1.

Note that this table maps destination per-node IP addresses to logical paths, and hence, will not change if a logical path is moved to an alternative physical path.

Also note that other logical paths between nodes 105-107 are not shown.

Example Interconnection Topology After Communication Link Failure

FIG. 4 illustrates the example interconnection topology after a failure of a communication link in accordance with an embodiment of the present invention. The example illustrated in FIG. 4 is the same as the example illustrated in FIG. 3A, except that there is a failure in the communication link between interface P2:B on node 105 and switch B 302. This failure affects the logical path L1,2 between nodes 104 and 105 as well as logical path L2,1 between nodes 105 and 104. This failure does not affect any of the other illustrated logical paths. (Although logical path L1,4 and logical path L4,1 also pass through switch B 302, they are not affected by the failure of the communication link between switch B 302 and interface P2:B on node 105.)

Once the failure is detected, logical paths L1,2 and L2,1 are routed around the failed communication link. This is done by reconfiguring logical paths L1,2 and L2,1 to be associated with an alternative physical path, which passes through interface P1:A in node 104, switch A 301 and interface P2:A in node 105.

Configuring and Operating Fault-Tolerant Communication Mechanism

FIG. 5 presents a flow chart illustrating the process of configuring and operating a fault-tolerant communication mechanism in accordance with an embodiment of the present invention.

The system starts by configuring a distinct logical path between each possible source node and each destination node across one of at least two disjoint physical pathways connecting each source node and each destination node (step 502). Note that this process involves configuring a first logical path across a first physical path between a first node and a second node in the cluster. In one embodiment, the system associates two distinct Internet Protocol (IP) addresses with each distinct logical pathway, one for each of two nodes located on opposite ends of the pathway.

In one embodiment, this configuration process also involves associating a distinct IP network with each distinct logical path (step 504). (We refer to each of these distinct IP networks as a “pair-wise” network, because the IP network couples together a “pair” of nodes.) Note that the two distinct IP addresses associated with each distinct logical pathway are located on the associated distinct IP network.

In one embodiment of the present invention, during the configuration process, the system also hosts a distinct per-node IP addresses on a loop-back interface within each node in the cluster (step 506). For example, in node 104 in FIG. 3A, per-node IP address L1 is hosted in the loopback interface of node 104.

Next, for each node in the cluster, the system associates the per-node IP address of each destination node with a corresponding logical path to the destination node (step 508). For example, in node 104 in FIG. 3A, per-node IP address L2 for destination node 105 is associated with logical path L1,2.

After the configuration process is complete, the system progresses to normal system operation. During normal system operation, path manager 108 (from FIG. 1) periodically monitors the status of physical paths within network 102 (step 510).

At some time during this monitoring process, the system detects a failure of the first physical path (step 512). In this case, the system reroutes the first logical path onto an alternative second physical path. This is accomplished by bringing down the first logical path over the first physical path without bringing down connections from the first logical path (step 514). Next, the system brings up the first logical path over the alternative second physical path (step 516). In this way, connections through the first logical path are maintained during the rerouting process. Note that the routing tables, which map per-node addresses onto logical paths do not change during this rerouting process because the logical paths do not change; only the associations between logical paths and physical paths change.

Note there exists an agreement system, which enables nodes at opposite ends of a pathway to agree on what path should be used. In one embodiment of the present invention, the nodes negotiate outside of the above-described protocol to determine what alternative path to use whenever a path fails. In another embodiment of the present invention, there exists a strict ordering of preference for all the paths between two nodes, and the most preferred path is always used. Using this system means that if the most preferred path has previously failed and then starts to function again, the logical pairwise network moves back onto the newly restored more preferred path to ensure agreement. This means that logical paths might be moved in the case of path restoration, not just path failure.

The foregoing descriptions of embodiments of the invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the invention. The scope of the invention is defined by the appended claims.

Claims (18)

What is claimed is:
1. A method for providing communications between a cluster of nodes in a clustered computing system in a manner that tolerates failures of communication pathways between the cluster of nodes, comprising:
configuring a distinct logical pathway between each possible source node and each possible destination node in the cluster of nodes, so that each distinct logical pathway is routed across one of at least two disjoint physical pathways between each possible source node and each possible destination node;
wherein the distinct logical pathway between each possible source node includes a first logical pathway between a first node and a second node in the cluster of nodes, so that the first logical pathway is routed across a first physical pathway of at least two disjoint physical pathways between the first node and the second node;
associating a distinct per-node logical address with each node in the cluster;
for each source node in the cluster, associating the per-node logical address for each destination node in the cluster with a corresponding logical pathway to the destination node, so that a communication from a given source node to a given per-node logical address of a given destination node is directed across the corresponding logical pathway to the given destination node;
detecting a failure of the first physical pathway; and
rerouting the first logical pathway across a second one of the at least two disjoint physical pathways between the first node and the second node.
2. The method of claim 1, wherein associating the distinct per-node logical address with each node in the cluster involves hosting the distinct per-node logical address on a loop-back interface within each node in the cluster.
3. The method of claim 1, further comprising associating two distinct Internet Protocol (IP) addresses with each distinct logical pathway, one for each of two nodes located on opposite ends of the pathway.
4. The method of claim 3, further comprising associating a distinct Internet Protocol (IP) network with each distinct logical pathway, wherein the two associated distinct IP addresses associated with each distinct logical pathway are located on the associated distinct IP network.
5. The method of claim 1, wherein detecting the failure of the first physical pathway involves using a monitor to periodically test physical pathways.
6. The method of claim 1, wherein rerouting the first logical pathway involves:
bringing down the first logical pathway over the first physical pathway without bringing down connections through the first logical pathway; and
bringing up the first logical pathway over the second physical pathway.
7. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for providing communications between a cluster of nodes in a clustered computing system in a manner that tolerates failures of communication pathways between the cluster of nodes, the method comprising:
configuring a distinct logical pathway between each possible source node and each possible destination node in the cluster of nodes, so that each distinct logical pathway is routed across one of at least two disjoint physical pathways between each possible source node and each possible destination node.
wherein the distinct logical pathway between each possible source node includes a first logical pathway between a first node and a second node in the cluster of nodes, so that the first logical pathway is routed across a first physical pathway of at least two disjoint physical pathways between the first node and the second node;
associating a distinct per-node logical address with each node in the cluster;
for each source node in the cluster, associating the per-node logical address for each destination node in the cluster with a corresponding logical pathway to the destination node, so that a communication from a given source node to a given per-node logical address of a given destination node is directed across the corresponding logical pathway to the given destination node;
detecting a failure of the first physical pathway; and
rerouting the first logical pathway across a second one of the at least two disjoint physical pathways between the first node and the second node.
8. The computer-readable storage medium of claim 7, wherein associating the distinct per-node logical address with each node in the cluster involves hosting the distinct per-node logical address on a loop-back interface within each node in the cluster.
9. The computer-readable storage medium of claim 7, wherein the method further comprises associating two distinct Internet Protocol (IP) addresses with each distinct logical pathway, one for each of two nodes located on opposite ends of the pathway.
10. The computer-readable storage medium of claim 9, wherein the method further comprises associating a distinct Internet Protocol (IP) network with each distinct logical pathway, and wherein the two associated distinct IP addresses associated with each distinct logical pathway are located on the associated distinct IP network.
11. The computer-readable storage medium of claim 7, wherein detecting the failure of the first physical pathway involves using a monitor to periodically test physical pathways.
12. The computer-readable storage medium of claim 7, wherein rerouting the first logical pathway involves:
bringing down the first logical pathway over the first physical pathway without bringing down connections through the first logical pathway; and
bringing up the first logical pathway over the second physical pathway.
13. An apparatus that provides communications between a cluster of nodes in a clustered computing system in a manner that tolerates failures of communication pathways between the cluster of nodes, comprising:
a configuration mechanism that configures a distinct logical pathway between each possible source node and each possible destination node in the cluster of nodes, so that each distinct logical pathway is routed across one of at least two disjoint physical pathways between each possible source node and each possible destination node
wherein the configuration mechanism further configures a first logical pathway between a first node and a second node in the cluster of nodes, so that the first logical pathway is routed across a first physical pathway of at least two disjoint physical pathways between the first node and the second node;
an association mechanism that is configured to:
associate a distinct per-node logical address with each node in the cluster, and
for each source node in the cluster, to associate the per-node logical address for each destination node in the cluster with a corresponding logical pathway to the destination node, so that a communication from a given source node to a given per-node logical address of a given destination node is directed across the corresponding logical pathway to the given destination node;
a detection mechanism that detects a failure of the first physical pathway; and
a rerouting mechanism that reroutes the first logical pathway across a second one of the at least two disjoint physical pathways between the first node and the second node when the detection mechanism.
14. The apparatus of claim 13, wherein the association mechanism is configured to associate the distinct per-node logical address with each node in the cluster by hosting the distinct per-node logical address on a loop-back interface within each node in the cluster.
15. The apparatus of claim 13, wherein the association mechanism is configured to associate two distinct Internet Protocol (IP) addresses with each distinct logical pathway, one for each of two nodes located on opposite ends of the pathway.
16. The apparatus of claim 15, wherein the association mechanism is configured to associate a distinct Internet Protocol (IP) network with each distinct logical pathway, and wherein the two associated distinct IP addresses associated with each distinct logical pathway are located on the associated distinct IP network.
17. The apparatus of claim 13, wherein the detection mechanism is configured to detect the failure of the first physical pathway by using a monitor to periodically test physical pathways.
18. The apparatus of claim 13, wherein the rerouting mechanism is configured to:
bring down the first logical pathway over the first physical pathway without bringing down connections through the first logical pathway; and to
bring up the first logical pathway over the second physical pathway.
US09480148 2000-01-10 2000-01-10 Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system Active US6535990B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09480148 US6535990B1 (en) 2000-01-10 2000-01-10 Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09480148 US6535990B1 (en) 2000-01-10 2000-01-10 Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system
EP20000204325 EP1117038A3 (en) 2000-01-10 2000-12-04 Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system

Publications (1)

Publication Number Publication Date
US6535990B1 true US6535990B1 (en) 2003-03-18

Family

ID=23906832

Family Applications (1)

Application Number Title Priority Date Filing Date
US09480148 Active US6535990B1 (en) 2000-01-10 2000-01-10 Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system

Country Status (2)

Country Link
US (1) US6535990B1 (en)
EP (1) EP1117038A3 (en)

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020174168A1 (en) * 2001-04-30 2002-11-21 Beukema Bruce Leroy Primitive communication mechanism for adjacent nodes in a clustered computer system
US20030018922A1 (en) * 2001-07-18 2003-01-23 Litwin Louis Robert Method and system for providing emergency shutdown of a malfunctioning device
US20030110409A1 (en) * 2001-12-07 2003-06-12 Alan Gale Method and apparatus for network fault correction via adaptive fault router
US6728207B1 (en) * 1997-07-11 2004-04-27 Telefonaktiebolaget Lm Ericsson Self-healing ring network and a method for fault detection and rectifying
US6766482B1 (en) 2001-10-31 2004-07-20 Extreme Networks Ethernet automatic protection switching
US20040143653A1 (en) * 2003-01-21 2004-07-22 Bellsouth Intellectual Property Corporation Method and system for provisioning and maintaining a circuit in a data network
US6901443B1 (en) * 2000-03-10 2005-05-31 Honeywell International Inc. Non-fault tolerant network nodes in a multiple fault tolerant network
US20050135254A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for automatically rerouting data from an overbalanced logical circuit in a data network
US20050135238A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for providing a failover circuit for rerouting logical circuit data in a data network
US20050138476A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for prioritized rerouting of logical circuit data in a data network
US20050135263A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for real time simultaneous monitoring of logical circuits in a data network
US20050135237A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for automatically rerouting logical circuit data in a data network
US20050172174A1 (en) * 2003-12-23 2005-08-04 Bellsouth Intellectual Property Corporation Method and system for automatically identifying a logical circuit failure in a data network
US20050172160A1 (en) * 2003-12-23 2005-08-04 Bellsouth Intellectual Property Corporation Method and system for automatically rerouting logical circuit data in a virtual private network
US20050238024A1 (en) * 2004-04-22 2005-10-27 Bellsouth Intellectual Property Corporation Method and system for provisioning logical circuits for intermittent use in a data network
US20050238006A1 (en) * 2004-04-22 2005-10-27 Bellsouth Intellectual Property Corporation Method and system for fail-safe renaming of logical circuit identifiers for rerouted logical circuits in a data network
US20060291459A1 (en) * 2004-03-10 2006-12-28 Bain William L Scalable, highly available cluster membership architecture
US20070047453A1 (en) * 2005-08-24 2007-03-01 International Business Machines Corporation Reliable message transfer over an unreliable network
US20070268832A1 (en) * 2006-05-16 2007-11-22 Shih-Chung Tom Soon System and method to achieve sub-second routing performance
US20080126829A1 (en) * 2006-08-26 2008-05-29 International Business Machines Corporation Simulation of failure recovery within clustered systems
US20080235333A1 (en) * 2001-04-30 2008-09-25 International Business Machines Corporation Group access privatization in clustered computer system
US20090041012A1 (en) * 2004-04-22 2009-02-12 William Taylor Method and system for automatically tracking the rerouting of logical circuit data in a data network
US20090055521A1 (en) * 2007-08-24 2009-02-26 Konica Minolta Holdings, Inc. Method for managing network connection and information processing apparatus
US20090086626A1 (en) * 2004-04-22 2009-04-02 William Taylor Methods and systems for automatically rerouting logical circuit data from a logical circuit failure to a dedicated backup circuit in a data network
US7646707B2 (en) 2003-12-23 2010-01-12 At&T Intellectual Property I, L.P. Method and system for automatically renaming logical circuit identifiers for rerouted logical circuits in a data network

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004066568A1 (en) * 2003-01-24 2004-08-05 Siemens Aktiengesellschaft Method for divering data packets in locally recognized link failures by multipath finding
US20050086385A1 (en) * 2003-10-20 2005-04-21 Gordon Rouleau Passive connection backup
US7325154B2 (en) * 2004-05-04 2008-01-29 Sun Microsystems, Inc. Service redundancy

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5173689A (en) * 1990-06-25 1992-12-22 Nec Corporation Self-distributed logical channel node failure restoring system
US5229990A (en) * 1990-10-03 1993-07-20 At&T Bell Laboratories N+K sparing in a telecommunications switching environment
US5577030A (en) 1995-08-31 1996-11-19 Nippon Telegraph And Telephone Corporation Data communication routing method and device
EP0841824A2 (en) 1996-11-08 1998-05-13 Nec Corporation Failure restoration system suitable for a large-scale network
US5774640A (en) 1991-10-21 1998-06-30 Tandem Computers Incorporated Method and apparatus for providing a fault tolerant network interface controller
US5793746A (en) * 1996-04-29 1998-08-11 International Business Machines Corporation Fault-tolerant multichannel multiplexer ring configuration
US5856981A (en) * 1997-05-15 1999-01-05 Lucent Technologies Inc. Reliable connection oriented networks
US5883939A (en) * 1996-08-29 1999-03-16 Cornell Research Foundation, Inc. Distributed architecture for an intelligent networking coprocessor
US5898827A (en) * 1996-09-27 1999-04-27 Hewlett-Packard Co. Routing methods for a multinode SCI computer system
WO1999059064A1 (en) 1998-05-12 1999-11-18 Sun Microsystems, Inc. Highly available cluster virtual disk system
US6112249A (en) * 1997-05-30 2000-08-29 International Business Machines Corporation Non-disruptively rerouting network communications from a secondary network path to a primary path
US6111881A (en) * 1997-12-29 2000-08-29 Nortel Networks Corporation Signaling protocol for rerouting ATM connections in PNNI environments
US6115753A (en) * 1997-02-18 2000-09-05 Alcatel Method for rerouting in hierarchically structured networks
US6393485B1 (en) * 1998-10-27 2002-05-21 International Business Machines Corporation Method and apparatus for managing clustered computer systems

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5173689A (en) * 1990-06-25 1992-12-22 Nec Corporation Self-distributed logical channel node failure restoring system
US5229990A (en) * 1990-10-03 1993-07-20 At&T Bell Laboratories N+K sparing in a telecommunications switching environment
US5774640A (en) 1991-10-21 1998-06-30 Tandem Computers Incorporated Method and apparatus for providing a fault tolerant network interface controller
US5577030A (en) 1995-08-31 1996-11-19 Nippon Telegraph And Telephone Corporation Data communication routing method and device
US5793746A (en) * 1996-04-29 1998-08-11 International Business Machines Corporation Fault-tolerant multichannel multiplexer ring configuration
US5883939A (en) * 1996-08-29 1999-03-16 Cornell Research Foundation, Inc. Distributed architecture for an intelligent networking coprocessor
US5898827A (en) * 1996-09-27 1999-04-27 Hewlett-Packard Co. Routing methods for a multinode SCI computer system
EP0841824A2 (en) 1996-11-08 1998-05-13 Nec Corporation Failure restoration system suitable for a large-scale network
US6115753A (en) * 1997-02-18 2000-09-05 Alcatel Method for rerouting in hierarchically structured networks
US5856981A (en) * 1997-05-15 1999-01-05 Lucent Technologies Inc. Reliable connection oriented networks
US6112249A (en) * 1997-05-30 2000-08-29 International Business Machines Corporation Non-disruptively rerouting network communications from a secondary network path to a primary path
US6111881A (en) * 1997-12-29 2000-08-29 Nortel Networks Corporation Signaling protocol for rerouting ATM connections in PNNI environments
US6272139B1 (en) * 1997-12-29 2001-08-07 Nortel Networks Limited Signaling protocol for rerouting ATM connections in PNNI environments
WO1999059064A1 (en) 1998-05-12 1999-11-18 Sun Microsystems, Inc. Highly available cluster virtual disk system
US6393485B1 (en) * 1998-10-27 2002-05-21 International Business Machines Corporation Method and apparatus for managing clustered computer systems

Cited By (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6728207B1 (en) * 1997-07-11 2004-04-27 Telefonaktiebolaget Lm Ericsson Self-healing ring network and a method for fault detection and rectifying
US6901443B1 (en) * 2000-03-10 2005-05-31 Honeywell International Inc. Non-fault tolerant network nodes in a multiple fault tolerant network
US20080235333A1 (en) * 2001-04-30 2008-09-25 International Business Machines Corporation Group access privatization in clustered computer system
US7433957B2 (en) * 2001-04-30 2008-10-07 International Business Machines Corporation Group access privatization in clustered computer system
US8078754B2 (en) 2001-04-30 2011-12-13 International Business Machines Corporation Group access privatization in clustered computer system
US20020174168A1 (en) * 2001-04-30 2002-11-21 Beukema Bruce Leroy Primitive communication mechanism for adjacent nodes in a clustered computer system
US7197536B2 (en) * 2001-04-30 2007-03-27 International Business Machines Corporation Primitive communication mechanism for adjacent nodes in a clustered computer system
US20030018922A1 (en) * 2001-07-18 2003-01-23 Litwin Louis Robert Method and system for providing emergency shutdown of a malfunctioning device
US7073083B2 (en) * 2001-07-18 2006-07-04 Thomas Licensing Method and system for providing emergency shutdown of a malfunctioning device
US6766482B1 (en) 2001-10-31 2004-07-20 Extreme Networks Ethernet automatic protection switching
US20030110409A1 (en) * 2001-12-07 2003-06-12 Alan Gale Method and apparatus for network fault correction via adaptive fault router
US20050066220A1 (en) * 2001-12-07 2005-03-24 Invensys Systems, Inc. Method and apparatus for network fault correction via adaptive fault router
US20050050379A1 (en) * 2001-12-07 2005-03-03 Invensys Systems, Inc. Method and apparatus for network fault correction via adaptive fault router
US7434088B2 (en) * 2001-12-07 2008-10-07 Invensys Systems, Inc. Method and apparatus for network fault correction via adaptive fault router
US6868509B2 (en) * 2001-12-07 2005-03-15 Invensys Systems, Inc. Method and apparatus for network fault correction via adaptive fault router
US7380154B2 (en) * 2001-12-07 2008-05-27 Invensys Systems, Inc. Method and apparatus for network fault correction via adaptive fault router
US7469282B2 (en) * 2003-01-21 2008-12-23 At&T Intellectual Property I, L.P. Method and system for provisioning and maintaining a circuit in a data network
US20090103544A1 (en) * 2003-01-21 2009-04-23 At&T Intellectual Property I, L.P. Method and system for provisioning and maintaining a circuit in a data network
US7890618B2 (en) 2003-01-21 2011-02-15 At&T Intellectual Property I, L.P. Method and system for provisioning and maintaining a circuit in a data network
US20110083045A1 (en) * 2003-01-21 2011-04-07 William Scott Taylor Methods and systems for provisioning and maintaining a circuit in a data network
US20040143653A1 (en) * 2003-01-21 2004-07-22 Bellsouth Intellectual Property Corporation Method and system for provisioning and maintaining a circuit in a data network
US8200802B2 (en) 2003-01-21 2012-06-12 At&T Intellectual Property I, L.P. Methods and systems for provisioning and maintaining a circuit in a data network
US8031620B2 (en) 2003-12-23 2011-10-04 At&T Intellectual Property I, L.P. Method and system for real time simultaneous monitoring of logical circuits in a data network
US8730795B2 (en) 2003-12-23 2014-05-20 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data
US8711679B2 (en) 2003-12-23 2014-04-29 At&T Intellectual Property I, L.P. Methods and systems for automatically identifying a logical circuit failure in a data network
US8750102B2 (en) 2003-12-23 2014-06-10 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data in a data network
US8547830B2 (en) 2003-12-23 2013-10-01 At&T Intellectual Property I, L.P. Methods and systems to reroute data in a data network
US8937856B2 (en) 2003-12-23 2015-01-20 At&T Intellectual Property I, L.P. Methods and systems to reroute data in a data network
US8942086B2 (en) 2003-12-23 2015-01-27 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data in a data network
US9059900B2 (en) 2003-12-23 2015-06-16 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data
US20050172160A1 (en) * 2003-12-23 2005-08-04 Bellsouth Intellectual Property Corporation Method and system for automatically rerouting logical circuit data in a virtual private network
US8547831B2 (en) 2003-12-23 2013-10-01 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data
US8243592B2 (en) 2003-12-23 2012-08-14 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting data in a data network
US8223632B2 (en) 2003-12-23 2012-07-17 At&T Intellectual Property I, L.P. Method and system for prioritized rerouting of logical circuit data in a data network
US20050172174A1 (en) * 2003-12-23 2005-08-04 Bellsouth Intellectual Property Corporation Method and system for automatically identifying a logical circuit failure in a data network
US7609623B2 (en) 2003-12-23 2009-10-27 At&T Intellectual Property I, L.P. Method and system for automatically rerouting data from an overbalanced logical circuit in a data network
US7630302B2 (en) 2003-12-23 2009-12-08 At&T Intellectual Property I, L.P. Method and system for providing a failover circuit for rerouting logical circuit data in a data network
US7639606B2 (en) 2003-12-23 2009-12-29 At&T Intellectual Property I, L.P. Method and system for automatically rerouting logical circuit data in a virtual private network
US7639623B2 (en) 2003-12-23 2009-12-29 At&T Intellectual Property I, L.P. Method and system for real time simultaneous monitoring of logical circuits in a data network
US20090323534A1 (en) * 2003-12-23 2009-12-31 William Taylor Methods and systems for automatically rerouting data in a data network
US7646707B2 (en) 2003-12-23 2010-01-12 At&T Intellectual Property I, L.P. Method and system for automatically renaming logical circuit identifiers for rerouted logical circuits in a data network
US20100020677A1 (en) * 2003-12-23 2010-01-28 William Taylor Methods and systems for automatically renaming logical circuit identifiers for rerouted logical circuits in a data network
US20100046380A1 (en) * 2003-12-23 2010-02-25 William Taylor Method and system for real time simultaneous monitoring of logical circuits in a data network
US8203933B2 (en) 2003-12-23 2012-06-19 At&T Intellectual Property I, L.P. Method and system for automatically identifying a logical circuit failure in a data network
US20050135237A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for automatically rerouting logical circuit data in a data network
US8199638B2 (en) 2003-12-23 2012-06-12 At&T Intellectual Property I, L.P. Method and system for automatically rerouting logical circuit data in a data network
US20050135263A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for real time simultaneous monitoring of logical circuits in a data network
US20050138476A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for prioritized rerouting of logical circuit data in a data network
US20050135238A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for providing a failover circuit for rerouting logical circuit data in a data network
US8031588B2 (en) 2003-12-23 2011-10-04 At&T Intellectual Property I, L.P. Methods and systems for automatically renaming logical Circuit identifiers for rerouted logical circuits in a data network
US20050135254A1 (en) * 2003-12-23 2005-06-23 Bellsouth Intellectual Property Corporation Method and system for automatically rerouting data from an overbalanced logical circuit in a data network
US8345543B2 (en) 2003-12-23 2013-01-01 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data
US20060291459A1 (en) * 2004-03-10 2006-12-28 Bain William L Scalable, highly available cluster membership architecture
JP2007538306A (en) * 2004-03-10 2007-12-27 スケールアウト ソフトウェア インコーポレイテッド Scalable and highly available cluster membership architecture
US7738364B2 (en) * 2004-03-10 2010-06-15 William L Bain Scalable, highly available cluster membership architecture
US8345537B2 (en) 2004-04-22 2013-01-01 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data from a logical circuit failure to a dedicated backup circuit in a data network
US20050238024A1 (en) * 2004-04-22 2005-10-27 Bellsouth Intellectual Property Corporation Method and system for provisioning logical circuits for intermittent use in a data network
US8953495B2 (en) 2004-04-22 2015-02-10 At&T Intellectual Property I, L.P. Methods and systems for provisioning logical circuits for intermittent use in a data network
US8339988B2 (en) 2004-04-22 2012-12-25 At&T Intellectual Property I, L.P. Method and system for provisioning logical circuits for intermittent use in a data network
US8339938B2 (en) 2004-04-22 2012-12-25 At&T Intellectual Property I, L.P. Method and system for automatically tracking the rerouting of logical circuit data in a data network
US9338051B2 (en) 2004-04-22 2016-05-10 At&T Intellectual Property I, L.P. Methods and systems for automatically tracking the rerouting of logical circuit data in a data network
US20090086626A1 (en) * 2004-04-22 2009-04-02 William Taylor Methods and systems for automatically rerouting logical circuit data from a logical circuit failure to a dedicated backup circuit in a data network
US8509118B2 (en) 2004-04-22 2013-08-13 At&T Intellectual Property I, L.P. Methods and systems for provisioning logical circuits for intermittent use in a data network
US8509058B2 (en) 2004-04-22 2013-08-13 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data from a logical circuit failure to a dedicated backup circuit in a data network
US20090041012A1 (en) * 2004-04-22 2009-02-12 William Taylor Method and system for automatically tracking the rerouting of logical circuit data in a data network
US8953435B2 (en) 2004-04-22 2015-02-10 At&T Intellectual Property I, L.P. Methods and systems for automatically tracking the rerouting of logical circuit data in a data network
US9148365B2 (en) 2004-04-22 2015-09-29 At&T Intellectual Property I, L.P. Methods and systems for automatically tracking the rerouting of logical circuit data in a data network
US8665705B2 (en) 2004-04-22 2014-03-04 At&T Intellectual Property I, L.P. Methods and systems for automatically rerouting logical circuit data from a logical circuit failure to a dedicated backup circuit in a data network
US8670348B2 (en) 2004-04-22 2014-03-11 At&T Intellectual Property I, L.P. Methods and systems for provisioning logical circuits for intermittent use in a data network
US7768904B2 (en) 2004-04-22 2010-08-03 At&T Intellectual Property I, L.P. Method and system for fail-safe renaming of logical circuit identifiers for rerouted logical circuits in a data network
US20050238006A1 (en) * 2004-04-22 2005-10-27 Bellsouth Intellectual Property Corporation Method and system for fail-safe renaming of logical circuit identifiers for rerouted logical circuits in a data network
US8737196B2 (en) 2004-04-22 2014-05-27 At&T Intellectual Property I, L.P. Methods and systems for automatically tracking the rerouting of logical circuit data in a data network
US8565074B2 (en) 2004-04-22 2013-10-22 At&T Intellectual Property I, L.P. Methods and systems for automatically tracking the rerouting of logical circuit data in a data network
US20070047453A1 (en) * 2005-08-24 2007-03-01 International Business Machines Corporation Reliable message transfer over an unreliable network
US8018844B2 (en) * 2005-08-24 2011-09-13 International Business Machines Corporation Reliable message transfer over an unreliable network
US8873379B2 (en) 2006-05-16 2014-10-28 At&T Intellectual Property I, L.P. System and method to achieve sub-second routing performance
US20070268832A1 (en) * 2006-05-16 2007-11-22 Shih-Chung Tom Soon System and method to achieve sub-second routing performance
US8295162B2 (en) 2006-05-16 2012-10-23 At&T Intellectual Property I, L.P. System and method to achieve sub-second routing performance
US20080126829A1 (en) * 2006-08-26 2008-05-29 International Business Machines Corporation Simulation of failure recovery within clustered systems
US7770063B2 (en) 2006-08-26 2010-08-03 International Business Machines Corporation Simulation of failure recovery within clustered systems
US20090055521A1 (en) * 2007-08-24 2009-02-26 Konica Minolta Holdings, Inc. Method for managing network connection and information processing apparatus

Also Published As

Publication number Publication date Type
EP1117038A2 (en) 2001-07-18 application
EP1117038A3 (en) 2001-08-22 application

Similar Documents

Publication Publication Date Title
Pfister An introduction to the infiniband architecture
US6606690B2 (en) System and method for accessing a storage area network as network attached storage
US6859835B1 (en) Virtual port multiplexing
US5835696A (en) Data router backup feature
US7783788B1 (en) Virtual input/output server
US6173411B1 (en) Method and system for fault-tolerant network connection switchover
US6895528B2 (en) Method and apparatus for imparting fault tolerance in a switch or the like
US7284067B2 (en) Method for integrated load balancing among peer servers
US6880089B1 (en) Firewall clustering for multiple network servers
US7260628B2 (en) Event notification in storage networks
US6988161B2 (en) Multiple port allocation and configurations for different port operation modes on a host
US6392990B1 (en) Method for implementing interface redundancy in a computer network
US7370336B2 (en) Distributed computing infrastructure including small peer-to-peer applications
US20030208572A1 (en) Mechanism for reporting topology changes to clients in a cluster
US20050021751A1 (en) Cluster data port services for clustered computer system
US6470013B1 (en) Use of enhanced ethernet link—loop packets to automate configuration of intelligent linecards attached to a router
US7450498B2 (en) Fault tolerant network architecture
US6681248B1 (en) Method for port connectivity discovery in transparent high bandwidth networks
US20050281190A1 (en) Automated recovery from a split segment condition in a layer2 network for teamed network resources of a computer systerm
US6871347B2 (en) Method and apparatus for facilitating load balancing across name servers
US20130117766A1 (en) Fabric-Backplane Enterprise Servers with Pluggable I/O Sub-System
US20110004877A1 (en) Maintaining Virtual Machines in a Network Device
US7257817B2 (en) Virtual network with adaptive dispatcher
US20050125557A1 (en) Transaction transfer during a failover of a cluster controller
US20070076590A1 (en) Selecting one of multiple redundant network access points on a node within an industrial process control network

Legal Events

Date Code Title Description
AS Assignment

Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ITERUM, SKEF F.;XIE, YING;TALLURI, MADHUSUDHAN K.;REEL/FRAME:010500/0766;SIGNING DATES FROM 20000103 TO 20000104

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: ORACLE AMERICA, INC., CALIFORNIA

Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:ORACLE USA, INC.;SUN MICROSYSTEMS, INC.;ORACLE AMERICA, INC.;REEL/FRAME:037278/0692

Effective date: 20100212