USRE44299E1 - System and method for enabling automated run-time input to network bootstrapping processes - Google Patents
System and method for enabling automated run-time input to network bootstrapping processes Download PDFInfo
- Publication number
- USRE44299E1 USRE44299E1 US12/756,653 US75665310A USRE44299E US RE44299 E1 USRE44299 E1 US RE44299E1 US 75665310 A US75665310 A US 75665310A US RE44299 E USRE44299 E US RE44299E
- Authority
- US
- United States
- Prior art keywords
- computer device
- configuration file
- bootstrap
- instructions
- memory block
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
Definitions
- the invention relates to a system and method for providing automated run-time input to network bootstrap processes.
- bootstrapping a process commonly known as “booting” or “bootstrapping” is executed.
- the bootstrapping process employs a “bootstrap” program that contain a specific set of instructions to initialize and load the operating system that manages the computer device.
- bootstrap programs were stored in the computer device's memory.
- PXE Pre-boot Execution Environment
- the computer device is configured with some type of code in non-volatile memory that will enable the device to obtain the identity of the appropriate bootstrap program from the remote server. The computer device may then gain access and load the identified bootstrap program from a remote file server. Once loaded, the bootstrap program then obtains the operating system image used to manage the device.
- the system may include on or more computer devices communicatively coupled to a management server and a TFTP server.
- the management server may store one or more boot options used to provide a first set of bootstrap instructions.
- the TFTP server may store one or more configuration files used to control the boot process of the computer device. Each configuration file may include one or more macros.
- the first set of bootstrap instructions may include a boot determination module and an initialization module.
- the boot determination module may be configured to determine an appropriate configuration file for the computer device and to determine the values for any macros included in the configuration file.
- the initialization module may be configured to choose an arbitrary block of memory not used for other processing. This block of memory may be used to store the name of the configuration file and the values of the macros, as determined by the boot determination module.
- a request may be sent to the management server to obtain a first set of bootstrap instructions.
- the first set of bootstrap instructions determines a configuration file corresponding to the computer device based in part on a unique attribute associated with the computer device.
- a memory block is then initialized with the name of the configuration file and values for any macros in the configuration file.
- the first set of bootstrap instructions then launches a second set of bootstrap instructions used to initiate the booting of the computer device.
- the second set of bootstrap instructions may parse the memory block to determine the needed configuration file.
- the second set of bootstrap instructions may then parse the configuration file, resolving any macros by referring to the memory block.
- FIG. 1 depicts a system enabling run-time input, in accordance with various embodiments of the invention.
- FIG. 2 depicts a block diagram of an initial bootstrap program, in accordance with various embodiments of the invention.
- FIG. 3 depicts a sample memory block, in accordance with various embodiments of the invention.
- FIG. 4 depicts a process for configuring a computer device using run-time input, according to various embodiments of the invention.
- the present invention contemplates systems and methods that enable automated run-time input to network bootstrap processes. These systems and methods allow a determination to be made at boot time whether a computer device should boot the operating system installed in the computer device's memory or download and boot a special purpose operating system to accomplish an assigned task.
- the required input parameters may be supplied without user input or intervention.
- a memory block may be initialized to store parameter values that would otherwise require user input.
- FIG. 1 depicts system 100 that includes one or more computer devices 11 a-n communicatively coupled, via a network, to management server 120 .
- system 100 further includes trivial file transport protocol (TFTP) server 130 .
- TFTP trivial file transport protocol
- the network may comprise a local area network (LAN), wide area network (WAN), an intranet, the Internet, or any other type of network suitable for such purposes.
- management server 120 and TFTP server 130 are illustrated as separate devices, a single server mechanism may be used.
- computer device 110 n may include a bootstrap loading module 112 n and a memory device 114 n.
- Memory device 114 n may be a portion of an internal memory device within computer device 110 n.
- computer device 110 n may be configured to contact management server 120 to request the identity of a bootstrap program.
- Bootstrap loading module 112 n may be configured to retrieve the identified bootstrap program from management server 120 and install and execute the bootstrap program.
- Management server 120 may be configured to store boot options 120 n consistent with the operation of computer device 110 n. According to some embodiments of the invention, management server 120 may comprise a PXE boot server.
- TFTP server 130 may be constructed and arranged to store one or more configuration files 130 n.
- Such configuration files may be designed to enable run-time inputs to a bootstrap program, in accordance with various embodiments of the present invention.
- Configuration file 130 n may include one or more macros. The macros enable configuration file 130 n to be used by a plurality of computer devices having different booting requirements.
- configuration file 130 n may store kernel parameters, such as, for example, the IP address of a policy server. By including a macros instead of the actual value of the parameter, the configuration file may be used by devices with differing parameters.
- initial bootstrap program 200 may include one or more modules, such as, for example, boot determination module 202 and initialization module 204 .
- Boot determination module 202 may be configured to determine how computer device 110 n should boot. For example, boot determination module 202 may determine whether computer device 110 n should boot using PXELINUX or some other boot loading application.
- Boot determination module 202 may also determine which configuration file 130 n should be used. For example, determining which configuration file 130 n to use may be determined by analyzing the computer's MAC address, serial number, hardware profile, and/or other characteristics. Boot determination module 202 may be configured to read data from the hard drive of computer device 110 n to determine the appropriate configuration file. In other embodiments, the configuration file 130 n may be passed to a second bootstrap program, which will be described below, via a custom DHCP tag.
- Each configuration file 130 a- 130 n may include macros as values for one or more fields. These macros may be resolved at runtime and their values substituted for the macro. As such, boot determination module 202 may also be configured to determine the values of any macros included in the selected configuration file. The appropriate configuration file and the appropriate values for macros within the configuration file may be determined by consulting a device profile associated with the computer device.
- initial bootstrap program 200 may also include an initialization module 204 .
- Initialization module 204 may be configured to store the macro values and related information used in the configuration file 130 n on computer device 110 n. The stored information may be stored in a dedicated area of memory device 114 n, that is, an area not used for other processing.
- FIG. 3 depicts a sample block of memory 300 that may be used for storing macro values used by configuration file 130 n.
- Memory block 300 may include signature 302 to identify the start of the memory block, a version field 304 , a length field 306 , a macro number field 308 , and one or more macro-value fields 304 .
- the contents of memory block 300 depicted in FIG. 3 are intended only to be exemplary. Additional and/or other values may be stored in memory block 300 , as defined by an administrator.
- the number of macro-value pairs in memory block 300 is determined by the requirements of the configuration file.
- the first macro-value pair in macro-value field 310 may indicate the name of the configuration file to use. The name and value for each macro used in the configuration file may then be included in subsequent fields.
- an initial network bootstrap program (NBP) is loaded on computer device 110 n.
- NBP network bootstrap program
- this may occur as the result of a request from computer device 110 n to management server 120 upon startup to determine how computer device 110 n should boot.
- computer device 110 n may boot from its local hard drive.
- computer device 110 n may need to perform a specific task assigned by an administrator. As such, computer device 110 n may be directed to download a specific bootstrap program to accomplish the specific task.
- the initial NBP may be configured to determine the appropriate configuration file and to initialize a block of memory used to determine the appropriate configuration file and macro values, as depicted at operation 404 .
- the appropriate configuration file may be determined by examining the MAC address and/or other device features. The device features may be compared to predetermined profiles to determine which configuration file is needed, and the values of any macros included in the configuration file.
- the name of the configuration file may be passed to a secondary NBP.
- the initial NBP may also initialize a memory block. Initializing the memory block may include storing the name of the appropriate configuration file and macro-value pairs used to resolve any macros in the configuration file. As discussed below, such initialization enables a secondary NBP to determine the appropriate configuration file and macro values.
- a secondary NBP is launched, as depicted at operation 406 .
- the initial NBP causes the secondary NBP to be loaded onto computer device 110 n from management server 120 .
- the secondary NBP may then parse the memory block to determine the appropriate configuration file.
- the secondary NBP enables the computer device to boot in accordance with the contents of the configuration file.
- the secondary NBP may receive the name of the configuration file through a customized DHCP tag, thus eliminating the need to parse the memory block to determine the appropriate configuration file.
- the secondary NBP may then parse the configuration file, looking up the values for any macros encountered in the configuration file by consulting the memory block.
- the address in the configuration file may be changed to a macro so that its value is determined on the fly. As such, the configuration file would not have to be changed each time it is deployed to other servers.
- the initial NBP would create and initialize an input memory block.
- the memory block would specify the name of the configuration file and the value of the address macro used in the configuration file.
- the secondary NBP When the secondary NBP is loaded, it then parses the input memory block, determines the configuration file that it should use, and parses the configuration file. While parsing the configuration file, the secondary NBP encounters the address macro, looks up the value in the memory block, and substitutes the value for the macro.
- the computer device is capable of booting a special purpose operating system to accomplish an assigned task without the need for immediate user input or intervention.
- boot determination module 202 may be configured to obtain characteristics associated with a requesting computer device, in order to determine the run time parameters needed by the secondary bootstrap program.
- the determined runtime parameters may be stored in memory device 114 n.
- the secondary bootstrap program may then be loaded to complete the boot process.
- the secondary boot process may consult memory block 114 n whenever user input would ordinarily be required. Rather than waiting for user input, the bootstrap program is able to continue by reading the appropriate values from memory block 114 n.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
A system and method are provided for enabling runtime parameter value input into a computer device during a network bootstrapping process. The system and method may use a memory block to store values needed at runtime that are ordinarily input by a user. A configuration file having one or more macros included may be stored at a TFTP server. A first bootstrap program is loaded on the computer device to initialize a memory block with the name of the configuration file to be used by the computer device during booting and the values for any macros included in the configuration file. The first bootstrap program then calls a second bootstrap program to parse the memory block and/or the configuration file in order to use the contents of the configuration file to boot the computer device. Using macros in the configuration files enable the same configuration file to be used by devices with differing booting needs.
Description
The invention relates to a system and method for providing automated run-time input to network bootstrap processes.
During the startup of a computer device, a process commonly known as “booting” or “bootstrapping” is executed. The bootstrapping process employs a “bootstrap” program that contain a specific set of instructions to initialize and load the operating system that manages the computer device. Traditionally, such bootstrap programs were stored in the computer device's memory.
Many computer devices, however, currently support network booting processes that enable the devices to communicate with a remote server and obtain system files over a network. Examples of such processes include the use of the Pre-boot Execution Environment (PXE) to download an operating system from a network. Generally, for such processes, the computer device is configured with some type of code in non-volatile memory that will enable the device to obtain the identity of the appropriate bootstrap program from the remote server. The computer device may then gain access and load the identified bootstrap program from a remote file server. Once loaded, the bootstrap program then obtains the operating system image used to manage the device.
Existing network bootstrap programs are geared towards allowing the user to have the flexibility to boot in almost any manner he chooses. These programs typically require entry of input parameters by the user during the run time of the bootstrapping process and, therefore, have no mechanisms to automate the boot selection process or the entry of input parameters.
A system and method are provided for enabling automated run-time input during a network bootstrapping process. The system may include on or more computer devices communicatively coupled to a management server and a TFTP server. The management server may store one or more boot options used to provide a first set of bootstrap instructions. The TFTP server may store one or more configuration files used to control the boot process of the computer device. Each configuration file may include one or more macros.
The first set of bootstrap instructions may include a boot determination module and an initialization module. The boot determination module may be configured to determine an appropriate configuration file for the computer device and to determine the values for any macros included in the configuration file.
The initialization module may be configured to choose an arbitrary block of memory not used for other processing. This block of memory may be used to store the name of the configuration file and the values of the macros, as determined by the boot determination module.
When a computer device first powers on, a request may be sent to the management server to obtain a first set of bootstrap instructions. The first set of bootstrap instructions then determines a configuration file corresponding to the computer device based in part on a unique attribute associated with the computer device.
A memory block is then initialized with the name of the configuration file and values for any macros in the configuration file. The first set of bootstrap instructions then launches a second set of bootstrap instructions used to initiate the booting of the computer device.
The second set of bootstrap instructions may parse the memory block to determine the needed configuration file. The second set of bootstrap instructions may then parse the configuration file, resolving any macros by referring to the memory block.
In accordance with the various disclosed embodiments, the present invention contemplates systems and methods that enable automated run-time input to network bootstrap processes. These systems and methods allow a determination to be made at boot time whether a computer device should boot the operating system installed in the computer device's memory or download and boot a special purpose operating system to accomplish an assigned task. The required input parameters may be supplied without user input or intervention. For example, a memory block may be initialized to store parameter values that would otherwise require user input.
Consistent with these embodiments, FIG. 1 depicts system 100 that includes one or more computer devices 11a-n communicatively coupled, via a network, to management server 120. According to some embodiments of the invention, system 100 further includes trivial file transport protocol (TFTP) server 130. It will be appreciated that the network may comprise a local area network (LAN), wide area network (WAN), an intranet, the Internet, or any other type of network suitable for such purposes. Furthermore, while management server 120 and TFTP server 130 are illustrated as separate devices, a single server mechanism may be used.
As depicted in FIG. 1 , computer device 110n may include a bootstrap loading module 112n and a memory device 114n. Memory device 114n may be a portion of an internal memory device within computer device 110n. Upon startup, computer device 110n may be configured to contact management server 120 to request the identity of a bootstrap program. Bootstrap loading module 112n may be configured to retrieve the identified bootstrap program from management server 120 and install and execute the bootstrap program.
As noted above, when computer device 110n is powered on, it is configured to send a bootstrap request to management server 120. In response to this request, computer device 110n may receive an initial bootstrap program 200. As depicted in FIG. 2 , initial bootstrap program 200 may include one or more modules, such as, for example, boot determination module 202 and initialization module 204. Boot determination module 202 may be configured to determine how computer device 110n should boot. For example, boot determination module 202 may determine whether computer device 110n should boot using PXELINUX or some other boot loading application.
Each configuration file 130a-130n may include macros as values for one or more fields. These macros may be resolved at runtime and their values substituted for the macro. As such, boot determination module 202 may also be configured to determine the values of any macros included in the selected configuration file. The appropriate configuration file and the appropriate values for macros within the configuration file may be determined by consulting a device profile associated with the computer device.
As noted above, initial bootstrap program 200 may also include an initialization module 204. Initialization module 204 may be configured to store the macro values and related information used in the configuration file 130n on computer device 110n. The stored information may be stored in a dedicated area of memory device 114n, that is, an area not used for other processing.
The number of macro-value pairs in memory block 300 is determined by the requirements of the configuration file. According to some embodiments, the first macro-value pair in macro-value field 310 may indicate the name of the configuration file to use. The name and value for each macro used in the configuration file may then be included in subsequent fields.
Turning now to FIG. 4 , a process 400 for configuring a computer device 110n with run-time input is presented, in accordance with embodiments of the present invention. As depicted at operation 402, an initial network bootstrap program (NBP) is loaded on computer device 110n. As noted above, this may occur as the result of a request from computer device 110n to management server 120 upon startup to determine how computer device 110n should boot. In some embodiments of the invention, computer device 110n may boot from its local hard drive. However, in other embodiments, computer device 110n may need to perform a specific task assigned by an administrator. As such, computer device 110n may be directed to download a specific bootstrap program to accomplish the specific task.
The initial NBP may be configured to determine the appropriate configuration file and to initialize a block of memory used to determine the appropriate configuration file and macro values, as depicted at operation 404. As discussed above, the appropriate configuration file may be determined by examining the MAC address and/or other device features. The device features may be compared to predetermined profiles to determine which configuration file is needed, and the values of any macros included in the configuration file. In other embodiments, the name of the configuration file may be passed to a secondary NBP.
As noted above, in addition to determining the appropriate configuration file at operation 404, the initial NBP may also initialize a memory block. Initializing the memory block may include storing the name of the appropriate configuration file and macro-value pairs used to resolve any macros in the configuration file. As discussed below, such initialization enables a secondary NBP to determine the appropriate configuration file and macro values.
Once the memory block has been initialized, a secondary NBP is launched, as depicted at operation 406. The initial NBP causes the secondary NBP to be loaded onto computer device 110n from management server 120. As depicted at operation 408, the secondary NBP may then parse the memory block to determine the appropriate configuration file. The secondary NBP enables the computer device to boot in accordance with the contents of the configuration file. As described above, the secondary NBP may receive the name of the configuration file through a customized DHCP tag, thus eliminating the need to parse the memory block to determine the appropriate configuration file. The secondary NBP may then parse the configuration file, looking up the values for any macros encountered in the configuration file by consulting the memory block.
An exemplary embodiment of the invention is further illustrated by the following example. Suppose that to boot a computer device for a specific task, the following configuration file is needed:
| File Name: pxelinux.cfg/default | |
| File Contents: Server_Location = 10.0.0.1 | |
If this same service is deployed on a different server, then that server would need its own copy of “pxelinux.cfg/default”. The file contents would need to be modified to reflect the second server's address. According to various embodiments of the invention, the address in the configuration file may be changed to a macro so that its value is determined on the fly. As such, the configuration file would not have to be changed each time it is deployed to other servers.
As described above, the initial NBP would create and initialize an input memory block. The memory block would specify the name of the configuration file and the value of the address macro used in the configuration file. When the secondary NBP is loaded, it then parses the input memory block, determines the configuration file that it should use, and parses the configuration file. While parsing the configuration file, the secondary NBP encounters the address macro, looks up the value in the memory block, and substitutes the value for the macro.
In this manner, the computer device is capable of booting a special purpose operating system to accomplish an assigned task without the need for immediate user input or intervention.
While described above in reference to the use of configuration files and macros to provide runtime input, the system and method of the present invention may otherwise provide runtime input. According to some embodiments of the invention, boot determination module 202, described above, may be configured to obtain characteristics associated with a requesting computer device, in order to determine the run time parameters needed by the secondary bootstrap program.
The determined runtime parameters may be stored in memory device 114n. The secondary bootstrap program may then be loaded to complete the boot process. The secondary boot process may consult memory block 114n whenever user input would ordinarily be required. Rather than waiting for user input, the bootstrap program is able to continue by reading the appropriate values from memory block 114n.
Other embodiments, uses, and advantages of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification should be considered exemplary only, and the scope of the invention is accordingly intended to be limited only by the following claims.
Claims (33)
1. A method of providing runtime input to a computer device during a network bootstrapping process, comprising:
providing a first set of bootstrap instructions to the computer device, the first set of bootstrap instructions configured to:
determine a configuration file corresponding to the computer device based at least in part on a unique attribute associated with the computer device;
determine one or more values associated with one or more macros in the configuration file; and
initialize a memory block with the one or more values associated with the one or more macros; and
generating a second set of bootstrap instructions, wherein the second set of bootstrap instructions is configured to parse the memory block to retrieve the one or more values and to initiate the booting bootstrapping process of on the computer device.
2. The method of claim 1 , wherein the first set of bootstrap instructions configured to initialize the memory block further comprises instructions configured to store the one or more values associated with the one or more macros.
3. The method of claim 2 , wherein the first set of bootstrap instructions configured to initialize the memory block further comprises instructions to:
store a signature identifying the an existence of the memory block; and
store a value indicating the a number of the macros used in the configuration file.
4. The method of claim 1 wherein the first set of bootstrap instructions is terminated when the second set of bootstrap instructions is generated.
5. The method of claim 1 , wherein the second set of bootstrap instructions is launched by the first set of bootstrap instructions.
6. The A method of claim 1 for providing runtime input values to a computer device during a network bootstrapping process, comprising:
providing a first set of bootstrap instructions to the computer device;
determining a configuration file corresponding to the computer device based at least in part on a unique attribute associated with the computer device;
initializing a memory block with parameter values identified in the configuration file; and
generating a second set of bootstrap instructions, wherein the second set of bootstrap instructions is further configured to:
determine what the configuration file corresponding to employ the computer device;
parse the configuration file corresponding to the computer device; and
parse the memory block to retrieve the parameter values for the macros identified in the parsed configuration file; and
initiate the bootstrapping process on the computer device with the parameter values retrieved from the parsed memory block.
7. The method of claim 6 , wherein the second set of bootstrap instructions is further configured to determine what the configuration file corresponding to employ the computer device by parsing the memory block to determine an appropriate the configuration file corresponding to the computer device.
8. The method of claim 6 , wherein the second set of bootstrap instructions is further configured to determine what the configuration file corresponding to employ the computer device by identifying the configuration file from a customized DHCP tag.
9. The method of claim 1 , wherein the unique attribute is the a media access control (MAC) address associated with the computer device.
10. The method of claim 1 , wherein the first set of bootstrap instructions is further configured to determine an appropriate boot environment for the computer device.
11. The method of claim 10 , wherein the boot environment is PXELINUX.
12. The method of claim 1 , wherein the first set of bootstrap instructions configured to initialize the memory block further comprises instructions configured to store the a name of the determined configuration file.
13. The method of claim 1 , wherein the first set of bootstrap instructions is further configured to determine one or more values associated with one or more macros by consulting a device profile associated with the computer device.
14. A system for providing runtime input into a computer device during a network bootstrapping process, comprising:
a first server mechanism configured to provide a first set of bootstrap instructions, the first set of bootstrap instructions including an initialization module and a boot determination module;
a second server mechanism configured to provide one or more configuration files comprising one or more macros, wherein the one or more configuration files control the boot bootstrapping process of on the computer device; and
a bootstrap loading module, incorporated within the computer device, configured to retrieve and install the first set of bootstrap instructions;
wherein the first set of bootstrap instructions is configured to launch a second set of bootstrap instructions, and
wherein the boot determination module comprises:
a mechanism for determining an appropriate boot environment for the computer device;
a mechanism for determining a configuration file associated with the computer device; and
a mechanism to determine one or more values associated with the one or more macros in the configuration file.
15. The system of claim 14 , wherein the second server mechanism is a TFTP server.
16. The system of claim 14 , wherein the initialization module further comprises a memory initialization mechanism for selecting a memory block for storing boot processing information relating to the bootstrapping process.
17. A computer device capable of accepting runtime input during a network bootstrapping process, comprising:
a bootstrap loading module configured to retrieve and install a first set of bootstrap instructions; and
a memory device configured to store one or more values associated with one or more macros in one or more configuration files used in the bootstrapping process;
wherein the first set of bootstrap instructions is configured to:
determine a configuration file corresponding to the computer device;
determine one or more values associated with the one or more macros in the configuration file; and
initialize the memory device and store the one or more values associated with the one or more macros.
18. The computer device of claim 17 , wherein the bootstrap loading module is configured to contact a server mechanism to retrieve the first set of bootstrap instructions when the device starts up.
19. The computer device of claim 17 , wherein the bootstrap loading module is further configured to retrieve a second set of bootstrap instructions.
20. The computer device of claim 19 , wherein the second set of bootstrap instructions is configured to parse the configuration file and parse the memory device to retrieve the values for the macros identified in the parsed configuration file, and to use the retrieved values and the configuration file to boot the computer device.
21. A method of providing runtime input to a computer device during a network bootstrapping process, comprising:
providing a first set of bootstrap instructions to the computer device, the first set of bootstrap instructions configured to:
determine a configuration file associated with the computer device;
consult a device profile to determine one or more values associated with one or macros in the configuration file, the one or more values needed to complete the bootstrapping process; and
initialize a memory block with the one or more values; and
generating a second set of bootstrap instructions, wherein the second set of bootstrap instructions is configured to parse the memory block to retrieve the one or more values to complete the bootstrapping process.
22. The method of claim 6, wherein the first set of bootstrap instructions initializes the memory block by storing the parameter values identified in the configuration file in the memory block.
23. The method of claim 6, wherein the first set of bootstrap instructions is terminated in response to generating the second set of bootstrap instructions.
24. The method of claim 6, wherein the first set of bootstrap instructions launches the second set of bootstrap instructions.
25. The method of claim 6, wherein the unique attribute comprises a media access control (MAC) address associated with the computer device.
26. The method of claim 6, wherein the first set of bootstrap instructions determines an appropriate boot environment for the computer device.
27. The method of claim 26, wherein the boot environment is PXELINUX.
28. The method of claim 6, wherein the first set of bootstrap instructions initializes the memory block by storing a name of the determined configuration file in the memory block.
29. The method of claim 6, wherein the first set of bootstrap instructions identifies the parameter values in the configuration file by consulting a device profile associated with the computer device.
30. A system for providing runtime input values to a computer device during a network bootstrapping process, comprising:
a first server mechanism configured to provide a first set of bootstrap instructions to the computer device;
a second server mechanism configured to provide a configuration file corresponding to the computer device, wherein the configuration file comprises one or more parameter values that control the bootstrapping process on the computer device; and
a bootstrap loading module, incorporated within the computer device, configured to retrieve and install the first set of bootstrap instructions on the computer device, wherein the first set of bootstrap instructions is configured to:
determine the configuration file corresponding to the computer device based at least in part on a unique attribute associated with the computer device;
initialize a memory block with the one or more parameter values in the configuration file; and
launch the second set of bootstrap instructions, wherein the second set of bootstrap instructions is configured to:
determine the configuration file corresponding to the computer device;
parse the configuration file corresponding to the computer device;
parse the memory block to retrieve the parameter values identified in the parsed configuration file; and
initiate the bootstrapping process on the computer device with the parameter values retrieved from the parsed memory block.
31. A computer device for providing runtime input values to a computer device during a network bootstrapping process, comprising:
a bootstrap loading module configured to retrieve and install a first set of bootstrap instructions, wherein the first set of bootstrap instructions is configured to:
determine a configuration file corresponding to the computer device based at least in part on a unique attribute associated with the computer device; and
initialize a memory block with one or more parameter values identified in the configuration file;
a memory device configured to store the one or more parameter values in the memory block for use in the bootstrapping process; and
a second set of bootstrap instructions, wherein the second set of bootstrap instructions is configured to:
determine the configuration file corresponding to the computer device;
parse the configuration file corresponding to the computer device;
parse the memory block to retrieve the parameter values identified in the parsed configuration file; and
initiate the bootstrapping process on the computer device with the parameter values retrieved from the parsed memory block.
32. A method for providing runtime input values to a computer device during a network bootstrapping process, comprising:
providing a first set of bootstrap instructions to the computer device, the first set of bootstrap instructions configured to:
determine a configuration file corresponding to the computer device based at least in part on a unique attribute associated with the computer device;
identify one or more parameter values in the configuration file; and
initialize a memory block with the one or more parameter values identified in the configuration file; and
generating a second set of bootstrap instructions, wherein the second set of bootstrap instructions is configured to:
parse the memory block to retrieve the one or more parameter values identified in the configuration file; and
initiate the bootstrapping process on the computer device with the parameter values retrieved from the parsed memory block.
33. A method of providing runtime parameter value input to a computer device during a network bootstrapping process, comprising:
providing a first set of bootstrap instructions to the computer device;
determining a configuration file corresponding to the computer device based at least in part on a unique attribute associated with the computer device;
initializing a memory block with parameter values identified in the configuration file; and
generating a second set of bootstrap instructions, wherein the second set of bootstrap instructions is configured to:
determine what configuration file to employ;
parse the configuration file;
parse the memory block to determine the values of the parameters identified in the configuration file; and
initiate the booting process of the computer device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US12/756,653 USRE44299E1 (en) | 2005-07-01 | 2010-04-08 | System and method for enabling automated run-time input to network bootstrapping processes |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/171,266 US7356685B2 (en) | 2005-07-01 | 2005-07-01 | System and method for enabling automated run-time input to network bootstrapping processes |
| US12/756,653 USRE44299E1 (en) | 2005-07-01 | 2010-04-08 | System and method for enabling automated run-time input to network bootstrapping processes |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US11/171,266 Reissue US7356685B2 (en) | 2005-07-01 | 2005-07-01 | System and method for enabling automated run-time input to network bootstrapping processes |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| USRE44299E1 true USRE44299E1 (en) | 2013-06-11 |
Family
ID=37591212
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US11/171,266 Ceased US7356685B2 (en) | 2005-07-01 | 2005-07-01 | System and method for enabling automated run-time input to network bootstrapping processes |
| US12/756,653 Expired - Fee Related USRE44299E1 (en) | 2005-07-01 | 2010-04-08 | System and method for enabling automated run-time input to network bootstrapping processes |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US11/171,266 Ceased US7356685B2 (en) | 2005-07-01 | 2005-07-01 | System and method for enabling automated run-time input to network bootstrapping processes |
Country Status (1)
| Country | Link |
|---|---|
| US (2) | US7356685B2 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8738664B2 (en) * | 2012-05-23 | 2014-05-27 | Lg Chem, Ltd. | System and method for generating diagnostic test files associated with a battery pack |
| US20170104628A1 (en) * | 2015-10-12 | 2017-04-13 | Dell Products, Lp | System and Method to Replicate Server Configurations Across Systems Using Sticky Attributions |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7580837B2 (en) | 2004-08-12 | 2009-08-25 | At&T Intellectual Property I, L.P. | System and method for targeted tuning module of a speech recognition system |
| US7668889B2 (en) | 2004-10-27 | 2010-02-23 | At&T Intellectual Property I, Lp | Method and system to combine keyword and natural language search results |
| US7242751B2 (en) | 2004-12-06 | 2007-07-10 | Sbc Knowledge Ventures, L.P. | System and method for speech recognition-enabled automatic call routing |
| US7751551B2 (en) | 2005-01-10 | 2010-07-06 | At&T Intellectual Property I, L.P. | System and method for speech-enabled call routing |
| US7657020B2 (en) | 2005-06-03 | 2010-02-02 | At&T Intellectual Property I, Lp | Call routing system and method of using the same |
| US20070300054A1 (en) * | 2006-06-21 | 2007-12-27 | Shi-Wu Lo | Universal BSP tool for porting on embedded systems and an application thereof |
| US8681779B2 (en) * | 2006-09-01 | 2014-03-25 | Alcatel Lucent | Triple play subscriber and policy management system and method of providing same |
| US7814274B2 (en) * | 2007-01-19 | 2010-10-12 | Scalent Systems, Inc. | Method and system for dynamic binding in a storage area network |
| US8386757B1 (en) * | 2009-02-13 | 2013-02-26 | Unidesk Corporation | Managed desktop system |
| TWI502508B (en) * | 2010-06-18 | 2015-10-01 | Wistron Corp | Method for enhancing stability of a server in a preboot execution environment and server device using the same |
| US8677187B2 (en) * | 2011-04-01 | 2014-03-18 | Vmware, Inc. | Performing network core dump without drivers |
| US11537406B2 (en) * | 2020-02-18 | 2022-12-27 | Juniper Networks, Inc. | Automatic formation of a virtual chassis using zero touch provisioning |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030005096A1 (en) * | 2001-06-28 | 2003-01-02 | International Business Machines Corporation | Method and system for dynamic redistribution of remote computer boot service in a network containing multiple boot servers |
| US20030005276A1 (en) * | 2001-06-28 | 2003-01-02 | Ibm Corporation | Method and system for booting of a target device in a network environment based on automatic client discovery and scan |
| US6560699B1 (en) | 1999-10-20 | 2003-05-06 | Cisco Technology, Inc. | Constraint-based language configuration files for updating and verifying system constraints |
| US6598057B1 (en) | 1999-12-22 | 2003-07-22 | Cisco Technology, Inc. | Method and apparatus for generating configuration files using policy descriptions |
| US20030217126A1 (en) | 2002-05-14 | 2003-11-20 | Polcha Andrew J. | System and method for automatically configuring remote computer |
| US20040049671A1 (en) * | 2002-09-10 | 2004-03-11 | Jareva Technologies, Inc. | System for managing boot-up of target computers |
| US6735692B1 (en) | 2000-07-11 | 2004-05-11 | International Business Machines Corporation | Redirected network boot to multiple remote file servers |
| US6810478B1 (en) | 2000-12-12 | 2004-10-26 | International Business Machines Corporation | System for remote booting of muntliple operating systems using chained bootstrap mechanism in a network |
| US20040268340A1 (en) | 2003-06-25 | 2004-12-30 | Microsoft Corporation | Managing multiple devices on which operating systems can be automatically deployed |
| US20050097310A1 (en) * | 2003-10-31 | 2005-05-05 | International Business Machines Corporation | Method and system for restricting PXE servers |
| US20060047792A1 (en) | 2000-11-02 | 2006-03-02 | Microsoft Corporation | Dynamically configuring a server computer |
| US7013385B2 (en) | 2002-06-04 | 2006-03-14 | International Business Machines Corporation | Remotely controlled boot settings in a server blade environment |
| US20060129788A1 (en) | 2004-12-15 | 2006-06-15 | Masato Maeda | System and method for initially configuring and booting a device using a device identifier |
| US20060143146A1 (en) | 2004-12-27 | 2006-06-29 | International Business Machines Corporation | Dynamic configuration files |
| US7085921B2 (en) | 2001-12-31 | 2006-08-01 | Hewlett-Packard Development Company, L.P. | Embedded OS PXE server |
| US7159106B2 (en) | 2003-04-03 | 2007-01-02 | Dell Products L.P. | Information handling system manufacture method and system |
-
2005
- 2005-07-01 US US11/171,266 patent/US7356685B2/en not_active Ceased
-
2010
- 2010-04-08 US US12/756,653 patent/USRE44299E1/en not_active Expired - Fee Related
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6560699B1 (en) | 1999-10-20 | 2003-05-06 | Cisco Technology, Inc. | Constraint-based language configuration files for updating and verifying system constraints |
| US6598057B1 (en) | 1999-12-22 | 2003-07-22 | Cisco Technology, Inc. | Method and apparatus for generating configuration files using policy descriptions |
| US6735692B1 (en) | 2000-07-11 | 2004-05-11 | International Business Machines Corporation | Redirected network boot to multiple remote file servers |
| US20060047792A1 (en) | 2000-11-02 | 2006-03-02 | Microsoft Corporation | Dynamically configuring a server computer |
| US6810478B1 (en) | 2000-12-12 | 2004-10-26 | International Business Machines Corporation | System for remote booting of muntliple operating systems using chained bootstrap mechanism in a network |
| US20030005276A1 (en) * | 2001-06-28 | 2003-01-02 | Ibm Corporation | Method and system for booting of a target device in a network environment based on automatic client discovery and scan |
| US20030005096A1 (en) * | 2001-06-28 | 2003-01-02 | International Business Machines Corporation | Method and system for dynamic redistribution of remote computer boot service in a network containing multiple boot servers |
| US7085921B2 (en) | 2001-12-31 | 2006-08-01 | Hewlett-Packard Development Company, L.P. | Embedded OS PXE server |
| US20030217126A1 (en) | 2002-05-14 | 2003-11-20 | Polcha Andrew J. | System and method for automatically configuring remote computer |
| US7013385B2 (en) | 2002-06-04 | 2006-03-14 | International Business Machines Corporation | Remotely controlled boot settings in a server blade environment |
| US20040049671A1 (en) * | 2002-09-10 | 2004-03-11 | Jareva Technologies, Inc. | System for managing boot-up of target computers |
| US7159106B2 (en) | 2003-04-03 | 2007-01-02 | Dell Products L.P. | Information handling system manufacture method and system |
| US20040268340A1 (en) | 2003-06-25 | 2004-12-30 | Microsoft Corporation | Managing multiple devices on which operating systems can be automatically deployed |
| US20050097310A1 (en) * | 2003-10-31 | 2005-05-05 | International Business Machines Corporation | Method and system for restricting PXE servers |
| US20060129788A1 (en) | 2004-12-15 | 2006-06-15 | Masato Maeda | System and method for initially configuring and booting a device using a device identifier |
| US20060143146A1 (en) | 2004-12-27 | 2006-06-29 | International Business Machines Corporation | Dynamic configuration files |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8738664B2 (en) * | 2012-05-23 | 2014-05-27 | Lg Chem, Ltd. | System and method for generating diagnostic test files associated with a battery pack |
| US20170104628A1 (en) * | 2015-10-12 | 2017-04-13 | Dell Products, Lp | System and Method to Replicate Server Configurations Across Systems Using Sticky Attributions |
| US10200242B2 (en) * | 2015-10-12 | 2019-02-05 | Dell Products, Lp | System and method to replicate server configurations across systems using sticky attributions |
Also Published As
| Publication number | Publication date |
|---|---|
| US20070005950A1 (en) | 2007-01-04 |
| US7356685B2 (en) | 2008-04-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| USRE44299E1 (en) | System and method for enabling automated run-time input to network bootstrapping processes | |
| US11474829B2 (en) | Customizing program logic for booting a system | |
| US7363514B1 (en) | Storage area network(SAN) booting method | |
| US7631173B2 (en) | Method and system for performing pre-boot operations from an external memory including memory address and geometry | |
| US9507604B2 (en) | Boot method and boot system | |
| US20060200539A1 (en) | Determining a boot server network address from which to download an operating system during a boot sequence | |
| US7650490B2 (en) | Embedded device for implementing a boot process on a host | |
| US20030126426A1 (en) | Embedded OS PXE server | |
| US20040255106A1 (en) | Recovery of operating system configuration data by firmware of computer system | |
| US7159106B2 (en) | Information handling system manufacture method and system | |
| JP6228177B2 (en) | Method, computer program, and apparatus for optimizing loading and booting of an operating system over a communication network in a computer system | |
| US20030023839A1 (en) | Method and system for creating and employing an operating system having selected functionality | |
| US7882345B1 (en) | System, method, and apparatus for processor detection in a pre-boot execution environment | |
| JP2009536399A (en) | Operating system gradual boot process | |
| US6928538B2 (en) | Method and system for delayed booting of a target device in a network environment | |
| US11429298B2 (en) | System and method for tying non-volatile dual inline memory modules to a particular information handling system | |
| US20090254641A1 (en) | Network card capable of remote boot and method thereof | |
| US8140683B2 (en) | Method and system for selecting an operating system at user login on a target device | |
| US7257704B2 (en) | Method of selectively loading a pre-boot execution extension determined based on an identifier | |
| US9189351B2 (en) | Method of obtaining instruction for triggering function | |
| CN112486508B (en) | Deployment method of operating system, server and computer storage medium | |
| US9342316B1 (en) | Installing digital signage device operating system from flash memory and registering signage device to a global network | |
| US20200364040A1 (en) | System and Method for Restoring a Previously Functional Firmware Image on a Non-Volatile Dual Inline Memory Module | |
| CN111324384B (en) | Device and method for selecting starting image file according to device message in pre-execution environment | |
| US8245021B2 (en) | System and method for re-imaging computers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment |
Owner name: NOVELL, INC., UTAH Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BACKMAN, DRAKE;REEL/FRAME:024206/0905 Effective date: 20050629 |
|
| AS | Assignment |
Owner name: CPTN HOLDINGS LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOVELL,INC.;REEL/FRAME:027465/0227 Effective date: 20110427 Owner name: NOVELL INTELLECTUAL PROPERTY HOLDINGS, INC., WASHI Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CPTN HOLDINGS LLC;REEL/FRAME:027465/0206 Effective date: 20110909 |
|
| AS | Assignment |
Owner name: NOVELL INTELLECTUAL PROPERTY HOLDING, INC., WASHIN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CPTN HOLDINGS LLC;REEL/FRAME:027325/0131 Effective date: 20110909 |
|
| FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| FPAY | Fee payment |
Year of fee payment: 8 |
|
| AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOVELL INTELLECTUAL PROPERTY HOLDINGS, INC.;REEL/FRAME:037809/0057 Effective date: 20160208 |
|
| AS | Assignment |
Owner name: JEFFERIES FINANCE LLC, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:RPX CORPORATION;REEL/FRAME:046486/0433 Effective date: 20180619 |
|
| FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC;REEL/FRAME:054486/0422 Effective date: 20201023 |