|Publication number||US7636772 B1|
|Application number||US 09/692,365|
|Publication date||Dec 22, 2009|
|Priority date||Oct 19, 2000|
|Publication number||09692365, 692365, US 7636772 B1, US 7636772B1, US-B1-7636772, US7636772 B1, US7636772B1|
|Inventors||Orvalle Theodore Kirby, Gregory Michael Nordstrom, Gregory Francis Pfister, Renato John Recio, Steven Mark Thurber|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (71), Non-Patent Citations (1), Referenced by (13), Classifications (12), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention is related to applications entitled System Area Network of End-to-End Context via Reliable Datagram Domains, Ser. No. 09/692,354, now U.S. Pat. No. 6,990,528; Method and Apparatus for Pausing a Send Queue without Causing Sympathy Errors, Ser. No. 09/692,340, now U.S. Pat. No. 6,766,467; Method and Apparatus to Perform Fabric Management, Ser. No. 09/692,344, now U.S. Pat. No. 6,978,300; End Node Partitioning using LMC for a System Area Network, Ser. No. 09/692,351, now U.S. Pat. No. 7,099,955; Method and Apparatus for Retaining Network Security Settings Across Power Cycles, Ser. No. 09/692,337, now abandoned; Method and Apparatus for Reporting Unauthorized Attempts to Access Nodes in a Network Computing System, Ser. No. 09/692,348, now U.S. Pat. No. 7,113,995; Method and Apparatus for Reliably Choosing a Master Network Manager During Initialization of a Network Computing System, Ser. No. 09/692,346, now U.S. Pat. No. 6,941,350; Method and Apparatus for Ensuring Scalable Mastership During Initialization of a System Area Network, Ser. No. 09/692,341, now U.S. Pat. No. 6,981,025; and Method and Apparatus for Using a Service ID for the Equivalent of Port ID in a Network Computing System, Ser. No. 09/692,352, now abandoned, all of which are filed even date hereof, assigned to the same assignee, and incorporated herein by reference.
1. Technical Field
The present invention relates generally to an improved data processing system, and in particular to a method and apparatus for managing a network computing system. Still more particularly, the present invention provides a method and apparatus for retaining configuration and management information for a network computing system.
2. Description of Related Art
In a System Area Network (SAN), the hardware provides a message passing mechanism which can be used for Input/Output devices (I/O) and interprocess communications between general computing nodes (IPC). Processes executing on devices access SAN message passing hardware by posting send/receive messages to send/receive work queues on a SAN channel adapter (CA). These processes also are referred to as “consumers”. The send/receive work queues (WQ) are assigned to a consumer as a queue pair (QP). The messages can be sent over five different transport types: Reliable Connected (RC), Reliable datagram (RD), Unreliable Connected (UC), Unreliable Datagram (UD), and Raw Datagram (RawD). Consumers retrieve the results of these messages from a completion queue (CQ) through SAN send and receive work completions (WC). The source channel adapter takes care of segmenting outbound messages and sending them to the destination. The destination channel adapter takes care of reassembling inbound messages and placing them in the memory space designated by the destination's consumer. Two channel adapter types are present, a host channel adapter (HCA) and a target channel adapter (TCA). The host channel adapter is used by general purpose computing nodes to access the SAN fabric. Consumers use SAN verbs to access host channel adapter functions. The software that interprets verbs and directly accesses the channel adapter is known as the channel interface (CI).
Within a SAN, the different consumers execute on nodes or devices within a node. For example, a node may be a host channel processor or a switch, while a device may be a channel adapter within a host channel processor. In managing the SAN, different nodes may be turned on and off at different times. Additionally, in some cases all of the nodes within the SAN may be powered on at the same time. In powering on nodes, the nodes are initialized and nodes within the SAN are discovered. In this situation, large initialization or boot times may occur, which results in lost time and possibly frustration to a user of the SAN.
In addition, after initialization, a customer may change the assignments made automatically by the subnet manager. Changes that a customer may want to make include: creation of multiple partitions, ports participating in a specific partition, and service levels that can be used by a given port. Without the ability to retain these manual changes, after each initialization the customer would have to redo all the assignments he had previously made.
Therefore, it would be advantageous to have an improved method and apparatus for increasing the speed at which configuration of nodes occur during initialization of the nodes, as well as maintaining manual configuration changes made by the customer.
The present invention provides a method in a network computing system for managing configuration information for a set of components in a network computing system. The configuration information is stored for the set of components in the network computing system to form stored configuration information. In the depicted examples, the components may be nodes or devices within nodes. Current configuration is obtained in response to a power cycle. The current configuration information is compared with the stored configuration information to form a comparison. The stored configuration information is updated if a difference is present in the comparison. The stored configuration information is used to configure the components when a power cycle occurs.
The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
The present invention provides a network computing system having end nodes, switches, routers, and links interconnecting these components. Each end node uses send and receive queue pairs to transmit and receives messages. The end nodes segment the message into packets and transmit the packets over the links. The switches and routers interconnects the end nodes and route the packets to the appropriate end node. The end nodes reassemble the packets into a message at the destination.
With reference now to the figures and in particular with reference to
SAN 100 is a high-bandwidth, low-latency network interconnecting nodes within the network computing system. A node is any component attached to one or more links of a network. In the depicted example, SAN 100 includes nodes in the form of host processor node 102, host processor node 104, redundant array independent disk (RAID) subsystem node 106, switch node 112, switch node 114, router node 117, and I/O chassis node 108. The nodes illustrated in
In one embodiment of the present invention, an error handling mechanism in distributed computer systems is present in which the error handling mechanism allows for reliable connection or reliable datagram communication between end nodes in network computing system, such as SAN 100.
A message, as used herein, is an application-defined unit of data exchange, which is a primitive unit of communication between cooperating processes. A packet is one unit of data encapsulated by a networking protocol headers and/or trailer. The headers generally provide control and routing information for directing the frame through SAN. The trailer generally contains control and cyclic redundancy check (CRC) data for ensuring packets are not delivered with corrupted contents.
SAN 100 contains the communications and management infrastructure supporting both I/O and interprocessor communications (IPC) within a network computing system. The SAN 100 shown in
The SAN 100 in
In one embodiment, a link is a full duplex channel between any two network fabric elements, such as end nodes, switches, or routers. Example suitable links include, but are not limited to, copper cables, optical cables, and printed circuit copper traces on backplanes and printed circuit boards.
For reliable service types, end nodes, such as host processor end nodes and I/O adapter end nodes, generate request packets and return acknowledgment packets. Switches and routers pass packets along, from the source to the destination. Except for the variant CRC trailer field which is updated at each stage in the network, switches pass the packets along unmodified. Routers update the variant CRC trailer field and modify other fields in the header as the packet is routed.
In SAN 100 as illustrated in
Host channel adapters 118 and 120 provide a connection to switch 112 while host channel adapters 122 and 124 provide a connection to switches 112 and 114.
In one embodiment, a host channel adapter is implemented in hardware. In this implementation, the host channel adapter hardware offloads much of central processing unit and I/O adapter communication overhead. This hardware implementation of the host channel adapter also permits multiple concurrent communications over a switched network without the traditional overhead associated with communicating protocols. In one embodiment, the host channel adapters and SAN 100 in
As indicated in
The I/O chassis 108 in
In this example, RAID subsystem node 106 in
SAN 100 handles data communications for I/O and interprocessor communications. SAN 100 supports high-bandwidth and scalability required for I/O and also supports the extremely low latency and low CPU overhead required for interprocessor communications. User clients can bypass the operating system kernel process and directly access network communication hardware, such as host channel adapters, which enable efficient message passing protocols. SAN 100 is suited to current computing models and is a building block for new forms of I/O and computer cluster communication. Further, SAN 100 in
Turning next to
Consumers 202-208 transfer messages to the SAN via the verbs interface 222 and message and data service 224. A verbs interface is essentially an abstract description of the functionality of a host channel adapter. An operating system may expose some or all of the verb functionality through its programming interface. Basically, this interface defines the behavior of the host. Additionally, host processor node 200 includes a message and data service 224, which is a higher level interface than the verb layer and is used to process messages and data received through channel adapter 210 and channel adapter 212.
With reference now to
A single channel adapter, such as the host channel adapter 300 shown in
Each queue pair consists of a send work queue (SWQ) and a receive work queue. The send work queue is used to send channel and memory semantic messages. The receive work queue receives channel semantic messages. A consumer calls an operating-system specific programming interface, which is herein referred to as verbs, to place work requests (WRs) onto a work queue.
With reference now to
Send work queue 402 contains work queue elements (WQEs) 422-428, describing data to be transmitted on the SAN fabric. Receive work queue 400 contains work queue elements (WQEs) 416-420, describing where to place incoming channel semantic data from the SAN fabric. A work queue element is processed by hardware 408 in the host channel adapter.
The verbs also provide a mechanism for retrieving completed work from completion queue 404. As shown in
Example work requests supported for the send work queue 402 shown in
A remote direct memory access (RDMA) read work request provides a memory semantic operation to read a virtually contiguous memory space on a remote node. A memory space can either be a portion of a memory region or portion of a memory window. A memory region references a previously registered set of virtually contiguous memory addresses defined by a virtual address and length. A memory window references a set of virtually contiguous memory addresses which have been bound to a previously registered region.
The RDMA Read work request reads a virtually contiguous memory space on a remote end node and writes the data to a virtually contiguous local memory space. Similar to the send work request, virtual addresses used by the RDMA Read work queue element to reference the local data segments are in the address context of the process that created the local queue pair. For example, work queue element 416 in receive work queue 400 references data segment 1 444, data segment 2 446, and data segment 448. The remote virtual addresses are in the address context of the process owning the remote queue pair targeted by the RDMA Read work queue element.
A RDMA Write work queue element provides a memory semantic operation to write a virtually contiguous memory space on a remote node. The RDMA Write work queue element contains a scatter list of local virtually contiguous memory spaces and the virtual address of the remote memory space into which the local memory spaces are written.
A RDMA FetchOp work queue element provides a memory semantic operation to perform an atomic operation on a remote word. The RDMA FetchOp work queue element is a combined RDMA Read, Modify, and RDMA Write operation. The RDMA FetchOp work queue element can support several read-modify-write operations, such as Compare and Swap if equal.
A bind (unbind) remote access key (R_Key) work queue element provides a command to the host channel adapter hardware to modify (destroy) a memory window by associating (disassociating) the memory window to a memory region. The R_Key is part of each RDMA access and is used to validate that the remote process has permitted access to the buffer.
In one embodiment, receive work queue 400 shown in
For interprocessor communications, a user-mode software process transfers data through queue pairs directly from where the buffer resides in memory. In one embodiment, the transfer through the queue pairs bypasses the operating system and consumes few host instruction cycles. Queue pairs permit zero processor-copy data transfer with no operating system kernel involvement. The zero processor-copy data transfer provides for efficient support of high-bandwidth and low-latency communication.
When a queue pair is created, the queue pair is set to provide a selected type of transport service. In one embodiment, a network computing system implementing the present invention supports four types of transport services.
Reliable and unreliable connected services associate a local queue pair with one and only one remote queue pair. Connected services require a process to create a queue pair for each process which is to communicate with over the SAN fabric. Thus, if each of N host processor nodes contain P processes, and all P processes on each node wish to communicate with all the processes on all the other nodes, each host processor node requires P2×(N−1) queue pairs. Moreover, a process can connect a queue pair to another queue pair on the same host channel adapter.
Reliable datagram service associates a local end-end (EE) context with one and only one remote end-end context. The reliable datagram service permits a client process of one queue pair to communicate with any other queue pair on any other remote node. At a receive work queue, the reliable datagram service permits incoming messages from any send work queue on any other remote node. The reliable datagram service greatly improves scalability because the reliable datagram service is connectionless. Therefore, an end node with a fixed number of queue pairs can communicate with far more processes and end nodes with a reliable datagram service than with a reliable connection transport service. For example, if each of N host processor nodes contain P processes, and all P processes on each node wish to communicate with all the processes on all the other nodes, the reliable connection service requires P2×(N−1) queue pairs on each node. By comparison, the connectionless reliable datagram service only requires P queue pairs+(N−1) EE contexts on each node for exactly the same communications.
The unreliable datagram service is connectionless. The unreliable datagram service is employed by management applications to discover and integrate new switches, routers, and end nodes into a given network computing system. The unreliable datagram service does not provide the reliability guarantees of the reliable connection service and the reliable datagram service. The unreliable datagram service accordingly operates with less state information maintained at each end node.
SAN architecture management facilities provide for a subnet manager (SM) and an infrastructure that supports a number of general management services. The management infrastructure requires a subnet management agent (SMA) in each node and defines a general service interface that allows additional general services agents.
The SAN architecture defines a common management datagram (MAD) message structure for communicating between managers and management agents. The subnet manager is an entity attached to a subnet that is responsible for configuring and managing switches, routers, and channel adapters. The subnet manager can be implemented with other devices, such as a channel adapter or a switch.
Turning next to
In data packet 500, message data 502 contains data segment 1 504, data segment 2 506, and data segment 3 508, which are similar to the data segments illustrated in
Additionally, transport header 518 also provides information such as the operation code, packet sequence number, and partition for data packet 500. The operating code identifies whether the packet is the first, last, intermediate, or only packet of a message. The operation code also specifies whether the operation is a send RDMA write, read, or atomic. The packet sequence number is initialized when communications is established and increments each time a queue pair creates a new packet. Ports of an end node may be configured to be members of one or more possibly overlapping sets called partitions.
SAN architecture management facilities provide for a subnet manager and an infrastructure that supports a number of general management services. The management infrastructure requires a subnet management agent in each node and defines a general service interface that allows additional general services agents. The SAN architecture includes a common management datagram (MAD) message structure for communicating between managers and management agents.
The subnet manager is an entity attached to a subnet that is responsible for configuring and managing switches, routers, and channel adapters. The subnet manager can be implemented with other devices, such as a channel adapter or a switch. The master subnet manager: (1) discovers the subnet topology; (2) configures each channel adapter port with a range of Local Identification (LID) numbers, Global Identification (GID) number, subnet prefix, and Partition Keys (P_Keys); (3) configures each switch with a LID, the subnet prefix, and with its forwarding database; and (4) maintains the end node and service databases for the subnet and thus provides a global unique identification (GUID) number to LID/GID resolution service as well as a services directory.
Each node provides a subnet manager agent that the subnet manager accesses through a well-known interface called the subnet management interface (SMI). Subnet manager interface allows for both LID routed packets and directed routed packets. Directed routing provides the means to communicate before switches and end nodes are configured.
SAN subnet management packets (SMPs) use an management key (M_Key) as an access control mechanism. When the subnet manager takes management control of a node, the subnet manager pushes its M_Key, along with a M_Key lease period, into each SAN component. The SAN component uses this M_Key to validate all future subnet management packets it receives within the M_Key lease period. Subsequent subnet management packets (SMPS) have their M_Key field compared with the value previously stored by subnet manager in the SAN component. If a M_Key field in a subnet management packet matches the M_Key value stored in the SAN component, the packet is accepted. Otherwise the packet is discarded.
The SAN architecture supports the notion of multiple subnet managers per subnet and specifies how multiple subnet managers negotiate for one to become the master subnet manager. Once a subnet manager gains control of a subnet, it can retain control as long as it does not lose its M_Key in the components of the subnet. Loss of the M_Key can happen under several circumstances. This loss can happen through a power cycle of the component which contains the M_Key, with the component coming up with the default M_Key when the power to the component is restored. This loss also may happen through a boot of the node which contains the subnet manager, such that the subnet manager goes away and the M_Key lease period expires in the component, in which case another subnet manager can take over control of the component.
The SAN architecture, in these examples, also supports the notion of a SM_Key. The SM_Key provides a additional level of authentication authority to control which subnet manager is allowed to be the master subnet manager. This also provides another level of granularity in determining which subnet managers are trusted is establishing standby subnet managers, that can backup the master subnet manager for redundancy and handoff.
SAN subnets can consist of thousands of nodes. The amount of time that this discovery and configuration process can take when all of the components are powered on, can be very large. This is particularly true in a large SAN environment, since, for example, complex algorithms may have to be executed to create correct and efficient routes for messages between nodes of the SAN. This situation can result in large boot times, which translates into lost time to the customer. This is particularly important when the boot is part of an error recovery process.
In addition, after initialization, a customer may want to change the assignments made by the subnet manager. Changes that a customer may want to make include: creation of multiple partitions, ports participating in a specific partition, and service levels that can be used by a given port. Without the ability to retain these changes, after each initialization the customer would have to redo all the assignments he had previously made.
The present invention provides a method, apparatus, and computer implemented instructions for solving the above problems by either having the subnet manager or the SAN components store the configuration information in some sort of non-volatile (NV) store. This non-volatile store may be, for example, a non-volatile random access memory (NVRAM) or magnetic storage media. In most cases the SAN configuration will not change significantly from one power on cycle to the next. By saving the information and only discovering the differences in configuration from the previous configuration, can save a lot of time in booting the system and can retain the manual changes made by the customer.
Turning next to
SAN subnet management packets are used by the subnet manager to query and update subnet management data at components in the subnet. Control of some aspects of the subnet management are through a user management console 636 in a host processor node 602. Additionally, higher level management applications 638 may be used in place of or in conjunction with management console 636 to manage and configure subnet 600. In this example, subnet manager 620 may implement the processes of the present invention used to retain configuration and management information. Configuration information retained includes such items as the range of local identification (LID) numbers applicable, subnet prefix, and partition keys (P_Keys).
Turning next to
Once the initial subnet configuration has started, a component is discovered (step 700). Step 700 is used by the subnet manager to sweep through the subnet to discover components within the subnet. Components may take various forms, such as, end nodes, switches, or routers. In these examples, subnet management packets are sent out by the subnet manager to discover components.
Next, the component configuration is setup (step 702). The component configuration is set up through the use of subnet management packets. Configuration information set up includes such items as the range of local identification (LID) numbers applicable, subnet prefix, and partition keys (P_Keys). The subnet manager looks at the component type as well as the other components in the system, the SAN configuration, and manually inputted user configuration information in order to determine what configuration should be set up for the component. Details about this initial component configuration is beyond the scope of the present invention. The configuration information is saved at the subnet manager node in the non-volatile (NV) store or at the component or at both locations (step 704). In these examples, the non-volatile store may take various forms, such as, for example, a NVRAM, a hard disk, or some other form of non-volatile store. This non-volatile store provides a mechanism to maintain configuration information during powering down of subnet components.
Next, a determination is made as to whether all the components have been configured (step 706). This decision step is used to continue the configuration and saving process until all of the components have been configured. If all components have been configured, the configuration is done and the network is operational.
With reference again to step 706, if all components have not been configured, the process returns to step 700.
Turning next to
Once the subsequent subnet configuration has started, a component is discovered (step 800). A determination is then made as to whether this is the same component as before in this location (step 802). This determination could be done in a number of different ways. An example is to use the global identifier (GID) of the component, which is an identifier that is unique to that component. If this is the same component as before in this location, the component configuration is setup as in the previous configuration (step 804). In this case, the configuration can be more quickly restored than if the subnet manager was required to perform the calculations and determinations necessary to normally configure the component. Examples of a couple of the many items that may need to be calculated or determined for a component during configuration include determination of the component's LID, which must be unique in the subnet, switch routing tables, and the P_Keys that are applicable to the component. Next, a determination is made as to whether all components have been configured (step 806). If all components have been configured, the configuration is done and the network is operational.
With reference again to step 802, if this is not the same component as before in this location, a new or changed component configuration is setup (step 808). In step 808, no previously saved information is present that may be used for the component being addressed. In other words, the component may be a different component, such as if a new or different component was put in place of the original component. The saved configuration information, however, may still be used with other components. This set up is performed with the potential that previously configured components may have to be reconfigured. Then, any conflicts with the previous configuration are corrected (step 810). In step 810, changes to the saved configuration information are made to take in account conflicts or differences between the component originally present and the current component. The configuration information is saved at the subnet manager node in the non-volatile store (step 812) with the process returning to step 806.
With reference again to step 806, if all components have not been configured, the process returns to step 800.
With this process, when the system is powered on, the subnet manager can quickly traverse the switch ports that were used before, verifying that all the same components are present, which will be the case most of the time. Then, the subnet manager uses subnet management packets to send the same information back to the SAN component that the component had before the component was powered down. After all the previous components are set back to the prior state and the system is up and running, the switch ports that were not used before powering down can be queried to see if the switch ports contain new hardware, which was added to the switch ports while the power was off. In this case, steps 808, 810, and 812 may be delayed until the rest of the system is up and running, allowing the subnet system to power up and run faster.
Turning next to
Once the subsequent subnet configuration has started, a component is discovered (step 900). A determination is then made as to whether the component indicates that it has stored the previous configuration (step 902). This determination is facilitated through the use of subnet management packets sent to the discovered component to identify whether previous configuration information is present for the component.
If the component does not indicate that it has stored the previous configuration, the component configuration is set up (step 904). Configuration information set up includes such items as the range of local identification (LID) numbers applicable, subnet prefix, and partition keys (P_Keys). The subnet manager looks at the component type as well as the other components in the system, the SAN configuration, and manually inputted user configuration information in order to determine what configuration should be set up for the component.
Next, a determination is made as to whether all components have been configured (step 906). If all components have been configured, the configuration is done and the network is operational.
With reference again to step 902, if the component does indicate that it has stored the previous configuration, the previous component configuration is read from the component (step 908). This information is obtained from the non-volatile store associated with the component. This step also includes configuring the component using the configuration information.
Next, any conflicts with the previous configuration are corrected (step 910). Conflicts can occur, for example, when components are moved around in the SAN, and since components in this embodiment take their old configuration information with them, if they are moved to other parts in the SAN, then configuration items like the component LIDs will conflict with routing tables or possibly other LIDs in the subnet. The changed configuration information, if any, is saved back into the non-volatile store at component(s) (step 912) with the process returning to step 906.
With reference again to step 906, if all components have not been configured, the process returns to step 900.
The embodiment of storing the information at the component as in
Turning next to
Once the subsequent subnet configuration has started, a component is discovered (step 1000). A determination is then made as to whether the component is the same as before in this location (step 1002). If this is not the same component as before in this location, the component configuration is set up (step 1004). Next, the configuration information is saved at the subnet manager node in the non-volatile store (step 1006). A determination is then made as to whether the component indicates that it can store the configuration (step 1008). If the component does indicate that it can store the configuration, the configuration information is saved into the non-volatile store at component (step 1010). Step 1010 is accomplished using a subnet manager packet, which is sent to the component to request that the component store the configuration information.
Next, a determination is made as to whether all components have been configured (step 1012). If all components have been configured, the configuration is done and the network is operational.
With reference again to step 1002, if the component is not the same as before in this location, a determination is made as to whether the component indicates that it has stored the previous configuration (step 1014). If the component indicates that it has stored the previous configuration, the previous component configuration is read from the component (step 1016). A determination is then made as to whether the component configuration is not the same as the previous configuration (step 1018). If the component configuration is not the same as the previous configuration, any conflicts with the previously configured components are corrected (step 1020). Then, the changed configuration information, if any, is saved back into the non-volatile store at component (step 1022). The configuration information is saved at the subnet manager node in the non-volatile store (step 1024) with the process then returning to step 1012 as described above.
With reference again to step 1008, if the component does not indicate that it can store the configuration, the process proceeds to step 1012. With reference again to step 1012, if all components have not been configured, the process returns to step 1000. With reference again to step 1014, if the component does not indicate that it has stored the previous configuration, the component configuration is set up (step 1026). Next, the configuration information is saved at the subnet manager node in the non-volatile store (step 1028) with the process proceeding to step 1012.
With reference again to step 1018, if the component configuration is the same as the previous configuration, the configuration is complete and the process returns to step 1012.
The advantage of this third embodiment in
Thus, the present invention provides a method, apparatus, and computer implemented instructions for retaining configuration information between power cycles in which the subnet or devices within the subnet are turned off and on. This mechanism eliminates time consuming steps of determining and resolving configuration conflicts within the subnet. This result speeds system boot time, which is a key time in recovery from power outages in a subnet. In this manner, subnet availability is increased.
It is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include recordable-type media, such as a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, and transmission-type media, such as digital and analog communications links, wired or wireless communications links using transmission forms, such as, for example, radio frequency and light wave transmissions. The computer readable media may take the form of coded formats that are decoded for actual use in a particular data processing system.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4638356||Mar 27, 1985||Jan 20, 1987||General Instrument Corporation||Apparatus and method for restricting access to a communication network|
|US4814984||Apr 3, 1987||Mar 21, 1989||International Computers Limited||Computer network system with contention mode for selecting master|
|US4939752||May 31, 1989||Jul 3, 1990||At&T Company||Distributed timing recovery for a distributed communication system|
|US4951225||Nov 14, 1988||Aug 21, 1990||International Business Machines Corp.||Updating pattern-matching networks|
|US4975829||Sep 22, 1986||Dec 4, 1990||At&T Bell Laboratories||Communication interface protocol|
|US5043981||May 29, 1990||Aug 27, 1991||Advanced Micro Devices, Inc.||Method of and system for transferring multiple priority queues into multiple logical FIFOs using a single physical FIFO|
|US5185736||May 12, 1989||Feb 9, 1993||Alcatel Na Network Systems Corp.||Synchronous optical transmission system|
|US5185741||May 30, 1990||Feb 9, 1993||Fujitsu Limited||Inter-network connecting system|
|US5218680||Mar 15, 1990||Jun 8, 1993||International Business Machines Corporation||Data link controller with autonomous in tandem pipeline circuit elements relative to network channels for transferring multitasking data in cyclically recurrent time slots|
|US5402416||Jan 5, 1994||Mar 28, 1995||International Business Machines Corporation||Method and system for buffer occupancy reduction in packet switch network|
|US5461608||Jun 30, 1994||Oct 24, 1995||Nec Corporation||Ring network with temporary master node for collecting data from slave nodes during failure|
|US5513368||Jul 16, 1993||Apr 30, 1996||International Business Machines Corporation||Computer I/O adapters for programmably varying states of peripheral devices without interfering with central processor operations|
|US5551066||Feb 27, 1995||Aug 27, 1996||Radio Local Area Networks, Inc.||Network link controller for dynamic designation of master nodes|
|US5610980||Feb 13, 1995||Mar 11, 1997||Eta Technologies Corporation||Method and apparatus for re-initializing a processing device and a storage device|
|US5617424||May 3, 1996||Apr 1, 1997||Hitachi, Ltd.||Method of communication between network computers by dividing packet data into parts for transfer to respective regions|
|US5617537||Oct 3, 1994||Apr 1, 1997||Nippon Telegraph And Telephone Corporation||Message passing system for distributed shared memory multiprocessor system and message passing method using the same|
|US5719938||Aug 1, 1994||Feb 17, 1998||Lucent Technologies Inc.||Methods for providing secure access to shared information|
|US5729686||Feb 2, 1996||Mar 17, 1998||Becker Gmbh||Method for initializing a network having a plurality of network subscribers capable of acting as masters|
|US5758083||Oct 30, 1995||May 26, 1998||Sun Microsystems, Inc.||Method and system for sharing information between network managers|
|US5778176||Oct 8, 1996||Jul 7, 1998||International Business Machines Corporation||System for automatically transferring access authorization of third node to first node even through first node is not previously authorized to access function of second node in computer network|
|US5793968||Mar 10, 1997||Aug 11, 1998||Peerlogic, Inc.||Scalable distributed computing environment|
|US5805072||Dec 1, 1995||Sep 8, 1998||Ultra-High Speed Network||VC connection method|
|US5884036||Nov 8, 1996||Mar 16, 1999||Haley; Andrew Paul||Method for determining the topology of an ATM network having decreased looping of topology information cells|
|US5907689||Dec 31, 1996||May 25, 1999||Compaq Computer Corporation||Master-target based arbitration priority|
|US5951683||Dec 19, 1997||Sep 14, 1999||Fujitsu Limited||Multiprocessor system and its control method|
|US6032191||Oct 28, 1997||Feb 29, 2000||International Business Machines Corporation||Direct coupling for data transfers|
|US6081752||Dec 12, 1997||Jun 27, 2000||International Business Machines Corporation||Computer system having power supply primary sense to facilitate performance of tasks at power off|
|US6085238||Apr 22, 1997||Jul 4, 2000||Matsushita Electric Works, Ltd.||Virtual LAN system|
|US6092214||Nov 6, 1997||Jul 18, 2000||Cisco Technology, Inc.||Redundant network management system for a stackable fast ethernet repeater|
|US6098098 *||Nov 14, 1997||Aug 1, 2000||Enhanced Messaging Systems, Inc.||System for managing the configuration of multiple computer devices|
|US6108739||Apr 29, 1999||Aug 22, 2000||Apple Computer, Inc.||Method and system for avoiding starvation and deadlocks in a split-response interconnect of a computer system|
|US6115776||May 2, 1997||Sep 5, 2000||3Com Corporation||Network and adaptor with time-based and packet number based interrupt combinations|
|US6128738||Apr 22, 1998||Oct 3, 2000||International Business Machines Corporation||Certificate based security in SNA data flows|
|US6192397||May 19, 1997||Feb 20, 2001||Nortel Networks Limited||Method for establishing a master-slave relationship in a peer-to-peer network|
|US6199133||Mar 29, 1996||Mar 6, 2001||Compaq Computer Corporation||Management communication bus for networking devices|
|US6222822||Mar 31, 1997||Apr 24, 2001||Cisco Systems, Incorporated||Method for optimizing a digital transmission network operation through transient error monitoring and control and system for implementing said method|
|US6269396||Dec 11, 1998||Jul 31, 2001||Alcatel Usa Sourcing, L.P.||Method and platform for interfacing between application programs performing telecommunications functions and an operating system|
|US6298376||Mar 7, 1997||Oct 2, 2001||General Electric Company||Fault tolerant communication monitor for a master/slave system|
|US6304973||Aug 6, 1998||Oct 16, 2001||Cryptek Secure Communications, Llc||Multi-level security network system|
|US6311321||Feb 22, 1999||Oct 30, 2001||Intel Corporation||In-context launch wrapper (ICLW) module and method of automating integration of device management applications into existing enterprise management consoles|
|US6330555||Feb 19, 1999||Dec 11, 2001||Nortel Networks Limited||Method and apparatus for enabling a view of data across a database|
|US6341322||Feb 25, 1999||Jan 22, 2002||Micron Electronics, Inc.||Method for interfacing two buses|
|US6343320||Jun 9, 1998||Jan 29, 2002||Compaq Information Technologies Group, L.P.||Automatic state consolidation for network participating devices|
|US6363411||Oct 19, 1999||Mar 26, 2002||Mci Worldcom, Inc.||Intelligent network|
|US6363416||Aug 28, 1998||Mar 26, 2002||3Com Corporation||System and method for automatic election of a representative node within a communications network with built-in redundancy|
|US6363495||Jan 19, 1999||Mar 26, 2002||International Business Machines Corporation||Method and apparatus for partition resolution in clustered computer systems|
|US6389432||Apr 5, 1999||May 14, 2002||Auspex Systems, Inc.||Intelligent virtual volume access|
|US6421779||Jul 29, 1998||Jul 16, 2002||Fujitsu Limited||Electronic data storage apparatus, system and method|
|US6434113||Apr 9, 1999||Aug 13, 2002||Sharewave, Inc.||Dynamic network master handover scheme for wireless computer networks|
|US6470397||Mar 30, 1999||Oct 22, 2002||Qlogic Corporation||Systems and methods for network and I/O device drivers|
|US6496503 *||Jun 1, 1999||Dec 17, 2002||Intel Corporation||Device initialization and operation using directed routing|
|US6507592||Jul 8, 1999||Jan 14, 2003||Cisco Cable Products And Solutions A/S (Av)||Apparatus and a method for two-way data communication|
|US6529286||Dec 22, 1998||Mar 4, 2003||Canon Kabushiki Kaisha||Dynamic printing interface for routing print jobs in a computer network|
|US6597956||Aug 2, 2000||Jul 22, 2003||Terraspring, Inc.||Method and apparatus for controlling an extensible computing system|
|US6636520||Dec 21, 1999||Oct 21, 2003||Intel Corporation||Method for establishing IPSEC tunnels|
|US6654363||Dec 28, 1999||Nov 25, 2003||Nortel Networks Limited||IP QOS adaptation and management system and method|
|US6658417||Oct 13, 2000||Dec 2, 2003||International Business Machines Corporation||Term-based methods and apparatus for access to files on shared storage devices|
|US6664978||Nov 17, 1997||Dec 16, 2003||Fujitsu Limited||Client-server computer network management architecture|
|US6665714||Jun 30, 1999||Dec 16, 2003||Emc Corporation||Method and apparatus for determining an identity of a network device|
|US6674911||Sep 25, 2002||Jan 6, 2004||William A. Pearlman||N-dimensional data compression using set partitioning in hierarchical trees|
|US6694361 *||Jun 30, 2000||Feb 17, 2004||Intel Corporation||Assigning multiple LIDs to ports in a cluster|
|US6708272||May 20, 1999||Mar 16, 2004||Storage Technology Corporation||Information encryption system and method|
|US20020021307||Apr 23, 2001||Feb 21, 2002||Steve Glenn||Method and apparatus for utilizing online presence information|
|US20020026517||Jun 29, 2001||Feb 28, 2002||Watson Richard A.||Enabling communications of electronic data between an information requestor and a geographically proximate service provider|
|US20020073257||Dec 7, 2000||Jun 13, 2002||Ibm Corporation||Transferring foreign protocols across a system area network|
|US20020133620||Mar 15, 2002||Sep 19, 2002||Krause Michael R.||Access control in a network system|
|US20030018787||Jul 12, 2001||Jan 23, 2003||International Business Machines Corporation||System and method for simultaneously establishing multiple connections|
|US20030046505||Aug 30, 2001||Mar 6, 2003||International Business Machines Corporation||Apparatus and method for swapping-out real memory by inhibiting I/O operations to a memory region|
|US20040057424||Nov 5, 2001||Mar 25, 2004||Jani Kokkonen||Communications system|
|JP2002064587A||Title not available|
|WO2000072519A1||May 19, 2000||Nov 30, 2000||Sony Corporation||Communication method, communication device, and communication system|
|1||Nehmer et al. "Fault Tolerance Approach for Distributed ISDN Control Systems", ACM SIGOPS European Workshop, Proceedings of the fourth workshop on ACM SIGOPS European workshop 1990, Bologna, Italy, 1990, pp. 1-4.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8301739 *||Oct 30, 2012||Emc Corporation||Storage system initialization utility|
|US8842518||Sep 16, 2011||Sep 23, 2014||Oracle International Corporation||System and method for supporting management network interface card port failover in a middleware machine environment|
|US8879396 *||Oct 10, 2012||Nov 4, 2014||Oracle International Corporation||System and method for using dynamic allocation of virtual lanes to alleviate congestion in a fat-tree topology|
|US9215083||Jul 11, 2012||Dec 15, 2015||Oracle International Corporation||System and method for supporting direct packet forwarding in a middleware machine environment|
|US9288160||Aug 23, 2011||Mar 15, 2016||Intel Corporation||GID capable switching in an infiniband fabric|
|US9325619||Nov 7, 2012||Apr 26, 2016||Oracle International Corporation||System and method for using virtual lanes to alleviate congestion in a fat-tree topology|
|US9332005||Jul 10, 2012||May 3, 2016||Oracle International Corporation||System and method for providing switch based subnet management packet (SMP) traffic protection in a middleware machine environment|
|US20090019536 *||Jan 29, 2007||Jan 15, 2009||Camrivox Ltd.||Automatic ip network determination and configuration for edge devices|
|US20130121154 *||May 16, 2013||Oracle International Corporation||System and method for using dynamic allocation of virtual lanes to alleviate congestion in a fat-tree topology|
|US20130304699 *||May 10, 2013||Nov 14, 2013||Oracle International Corporation||System and method for supporting configuration daemon (cd) in a network environment|
|WO2012037512A1 *||Sep 16, 2011||Mar 22, 2012||Oracle International Corporation||Performing partial subnet initialization in a middleware machine environment|
|WO2013028175A1 *||Aug 23, 2011||Feb 28, 2013||Intel Corporation||Gid capable switching in an infiniband fabric|
|WO2013147829A1 *||Mar 30, 2012||Oct 3, 2013||Intel Corporation||Efficient distribution of subnet administration data over an rdma network|
|U.S. Classification||709/221, 713/2, 713/1, 713/100, 370/278, 710/104, 709/222|
|International Classification||G06F15/16, G06F13/00, G06F9/00|
|Nov 9, 2010||CC||Certificate of correction|
|Mar 29, 2013||FPAY||Fee payment|
Year of fee payment: 4