|Publication number||US7593323 B2|
|Application number||US 11/205,693|
|Publication date||Sep 22, 2009|
|Filing date||Aug 17, 2005|
|Priority date||Aug 17, 2005|
|Also published as||CN101292502A, EP1915847A2, US20070041313, WO2007022183A2, WO2007022183A3|
|Publication number||11205693, 205693, US 7593323 B2, US 7593323B2, US-B2-7593323, US7593323 B2, US7593323B2|
|Original Assignee||Honeywell International Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (13), Referenced by (2), Classifications (9), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to computer networks, and more particularly to managing communications traffic on a fault tolerant network.
Networks provide communications from one node on a network to other nodes on the network. The nodes may include a variety of equipment that utilize the network to communicate information to other equipment on the network. For example, a workstation on a network may communicate with a server or a printer over the network. In a more basic network, a sensor may communicate information to a base computer, which may communicate information to a mechanical actuator. The base computer may communicate with a variety of sensors and a mechanical actuator to perform a desired operation.
The communication channel provides a medium to allow the network to communicate with the network nodes. The communication channel may be one or more conductive wires or optical cables. The communication channel may be a wireless communication channel using, for example, radio frequencies, microwaves, or infrared.
The network may be a Local Area Network (LAN). The nodes on the LAN may communicate with other LANs via a Wide Area Network. To provide routing of the data within a network and to various other connected networks, the network may use equipment to facilitate routing of data. For example, switches, routers, hubs, bridges may be used to transmit and communicate data between nodes and networks.
The network may use a protocol to allow the nodes to receive and transmit data. One of the most commonly used protocols is Ethernet. Ethernet allows nodes to package data, transmit the data to the desired node, and unpackage the data at the desired node. The nodes on the Ethernet network may use a network interface card to supply data from the node to the communication channel.
The Ethernet protocol also provides recovery of data that may be corrupted or lost during transmission. However, the protocol cannot recover when nodes or equipment on the network lose connection with the network. Fault tolerance is often provided to assure continued node-to-node communications. Redundancy of components on the networks allows the node to communicate over a secondary component when the primary component fails. Nodes of the fault tolerant network may have more than one network interface cards, and include nodes having multiple communication paths. A network fault tolerance manager oversees detection of failures and manipulation of failure recovery. Failure recovery includes redirecting data transmission of a node or component indicating a failure. The fault tolerance manager may terminate communications over a primary network interface card or communication path.
Even though the fault tolerant network may restore communications over a secondary component of the network, the node attached to an Ethernet network can sometimes suffer conditions that cause the node to generate inordinate amounts of traffic, assume the electronic identity of other nodes attached to the network, or otherwise interfere with the desired operation of the network. In a fault tolerant network deployed in a critical application, this failure mode could cause loss of visibility of that node or other nodes on the network. In some cases, this failure could cause loss of control of equipment associated with the node.
Accordingly, an efficient and effective system and method is needed for preventing error communication from failed nodes or equipment from interfering and/or preventing legitimate communication by other nodes on the network. In addition, the system and method may provide information to the fault tolerance manager regarding which components or equipment of the network are generating error communications.
It is, therefore, an objective of the present invention to provide devices, systems, and methods to manage communications traffic on a fault tolerant network. According to an exemplary embodiment of the present invention, a fault tolerant network may have two or more nodes. The system may have two or more channels of communication. Each channel of communication couples the two or more nodes. Each node selectively communicates on one of the two or more channels of communication. The system also has a switch in communication with the two or more channels. The switch receives network traffic and terminates network traffic on two or more of the channels of communication. The termination of network traffic causes a fault tolerance manager to reroute network traffic on one of the two or more communication channels.
In an alternate embodiment, the switch may terminate network traffic based on network traffic errors received or the volume of network traffic. In another embodiment, the switch has a network traffic analysis for determining network traffic statistics. The switch may communicate the network traffic statistics to the fault tolerance manager. In another embodiment, the termination of network traffic by the switch is controlled or dictated by the fault tolerance manager. In yet another embodiment, the termination of network traffic by the switch terminates traffic from selective nodes.
The above and other objectives and advantages of the present invention will be apparent upon consideration of the following detailed description, taken in conjunction with the accompanying drawings, in which like reference numbers refer to like parts throughout, and in which:
A fault tolerance network 100, as shown in
The fault tolerance network 100 may have some nodes with multiple network interface cards, for example, Node A and Node B as shown in
When in use, the fault tolerance network 100 provides redundant equipment to compensate for equipment failure. For example, if the network interface card coupling Node A to the first communication channel 102 should fail, the fault tolerance manager may terminate communication to Node A through that network interface card. The fault tolerance manager will begin sending communications destined for Node A to a second network interface card via the second communication channel 104. The fault tolerance network may also compensate for failure of a communication channel. For example, if the first communication channel 102 should fail at a point between Node B and Node A, the fault tolerance manager may continue to transmit communications to Node B via the first communication channel 102. To correct the problem associated with not being capable of sending communications over the first communication channel 102 beyond Node B, the fault tolerance manager may begin sending communications over the second communication channel 104. When equipment of the network fails or the manager node terminates network communication to a component, error messages may continue to be transmitted by the failing or terminated components. These error messages may produce unnecessary congestion or interfere with legitimate network traffic.
According to an exemplary embodiment of the present invention, the switch 106 may detect the increase in error communications from the terminated node A. The switch 106 may independently terminate communications on the first communication channel 102. The fault tolerance manager may correct the failure to communicate to node A and node B by transmitting communications to the second network interface card of node A and node B. The switch 106 may successfully prevent error communication from interfering with legitimate communication and allow the fault tolerance manager to reroute the communications for node A and node B to the second communication path 104.
Architecturally in terms of hardware, the switch 106 may include a processor, memory, and one or more input and output interface devices. The local interface may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among the components of a network.
The systems and methods may also be incorporated in software used with a computer or other suitable operating device of the switch. The software stored or loaded in the memory may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing the methods and systems of the invention. The software may work in conjunction with an operating system. The operating system essentially controls the execution of the computer programs, such as the software stored within the memory, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The system and method may also include a Graphic User Interface (GUI) to allow the administrator or user to enter constraints associated with the switch 106 managing communications traffic on a fault tolerant network, as will be discussed later herein.
The fault tolerance manager 202 controls the communication channels for the nodes of the network. A local failure in the fault tolerant network 200 may be characterized by a device failure affecting communications to one network interface card of a node. For example, a local failure of network interface card D1 of node D may result in the fault tolerance manager switching to network interface card D2. Node D may now communicate via network interface card D2 and the third switch 208.
While Node D no longer communicates traffic over network interface card D1, the second switch 206 may still receive a high volume of error traffic generated by the failure of network interface card D1 or the component of the network related to the failure. According to an exemplary embodiment of the invention, the second switch 206 may recognize the high volume of error traffic generated by network interface card D1. The second switch 206 may terminate network traffic received from network interface card D1. By taking this action the second switch 206 prevents the error message from propagating through the communication network and creating unnecessary congestion or further errors in communication.
The switch may also take additional measures by terminating all network traffic via the switch and allowing the fault tolerance manager to take appropriate action. According to the above example, the second switch 206 may terminate all communications. The fault tolerance manager 202 may direct communication from Node B through the first network interface card B1 and the first switch 204. The fault tolerance manager 202 may also direct communication from Node C through the second network interface card C2 and the third switch 208. The result of the second switch 206 terminating all traffic allows the communication network to continue communication while preventing errors generated by the first network interface card C1 of node C from propagating through the network and causing further problems.
The above example is for illustrative purposes. A variety of complex actions may be taken by the switch as one skilled in the art will appreciate. For example, the switch may be in communication with the fault tolerance manager or have memory to store the predefined procedures of the fault tolerance manager. These predefined procedures are the actions the fault tolerance manager will take based upon specific network component failures. The switch may sort through and analyze these actions and perform certain actions to cause the fault tolerance manager to react. The switch may also have a variety of predefined threshold levels that determine when and which actions should be performed by the switch. For example, if the switch receives a predefined volume of network traffic, the switch may terminate communication.
The switch may use a variety of stored thresholds and actions to control error traffic in the network. These actions and thresholds may be standardized and set based upon a specific general network configuration and fault tolerance manager. The actions and thresholds may be customized based upon parameters entered by a user or an administrator as previously discussed. The switch may also recognize components supported by the switch and define actions based upon the supported components.
In the exemplary system of
The switch may take into account a variety of failure detection modes used by a fault tolerance manager. A variety of failure detection modes used by fault tolerant networks are known. The switch may be used with a variety of these failure detection modes to aid the fault tolerant network in detecting a failure of at least one network component and responding to that failure.
In an alternate embodiment, the switch may also gather network communication statistics and report the statistics to the fault tolerance manager. The fault tolerance manager can use these statistics to determine the appropriate communication channels and equipment to utilize. The switch may communicate the error traffic to the fault tolerance manager via the communication channel of the network using the protocol of the network. Alternatively the switch may have an independent communication channel to communicate with the fault tolerance manager.
The statistics gathered by the switch may not be seen by the fault tolerance manager. For example, an error message may not be propagated by the switch and may not viewed by the fault tolerance manager. The invention allows the switch to gather this information and communicate the information to the fault tolerance manager. An aspect of this embodiment will be described in greater detail later herein.
The switch provides communications from the first node to the second node over a second channel (block 306). The switch may terminate network traffic on either the first channel or the second channel (block 308). The termination of network traffic or actions taken by the switch causes the fault tolerance manager to reroute network traffic (block 310). This allows the switch to control and change network traffic based on local network traffic that may not be viewed by the fault tolerance manager. As previously discussed, the switch may be preprogrammed to take into account a variety of network factors as well as factors specific to the fault tolerance manager and actions taken by the fault tolerance manager.
The switch may determine network traffic statistics (block 412). For example, the switch may record the amount and components generating network traffic. The switch may compute and analyze these statistics. The statistics may take into account the total volume of traffic transmitted by the switch. The switch may use these statistics to determine what actions to take. The switch may alternatively communicate the network traffic statistics to the fault tolerance manager (block 414). The network traffic statistics may include all the data gathered by the switch or a summarized version of the statistics. The fault tolerance manager may utilize these statistics to determine an appropriate fault tolerance mode or other action.
It will be understood that the foregoing is only illustrative of the principles of the invention and that various modifications can be made by those skilled in the art without departing from the scope and spirit of the invention. Accordingly, such embodiments will be recognized as within the scope of the present invention. For example, the exemplary embodiments are illustrated as being implemented within a switch of the network, however, one skilled in the art will appreciate that embodiments of the invention may be implemented with a variety of network components, for example, routers, hubs, and servers.
Persons skilled in the art will appreciate that the present invention can be practiced by other than the described embodiments, which are presented for purposes of illustration rather than of limitation and that the present invention is limited only by the claims that follow.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6133846||Oct 1, 1996||Oct 17, 2000||Honeywell Inc.||Low cost redundant communications system|
|US6275503||Jul 24, 1998||Aug 14, 2001||Honeywell International Inc.||Method for transmitting large information packets over networks|
|US6308282||Nov 10, 1998||Oct 23, 2001||Honeywell International Inc.||Apparatus and methods for providing fault tolerance of networks and network interface cards|
|US6373376||Sep 11, 2000||Apr 16, 2002||Honeywell International Inc.||AC synchronization with miswire detection for a multi-node serial communication system|
|US6448901||Sep 11, 2000||Sep 10, 2002||Honeywell International Inc||Status indicator for an interface circuit for a multi-node serial communication system|
|US6467003||Dec 2, 1999||Oct 15, 2002||Honeywell International, Inc.||Fault tolerant data communication network|
|US6851621||Aug 18, 2003||Feb 8, 2005||Honeywell International Inc.||PDA diagnosis of thermostats|
|US6901443||Mar 10, 2000||May 31, 2005||Honeywell International Inc.||Non-fault tolerant network nodes in a multiple fault tolerant network|
|US7305486 *||Jun 28, 2001||Dec 4, 2007||Kanad Ghose||System and method for fast, reliable byte stream transport|
|US20050129037||Nov 19, 2004||Jun 16, 2005||Honeywell International, Inc.||Ring interface unit|
|US20060182128 *||May 21, 2004||Aug 17, 2006||Tsuneo Nakata||Data communication system, communication device and communication program thereof|
|US20060203720 *||Jun 24, 2005||Sep 14, 2006||Shinya Kano||Data relay apparatus and data relay method|
|WO2000028715A1||Oct 7, 1999||May 18, 2000||Honeywell Inc.||Fault-tolerant networking|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8254291 *||Dec 15, 2009||Aug 28, 2012||Electronics And Telecommunications Research Institute||Ethernet device and lane operating method|
|US20100329112 *||Dec 15, 2009||Dec 30, 2010||Electronics And Telecommunications Research Institute||Ethernet device and lane operating method|
|Cooperative Classification||H04L69/14, H04L69/40, H04L41/0659|
|European Classification||H04L41/06C1, H04L29/14, H04L12/24D3, H04L29/06H|
|Aug 17, 2005||AS||Assignment|
Owner name: HONEYWELL INTERNATIONAL, INC., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HIDLE, FREDERICK;REEL/FRAME:016899/0451
Effective date: 20050812
|Oct 27, 2009||CC||Certificate of correction|
|Sep 21, 2010||CC||Certificate of correction|
|Feb 25, 2013||FPAY||Fee payment|
Year of fee payment: 4