Stand-in computer server

• US 5,592,611 A
• Filed: 03/14/1995
• Issued: 01/07/1997
• Est. Priority Date: 03/14/1995
• Status: Expired due to Term

• Current Assignee: Autonomy Incorporated (HP Inc.)
• Original Assignee: Network Integrity, Inc.
• Inventors: Midgely, Christopher W., Webb, John W., Acott, John L.
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Decady, Albert
• Application Number:
  US08/403,307
• Time in Patent Office: 665 Days
• Field of Search: 395/181, 395/182.01, 395/182.02, 395/182.05, 395/180, 379/220, 379/219, 379/221, 364/242.94, 364/242.95, 364/284.4, 364/927.96, 364/940.62, 364/940.64
• US Class Current: 714/4.3
• CPC Class Codes: G06F 11/1443 Transmit or communication errors
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence

Abstract

An Integrity Server computer for economically providing a stand-in computer, replacing a failed server of a network. The invention provides methods for re-establishing connections between clients and servers, and communicating packets between network nodes, to allow the Integrity Server to stand-in for a failed server without requiring reconfiguration of the network clients when a server fails. In one method, the Integrity Server publishes the name of the failed server, in addition to its normal name, when the failed server becomes inaccessible. In a second method, a first channel accepts network packets addressed to the failed server, and forwards them to a second channel for service.

Claims

1. In a network of computers, the computers comprising one or more server nodes and client nodes requesting services from the server nodes, messages sent between nodes each having a destination address and a message content, a method for providing the services of a protected one of said server nodes to the client nodes, comprising the steps:

when said protected server node becomes unavailable to said client nodes, a connection server connected to another node on the network publishing as its name the name of the unavailable server node, in addition to publishing a name by which the connection server is regularly known;

a client node requesting services from a service server by continuing to request services by the name of the unavailable server node in the same manner as requests were made prior to the protected server node becoming unavailable.

5. The method of any one of claims 1, 2, or 3, wherein:

a plurality of client nodes send messages to and receive messages from said connection server; and

said connection server comprises a plurality of channels, a master group of said channels receiving messages from and forwarding messages to said client nodes, and a plurality of helper groups of said channels, each helper group corresponding to a distinct one of said client nodes.

6. The method of claim 5, wherein:

a plurality of client nodes send messages to and receive messages from said connection server; and

sequence numbers of said request and response messages are used to route response packets through said connection server to the proper one of said client nodes.

7. The method of any one of claims 1, 2, or 3, wherein:

said connection server and said service server are both implemented by the same single computer of said network.

8. The method of any one of claims 1, 2, 3, or 4, further comprising:

for at least some request message directed by said client node to said unavailable server and received at said first channel, performing the service requested by the request message and sending a reply to said client node without forwarding a corresponding request message to said second channel.

9. The method of claim 8 wherein:

each request message includes a function code determining an action to be performed by the message'"'"'s destination node; and

determination that the service is to be performed without said forwarding is based on the function code of said request message.

10. The method of claim 1, 2, 3, or 4, further comprising:

for at least some message directed by said client node to said unavailable server and received at said first channel, altering the contents of the request message before forwarding a corresponding request message to said second channel.

11. The method of claim 10, wherein:

each request message includes a function code determining an action to be performed by the message'"'"'s destination node; and

portions of the contents of said request message to be altered are determined according to the function code of said request message.

12. The method of claim 10, further comprising:

instances of altering of said messages include at least one instance each of modifying each of a server name, a file pathname, a volume name, and directory service information.

13. The method of claim 10, further comprising:

altering the packet sequence number in said altered packet.

14. The method of any one of claims 1, 2, 3, or 4, further comprising:

after performing said requested service, receiving a response message at a channel of said connection server;

forwarding a response message corresponding to said received response messages to said client node; and

for at least one of said messages forwarded by said connection server, altering the contents of the forwarded response message.

15. The method of claim 14, wherein:

each response message includes a function code determining an action to be performed by the message'"'"'s destination node; and

portions of the contents of said response message to be altered are determined according to the function code of said response message.

16. The method of claim 14, further comprising:

instances of altering of said response messages include at least one instance each of modifying each of a server name and a file pathname.

17. The method of claim 14, further comprising:

altering the packet sequence number in said forwarded response packet.

2. In a computer network of nodes, the nodes each having a network address and comprising a server node providing specific services and client nodes requesting services from the server node, messages sent between nodes each having a destination address and a message content, a method for servicing service request messages comprising:

establishing a communication path between a client node and a connection server node, by the client node requesting a connection to an unavailable server node, and the connection server responding to the client'"'"'s connection request by representing itself as able to provide the services of the unavailable server;

transmitting a first request message from the client node to the connection server requesting a service of the unavailable server;

receiving the first request message at a forwarding channel of the connection server, and forwarding a second request message from the forwarding channel to a service channel of a service server;

servicing the second request message at the service channel, which is configured to provide all services of the unavailable server, and generating a first response message addressed to the forwarding channel; and

at the forwarding channel, generating a second response message addressed to the client node.

3. The method of claim 2, wherein:

the connection server represents itself as able to provide the services of the unavailable server by publishing as its name the name of the unavailable server node, in addition to publishing a name by which the connection server is regularly known; and

a client node obtaining services from the service server node by requesting services by the name of the unavailable server node.

4. The method of claim 2, where the forwarding channel is implemented by using operating system hooks to intercept, filter, and route communications between multiple clients and the integrity server.