Multiplex communications – Pathfinding or routing – Switching a message which includes an address header
Reexamination Certificate
1999-03-18
2003-01-28
Chin, Wellington (Department: 2664)
Multiplex communications
Pathfinding or routing
Switching a message which includes an address header
C370S242000, C370S244000, C709S224000
Reexamination Certificate
active
06512774
ABSTRACT:
TECHNICAL FIELD
The present invention relates to the field of computer system networks. In particular, the present invention pertains to a software-based module for augmenting a server computer system to perform network interface card fault tolerance and fail over.
BACKGROUND ART
Computer systems linked to each other in a network are commonly used in businesses and other organizations. Computer system networks (“networks”) provide a number of benefits for the user, such as increased productivity, flexibility, and convenience as well as resource sharing and allocation.
Networks are configured in different ways depending on implementation-specific details such as the hardware used and the physical location of the equipment, and also depending on the particular objectives of the network. In general, networks include one or more server computer systems, each communicatively coupled to numerous client computer systems.
In contemporary networks, server computer systems are typically coupled to the network using more than one network interface card (NIC). Multiple NICs increase the total available bandwidth capacity for transmitting and sending data packets. Multiple NICs also provide resiliency and redundancy if one of the NICs fails. In the case of a failure of a NIC, one of the other NICs is used to handle the traffic previously handled by the failed NIC, thereby increasing overall system reliability. Therefore, the client computer systems in communication with the server computer system through a particular NIC are not cut off from the server should that NIC fail. Accordingly, it is necessary to be able to detect when a NIC fails and, when a failed NIC is detected, to switch to a functioning NIC (this is referred to as fault tolerance and fail over support) as quickly as possible in order to minimize the time until a communication link is re-established between the server computer system and the client computer systems.
Prior Art
FIG. 1
is an illustration of exemplary network
50
including two virtual local area networks (VLANs). In network
50
, client computer system
140
(e.g., a workstation) is in one VLAN, and client computer systems
141
,
142
and
143
are in a second VLAN. Both VLANs are serviced by server computer system
160
. A data packet sent by server computer system
160
contains address information that is used to identify the particular client computer system(s) to which the data packet is to be sent. In addition, the data packet is tagged with a VLAN identifier that identifies the destination VLAN. The methods for addressing a data packet in a network comprising multiple VLANs are well known in the art; one method is defined by the IEEE 802.1Q standard.
Switches
150
and
151
are able to read the VLAN identifier and the other address information contained in the data packet and direct the data packet accordingly. Thus, switch
150
reads the VLAN identifier and will direct the data packet to client computer system
140
if appropriate. Otherwise, the data packet proceeds to switch
151
, which directs the data packet to the proper client computer system (e.g., client computer systems
141
,
142
or
143
) depending on the address information contained in the data packet.
One prior art technique for fault tolerance and fail over support utilizes a switch-dependent protocol implemented using server computer system
160
and switches
150
and
151
. This prior art technique also requires NICs that are specifically designed for compatibility with switches
150
and
151
and the protocol being used. This prior art technique is problematic because it requires the use of a specific type of hardware (e.g., a specific type of NIC compatible with a specific type of switch). Thus, this prior art technique is not suitable for different types of hardware (e.g., NICs and switches). In particular, the prior art is not suitable for legacy hardware already present in a network.
Another drawback to this type of prior art technique is that the switch must be designed with the capability to implement the fault tolerance and fail over schemes. Thus, the complexity and the cost of the switch are substantially increased. Even so, the capabilities of the switch are relatively limited, and so the schemes for providing fault tolerance and fail over support are also limited. In addition, the cost of implementing this type of prior art technique is increased by the need to replace or upgrade legacy devices.
Prior art techniques for fault tolerance and fail over support are also not capable of detecting a partial failure of a NIC; that is, for example, they are not capable of detecting a NIC failure if the NIC is not able to properly transmit but continues to receive. These prior art techniques rely on the NIC to notify the server computer system protocols that the NIC is not functioning. However, consider the case in which a particular NIC is receiving and transmitting, but the outgoing data packets are not be received at their destination because of a failure that solely affects that NIC, such as, for example, a loose cable. In this case, the NIC is not aware that data packets it is transmitting are not reaching their destination. Because the NIC continues to receive properly, the NIC believes it is properly performing both of its send and receive functions. The NIC therefore does not notify the server computer system protocols that it is not functioning.
Thus, a disadvantage to the prior art is that some NIC failures are not detected, in particular partial failures, and so the overall reliability and performance of the server computer system and the network are reduced. This disadvantage is compounded because those who are responsible for maintaining the network will also not be aware of the failure and so cannot implement a fix; thus, the server computer system and network can continue to operate indefinitely with reduced reliability and performance. Furthermore, if the failure is detected, it may be necessary to test all of the NICs in order to isolate the failed NIC.
Accordingly, a need exists for a system and method that implement fault tolerance and fail over support wherein the system and method are not limited by the capabilities of a switch. A need also exists for a system and method that satisfy the above need, are switch-independent, and can be used with legacy hardware (e.g., switches and NICs). In addition, a need exists for a system and method that satisfy the above needs, can detect partial NIC failures (such as the inability of the NIC to either send or receive), and can identify which NIC has failed. Furthermore, a need exists for a system and method that satisfy the above needs and quickly accomplishes fail over to a functioning NIC in order to minimize the time during which the communication link between the server computer system and client computer systems is not available.
DISCLOSURE OF THE INVENTION
The present invention provides a system and method that implement fault tolerance and fail over support wherein the system and method are not limited by the capabilities of a switch. The present invention also provides a system and method that satisfy the above need, are switch-independent, and can be used with legacy hardware (e.g., switches and NICs). Furthermore, the present invention provides a system and method that satisfy the above needs, can detect partial NIC failures (such as the inability of the NIC to either send or receive), and can identify which NIC has failed. In addition, the present invention provides a system and method that satisfy the above needs and quickly accomplishes fail over to a functioning NIC in order to minimize the time during which the communication link between the server computer system and client computer systems is not available.
Specifically, in one embodiment, the present invention pertains to a method for detecting a non-functioning network interface card (NIC) in a server computer system adapted to have a plurality of network interface cards coupled thereto and communicatively coupled to client computer systems in a n
Baker Roman G.
Maufer Thomas A.
Nanda Sameer
Vepa RamKrishna
3Com Corporation
Chin Wellington
Duong Frank
Wagner , Murabito & Hao LLP
LandOfFree
Fail over with multiple network interface cards does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Fail over with multiple network interface cards, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Fail over with multiple network interface cards will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3072119