Method, apparatus, and program for server based network computer load balancing across multiple boot servers

• US 7,139,816 B2
• Filed: 12/18/2000
• Issued: 11/21/2006
• Est. Priority Date: 12/18/2000
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Schoech, James Richard, Stern, Bradford Allen, Anand, Vaijayanthimala K., French, Steven Michael, Paul, Chakkalamattam Jos
• Primary Examiner(s): Follansbee, John
• Assistant Examiner(s): SIDDIQI, MOHAMMAD A
• Application Number:
  US09/740,565
• Publication Number:
  US 20020078188A1
• Time in Patent Office: 2,164 Days
• Field of Search: 709220-222, 709/227, 709/217, 709/219, 709/223, 713/1, 713/2, 713/100
• US Class Current: 709/220
• CPC Class Codes: G06F 11/1417 Boot up procedures
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]

Abstract

A method, system, and program is provided to redirect a client computer to an appropriate boot server after it has been directed to any initial boot server by preboot execution environment (PXE) or similar services. An apparatus includes a data file containing a set of addresses of managed boot servers in any syntax and a program file containing a network bootstrap program (NBP) that interprets the syntax of the data file. These files are placed on every initial boot server. The NBP requests a file from the initial boot server whose name is identified with the client computer. The initial boot server will not return that file if it is not an appropriate server for booting the client. In that case, the NBP requests the data file containing the boot server addresses. The NBP then polls each of those boot servers by requesting the client'"'"'s unique file. A boot server that returns the file is an appropriate boot server for the client computer. The data file containing boot server addresses is changed to reflect current boot server load balancing requirements without involving the configuration or affecting the availability of PXE or similar services.

Claims

1. A method for retrieving client boot information in a network environment with multiple boot servers, comprising:

initiating at a client an initial request for client configuration information;

sending from the client the initial request for client configuration information to a first boot server;

receiving at the client a boot server list if the client configuration information is not found on the first boot server; and

sending from the client a configuration information request for the client configuration information to each server in the boot server list until the client configuration information is found or a request has been sent to every server in the boot server list.

2. The method of claim 1, wherein at least one of the initial request, the list request, and the configuration information request is a trivial file transfer protocol request.

3. The method of claim 1, further comprising:

receiving, from the first boot server, an error message that indicates that the client information is not found on the first boot server.

4. The method of claim 1, further comprising:

receiving the client configuration information from an associated boot server in response to the client configuration information being found.

5. The method of claim 4, further comprising:

sending a boot file request for remaining boot files to the associated boot server based on the client configuration information.

6. The method of claim 1, further comprising:

determining whether the entries in the boot server list were pre-ordered, in order to better support load balancing among boot servers, prior to transmission to the client; and

if the list is found to be ordered, sending a configuration information request for the client configuration information to each server in the boot server list in the order given.

7. The method of claim 1, further comprising:

sending a configuration information request for the client configuration information to each server in the boot server list in order of increasing network distance, where distance is estimated from available network configuration information when there was no indication that the order of the original boot server list was optimized in order to better support load balancing.

8. The method of claim 1, wherein the method is performed by a network bootstrap program.

9. The method of claim 1, wherein the method is performed on a client computer.

10. A method for providing client boot information in a network environment with multiple boot servers, comprising:

receiving at a boot server an initial request for client configuration information from a client, wherein the initial request is initiated at the client;

sending from the boot server a boot server list to the client if the client configuration information is not found; and

adding an indication to the boot server list to inform the client that the list is being provided in optimal order to support load balancing among boot servers.

11. The method of claim 10, wherein at least one of the initial request and the list request is a trivial file transfer protocol request.

12. An apparatus for retrieving client boot information in a network environment with multiple boot servers, comprising:

initiating means for initiating at a client an initial request for client configuration information;

first sending means for sending from a client an initial request for client configuration information to a first boot server;

receipt means for receiving at the client a boot server list if the client configuration information is not found on the first boot server; and

second sending means for sending from the client a configuration information request for the client configuration information to each server in the boot server list until the client configuration information is found or a request has been sent to every server in the boot server list.

13. The apparatus of claim 12, wherein at least one of the initial request, the list request, and the configuration information request is a trivial file transfer protocol request.

14. The apparatus of claim 12, further comprising:

means for receiving, from the first boot server, an error message that indicates that the client information is not found on the first boot server.

15. The apparatus of claim 12, further comprising:

means for receiving the client configuration information from an associated boot server in response to the client configuration information being found; and

means for sending a boot file request for remaining boot files to the associated boot server based on the client configuration information.

16. The apparatus of claim 12, further comprising:

means for determining whether the entries in the boot server list were pre-ordered, in order to better support load balancing among boot servers, prior to transmission to the client; and

if the list is found to be ordered, means for sending a configuration information request for the client configuration information to each server in the boot server list in the order given.

17. The apparatus of claim 12, further comprising:

means for sending a configuration information request for the client configuration information to each server in the boot server list in order of increasing network distance, where distance is estimated from available network configuration information when there was no indication that the order of the original boot server list was optimized in order to better support load balancing.

18. The apparatus of claim 12, wherein the apparatus is client computer running a network bootstrap program.

19. An apparatus for providing client boot information in a network environment with multiple boot servers, comprising:

receipt means for receiving at a boot server an initial request for client configuration information from a client, wherein the initial request is initiated at the client;

sending means for sending from the boot server a boot server list to the client if the client configuration information is not found; and

adding means for adding an indication to the boot server list to inform the client that the list is given in optimal order to support load balancing among boot servers.

20. The apparatus of claim 19, wherein at least one of the initial request and the list request is a trivial file transfer protocol request.

21. A computer program product, in a computer readable storage medium, for retrieving client boot information in a network environment with multiple boot servers, comprising:

instructions for initiating at a client an initial request for client configuration information;

instructions for sending from the client an initial request for client configuration information to a first boot server;

instructions for receiving at the client a boot server list if the client configuration information is not found on the first boot server; and

instructions for sending from the client a configuration information request for the client configuration information to each server in the boot server list until the client configuration information is found or a request has been sent to every server in the boot server list.

22. A computer program product, in a computer readable storage medium, for providing client boot information in a network environment with multiple boot servers, comprising:

instructions for receiving at a boot server an initial request for client configuration information from a client, wherein the initial request is initiated at the client;

instructions for sending from the boot server a boot server list to the client if the client configuration information is not found; and

instructions for adding an indication to the boot server list to inform the client that the list is being provided in optimal order to support load balancing among boot servers.