CA2402872A1 - Non-fault tolerant network nodes in a multiple fault tolerant network - Google Patents
Non-fault tolerant network nodes in a multiple fault tolerant network Download PDFInfo
- Publication number
- CA2402872A1 CA2402872A1 CA002402872A CA2402872A CA2402872A1 CA 2402872 A1 CA2402872 A1 CA 2402872A1 CA 002402872 A CA002402872 A CA 002402872A CA 2402872 A CA2402872 A CA 2402872A CA 2402872 A1 CA2402872 A1 CA 2402872A1
- Authority
- CA
- Canada
- Prior art keywords
- network
- fault
- tolerant
- data
- node
- 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.)
- Abandoned
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40169—Flexible bus arrangements
- H04L12/40176—Flexible bus arrangements involving redundancy
- H04L12/40189—Flexible bus arrangements involving redundancy by using a plurality of bus systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
Abstract
The present invention provides a method and apparatus for facilitating communication with non-fault tolerant network nodes in a fault-tolerant network environment. In various embodiments, a network address or network location of any network nodes present on a network that are not fault-tolerant is determined and stored, and data intended for the detected non-fault-tolerant network nodes is routed only over that network to which the non-fault-tolerant network node is connected. In further embodiments, the fault-tolerant network comprises a primary and redundant network with fault tolerant network nodes that are attached to each network; a non-fault-tolerant network node that is attached to either the primary or redundant network is then operable to communicate with any fault-tolerant network node via data sent over only the network to which the non-fault-tolerant network node is connected.
Description
Non-Fault Tolerant Network Nodes in a Multiple Fault Tolerant Network Field of the Invention The invention relates generally to computer networks, and more specifically to a method and apparatus providing non-fault tolerant network node operability in a fault-tolerant network.
Notice of Copending Applications This application is related to the following copending applications, which are hereby incorporated by reference:
"Fault Tolerant Networking", serial number 09/188,976; and Atty. doclcet number 256.044us1 Background of the Invention Computer networks have become increasingly important to communication and productivity in environments where computers are utilized for worlc.
Electronic mail has in many situations replaced paper mail and faxes as a means of distribution of information, and the availability of vast amounts of information on the Internet has become an invaluable resource both fox many work-related and personal tasks. The ability to exchange data over computer networlcs also enables sharing of computer resources such as printers in a work environment, and enables centralized networlc-based management of the networked computers.
For example, an off ce worker's personal computer may run software that is installed and updated automatically via a network, and that generates data that is printed to a networked printer shared by people in several different offices.
The network may be used to inventory the software and hardware installed in each personal computer, greatly simplifying the task of inventory management. Also, the software and hardware conf guration of each computer may be managed via the network, making the task of user support easier in a networked environment.
Networked computers also typically are connected to one or more network servers that provide data and resources to the networked computers. For example, a server may store a number of software applications that can be executed by the networked computers, or may store a database of data that can be accessed and utilized by the networked computers. The network servers typically also manage access to certain networked devices such as printers, which can be utilized by any of the networked computers. Also, a server may facilitate exchange of data such as e-mail or other similar services between the networked computers.
Connection from the local networlc to a larger network such as the Internet can provide greater ability to exchange data, such as by providing Internet e-mail access or access to the World Wide Web. These data connections make conducting business via the Internet practical, and have contributed to the growth in development and use of computer networks. Internet servers that provide data and serve functions sucn as e-commerce, streaming audio or video, e-mail, or provide other content rely on the operation of local networks as well as the Internet to provide a path between such data servers and client computer systems.
But Iike other electronic systems, networks are subject to failures.
Misconfiguration, broken wires, failed electronic components, and a number of other factors can cause a computer network connection to fail, leading to possible inoperability of the computer network. Such failures can be minimized in critical networking environments such as process control, medical, or other critical applications by utilization of backup or redundant network components. One example is use of a second network connection to critical network nodes providing the same function as the first network connection. But, management of the networlc connections to facilitate operation in the event of a network failure can be a difficult task, and is itself subject to the ability of a network system or user to properly detect and compensate for the network fault. Furthermore, when both a primary and redundant network develop faults, exclusive use of either network will not provide full network operability.
One solution is use of a method or apparatus that can detect and manage the state of a network of computers utilizing redundant communication channels.
Such a system incorporates in various embodiments nodes which are capable of detecting and managing the state of communication channels between the node and each other fault-tolerant network node to which it is connected. In some embodiments, such network nodes employ a network status data record indicating the state of each of a primary and redundant network connection to each other node, and further employ logic enabling determination of an operable data path to send and receive data between each pair of nodes.
But, such networks will desirably include nodes which do not have full fault-tolerant capability. One common example of such a non-fault-tolerant networlc node is a standard office laser printer with a built-in network connection.
What is needed is a method and apparatus to facilitate communication with non-fault-tolerant network nodes in such a fault-tolerant network system.
Summary of the Invention The present invention provides a method and apparatus for operation of non-fault tolerant network nodes in a fault-tolerant network enviromnent. In some embodiments, a network address or network location of any network nodes present on a network that are not fault-tolerant is determined and stored, and data to be sent to the detected non-fault-tolerant network nodes is routed only over that network to which the non-fault-tolerant network node is connected. In various further embodiments, the fault-tolerant network comprises a primary and redundant networlc with fault tolerant network nodes that are attached to each network;
a non-fault-tolerant network node that is attached to either the primary or redundant network is then operable to communicates with any fault-tolerant network node via data sent over only the networlc to which the non-fault-tolerant network node is connected.
Brief Description of the Figures Figure 1 shows a diagram of a fault-tolerant computer network with multiple fault-tolerant network nodes having primacy and redundant network connections and having multiple non-fault-tolerant network nodes, consistent with an embodiment of the present invention.
Figure 2 shows a flowchart of a method of managing communication with non-fault-tolerant network nodes in a fault-tolerant computer network, consistent with an embodiment of the present invention.
Detailed Description In the following detailed description of sample embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific sample embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the invention is defined ony by the appended claims.
The present invention provides a method and apparatus for managing communication with non-fault-tolerant network nodes in a fault-tolerant network.
The invention is capable in various embodiments of identifying the network location and address of non-fault tolerant networlc nodes, and of routing data only over certain portions of the network to communicate with the non-fault-tolerant network node. The network in some embodiments comprises a primary and a redundant network having connections to each fault-tolerant network node, and the invention comprises routing information to non-fault-tolerant network nodes connected to either the primary or redundant network via only that network to which the non-fault-tolerant networlc node is connected.
The invention in various forms is implemented within an existing network interface technology, such as Ethernet. In one such embodiment, the fault-tolerant network comprises two Ethernet connections connected to each fault-tolerant computer or node - a primary network connection and a redundant network connection. It is not critical fox purposes of the invention which connection is the primary connection and which is the redundant connection, as the connections are physically and functionally similar. In the example embodiment discussed here, the primary and redundant network connections are interchangeable and are named primarily for the purpose of distinguishing the two networks from each other.
Each of the primary and redundant networks also may have one or more non-fault-tolerant network nodes attached, and communication with such non-fault-tolerant networks is facilitated by the present invention.
Figure 1 illustrates an exemplary fault-tolerant network with fault-tolerant network nodes 101, 102 and 103. A primary network 104 and a redundant network 1 OS link each node to the other nodes of the network, as indicated by the lines connecting the nodes to each of the networks. Non-fault tolerant network nodes are also connected to each network, including non-fault-tolerant network node connected to the primary network 104 and non-fault-tolerant network node 107 comlected to redundant network 105.
The fault-tolerant network connections linking the fault-tolerant network nodes axe configured such that the fault-tolerant network nodes can communicate with each other despite multiple network faults, such as by use in some embodiments of particular node-to-node communication rules and network status monitoring capability within each node. The communication rules in various embodiments of a fault-tolerant network facilitate determination of a network path between each pair of nodes based on the network status data stored in and communicated between each fault-tolerant network node. Each fault-tolerant network node of such a system must be able to recognize non-fault-tolerant network nodes and adapt its communication rules for communicating with non-fault-tolerant network nodes such as nodes 106 and 107 of the example network of Figure 1.
In a typical single network configuration, data intended for a network node is simply sent over the network to the intended node. But, where multiple networks are combined to form a fault-tolerant network capable of compensating for multiple faults such as the network of Figure 1, data intended for a single non-fault-tolerant network node such as node 106 or 107 is desirably sent over the specific network to which the non-fault-tolerant network node is connected.
In some embodiments of the invention, data intended for a non-fault-tolerant network node such as non-fault-tolerant network node 106 is simply broadcast or transmitted over both the primary network 104 and the redundant network 105, ensuring that the data is sent to the network to which the non-fault-tolerant network node is connected. Such a system does not require tracking addresses or locations of non-fault-tolerant network nodes, and simply relies on the network interface adapters of the redundant network 105 to filter out the extra data.
But, such a configuration is reliant on the ability of the nodes connected to the redundant network 105 to ignore the data intended for a networlc node not attached to that network, and further wastes network bandwidth on the redundant network.
Other embodiments of the invention comprise maintaining an address table of detected non-fault-tolerant network nodes that are present on both the primary network 104 and the redundant network 105, and further associating each address or non-fault-tolerant network node with the network on which the node address was detected. In some embodiments of the invention, detection of the non-fault-tolerant network node address comprises monitoring for and intercepting Internet Protocol (IP) Address Resolution Protocol (ARP) packets that are sent by each node in certain IP-compatible networlc configurations. For example, each ARP
packet in an Ethernet network contains the Media Access Control (MAC) address that uniquely identifies the node transmitting the IP ARP packet. The intercepted MAC address of each non-fault-tolerant network node is then recorded along with the network on which the non-fault-tolerant network node is detected. In other embodiments, other network hardware and communication protocols may be used for the same purpose, and are within the scope of the invention.
To send data from a fault-tolerant network node to a non-fault-tolerant network node in such embodiments of the invention, the address of the desired node is found in the stored address records of the sending fault-tolerant network node, and the associated network is determined. For example, if fault-tolerant networlc node 101 initiates a data transfer to non-fault-tolerant network node 106, node 1 O1 searches its stored address records and finds the address of node 106, and further finds that the address data for node 106 was received on the primary network 104 rather than the redundant network 105. Node 101 then sends the data intended for node 106 only over network 104, eliminating the need to send the same data over redundant network 105 and use additional network bandwidth.
In further embodiments of the invention, fault-tolerant network nodes such as node 101 use the network status data indicating the ability of that node to communicate with other fault-tolerant network nodes to reroute data intended for a non-fault-tolerant network node around a network fault. This is achieved in some embodiments by initially sending the data on the network on which the non-fault-tolerant network node does not reside and using a selected fault-tolerant network node to transfer the sent data to the network on which the non-fault-tolerant network node resides at a point on the non-fault-tolerant network node's network such that the fault on the non-fault-tolerant networlc node's network is not between the transferring node and the non-fault-tolerant receiving node. Other embodiments exist in which data can be rerouted across the fault-tolerant networks to avoid multiple faults, and are within the scope of the invention.
In further embodiments, data sent to non-fault-tolerant networlc nodes is sent over all networks in the fault-tolerant network system rather than sent over a single network if the record containing address and network data for non-fault-tolerant network nodes does not contain data on the intended destination non-fault-tolerant network node. Sending such data comprises sending or replicating the data on both the primary and redundant network of the example network discussed above and shown in Figure 1.
Figure 2 is a flowchart of a method of managing communication between fault-tolerant network nodes and non-fault-tolerant network nodes in a fault-tolerant network such as the example network of Figure I. At 201, each fault-tolerant network node determines the network address of any non-fault-tolerant network nodes present on each network to which the fault-tolerant network node is connected. This may be achieved in any suitable manner, including searching for IP ARP packets or other identifying data transmitted by the non-fault-tolerant network nodes. At 202, each fault-tolerant network node further determines the networlc on which each non-fault-tolerant network node exists. In some embodiments, this simply comprises detecting which network adapter in the detecting fault-tolerant network node detected the IP ARP packet or other identifying data. At 203, the fault-tolerant network nodes each store the data determined at 201 and 202. The address and network data for each non-fault-tolerant network node are associated with each other in the stored data in one embodiment, so that looking up a record for a particular non-fault-tolerant network node results in retrieval of both the network address of the node and the network on which the node resides. In various embodiments, the process of determination of network addresses and networks associated with each non-fault-tolerant network node and the storing of this data is a continuous process, and occurs even during other operations such as execution of other blocks of the flowchart of Figure 2.
At 204, a fault-tolerant networlc node initiates sending data to a non-fault-tolerant network node. At 205, the stored data is searched for the address and network of the non-fault-tolerant network node. At 206, a decision is made based on determination of whether the address and network data for the non-fault-tolerant network node are present in the stored data. If the address and network data axe present in the stored data, the data to be sent is sent from the fault-tolerant network node to the non-fault-tolerant network node over only that network to which the stored data indicates the non-fault-tolerant network node is connected at 207.
In other embodiments, the data is sent indirectly via one or more intermediate nodes to the non-fault-tolerant network node, to avoid one or more networlc faults.
If the address and network data are not present in the stored data, the data to be sent is sent over all networks to which the sending fault-tolerant network node is comzected to ensure that the intended non-fault-tolerant network node receives the data. In the example of Figure 1, the data would be sent over both the primary network 104 and the redundant network 105.
The present invention provides a method and apparatus that enable a network with primary and redundant network connections to manage routing of data to non-fault-tolerant network nodes within the network. Some embodiments of the invention incorporate a data record within each fault-tolerant network node that contains detected address and network data for each non-fault-tolerant networlc node, and which then is used by the fault-tolerant network node to determine over which network data intended for a specific non-fault-tolerant network node should be sent. In some embodiments, the invention includes rerouting data that cannot be transferred directly from a fault-tolerant network node to a non-fault-tolerant network node due to a network fault, and comprises routing the data to one or more intermediate nodes which are able to facilitate communication between the nodes.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the invention. It is intended that this invention be limited only by the claims, and the full scope of equivalents thereof.
Notice of Copending Applications This application is related to the following copending applications, which are hereby incorporated by reference:
"Fault Tolerant Networking", serial number 09/188,976; and Atty. doclcet number 256.044us1 Background of the Invention Computer networks have become increasingly important to communication and productivity in environments where computers are utilized for worlc.
Electronic mail has in many situations replaced paper mail and faxes as a means of distribution of information, and the availability of vast amounts of information on the Internet has become an invaluable resource both fox many work-related and personal tasks. The ability to exchange data over computer networlcs also enables sharing of computer resources such as printers in a work environment, and enables centralized networlc-based management of the networked computers.
For example, an off ce worker's personal computer may run software that is installed and updated automatically via a network, and that generates data that is printed to a networked printer shared by people in several different offices.
The network may be used to inventory the software and hardware installed in each personal computer, greatly simplifying the task of inventory management. Also, the software and hardware conf guration of each computer may be managed via the network, making the task of user support easier in a networked environment.
Networked computers also typically are connected to one or more network servers that provide data and resources to the networked computers. For example, a server may store a number of software applications that can be executed by the networked computers, or may store a database of data that can be accessed and utilized by the networked computers. The network servers typically also manage access to certain networked devices such as printers, which can be utilized by any of the networked computers. Also, a server may facilitate exchange of data such as e-mail or other similar services between the networked computers.
Connection from the local networlc to a larger network such as the Internet can provide greater ability to exchange data, such as by providing Internet e-mail access or access to the World Wide Web. These data connections make conducting business via the Internet practical, and have contributed to the growth in development and use of computer networks. Internet servers that provide data and serve functions sucn as e-commerce, streaming audio or video, e-mail, or provide other content rely on the operation of local networks as well as the Internet to provide a path between such data servers and client computer systems.
But Iike other electronic systems, networks are subject to failures.
Misconfiguration, broken wires, failed electronic components, and a number of other factors can cause a computer network connection to fail, leading to possible inoperability of the computer network. Such failures can be minimized in critical networking environments such as process control, medical, or other critical applications by utilization of backup or redundant network components. One example is use of a second network connection to critical network nodes providing the same function as the first network connection. But, management of the networlc connections to facilitate operation in the event of a network failure can be a difficult task, and is itself subject to the ability of a network system or user to properly detect and compensate for the network fault. Furthermore, when both a primary and redundant network develop faults, exclusive use of either network will not provide full network operability.
One solution is use of a method or apparatus that can detect and manage the state of a network of computers utilizing redundant communication channels.
Such a system incorporates in various embodiments nodes which are capable of detecting and managing the state of communication channels between the node and each other fault-tolerant network node to which it is connected. In some embodiments, such network nodes employ a network status data record indicating the state of each of a primary and redundant network connection to each other node, and further employ logic enabling determination of an operable data path to send and receive data between each pair of nodes.
But, such networks will desirably include nodes which do not have full fault-tolerant capability. One common example of such a non-fault-tolerant networlc node is a standard office laser printer with a built-in network connection.
What is needed is a method and apparatus to facilitate communication with non-fault-tolerant network nodes in such a fault-tolerant network system.
Summary of the Invention The present invention provides a method and apparatus for operation of non-fault tolerant network nodes in a fault-tolerant network enviromnent. In some embodiments, a network address or network location of any network nodes present on a network that are not fault-tolerant is determined and stored, and data to be sent to the detected non-fault-tolerant network nodes is routed only over that network to which the non-fault-tolerant network node is connected. In various further embodiments, the fault-tolerant network comprises a primary and redundant networlc with fault tolerant network nodes that are attached to each network;
a non-fault-tolerant network node that is attached to either the primary or redundant network is then operable to communicates with any fault-tolerant network node via data sent over only the networlc to which the non-fault-tolerant network node is connected.
Brief Description of the Figures Figure 1 shows a diagram of a fault-tolerant computer network with multiple fault-tolerant network nodes having primacy and redundant network connections and having multiple non-fault-tolerant network nodes, consistent with an embodiment of the present invention.
Figure 2 shows a flowchart of a method of managing communication with non-fault-tolerant network nodes in a fault-tolerant computer network, consistent with an embodiment of the present invention.
Detailed Description In the following detailed description of sample embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific sample embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, and other changes may be made without departing from the spirit or scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the invention is defined ony by the appended claims.
The present invention provides a method and apparatus for managing communication with non-fault-tolerant network nodes in a fault-tolerant network.
The invention is capable in various embodiments of identifying the network location and address of non-fault tolerant networlc nodes, and of routing data only over certain portions of the network to communicate with the non-fault-tolerant network node. The network in some embodiments comprises a primary and a redundant network having connections to each fault-tolerant network node, and the invention comprises routing information to non-fault-tolerant network nodes connected to either the primary or redundant network via only that network to which the non-fault-tolerant networlc node is connected.
The invention in various forms is implemented within an existing network interface technology, such as Ethernet. In one such embodiment, the fault-tolerant network comprises two Ethernet connections connected to each fault-tolerant computer or node - a primary network connection and a redundant network connection. It is not critical fox purposes of the invention which connection is the primary connection and which is the redundant connection, as the connections are physically and functionally similar. In the example embodiment discussed here, the primary and redundant network connections are interchangeable and are named primarily for the purpose of distinguishing the two networks from each other.
Each of the primary and redundant networks also may have one or more non-fault-tolerant network nodes attached, and communication with such non-fault-tolerant networks is facilitated by the present invention.
Figure 1 illustrates an exemplary fault-tolerant network with fault-tolerant network nodes 101, 102 and 103. A primary network 104 and a redundant network 1 OS link each node to the other nodes of the network, as indicated by the lines connecting the nodes to each of the networks. Non-fault tolerant network nodes are also connected to each network, including non-fault-tolerant network node connected to the primary network 104 and non-fault-tolerant network node 107 comlected to redundant network 105.
The fault-tolerant network connections linking the fault-tolerant network nodes axe configured such that the fault-tolerant network nodes can communicate with each other despite multiple network faults, such as by use in some embodiments of particular node-to-node communication rules and network status monitoring capability within each node. The communication rules in various embodiments of a fault-tolerant network facilitate determination of a network path between each pair of nodes based on the network status data stored in and communicated between each fault-tolerant network node. Each fault-tolerant network node of such a system must be able to recognize non-fault-tolerant network nodes and adapt its communication rules for communicating with non-fault-tolerant network nodes such as nodes 106 and 107 of the example network of Figure 1.
In a typical single network configuration, data intended for a network node is simply sent over the network to the intended node. But, where multiple networks are combined to form a fault-tolerant network capable of compensating for multiple faults such as the network of Figure 1, data intended for a single non-fault-tolerant network node such as node 106 or 107 is desirably sent over the specific network to which the non-fault-tolerant network node is connected.
In some embodiments of the invention, data intended for a non-fault-tolerant network node such as non-fault-tolerant network node 106 is simply broadcast or transmitted over both the primary network 104 and the redundant network 105, ensuring that the data is sent to the network to which the non-fault-tolerant network node is connected. Such a system does not require tracking addresses or locations of non-fault-tolerant network nodes, and simply relies on the network interface adapters of the redundant network 105 to filter out the extra data.
But, such a configuration is reliant on the ability of the nodes connected to the redundant network 105 to ignore the data intended for a networlc node not attached to that network, and further wastes network bandwidth on the redundant network.
Other embodiments of the invention comprise maintaining an address table of detected non-fault-tolerant network nodes that are present on both the primary network 104 and the redundant network 105, and further associating each address or non-fault-tolerant network node with the network on which the node address was detected. In some embodiments of the invention, detection of the non-fault-tolerant network node address comprises monitoring for and intercepting Internet Protocol (IP) Address Resolution Protocol (ARP) packets that are sent by each node in certain IP-compatible networlc configurations. For example, each ARP
packet in an Ethernet network contains the Media Access Control (MAC) address that uniquely identifies the node transmitting the IP ARP packet. The intercepted MAC address of each non-fault-tolerant network node is then recorded along with the network on which the non-fault-tolerant network node is detected. In other embodiments, other network hardware and communication protocols may be used for the same purpose, and are within the scope of the invention.
To send data from a fault-tolerant network node to a non-fault-tolerant network node in such embodiments of the invention, the address of the desired node is found in the stored address records of the sending fault-tolerant network node, and the associated network is determined. For example, if fault-tolerant networlc node 101 initiates a data transfer to non-fault-tolerant network node 106, node 1 O1 searches its stored address records and finds the address of node 106, and further finds that the address data for node 106 was received on the primary network 104 rather than the redundant network 105. Node 101 then sends the data intended for node 106 only over network 104, eliminating the need to send the same data over redundant network 105 and use additional network bandwidth.
In further embodiments of the invention, fault-tolerant network nodes such as node 101 use the network status data indicating the ability of that node to communicate with other fault-tolerant network nodes to reroute data intended for a non-fault-tolerant network node around a network fault. This is achieved in some embodiments by initially sending the data on the network on which the non-fault-tolerant network node does not reside and using a selected fault-tolerant network node to transfer the sent data to the network on which the non-fault-tolerant network node resides at a point on the non-fault-tolerant network node's network such that the fault on the non-fault-tolerant networlc node's network is not between the transferring node and the non-fault-tolerant receiving node. Other embodiments exist in which data can be rerouted across the fault-tolerant networks to avoid multiple faults, and are within the scope of the invention.
In further embodiments, data sent to non-fault-tolerant networlc nodes is sent over all networks in the fault-tolerant network system rather than sent over a single network if the record containing address and network data for non-fault-tolerant network nodes does not contain data on the intended destination non-fault-tolerant network node. Sending such data comprises sending or replicating the data on both the primary and redundant network of the example network discussed above and shown in Figure 1.
Figure 2 is a flowchart of a method of managing communication between fault-tolerant network nodes and non-fault-tolerant network nodes in a fault-tolerant network such as the example network of Figure I. At 201, each fault-tolerant network node determines the network address of any non-fault-tolerant network nodes present on each network to which the fault-tolerant network node is connected. This may be achieved in any suitable manner, including searching for IP ARP packets or other identifying data transmitted by the non-fault-tolerant network nodes. At 202, each fault-tolerant network node further determines the networlc on which each non-fault-tolerant network node exists. In some embodiments, this simply comprises detecting which network adapter in the detecting fault-tolerant network node detected the IP ARP packet or other identifying data. At 203, the fault-tolerant network nodes each store the data determined at 201 and 202. The address and network data for each non-fault-tolerant network node are associated with each other in the stored data in one embodiment, so that looking up a record for a particular non-fault-tolerant network node results in retrieval of both the network address of the node and the network on which the node resides. In various embodiments, the process of determination of network addresses and networks associated with each non-fault-tolerant network node and the storing of this data is a continuous process, and occurs even during other operations such as execution of other blocks of the flowchart of Figure 2.
At 204, a fault-tolerant networlc node initiates sending data to a non-fault-tolerant network node. At 205, the stored data is searched for the address and network of the non-fault-tolerant network node. At 206, a decision is made based on determination of whether the address and network data for the non-fault-tolerant network node are present in the stored data. If the address and network data axe present in the stored data, the data to be sent is sent from the fault-tolerant network node to the non-fault-tolerant network node over only that network to which the stored data indicates the non-fault-tolerant network node is connected at 207.
In other embodiments, the data is sent indirectly via one or more intermediate nodes to the non-fault-tolerant network node, to avoid one or more networlc faults.
If the address and network data are not present in the stored data, the data to be sent is sent over all networks to which the sending fault-tolerant network node is comzected to ensure that the intended non-fault-tolerant network node receives the data. In the example of Figure 1, the data would be sent over both the primary network 104 and the redundant network 105.
The present invention provides a method and apparatus that enable a network with primary and redundant network connections to manage routing of data to non-fault-tolerant network nodes within the network. Some embodiments of the invention incorporate a data record within each fault-tolerant network node that contains detected address and network data for each non-fault-tolerant networlc node, and which then is used by the fault-tolerant network node to determine over which network data intended for a specific non-fault-tolerant network node should be sent. In some embodiments, the invention includes rerouting data that cannot be transferred directly from a fault-tolerant network node to a non-fault-tolerant network node due to a network fault, and comprises routing the data to one or more intermediate nodes which are able to facilitate communication between the nodes.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the invention. It is intended that this invention be limited only by the claims, and the full scope of equivalents thereof.
Claims (27)
1. A method of managing communication with non-fault tolerant network nodes in a fault-tolerant computer network, comprising:
determining network addresses of network nodes present in a plurality of networks that are not fault-tolerant and are connected to only a single network;
determining the network on which each non-fault tolerant network node exists;
storing the detected network address data of the non-fault tolerant network nodes and storing associated network data comprising the network on which the non-fault tolerant network node exists therewith; and sending data intended for a non-fault tolerant network node over only the network on which the non-fault tolerant network node has been determined to exist.
determining network addresses of network nodes present in a plurality of networks that are not fault-tolerant and are connected to only a single network;
determining the network on which each non-fault tolerant network node exists;
storing the detected network address data of the non-fault tolerant network nodes and storing associated network data comprising the network on which the non-fault tolerant network node exists therewith; and sending data intended for a non-fault tolerant network node over only the network on which the non-fault tolerant network node has been determined to exist.
2. The method of claim 1, wherein determining the network addresses of non-fault-tolerant network nodes comprises detection of network address information that the non-fault-tolerant network nodes send over a network.
3. The method of claim 2, wherein the network address information that is sent comprises Internet Protocol Address Resolution Protocol packets (IP ARP
packets).
packets).
4. The method of claim 2, wherein determining the network on which each non-fault-tolerant network node exists comprises determining which network interface received the network address information sent from each non-fault-tolerant network node.
5. The method of claim 1, wherein storing the data comprises populating a non-fault-tolerant network node address table.
6. The method of claim 1, further comprising sending data intended for a non-fault-tolerant network node over both the primary and redundant network if the network on which the non-fault-tolerant network node exists has not been determined.
7. The method of claim 6, wherein determination of whether the network on which the non-fault-tolerant network node exists has been determined comprises:
searching an address table for the stored data;
determining the network on which the non-fault-tolerant network node exists has bean determined if the address table contains an entry for the non-fault-tolerant network node; and determining the network on which the non-fault-tolerant network node exists has not been determined if the address table does not contain an entry for the non-fault-tolerant network node.
searching an address table for the stored data;
determining the network on which the non-fault-tolerant network node exists has bean determined if the address table contains an entry for the non-fault-tolerant network node; and determining the network on which the non-fault-tolerant network node exists has not been determined if the address table does not contain an entry for the non-fault-tolerant network node.
8. A method of managing communication with non-fault tolerant network nodes in a fault-tolerant computer network, comprising:
transmitting data from a transmitting node to a non-fault tolerant network node over a primary network; and transmitting data from the transmitting node to the non-fault tolerant network node over a redundant network.
transmitting data from a transmitting node to a non-fault tolerant network node over a primary network; and transmitting data from the transmitting node to the non-fault tolerant network node over a redundant network.
9. The method of claim 8, further comprising receiving and retransmitting the data via an intermediate node when the transmitting node is unable to communicate with both the primary and redundant networks, such that if the intermediate node receives the data via the redundant network it retransmits the data on the primary network and if the intermediate node receives the data via the primary network it retransmits the data on the redundant network.
10. A fault-tolerant network node interface operable to communicate with non-fault-tolerant network nodes, the interface operable to:
determine the network addresses of network nodes present in a plurality of networks that axe not fault-tolerant and are connected to only a single network;
determine the network on which each non-fault tolerant network node exists;
store the detected network address data of the non-fault tolerant network nodes and to store associated network data comprising the network on which the non-fault tolerant network node exists therewith; and send data intended for a non-fault tolerant network node over only the network on which the non-fault tolerant network node has been determined to exist.
determine the network addresses of network nodes present in a plurality of networks that axe not fault-tolerant and are connected to only a single network;
determine the network on which each non-fault tolerant network node exists;
store the detected network address data of the non-fault tolerant network nodes and to store associated network data comprising the network on which the non-fault tolerant network node exists therewith; and send data intended for a non-fault tolerant network node over only the network on which the non-fault tolerant network node has been determined to exist.
11. The interface of claim 10, wherein determining the network addresses of non-14~
fault-tolerant network nodes comprises detection of network address information that the non-fault-tolerant network nodes send over a network.
fault-tolerant network nodes comprises detection of network address information that the non-fault-tolerant network nodes send over a network.
12. The interface of claim 11, wherein the network address information that is sent comprises Internet Protocol Address Resolution Protocol packets (IP ARP
packets).
packets).
13. The interface of claim 11, wherein determining the network on which each non-fault-tolerant network node exists comprises determining which network interface received the network address information sent from each non-fault-tolerant network node.
14. The interface of claim 10, wherein storing the data comprises populating a non-fault-tolerant network node address table.
15. The interface of claim 10, wherein the network interface is further operable to send data intended for a non-fault-tolerant network node over both the primary and redundant network if the network on which the non-fault-tolerant network node exists has not been determined.
16. The interface of claim 15, wherein determination of whether the network on which the non-fault-tolerant network node exists has been determined comprises:
searching an address table for the stored data;
determining the network on which the non-fault-tolerant network node exists has been determined if the address table contains an entry for the non-fault-tolerant network node; and determining the network on which the non-fault-tolerant network node exists has not been determined if the address table does not contain an entry for the non-fault-tolerant network node.
searching an address table for the stored data;
determining the network on which the non-fault-tolerant network node exists has been determined if the address table contains an entry for the non-fault-tolerant network node; and determining the network on which the non-fault-tolerant network node exists has not been determined if the address table does not contain an entry for the non-fault-tolerant network node.
17. A fault-tolerant network node interface operable to communicate with non-fault-tolerant network nodes, the interface operable to:
transmit data to a non-fault-tolerant network node over a primary network;
and transmit data to a non-fault-tolerant network node over a redundant network.
transmit data to a non-fault-tolerant network node over a primary network;
and transmit data to a non-fault-tolerant network node over a redundant network.
18. The interface of claim 17, wherein transmitting data to a non-fault tolerant network node comprises receiving and retransmitting the data via an intermediate node when the transmitting node is unable to communicate with both the primary and redundant networks, such that if the intermediate node receives the data via the redundant network it retransmits the data on the primary network and if the intermediate node receives the data via the primary network it retransmits the data on the redundant network.
19. A machine-readable medium with instructions stored thereon, the instructions when executed on a computerized system operable to cause the computerized system to:
determine the network addresses of network nodes present in a plurality of networks that are not fault-tolerant and are connected to only a single network;
determine the network on which each non-fault tolerant network node exists;
store the detected network address data of the non-fault tolerant network nodes and to store associated network data comprising the network on which the non-fault tolerant network node exists therewith; and send data intended for a non-fault tolerant network node over only the network on which the non-fault tolerant network node has been determined to exist.
determine the network addresses of network nodes present in a plurality of networks that are not fault-tolerant and are connected to only a single network;
determine the network on which each non-fault tolerant network node exists;
store the detected network address data of the non-fault tolerant network nodes and to store associated network data comprising the network on which the non-fault tolerant network node exists therewith; and send data intended for a non-fault tolerant network node over only the network on which the non-fault tolerant network node has been determined to exist.
20. The machine-readable medium of claim 19, wherein determining the network addresses of non-fault-tolerant network nodes comprises detection of network address information that the non-fault-tolerant network nodes send over a network.
21. The machine-readable medium of claim 20, wherein the network address information that is sent comprises Internet Protocol Address Resolution Protocol packets (IP ARP packets).
22. The machine-readable medium of claim 20, wherein determining the network on which each non-fault-tolerant network node exists comprises determining which network interface received the network address information sent from each non-fault-tolerant network node.
23. The machine-readable medium of claim 19, wherein storing the data comprises populating a non-fault-tolerant network node address table.
24. The machine-readable medium of claim 19, the instructions when executed further operable to cause a computerized system to send data intended for a non-fault-tolerant network node over both the primary and the redundant network if the network on which the non-fault-tolerant network node exists has not been determined.
25. The machine-readable medium of claim 24, wherein determination of whether the network on which the non-fault-tolerant network node exists has been determined comprises:
searching an address table for the stored data;
determining the network on which the non-fault-tolerant network node exists has been determined if the address table contains an entry for the non-fault-tolerant network node; and determining the network on which the non-fault-tolerant network node exists has not been determined if the address table does not contain an entry for the non-fault-tolerant network node.
searching an address table for the stored data;
determining the network on which the non-fault-tolerant network node exists has been determined if the address table contains an entry for the non-fault-tolerant network node; and determining the network on which the non-fault-tolerant network node exists has not been determined if the address table does not contain an entry for the non-fault-tolerant network node.
26. A machine-readable medium with instructions stored thereon, the instructions when executed on a computerized system operable to cause the computerized system to:
transmit data to a non-fault-tolerant network node over a primary network;
and transmit data to the non-fault-tolerant network node over a redundant network.
transmit data to a non-fault-tolerant network node over a primary network;
and transmit data to the non-fault-tolerant network node over a redundant network.
27. The machine-readable medium of claim 26, the instructions when executed further operable to cause a computerized network of nodes to receive and retransmit the data via an intermediate node when the transmitting node is unable to communicate with both the primary and redundant networks, such that if the intermediate node receives the data via the redundant network it retransmits the data on the primary network and if the intermediate node receives the data via the primary network it retransmits the data on the redundant network.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US09/522,702 | 2000-03-10 | ||
| US09/522,702 US6901443B1 (en) | 2000-03-10 | 2000-03-10 | Non-fault tolerant network nodes in a multiple fault tolerant network |
| PCT/US2001/007405 WO2001069850A2 (en) | 2000-03-10 | 2001-03-08 | Non-fault tolerant network nodes in a multiple fault tolerant network |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2402872A1 true CA2402872A1 (en) | 2001-09-20 |
Family
ID=24081976
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002402872A Abandoned CA2402872A1 (en) | 2000-03-10 | 2001-03-08 | Non-fault tolerant network nodes in a multiple fault tolerant network |
Country Status (9)
| Country | Link |
|---|---|
| US (1) | US6901443B1 (en) |
| EP (1) | EP1262040B1 (en) |
| JP (1) | JP2004500778A (en) |
| CN (1) | CN1185828C (en) |
| AT (1) | ATE375650T1 (en) |
| AU (2) | AU4911401A (en) |
| CA (1) | CA2402872A1 (en) |
| DE (1) | DE60130873T2 (en) |
| WO (1) | WO2001069850A2 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006042776A1 (en) * | 2004-10-20 | 2006-04-27 | Siemens Aktiengesellschaft | Method for error detection in a packet-based message distribution system |
| US7593323B2 (en) * | 2005-08-17 | 2009-09-22 | Honeywell International Inc. | Apparatus and methods for managing nodes on a fault tolerant network |
| US8315274B2 (en) * | 2006-03-29 | 2012-11-20 | Honeywell International Inc. | System and method for supporting synchronous system communications and operations |
| US7817538B2 (en) * | 2006-09-13 | 2010-10-19 | Rockwell Automation Technologies, Inc. | Fault-tolerant Ethernet network |
| JP4893533B2 (en) * | 2007-08-24 | 2012-03-07 | コニカミノルタホールディングス株式会社 | Network connection management method and information processing apparatus |
| US8670303B2 (en) | 2011-10-05 | 2014-03-11 | Rockwell Automation Technologies, Inc. | Multiple-fault-tolerant ethernet network for industrial control |
| US9450916B2 (en) | 2014-08-22 | 2016-09-20 | Honeywell International Inc. | Hardware assist for redundant ethernet network |
Family Cites Families (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5862344A (en) * | 1995-08-28 | 1999-01-19 | Ncr Corporation | Apparatus and methods for routing data packets through a processing system network |
| DE19533961A1 (en) | 1995-09-13 | 1997-03-20 | Siemens Ag | Method for loading software in communication systems with non-redundant, decentralized devices |
| US5852724A (en) * | 1996-06-18 | 1998-12-22 | Veritas Software Corp. | System and method for "N" primary servers to fail over to "1" secondary server |
| JP3224745B2 (en) * | 1996-07-09 | 2001-11-05 | 株式会社日立製作所 | High reliability network system and server switching method |
| US5963640A (en) * | 1996-11-07 | 1999-10-05 | Ericsson, Inc. | Radiotelephone having an acoustical wave guide coupled to a speaker |
| JPH10200552A (en) * | 1997-01-16 | 1998-07-31 | Yamatake Honeywell Co Ltd | Redundant method using ethernet communication |
| US6108300A (en) * | 1997-05-02 | 2000-08-22 | Cisco Technology, Inc | Method and apparatus for transparently providing a failover network device |
| US6356622B1 (en) * | 1997-05-02 | 2002-03-12 | Paradyne Corporation | System and apparatus for enhancing a network link |
| 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 |
| US5963540A (en) | 1997-12-19 | 1999-10-05 | Holontech Corporation | Router pooling in a network flowswitch |
| US6070187A (en) * | 1998-03-26 | 2000-05-30 | Hewlett-Packard Company | Method and apparatus for configuring a network node to be its own gateway |
| US6389030B1 (en) * | 1998-08-21 | 2002-05-14 | Adc Telecommunications, Inc. | Internet access over a ring network |
| US6370654B1 (en) * | 1998-12-17 | 2002-04-09 | Northern Telecom Limited | Method and apparatus to extend the fault-tolerant abilities of a node into a network |
| US6374316B1 (en) * | 1999-03-19 | 2002-04-16 | Sony Corporation | Method and system for circumscribing a topology to form ring structures |
| US6392990B1 (en) * | 1999-07-23 | 2002-05-21 | Glenayre Electronics, Inc. | Method for implementing interface redundancy in a computer network |
| US6535990B1 (en) * | 2000-01-10 | 2003-03-18 | Sun Microsystems, Inc. | Method and apparatus for providing fault-tolerant addresses for nodes in a clustered system |
| US6408000B1 (en) * | 2000-03-24 | 2002-06-18 | Securities Industry Automation Corporation | Multicast data distribution system |
-
2000
- 2000-03-10 US US09/522,702 patent/US6901443B1/en not_active Expired - Lifetime
-
2001
- 2001-03-08 EP EP01922297A patent/EP1262040B1/en not_active Expired - Lifetime
- 2001-03-08 CN CN01809257.8A patent/CN1185828C/en not_active Expired - Fee Related
- 2001-03-08 CA CA002402872A patent/CA2402872A1/en not_active Abandoned
- 2001-03-08 AU AU4911401A patent/AU4911401A/en active Pending
- 2001-03-08 DE DE60130873T patent/DE60130873T2/en not_active Expired - Lifetime
- 2001-03-08 WO PCT/US2001/007405 patent/WO2001069850A2/en active IP Right Grant
- 2001-03-08 AT AT01922297T patent/ATE375650T1/en not_active IP Right Cessation
- 2001-03-08 JP JP2001567178A patent/JP2004500778A/en not_active Withdrawn
- 2001-03-08 AU AU2001249114A patent/AU2001249114B2/en not_active Ceased
Also Published As
| Publication number | Publication date |
|---|---|
| WO2001069850A2 (en) | 2001-09-20 |
| CN1185828C (en) | 2005-01-19 |
| AU2001249114B2 (en) | 2004-11-25 |
| DE60130873T2 (en) | 2008-07-17 |
| ATE375650T1 (en) | 2007-10-15 |
| AU4911401A (en) | 2001-09-24 |
| DE60130873D1 (en) | 2007-11-22 |
| EP1262040B1 (en) | 2007-10-10 |
| US6901443B1 (en) | 2005-05-31 |
| CN1428030A (en) | 2003-07-02 |
| JP2004500778A (en) | 2004-01-08 |
| WO2001069850A3 (en) | 2002-01-10 |
| EP1262040A2 (en) | 2002-12-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6295558B1 (en) | Automatic status polling failover or devices in a distributed network management hierarchy | |
| US6760859B1 (en) | Fault tolerant local area network connectivity | |
| JPH1127320A (en) | Packet relay control method, packet repeater and program storage medium | |
| US7518983B2 (en) | Proxy response apparatus | |
| EP1773008B1 (en) | Method and system for implementing virtual router redundancy protocol on a resilient packet ring | |
| US6425008B1 (en) | System and method for remote management of private networks having duplicate network addresses | |
| AU2001241700B2 (en) | Multiple network fault tolerance via redundant network control | |
| EP1370918B1 (en) | Software-based fault tolerant networking using a single lan | |
| AU2001241700A1 (en) | Multiple network fault tolerance via redundant network control | |
| US20080205376A1 (en) | Redundant router having load sharing functionality | |
| EP1262040B1 (en) | Non-fault tolerant network nodes in a multiple fault tolerant network | |
| AU2001249114A1 (en) | Non-fault tolerant network nodes in a multiple fault tolerant network | |
| JP4464256B2 (en) | Network host monitoring device | |
| US7421479B2 (en) | Network system, network control method, and signal sender/receiver | |
| JP4028627B2 (en) | Client server system and communication management method for client server system | |
| JP2000059385A (en) | Method for managing plural systems at time of overlapping ip addresses | |
| JPH11331231A (en) | Multiplex network system and its communication equipment | |
| AU2002232814A1 (en) | Software-based fault tolerant networking using a single LAN | |
| JPH11177630A (en) | Address translation router system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |