JP2014174878A - Network boot system and network boot method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To resolve complicated processing based on an instruction from a maintenance person by uniformly managing setting information on respective servers associated with network boot operation.SOLUTION: A setting information management server 1 accepts registration of setting information on respective servers associated with network boot operation and distributes the setting information to the respective servers. A client 5 acquires an IPv4 address of itself and an IP address of a boot server 3 from a DHCPv4 server 2, and then acquires and executes a network boot image from a boot server 3 so as to acquire a start-up image. Then, the client 5 executes the start-up image so as to acquire an IPv6 address of itself from a DHCPv6 server 4. The setting information management server 1 collects information on a service result provided from the respective servers to the client 5 and uniformly stores states of network boot operation of the respective clients 5.

Description

  The present invention relates to a network boot system and a network capable of starting a computer by acquiring, via a network, start image data that reproduces an operating environment such as an OS (Operating System) and applications necessary for starting the computer. It relates to the boot method.

  In the business-oriented market, computer terminals called thin clients have been introduced mainly to improve the efficiency of security and operation management work. In thin clients, computer terminals (clients) used by employees have minimal functions, and in order to collectively manage resources such as application software and files on the server side, the operating environment of the client is set on the server side. A configurable network boot is used. Further, even in a system in which a conventional computer terminal is used as a client, automatic installation by network boot is performed in order to reduce installation work and to unify the operating environment of each client. In this automatic installation, setting of IPv6 (Internet Protocol version 6) addresses and the like that have become widespread in recent years is often automatically performed (for example, when ipv6 = dhcp is set in Non-Patent Document 1). .

Red Hat, Inc., “Red Hat Enterprise Linux Installation Guide 32.10 Starting Kickstart Installation”, [online], [Search March 2, 2013], Internet (URL: https://access.redhat.com/ knowledge / docs / en-US / Red_Hat_Enterprise_Linux / 6 / html / Installation_Guide / s1-kickstart2-startinginstall.html)

  FIG. 9 is a sequence diagram showing an operation example of a conventional network boot system. As shown in FIG. 9, in a conventional network boot system in which an IPv4 (Internet Protocol version 4) address and an IPv6 address coexist, an IPv4 compatible DHCPv4 (Dynamic Host Configuration Protocol version 4) server 2 and an IPv4 compatible boot server 3 In addition, the setting information is individually registered from the management terminal 6 to the DHCPv6 (same version 6) server 4 corresponding to IPv6 (steps S21 to S23).

  When the client 5 is powered on and starts a network boot (step S24), the network boot activation program stored in the ROM (Read Only Memory) of the communication board of the client 5 is executed, and first the DHCPv4 server 2 is loaded. The connection is made and the IPv4 address used by the client 5 is set (step S25). Since the IP address of the boot server 3 is notified to the client 5 through this setting, the client 5 next connects to the boot server 3 using the notified IP address, and should be executed by the boot server 3 itself. A startup image is acquired (step S26). Subsequently, the client 5 starts the operation in the necessary OS and application environment by executing the acquired startup image (step S27). Thereby, the connection from the client 5 to the DHCPv6 server 4 is performed, and the IPv6 address used by the client 5 is set (step S28).

  In this way, registration of various setting information to the DHCPv4 server 2, the boot server 3, and the DHCPv6 server 4 is performed separately, and information such as an IP address assigned to each client 5 is also managed individually for each server. Will be. Therefore, in order to confirm the setting for each client 5, it is necessary to execute a process of individually accessing each server from the management terminal 6 based on an instruction from the maintenance person (step S29).

  FIG. 10 is a sequence diagram showing an operation example when a boot error occurs in the conventional network boot system. As in the example of FIG. 10, it is assumed that a hardware failure or the like has occurred in the middle of step S26 after the client 5 has acquired an IPv4 address or the like from the DHCPv4 server 2 in step S25. In this case, in order to release the IPv4 address assigned to the client 5 and make it reusable, the management terminal 6 that has received the error notification from the boot server 3 in step S30 issues an instruction from the maintenance person. It is necessary to execute a process of accepting and instructing the DHCPv4 server 2 to release the IPv4 address assigned to the client 5 (step S31).

  A method of eliminating the complicated processing of the management terminal based on the instruction from the maintenance person as described above by consolidating all of these servers into one apparatus is conceivable. In this case, however, the load of the integrated apparatus is reduced. There is a problem of becoming high.

  The present invention has been made in order to solve the above-described problems. By distributing and processing the processing load of the DHCPv4 server, the boot server, and the DHCPv6 server, the setting information of each of these servers is stored and managed centrally. An object of the present invention is to eliminate complicated processing of a management terminal based on an instruction from a maintenance person, which was necessary in the past.

  In order to achieve the above object, the present invention provides a network boot system for providing a boot image including a process of acquiring an IPv6 address to one or more network bootable clients connected to an IP network, A boot server that provides the client with a network boot image including a process for acquiring a boot image, a first DHCP server that gives an IPv4 address to the client and notifies the IP address of the boot server, and the client A second DHCP server that assigns an IPv6 address; and a setting information management server that is communicably connected to each of the servers, wherein the setting information management server includes the boot server, the first DHCP server, And that of the second DHCP server When the registration of the setting information necessary for the service provided by the client is received, the setting information is distributed to each of these servers, and the client performs a network boot, the first DHCP server responds to the request from the client. Based on the request from the client, the boot server transmits the network boot image to the client based on a request from the client, and assigns an IPv4 address to the client and notifies the IP address of the boot server. The DHCP server gives the client an IPv6 address that requests acquisition when the client executes the boot image acquired by executing the network boot image, and the setting information management server further , From each of the servers Ianto collects service result information provided to the client along with the network boot was assumed that collectively stores the status of the network boot operation of each client.

  By doing so, it is possible to centrally store and manage the setting information of these servers while distributing the processing load of the DHCPv4 server, boot server, and DHCPv6 server.

  In the network boot system according to the present invention, if the network boot operation of the client ends abnormally after the client is given its IPv4 address from the first DHCP server, the abnormality is The detected boot server or the second DHCP server notifies the setting information management server of an error, and the setting information management server receiving the notification releases the IPv4 address to the first DHCP server. Was to be commanded.

  In this way, when the network boot operation ends abnormally in the middle, the IPv4 address assigned to the corresponding client is automatically released, so that complicated processing of the management terminal can be reduced.

  The present invention is also a network boot method for a network boot system that provides a boot image including processing for acquiring an IPv6 address to one or more network bootable clients connected to an IP network, the network boot system comprising: A boot server that provides the client with a network boot image including a process for obtaining the boot image, a first DHCP server that gives the client an IPv4 address and notifies the IP address of the boot server, A second DHCP server that assigns an IPv6 address to the client; and a setting information management server that is communicably connected to each of the servers. The setting information management server includes the boot server, the first server, 1 DHCP And registration of setting information necessary for the service provided by each of the server and the second DHCP server, and delivering the setting information to each of these servers, and when the client is network booted, A first DHCP server assigning an IPv4 address to the client based on a request from the client and notifying an IP address of the boot server; and the boot server based on a request from the client. Sending the network boot image to the client; and the second DHCP server requests acquisition when the client executes the boot image acquired by executing the network boot image. Address And the setting information management server notifies the client of the network based on the service result information provided to the client, which is notified from the servers as the client performs a network boot. Storing information indicating the progress status of the boot operation.

  By doing so, it is possible to centrally store and manage the setting information of these servers while distributing the processing load of the DHCPv4 server, boot server, and DHCPv6 server.

  In the network boot method according to the present invention, if the network boot operation of the client ends abnormally after the client is given its IPv4 address from the first DHCP server, the abnormality is The detected boot server or the second DHCP server notifies the setting information management server of an error, and the setting information management server receiving the notification releases the IPv4 address to the first DHCP server. Further including a step of commanding.

  In this way, when the network boot operation ends abnormally in the middle, the IPv4 address assigned to the corresponding client is automatically released, so that complicated processing of the management terminal can be reduced.

  According to the present invention, the processing load of the DHCPv4 server, the boot server, and the DHCPv6 server is distributed, and the setting information of each server is stored and managed in a centralized manner. The complicated processing of the management terminal based on can be eliminated.

It is a figure which shows the structural example of a network boot system. It is a figure which shows the structural example of the setting information delivered to a DHCPv4 server. It is a figure which shows the structural example of client management information. It is a sequence diagram which shows the network boot operation example at the time of applying a setting information management server. It is a detailed sequence diagram about setting operation | movement of an IPv4 address etc. It is a detailed sequence diagram about the acquisition operation of a starting image. It is a detailed sequence diagram about the setting operation of an IPv6 address or the like. It is a sequence diagram which shows the operation example when the boot error generate | occur | produces in the network boot system to which the setting information management server is applied. It is a sequence diagram which shows the operation example of the conventional network boot system. It is a sequence diagram which shows the operation example when the boot error generate | occur | produces in the conventional network boot system.

  Hereinafter, a mode for carrying out the present invention (hereinafter referred to as “the present embodiment”) will be described in detail with reference to the drawings as appropriate.

  FIG. 1 is a diagram illustrating a configuration example of a network boot system according to the present embodiment. As illustrated in FIG. 1, the network boot system 100 includes a setting information management server 1, a DHCPv4 server 2, a boot server 3, a DHCPv6 server 4, and a management terminal 6. The DHCPv4 server 2, the boot server 3, and the DHCPv6 server 4 are communicably connected to one or more network bootable clients 5 via an unillustrated IP (Internet Protocol) network such as a LAN (Local Area Network). Is done.

  The setting information management server 1 is communicably connected to the DHCPv4 server 2, the boot server 3, the DHCPv6 server 4, and the management terminal 6 via a LAN or a dedicated line. Note that the setting information management server 1 does not have to be an independent device, and may be integrated with any device of another server.

  The setting information management server 1 is configured by a computer including a control unit 11 and a storage unit 12. The control unit 11 includes a setting information registration unit 111, a setting information distribution unit 112, a client information management unit 113, a request information response unit 114, and a boot error processing unit 115. Each of these functional units is embodied by executing a predetermined setting information management program stored in the storage unit 12 by a CPU (Central Processing Unit) (not shown) included in the control unit 11. On the other hand, IPv4 address setting information 121, network boot image 122, IPv6 address setting information 123, client management information 124, and the like are stored in the storage unit 12 configured by a hard disk, a semiconductor memory, or the like.

  The setting information registration unit 111 receives registration of various setting information from the management terminal 6 operated by the maintenance person, and registers the information in the IPv4 address setting information 121, the network boot image 122, and the IPv6 address setting information 123. The setting information distribution unit 112 registers the setting information registered in the IPv4 address setting information 121 in the DHCPv4 server 2, the network boot image registered in the network boot image 122 in the boot server 3, and the IPv6 address setting information 123. The setting information is distributed to the DHCPv6 server 4.

  The client information management unit 113 manages information on the client 5 that executes the network boot operation. The request information response unit 114 receives a request for browsing various setting information from the management terminal 6, acquires corresponding information from the storage unit 12, and returns the information to the management terminal 6. The boot error processing unit 115 executes error processing when the network boot operation of the client 5 ends abnormally.

  The IPv4-compatible DHCPv4 server 2 corresponding to the first DHCP server of the present invention includes an IPv4 address assignment unit 21 that assigns a 32-bit IPv4 address or the like to the client 5. In addition, the IPv6 compatible DHCPv6 server 4 corresponding to the second DHCP server of the present invention includes an IPv6 address assigning unit 41 that assigns a 128-bit IPv6 address or the like to the client 5. The boot server 3 includes a boot image transfer unit 31 that transfers a network boot image to the client 5. The client 5 includes a network boot execution unit 51 that executes a network boot when the power is turned on.

  In the IPv4 address setting information 121, setting information such as an IPv4 address distributed to the DHCPv4 server 2 is registered. A network boot image distributed to the boot server 3 is registered in the network boot image 122. The network boot image includes a network boot program in which processing for obtaining a startup image is described. In the IPv6 address setting information 123, setting information such as an IPv6 address distributed to the DHCPv6 server 4 is registered. In the client management information 124, information related to the IP address assigned to each client 5 and the progress status of the network boot operation is registered.

  FIG. 2 is a diagram illustrating a configuration example of setting information distributed to the DHCPv4 server 2. 2, (a) is address pool setting information 121A, (b) is reserved address setting information 121B, and (c) is other setting information (extract) 121C. Since the configuration information distributed to the DHCPv6 server 4 has almost the same configuration, detailed description thereof is omitted.

  The address pool setting information 121A specifies a range of continuous IP addresses that can be lent to the individual clients 5 that the DHCPv4 server 2 has received an IP address rent request for. The range of each successive IP address is called an address pool, and each address pool is specified by a set of a start IP address and an end IP address. When there are a plurality of address pools, a number of records equal to the number of address pools are registered.

  The reserved address setting information 121B is for individually reserving IP addresses to be lent to individual clients 5 for which the DHCPv4 server 2 has received an IP address rent request. When an IP address lending request is received from an individual client 5, a MAC (Media Access Control) address that uniquely identifies the client 5 is notified. Therefore, a record that associates each MAC address with a reserved IP address is required. Register in advance.

  The other setting information 121C is an excerpt of various information notified from the DHCPv4 server 2 to each client 5, and includes the lease period, the IP address of the boot server, and the file name of the network boot image. The lease period is a valid period of the IP address lent to each client 5. Each client 5 can continue to use the currently lent IP address by requesting the renting of the IP address before the validity period expires. The IP address of the boot server is the IP address of the boot server 3 that is the download destination of the network boot image. The file name of the network boot image is a path and file name where the image file is stored in the boot server 3.

  FIG. 3 is a diagram illustrating a configuration example of the client management information. As shown in FIG. 3, in the client management information 124, a record including a MAC address, an IPv4 address, an IPv6 address, and a status is registered for each client 5. Here, the MAC address is identification information assigned to uniquely identify the client 5. The IPv4 address is a version 4 (32 bit) IP address assigned to the client 5. The IPv6 address is a version 6 (128 bit) IP address assigned to the client 5. If no IP address is assigned, a null code is stored in both.

  The status indicates which stage of the network boot process the client 5 is in. For example, the stage before acquiring the network boot program after acquiring the IPv4 address is “stage 1”, and the network boot program. “Stage 2” is the stage before acquiring the startup image after acquiring the IP address, “Stage 3” is the stage before acquiring the IPv6 address after acquiring the startup image, and starts the application after acquiring the IPv6 address. The stage before performing is “stage 4”. This status is sequentially updated by the client information management unit 113 as the network boot operation process proceeds.

  FIG. 4 is a sequence diagram illustrating an example of a network boot operation when the setting information management server is applied. Here, the information to be set for the DHCPv4 server 2, the boot server 3, and the DHCPv6 server 4 is designed in advance, and the setting information is input from the management terminal 6, and the setting information registration unit 111 sets the setting information management server. It is assumed that it is registered in one storage unit 12.

  As shown in FIG. 4, first, the setting information registration unit 111 of the setting information management server 1 receives various setting information input from the management terminal 6, and receives the received setting information as IPv4 address setting information 121, a network. Registration is made in each of the boot image 122 and the IPv6 address setting information 123 (step S1). Next, the setting information distribution unit 112 of the setting information management server 1 sequentially distributes the setting information to each server (steps S2 to S4). That is, the setting information distribution unit 112 distributes the IPv4 address setting information 121 to the DHCPv4 server 2, distributes the network boot image 122 to the boot server 3, and distributes the IPv6 address setting information 123 to the DHCPv6 server 4. Each server registers the setting information distributed to itself in a storage unit (not shown).

  After that, when the client 5 is turned on to start network boot (step S5), the network boot execution unit embodied by the network boot activation program stored in the ROM (Read Only Memory) of the communication board of the client 5 51, the connection to the DHCPv4 server 2 is made, and the DHCPv4 server 2 sets the IPv4 address and the like used by the client 5 (step S6).

  FIG. 5 is a detailed sequence diagram for the setting operation of the IPv4 address or the like. As shown in FIG. 5, first, a DHCPv4 Discover message is broadcast from the client 5 (network boot execution unit 51) (step S61). Upon receiving this message, the IPv4 address assigning unit 21 of the DHCPv4 server 2 assigns one IPv4 address candidate to be lent to the client 5, if there is an IPv4 address that can be lent to the client 5, and the IPv4 address candidate and its own A DHCPv4 Offer message including the IPv4 address is broadcast (step S62). Receiving this message, the client 5 transmits a DHCPv4 Request message notifying that it is desired to use the notified IPv4 address candidate to the DHCPv4 server 2 (step S63). Finally, the DHCPv4 server 2 (IPv4 address assignment unit 21) officially assigns the IPv4 address to the client 5, and sends a DHCPv4 Ack message including the lease period, the IP address of the boot server 3, the file name of the network boot image, and the like. It transmits to the said client 5 address (step S64). The client 5 that has received this message sets the IPv4 address to be used by itself, and registers information such as the file name of the notified network boot image in a storage unit (not shown).

  Returning to FIG. 4, the DHCPv4 server 2 that has completed the setting of the IPv4 address or the like in step S <b> 6 next manages the setting completion notification including the MAC address of the client 5 and the IPv4 address assigned to the client 5. It transmits to the server 1 (step S7). Upon receiving this notification, the client information management unit 113 of the setting information management server 1 additionally registers a new record if the record corresponding to the client 5 does not exist in the client management information 124, and the MAC address is registered in the record. , “IPv4 address” and “stage 1” are stored as the status. If a record corresponding to the client 5 exists, the IPv4 address is stored in the record, and the status is updated to “stage 1”.

  Next, the client 5 (network boot execution unit 51) connects to the boot server 3 using the IP address of the boot server 3 notified in step S6, and the boot server 3 should be executed by the client 5 The activation image is transmitted to the client 5 (step S8).

  FIG. 6 is a detailed sequence diagram for the startup image acquisition operation. As shown in FIG. 6, first, the client 5 (network boot execution unit 51) transmits a PXE (Preboot eXecution Environment) start request message for requesting the start of the network boot process to the boot server 3 (step S81). The boot image transfer unit 31 of the boot server 3 that has received this message transmits a response message including the file name of the network boot image stored in its own storage unit to the client 5 (step S82). The client 5 that has received this response message transmits a file transfer request message for requesting file transfer by designating the notified file name to the boot server 3 (step S83). Receiving this message, the boot server 3 reads the network boot image file having the designated file name and transmits the file to the client 5 (step S84).

  Although illustration is omitted, when the transmission of the network boot image is completed, the boot server 3 sends a setting completion notification including the identification information (MAC address or IP address) of the client 5 to the setting information management server. The client information management unit 113 of the setting information management server 1 that has transmitted to 1 and received this notification updates the status of the record corresponding to the client 5 of the client management information 124 to “stage 2”.

  Subsequently, the client 5 stores the received network boot image data in its main memory to generate an execution environment of the network boot program included in the image, and then starts the network boot image (step S85). In the network boot program executed thereby, a process for acquiring a boot image to be executed by the client 5 is described. Here, the boot image is described as being registered in the boot server 3. However, the startup image may be registered in another file server or the like.

  When the client 5 executes the network boot program, the client 5 sends a boot image transfer request message for designating a file name of the boot image and requesting transfer of the boot image to the boot server 3. (Step S86). Receiving this message, the boot server 3 reads the boot image file having the designated file name and transmits the file to the client 5 (step S87).

  Returning to FIG. 4, the boot server 3 that has completed transmission of the startup image in step S <b> 8 transmits a setting completion notification including the identification information (MAC address or IP address) of the client 5 to the setting information management server 1. (Step S9). Upon receiving this notification, the client information management unit 113 of the setting information management server 1 updates the status of the record corresponding to the client 5 in the client management information 124 to “stage 3”.

  Subsequently, the client 5 stores the received startup image data in its own main memory to generate the operating environment of the OS and application to be started, and then executes the startup image (step S10). At this time, since the process for acquiring the IPv6 address is described in the startup image, the connection from the client 5 to the DHCPv6 server 4 is performed, and the DHCPv6 server 4 uses the IPv6 used by the client 5. An address and the like are set (step S11).

  FIG. 7 is a detailed sequence diagram for the setting operation of the IPv6 address or the like. As shown in FIG. 7, first, a DHCPv6 Solicit message is broadcast from the client 5 (network boot execution unit 51) (step S111). Upon receiving this message, the IPv6 address assigning unit 41 of the DHCPv6 server 4 assigns one IPv6 address candidate to be lent to the client 5, if there is an IPv6 address that can be lent to the client 5, and the IPv6 address candidate and itself A DHCPv6 Advertise message including the IPv6 address of the user is broadcast (step S112). Receiving this message, the client 5 transmits a DHCPv6 Request message notifying that it is desired to use the notified IPv6 address candidate to the DHCPv6 server 4 (step S113). Finally, the DHCPv6 server 4 (IPv6 address allocation unit 41) officially allocates the IPv6 address to the client 5 and transmits a DHCPv6 Reply message including a lease period to the client 5 (step S114). The client 5 that has received this message sets the IPv6 address to be used by itself, and registers the notified various information in a storage unit (not shown).

  Returning to FIG. 4, the DHCPv6 server 4 that has completed the setting of the IPv6 address and the like in step S11 transmits a setting completion notification including the identification information (MAC address) of the client 5 to the setting information management server 1 (step) S12). Upon receiving this notification, the client information management unit 113 of the setting information management server 1 stores the IPv6 address in the IPv6 address of the record corresponding to the client 5 of the client management information 124 and updates the status to “stage 4”. .

  By performing the above-described operations, various setting information is requested from the management terminal 6 to the request information response unit 114 of the setting information management server 1 so that various setting confirmations can be integrated from a single operating environment. This can be done (step S13).

  FIG. 8 is a sequence diagram illustrating an operation example when a network boot error occurs when the setting information management server is applied. As in the example of FIG. 8, it is assumed that after the client 5 acquires the IPv4 address and the like from the DHCPv4 server 2 in step S6, a hardware failure or the like occurs in the middle of step S8.

  In this case, an error notification is transmitted to the setting information management server 1 from the boot server 3 that detected the abnormality in step S14. Accordingly, the boot error processing unit 115 of the setting information management server 1 that has received this notification transmits to the DHCPv4 server 2 an IPv4 address release command instructing release of the IPv4 address assigned to the client 5 (step S15). The DHCPv4 server 2 that has received this command releases the IPv4 address assigned to the client 5 so that it can be reused (step S17). As a result, the management terminal 6 that has received the error notification from the setting information management server 1 in step S16 instructs the release of the IPv4 address in accordance with an instruction from the maintainer, which was conventionally necessary (step in FIG. 10). There is no need to execute S31).

  As described above, according to the present embodiment, the setting information management server 1 monitors the progress of the network boot operation executed by each client 5, so that the necessary recovery processing is performed when an error occurs in the middle. Can be executed automatically. Therefore, even when an error occurs during the network boot operation, the system can be automatically restored.

  As described above, according to the present embodiment, the setting information of each of these servers is stored centrally by the setting information management server 1 while the processing loads of the DHCPv4 server 2, the boot server 3, and the DHCPv6 server 4 are distributed. By managing, complicated processing of the management terminal 6 based on an instruction from a maintenance person, which was necessary in the past, can be eliminated.

  Although the description of the embodiment of the present invention has been completed above, the embodiment of the present invention is not limited to this, and various modifications can be made without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 100 Network boot system 1 Setting information management server 11 Control part 111 Setting information registration part 112 Setting information delivery part 113 Client information management part 114 Request information response part 115 Boot error processing part 12 Storage part 121 IPv4 address setting information 121A Address pool setting information 121B Reserved address setting information 121C Other setting information 122 Network boot image 123 IPv6 address setting information 124 Client management information 2 DHCPv4 server (first DHCP server)
21 IPv4 address allocation unit 3 Boot server 31 Boot image transfer unit 4 DHCPv6 server (second DHCP server)
41 IPv6 address allocation unit 5 Client 6 Management terminal

Claims (4)

A network boot system that provides a boot image including processing for acquiring an IPv6 address to one or more network bootable clients connected to an IP network,
A boot server that provides the client with a network boot image including a process of acquiring the startup image;
A first DHCP server for giving an IPv4 address to the client and notifying an IP address of the boot server;
A second DHCP server for assigning an IPv6 address to the client;
A setting information management server that is communicably connected to each of the servers;
With
The setting information management server receives registration of setting information necessary for a service provided by each of the boot server, the first DHCP server, and the second DHCP server, and sends the setting information to each of these servers. Deliver,
When the client network boots,
Based on a request from the client, the first DHCP server gives an IPv4 address to the client and notifies the IP address of the boot server;
The boot server sends the network boot image to the client based on a request from the client,
The second DHCP server gives the client an IPv6 address that requests acquisition when the client executes the boot image acquired by executing the network boot image,
The setting information management server further includes:
Collecting service result information provided to each client as the client performs a network boot from each server, and collectively storing the status of the network boot operation of each client system. The network boot system according to claim 1,
After the client is given its IPv4 address from the first DHCP server and the network boot operation of the client ends abnormally,
The boot server or the second DHCP server that detects the abnormality notifies the setting information management server of an error, and the setting information management server that has received the notification notifies the first DHCP server of the IPv4. A network boot system, which commands release of an address. A network boot method for a network boot system that provides a boot image including processing for acquiring an IPv6 address to one or more network bootable clients connected to an IP network,
The network boot system is:
A boot server that provides the client with a network boot image including a process of acquiring the startup image;
A first DHCP server for giving an IPv4 address to the client and notifying an IP address of the boot server;
A second DHCP server for assigning an IPv6 address to the client;
A setting information management server that is communicably connected to each of the servers;
With
The setting information management server accepts registration of setting information required for services provided by the boot server, the first DHCP server, and the second DHCP server, and sends the setting information to each of these servers. Delivering, and
When the client network boots,
The first DHCP server grants an IPv4 address to the client based on a request from the client and notifies the IP address of the boot server;
The boot server sending the network boot image to the client based on a request from the client;
The second DHCP server gives the client an IPv6 address that requests acquisition when the client executes the boot image acquired by executing the network boot image;
The setting information management server indicates the progress status of the network boot operation of the client based on the service result information provided to the client, which is notified from each server as the client performs network boot. Storing information; and
A network boot method comprising: The network boot method according to claim 3,
After the client is given its IPv4 address from the first DHCP server and the network boot operation of the client ends abnormally,
The boot server or the second DHCP server that detected the abnormality notifies the setting information management server of an error, and the setting information management server that has received the notification notifies the first DHCP server of the IPv4. The step of commanding the release of the address;
A network boot method, further comprising:

Images