text:
|Publication number
|Publication type
|Application number
|Publication date
|Jun 26, 2001
|Filing date
|Oct 1, 1997
|Priority date
|May 13, 1997
|Fee status
|Publication number
|Carlton G. Amdahl, Dennis H. Smith, Don A. Agneta
|Original Assignee
|Micron Electronics, Inc.
|Export Citation
|BiBTeX, EndNote, RefMan
|Patent Citations (310), Non-Patent Citations (40), Referenced by (104), Classifications (31), Legal Events (6)
|External Links: USPTO, USPTO Assignment, Espacenet
The benefit under 35 U.S.C. � 119(e) of the following U.S. Provisional Application entitled, "Three Bus Server Architecture With A Legacy PCI Bus and Mirrored I/O PCI Buses," as application Ser. No. 60/046,490, filed on May 13, 1997, and U.S. Provisional Application entitled, Means For Allowing Two Or More Network Interface Controller Cards To Appear as One Card To An Operating System," Ser. No. 60/046,491, filed on May 13, 1997, are hereby claimed.
The subject matter of U.S. Application entitled "Means For Allowing Two Or More Network Interface Controller Cards To Appear As One Card To An Operating System," filed on Oct. 1, 1997, application Ser. No. 08/943,379, and is related to this application.
Appendix A, which forms a part of this disclosure, is a list of commonly owned copending U.S. Patent applications. Each one of the applications listed in Appendix A is hereby incorporated herein in its entirety by reference thereto.
Appendix B, which forms part of this disclosure, is a copy of the U.S. provisional patent application filed May 13, 1997, entitled "Three Bus Server Architecture With A Legacy PCI Bus and Mirrored I/O PCI Buses," and assigned application Ser. No. 60/046,490.
Copyright Authorization
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
1. Field of the Invention
The present invention relates to a system for enhancing the performance of a a computational server connected to both data storage devices and networks, and more particularly to a system that provides load balancing and fault tolerance capabilities.
2. Related Art
Personal computers (PCs) have undergone evolutionary changes since the original models based on the Intel 8088 microprocessor, such as the International Business Machine Corporation (IBM) PC and other IBM-compatible machines. As the popularity of PCs have grown, so has the demand for more advanced features and increased capability, reliability and speed. Higher order microprocessors such as the Intel 20286, 30386, 40486, and more recently, the Pentium� series have been developed. The speed of the fastest of these processors, the Pentium� II series is 266 MHz as opposed to the 8 MHz clock speed for the 8088 microprocessor.
Faster bus architectures have been developed to support the higher processor speeds. Modern computer systems typically include one or more processors coupled through a system bus to main memory. The system bus also typically couples to a high bandwidth expansion bus, such as the Peripheral Component Interconnect (PCI) bus which operates at 33 or 66 MHz. High speed devices such as small computer systems interface (SCSI) adapters, network interface cards (NIC), video adapters, etc. can be coupled to a PCI bus. An older type low bandwidth bus such as the Industry Standard Architecture (ISA), also referred to as the AT bus, is generally coupled to the system bus as well. This bus operates at 6 MHz. To the ISA bus are attached various low speed devices such as keyboard, monitor, Basic Input/Output System (BIOS) and parallel and communications ports. These devices are known as legacy devices because they trace their lineage, their legacy, back to the initial PC architecture introduced by IBM in 1982:
With the enhanced processor and bus speeds the PC now is utilized to perform as a server, and to provide high speed data transfers between, for example, a network and a storage device. There are, however, several constraints inherent in the current PC architecture, which limit its performance as a server. First, the legacy devices and the high speed devices compete for limited bus bandwidth, and thereby degrade system performance. Second, whereas the original PC operated as a standalone and did not affect other PCs when there was a system failure, the PC/Server must be able to maintain operation despite failure of individual components. The PC/Server must, in other words, be fault-tolerant, i.e. able to maintain operation despite the failure of individual components.
What is needed is a way to move the PC from a standalone model to a server model. In doing so, the inherant conflict of high and low bandwidth buses must be resolved, fault-tolerance must be provided, and throughput should be enhanced.
An embodiment of the present invention provides a fault-tolerant computer system with a processor and a memory, connected to a system bus. The system includes at least two mirrored circuits, at least two mirrored input/output devices, a detection means and a re-route means. The two mirrored circuits each include an interface to the system bus, and an input/output interface. The input/output interface of each of the mirrored circuits is connected to one of the two mirrored input/output devices. Detection means detect a load imbalance in the data transfer between the system bus and either one of the two mirrored IO devices. In response the re-route means, re-routes the data transfer between the system bus and the other one of the two mirrored IO devices.
In another embodiment, a fault-tolerant computer system includes a first, second and third input/output (IO) bus, legacy devices, and two IO devices. The first IO bus is connected to the system bus. The legacy devices are connected to the first IO bus. The second and third IO buses are each connected to the system bus. The IO devices are each connected to a corresponding one of the second and third IO buses.
An other embodiment of the invention can be characterized as an apparatus for transferring data between at least one transport protocol stack and a plurality of network adapters coupled to a computer network that supports recovery from network adapter and a connection failure. The apparatus includes a first interface bound to at least one transport protocol stack and a plurality of network adapters coupled to a computer network that supports recovery from network adapter and connection failure. The apparatus includes a first interface bound to at least one transport protocol stack. It also includes a second interface bound to the plurality of network adapters, as well as a mechanism coupled to the first interface and the second interface that receives a first MAC-level packet from a transport protocol stack through the first interface and forwards the first MAC-level packet through the second interface to a network adapter in a protocol independent matter. The apparatus also includes a mechanism coupled to the first interface and the second interface that receives the second packet from a network adapter through the second interface and forwards the second packet through the first interface to a transport protocol stack.
According to another aspect of the present invention, the apparatus can function as a prescan protocol stack for examining packets flowing between protocol stacks and drivers.
FIG. 1 is a block diagram illustrating one embodiment of a server computer and client computers linked in a network through network interface cards.
FIG. 2 is a flow diagram illustrating one embodiment of the overall process of detecting faulty network interface cards and automatically switching from a primary network interface card to a secondary network interface card.
FIG. 3 is a block diagram illustrating an implementation of software modules running within a server computer under a Novell Netware network operating system.
FIG. 4 is a block diagram illustrating an implementation of software modules running within a server computer under a Microsoft� Windows� NT network operating system.
FIG. 5 is a block diagram illustrating one embodiment of the structure of a probe packet for an Ethernet network system.
FIG. 6 is a block diagram illustrating one embodiment of the structure of a probe packet for a FDDI or Token Ring network system.
FIG. 7 is a flow diagram illustrating one embodiment of a process for determining whether a network interface adapter has failed.
FIG. 8 is a block diagram of one embodiment of a MAC level packet, including a header, destination address and contents.
FIG. 9 is a flow diagram illustrating one embodiment of the steps involved in moving data packets between network interface cards and protocol.
FIG. 10 is a flow diagram illustrating one embodiment of the steps involved in load sharing data packets across a plurality of network interface cards.
FIG. 11 is a hardware block diagram of a server with a legacy backbone 46 and a mirrored block 48.
FIG. 12 shows an embodiment of the dual I/O buses with redundant storage links.
FIG. 13 show the dual I/O buses with redundant network links.
FIGS. 14A-B shows an embodiment of the dual I/O buses of a computer system with bridges and canisters which support a Hot-Add and Hot-Swap.
FIG. 15 is a map describing the distribution of address spaces to busses in a hierarchical, multi-PCI bus computer system shown in FIGS. 14A-Ba.
The present invention includes a system providing failure detection and re-routing of network packets in a computer having multiple network interface cards (NICs) connected as groups (MULTISPAN groups) each to a common network segment. In addition, embodiments of the invention include load sharing to distribute network packet traffic across the NICs in a group. Further, the present invention may provide this benefit to all traffic regardless of the network protocol used to route the traffic (i.e., in a protocol independent manner).
Fault detection and recovery is accomplished by "MULTISPAN", a process operating within the system. For each group of NICs, if there is a failure virtually on any component related to network traffic, the MULTISPAN process detects the interruption of the data flow and determines which NIC is no longer working. MULTISPAN directs traffic through only the working NICs until the failed NIC is again able to send and receive traffic reliably. Restoring a NIC to reliable operation may involve such steps as replacing a failed NIC (in a computer which supports the hot replacement of failed components), reconnecting or replacing a cable, replacing a failed network switch or router. By placing each NIC in the server on a separate path to the network, MULTISPAN will normally keep the system running until repairs can be accomplished. Being able to schedule repairs decreases cost of owning and operating the computer system.
The MULTISPAN system can be implemented in many different forms, as discussed below. Programming languages such as C, C++, Cobol, Fortran, Basic or any other conventional language can be employed to provide the functions of the MULTISPAN system. In addition, software related to the MULTISPAN system can be stored within many types of programmed storage devices. A programmed storage device can be a Random Access Memory, Read-Only Memory, floppy disk, hard disk, CD-ROM or the like.
In one embodiment, the present invention identifies one NIC, called the primary, by which the entire group is identified. Some operating systems disallow more than a single NIC on a single network segment. For such operating systems, this embodiment uses the primary to represent the entire group to the operating system. The remaining NICs in the group are hidden from the operating system.
In one embodiment of the invention, network failures are detected by a process of sending out "probe" packets with in a MultiSpan group from primary NIC to secondary NIC(s) and vice versa. If the probe packet fails to arrive at the target NIC, the failing path is determined and recovery procedure is performed. The MULTISPAN process confirms the source NIC that has failed by repeatedly sending packets to every other NIC in the group until, by process of elimination, the failing NIC is determined. If the failing NIC is a primary NIC, the MULTISPAN process stops routing network traffic through this unreachable/failed NIC. Traffic is thereafter directed through one of the remaining NIC(s), which is designated as the new primary (this process of designating a new primary when the current one fails is called fail-over). MULTISPAN continues to attempt to send probe packets to and from the failing NIC and, should probe packets once again be successfully delivered, the NIC is returned to service as a secondary.
In an embodiment of the present invention, the traffic load for a network segment is shared among all NICs in the group connected to the segment. Traffic inbound to the server from the network segment may arrive through any NIC in the group, and be properly delivered by MULTISPAN to the operating system. In some situations, all inbound traffic arrives through a single NIC (usually the primary), while in others traffic may arrive through all NICs at once. Traffic outbound from the server to the network segment is directed through some or all NICs in the group according to some algorithm which may vary from one embodiment to another, or may vary within one embodiment from one group to another.
FIG. 1 is an illustration of a server computer 10 linked through a network backbone 12 to client computers 14 and 16. The server computer 10 can be any well-known personal computer such as those based on an Intel microprocessor, Motorola microprocessor, Cyrix microprocessor or Alpha microprocessor. Intel microprocessors such as the Pentium�, Pentium� Pro and Pentium� II are well-known within the art. The server computer 10 includes a group of network interface cards (NICs) 18, 20, 22 which provide communications between the server computer 10 and the network backbone 12. Similarly, the client computer 14 includes a network interface card 24 and the client computer 16 includes a network interface card 26 for communicating with the network backbone 12. The network backbone 12 may be a cable such as a 10B2 Thin Ethernet cable, an Ethernet 10BT workgroup hub such as a 3Com Hub 8/TPC, or several interconnected switches or routers 28, 30, 32 such as a Cisco Catalyst 500, as shown in FIG. 1.
As will be explained in more detail below, the client computers 14 and 16 make requests for information from the server computer 10 through the network backbone 12. Under normal circumstances, the requests made by the client computers are acknowledged through the primary network interface card 18 to the server computer 10. However, if the primary network interface card 18, or cable 34 or switch or router 28 fails, the embodiments of the present invention provide a mechanism for routing network requests through one of the secondary network interface cards 20 or 22. The re-routing of network requests is transparent to the client computer 14 or 16.
FIG. 2 depicts one embodiment of the overall process 45 of detecting errors for NICs located in a MultiSpan group. The process 45 begins at a start state 48 and then moves to process 49 wherein a MULTISPAN group is created. During process 49, a user identifies the NICs to be grouped and issues a command to the MULTISPAN system to create a group. In one embodiment, the command is issued through a command prompt. In another embodiment, the command is issued through a management application which may be remote from or local to the computer system 10, and directed to the present invention via the simple network management protocol (SNMP) and associated SNMP agent software. If there is an error, the user is notified that there is a failure in creating the group. Otherwise, the user is returned with a prompt indicating that the MULTISPAN group was created successfully. The binding process will be discussed in more detail below. The MULTISPAN process uses the user-supplied information to associate all NICs in a particular group together and with their primary NIC.
The process 45 then moves to state 50 wherein the first MultiSpan group is retrieved. Proceeding to state 52, the first NIC in the current group is retrieved. At process state 54 the first NIC is analyzed to determine whether it is functioning properly, or is failing. The process 45 then moves to decision state 56 to determine whether any errors were detected. If a failure was detected at the decision state 56 for this NIC, the process 45 proceeds to state 58, wherein the NIC is disabled from the MULTISPAN group. The process 45 then proceeds to decision state 60 to determine whether the disabled NIC was a primary NIC. If a determination is made at state 60 that the failed NIC is a primary, the process 45 moves to process state 62 and enables the secondary NIC as a primary. The process 45 then moves to decision state 64 to determine whether the current NIC is the last NIC in the MULTISPAN group. Similarly, if a determination is made at the decision state 56 that there were no errors, the process 45 also moves to decision state 64.
If a determination is made at the decision state 64 that there are more NICs in this MULTISPAN group, then process 45 moves to state 66 to select the next NIC to analyze. The process 45 then returns to process state 54 to analyze the newly selected NIC for errors.
If a determination is made at the decision state 64 that there are no more NICs in the current MULTISPAN group, the process 45 proceeds to decision state 68 to check whether this was the last group. If a determination is made that this is not the last group, the process 45 moves to process state 70 and selects the next group. The process 45 then returns to state 52 to begin analyzing the group's NICs. If a determination is made at the decision state 68 that this is the last group, the process 45 returns to state 50 to begin checking the first group once again.
Novell Netware Implementation
Referring now to FIG. 3, an overview of the software modules running within the server computer 10 is illustrated. In the implementation described below, the server computer 10 is running under the Novell Netware operating system. As shown, a protocol stack 100 includes a first data packet 102 and a second data packet 104. In this figure, the protocol stack is the IPX (InternetNetwork Packet Exchange) protocol but could include TCP/IP or NETBEUI or any other network packet protocols in combinations for transmitting data across a network. As is known, generally client computers request data from server computers by attempting to read particular files within the server computer. In order for the client computers and server computer 10 to communicate across cables, the data is broken into a series of data packets. These data packets include network routing information and small portions of the requested data. The network packets are then routed from the server computer to the requesting client computer and thereafter rebuilt into the requested data file.
As is known, the link support layer (LSL) is the interface between drivers and protocol stacks within the Novell NetWare operating system. More information on the link support layer 112 and prescan drivers can be found in the Novell LAN Developer Guide (Novell Corporation, Orem Utah).
The main objectives embodiments of the MULTISPAN processes are (1) to load share LAN traffic among NICs in a group, and (2) to perform a transparent fail-over when a primary adapter in a group fails. These features may be achieved essentially without modification to the transport protocol portions of the packets. Instead, the features are achieved through system services provided for interfacing with LAN drivers and other Netware system modules like the Media Specific Module (MSM), Topology Specific Module (TSM) and Link Support Layer (LSL). The MULTISPAN process may be a totally media-dependent intermediate module.
Once drivers for primary and secondary NICs are loaded, a multispan group can be created by issuing MSP BIND statement, specifying the slot numbers of primary and secondary adapters. If there are any protocol stacks bound to the secondary NIC, the MULTISPAN process displays an error message and does not create a MULTISPAN group.
The user can optionally specify more than one secondary NIC when creating a group. Typically this is done to allow load sharing of the outbound LAN traffic across all the NMCs. If any LAN drivers had been loaded before loading MSP.NLM, then MSP BIND command does not create any MULTISPAN groups and displays the error message "Error locating DCT Address in Internal Table". Thus, the MSP.NLM module should be loaded before any LAN drivers. As discussed above, MSP.NLM module should normally be loaded under Netware through the STARTUP.NCF file.
The MULTISPAN system allows users to configure LAN cards of same topology, but different kind (example Intel Smart card and Intel Pro 100B card) into a MULTISPAN group. For example, issuing the following commands will load several Ethernet cards and bind them into a MULTISPAN group.
load e100b.lan slot=10001 frame=ethernet—802.2 name=primary—8022
load e100b.lan slot=10001 frame=ethernet—802.3 name=primary—8023
load e100b.lan slot=10002 frame=ethernet—802.2 name=secondary—8022
load e100b.lan slot=10002 frame=ethernet—802.3 name=secondary—8023
bind ipx to primary—8022 net=f001
bind ipx to primary—8023 net=f002
The MSP Bind command can also be issued specifying logical names associated with the primary and secondary NICs. For example:
MSP NAMEBIND primary—8022 secondary—8022
Once the MSP BIND or MSP NAMEBIND commands have been issued, a MULTISPAN group is created for all logical frame types supported by the NIC. In addition, the probing mechanism becomes active for the current base frame. In the case of above example group gets created for frame type of ETHERNET—802.2 and ETHERNET—802.3. When a group gets created, MULTISPAN performs "Link Intergrity" check to make sure that all the NICs in the group are accessable from one to another by using the same probing mechanism described earlier. If the check fails the user is displayed with appropriate error messages.
The MULTISPAN NLM gains control over the network activity by registering a prescan protocol stack for sends and receives. The purpose of a prescan protocol stack is to provide the ability to examine the packets flowing between protocol stacks and drivers. MULTISPAN also intercepts the MLID registration process by patching the LSL portion of server code during the software load time. In Netware, protocol stacks send packets via LSL using a buffer known as ECBs (Event Control Block), which not only contains the address of the packet payload and its length but also contains information such as about which NIC to use and what frame type to use on the medium. This information is helps LSL in deciding the driver interface it needs to correspond to, in sending a packet. When LSL corresponds to MULTISPAN PreScan stack, it uses the same data structure to pass in information.
As illustrated in FIG. 3, a packet 102 is sent from the IPX protocol stack 100 via LSL 112. The LSL checks the registered pre-scan stack and calls the MULTISPAN PreScan send handler routine. The MULTISPAN PRESCAN process 110 determines the NIC through which the packet is to be sent.
Once the packets 102 and 104 have been analyzed by the MULTISPAN prescan module 110, they are output to their target network interface driver 120 and 122 respectively, and thereafter sent to the network backbone 12. By way of illustration, the packet 104 could be routed through the MULTISPAN prescan module 110 to a secondary network interface card driver 122 and thereafter out to the network backbone 12. It should be noted that during normal operations, Novell NetWare would only allow packets to flow through a single network interface card. MULTISPAN presents the primary NIC of each group as this single adapter, transparently applying its load sharing and failure recovery functions to the group.
Thus, data packet 104 can be sent to the LSL 112 with information to route it through the primary driver 120 to a NIC 124. However, in order to distribute the load, the MULTISPAN prescan module 110 intercepts the packet 104 and alters its destination so that it flows through the secondary driver module 122 to the NIC 126 and out to the network backbone 12.
By the same mechanism, if the primary driver 120 or primary NIC 124 fails, the MULTISPAN prescan module 110 can route the packet 102 into the secondary driver 122 and out to the NIC 126. By determining the destination of every packet coming through the LSL, the MULTISPAN prescan module 110 can completely control the ultimate destination of each packet.
During the load process, the MULTISPAN module patches the server code for the NetWare functions LSLRegisterMLIDRTag() and LSLDeRegisterMLID(). In addition, the MULTISPAN module allocates enough memory needed for maintaining information pertinent to logical boards such as the address of the DriverConfigTable, Multicast address list, and original DriverControlEntry. Initialization related to generating NetWare Alerts is done at this point and an AESCalIBack procedure is scheduled for managing the probing functionality.
After loading the MULTISPAN.NLM, the user can configure the system to load drivers for both the primary NIC and one or more secondary NICs using the INETCFG command or by manually editing AUTOEXEC.NCF or manually loading drivers at the system console. The user can also choose the appropriate protocol stack to bind with for every instance of the primary NIC. Once this process is done, the MULTISPAN BIND command can be issued to associate NICs together into a group, and designate a primary adapter for the group.
As part of initialization, LAN drivers typically make call to register their instance with LSL via LSLRegisterMLIDRTag. This call manages all information pertinent to an occurrence of a logical board and assigns the caller with next logical board available. When the LSLRegisterMLIDRTag function is called by the NetWare drivers (MLIDs), control jumps to the MULTISPAN code as a result of a patch in the LSL made by the MULTISPAN module while loading. The MULTISPAN system saves the addresses of certain MLID data structures and maintains internal tables for every logical board. This information is passed to the real target of the MLID's call.
This technique allows embodiments of the MULTISPAN system to intercept certain dialogs between the MLID and the LSL or the protocol stacks for such purposes as establishing or changing multicast address lists and the DriverConfig Table. When a fail-over takes place, the MULTISPAN system can retrieve the multicast list from the local internal table and send a multicast update call to the switched-over NIC.
In addition to intercepting the control handler, MULTISPAN also intercepts the DriverReset call. When the DriverReset call fails for some reason (e.g., NIC is powered off during hot swap), MSM usually removes the instance of that driver from memory and makes it impossible to activate the driver for that particular instance. By intercepting the reset call, MULTISPAN can tell MSM that reset was successful but generate an NetWare Alert for failure of a particular adapter. Since MULTISPAN knows which NIC is active and which is not, it ensures that there are no side effects in doing this kind of interception.
Once the MULTISPAN BIND command is issued, the bind procedure locates the appropriate logical boards corresponding to the arguments specified and creates a MULTISPAN group for all logical frames that the NIC currently supports. The primary NIC is specified first, followed by one or more secondary NICs. The MULTISPAN process forms a group only if there is a match for frame-type across all NICs specified. Note that the primary NIC should have a protocol stack bound to it and that a secondaries should not have any protocol stack bound to them.
Once a MULTISPAN group of NICs is created, the probing module starts sending probe packets from the primary NIC to all secondary NICs and from all secondary NICs to the primary NIC to monitor the status of the network link. The structure of a the payload portion of a probe packet is illustrated by the data structure definition below:
struct HEART_BEAT {
LONG signature; //LONG value of 'NMSP'
LONG seqNo; // sequence number of the probe packet sent.
LONG pSource; // pointer to structure pertaining to the source board
LONG pDestn; // pointer to structure pertaining to the destination board
struct IPX_HEADER {
WORD checkSum; //0xFFFF always
WORD packetLength; //size of IPX_HEADER+size of HEARTBEAT
BYTE transportControl; //zero,not used
BYTE packetType; //IPX_PACKET
BYTE destinationNetwork[4]; //zero
BYTE destinationNode[6]; //corresponds to node address of destination board.
WORD destSocket; //value returned by IPXOpenSocket() call.
BYTE sourceNetwork[4]; //zero
BYTE sourceNode[6]; //corresponds to node address of source board
WORD sourceSocket; //value returned by IPXOpenSocketo() call.
struct PROBE_PACKET {
IPX_HEADER ipxHeader;
HEART_BEAT heartBeat;
If any packets are not received, MULTISPAN system re-transmits the probe packet for a specified number of times. If there is a repeated failure, the MULTISPAN system determines which NIC failed by analyzing which packets were received and which were not, and removes the failing board from the bound group and deactivates the adapter by placing it in a wait mode. The MULTISPAN system thereafter monitors the deactivated board to determine if data packet reception begins to occur again on the deactivated board. If there is no packet reception for a specified time, MULTISPAN marks the board as dead. If the primary NIC is marked as dead, and there is at least one active secondary, then MULTISPAN does switch-over by causing a secondary NIC to be the primary. This is accomplished by shutting the board, changing the node address of the secondary NIC to that of primary NIC in the Driver Configuration Table (DCT) and then resetting the NIC. In addition, the multicast table of the original primary NIC is transferred to the switched-over primary and promiscuous mode is turned on if it was originally active for the primary.
In one embodiment, the MULTISPAN system also resets the source node address field in TCBs (Transmission Control Blocks) maintained by TSM for both failed and switch-over adapter. This is done to ensure that all load sharing NICs send packets with their current address, not the original address which was identified during load time thus eliminating the confusion with certain protocols (such as Ethertalk), which direct the requests to the node from which a reply was received.
Once the MULTISPAN system detects data packet reception on the old primary NIC, it activates the card to be a part of the group. The reactivated card then becomes a new secondary. If load sharing is enabled, the MULTISPAN system begins to use the board to share the outbound traffic. The fail-over process works the same way on this new configuration as before.
In order to load share the outbound traffic, MULTISPAN requires at least one secondary in a group. This feature can be enabled or disabled during runtime through the MULTISPAN LOAD SHARING command, which toggles this mode. When a packet is sent from the protocol stack 100 to the primary NIC 124 (the board which is known to the protocol stack), the MULTISPAN system intercepts the request and selects the next active board from the group on which the packet could be sent and changes the board number to the one selected. In one embodiment, the algorithm is based on a round-robin mechanism where every NIC in the group gets a turn to send packets. If a selected board in the bound group is marked "DISABLED", the MULTISPAN system bypasses that board and selects the next active board in the group. In another embodiment, the algorithm used makes a calculation based on the destination address in order to make routing of outgoing packets predictable to switches or routers connected to the group's NICs.
During load sharing, the MULTISPAN system changes the SendCompleteHandler in the Event Control Block (ECB) of the data packet to point to MULTISPAN primary NIC SendCompleteHandler. The purpose of this is to restore the original board number when the ECBs get handed back to the protocol stack through the LSL. This also fixes the problem when the system is running with Novell's IPXRTR product, wherein the Netware Core Protocol (NCP) does not recognize SendCompletes on the secondary NIC to which the protocol stacks are not bound.
Although the MULTISPAN system has been described above in relation to a Novell Netware implementation, the system is not so limited. For example, the MULTISPAN process can be implemented within other network operating systems such as Microsoft Windows NT, as discussed below.
Windows NT Implementation
FIG. 4 is a block diagram illustrating some of the major functional components of a Microsoft� Windows� NT system for transferring data between a plurality of protocol stacks 500, 502 and 504 and a plurality of NICs 505 a,b in accordance with an aspect of the present invention. The protocol stacks include TCP/IP protocol stack 500, IPX/SPX (Synchronous Packet Exchange) protocol stack 502 and net BEUI protocol stack 504. These protocol stacks connect to NDIS 506, which is part of the Microsoft� Windows� NT operating system. NDIS 506 connects to NICs 18, 20 & 22 and additionally connects to a MULTISPAN system 508, which performs load sharing and fail-over functions.
A variety of references and device driver development kits are available from Microsoft describing the LAN driver model, NDIS, and how they interact. These will be familiar to anyone of ordinary skill in writing such drivers for Windows NT. The MULTISPAN system 508 is an NDIS 4.0 intermediate driver. FIG. 4 illustrates the relationship between the NDIS wrapper, transport protocols, NIC driver, and MULTISPAN driver in a Windows� NT system.
When the MULTISPAN driver 508 loads, it registers itself as an NDIS 4.0 intermediate driver. It creates a virtual adapter 510 on its upper edge for each group of NICs. The virtual adapter 510 binds to the transport protocols 500, 502 and 504 (e.g., TCP/IP, IPX/SPX). The lower edge 512 of the MULTISPAN driver 508 behaves like a transport protocol and binds to network interface cards 505 a,b. When, for example, the TCP/IP protocol stack 500 sends out packets, they are intercepted by the MULTISPAN driver 508 first. The MULTISPAN driver 508 then sends them to the appropriate network adapter 505 a or 505 b. All the packets received by the NICs are passed to the bound MULTISPAN driver 508. The MULTISPAN driver then decides whether it should forward the packets to the transport protocols, depending on the state of the adapter.
The MULTISPAN driver is also responsible for verifying the availability of bound NICs. It detects adapter failures by periodically monitoring the activity of the NICs, as will be discussed in more detail below. If an adapter has failed, the MULTISPAN driver 508 disables the adapter and records it in the event log. If the failed NIC was a primary adapter, the MULTISPAN driver selects a secondary NIC to become the primary adapter.
Since Windows� NT does not allow the network address of a NIC to be changed dynamically, all the NICs bound to the MULTISPAN driver are configured to the same physical address when they are loaded. When the primary adapter fails, the MULTISPAN driver disables it and starts sending and receiving packets through a secondary adapter.
The MULTISPAN driver 508 continuously tracks the state of bound network interface cards. There are three different states for network interface cards. The "IN_USE" state means that the adapter is the primary adapter. All packets will be sent and received through this adapter when the load sharing feature is disabled. When load sharing is enabled, packets are sent out from all available NICs. The "READY" state means the adapter is in standby mode, but is operating correctly. When the primary adapter fails, one of the adapters in the "READY" state is changed to the "IN_USE" state and begins to send and receive packets. When the adapter cannot send or receive packets, it is set to a "DISABLED" state. The MULTISPAN driver sends packets out from the primary adapter (the NIC in "IN USE" state). It simply passes packets received from the primary adapter up to the protocols and discards packets received from all the other adapters.
The MULTISPAN driver 508 continuously monitors the activity of any bound adapters. In most LAN segments, "broadcast" packets are periodically sent out by different machines. All the NICs attached to the LAN segment should receive these packets. Therefore, if a network adapter has not received any packets for an extended period of time, it might not be functioning correctly. The MULTISPAN driver 508 uses this information to determine if the bound network interface card is functioning correctly. For those LAN segments where no stations send out broadcast packets, the MULTISPAN driver sends out probe packets, as discussed above in the Novell Netware implementation. All the NICs should receive probe packets, since they are broadcast packets. A NIC will be disabled if it does not receive these probe packets.
When the network adapter is in an "IN_USE" state, and its receiver idle time exceeds a pre-set threshold, that adapter might not be operating correctly. The Receiver idle time for a NIC is the time that has elapsed since the last packet was received by the NIC. The MULTISPAN driver then scans through all the adapters in the "READY" state. If the receiver idle time of an adapter in a "READY" state is shorter than that of the primary adapter, the MULTISPAN driver disables the primary adapter by setting it to the "DISABLED" state and changes the adapter in "READY" state to the "IN_USE" state. This adapter then becomes the primary adapter. The MULTISPAN system will now begin using the new network adapter to send and receive packets.
If the adapter is in a "READY" state and has not received any packets for a period of time, the MULTISPAN driver places the adapter in a "DISABLED" state. If the adapter is fixed and starts receiving packets, it is changed to the "READY" state.
The MULTISPAN driver uses an adapter packet filter to reduce the overhead introduced by the secondary adapters the MULTISPAN driver sets the packet filter depending on the state of the adapter. When the adapter is in the "IN_USE" state, the filter is set by transport protocols. Normally, transport protocols set the filter to receive broadcast, multicast and directed packets. When the adapter is in the "READY" state, the packet filter is set to receive only multicast and broadcast packets. This should minimize the impact on performance. An adapter in the "DISABLED" state will receive all broadcast multicast and directed packets. Once the adapter is replaced or the cable is reconnected so that the adapter can again receive packets, it is switched to the "READY" state and its packet filter is set accordingly.
Windows NT uses a registry database is to store configuration information. Each driver in Windows NT has at least one entry in the following subkey:
The drivers can store configurable parameter values under the driver's subkey. NDIS drivers also store binding information inside the subkey. For a normal NDIS NIC driver, one entry is created for the NDIS miniport interface and one subkey is created for each adapter that is installed.
As discussed above, MULTISPAN is an NDIS intermediate driver which has a miniport interface on its upper edge and a transport interface on its lower edge. Each interface needs a separate subkey to describe it.
After installing the MULTISPAN driver, the installation program (oemsetup.inf) creates
for its NDIS transport interface and
for its NDIS miniport interface. It also creates
for each virtual adapter installed, where # is the adapter number assigned by Windows NT. For each NIC bound to the MULTISPAN driver, a Span subkey is created under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NETCARD#\ Parameters.
to configure how the NIC is bound to the MULTISPAN virtual adapter.
There are two entries in the Parameters subkey. "Connect" stores the name of the virtual MULTISPAN adapter to which the NIC is connected. All network interface cards belonging to the same group will have the same Connect value. "Number" stores the sequence number of the adapter. Number zero means that this adapter is the primary adapter of the adapter group. For example, the registry might resemble the following:
Connect: REG_SZ: mspa3
Number: REG_DWORD: 0x1
The installation script also creates a Network Address under the Parameters subkey of all bound adapters. This stores the actual MAC address used for the adapter group.
The MULTISPAN driver stores configurable parameters in
The following are values in the subkey of the REG_DWORD data type CheckTime, DisableTime, IdleTime, ProbeTime, LoadBalance. Network Address is a value in the subkey of the REG_SZ type. These values are described in detail in the following section.
There are five different parameters in the Windows NT registry which control the behavior of the MULTISPAN driver. The user can set these parameters based on the operational environment.
Check Time determines how often the MULTISPAN driver checks if the adapter is still alive. The recommended value is 1000 milliseconds (1 second). The maximum value is 1000 seconds in some embodiments.
Probe Time determines if the MULTISPAN driver should send out a probe packet if the bound adapter has not received a packet for the specified period of time. For example, if the Probe Time is set to 2000 milliseconds, the MULTISPAN driver will send out a probe packet if the adapter has not received any packets during a two second interval. If the Probe Time is set to 0, no probe packet will be sent out. The Probe Time value should be either greater than or equal to the Check Time, unless it is zero. The default value is 3000 milliseconds.
Disable Time determines when the MULTISPAN driver is to disable a bound adapter. If the adapter has not received any packets in the specified time, the MULTISPAN driver disables the adapter. The default value is 8000 milliseconds.
Idle Time determines when the MULTISPAN driver should switch to the secondary adapter if the primary adapter has not received any packets within the specified time period. The Idle Time value should be greater than the Check Time and Probe Time values. The default value is 4000 milliseconds.
FIG. 5 illustrates the structure of a probe packet for an Ethernet system in accordance with an aspect of the present invention. The packet includes a number of fields, including a destination address 700, source address 702, packet type 704 and adapter ID 706.
Since Windows NT does not allow the network address of a NIC to be changed dynamically, all the NICs that are bound to the same MULTISPAN virtual adapter are configured to the same physical address when they are loaded, which is called the MULTISPAN Virtual Network Address. Ethernet hardware addresses are 48 bits, expressed as 12 hexadecimal digits. The first 2 digits have to be 02 to represent the locally administrated address. It is recommended that 00 be used as the last two digits to support load sharing. The MULTISPAN Virtual Network Address should appear as follows:
where XXXXXXXX are arbitrary hexadecimal numbers. This address has to be unique among single Ethernet segments.
FIG. 6 illustrates the structure of a probe packet for FDDI and token ring networks. The probe packet illustrated in FIG. 6 includes Access Control (ACS CTL) 800, Frame Control (FRM CTL) 802, destination address 804, source address 806, Destination Service Access Point (DSAP) 808, Source Service Access Point (SSAP) 810, CTL 812, protocol 814, packet type 816 and adapter ID 818.
Since an FDDI and Token-Ring networks do not allow two adapters with the same network address to coexist on the same network segment, the same mechanism described in the Ethernet section cannot be used to handle the fail-over process. The MULTISPAN driver therefore uses special FDDI and Token-Ring NIC drivers to provide the mechanism for resetting the NIC and changing the network address. On startup, only the primary adapter's address is overwritten to the MULTISPAN Virtual Network Address. All the other adapters use the address which is generated from Virtual Network Address and the adapter number assigned by NT. When the primary card has failed, MULTISPAN resets and changes the address of the primary adapter to the address generated from Virtual Network Address and its adapter number; it then resets and changes the network address of the secondary adapter to the MULTISPAN Virtual Network Address and uses that card as the primary adapter.
FDDI network addresses are 48 bits long, expressed as 12 hexadecimal digits. The first 2 digits have to be 02 to represent the address of the locally administrated station. It is recommended that 00 be used as the last two digits to support load sharing. The MULTISPAN Virtual Network Address should appear as follows:
where XXXXXXXX are arbitrary hexadecimal numbers. This address must be unique within a single ring segment.
FIG. 7 is a flowchart illustrating one embodiment of a method for determining whether a network adapter has failed. The network adapters are divided into a primary adapter and a plurality of secondary adapters. The method illustrated in FIG. 7 determines whether the primary adapter has failed. The method begins at state 900 which is a start state.
The system next advances to state 910 in which a packet is sent from the primary to a secondary adapter. In one embodiment, the primary sends packets to all of the secondary adapters in sequence. Next, the system advances to state 912. In state 912, the system attempts to receive a packet from the secondary adapter. The system next advances to state 914. At state 914, the system sends a packet from a secondary adapter to the primary adapter. In one embodiment, all of the secondary adapters send a packet to the primary adapter. The system next advances to state 916. At state 916, the system attempts to receive a packet from the primary adapter. The system next advances to state 918.
At state 918, the system determines whether a packet has not been received from the primary adapter or if the packet has not been received from the secondary adapter. If no packets have been received from either the primary or secondary adapter, the system assumes that the primary adapter has failed. The system then advances to step 924. At step 924, the system converts a secondary adapter to a replacement primary adapter. The system then proceeds to state 922, which is an end state. At state 918, if a packet had been received from either the primary or the secondary adapter, then the system assumes that the primary adapter has not failed and it proceeds to the end state 922.
One embodiment of the present invention operates at the MAC level and lower, thus avoiding the complexity of providing software support for higher layer protocols. As indicated in FIG. 8, the structure of a MAC-level packet 1005 illustrated. These packets include a header with a destination address 1010 and protocol-level header 1020 for storing protocol information for protocols such as TCP/IP, IPX/SPX and NET BEUI. In addition, the MAC packet 1005 can include contents 1025.
FIG. 9 is a flow chart illustrating some of the steps involved in receiving packets through the NICs using the apparatus illustrated in FIGS. 3 and 4 in accordance with one embodiment of the present invention. The process starts at start 1100 which is a start state. The system next proceeds to state 1110 when a NIC of a group receives a first MAC-level packet from the network. The system next proceeds to decision state 1112, wherein the MULTISPAN system determines whether the packet is a probe packet. If the packet is a probe packet, then the system moves to state 1120 and updates the state of the NIC to indicate that the probe packet has been sent correctly. The system then moves to state 1130 wherein the packet is dismissed and the process terminates at end state 1150 without forwarding the packet to any protocol stack.
If a decision is made at decision state 1112 that the packet is not a probe packet, then the system moves to decision state 1114 to determine whether the packet is from a primary NIC. If so, then the system proceeds to state 1140, where the packet is passed to the protocol stack. Thus, the normal packet receive path is from state 1110 to 1112 to 1114 to 1140 then to 1150, the end state.
If a determination is made at decision state 1114 that the packet is from a secondary (not a primary) NIC, then system proceeds to a decision state 1116 to decide whether the packet is a multicast or broadcast packet. If the packet is a multicast or broadcast packet, then the system assumes that the same packet was received by all NICs in the group, and the system proceeds to state 1130 to discard the packet. However, if the packet is not a broadcast or multicast packet at decision state 116, the system proceeds to state 1140 and passes the packet to the protocol stack for processing. In some embodiments, state 1140 will make all packets forwarded to the protocol stack look like they arrived through the primary NIC.
FIG. 10 is a flow chart illustrating some of the steps involved in load sharing packets across a plurality of NICs in accordance with one embodiment of the present invention. The process starts at a start state 1200 and then moves to state 1210 wherein the system receives a MAC-level packet from a protocol stack. The system next proceeds to state 1220 selects a NIC to send out packets from the plurality of NICs according to an algorithm specific to one embodiment of the invention. Some embodiments will choose a NIC that is less loaded than at least one other NIC in the plurality of NICs. The system then proceeds to state 1230 and routes the MAC-level packet to the NIC selected at state 1220. The system the terminates at an end state 1240.
Used for creating multispan group by specifying slot numbers (port number if slot is NULL) of primary and secondary NICs.
: MSP BIND PrimarySlotNo SecondarySlotNo
MSP BIND PrimaryPortNo SecondaryPortNo
MSP BIND 0x5a 0x6a (used when slot number is NULL)
: None
For all successful creation of the MULTISPAN group, the MULTISPAN system displays "Group has been created for Primary Slot # xxxx and Frame_Type:yyyy". If there is a group already present, MSP displays error message "Group Already Present". MSP displays "failed to create a group", if multispan is unable to create group for at least one frame type supported by the NIC.
Error Conditions:
1. No valid primary or secondary NIC
2. primary does not have any bound protocol stack
3. secondary has a protocol stack bound
4. Link Intergrity check failed
Used for deleting a multispan group from the list. To delete a group, the user specifies the slot number associated with primary NIC (port in case slot number is NULL). The group gets deleted automatically if LAN driver for that group is unloaded.
: MSP UNBIND PrimarySlotNo
: None
If successful, MSP displays "Cleaning Up resources for group associated with Primary Slot #xxxx" for all frame types supported by NIC.
Used for setting probe send timeout value. This command changes the values of MSP_PROBE_SEND_TIMEOUT variable for any given group, if there is a valid argument.
MSP waits for MSP_PROBE_SEND_TIMEOUT seconds, when LSL has been requested to sendprobe packets and the request does not get acknowledged. After waiting for specified time, MSP retransmits the probe packet.
: MSP SEND TMO <SlotNo><ValueInSecs>
: 10
Possible Values
: any non zero positive value.
: If no argument is specified or the specified argument is
invalid, the current value is displayed, otherwise the
new value is displayed and
MSP_PROBE_SEND_TIMEOUT for the specified
group is set to the new value.
Used to set the maximum wait time for receipt of a probe packet. This command changes the value of MSP_PROBE_WAIT_TIMEOUT variable for a specified group,if there is a valid argument.MSP waits for MSP_PROBE_WAIT_TIMEOUT seconds before marking the board "IN_ACTIVE" when the board is in WAIT_MODE and MSP has not detected any status change.
: MSP WAIT TMO <SlotNo><ValueInSecs>
: 1
Possible Values
: any non zero positive value.
: If no argument is specified or the specified argument is
invalid, the current value is displayed. Otherwise the
new value is displayed and
MSP_PROBE_WAIT_TIMEOUT for the specified
group is set to the new value.
Used to set maximum number of probe retry count. This command changes the value of MAX_PROBE_RETRY variable, if there is a valid argument.
When probe packet fails to appear at the receive end, MSP will resend the probe packet until the retry count of MAX_PROBE_RETRY+1 is reached. After reaching this limit, MSP puts the board in WAIT_MODE.
: MSP RETRY COUNT <noOfRetries>
: 1
Possible Values
: any non zero positive value.
: If no argument is specified or the specified argument is
invalid, the current value is displayed, otherwise the
new value is displayed and
MSP_PROBE_RETRY is set to the new value.
Displays all the supported commands recognized by MSP.
Used for creating a multispan group by specifying logical names associated with primary and secondary NICs.
: MSP NAMEBIND PrimaryLName SecondaryLname
: MSP NAMEBIND primary_8022 secondary_8022
: None
For all successful creation of group, MSP displays "Group has been created for Primary Slot # xxxx and Frame_Type:yyyy".
If there is a group already present, MSP displays error message "Group Already Present". MSP displays "failed to create a group", if multispan is unable to create group for atleast one frame type supported by the NIC.
Error Conditions:
1. there is no valid board for the name specified.
2. primary does not have any bound protocol stack
3. secondary has a protocol stack bound
4. Link intergrity check failed
To set the inter probe packet delay. This command changes the value AES Wakeup Delay if there is a valid argument.
This value gets effective only when the AESCallBack procedure makes a call to the server to reschedule another AES event. This mainly affects the interval at which successive probe packets are sent on the same board. If the delay is longer, MSP might take more time to recognize the adapter failure or link failure.
: MSP PROBE INTERVAL <inTicks>
: 18 (one second)
Possible Values
: any non zero positive value.
: If no argument is specified or the specified argument
is invalid, the current value is displayed, otherwise the
new value is displayed.
: MSP LOAD SHARING (Not Applicable for OEM)
To turn load sharing mode on or off. MSP load shares the outbound LAN traffic only if load sharing mode is ON. MSP load shares transmits only.
: On
: Current state of the load sharing is displayed.
To set the timeout value for receiving probe packet when sent from one board to another. This command changes the value MSP_RECEIVE_PROBE_TIMEOUT if there is a valid argument. The idea of providing this to satisfy variety of switches.
: MSP RECEIVE TMO <slotNo><inTicks>
: 1 tick for Ethernet and FDDI. 18 ticks for Token-Ring.
Possible Values
: any non zero positive value.
: If no argument is specified or the specified argument
is invalid, the current value is displayed, otherwise the
new value is displayed. slotNo can be a hexadecimal
the current value is displayed, otherwise the new value is displayed. slotNo can be a hexadecimal value.
: MSP DISPLAY STATUS <slotNo>
: slotNo is optional. If the slotNo is not specified,
MSP displays information for all the groups it knows
about, otherwise only for slotNo is displayed on the
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.
FIG. 11 is a hardware block diagram of a server with a legacy block 1346 and dual mirrored block 1348. In this embodiment, the server is an Intel archetecture server. The legacy block maintains backward compatibility via an Industry Standard Architecture (ISA) bus with devices such as the keyboard, monitor, ports, and Basic Input/Output System (BIOS), a.k.a. the legacy components. These devices are identified as legacy components because their operation was part of the original IBM� PC specification defined in 1982. Forward compatibility with new high speed devices is provided via dual mirrored block 1348. This block includes redundant: bridges, busses, and devices; all capable of supporting high speed communications between the CPU 1350 and the devices. The performance of the dual mirrored block is unimpeded by slow speed legacy traffic which is handled in the legacy block.
The legacy block 1346 includes: CPU 1350, memory 1352, bridge-queue 1354A-B video/graphics card 1360, bridge-queue 1362A-B, parallel port 1364, communications port 1366, monitor 1368, keyboard 1370, system clock 1372 and bios 1374. The CPU and memory are connected to a system bus 1380 which operates at 66 MHz. Bridge-que 1354A-B connects system bus 1380 to a peripheral component interface (PCI) bus 1382. The PCI bus operates at 33 MHz. The video/graphics card 1360 is connected to the PCI bus 1382. The PCI bus 1382 is connected to the industry standard architecture (ISA) bus 1388 via bridge-que 1362A-B. The ISA bus 1388 operates at 6 MHz. The remaining legacy devices 1364-1374 are all directly connected to the ISA bus.
The ISA bus operates at a fraction of a percent of the speed of either the PCI bus or the system bus. The Windows� 3.x, 95, NT operating systems all support the legacy devices. All communications between CPU 1350 and any of the legacy devices 1364-1374 pass from the ISA bus via the PCI bus onto the system bus. A considerable portion of the traffic on the PCI bus 1382 traffic is devoted to the legacy devices. It is therefore inappropriate to attach high speed devices to PCI bus 1382 because its operation is impeded by slow speed traffic to/from the ISA bus 1388. High speed devices are better handled in either one or both of the PCI busses 1384-1386 of the dual mirrored block 1348. The dual mirrored block allows high bandwidth communications between the CPU 1350 and peripheral devices such as a small computer storage interface (SCSI) or Network Interface Controller (NIC) cards. The dual mirrored block also allows load balancing of Network traffic as will be described in greater detail with respect to FIGS. 1-10. Additionally, the dual mirrored block allows for a failure of either mirrored block without impairing the operation of the remaining mirrored block.
In the embodiment shown in FIG. 11, mirrored block 1348 includes: bridge-ques 1356A-B, 1358A-B, (SCSI) devices 1390-1392, NMCs 1394-1396 and PCI busses 1384-1386. A PCI bus 1384 is connected via bridge-que 1356A-B to system bus 1380. SCSI device 1390 and NIC 1394 are connected to PCI bus 1384. PCI bus 1386 is connected to system bus 1380 via bridge-que 1358A-B. SCSI device 1392 and NIC device 1396 are connected to PCI bus 1386. Both PCI buses 1384-1386 operate at 133 MHz.
In operation, communication between the legacy devices 1364-1374 and CPU 1350 passes via bridge-queues 1354A-B, 1362A-B from the ISA bus 1388 to the system bus 1380 via PCI bus 1382. All high speed traffic from the SCSI and NIC devices is handled by either or both of PCI buses 1384-1386. Neither of these buses handles legacy traffic. Therefore their performance is unimpaired. Additionally, server down time is greatly reduced by redundancy at the bridge, bus, and device level. Bridge 1356A, PCI bus 1384, SCSI 1390 and NIC 1394, are mirror images of bridge 1358A, PCI bus 1386, SCSI 1392 and NIC 1396.
Thus, the architecture of the mirrored block 1348 allows an individual component at either the device level, the bus level or the bridge level to fail without affecting the operability of the server. Furthermore, because communications between the CPU and any of the legacy devices does not pass via either of the mirrored PCI buses 1384-1386, those mirrored buses handle only high speed traffic, and thus can provide more throughput to/from the SCSI and NIC devices. Additionally, the symmetry of the mirrored block allows load balancing to be implemented.
FIG. 12 shows an embodiment of the dual mirrored buses in which mirrored data storage is supported. FIG. 12 shows the system bus 1380 connected to the mirrored block 1348 via bridge-ques 1356A-B and 1358A-B. Storage device 1400 is connected to SCSI device 1390. Storage device 1402 is connected to SCSI device 1392.
In operation, data mirroring is accomplished by the mirroring portion of mirror and failure detection processes 1404 operating on CPU 1350. These processes are implemented in industry standard operating systems, such as Novell Netware� and Microsoft Windows NT�. In an embodiment of the invention the mirroring portion of the processes 1404 causes identical data to be stored on each of storage devices 1400-1402. Mirroring is implemented by CPU 1350, which directs data Writes to both storage unit 1400 and storage unit 1402. Thus, a memory access request to "Write" request is passed via bridge-queue 1356A-B, PCI bus 1384, SCSI device 1390 to storage unit 1400. The same "Write" memory access request is also passed via bridge-que 1358A-B, PCI bus 1386, SCSI device 1390 to storage unit 1402. In this embodiment, the write requests are routed through mirrored hardware paths to mirrored storage devices.
Memory access "Read" requests may be passed to either one of storage devices 1400 and 1402, thus improving data throughput. While one "Read" request directed to storage device 1400 is being placed in queue 1356-B another memory access "Read" data can be transferred from queue 1358-B via bridge 1358A to CPU 1350 via system bus 1380. When many read requests are directed to the storage devices, a hardware embodiment which provides independent high speed paths to memory may provide much better throughput that a prior art dual PCI bus computer system where, at best, one of the paths must be shared with the legacy ISA bus.
Detection and fail-over is accomplished by the failure portion of processes 1404 operating on CPU 1350. Traffic from bridges 1356A and 1358A is constantly monitored. When it is interrupted there is a failure of either a bridge-que, a PCI bus, a SCSI device or the storage unit itself on either of the mirrored blocks. When the failure is detected failover is implemented. Failover is accomplished by terminating mirrored writes, and instead writing and reading from the remaining accessible storage device, i.e., device 1400 or 1402. The remaining bridge, bus, and SCSI portion of mirrored block 1348 can continue to provide the data storage function without requiring down time on the server. Furthermore, if the mirrored blocks are designed in such a way as to support hot-swapping, the SCSI and/or storage device can be replaced without requiring server down time.
FIG. 13 shows an embodiment of the dual mirrored block architecture utilized for both load balancing and fail over of network traffic. The dual mirrored block 1348 is shown. Additionally, switch 1420, and Local Area Network (LAN) segments 1424-1426 are shown. NICs 1394 and 1396 are connected to individual ports of switch 1420. Switch 1420 may include a routing table 1422. Processes 1428 for load balancing, failure detection and fail over are shown. These processes include protocol stacks 1430-1432 for respectively NICs 1394-1396.
When both bridge bus and device portions of mirrored block 1348 are operational, load balancing is performed in the following manner. Incoming traffic from either LAN segment is tagged with a destination Medium Access Control (MAC) address. Each NIC has a unique MAC address. Switch 1420 routes incoming packets to whichever of NICs 1394-1396 has a MAC address matching the destination address of the packet. Each NIC has associated with it a pair of protocol stacks. Each stack processes packets in first in first out (FIFO) order. One of each pair handles incoming packets while the other handles outgoing packets.
Load balancing of incoming packets are normally subject to the following processes broadly defined as packet processing of incoming packets. These processes include: removing the MAC header including the destination MAC address, performing any decryption or decompression on the payload, and processing the command, query, or response that is contained in the payload. If, for example, the server is performing as a database server, incoming packets might contain payloads with querys. These would be passed after packet processing to the database engine which would retrieve appropriate records from the database. Packet processing is processor intensive activity. Packet processing is traditionally handled by a dedicated processor on each NIC. Traditionally, once a packet is routed by a switch such as switch 1420, that packet ends up in the corresponding one of protocol stack pairs 1430-1432 associated with the receiving NIC, e.g., either NIC 1394 or 1396. The current invention provides processes for balancing incoming and outgoing network traffic between the packet processors. These processes 1428 monitor the size of incoming and outgoing traffic in each of the protocol stack pairs and balance the load between processors, to minimize delay and maximize throughput. If an imbalance of incoming traffic is detected, i.e., if the incoming portion of the protocol stack pair 1430 is longer than the incoming portion of protocol stack pair 1432, then the next incoming packet for protocol stack pair 1430 is sent instead to the incoming portion of protocol stack pair 1432. This re-routing is accomplished at the MAC level, i.e., before packet processing has commenced. The MAC address in the header is changed and the packet is received and processed by the less heavily loaded processor. These processes will be discussed in greater detail in the following FIGS. 1-10. This rerouting is performed transparently in what the traditional Open Systems Interconnection Reference Model (Day and Zimmerman, 1983) (OSI) characterizes as the data link layer.
Load balancing of outgoing packets are normally subject to the following processes broadly defined as packet processing of outgoing packets. These processes include: performing any encryption or compression on the payload including the source and destination address, and wrapping the payload with a header including a destination MAC address. Normally the processing portion of the NIC which receives a packet handles the processing of the response packet as well. In the current invention this is not necessarily the case. Outgoing traffic from the server, to the LANs is also subject to load balancing. If, for example the server is performing as a database server, outgoing packets might contain payloads with records which match a query. These records would be passed to the receiving NIC for outbound processing: including encryption, compression, and wrapping. The packets would be processed in FIFO order from the outgoing portion of the protocol stack pair of the receiving NIC, e.g., either stack pairs 1430 or 1432. Packet processing is processor intensive activity. The outgoing portion of protocol stack pairs can also be impalanced. The current invention provides processes 1428 for detecting outgoing stack imbalance, and rerouting the next outgoing packet to whichever of the outgoing portion of protocol stack pairs 1430-1432 is shorter in size, to minimize delay and maximize throughput. This re-routing is accomplished at the MAC level, i.e., before packet processing has commenced. The MAC address in the header is changed and the packet is received and processed by the less heavily loaded processor. These processes will be discussed in greater detail in the following FIGS. 1-10. This rerouting is performed transparently in what the traditional Open Systems Interconnection Reference Model (Day and Zimmerman, 1983) (OSI) characterizes as the data link layer.
Detection and fail-over is accomplished by the failure portion of processes 1428 operating on CPU 1350. Traffic from bridges 1356A and 1358A is constantly monitored. If there is a failure of either a bridge-que, a PCI bus, a NlCdevice on either portion of the mirrored blocks, traffic is interrupted and the interruption is detected. When the failure is detected failover is implemented. Failover is accomplished by terminating communications with the unreachable/failed NIC. Traffic is directed to the remaining NIC(s). If there is more than one, load balancing is implemented with the remaining NIC(s). The remaining bridge, bus, and NIC(s) portion of mirrored block 1348 can continue to provide the network interface function without requiring down time on the server. Furthermore, if the mirrored blocks are designed in such a way as to support hot-swapping, the NIC can be replaced without requiring server down time.
As will be obvious to those skilled in the art, more than on NIC may be added to either of buses 1384 and 1386 to further improve system throughput.
Sparse Bridge Mapping
As indicated in the discussion of Plug and Play, each adapter card must be configured. Normally, this configuration is done at boot time by the BIOS, insuring that no adapter card's assigned addresses encroach on those of another adapter card.
PCI defines three address spaces through which devices may communicate: memory space, I/O space and configuration space. Software normally communicates with PCI devices through registers and buffers programmed to respond to specific memory or I/O addresses. The third address space, configuration space, is used by specific system software, such as the BIOS at boot time, to program the memory or I/O addresses the PCI device's registers will respond to. The phrase "configuration of a PCI device" refers to this programming of the device through its configuration space. As was indicated earlier, the memory and I/O address spaces must be managed by the BIOS, and by other system software to properly program adapter cards following a hot swap or hot add operation.
Under PCI, PCI-to-PCI bridges each define trees of subordinate busses. Each bus receives a bus number, Primary Bus Number (608), and each bridge defines the range of bus numbers implemented below it in the tree. The Secondary Bus Number 606 is the bus number of the PCI bus on the other side of the bridge, and the Maximum Subordinate Bus Number 622 is the largest PCI bus number found within the tree below this bridge. This implies that the bus number space is allocated among the bridges such that all buses accessible through a bridge are contiguously numbered, and that the bus number ranges allocated among peer bridges are disjoint.
Each PCI bridge also has two pairs of address registers which define the ranges of memory and I/O addresses (respectively) which this bridge will pass through to subordinate buses. The Memory Base (610) and Memory Limit (612) define the range of memory addresses, and the I/O Limit Upper 16 Bits and I/O Base Upper 16 Bits define a range of I/O addresses. PCI devices attached to the bridge's secondary bus, or to buses subordinate to the secondary bus are assigned memory and I/O address ranges from these two ranges.
FIGS. 14-15 illustrate a sparse mapping of bus numbers and address ranges. Sparse mapping refers to assigning bus numbers and address ranges sparsely as the buses are scanned at boot time, so that each bridge has a range allocated to it from which new adapter cards and bridges may be allocated bus numbers and address ranges when they are hot added to the computer. This preallocation results from sparse mapping processes 1542 which allocates bus numbers and address ranges according to a sparse map [See FIG. 15] which is contained in boot memory. The sparse mapping processes are executed during booting of the computer system.
FIG. 14A shows an embodiment of an extensible PCI bus hierarchy. The base system features three PCI buses 1506-1510. One bus 1506 is implemented entirely on the motherboard, and is intended to support embedded SCSI and video controllers, and the ISA bus. There are no PCI connectors on this bus. The other two buses 1508-1510 are provided for support of hot pluggable PCI cards. To support this, PCI—PCI bridges are utilized throughout the implementation of these latter two PCI buses.
For a prior art PC system, where the bridges and buses are discovered and assigned statically at boot time, the assignment procedure is a simple top down, left to right traversal of the PCI space, assessing the requirements of each PCI device on the way down, summing them and assigning address ranges, PCI bus numbers and programming the Secondary Bus Number 606, Maximum Subordinate Bus Number 622, base registers 610, 614 and limit registers 612, 616 for each PCI-to-PCI bridge on the way back up. A Plug and Play BIOS normally assigns these values contiguously by scanning all buses, PCI-to-PCI bridges and adapter cards. In a system where adapter cards, possibly containing PCI-to-PCI bridges themselves may be introduced long after the system booted, this arrangement is inadequate. Such newly introduced devices may not themselves be configurable because no bus numbers or adequate address ranges are available on that PCI bus.
However, where hot adding of PCI cards, devices and bridges is supported, bus numbers and address ranges must be sparsely allocated a priori to allow for addition of bridges during run-time.
PCI Bus Topology for an Intel Embodiment
An embodiment of a PCI-based computer system incorporating the present invention is shown in FIG. 14A. The following discussion assumes an embodiment conforming to Intel MPS 1.4. Other embodiments are possible, including ones conforming to other computer system specifications, such as the CHRP design for PowerPC from Motorola, IBM and Apple Computer.
In FIG. 14A, four backplane connectors (1670-1676, 1678A-1684A) may be provided on each hot pluggable PCI bus (1508, 1510). Each of these is isolated from the PCI bus by an associated bridge (1650-1664). Into each connector may be plugged a canister containing four-PCI slots (1670, for example), card guides and EMI shielding. Hot plugging is accomplished by removing and replacing this canister and any PCI cards in it. This embodiment incorporates one PCI—PCI bridge per four slot canister. There are thus five PCI buses in each of the two hot pluggable bus hierarchies, or ten PCI buses in the base system.
In addition to this passive canister, a second, active type of canister is disclosed. An I/O Processor (IOP) is incorporated in this type of canister which provides local intelligence to service the canister's adapter cards. The IOP may be any processor, including Intel Pentium�, Motorola PowerPC�, Intel 80960. In one embodiment, 1692, the IOP is an Intel 80960RP, which includes, internally, an additional PCI-to-PCI bridge, and support for further isolating the card slots from the computer behind the intelligence provided in the IOP.
Each PCI bus may also include an Intel 82379AB SIO.A chip. For the motherboard PCI bus 1506, this chip provides an ISA bridge, legacy devices such as real time clock, and an 8059A-compatible PCI. This PCI bus is also called the compatibility PCI bus. The I/O Advanced Programmable Interrupt Controller (APIC) portion of this chip is used for forwarding interrupts to the CPU 102. The SIO.A chips associated with the hot pluggable PCI buses are known as I/O APICs, and are initialized such their ISA components are in a passive state. When scanning the PCI buses, the BIOS must be aware that, due to subtractive decode in the 82379AB, the ISA portion of the I/O APICs will respond to all unclaimed I/O accesses.
In an embodiment, the INT A line of each PCI slot may be wired to a separate, PCI-compatible input of the 10 APIC associated with its PCI bus. The remaining INT lines on the PCI buses may be wired to share these inputs to the associated IO APIC. Since each input to an IO APIC may be programmed to invoke a unique ISR when it is asserted to interrupt the CPU, this wiring insures that, when an ISR is invoked, one of only a minimal number of adapter cards may be asserting the interrupt. This, in turn, minimizes the number of devices which the ISR must query before finding the source of the interrupt. In systems where fewer IO APICs are provided, interrupt lines must be shared by many PCI slots, causing the ISR to query more adapter cards to find an interrupting card, and increasing the interrupt service latency.
Another embodiment provides one IO APIC for each four slots. INT lines of the PCI slots are wired each to a separate input of its associated IO APIC. In such an embodiment, each INT line can assert a unique interrupt and invoke a unique ISR, eliminating the need to share interrupts among device functions. In such an embodiment, a multifunction PCI card may have a unique interrupt assigned to each of its functions. The following table illustrates wiring of slot interrupt lines to I/O APICs in one possible embodiment:
Slot #
Slot #
ISA Device
Secondary PIC
PCI Bus 1 (*)
PCI bus 129 (*)
Math Error
(*) ISA IRQs for PCI Bus 1 and PCI Bus 129 must be disabled when in full APIC mode.
In an embodiment, the BIOS may initialize the interrupt system in Virtual-Wire mode before initializing any devices (see Intel MPS 1.4 for a description of virtual wire mode).
For an embodiment conforming to Intel MPS 1.4 Variable Interrupt Routing, the INT lines of all PCI slots of PCI buses 1508 and 1510 are also routed, through intervening logic, to inputs of the motherboard SIO chip's 8059A. In uni-processor mode, these interrupts may be presented through the 8059A of 1512 as ISA interrupts, or in another embodiment which utilizes virtual wire mode as APIC interrupts through the APIC of 1512 Variable Interrupt Routing requires that this intervening logic be capable of suppressing presentation of interrupts through these ISA IRQs when running in full APIC or multiprocessor mode.
According to sparse bus mapping, the bus number space is statically partitioned across the maximum number of backplane slots such that each slot is allocated thirty-two bus numbers. In this embodiment, any one canister may have a PCI bus structure below it with, at most, thirty-one subordinate buses.
The bus number space may be allocated more or less equally between the two hot pluggable buses 1508-1510. One of the hot pluggable buses loses a bus number to the compatibility bus 1506 (number zero). The other hot pluggable bus loses one number to the ISA bus (which must be bus 255). Also, each hot pluggable bus hierarchy loses a bus number to the PCI bus implemented on the backplane. The missing bus numbers are removed from the allocation of the last slot on each backplane bus.
In another embodiment shown in FIG. 14A, only the left-most two PCI/PCI bridges and associated slots or canisters on each of the two backplane PCI buses (i.e., bus numbers 2-34, 35-66, 130-162, 163-194) are provided. The bus numbers assigned to the missing slots may be lost (i.e., reserved), or may be allocated among the implemented canisters according to some mapping other than the one described for the present embodiment.
In an embodiment where CPU 102 is an Intel Pentium(r) Pro, three PCI buses are generated by separate Intel 82450GX Orion-PCI-Bridge (OPB) chip sets. Each OPB has two ranges of I/O addresses which can be programmed to be ignored (handled by another bus), or recognized by this bus. The SIO chip implements a number of ISA devices, ranging from the old AT motherboard devices (RTC, floppy) at port addresses below 100h, to serial controllers at port ranges above 300h. The two OPB registers don't provide enough granularity to allocate portions of the ISA port address range among the OPBs
In the embodiment shown in FIG. 14A, all legacy ISA devices are realized on the primary PCI bus, though the chip 1512 and associated external logic chip (serial, parallel, RTC, keyboard, etc.), as are an S3-based PCI video controller, and a PCI fast/wide SCSI controller. The legacy devices span the entire ISA range as shown in the following table.
I/O Address Range
Reserved for:
PC/AT-compatible motherboard devices
ISA-compatible cards
EISA motherboard I/O devices
ISA I/O devices
EISA motherboard I/O devices
ISA I/O devices
EISA motherboard I/O devices
ISA I/O devices
15 EISA cards, x000h-xfffh per card
Most ISA devices, as well as the PCI video and SCSI controllers, use ports in the range of 0100h-03ffh.
In an embodiment having multiple OPBs, the compatibility OPB (i.e., the one which has the ISA bridge associated with it) decodes all I/O references except those specifically disabled by the I/O Space Range registers (pp. 64-65 of the Intel OPB spec "82450 GX/KX PCISETS EDS", rev 2.3). The other OPBs will not decode any I/O references unless they are specifically enabled by these same registers. Further, the OPB will always alias I/O references to ISA I/O ports by masking the upper 16 bits of a 32 bit port address, passing only the low 16 bits (i.e., wrapping the addresses into the 64KB ISA I/O space). The PCI Decode Mode register provides some deviation from this decode procedure. The overall affect of this is to limit the I/O range available in to 64KB, limiting the space available for partitioning to each PCI bus.
The Intel MP Spec (1.4) defines three regions of the x86 address space as available for memory mapped I/O. Since the OPBs may implement subtractive decode (they will decode references to any address to which no one else responds), each OPB must be told which memory ranges it is to decode for I/O mapping, and which it is not (more correctly, each OPB is told which gaps in the x86 address space it should ignore). Since there are only two such memory gap registers in the OPB, the three ranges of memory mapped I/O addresses must be carved out of, at most, two contiguous address ranges.
In one embodiment, we define a 16 MB range for each PCI bus. The compatibility bus 1506 uses the upper most 16 MB range (0FEF0—0000h-OFFD_FFFFh). Of this space, 1 MB will be reserved for a SCSI controller, and 8 MB for a video controller. The remaining 7 MB is available for future expansion. For the two remaining PCI buses 1508-1510, 32 MB is allocated and divided equally between the two buses immediately below the I/O APIC range (0FCE0—0000H-0FDDF_FFFFh and 0FDE0—0000h-0FDF_FFFFh, for bus 129 and bus 1, respectively).
It is possible that a hot added PCI card may require more memory space than is left in bus' allocation. In one embodiment of the current invention, this condition may result in a configuration error, and the card will not be initialized. In such a situation, the offending card may be moved to another PCI bus or canister which has enough space remaining in its allocation. In another embodiment of the current invention, configuration software support may be provided which will scan the current configuration and allocated resources and suggest where to place the new card. In a third embodiment, existing address assignments may be adjusted to accommodate the new card.
PCI Configuration space is defined to be 64 double words for each PCI device function (i.e., for each of up to eight functions which each PCI device may support). The bus number, device and function are implicit in the 32-bit configuration address so no allocation or rationing of this space is needed. The boot memory 116 may maintain a database of buses, bridges and PCI devices and their addresses such as that shown in FIG. 15. Representation of this information may be designed such that the database may be edited, and queried through standard PC APIs (e.g., DMF, Card Services).
In an embodiment, as shown in FIG. 15, 4 KB of I/O address space is reserved for the compatibility PCI bus and each canister by using the I/O ranges assigned to EISA, Since no support is provided for the EISA bus.
The following sections outline the requirements of NetWare� by Novell Inc. of Orem Utah, Windows� NT by Microsoft of Redmond Wash. and of the sparse bridge mapping processes 118 which are part of the boot memory 116 BIOS, with respect to routing of PCI interrupts and interrupt management. [See PCI System Architecture, Tom Shanley and Don Anderson, 1995, MindShare, Inc, ISBN: 0-201-40993-3 and from the Intel MPS Specification (Version 1.4), Appendix D each of which is incorporated herein by reference as if fully set forth herein.
NetWare� provides support for up to four PCI buses, and 64 PCI interrupt vectors. PCI interrupts are assumed to be routed through an I/O APIC, where each PCI interrupt may be separately mapped to an IRQ. NetWare provides all APIC programming, as long as the design includes an Intel I/O APIC. Novell would like the APICs to be I/O mapped. NetWare also requires that individual PCI interrupts be "peeled" away from the ISA interrupt controller, and rerouted as full APIC interrupts.
NetWare expects the BIOS to provide a table compatible with MPS 1.4. NetWare does not perform its own PCI discovery, and makes no assumptions about the MPS 1.4 table being static.
NetWare supports a variety of PCI controller cards which can be accessed via the ISA IO Port space, as well as being accessible as PCI devices. NetWare requires that these cards support currently shipping legacy drivers, wherever the cards are plugged in. This requires that two hot pluggable buses 1508-1510 [see FIG. 14A] be mapped into the ISA IO space, and the ISA IRQ space, as well as being treated as peer PCI buses (i.e., they must be dual mode).
Windows NT� requires the BIOS to have built an MPS table, compliant with the MPS 1.4 spec. NT does not rescan the PCI bus, and does not rebuild the table.
In the Intel Pentium Pro embodiment described above, the MP configuration table is be positioned in read/write memory, and completed to reflect the actual buses, devices, and address assignments. Devices in the table which are not present, or not functional, are either removed from the table, or flagged as not functioning.
A Floating Pointer Structure and MP Configuration Table may provided. The MP Configuration Table will be large (4600 bytes or larger), and so must be implemented at the top of extended memory. The entire maximum topology of the embodiment being described in reference to FIG. 14A may be reflected in the following OEM configuration table, including both 82379AB I/O APICs and 80960RPs. This may be done in order to accommodate hot adding of components. If external bridge components are dynamically added, the Configuration Table will have to be edited and rewritten, so that entries appear in the right order.
The following is an OEM Configuration Table which may be used to connect to the configuration database shown in FIG. 15.
I/O Interrupt
ISA ints
pluggable w/o 80960RP
pluggable w/80960RP
Sys Addr Mapping
Bus Hierarchy
Compat. Bus Mapping
In FIG. 14B a detailed view of bridges 1678A-1684A is shown. These bridges are initially set forth in FIG. 14A. Control unit 1500, primary bridge 1504A and swap/add unit 1502 are shown. Bridge 1504A includes configuration register 1504B. Swap/add unit 1502 includes bridges 1678A-1684A, canisters 1618-1622, power switch 1524 and LEDs 1630-1636. Each of bridges 1678A-1684A includes respectively, control registers 1678B-1684B. Canister 1622 includes adapter cards 1640-1644. Control unit 1500 is connected via bridge 1504A to bus 1510. Bridges 1678A-1684A each connect via intermediate bridges [see FIG. 14A] to primary bus 1510. Canisters 1618-1622 each connect to bridges 1678A-1682A. Bridge 1684A is not connected to a canister. Canisters 1618-1622 each include four slots for peripheral cards. Canister 1622 includes cards 1640-1644 in three of its four available slots. Bridge 1684A is configured to accept a canister referenced as 1624 but in the example shown does not contain such a canister.
Power control 1524 is connected via signal lines 1520 and 1522 to bus 1510. Power control 1524 is also connected to power lines 1526. Power control is connected via signal lines 1628 to each of LEDs 1630-1636 associated with, respectively, canisters 1618-1622 and interface 1624. Power control 1524 is also connected via individual power lines 1626 to each, respectively, of canisters 1618-1622 and to canister slot 1624.
In order to implement a Hot-Add environment in a PCI architecture each of bridges 1504A and 1678A-1684A may be configured to reserve sufficient address space not only to support those peripheral devices physically present in the system but also to support those devices which might be added to this system after boot-up. In the example shown in FIG. 14B the only devices physically present at boot-up are bridges 1504A and 1678A-1684A and peripheral devices 1640-1644. Nevertheless, a sparse map similar to that discussed above in connection with FIG. 15 may, for example, require each bridge to reserve 4 MB per canister. The sparse map is contained in boot memory 1540. Sparse bridge mapping processes, which may be included as part of the system BIOS, configure the computer on power up in accordance with the speculative bridge map. The bridge mapping code 1542 stored in boot memory 1540 may cause the processor 102 to write to the configuration registers of bridges 1678A-1684A and 1504A a range of addresses similar to those present in the table shown in FIG. 15. The reserved address range may be greater than required by the actual physical devices on the secondary side of each bridge.
Fault-Tolerance: A computer system is fault-tolerant when it has the ability to continue operation despite the failure of one or more individual elements.
Redundancy: To implement fault-tolerance system components and data pathways are duplicated or mirrored in order to provide primary and backup components and data pathways.
Fault-Detection: A fault-tolerant system includes the ability to detect a failure in any of its components.
Fail-Over: A fault-tolerant system includes the ability to transition operational control from components that have failed to components that remain operational.
Load Sharing: In a computer system with redundant components, load sharing is implemented by controlling the data flow through one or another of at least two redundant operational data paths in order to maximize throughput.
Processor: Refers to any combination of processors on the system bus, on an IO bus, or within peripheral devices such as NICs. The processors may be any conventional general purpose single- or multi-chip microprocessor such as a Pentium processor, a Pentium Pro processor, a 8051 processor, a MIPS processor, a Power PC processor, or an Alpha processor. In addition, the processor may be any conventional special purpose processor such as a digital signal processor or a graphics processor, or network interface packet processor operating individually or in combination.
Program Code: Processing is implemented with a series of conditional instructions which collectively are referred to as program code. The program code may be stored in a memory or embedded in a logic unit.
Memory: Includes physical medium for storage of data either permanently or temporarily.
The foregoing description 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. Obviously, many modifications and variations will be apparent to practitioners skilled in the art.
The following patent applications, commonly owned and filed OCT. 1, 1997, are hereby incorporated herein in their entirety by reference thereto:
Docket No.
"System Architecture for
Remote Access and Control
of Environmental Management"
"Method of Remote Access and
Control of Environmental
"System for Independent
Powering of Diagnostic
Processes on a
Computer System"
"Method of Independent
Powering of Diagnostic
Processes on a
Computer System"
"Diagnostic and Managing
Distributed Processor System"
"Method for Managing a
Distributed Processor System"
"System for Mapping
Environmental Resources
to Memory for
Program Access"
"Method for Mapping
Environmental Resources
to Memory for
Program Access"
"Hot Add of Devices Software
"Method for The Hot Add of
"Hot Swap of Devices Software
"Method for The Hot Swap of
"Method for the Hot Add
of a Network Adapter on a
System Including a Dynamically
Loaded Adapter Driver"
"Method for the Hot Add of a
Mass Storage Adapter on a
System Including a Statically
Loaded Adapter Driver"
"Method for the Hot Add of a
Network Adapter on a System
Including a Statically
Loaded Adapter Driver"
"Method for the Hot Add of a
Mass Storage Adapter on a
System Including a Dynamically
Loaded Adapter Driver"
"Method for the Hot Swap of a
Network Adapter on a System
Including a Dynamically
Loaded Adapter Driver"
"Method for the Hot Swap of a
Mass Storage Adapter on a
System Including a Statically
Loaded Adapter Driver"
"Method for the Hot Swap of a
Network Adapter on a System
Including a Statically
Loaded Adapter Driver"
"Method for the Hot Swap of a
Mass Storage Adapter on a
System Including a Dynamically
Loaded Adapter Driver"
"Method of Performing an
Extensive Diagnostic Test in
Conjunction with a BIOS
Test Routine"
"Apparatus for Performing an
Extensive Diagnostic Test in
Conjunction with a BIOS
Test Routine"
"Configuration Management
Method for Hot Adding and
Hot Replacing Devices
"Configuration Management
System for Hot Adding and
Hot Replacing Devices"
"Apparatus for Interfacing
"Method for Interfacing Buses"
"Computer Fan Speed Control
"Computer Fan Speed Control
"System for Powering Up and
Powering Down a Server"
"Method of Powering Up and
Powering Down a Server"
"System for Resetting a Server"
"Method of Resetting a Server"
"System for Displaying Flight
"Method of Displaying Flight
"Synchronous Communication
"Synchronous Communication
"Software System Facilitating
the Replacement or Insertion of
Devices in a Computer System"
"Method for Facilitating the
Replacement or Insertion of
Devices in a Computer System"
"System Management Graphical
User Interface"
"Display of System Information"
"Data Management System
Supporting Hot Plug Operations
on a Computer"
"Data Management Method
Supporting Hot Plug Operations
on a Computer"
"Alert Configurator and
"Managing Computer System
"Computer Fan Speed Control
"Computer Fan Speed Control
System Method"
"Black Box Recorder for
Information System Events"
"Method of Recording
Information System Events"
"Method for Automatically
Reporting a System Failure
in a Server"
"System for Automatically
Reporting a System Failure
in a Server"
"Expansion of PCI Bus Loading
"Method for Expanding PCI Bus
Loading Capacity"
"System for Displaying System
"Method of Displaying System
"Fault Tolerant Computer
"Method for Hot Swapping of
Network Components"
"A Method for Communicating
a Software Generated Pulse
Waveform Between Two
Servers in a Network"
"A System for Communicating
a Software Generated Pulse
Waveform Between Two
Servers in a Network"
"Method for Clustering Software
"System for Clustering Software
"Method for Automatically
Configuring a Server after Hot
Add of a Device"
"System for Automatically
Configuring a Server after Hot
Add of a Device"
"Method of Automatically
Configuring and Formatting a
Computer System and
Installing Software"
"System for Automatically
Configuring and Formatting a
Computer System and
Installing Software"
"Determining Slot Numbers in a
"System for Detecting Errors
in a Network"
"Method of Detecting Errors
in a Network"
"System for Detecting Network
"Method of Detecting Network
|Cited Patent
|Filing date
|Publication date
|Jun 14, 1976
|Nov 8, 1977
|Sperry Rand Corporation
|Remote controlled test interface unit
|Apr 2, 1976
|Jul 11, 1978
|International Business Machines Corporation
|Computer controlled distribution apparatus for distributing transactions to and from controlled machine tools having means independent of the computer for completing or stopping a tool function initiated by a computer transaction
|Oct 5, 1981
|May 15, 1984
|Digital Equipment Corporation
|Interface between a pair of processors, such as host and peripheral-controlling processors in data processing systems
|Mar 18, 1985
|Jun 9, 1987
|Tandem Computers Incorporated
|Multiprocessor system
|Dec 17, 1984
|Sep 8, 1987
|At&T Bell Laboratories
|Reliable local data network arrangement
|Oct 25, 1984
|Sep 22, 1987
|Unisys Corporation
|Maintenance subsystem for computer network including power control and remote diagnostic center
|Jun 17, 1985
|Nov 17, 1987
|International Business Machines Corporation
|Emulator for computer system input-output adapters
|Aug 11, 1986
|Sep 6, 1988
|Isaac Levanon
|Modular computer system with portable travel unit
|Jul 27, 1987
|Sep 27, 1988
|Nittan Co., Ltd.
|Environmental abnormality detection apparatus
|Feb 25, 1985
|Apr 11, 1989
|Itt Corporation
|Device interface controller for intercepting communication between a microcomputer and peripheral devices to control data transfers
|Jul 21, 1986
|May 30, 1989
|American Telephone And Telegraph Company, At&T Bell Laboratories
|Method and apparatus for controlled removal and insertion of circuit modules
|Sep 30, 1988
|Jan 16, 1990
|Tandy Corporation
|Portable computer with removable and replaceable add-on modules
|Oct 21, 1988
|Aug 14, 1990
|Modular Computer Systems, Inc.
|Intermediate memory system for connecting microcomputers to a rotating disk memory
|Feb 3, 1989
|Nov 6, 1990
|Digital Equipment Corporation
|Modular crossbar interconnection metwork for data transactions between system units in a multi-processor system
|Jul 15, 1988
|Mar 12, 1991
|Bull Hn Information Systems Inc.
|Hot extraction and insertion of logic boards in an on-line communication system
|Oct 12, 1989
|Apr 9, 1991
|Catene Systems Corporation
|Segmented backplane for multiple microprocessing modules
|May 3, 1988
|Apr 16, 1991
|Care Systems, Inc.
|Apparatus and method for updated recording of irregularities in an electrocardiogram waveform
|Apr 19, 1990
|Jul 16, 1991
|Digital Equipment Corporation
|Memory selftest method and apparatus same
|Nov 13, 1989
|Sep 24, 1991
|Secure Telecom, Inc.
|Remote control system using power line of remote site
|Aug 31, 1990
|Dec 17, 1991
|Oded Yossifor
|Secured data transmission and error recovery mechanism in cordless telephones
|May 31, 1989
|Apr 7, 1992
|M. T. Mcbrian Inc.
|Control system for controlling environmental conditions in a closed building or other conditions
|Dec 8, 1990
|Jun 2, 1992
|Storage Technology Corporation
|Controller for disabling a data bus
|May 13, 1991
|Jun 9, 1992
|International Business Machines Corporation
|Preliminary polling for identification and location of removable/replaceable computer components prior to power-up
|Sep 29, 1989
|Jun 16, 1992
|The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration
|Remote maintenance monitoring system
|Apr 3, 1990
|Aug 4, 1992
|Oce-Nederland B.V.
|Distributed office automation system with specific task assignment among workstations
|May 30, 1989
|Aug 4, 1992
|Fujitsu Limited
|Terminal apparatus for resetting by remote control
|Feb 15, 1990
|Aug 11, 1992
|National Semiconductor Corporation
|Built-in self test for integrated circuit memory
|Sep 24, 1990
|Oct 20, 1992
|Novell, Inc.
|Fault tolerant computer system
|Oct 7, 1992
|May 11, 1993
|International Business Machines Corporation
|System for computer peripheral bus for allowing hot extraction on insertion without disrupting adjacent devices
|Jun 6, 1991
|Sep 14, 1993
|International Business Machines Corporation
|Diagnostic system and interface for a personal computer
|Jun 19, 1991
|Sep 21, 1993
|International Business Machines Corporation
|System and method for installing software and updating configuration files
|Sep 25, 1992
|Oct 12, 1993
|Apple Computer, Inc.
|Method of arbitration for buses operating at different speeds
|Apr 8, 1991
|Nov 9, 1993
|International Business Machines Corporation
|Asynchronous replication of data changes by distributed update requests
|Aug 3, 1990
|Nov 23, 1993
|International Business Machines Corporation
|Method and means for managing DASD array accesses when operating in degraded mode
|Dec 5, 1991
|Nov 30, 1993
|Thinking Machines Corporation
|Power supply system including power sharing control arrangement
|Sep 24, 1990
|Dec 7, 1993
|Emc Corporation
|Dynamically reconfigurable data storage system with storage system controllers selectively operable as channel adapters on storage device adapters
|Sep 9, 1991
|Dec 21, 1993
|Compaq Computer Corporation
|Power supply for computer system manager
|Nov 12, 1991
|Dec 21, 1993
|International Business Machines Corporation
|Hot-plugging circuit for the interconnection of cards to boards
|Jun 28, 1991
|Jan 4, 1994
|Digital Equipment Corporation
|Computer system console
|Sep 24, 1992
|Jan 11, 1994
|Compaq Computer Corporation
|Apparatus for removably supporting a plurality of hot plug-connected hard disk drives
|Feb 17, 1993
|Jan 18, 1994
|Zenith Data Systems Corporation
|Personal computer having dedicated processors for peripheral devices interconnected to the CPU by way of a system control processor
|Jun 24, 1991
|Feb 1, 1994
|Compaq Computer Corporation
|Power supply for computer system manager
|May 31, 1991
|Apr 26, 1994
|International Business Machines Corporation
|Method and apparatus for remote maintenance and error recovery in distributed data processing networks
|Aug 6, 1992
|May 10, 1994
|Logistics Management Inc.
|Computer with modules readily replaceable by unskilled personnel
|Dec 6, 1991
|May 10, 1994
|M. T. Mcbrian Company, Inc.
|Reconfigurable controller for monitoring and controlling environmental conditions
|Apr 4, 1991
|May 31, 1994
|Digital Equipment Corporation
|Computer peripheral device network with peripheral address resetting capabilities
|Apr 15, 1992
|Jul 12, 1994
|International Business Machines Corp.
|System to service processor interface for a tablet computer
|Feb 6, 1992
|Aug 9, 1994
|Tandem Computers Incorporated
|Environment monitoring system for standard interface bus computer systems
|Feb 10, 1992
|Sep 27, 1994
|Simpact Associates, Inc.
|Digital/audio interactive communication network
|Feb 4, 1994
|Nov 22, 1994
|Compaq Computer Corporation
|Computer system manager for monitoring events and operating parameters and generating alerts
|Oct 25, 1993
|Jan 3, 1995
|Unisys Corporation
|Pry-in/pry-out disk drive receptacle
|Mar 27, 1991
|Jan 3, 1995
|Kabushiki Kaisha Toshiba
|Apparatus for remotely operating computer system
|Oct 14, 1992
|Jan 31, 1995
|International Business Machines Corp.
|Hot removable and insertion of attachments on fully initialized computer systems
|May 29, 1991
|Feb 7, 1995
|Dell Usa, L.P.
|Method and apparatus for updating and restoring system BIOS functions while maintaining BIOS integrity
|Nov 23, 1993
|Mar 28, 1995
|Compaq Computer Corporation
|Innate bus monitoring system for computer system manager
|Jan 22, 1993
|Apr 4, 1995
|Intel Corporation
|System for copying device driver stub into allocated portion of system memory corresponding to receiving resource to enable device driver execution from resource memory
|Sep 29, 1992
|Jun 6, 1995
|Amdahl Corporation
|Error handling mechanism for a controller having a plurality of servers
|Jan 14, 1994
|Jun 20, 1995
|Ast Research, Inc.
|Signaling protocol for concurrent bus access in a multiprocessor system
|Dec 23, 1993
|Jul 4, 1995
|Krone Ag
|Digital electronic loop crossconnect and carrier system
|Jun 17, 1992
|Jul 4, 1995
|Unisys Corporation
|Peripheral device interface for dynamically selecting boot disk device driver
|Jun 29, 1993
|Jul 11, 1995
|Hitachi, Ltd.
|Computer system and monitoring method
|Apr 11, 1991
|Jul 11, 1995
|International Business Machines Corp.
|LAN server personal computer with unattended activation capability
|Mar 23, 1993
|Aug 1, 1995
|Smith; Peter L.
|Self-powered computer accessory device for power extraction from attached data signals and method of operating thereof
|Jul 6, 1993
|Aug 8, 1995
|Kabushiki Kaisha Toshiba
|Computer system capable of connecting expansion unit
|Oct 15, 1993
|Sep 5, 1995
|Tandem Computers Incorporated
|Method and apparatus for fault tolerant connection of a computing system to local area networks
|Jul 14, 1993
|Oct 3, 1995
|Dell Usa, L.P.
|Circuit and method for remote diagnosis of personal computers
|Nov 1, 1994
|Oct 24, 1995
|Compaq Computer Corporation
|Rack-mounted computer apparatus
|Jul 14, 1993
|Oct 31, 1995
|Dell Usa, L.P.
|System and method for loading diagnostics routines from disk
|Oct 5, 1994
|Nov 7, 1995
|Gemplus Card International
|System for monitoring abnormal integrated circuit operating conditions and causing selective microprocessor interrupts
|Aug 21, 1992
|Nov 28, 1995
|Compaq Computer Corporation
|Computer management system and associated management information base
|Mar 29, 1994
|Nov 28, 1995
|The United States Of America As Represented By The Secretary Of The Navy
|Network file server with automatic sensing means
|Jun 30, 1993
|Dec 5, 1995
|Harris Corporation
|Hot pluggable motherboard bus connection method
|Nov 15, 1993
|Jan 9, 1996
|Teac Corporation
|Hot-swappable multi-cartridge docking module
|Jan 17, 1995
|Jan 16, 1996
|Apple Computer, Inc.
|Method and apparatus for fuzzy logic rule execution
|Feb 5, 1993
|Jan 16, 1996
|Digital Equipment Corporation
|Concurrency-control method and apparatus in a database management system utilizing key-valued locking
|Feb 9, 1994
|Jan 23, 1996
|Honda Giken Kogyo Kabushikikaisha
|Method and apparatus for detecting faults in a computer network
|Sep 30, 1992
|Feb 6, 1996
|Bay Networks Group, Inc.
|System having central processor for transmitting generic packets to another processor to be altered and transmitting altered packets back to central processor for routing
|Jan 13, 1995
|Feb 13, 1996
|International Business Machines Corporation
|System and method for remote workstation monitoring within a distributed computing environment
|Jul 25, 1994
|Feb 20, 1996
|Zilog, Inc.
|Power efficient RAM disk and a method of emulating a rotating memory disk
|Jan 11, 1995
|Feb 20, 1996
|Apple Computer, Inc.
|Memory architecture using page mode writes and single level write buffering
|Jan 27, 1995
|Apr 30, 1996
|Auspex Systems, Inc.
|Fault tolerant NFS server system and mirroring protocol
|Dec 19, 1994
|Apr 30, 1996
|At&T Corp.
|Concurrent fault simulation of circuits with both logic elements and functional circuits
|Apr 25, 1994
|May 14, 1996
|Compaq Computer Corp.
|Expansion device configuration system having two configuration modes which uses automatic expansion configuration sequence during first mode and configures the device individually during second mode
|Mar 14, 1994
|May 21, 1996
|Sun Microsystems, Inc.
|Portable PCMCIA interface for a host computer
|Jun 14, 1993
|Jun 11, 1996
|Compaq Computer Corporation
|Temperature dependent fan control circuit for personal computer
|Oct 13, 1994
|Jun 18, 1996
|Nt International, Inc.
|Fiber-optic interface system
|Jun 7, 1995
|Jun 25, 1996
|3Com Corporation
|Apparatus for live bus insertion of add-on devices
|Jun 24, 1994
|Jul 2, 1996
|Xerox Corporation
|Method of saving machine fault information including transferring said information to another memory when an occurrence of predetermined events or faults of a reproduction machine is recognized
|Nov 30, 1992
|Jul 2, 1996
|Cray Research, Inc.
|Direction order priority routing of packets between nodes in a networked system
|Jun 6, 1995
|Jul 9, 1996
|International Business Machines Corporation
|System and method for logical console verification and feedback
|Apr 20, 1994
|Jul 23, 1996
|International Business Machines Corporation
|Load balancing of network by maintaining in each computer information regarding current load on the computer and load on some other computers in the network
|May 28, 1993
|Jul 30, 1996
|International Business Machines Corp.
|System for counting the number of peripheral buses in each hierarch connected to primary bus for creating map of peripheral buses to locate peripheral devices
|Jan 18, 1995
|Aug 13, 1996
|Dell Usa, L.P.
|Serial fan cooling subsystem for computer systems
|Jan 19, 1995
|Aug 20, 1996
|Hewlett-Packard Company
|Data storage system and method for managing asynchronous attachment and detachment of storage disks
|Aug 2, 1994
|Sep 10, 1996
|Intel Corporation
|Automatic computer card insertion and removal algorithm
|Aug 18, 1994
|Sep 24, 1996
|International Business Machines Corporation
|HMC: A hybrid mirror-and-chained data replication method to support high data availability for disk arrays
|Aug 20, 1993
|Sep 24, 1996
|Compaq Computer Corporation
|Graphical user interface for computer management system and an associated management information base
|Sep 1, 1994
|Sep 24, 1996
|Intel Corporation
|Input/output adapter cards having a plug and play compliant mode and an assigned resources mode
|Jul 19, 1994
|Sep 24, 1996
|Intel Corporation
|Power management coordinator system and interface
|Aug 2, 1994
|Oct 8, 1996
|Pemberton; Adam C.
|Apparatus for connecting and disconnecting peripheral devices to a powered bus
|Dec 30, 1993
|Oct 15, 1996
|Lockheed Martin Corporation
|Fault tolerant method and system for high availability document image and coded data processing
|Oct 23, 1992
|Oct 15, 1996
|Fox Network Systems, Inc.
|System and method for monitoring computer environment and operation
|May 15, 1995
|Oct 22, 1996
|Dell Usa, L.P.
|Method and apparatus for detecting the insertion or removal of expansion cards using capacitive sensing
|Jan 5, 1995
|Oct 22, 1996
|International Business Machines Corporation
|Method and apparatus for configuring a bus-to-bus bridge
|Jan 18, 1995
|Nov 5, 1996
|Dell Usa, L.P.
|Plenum bypass serial fan cooling subsystem for computer systems
|Apr 21, 1995
|Nov 19, 1996
|Ht Research, Inc.
|Chassis for a multiple computer system
|Jun 30, 1994
|Nov 26, 1996
|Teletransaction, Inc.
|Portable work slate computer with multiple docking positions for interchangeably receiving removable modules
|Jul 7, 1994
|Nov 26, 1996
|Dell U.S.A., L.P.
|Local proactive hot swap request/acknowledge system
|Apr 3, 1995
|Nov 26, 1996
|Dell Usa, L.P.
|Computer system employing docking bay with spring loaded connector pins and file coherency method
|Nov 17, 1994
|Dec 3, 1996
|Intel Corporation
|Method and apparatus for managing live insertion of CPU and I/O boards into a computer system
|Jun 7, 1995
|Dec 3, 1996
|International Business Machines Corporation
|Bus-to-bus read prefetch logic for improving information transfers in a multi-bus information handling system (bus-to-bus bridge for a multiple bus information handling system that optimizes data transfers between a system bus and a peripheral bus)
|Feb 2, 1994
|Dec 10, 1996
|3Com Corporation
|Method and apparatus for live insertion and removal of electronic sub-assemblies
|Nov 12, 1993
|Dec 17, 1996
|Conner Peripherals, Inc.
|SCSI-coupled module for monitoring and controlling SCSI-coupled raid bank and bank environment
|May 9, 1996
|Dec 24, 1996
|International Computers Limited
|Parallel computer having MAC-relay layer snooped transport header to determine if a message should be routed directly to transport layer depending on its destination
|Nov 29, 1994
|Dec 24, 1996
|Hitachi, Ltd.
|Storage system having a bus common to a plurality of kinds of groups of packages
|Dec 21, 1994
|Jan 7, 1997
|Intel Corporation
|Method and apparatus for enhancing the fault-tolerance of a network
|Mar 14, 1995
|Jan 7, 1997
|Network Integrity, Inc.
|Stand-in computer server
|Jan 26, 1995
|Jan 21, 1997
|Compaq Computer Corporation
|Computer failure recovery and alert system
|Sep 28, 1992
|Jan 28, 1997
|Sixtel S.P.A.
|Cordless local area network having a fixed central control device
|Jan 26, 1995
|Feb 11, 1997
|Gas Research Institute
|Installation link-up procedure
|Dec 28, 1994
|Feb 18, 1997
|Intel Corporation
|Circuitry for controlling power application to a hot docking SCSI SCA disk drive
|Jan 27, 1995
|Feb 25, 1997
|Intel Corporation
|Method and apparatus for multiplexing signals from a bus bridge to an ISA bus interface and an ATA bus interface
|Mar 14, 1995
|Mar 4, 1997
|Network Integrity, Inc.
|Stand-in Computer file server providing fast recovery from computer file server failures
|May 22, 1995
|Mar 4, 1997
|International Business Machines Corporation
|Add-in board with enable-disable expansion ROM for PCI bus computers
|Jun 7, 1995
|Mar 25, 1997
|Advanced Micro Devices, Inc.
|Side bus to dynamically off load main bus
|Nov 2, 1995
|Apr 15, 1997
|Dell Usa L.P.
|Method and apparatus for determining fan bearing friction
|Oct 10, 1995
|Apr 15, 1997
|Intel Corporation
|Method and apparatus for managing alerts and events in a networked computer system
|May 17, 1995
|Apr 22, 1997
|Taco, Inc.
|Integrated zoning circulator with priority controller
|Feb 3, 1995
|Apr 29, 1997
|Motorola, Inc.
|Apparatus for non-disruptively interconnecting perpheral device modules with a host device
|Dec 30, 1994
|May 6, 1997
|Compaq Computer Corporation
|Circuit for reassigning the power-on processor in a multiprocessing system
|Mar 2, 1995
|May 6, 1997
|Data Translation, Inc.
|Reprogrammable PCMCIA card and method and apparatus employing same
|May 5, 1995
|May 13, 1997
|Apple Computer, Inc.
|Dynamic device matching using driver candidate lists
|Apr 27, 1995
|May 20, 1997
|Elonex I.P. Holdings, Ltd
|System for network file server failure notification
|Oct 25, 1995
|May 20, 1997
|Cisco Systems Inc.
|Computer system with cascaded peripheral component interconnect (PCI) buses
|Jun 7, 1995
|Jun 3, 1997
|Hitachi, Ltd.
|Fault processing method and information processing system
|Mar 17, 1995
|Jun 10, 1997
|Fujitsu Limited
|Method and apparatus allowing hot replacement of circuit boards
|Nov 2, 1995
|Jul 1, 1997
|International Business Machines Corporation
|Autodocking hardware for installing and/or removing adapter cards without opening the computer system cover
|Jul 7, 1995
|Jul 1, 1997
|Sun Microsystems, Inc.
|Method and apparatus for hot plugging/unplugging a sub-system to an electrically powered system
|Jun 5, 1995
|Jul 22, 1997
|Hitachi, Ltd.
|Hierarchical network management system
|Nov 13, 1995
|Jul 29, 1997
|Systemsoft Corporation
|Method and apparatus for diagnosis and correction of peripheral device allocation faults
|Mar 9, 1995
|Jul 29, 1997
|Hitachi, Ltd.
|Method and apparatus for performing change-over control to processor groups by using rate of failed processors in a parallel computer
|Mar 29, 1994
|Jul 29, 1997
|The United States Of America As Represented By The Secretary Of The Navy
|Method of non-intrusively sensing status in a computer peripheral
|Oct 17, 1994
|Jul 29, 1997
|Hitachi, Ltd.
|Method and apparatus for controlling remote power source
|Jun 7, 1995
|Jul 29, 1997
|International Business Machines Corporation
|Method and apparatus for establishing communications sessions in a remote resource control environment
|Mar 8, 1995
|Aug 5, 1997
|Bmc Software, Inc.
|System for monitoring and managing computer resources and applications across a distributed computing environment using an intelligent autonomous agent architecture
|Jun 7, 1995
|Aug 5, 1997
|Emc Corporation
|Programmable rset system and method for computer network
|Dec 13, 1994
|Aug 5, 1997
|Microsoft Corporation
|Method for automatically configuring devices including a network adapter without manual intervention and without prior configuration information
|Jun 16, 1994
|Aug 19, 1997
|International Business Machines Corporation
|Scheme to determine completion of directory operations for server recovery
|Mar 24, 1995
|Sep 2, 1997
|Kabushiki Kaisha Toshiba
|Computer system having detachable expansion unit
|Aug 16, 1996
|Sep 2, 1997
|Dell Usa, L.P.
|Local proactive hot swap request/acknowledge system
|Jun 7, 1995
|Sep 9, 1997
|Ast Research, Inc.
|Disk power manager for network servers
|May 24, 1996
|Sep 16, 1997
|International Business Machines Corporation
|Virtual shared disks with application transparent recovery
|Aug 1, 1994
|Sep 16, 1997
|International Business Machines Corporation
|Self-configuring computer system
|Feb 23, 1996
|Sep 16, 1997
|Hughes Electronics
|Signal processing array
|Oct 18, 1995
|Sep 23, 1997
|Hitachi, Ltd.
|Bus control system
|May 19, 1995
|Oct 7, 1997
|Compaq Computer Corporation
|Multi-server fault tolerance using in-band signalling
|Jun 7, 1995
|Oct 21, 1997
|International Business Machines Corporation
|Hot plugging of an adapter card
|Sep 11, 1996
|Oct 28, 1997
|Bbn Corporation
|Centralized computer event data logging system
|Aug 22, 1995
|Nov 4, 1997
|Sequent Computer Systems, Inc.
|Packaging architecture for a data server
|Jul 5, 1996
|Nov 18, 1997
|Johnson; R. Brent
|Console simulator, multi-console management system and console management distribution system
|Jun 19, 1995
|Dec 9, 1997
|Compaq Computer Corporation
|Fault tolerant multiple network servers
|Nov 18, 1992
|Dec 9, 1997
|Canon Kabushiki Kaisha
|Method and apparatus for adaptively determining the format of data packets carried on a local area network
|Jun 15, 1995
|Dec 9, 1997
|Intel Corporation
|System for PCI slots expansion using asynchronous PCI-to-PCI bridge with clock generator for providing clock signal to the expansion mother board and expansion side of bridge
|Apr 15, 1996
|Dec 9, 1997
|Intel Corporation
|Architecture for implementing PCMCIA card services under the windows operating system in enhanced mode
|Mar 27, 1991
|Dec 23, 1997
|Microstar Laboratories
|Method and apparatus for providing initial instructions through a communications interface in a multiple computer system
|Dec 8, 1995
|Dec 30, 1997
|Fujitsu Limited
|Method of performing self-diagnosing hardware, software and firmware at a client node in a client/server system
|Oct 17, 1995
|Jan 13, 1998
|Fuji Xerox Co., Ltd.
|Fault information notification system localized at each network server
|May 9, 1996
|Jan 13, 1998
|Elonex I.P. Holdings
|Automatic recovery for network appliances
|Apr 15, 1996
|Jan 27, 1998
|Compaq Computer Corporation
|Hot plug protection system
|Feb 13, 1995
|Feb 3, 1998
|International Business Machines Corporation
|Method and apparatus for booting a computer system without pre-installing an operating system
|Oct 6, 1995
|Feb 10, 1998
|Elonex I.P. Holdings Ltd.
|Enhanced mini-tower computer architecture
|Feb 18, 1997
|Feb 24, 1998
|Compaq Computer Corporation
|Apparatus and method for entering low power mode in a computer system
|Nov 22, 1995
|Mar 3, 1998
|Cirrus Logic, Inc.
|Computer system with multiple PC card controllers and a method of controlling I/O transfers in the system
|Jun 5, 1995
|Mar 10, 1998
|Alantec Corporation
|Hot insertion power arrangement
|Sep 7, 1994
|Mar 10, 1998
|Adaptec, Inc.
|Method and apparatus for automatically loading configuration data on reset into a host adapter integrated circuit
|Oct 7, 1994
|Mar 17, 1998
|Dell Usa, L.P.
|System and method for accessing peripheral devices on a non-functional controller
|Sep 2, 1994
|Mar 24, 1998
|Compaq Computer Corporation
|Storage medium storing application programs and application initialization files and automatic launching of computer applications stored on the storage medium
|Nov 14, 1994
|Apr 7, 1998
|Qualcomm Incorporated
|Method for handling unrecognizable commands in a wireless environment
|Jun 10, 1996
|Apr 7, 1998
|Emc Corporation
|Prefetching to service multiple video streams from an integrated cached disk array
|Aug 17, 1995
|Apr 14, 1998
|Videoserver, Inc.
|Hot swap bus architecture
|Sep 11, 1996
|Apr 21, 1998
|Compaq Computer Corporation
|Integrated remote asynchronous power switch
|Nov 30, 1995
|Apr 21, 1998
|International Business Machines Corporation
|Programmable power management system and method for network computer stations
|Jul 31, 1996
|May 5, 1998
|Hewlett-Packard Company
|Redundant power supply and storage system
|Apr 29, 1996
|May 5, 1998
|Paradyne Corporation
|Method for interfacing to a powered bus
|Apr 25, 1995
|May 12, 1998
|American Pcs L.P.
|Autonomous remote measurement unit for a personal communications service system
|Feb 7, 1996
|May 19, 1998
|Mitsubishi Denki Kabushiki Kaisha
|Apparatus for allowing smooth hot insertion and removal of a peripheral by gradually applying and removing power to the peripheral
|Jul 7, 1995
|May 26, 1998
|Sun Microsystems, Inc.
|Local area network and network operating system for formatting a client disk and installing a client operating system
|Sep 5, 1996
|May 26, 1998
|Microsoft Corporation
|Common name space for long and short filenames
|Sep 9, 1996
|Jun 2, 1998
|Sejus Corporation
|Open computer system with externally interconnected peripheral modules
|Dec 22, 1995
|Jun 2, 1998
|Apple Computer, Inc.
|Modular, redundant, hot swappable, blind mate power supply system
|Nov 12, 1996
|Jun 2, 1998
|The United States Of America As Represented By The Secretary Of The Navy
|Method for monitoring environmental parameters at network sites
|Dec 13, 1996
|Jun 2, 1998
|International Business Machines Corporation
|Method and system for supporting peripheral component interconnect (PCI) peer-to-peer access across multiple PCI host bridges within a data-processing system
|Feb 28, 1996
|Jun 2, 1998
|Sun Microsystems, Inc.
|High speed flexible slave interface for parallel common bus to local cache buffer
|Aug 24, 1995
|Jun 9, 1998
|Ncr Corporation
|Method and apparatus for extending a local PCI bus to a remote I/O backplane
|Aug 5, 1996
|Jun 9, 1998
|Kabushiki Kaisha Toshiba
|Clock supply permission/inhibition control system
|Aug 8, 1996
|Jun 9, 1998
|International Business Machines Corporation
|Personal computer with riser card PCI and Micro Channel interface
|Feb 1, 1996
|Jun 9, 1998
|Cray Research, Inc.
|Transparent relocation of real memory addresses in the main memory of a data processor
|Feb 29, 1996
|Jun 16, 1998
|Sun Microsystems Inc
|Modified universal serial bus interface implementing remote power up while permitting normal remote power down
|Jun 15, 1995
|Jun 16, 1998
|Dell U.S.A., L.P.
|System for hot-plugging peripheral device to computer bus and disconnecting peripheral device upon detecting predetermined sequence of keystrokes inputted by user through keyboard
|Dec 27, 1996
|Jun 16, 1998
|Intel Corporation
|Method and apparatus for automatically configuring circuit cards in a computer system
|Feb 14, 1996
|Jun 23, 1998
|Sterling Commerce, Inc.
|System and method for failure detection and recovery
|Oct 21, 1991
|Jun 30, 1998
|Tandem Computers Incorporated
|Method and apparatus for providing a fault tolerant network interface controller
|Aug 29, 1995
|Jun 30, 1998
|Aerospatiale Societe Nationale Industrielle
|Process and device for identifying faults in a complex system
|Dec 30, 1996
|Jun 30, 1998
|Samsung Electronics Co., Ltd.
|Portable computer having a port connector for communicating with a variety of optional extension modules
|Nov 26, 1996
|Jul 7, 1998
|The United States Of America As Represented By The Secretary Of The Navy
|Method for optimizing the rotational speed of cooling fans
|Apr 26, 1996
|Jul 7, 1998
|International Business Machines Corp.
|Method for allocating system resources in a hierarchical bus structure
|Sep 6, 1996
|Jul 14, 1998
|Candle Distributed Solutions, Inc.
|Intelligent remote agent for computer performance monitoring
|Feb 19, 1997
|Jul 14, 1998
|Compaq Computer Corporation
|Fault tolerant multiple network servers
|Aug 25, 1995
|Jul 14, 1998
|Apple Computer, Inc.
|Method and apparatus for ensuring safe peripheral connection
|Oct 31, 1996
|Jul 14, 1998
|Hitachi, Ltd.
|Package blocking method for a storage system having a bus common to a plurality of kinds of groups of packages
|Nov 18, 1996
|Jul 14, 1998
|International Business Machines Corporation
|Method and apparatus for providing hot swapping capability in a computer system with static peripheral driver software
|Apr 18, 1996
|Jul 21, 1998
|Microsoft Corporation
|Automation and dial-time checking of system configuration for internet
|Oct 31, 1996
|Jul 21, 1998
|International Business Machines Corp.
|Method and apparatus for adding and removing components of a data processing system without powering down
|May 10, 1996
|Jul 28, 1998
|Apple Computer, Inc.
|System and method for handling dynamic changes in device states
|Dec 27, 1995
|Jul 28, 1998
|Emc Corporation
|Distributed disk array architecture
|Jan 26, 1996
|Jul 28, 1998
|Dell Usa Lp
|Fast method and apparatus for creating a partition on a hard disk drive of a computer system and installing software into the new partition
|Oct 23, 1995
|Aug 4, 1998
|Digital Equipment Corporation
|Host transparent storage controller failover/failback of SCSI targets and associated units
|Sep 18, 1996
|Aug 4, 1998
|Opti Inc.
|VL-bus/PCI-bus bridge
|Nov 27, 1995
|Aug 11, 1998
|Nec Corporation
|Method and apparatus for recording and analyzing an interaction log
|Jul 22, 1996
|Aug 11, 1998
|Cisco Systems, Inc.
|Hot plug port adapter with separate PCI local bus and auxiliary bus
|Jun 13, 1996
|Aug 11, 1998
|Vlsi Technology, Inc.
|Method and apparatus for arbitrating access to main memory of a computer system
|Apr 24, 1997
|Aug 11, 1998
|International Business Machines Corporation
|Device driver and input/output hardware research manager
|Oct 15, 1996
|Aug 18, 1998
|Sony Corporation
|Circuit card present sense and protective power supply inhibit for airborne application of ATM switch unit
|Apr 13, 1994
|Aug 18, 1998
|Hitachi, Ltd.
|Air-cooled information processing apparatus having cooling air fan, sub-fan, and plural separated cooling air flow channels
|May 31, 1996
|Aug 18, 1998
|Oracle Corporation
|Fault tolerant client server system
|Sep 16, 1994
|Aug 18, 1998
|Cirrus Logic, Inc.
|Method and apparatus for providing register compatibility between non-identical integrated circuits
|Jul 10, 1997
|Aug 18, 1998
|Digital Equipment Corporation
|Method and apparatus for fault tolerant BIOS addressing
|Mar 13, 1996
|Aug 25, 1998
|American Research Corporation Of Virginbia
|Laser aligned five-axis position measurement device
|Jun 29, 1995
|Aug 25, 1998
|Staples; Leven E.
|Computer system which provides analog audio communication between a PC card and the computer's sound system
|Jul 2, 1996
|Aug 25, 1998
|Gateway 2000, Inc.
|Method and apparatus of providing power management using a self-powered universal serial bus (USB) device
|Nov 19, 1996
|Sep 1, 1998
|Symex, Inc.
|Integrated data, voice, and video communication network
|Jun 28, 1996
|Sep 1, 1998
|Intel Corporation
|Method and apparatus for power management of distributed direct memory access (DDMA) devices
|Aug 26, 1996
|Sep 1, 1998
|Fujitsu Limited
|Defect-free type remote procedure call system and method thereof
|May 17, 1996
|Sep 1, 1998
|Microsoft Corporation
|System for remotely waking a sleeping computer in power down state by comparing incoming packet to the list of packets storing on network interface card
|Dec 23, 1996
|Sep 1, 1998
|Compaq Computer Corporation
|Computer system with PCI repeater between primary bus and second bus
|Apr 22, 1997
|Sep 1, 1998
|International Business Machines Corporation
|Computer system for detecting and accessing BIOS ROM on local bus peripheral bus or expansion bus
|Oct 1, 1997
|Sep 1, 1998
|Intel Corporation
|System and method for allocating and sharingpage buffers for a flash memory device
|May 31, 1996
|Sep 1, 1998
|International Business Machines Corporation
|System and method for protecting integrity of alterable ROM using digital signatures
|Feb 19, 1997
|Sep 8, 1998
|Coleman Safety And Security Products, Inc.
|Thermostat with remote temperature sensors and incorporating a measured temperature feature for averaging ambient temperatures at selected sensors
|Mar 12, 1997
|Sep 8, 1998
|Oracle Corporation
|Method and apparatus for scalable, high bandwidth storage retrieval and transportation of multimedia data on a network
|Aug 1, 1996
|Sep 8, 1998
|Zilog, Inc.
|Hot reconfigurable parallel bus bridging circuit
|Oct 13, 1995
|Sep 15, 1998
|Compaq Computer Corporation
|On-line disk array reconfiguration
|Jun 11, 1996
|Sep 15, 1998
|Data General Corporation
|Soft power switching for hot installation and removal of circuit boards in a computer system
|Dec 17, 1996
|Sep 15, 1998
|Compaq Computer Corporation
|Automatic computer upgrading
|Jun 14, 1996
|Sep 15, 1998
|Dell U.S.A., L.P.
|System and method for providing centralized backup power in a computer system
|Dec 15, 1995
|Sep 15, 1998
|Compaq Computer Corporation
|Method of determining sizes of 1:1 and 2:1 memory interleaving in a computer system, configuring to the maximum size, and informing the user if memory is incorrectly installed
|May 16, 1995
|Sep 22, 1998
|Vinca Corporation
|Method for improving recovery performance from hardware and software errors in a fault-tolerant computer system
|Mar 27, 1997
|Sep 22, 1998
|Cabletron Systems, Inc.
|Method and apparatus for monitoring the status of non-pollable devices in a computer network
|Jul 5, 1996
|Sep 22, 1998
|Mitsubishi Denki Kabushiki Kaisha
|Processing board, a computer, and a fault recovery method for the computer
|Sep 25, 1996
|Sep 22, 1998
|Cirrus Logic, Inc.
|Method and apparatus for providing register and interrupt compatibility between non-identical integrated circuits
|Jan 2, 1997
|Sep 29, 1998
|Raytheon Company
|Digital direction finding receiver
|May 23, 1997
|Sep 29, 1998
|International Business Machines Corporation
|Error recovery by isolation of peripheral components in a data processing system
|Sep 6, 1996
|Sep 29, 1998
|Digital Equipment Corporation
|Method and apparatus for CPU failure recovery in symmetric multi-processing systems
|May 30, 1996
|Sep 29, 1998
|Hitachi, Ltd.
|Computer management system
|Mar 24, 1997
|Oct 13, 1998
|Integrated Micromachines, Inc.
|Batch fabricated semiconductor micro-switch
|May 31, 1996
|Oct 13, 1998
|Texas Instruments Incorporated
|Method and apparatus for providing a portable computer with hot pluggable modular bays
|Feb 3, 1997
|Oct 20, 1998
|Ast Research, Inc.
|Docking station with serially accessed memory that is powered by a portable computer for identifying the docking station
|Jun 10, 1996
|Oct 27, 1998
|Emc Corporation
|On-line tape backup using an integrated cached disk array
|Nov 17, 1997
|Nov 10, 1998
|Advanced Micro Devices, Inc.
|Apparatus and method for remote wake-up in system having interlinked networks
|Jun 24, 1996
|Nov 10, 1998
|International Business Machines Corporation
|Address space architecture for multiple bus computer systems
|Jun 30, 1997
|Nov 17, 1998
|Compaq Computer Corporation
|Transparent PCI to PCI bridge with dynamic memory and I/O map programming
|Dec 29, 1995
|Nov 17, 1998
|Intel Corporation
|Method and apparatus providing programmable decode modes for secondary PCI bus interfaces
|Jun 20, 1996
|Nov 24, 1998
|Canon Kabushiki Kaisha
|Operating state management system
|Nov 18, 1992
|Nov 24, 1998
|Canon Information Systems, Inc.
|In an Interactive network board, a method and apparatus for storing a media access control address in a remotely alterable memory
|Oct 26, 1995
|Dec 1, 1998
|Hitachi, Ltd.
|Redundant client server system
|Jul 21, 1995
|Dec 1, 1998
|Motorola Inc.
|Method and apparatus for storing and restoring controller configuration information in a data communication system
|Dec 6, 1996
|Dec 15, 1998
|Samsung Electronics Co., Ltd.
|Central processing unit reset device and a reset method for a central processing unit
|Aug 16, 1996
|Dec 22, 1998
|Compaq Computer Corp.
|System for storing display data during first time period prior to failure of computer and during second time period after reset of the computer
|Jun 18, 1996
|Dec 22, 1998
|Veritas Software Corp.
|System and method for "N" primary servers to fail over to "1" secondary server
|Aug 16, 1996
|Jan 5, 1999
|Compaq Computer Corp.
|Server controller responsive to various communication protocols for allowing remote communication to a host computer connected thereto
|Mar 14, 1995
|Jan 5, 1999
|Sun Microsystems, Inc.
|System and method for determining and manipulating configuration information of servers in a distributed object environment
|Dec 31, 1996
|Jan 26, 1999
|Compaq Computer Corporation
|PCI hot spare capability for failed components
|Feb 19, 1997
|Jan 26, 1999
|Nec Electronics, Inc.
|Systems and methods for fault tolerant information processing
|Feb 12, 1996
|Jan 26, 1999
|Hewlett-Packard Company
|Method for determining if data should be written at the beginning of a buffer depending on space available after unread data in the buffer
|Jul 31, 1997
|Feb 2, 1999
|Micron Eletronics, Inc.
|Method for configuration of peripherals by interpreting response from peripherals to enable selection of driver file and altering configuration file to enable loading of selected driver file
|Aug 14, 1997
|Feb 23, 1999
|National Semiconductor Corporation
|Method and apparatus to enable docking/undocking of a powered-on bus to a docking station
|Jun 18, 1997
|Feb 23, 1999
|International Business Machines Corporation
|Peripheral component interconnect (PCI) architecture having hot-plugging capability for a data-processing system
|May 24, 1996
|Feb 23, 1999
|International Business Machines Corporation
|Secondary I/O bus with expanded slot capacity and hot plugging capability
|Jul 11, 1997
|Mar 2, 1999
|Compaq Computer Corp.
|Apparatus, method and system for a comuter CPU and memory to PCI bridge having a pluarlity of physical PCI buses
|Aug 7, 1997
|Mar 2, 1999
|Dell Usa, L.P.
|Technique for supporting semi-compliant PCI devices behind a PCI-to-PCI bridge
|Jun 5, 1996
|Mar 9, 1999
|Fastor Technologies, Inc.
|Data storage subsystem with block based data management
|Jun 5, 1997
|Mar 16, 1999
|Intel Corporation
|Architecture for an I/O processor that integrates a PCI to PCI bridge
|Dec 31, 1996
|Mar 16, 1999
|Compaq Computer Corporation
|Increased processor performance comparable to a desktop computer from a docked portable computer
|Jul 10, 1997
|Mar 23, 1999
|Samsung Electronics Co., Ltd.
|Power supply apparatus for portable computer and DC input selection circuit adapted to the same
|Oct 1, 1997
|Mar 30, 1999
|Micron Electronics, Inc.
|Method for the hot swap of a network adapter on a system including a dynamically loaded adapter driver
|Oct 4, 1996
|Apr 6, 1999
|Honeywell, Inc.
|Error management system for supporting the identification and logging of error messages
|May 5, 1997
|Apr 6, 1999
|Emc Corporation
|System having client sending edit commands to server during transmission of continuous media from one clip in play list for editing the play list
|Oct 1, 1997
|Apr 6, 1999
|Micron Electronics, Inc.
|Method for the hot add of a network adapter on a system including a dynamically loaded adapter driver
|Nov 13, 1996
|Apr 6, 1999
|Emc Corporation
|File server having a file system cache and protocol for truly safe asynchronous writes
|Dec 8, 1997
|Apr 27, 1999
|Kelly; Michael
|CPU interconnect system for a computer
|Dec 13, 1996
|Apr 27, 1999
|International Business Machines Corporation
|Method and system for translating peripheral component interconnect (PCI) peer-to-peer access across multiple PCI host bridges within a computer system
|Nov 12, 1996
|May 18, 1999
|The United States Of America As Represented By The Secretary Of The Navy
|Apparatus for monitoring environmental parameters at network sites
|Oct 4, 1995
|May 25, 1999
|Stac, Inc.
|System for backing up computer disk volumes with error remapping of flawed memory addresses
|Sep 3, 1996
|Jun 1, 1999
|Apple Computer, Inc.
|Process and apparatus for transferring data between different file formats
|Mar 31, 1997
|Jun 15, 1999
|Emc Corporation
|Storage device array architecture with copyback cache
|Aug 27, 1996
|Jun 15, 1999
|Compaq Computer Corp.
|Administrator station for a computer system
|Mar 20, 1997
|Jun 29, 1999
|Industrial Technology Research Institute
|Method and apparatus for dispatching multiple interrupt requests simultaneously
|Dec 31, 1996
|Jul 13, 1999
|Compaq Computer Corporation
|Expansion card insertion and removal
|Nov 22, 1996
|Jul 13, 1999
|International Business Machines Corporation
|Virtual internet protocol (IP) addressing
|Mar 13, 1997
|Jul 27, 1999
|Mitsubishi Chemical America, Inc.
|Storage device having a nonvolatile memory for storing user changeable operating parameters
|Jun 9, 1995
|Aug 10, 1999
|Canon Information Systems, Inc.
|Outputting a network device log file
|Aug 21, 1997
|Aug 10, 1999
|Advanced Micro Devices, Inc.
|Apparatus for and method of communicating among devices interconnected on a bus
|Aug 15, 1997
|Aug 17, 1999
|Compaq Computer Corporation
|Bus ring-back and voltage over-shoot reduction techniques coupled with hot-pluggability
|Jul 25, 1997
|Aug 24, 1999
|Merrill Lynch & Company, Incorporated
|Distributed network agents
|Apr 7, 1997
|Oct 12, 1999
|International Business Machines Corporation
|Method and system for enabling nondisruptive live insertion and removal of feature cards in a computer system
|Mar 5, 1998
|Nov 9, 1999
|Sony Corporation
|Changer apparatus, method for locking security protection thereof, method for unlocking executing commands thereon, and computer for sending commands thereto
|Oct 1, 1997
|Nov 16, 1999
|Micron Electronics, Inc.
|Method of controlling the transfer of information across an interface between two buses
|May 5, 1997
|Nov 16, 1999
|Emc Corporation
|Hardware and software failover services for a file server
|Oct 27, 1992
|Nov 16, 1999
|Rawlings, Iii; Joseph H.
|Methods and apparatus for high-speed mass storage access in a computer system
|Sep 4, 1997
|Jan 4, 2000
|Siemens Information And Communication Networks, Inc.
|Method and apparatus for automated disk drive upgrades
|Cmasters, Usenet post to microsoft.public.windowsnt.setup, Aug. 1997, "Re: FDISK switches.".
|Compaq Computer Corporation, Phenix Technologies, LTD, and Intel Corporation, specification, 55 pages, May 5, 1994, "Plug & Play BIOS Specification.".
|Compaq Computer Corporation, Technology Brief, pp. 1-13, Dec. 1996, "Where Do I Plug the Cable? Solving the Logical-Physical Slot Numbering Problem.".
|Davis, T, Usenet post to alt.msdos.programmer, Apr. 1997, "Re: How do I create an FDISK batch file?".
|Davis, T., Usenet post to alt.msdos.batch, Apr. 1997, "Re: Need help with automating FDISK and FORMAT . . . ".
|Digital Equipment Corporation, datasheet, 140 pages, 1993, "DECchip 21050 PCI-TO-PCI Bridge.".
|ftp.cdrom.com/pub/os2/diskutil/, PHDX software, phdx.zip download, Mar. 1995, "Parallel Hard Disk Xfer.".
|Gorlick, M., Conf. Proceedings: ACM/ONR Workshop on Parallel and Distribution Debugging, pp. 175-181, 1991, "The Flight Recorder: An Architectural Aid for System Monitoring.".
|Haban, D. & D. Wybranietz, IEEE Transaction on Software Engineering, 16(2):197-211, Feb. 1990, "A Hybrid Monitor for Behavior and Performance Analysis of Distributed Systems."
|Herr, et al., Linear Technology Magazine, Design Features, pp. 21-23, Jun. 1997, "Hot Swapping the PCI Bus.".
|Hildebrand, N., Usenet post to comp.msdos.programmer, May 1995, "Re: Structure of disk partition into.".
|IBM Technical Disclosure Bulletin, 92A+62947, pp. 391-394, Oct. 1992, Method for Card Hot Plug Detection and Control.
|Joint work by Intel Corporation, Compaq, Adaptec, Hewlett Packard, and Novell, presentation, 22 pages, Jun. 1996, "Intelligent I/O Architecture.".
|Lewis, L., Usenet post to alt.msdos.batch, Apr. 1997, "Re: Need help with automating FDISK and FORMAT.".
|Lockareff, M., HTINews, http://www.hometoys.com/htinews/dec96/articles/Ionworks.htm, 2 pages, Dec. 1996, "Loneworks-An Introduction.".
|Lockareff, M., HTINews, http://www.hometoys.com/htinews/dec96/articles/Ionworks.htm, 2 pages, Dec. 1996, "Loneworks—An Introduction.".
|Lyons, Computer Reseller News, Issue 721, pp. 61-62, Feb. 3, 1997, "ACC Releases Low-Cost Solution for ISPs.".
|M2 Communications, M2 Presswire, 2 pages, Dec. 19, 1996, "Novell IntranetWare Supports Hot Pluggable PCI from NetFRAME.".
|Microsoft Corporation, file:///A|/Rem_devs.htm, 4 pages, Copyright 1997, updated Aug. 13, 1997, "Supporting Removable Devices Under Windows and Windows NT.".
|NetFRAME Systems Incorporated, datasheet, 2 pages, Feb. 1996, "NF450FT Network Mainframe.".
|NetFRAME Systems Incorporated, datasheet, 9 pages, Mar. 1996, "NetFRAME Cluster Server 8000.".
|NetFrame Systems Incorporated, Doc. No. 78-1000226-01, pp. 1-2, 5-8, 359-404, and 471-512, Apr. 1996, "NetFrame Clustered Multiprocessing Software: NW0496 DC-ROM for Novel(R) NetWare(R) 4.1 SMP, 4.1, and 3.12.".
|NetFrame Systems Incorporated, Doc. No. 78-1000226-01, pp. 1-2, 5-8, 359-404, and 471-512, Apr. 1996, "NetFrame Clustered Multiprocessing Software: NW0496 DC-ROM for Novel� NetWare� 4.1 SMP, 4.1, and 3.12.".
|NetFRAME Systems Incorporated, News Release, 3 pages, referring to May 9, 1994, "NetFRAME's New High-Availability ClusterServer Systems Avoid Scheduled as well as Unscheduled Downtime.".
|Netframe, http://www.netframe-support.com/technology/datasheets/data.htm, before Mar. 1997, "Netframe ClusterSystem 9008 Data Sheet.".
|NTRR, Ltd, http://www.nrtt.demon.co.uk/cantech.html, 5 pages, May 28, 1997, "CAN: Technical Overview.".
|PCI Hot-Plug Specification, Preliminary Revision for Review Only, Revision 0.9, pp. i-vi, and 1-25, Mar. 5, 1997.
|PCI Special Interest Group, specification, 35 pages, Draft For Review Only, Jun. 15, 1997, "PCI Bus Hot Plug Specification.".
|Rigney, PC Magazine, 14(17): 375-379, Oct. 10, 1995, "The One for the Road (Mobile-aware capabilities in Windows 95).".
|Schofield, M.J., http://www.omegas.co.uk/CAN/canworks.htm, 4 pages, Copyright 1996, 1997, "Controller Area Network-How CAN Works.".
|Schofield, M.J., http://www.omegas.co.uk/CAN/canworks.htm, 4 pages, Copyright 1996, 1997, "Controller Area Network—How CAN Works.".
|SES SCSI-3 Enclosure Services, X3T10/Project 1212-D/Rev 8a, pp. i, iii-x, 1-76, and I-1 (index), Jan. 16, 1997.
|Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 15, pp. 297-302, Copyright 1995, "Intro To Configuration Address Space.".
|Shanley, and Anderson, PCI System Architecture, Third Edition, Chapter 16, pp. 303-328, Copyright 1995, "Configuration Transactions.".
|Shanley, and Anderson, PCI System Architecture, Third Edition, p. 382, Copyright 1995.
|Simos, M., Usenet post to comp.os.msdos.misc, Apr. 1997, "Re: Auto FDISK and FORMAT.".
|Standard Overview, http://www.pc-card.com/stand_overview.html#1, 9 pages, Jun. 1990, "Detailed Overview of the PC Card Standard.".
|Sun Microsystems Computer Company, Part No. 802-5355-10, Rev. A, May 1996, "Solstice SyMON User's Guid.".
|Sun Microsystems, Part No. 802-6569-11, Release 1.0.1, Nov. 1996, "Remote Systems Diagnostics Installation & User Guide.".
|Wood, M. H., Usenet post to comp.os.netware.misc, Aug. 1996, "Re: Workstation duplication method for WIN95.".
|Citing Patent
|Filing date
|Publication date
|Mar 29, 1999
|Apr 23, 2002
|Hewlett-Packard Company
|Enclosure processor with failover capability
|Mar 1, 1999
|Sep 17, 2002
|Sun Microsystems, Inc.
|High performance network interface
|Mar 18, 1999
|Dec 3, 2002
|3Com Corporation
|High performance load balancing and fail over support of internet protocol exchange traffic over multiple network interface cards
|Aug 23, 1999
|Dec 24, 2002
|Advanced Micro Devices, Inc.
|Redirecting I/O address holes
|Mar 18, 1999
|May 6, 2003
|3Com Corporation
|Receive load balancing and fail over with multiple network interface cards
|Jan 11, 1999
|Jul 15, 2003
|Yokogawa Electric Corporation
|Communication control system
|Apr 27, 2000
|Sep 16, 2003
|Hewlett-Packard Development Company, L.P.
|Method and system for updating routes in a route table on a client computer
|Oct 2, 2000
|Nov 11, 2003
|International Business Machines Corporation
|Determination of the degree of common usage for elements of a data processing system
|Mar 17, 2001
|Jan 6, 2004
|Hewlett-Packard Development Company, L.P.
|Communication bus controller including designation of primary and secondary status according to slot position
|Sep 5, 2002
|Apr 13, 2004
|International Business Machines Corporation
|Remote direct memory access enabled network interface controller switchover and switchback support
|Oct 31, 2001
|Jul 20, 2004
|Extreme Networks
|Ethernet automatic protection switching
|Nov 18, 1999
|Mar 29, 2005
|Intel Corporation
|Apparatus and method for networking driver protocol enhancement
|Nov 12, 1999
|Feb 21, 2006
|Ntt Docomo, Inc.
|Communication control method, communication control apparatus and storage medium
|Dec 31, 1999
|Jul 25, 2006
|Intel Corporation
|Method and apparatus for accelerating hardware encryption with multiple networking interfaces
|Mar 31, 2004
|Aug 8, 2006
|International Business Machines Corporation
|Method and apparatus for supporting interrupt devices configured for a particular architecture on a different platform
|Apr 2, 2003
|Sep 26, 2006
|International Business Machines Corporation
|State recovery and failover of intelligent network adapters
|Jun 29, 2001
|Oct 17, 2006
|Intel Corporation
|Intelligently determining which traffic streams to offload efficiently
|May 16, 2000
|Dec 12, 2006
|Lucent Technologies Inc.
|System and method for peer-level communication with a network interface card
|Aug 23, 2002
|Dec 19, 2006
|Intel Corporation
|General input/output architecture, protocol and related methods to manage data integrity
|Aug 22, 2002
|Feb 13, 2007
|Intel Corporation
|General input/output architecture, protocol and related methods to provide isochronous channels
|Aug 23, 2002
|Jun 12, 2007
|Intel Corporation
|General input/output architecture, protocol and related methods to support legacy interrupts
|Aug 5, 2003
|Oct 9, 2007
|Apple Inc.
|Method and apparatus for border node behavior on a full-duplex bus
|Aug 5, 2003
|Oct 9, 2007
|Apple Inc.
|Method and apparatus for border node behavior on a full-duplex bus
|Feb 4, 2005
|Nov 6, 2007
|Inventec Corporation
|Computer peripheral connecting interface system configuration debugging method and system
|Mar 7, 2002
|Dec 4, 2007
|Nokia Corporation
|Method and apparatus for clustered SSL accelerator
|Aug 5, 2003
|Jan 8, 2008
|Apple Inc.
|Method and apparatus for border node behavior on a full-duplex bus
|Oct 23, 2006
|Apr 1, 2008
|Intel Corporation
|General input/output architecture, protocol and related methods to manage data integrity
|Jan 31, 2005
|Mar 17, 2009
|International Business Machines Corporation
|Method, apparatus and program storage device for providing mutual failover and load-balancing between interfaces in a network
|Aug 23, 2002
|May 19, 2009
|Intel Corporation
|General input/output architecture, protocol and related methods to implement flow control
|Dec 20, 2004
|Oct 6, 2009
|Mitac Technology Corp.
|Network setting configuration systems and methods
|Nov 21, 2005
|Dec 1, 2009
|Ntt Docomo, Inc.
|Communication control method, communication control apparatus and storage medium
|Jan 11, 2006
|Dec 8, 2009
|Intel Corporation
|Subnet independent transparent bridge
|Aug 6, 2004
|Mar 16, 2010
|Logic Controls, Inc.
|Diagnostic method and apparatus for detecting and locating computer network discontinuities
|Dec 15, 2005
|Apr 6, 2010
|Nvidia Corporation
|Single logical network interface for advanced load balancing and fail-over functionality
|Apr 27, 2001
|Apr 27, 2010
|Airsys Atm S.A.
|Redundant input/output management device, notably for data routing
|Sep 1, 2005
|Jul 27, 2010
|Intel Corporation
|Intermediate driver having a fail-over function
|Aug 22, 2008
|Mar 1, 2011
|Polycom, Inc.
|Method and system for assigning a plurality of MACs to a plurality of processors
|Nov 20, 2008
|Mar 8, 2011
|International Business Machines Corporation
|Method, apparatus and program storage device for providing mutual failover and load-balancing between interfaces in a network
|Dec 17, 2002
|Apr 26, 2011
|Hewlett-Packard Development Company, L.P.
|Method and system for performing load balancing across control planes in a data center
|Jun 8, 2009
|Apr 26, 2011
|Broadcom Corporation
|System and method for network interfacing
|May 3, 2011
|Xsigo Systems
|Communication between computer systems over an input/output (I/O) bus
|Jan 28, 2009
|Jun 7, 2011
|Huawei Technologies Co., Ltd.
|Method and system for synchronization of packet
|Aug 30, 2011
|Broadcom Corporation
|System and method for network interfacing
|Dec 19, 2006
|Oct 11, 2011
|Brother Kogyo Kabushiki Kaisha
|Processing method and apparatus for communication path load distribution
|Aug 17, 2004
|Oct 25, 2011
|Swisscom Ag
|Method and system for mobile IP-nodes in heterogeneous networks
|Sep 20, 2010
|Nov 1, 2011
|International Business Machines Corporation
|Self-healing chip-to-chip interface
|Dec 30, 2009
|Nov 15, 2011
|Halliburton Energy Services Inc.
|Consumable downhole tools
|Dec 15, 2005
|Mar 13, 2012
|Nvidia Corporation
|Technique for identifying a failed network interface card within a team of network interface cards
|Nov 8, 2005
|Apr 17, 2012
|Nvidia Corporation
|Memory interface with dynamic selection among mirrored storage locations
|Jun 23, 2003
|May 1, 2012
|Siemens Aktiengesellschsft
|Computer system connected to a data communications network
|Mar 17, 2009
|May 29, 2012
|Fujitsu Limited
|Apparatus and method for forwarding packet data
|Aug 13, 2008
|Aug 7, 2012
|Robertson Intellectual Properties, LLC
|Consumable downhole tool
|Feb 14, 2002
|Aug 14, 2012
|Marvell International Ltd.
|Method and apparatus for enabling a network interface to support multiple networks
|Aug 20, 2010
|Sep 4, 2012
|Halliburton Energy Services Inc.
|Consumable downhole tools
|Nov 10, 2011
|Sep 25, 2012
|Halliburton Energy Services Inc.
|Method for removing a consumable downhole tool
|Nov 10, 2011
|Oct 23, 2012
|Halliburton Energy Services Inc.
|Consumable downhole tools
|May 18, 2007
|Oct 30, 2012
|Nvidia Corporation
|Intelligent load balancing and failover of network traffic
|Oct 19, 2011
|Dec 4, 2012
|Halliburton Energy Services, Inc.
|Consumable downhole tools
|Aug 13, 2008
|Dec 11, 2012
|Robertson Intellectual Properties, LLC
|Method for removing a consumable downhole tool
|Jun 23, 2011
|Apr 23, 2013
|Intel Corporation
|Failover and load balancing
|May 18, 2007
|Apr 30, 2013
|Nvidia Corporation
|Intelligent failback in a load-balanced networking environment
|Aug 13, 2012
|May 21, 2013
|Marvell International Ltd.
|Method and apparatus for enabling a network interface to support multiple networks
|Feb 27, 2009
|Oct 22, 2013
|Intel Corporation
|General input/output architecture, protocol and related methods to implement flow control
|Dec 15, 2005
|Oct 29, 2013
|Nvidia Corporation
|Single logical network interface for advanced load balancing and fail-over functionality
|Aug 29, 2003
|Jan 14, 2014
|Broadcom Corporation
|System and method for network interfacing in a multiple network environment
|Jun 3, 2005
|Mar 18, 2014
|Oracle International Corporation
|High availability and I/O aggregation for server environments
|Oct 28, 2009
|May 13, 2014
|International Business Machines Corporation
|Zero packet loss energy efficient ethernet link transition via driver fast failover
|Dec 28, 2012
|Aug 26, 2014
|Intel Corporation
|General input/output architecture with PCI express protocol with credit-based flow control
|May 15, 2013
|Nov 11, 2014
|Marvell International Ltd.
|Method and apparatus for enabling a network interface to support multiple networks
|Dec 28, 2012
|Jun 2, 2015
|Intel Corporation
|General input/output architecture, protocol and related methods to implement flow control
|Dec 28, 2012
|Jun 30, 2015
|Intel Corporation
|General input/output architecture, protocol and related methods to implement flow control
|Dec 28, 2010
|Jul 14, 2015
|Crimson Corporation
|Retransmitting lost packets for multicast data distribution
|Oct 29, 2012
|Jul 14, 2015
|Oracle International Corporation
|Network virtualization over infiniband
|Jan 13, 2014
|Jul 21, 2015
|Broadcom Corporation
|System and method for network interfacing in a multiple network environment
|Dec 28, 2012
|Jul 21, 2015
|Intel Corporation
|General input/output architecture, protocol and related methods to implement flow control
|Apr 27, 2001
|Jan 24, 2002
|Airsys Atm Sa
|Redundant input/output management device, notably for data routing
|Dec 19, 2000
|Jun 20, 2002
|Young Gene F.
|High density serverlets utilizing high speed data bus
|Aug 23, 2002
|Jun 19, 2003
|Jasmin Ajanovic
|General input/output architecture, protocol and related methods to support legacy interrupts
|Aug 23, 2002
|Jul 31, 2003
|Wehage Eric R.
|General input/output architecture, protocol and related methods to manage data integrity
|Aug 23, 2002
|Aug 21, 2003
|Jasmin Ajanovic
|General input/output architecture, protocol and related methods to implement flow control
|Aug 29, 2003
|May 13, 2004
|Uri Elzur
|System and method for network interfacing
|Dec 17, 2002
|Jun 17, 2004
|Doug Steele
|Method and system for performing load balancing across control planes in a data center
|Apr 2, 2003
|Oct 7, 2004
|International Business Machines Corporation
|State recovery and failover of intelligent network adapters
|Jul 10, 2003
|Jan 13, 2005
|International Business Machines Corporation
|Method and apparatus for managing adapters in a data processing system
|Sep 24, 2003
|Mar 24, 2005
|Stachura Thomas L.
|Method and apparatus for alert failover
|Sep 25, 2003
|Mar 31, 2005
|Klein Dean A.
|Secure processor-based system and method
|Oct 16, 2003
|Apr 21, 2005
|International Business Machines Corporation
|Efficient packet desegmentation on a network adapter
|Mar 31, 2004
|Oct 13, 2005
|International Business Machines Corporation
|Method and apparatus for supporting interrupt devices configured for a particular architecture on a different platform
|Aug 6, 2004
|Feb 9, 2006
|Logic Controls, Inc.
|Diagnostic method and apparatus for detecting and locating computer network discontinuities
|Oct 22, 2004
|Apr 27, 2006
|Linden Cornett
|Modular SDD (scalable device driver) framework
|Dec 20, 2004
|Jun 22, 2006
|Mitac Technology Corp.
|Network setting configuration systems and methods
|Feb 4, 2005
|Jun 22, 2006
|Inventec Corporation
|Computer peripheral connecting interface system configuration debugging method and system
|Nov 21, 2005
|Jul 20, 2006
|Ntt Docomo, Inc.
|Communication control method, communication control apparatus and storage medium
|Jan 31, 2005
|Aug 3, 2006
|Vivek Kashyap
|Method, apparatus and program storage device for providing mutual failover and load-balancing between interfaces in a network
|Sep 1, 2005
|Sep 7, 2006
|Intel Corporation
|Intermediate driver having a fail-over function
|Jan 11, 2006
|Sep 21, 2006
|Blum Scott B
|Subnet independent transparent bridge
|Oct 23, 2006
|Feb 15, 2007
|Wehage Eric R
|General input/output architecture, protocol and related methods to manage data integrity
|Oct 28, 2009
|Apr 28, 2011
|International Business Machines Corporation
|Zero Packet Loss Energy Efficient Ethernet Link Transition Via Driver Fast Failover
|Oct 20, 2011
|Alexander Belyakov
|Failover and load balancing
|Jan 30, 2013
|Sep 19, 2013
|Huawei Technologies Co., Ltd.
|Integrated circuit and method for monitoring bus status in integrated circuit
|Mar 18, 2004
|Sep 22, 2004
|Broadcom Corporation
|System and method for network interfacing (FKA mechanism for handling out-of-order TCP/IP frames)
|Mar 18, 2004
|Sep 22, 2004
|Broadcom Corporation
|System and method for network interfacing in a multiple network environment
|Aug 29, 2003
|Jun 15, 2005
|Broadcom Corporation
|System and method for network interfacing in a multiple network environment
|Dec 20, 2001
|Jul 4, 2002
|Siemens Ag
|Computer system that can be connected to a data transmission network
|U.S. Classification
|714/4.12, 710/312, 718/105, 714/43, 709/239
|International Classification
|Cooperative Classification
|European Classification
|Mar 19, 1998
Owner name: MICRON ELECTRONICS, INC., IDAHO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:AMDAHL, CARLTON G.;SMITH, DENNIS H.;AGNETA, DON A.;REEL/FRAME:009049/0719
Effective date: 19980210
|Mar 30, 2001
|Oct 22, 2001
|Sep 27, 2004
|Fee payment
Year of fee payment: 4
|Nov 26, 2008
|Fee payment
Year of fee payment: 8
|Oct 1, 2012
|Fee payment
Year of fee payment: 12