Technique for reliable network booting of an operating system to a client computer

• US 5,974,547 A
• Filed: 03/20/1998
• Issued: 10/26/1999
• Est. Priority Date: 03/20/1998
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Klimenko, Yevgeniy
• Primary Examiner(s): Palys, Joseph E.
• Assistant Examiner(s): Mai, Rijue
• Application Number:
  US09/045,577
• Time in Patent Office: 585 Days
• Field of Search: 713/1, 713/2, 713/100, 709/220, 709/221, 709/222-228, 709/203, 709/217, 709/223, 709/224
• US Class Current: 713/2
• CPC Class Codes: G06F 9/4416 Network booting; Remote initial program loading [RIPL]

Abstract

A technique, specifically apparatus and accompanying methods, for use in a client-server environment for booting an operating system (O/S), such as a 32-bit personal computer (PC) O/S, on a client computer through a networked connection to a server. Specifically, the server stores an image of a client hard disk including the client O/S and desired applications. During a boot process, a procedure, which is compliant with both an interrupt handler in the client and a network driver kernel in the client O/S, is installed in the client. Based on client O/S resources then available when, during the boot process, the client requests a local hard disk access to a particular sector, the procedure will re-direct that request, to the network file server, through a network driver kernel in the client O/S rather than through a client interrupt handler. Each such request is processed, to provide physical sector read or write access, through my inventive random access trivial file transfer protocol (RATFTP) server executing in the network server. Advantageously, the source of the sectors remains transparent to the client O/S, while it is being booted from a network connection, in lieu of a local hard disk drive. Hence, client hard disk emulation occurs seamlessly and continuously throughout the entire boot process even though, during this process, the client processing mode changes from real to protected and the client O/S resets and gains control of a client network adapter.

Claims

1. A method of booting an operating system (O/S) to a client computer from a network, the network storing an image on a first server, the image having O/S files for the client computer, the method comprising the steps, in the client computer, of:

(a) issuing a corresponding request to the first server to download contents of a corresponding one of each of a plurality of sectors residing on the first server so as to form a plurality of requests, wherein;

(a1) said sectors collectively store an image file which contains the image; and

(a2) the first server emulates, in response to said plurality of requests, behavior of a disk drive on the client computer such that contents of individual physical sectors of the image file specified in corresponding ones of the requests are accessed by the first server on a sector-by-sector basis from a disk drive associated with the first server and downloaded, via the network, to the client computer, and wherein the corresponding request issuing step comprises the steps of;

(a3) generating a request, to the first server, to download a boot sector contained in the image file; and

(a4) executing the boot sector, once the boot sector is downloaded from the first server, so as to subsequently generate each of said plurality of requests such that the client computer receives, on a sector-by-sector basis from the first server, the contents of the individual physical sectors that collectively comprise client O/S files;

(b) storing the contents of each of said sectors received from the first server; and

(c) activating client O/S processes embodied by the contents of said sectors stored on the client computer.

2. The method in claim 1 wherein said corresponding request issuing step, in the client computer, further comprises the step of:

obtaining, from a second server, an address of the image file stored on the first server.

3. The method in claim 2 further comprising the step, in the client computer, of obtaining a boot file from a second network server, the boot file comprising real-mode client disk emulation code;

and wherein the request generating step comprises the step of producing the boot sector download request through executing the boot file, wherein the boot sector request contains an identification of the first server and the name of the image file.

4. The method in claim 3 wherein the first and second servers are the same server or different servers connected to the network.

5. The method in claim 3 further comprising the step of providing the client disk emulation, on a sectorized basis, while a processing mode of the client computer changes from real to protected and the client O/S takes ownership of a network interface situated in the client computer and connected to the network.

6. The method in claim 5 further comprising the step, in the client computer, of:

downloading, as part of the image file, a transport driver; and

executing, as one of the client O/S processes, the transport driver such that each of the client disk access requests, generated by the client computer while the client O/S is being booted, is directed to the first server so as to retrieve contents of a corresponding sector of the image file stored on the first server in lieu of accessing a sector associated with a disk locally situated at the client computer, whereby, through use of the transport driver and while the client O/S is being booted, an actual source of the contents of the sectors remains transparent to the client O/S.

7. The method in claim 6 wherein the transport driver execution step further comprising the steps of:

while the client computer is operating in the real processing mode, handling client disk access operations through a real mode interrupt handler procedure so as to generate ones of the plurality of requests;

while the client computer is operating in the protected mode, handling client disk access operations through pre-defined client O/S network procedures so as to generate subsequent ones of the plurality of requests;

detecting, as the client O/S processes are being activated, a transition in the client processing mode from real to protected; and

during the transition, controlling a changeover in handling client disk access operations from the real mode interrupt handling procedure to the client O/S network procedures to generate said subsequent ones of the plurality of requests.

8. The method in claim 7 wherein the controlling step comprises the step of controlling the changeover based on whether sufficient active resources then exist in client O/S as it is booting.

9. The method in claim 7 wherein the detecting step comprises the step of employing a semaphore-based procedure for detecting said transition in the client processing mode.

10. The method in claim 7 further comprising the steps, in the client computer, of:

executing predefined boot code stored in the client computer which, in response thereto, broadcasts a client IP (Internet protocol) request message on the network, said client IP request message containing an address of the network interface situated in the client computer;

obtaining, from the second server, a reply message to the client IP request message, wherein the reply message contains an IP address assigned to the client computer, an IP address of the first server and an address of the boot file stored on the second server, wherein the boot file contains the real-mode client disk emulation code and a name of an initialization file;

downloading the boot file from the second server;

executing the emulation code contained in the boot file, once it has been downloaded, so as to initiate real-mode client disk emulation through the second server and thereafter to download the initialization file from the second server, wherein the initialization file contains an address of the image file residing on the first server and an address of the first server; and

downloading, from the first server and in response to execution of the boot file in conjunction with the initialization file, a boot sector contained within the image file;

issuing, as a result of executing the boot sector, each of said plurality of requests, to the second server, to download the contents of the plurality of corresponding sectors that collectively store the image file; and

starting execution of various client O/S processes in the client computer as sufficient O/S files are downloaded on a sector-by-sector basis from the image file stored on the first server.

11. The method in claim 10 wherein the plurality of requests issuing step comprises the step of generating a separate random access trivial file transfer protocol (RATFTP) read request message to an RATFTP server in the first server in order to download a corresponding one of the sectors of the image file, wherein the RATFTP server implements sectorized access to the image file.

12. The method in claim 10 wherein the controlling step comprises the step of controlling the changeover based on whether sufficient active resources then exist in client O/S as it is booting.

13. The method in claim 10 wherein the detecting step comprises the step of employing a semaphore-based procedure for detecting said transition in the client processing mode.

14. The method in claim 10 wherein the first and second servers are the same server or different servers connected to the network.

15. The method in claim 5 further comprising the steps, in the client computer, of:

executing predefined boot code stored in the client computer which, in response thereto, broadcasts a client IP (Internet protocol) request message on the network, said client IP request message containing an address of the network interface situated in the client computer;

obtaining, from the second server, a reply message to the client IP request message, wherein the reply message contains an IP address assigned to the client computer, an IP address of the first server and an address of the boot file stored on the second server, wherein the boot file contains the real-mode client disk emulation code and a name of an initialization file;

downloading the boot file from the second server;

executing the emulation code contained in the boot file, once it has been downloaded, so as to initiate real-mode client disk emulation through the second server and thereafter to download the initialization file from the second server, wherein the initialization file contains an address of the image file residing on the first server and an address of the first server; and

downloading, from the first server and in response to execution of the boot file in conjunction with the initialization file, a boot sector contained within the image file;

issuing, as a result of executing the boot sector, each of said plurality of requests, to the second server, to download the contents of the plurality of corresponding sectors that collectively store the image file; and

starting execution of various client O/S processes in the client computer as sufficient O/S files are downloaded on a sector-by-sector basis from the image file stored on the first server.

16. The method in claim 15 wherein the plurality of requests issuing step comprises the step of generating a separate random access trivial file transfer protocol (RATFTP) read request message to an RATFTP server in the first server in order to download a corresponding one of the sectors of the image file, wherein the RATFTP server implements sectorized access to the image file.

17. The method in claim 15 wherein the first and second servers are the same server or different servers connected to the network.

18. Apparatus for booting an operating system (O/S) to a client computer from a network, the network storing an image on a first server, the image having O/S files for the client computer, the apparatus comprising a client computer having;

(a) a processor; and

(b) a memory, connected to the processor, for storing executable computer instructions therein; and

(c) wherein the processor, in response to the instructions;

(c1) issues a corresponding request to the first server to download contents of a corresponding one of each of a plurality of sectors residing on the first server so as to form a plurality of requests, wherein;

(c1a) said sectors collectively store an image file which contains the image; and

(c1b) the first server emulates, in response to said plurality of requests, behavior of a disk drive on the client computer such that contents of individual physical sectors of the image file specified in corresponding ones of the requests are accessed by the first server on a sector-by-sector basis from a disk drive associated with the first server and downloaded, via the network, to the client computer, and wherein the processor further;

(c1c) generates a request, to the first server, to download a boot sector contained in the image file; and

(c1d) executes the boot sector, once the boot sector is downloaded from the first server, so as to subsequently generate each of said plurality of requests such that the client computer receives, on a sector-by-sector basis from the first server, the contents of the individual physical sectors that collectively comprise client O/S files;

(c2) stores the contents of each of said sectors received from the first server; and

(c3) activates client O/S processes embodied by the contents of said sectors stored on the client computer.

19. The apparatus in claim 18 wherein the processor, in response to the executable instructions:

obtains, from a second server, an address of the image file stored on the first server.

20. The apparatus in claim 19 wherein the processor, in response to the executable instructions:

obtains a boot file from a second network server, the boot file comprising real-mode client disk emulation code; and

produces the boot sector download request through executing the boot file, wherein the boot sector request contains an identification of the first server and the name of the image file.

21. The apparatus in claim 20 wherein the first and second servers are the same server or different servers connected to the network.

22. The apparatus in claim 20 wherein the image comprises client O/S files and application program files.

23. The apparatus in claim 20 wherein the first server provides the client disk emulation, on a sectorized basis, while a processing mode of the client computer changes from real to protected and the client O/S takes ownership of a network interface situated in the client computer and connected to the network.

24. The apparatus in claim 23 wherein the processor, in response to the executable instructions:

downloads, as part of the image file, a transport driver; and

executes, as one of the client O/S processes, the transport driver such that each of the client disk access requests, generated by the client computer while the client O/S is being booted, is directed to the first server so as to retrieve contents of a corresponding sector of the image file stored on the first server in lieu of accessing a sector associated with a disk locally situated at the client computer, whereby, through use of the transport driver and while the client O/S is being booted, an actual source of the contents of the sectors remains transparent to the client O/S.

25. The apparatus in claim 24 wherein the processor, in response to the executable instructions:

handles, while the client computer is operating in the real processing mode, client disk access operations through a real mode interrupt handler procedure so as to generate ones of the plurality of requests;

handles, while the client computer is operating in the protected mode, client disk access operations through pre-defined client O/S network procedures so as to generate subsequent ones of the plurality of requests;

detects, as the client O/S processes are being activated, a transition in the client processing mode from real to protected; and

during the transition, controls a changeover in handling client disk access operations from the real mode interrupt handling procedure to the client O/S network procedures to generate said subsequent ones of the plurality of requests.

26. The apparatus in claim 25 wherein the pre-defined client O/S network procedures comprise an input/output subsystem (IOS) process and network driver interface specification (NDIS) process.

27. The apparatus in claim 25 wherein the processor, in response to the executable instructions, controls the changeover based on whether sufficient active resources then exist in client O/S as it is booting.

28. The apparatus in claim 25 wherein processor, in response to the executable instructions, employs a semaphore-based procedure for detecting said transition in the client processing mode.

29. The apparatus in claim 25 wherein the processor, in response to the executable instructions:

executes predefined boot code stored in the client computer which, in response thereto, broadcasts a client IP (Internet protocol) request message on the network, said client IP request message containing an address of the network interface situated in the client computer;

obtains, from the second server, a reply message to the client IP request message, wherein the reply message contains an IP address assigned to the client computer, an IP address of the first server and an address of the boot file stored on the second server, wherein the boot file contains the real-mode client disk emulation code and a name of an initialization file;

downloads the boot file from the second server;

executes the emulation code contained in the boot file, once it has been downloaded, so as to initiate real-mode client disk emulation through the second server and thereafter to download the initialization file from the second server, wherein the initialization file contains an address of the image file residing on the first server and an address of the first server; and

downloads, from the first server and in response to execution of the boot file in conjunction with the initialization file, a boot sector contained within the image file;

issues, as a result of executing the boot sector, each of said plurality of requests, to the second server, to download the contents of the plurality of corresponding sectors that collectively store the image file; and

starts execution of various client O/S processes in the client computer as sufficient O/S files are downloaded on a sector-by-sector basis from the image file stored on the first server.

30. The apparatus in claim 29 wherein the processor, in response to the executable instructions, generates a separate random access trivial file transfer protocol (RATFTP) read request message to an RATFTP server in the first server in order to download a corresponding one of the sectors of the image file, wherein the RATFTP server implements sectorized access to the image file.

31. The apparatus in claim 29 wherein the pre-defined client O/S network procedures comprise an input/output subsystem (IOS) process and network driver interface specification (NDIS) process.

32. The apparatus in claim 29 wherein the processor, in response to the executable instructions, controls the changeover based on whether sufficient active resources then exist in client O/S as it is booting.

33. The apparatus in claim 29 wherein the processor, in response to the executable instructions, employs a semaphore-based procedure for detecting said transition in the client processing mode.

34. The apparatus in claim 29 wherein the first and second servers are the same server or different servers connected to the network.

35. The apparatus in claim 29 wherein the image comprises client O/S files and application program files.

36. The apparatus in claim 23 wherein the processor, in response to the executable instructions:

executes predefined boot code stored in the client computer which, in response thereto, broadcasts a client IP (Internet protocol) request message on the network, said client IP request message containing an address of the network interface situated in the client computer;

obtains, from the second server, a reply message to the client IP request message, wherein the reply message contains an IP address assigned to the client computer, an IP address of the first server and an address of the boot file stored on the second server, wherein the boot file contains the real-mode client disk emulation code and a name of an initialization file;

downloads the boot file from the second server;

executes the emulation code contained in the boot file, once it has been downloaded, so as to initiate real-mode client disk emulation through the second server and thereafter to download the initialization file from the second server, wherein the initialization file contains an address of the image file residing on the first server and an address of the first server; and

downloads, from the first server and in response to execution of the boot file in conjunction with the initialization file, a boot sector contained within the image file;

issues, as a result of executing the boot sector, each of said plurality of requests, to the second server, to download the contents of the plurality of corresponding sectors that collectively store the image file; and

starts execution of various client O/S processes in the client computer as sufficient O/S files are downloaded on a sector-by-sector basis from the image file stored on the first server.

37. The apparatus in claim 36 wherein the processor, in response to the executable instructions, generates a separate random access trivial file transfer protocol (RATFTP) read request message to an RATFTP server in the first server in order to download a corresponding one of the sectors of the image file, wherein the RATFTP server implements sectorized access to the image file.

38. The apparatus in claim 36 wherein the first and second servers are the same server or different servers connected to the network.

39. The apparatus in claim 36 wherein the image comprises client O/S files and application program files.