JP2005149334A - Network boot system, network boot method, and caching device for network boot - Google Patents

Network boot system, network boot method, and caching device for network boot Download PDF

Info

Publication number
JP2005149334A
JP2005149334A JP2003388670A JP2003388670A JP2005149334A JP 2005149334 A JP2005149334 A JP 2005149334A JP 2003388670 A JP2003388670 A JP 2003388670A JP 2003388670 A JP2003388670 A JP 2003388670A JP 2005149334 A JP2005149334 A JP 2005149334A
Authority
JP
Japan
Prior art keywords
storage device
computer
data
cache
operating system
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.)
Granted
Application number
JP2003388670A
Other languages
Japanese (ja)
Other versions
JP4440608B2 (en
Inventor
Hirofumi Inomata
Shinji Kimura
Ikuko Kobayashi
Shin Kobayashi
Takeshi Mie
Shinichi Yoshida
武 三栄
真一 吉田
心 小林
郁子 小林
信二 木村
宏文 猪股
Original Assignee
Hitachi Ltd
Nippon Telegr & Teleph Corp <Ntt>
日本電信電話株式会社
株式会社日立製作所
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd, Nippon Telegr & Teleph Corp <Ntt>, 日本電信電話株式会社, 株式会社日立製作所 filed Critical Hitachi Ltd
Priority to JP2003388670A priority Critical patent/JP4440608B2/en
Publication of JP2005149334A publication Critical patent/JP2005149334A/en
Application granted granted Critical
Publication of JP4440608B2 publication Critical patent/JP4440608B2/en
Application status is Expired - Fee Related legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Abstract

<P>PROBLEM TO BE SOLVED: To provide a network boot system capable of shortening the time required to start a diskless personal computer (PC) having no storage devices. <P>SOLUTION: When data for a transmission request from a diskless PC 1 is a request for reading a prescribed logical block, for example, logical block address 0, a cache device 2 transmits a request for reading logical block address 0 to a storage router 7 and transmits a request for reading preliminarily set OS image-portion data to the storage router 7. The cache device 2 stores a received OS image in an incorporated storage medium in response to receiving a read response of OS image-portion data from the storage router 7 and thereafter transfers pertinent data to the diskless PC 1 from the OS image stored in the device itself without requesting read to a storage device 6, in response to a read request for logical block address 1 and following addresses from the diskless PC 1. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a network boot system, a network boot method, and a network boot cache device that start an personal computer by acquiring an operating system or the like via a network.

2. Description of the Related Art Conventionally, a network boot system that acquires a bootstrap or an operating system (OS) image via a network and starts a personal computer that does not have a storage is known (see, for example, Patent Document 1). In the method described in US Pat. No. 6,057,033, when the bootstrap is loaded on the client computer, it includes a map of the network subnets and their corresponding local file servers from the remote file server. By acquiring a configuration file, using the configuration file, determining a local file server that services the subnet in which the client computer resides, and acquiring an OS image from the local file server, it is efficient. Enables file transfer.
JP 2002-123400 A

  However, the conventional network boot system has a problem that when the network becomes a wide area network, it takes time to acquire a bootstrap and an OS image, and it takes time to start a personal computer.

  The present invention has been made to solve the conventional problems, and provides a network boot system capable of reducing the time for acquiring an OS image and the time for starting a personal computer having no storage. For the purpose.

  A first invention for solving the above problems is a network boot system in which a diskless personal computer not having a storage device acquires a bootstrap and an operating system via a network and starts the diskless personal computer (hereinafter referred to as a diskless PC). A storage device accessible via the network, an authentication server for authenticating a user, managing information on the storage device corresponding to the user, and notifying information on the storage device corresponding to a user who is normally authenticated And mediating communication between the diskless PC and the storage device, temporarily storing data acquired from the storage device, and temporarily requesting data read from the diskless PC. It is characterized in further comprising a cache device for transferring, if in the data that are 憶 without access to the storage device the data to the diskless PC.

  In the present invention, if the data requested to be read is stored in the cache device, the stored data is transferred. Therefore, the number of accesses to the storage device is reduced.

  A second invention for solving the above-mentioned problems is characterized in that, in addition to the configuration of the first invention, the diskless PC acquires an operating system or an operating system and an associated application program from the storage device. To do.

  In the present invention, the operating system is acquired from the storage device corresponding to the user. Therefore, an operating system (including an application program as required) corresponding to the user is acquired.

  According to a third invention for solving the above problem, in addition to the configuration of the first invention or the second invention, the cache device requests the storage device to read a prescribed logical address (for example, logical 0 address). Is received and stored all or part of the operating system (which may include an application program; the same shall apply hereinafter) necessary to start the diskless PC.

  In the present invention, an operating system necessary for starting up the diskless PC is acquired and stored in the cache device in response to a read request for a prescribed logical address to the storage device. Therefore, the operating system of the diskless PC is acquired from the cache device.

  According to a fourth invention for solving the above-mentioned problem, in addition to the configuration of the first invention or the second invention, the authentication server is configured such that when user authentication is normal and a storage device corresponding to the user is found, The cache device is instructed to acquire all or part of the operating system necessary for starting the diskless PC, and the cache device is configured to acquire all of the operating system necessary for starting the diskless PC in accordance with an instruction from the authentication server. Alternatively, a part is acquired and stored.

  In the present invention, the operating system necessary for starting up the diskless PC when the user authentication is normal is acquired and stored in the cache device. Therefore, the operating system of the diskless PC is acquired from the cache device.

  A fifth invention for solving the above-mentioned problem is a network boot method in which a diskless PC not having a storage device acquires a bootstrap and an operating system via a network and starts the diskless PC. The process of transmitting an authentication request to an authentication server having an authentication function, and the authentication server authenticates the user in response to the user authentication request, and stores information on the storage device that stores the operating system corresponding to the user who is authenticated normally. The process of notifying the diskless PC, and the process of the diskless PC sending a read request for a prescribed logical address to the storage apparatus to the cache apparatus that mediates communication between the diskless PC and the storage apparatus. When When the cache device receives a read request for a prescribed logical address to the storage device, all or part of the operating system necessary for starting the diskless PC is acquired from the storage device via the network and stored. And a process in which the cache device transfers data requested to be read from the computer from the data acquired from the storage device and stored in the computer. is there.

  In the present invention, an operating system necessary for starting up the diskless PC is acquired and stored in the cache device in response to a read request for a prescribed logical address to the storage device. Therefore, the operating system of the diskless PC is acquired from the cache device.

  A sixth invention for solving the above-described problem is a network boot method in which a diskless PC that does not have a storage device acquires a bootstrap and an operating system via a network and starts the diskless PC. The process of sending an authentication request to an authentication server having an authentication function, and the authentication server authenticates the user in response to the user authentication request, and the user authentication is normal, and the operating system corresponding to the user is stored. A step of instructing a cache device that mediates communication between the diskless PC and the storage device to acquire all or part of an operating system necessary for starting the diskless PC when a storage device is identified; , A cache device that acquires and stores all or part of an operating system necessary for starting the computer from the storage device via a network according to an instruction from the authentication server, and the cache device includes the storage device And transferring the data requested to be read out from the data acquired and stored in the diskless PC.

  In the present invention, when the user authentication is normal, the operating system necessary for the diskless PC is acquired and stored in the cache device. Therefore, the operating system of the diskless PC is acquired from the cache device.

  According to the present invention, a cache device that temporarily stores data acquired from a storage device is provided, and the cache device is configured to execute a diskless PC operating system or an operating system and an associated application program a small number of times. By obtaining all the data from the storage device in response to a read request, the startup time of the diskless PC can be shortened.

  Even in a system in which only one diskless PC is connected to one cache device, it is possible to shorten the startup time of the diskless PC by prefetching data from the storage device to the cache device. In a system in which a plurality of diskless PCs are connected to a cache device and a plurality of diskless PCs use a common operating system, the amount of data transferred between the cache device and the storage device can be reduced. A big effect is acquired.

  Also, especially when the diskless PC and the storage device are installed at very long distances, the entire data transfer time can be shortened by installing the cache device near the diskless PC. The effect is great.

  A diskless PC can acquire the operating system and associated application programs simply by receiving user authentication from the authentication server, and does not need to be aware of the location of the storage device, and changes the management information of the authentication server. By simply changing the operating system and application program for each user, a flexible network boot system can be constructed.

  Hereinafter, a network boot system according to an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing a network boot system according to an embodiment of the present invention.

  1, the network boot system according to the present embodiment includes diskless PCs 1a, 1b, 1c,... (Hereinafter simply referred to as diskless PC1) which are personal computers (PCs) having no storage device such as a hard disk. , A cache device 2 that communicates with a device connected to the network 8 via the network 8 in response to a request from the diskless PC 1 and temporarily stores data received via the network 8, and an address acquisition request A DHCP (Dynamic Host Configuration Protocol) server 3 that returns an IP address to be assigned in response to the request, a TFTP server 4 that transfers a file using the TFTP (Trivial File Transfer Protocol), and an authentication result in response to the authentication request Authentication server 5 and disk It is connected to a storage device 6 such as a hard disk for storing an image of an operating system (OS) operating on the PC 1 and a disk image of each user to be accommodated, and the storage device 6 via a fiber channel, etc. A request to the storage apparatus 6 transmitted via the network 8 by (Internet Small Computer System Interface) or the like is transmitted to the storage apparatus 6 via the fiber channel, and a response from the storage apparatus 6 is requested via the network 8. A storage router 7 for returning to the original and a network 8 based on IP (Internet Protocol) or the like are provided.

  As described above, the storage router 7 has a function of converting a request or response by iSCSI or the like into a request or response by Fiber Channel or vice versa. On the other hand, some storage devices have a function of directly transmitting and receiving requests and responses by iSCSI and the like. If the storage device is the storage device 6 in FIG. 1, the storage device 6 and the network 8 are directly connected. The network boot system according to the present invention can be configured without using the storage router 7. However, in the following description, the embodiment of the invention will be described by taking the case of using the storage router 7 as an example.

  In the network boot system as shown in FIG. 1, the storage device 6 has a plurality of logical units, and OS images are stored from the addresses of the prescribed logical blocks of each logical unit. In the following description, it is assumed that the OS image is stored from logical block 0, but it does not have to be 0. When there is a read request for the logical block address 0 of the storage device 6 from the diskless PC 1, the cache device 2 determines that it is trying to read the OS image, and all or part of the OS image necessary for startup is stored in the storage device. Copy from 6.

  The operation of the network boot system shown in FIG. 1 will be described below with reference to the sequence diagram shown in FIG. As shown in the sequence diagram of FIG. 2, when the diskless PC 1 is activated by turning on the power or the like, it transmits a DHCP request to the DHCP server 3 via the cache device 2 and acquires an IP address. When receiving the DHCP request, the DHCP server 3 selects an unused IP address from a preset address range, and selects the selected IP address, a preset bootstrap name, the IP address of the TFTP server 4, and the like. The included DHCP response is returned to the requesting diskless PC 1.

  When the diskless PC 1 receives the DHCP response, the diskless PC 1 transmits a TFTP request for requesting transfer of the file of the bootstrap name set in the DHCP response to the TFTP server 4 set in the DHCP response via the cache device 2. When receiving the TFTP request, the TFTP server 4 transfers a file having a set file name (in this case, a bootstrap name).

  The diskless PC 1 stores the data transferred as a response to the TFTP request in a built-in RAM (Random Access Memory), and starts the bootstrap stored in the RAM when the transfer is completed. When the bootstrap is activated, the diskless PC 1 requests the user to input authentication information using the attached display. When a user name and password are input using an attached keyboard or mouse, an authentication request in which the input user name and password are set is transmitted to the authentication server 5 via the cache device 2.

  Upon receiving the authentication request, the authentication server 5 determines whether the user name and password set in the received authentication request match the registered information, and if there is a match, sets it for that user. An authentication response including the IP address of the storage router 7, the port number, the target ID of the storage device 6, and the logical unit number (LUN) information of the storage device 6 is returned.

  Upon receiving the authentication response, the diskless PC 1 sends the storage router 7 set in the authentication response to the storage router 7 IP address, port number, storage device 6 target ID, storage device 6 Based on the LUN information, reading of the OS image is started.

  First, the diskless PC 1 transmits a read request for the logical block address 0 of the LUN in the LUN information set in the authentication response (for example, by iSCSI) to the storage router 7 via the cache device 2. The cache device 2 checks the content of the data indicating the transmission request from the diskless PC 1. If the requested data is a read request for the logical block 0, the cache device 2 requests the storage router 7 to read the logical block 0. And a request to read data for a preset OS image are transmitted to the storage router 7.

  When the storage router 7 receives a read request for logical block 0 from the network 8 side, the storage router 7 transmits a read request for logical block 0 to the storage apparatus 6 via the fiber channel. Thereafter, when a read response of logical block 0 is received from the storage device 6 via the fiber channel, the read response of logical block 0 is transferred to the request source via the network 8. Similarly, when a read request for data for the OS image is received from the network 8 side, a read request for data for the OS image is transmitted to the storage apparatus 6 via the fiber channel, and the OS is transmitted from the storage apparatus 6 via the fiber channel. Receives an image data read response. The received OS image data read response is transferred to the requesting cache device 2 via the network 8.

  When the cache device 2 receives the read response of the logical block address 0 from the storage router 7, the cache device 2 transfers it to the requesting diskless PC 1. Also, when receiving a response for reading the data for the OS image requested by itself, the received OS image is stored in a built-in storage medium (a cache table 270 described later).

  Thereafter, the cache device 2 does not make a request to the storage device 6 in response to a read request from the diskless PC 1 after the logical block address 1, and reads the corresponding data from the OS image stored in the own device. Transfer to diskless PC1.

  As described above, in this embodiment, the cache device 2 monitors the transmission data from the diskless PC 1, and when the transmission data is a read request for the logical block address 0, the OS image is read from the storage device 6 in a batch. Since the data is transferred from the stored OS image in response to the OS image read request from the diskless PC 1, there is no need to read out from the storage device 6 for each logical block, and the OS image transfer is performed. Time can be shortened.

  Further, the authentication server 5 manages the storage device 6 and LUN information corresponding to each user, and the diskless PC 1 acquires and activates the OS image based on this information, so that the OS to be activated can be changed for each user. .

  The configuration and processing contents of the cache device 2 will be described in more detail. FIG. 3 is a block diagram illustrating a configuration example of the cache device 2.

  The cache device 2 includes a transmission / reception unit 20 for communicating with the diskless PC 1, a transmission / reception unit 21 having a communication interface with the network 8, a TCP / IP packet analysis unit 22 for analyzing the received TCP / IP packet, and a TCP / IP packet to be transmitted. TCP / IP packet generator 23 for generating iSCSI data, iSCSI data analyzer 24 for analyzing iSCSI data in TCP / IP packets, iSCSI data generator 25 for generating iSCSI data to be transmitted, temporary storage of received data, and A cache processing execution control unit 26 that processes the reading of the data, a cache data management unit 27 that stores a cache table (described later with reference to FIG. 4) in a built-in storage medium, and data that determines a prefetch target from the storage device 6 are managed. Pre-read target management unit 28 That.

  The iSCSI data analysis unit 24 extracts the IP address, target ID, logical unit number (LUN) information, read address range, and data of the storage router 7 from the received “read request”, and sends it to the cache processing execution control unit 26. Send. The iSCSI data generation unit 25 regenerates a “read response” packet from the IP address, target ID, LUN information, read address range, and data of the storage router 7 and transmits the packet to the TCP / IP packet generation unit 23.

  The prefetch target management unit 28 manages a logical address list that stores data necessary for starting an OS (which may include an application program) for each IP address, target ID, and LUN information of the storage router 7. Yes.

  The cache data management unit 27 stores a cache table 270 shown in FIG. The cache table 270 includes an entry number (No.), an IP address (fixed length) of the storage router 7, a port number (fixed length), a target ID (fixed length), LUN information (fixed length), and a logical address (fixed length). , A table storing cache data composed of data (fixed length) stored in the logical address. The target ID is information for identifying the storage apparatus 6 that stores the operating system of the diskless PC 1 that issued the “read request”. The data stored at each logical address is usually 512 bytes in size.

  For example, when the storage router 7 with the IP address “192.168.1.1”, target ID = 0, LUN = 1, and logical address 0 data (for one block) is read from the storage device 6, the cache process is executed. The control unit 26 controls the entry number. Cache data such as = 1 is stored in the cache table 270. Next, with this as an opportunity, when the data (3 blocks) of the logical address of the same LUN = 100 to 102 is prefetched from the storage device 6, the entry No. The cache data is stored in the cache table 270 as in the case of = 2-4.

  In this state, when there is a “read request” from the diskless PC 1 for the data (2 blocks) of the logical address of the same LUN = 100 to 101, the cache device 2 stores the data “00 00 1F... 5C” from the cache table 270. Is returned to the diskless PC 1 as a “read response”.

  Next, the entry number in the cache table 270 is changed. When there are entries up to = 999, the storage router 7 with the IP address “192.168.128.1”, the data (1 block) of the target ID = 0, LUN = 2, and logical address = 0 are stored in the storage device. 6 is read out, entry no. = 1000 cache data is stored in the cache table 270. Thereafter, the cache data is written and read in the same manner.

  The IP address in the cache table 270 is the IP address of the storage router 7 in this example, but in the case of the storage device 6 that can be directly connected to the network 8 as described above, the storage router 7 must be used. The IP address in the cache table 270 is the IP address of the storage device 6.

  In order for a “read request” issued from the diskless PC 1 to reach the storage router 7 via the network, an IP address and a port number are required. Therefore, the IP address and the port number are stored in the cache table 270, but once reaching the inside of the storage router 7, the combination of the IP address, the port number, and the target ID is expressed as “target name” ( (Text character string) can be identified only. Therefore, cache data can be managed by “target name” instead of the combination of IP address, port number, and target ID.

  FIG. 5 shows an internal processing flow of the cache device 2 of the present embodiment. Each time the cache device 2 receives a “read request” from the diskless PC 1, it executes the processing shown in FIG. 5.

  When the transmission / reception unit 20 of the cache device 2 receives a “read request” TCP / IP packet from the diskless PC 1 (step S10), the TCP / IP packet analysis unit 22 analyzes the TCP / IP packet, and analyzes the analyzed data. The data is sent to the iSCSI data analysis unit 24. The iSCSI data analysis unit 11 reads the logical address range (start address to end address) of the “read request” from the “read request” data (step S11). The actual “read request” data includes the start logical address and the number of read blocks. Therefore, the end address is calculated by the following formula.

End address = start address + number of read blocks−1
The iSCSI data analysis unit 24 notifies the cache processing execution control unit 26 of the analysis result. The cache processing execution control unit 26 checks whether or not there is an entry in the range of the logical address where the “read request” has been made in the cache table 270 (step S12). If there is even one logical address with no entry in the range of logical addresses where there is a “read request”, it is determined here that “no entry”. For example, when the logical address = 5, 6, 7, 10 is in the entry and the logical address = 8, 9 is not in the entry, and there is a “read request” in the range of the logical address = 5-10, Judge that there is no entry.

  In the case of “entry present”, the cache device 2 retrieves data from a corresponding entry (hereinafter simply referred to as a cache) in the cache table 270 without relaying a “read request” from the diskless PC 1, the iSCSI data generation unit 25, TCP / The "read response" is returned to the diskless PC 1 via the IP packet generator 23 and the transmitter / receiver 20 (step S13).

  On the other hand, in the case of “no entry”, the “read request” from the diskless PC 1 is directly relayed to the storage router 7 via the transmission / reception unit 21 and the network 8 (step S14). When the “read response” is received from the storage router 7 (step S15), the cache processing execution control unit 26 records the read data included in the “read response” in the cache (adds an entry to the cache table 270), and The “read response” is relayed to the diskless PC 1 via the transmission / reception unit 20 (step S16). If an entry already exists in the cache table 270 at this time, the “read response” is overwritten and added.

  Next, it is determined whether the head (start address) of the range of the logical address of the “read request” from the diskless PC 1 is address 0 (step S17). If the address is not 0, the process for the read request is terminated.

  When the head is 0 address, the prefetch target logical address list data is acquired from the prefetch target management unit 28 (step S18). The look-ahead target management unit 28 stores in advance list information of logical addresses that may be subsequently requested from the diskless PC 1 in accordance with the size of the operating system and application programs necessary for starting the diskless PC 1.

  Next, it is checked whether or not there is an entry in the cache table 270 for all of the acquired logical addresses (step S19). If there are entries for all, the process is terminated. If there is at least one logical address that does not have an entry, data that already has an entry in the cache table 270 is excluded from the prefetch target, and a “read request” that targets only a logical address that does not have an entry is assigned to the iSCSI. The data is generated by the data generation unit 25 and transmitted to the storage router 7 via the TCP / IP packet generation unit 23 and the transmission / reception unit 21 (step S20). If a “read response” for the “read request” is received from the storage router 7 (step S21), the read data included in the received “read response” is recorded in the cache (an entry is added to the cache table 270). (Step S22), the process ends.

  Next, another embodiment of the present invention will be described with reference to the sequence diagram shown in FIG. This second embodiment differs from the first embodiment described with reference to FIG. 2 in that the OS image “read request” is sent to the storage router 7. In the case of the second embodiment, when an authentication request is sent from the diskless PC 1 to the authentication server 5, if the authentication is normal, the authentication server 5 issues an instruction to read the OS image to the cache device 2, and the cache device 2 sends an OS image “read request” to the storage router 7 before receiving the first “read request” from the diskless PC 1.

  As shown in FIG. 6, when the diskless PC 1 is started by turning on the power, the DHCP request is transmitted to the DHCP server 3 via the cache device 2 to acquire the IP address. When receiving the DHCP request, the DHCP server 3 selects an unused IP address from a preset address range, and selects the selected IP address, a preset bootstrap name, the IP address of the TFTP server 4, and the like. The included DHCP response is returned to the requesting diskless PC 1.

  When the diskless PC 1 receives the DHCP response, the diskless PC 1 transmits a TFTP request for requesting transfer of the file of the bootstrap name set in the DHCP response to the TFTP server 4 set in the DHCP response via the cache device 2. When receiving the TFTP request, the TFTP server 4 transfers a file having a set file name (in this case, a bootstrap name).

  The diskless PC 1 stores the data transferred as a response to the TFTP request in a built-in RAM (Random Access Memory), and starts the bootstrap stored in the RAM when the transfer is completed. When the bootstrap is activated, the diskless PC 1 requests the user to input authentication information using the attached display. When a user name and password are input using an attached keyboard or mouse, an authentication request in which the input user name and password are set is transmitted to the authentication server 5 via the cache device 2. The above processing is the same as that of the first embodiment described in FIG.

  When the authentication server 5 receives the authentication request and the user name and password set in the received authentication request match the registered information, the IP address of the storage router 7 set for the user And an authentication response including the LUN information of the storage device 6, and the OS image data including the IP address of the storage router 7 set for the user in the cache device 2 and the LUN information of the storage device 6. "Read instruction" is transmitted.

  When the cache device 2 receives the “read instruction” for the data for the OS image, the cache device 2 sets the “read instruction” for the data for the OS image to the storage router 7 set to the “read instruction” for the data for the OS image. Based on the set LUN information, a “read request” of data for the OS image is transmitted.

  When the storage router 7 receives the “read request” for the OS image data from the network 8 side, the storage router 7 transmits the “read request” for the OS image data to the storage device 6 via the fiber channel. Thereafter, when a “read response” of the OS image data is received from the storage device 6 via the fiber channel, the “read response” of the OS image data is transferred to the request source via the network 8.

  When the cache device 2 receives the “read response” of the OS image data from the storage router 7, the cache device 2 stores the received OS image in a built-in storage medium. Thereafter, in response to the “read request” from the logical block address 0 from the diskless PC 1, the storage device 6 is not requested, and the corresponding data is transferred from the OS image stored in the own device to the diskless PC 1.

  With this configuration, when the authentication is normal, the authentication server 5 causes the cache device 2 to collectively read and store the OS image from the storage device 6, and the cache device 2 responds to the OS image read request from the diskless PC 1. Thus, since the data is transferred from the stored OS image, it is not necessary to read from the storage device 6 for each logical block, and the OS image transfer time can be shortened.

  An example of the configuration of the cache device 2 in the second embodiment is shown in FIG. The cache device 2 according to the second embodiment is different from the first embodiment described with reference to FIG. 3 in that it includes a read instruction analysis unit 29 that analyzes a “read instruction” from the authentication server 5. . Other parts are almost the same as those of the first embodiment described above.

  When the read instruction analysis unit 29 analyzes the “read instruction” of the data for the OS image received from the authentication server 5, the read instruction analysis unit 29 notifies the cache processing execution control unit 26 of the analysis result. The iSCSI data generation unit 25 generates a “read request” for the data corresponding to the OS image based on the LUN information set in the “read instruction” for the storage router 7 set in the “read instruction”. The “read request” generated by the iSCSI data generation unit 23 is transmitted to the storage router 7 via the TCP / IP packet generation unit 25 and the transmission / reception unit 21.

  8 and 9 show a processing flow of the cache device 2 in the second embodiment. The cache device 2 executes the process shown in FIG. 8 every time it receives a “read instruction” from the authentication server 5 regardless of the reception of the “read request” from the diskless PC 1.

  When the transmission / reception unit 20 of the cache device 2 receives the “read instruction” of the OS image data from the authentication server 5 (step S30), the TCP / IP packet analysis unit 22 and the read instruction analysis unit 29 analyze the contents of the instruction, The cache processing execution control unit 26 is notified of the content of the “read instruction”.

  The cache process execution control unit 26 checks whether or not the cache table 270 has all or some entries of the operating system necessary for starting the diskless PC 1 (step S31). If there are all applicable entries, the process ends. If there is at least one logical address having no entry in the cache table 270 within the range in which the “read instruction” has been issued, it is determined that there is no entry, and the process proceeds to step S32.

  In step S 32, a “read request” for OS image data to the storage router 7 is generated and transmitted to the storage router 7, and all or part of the operating system necessary for starting up the diskless PC 1 is prefetched and acquired. The cache process execution control unit 26 records the prefetched data in the cache (adds an entry to the cache table 270), and ends the process (step S33). At this time, if an entry already exists in the cache table 270, the pre-read data is overwritten and added to the entry.

  When the cache device 2 receives a “read request” from the diskless PC 1, the cache device 2 executes the cache processing shown in FIG. 9.

  When the transmission / reception unit 20 of the cache device 2 receives a “read request” TCP / IP packet from the diskless PC 1 (step S40), the TCP / IP packet analysis unit 22 and the iSCSI data analysis unit 24 analyze the received data. The range of the logical address of “read request” (start address to end address) is read from the data of “read request” (step S41). The analysis result is notified to the cache processing execution control unit 26.

  The cache process execution control unit 26 checks whether or not there is an entry in the range of the logical address where the “read request” has been made in the cache table 270 (step S42). If there is even one logical address that does not have an entry in the range of logical addresses for which there has been a “read request”, it is determined here that there is no entry, and the process proceeds to step S44. In the case of “entry present”, the cache device 2 retrieves data from the cache without relaying the “read request” from the diskless PC 1 to the storage router 7, and the iSCSI data generation unit 25, TCP / IP packet generation unit 23, A “read response” is returned to the diskless PC 1 via the transmission / reception unit 20 (step S43).

  On the other hand, in the case of “no entry”, the “read request” from the diskless PC 1 is directly relayed to the storage router 7 via the transmission / reception unit 21 and the network 8 (step S44). When the “read response” is received from the storage router 7 (step S45), the cache processing execution control unit 26 records the read data included in the “read response” in the cache (adds an entry to the cache table 270), and The “read response” is relayed to the diskless PC 1 via the transmission / reception unit 20, and the process is terminated (step S46).

  In the above embodiment, the data that is finally sent from the storage device 6 to the diskless PC 1 may be only the operating system or may include an application program that operates under the operating system. At this time, the files of the operating system and the application program may be configured as one file or a plurality of files, and the present invention can be implemented in either form.

  In the above embodiment, a storage device having a function (command queuing) for processing a plurality of read requests in parallel can also be used as the storage device 6, and a storage device having such a function. By using, it is possible to further reduce the processing time for a read request for a preset OS image or an accompanying application program as a whole.

It is a block diagram which shows the structural example of a network boot system. It is a sequence diagram for operation | movement description of a network boot system. It is a block diagram which shows the structural example of a cache apparatus. It is a figure which shows the structural example of a cache table. It is a figure which shows the internal processing flow of a cache apparatus. It is a sequence diagram for operation | movement description of the network boot system of other embodiment. It is a block diagram which shows the structural example of the cache apparatus of other embodiment. It is a figure which shows the internal processing flow of the cache apparatus of other embodiment. It is a figure which shows the internal processing flow of the cache apparatus of other embodiment.

Explanation of symbols

1 Discless PC
DESCRIPTION OF SYMBOLS 2 Cache apparatus 3 DHCP server 4 TFTP server 5 Authentication server 6 Storage apparatus 7 Storage router 8 Network 20, 21 Transmission / reception part 22 TCP / IP packet analysis part 23 TCP / IP packet generation part 24 iSCSI data analysis part 25 iSCSI data generation part 26 Cache processing execution control unit 27 Cache data management unit 28 Prefetch target management unit 29 Read instruction analysis unit 270 Cache table

Claims (8)

  1. In a network boot system in which a computer that does not have a storage device that stores an operating system in advance acquires the operating system via a network and starts the computer.
    A storage device storing at least an operating system necessary for starting up the computer, accessible from other devices via the network;
    An authentication server for authenticating a user who uses the computer, managing information on the storage device corresponding to the user, and notifying the computer or another device of information on the storage device corresponding to a user who has been authenticated successfully; ,
    Mediates communication between the computer and the storage device, temporarily stores data acquired from the storage device, and if the data requested to be read from the computer is in the temporarily stored data A network boot system comprising: a cache device that transfers the data to the computer without accessing the storage device.
  2. The network boot system according to claim 1, wherein the computer acquires an operating system or an operating system and an application program stored in the storage device from the cache device.
  3. When the cache device receives a read request for a prescribed logical address to the storage device, the cache device stores all or part of the operating system necessary for starting the computer, or all or part of the application program associated therewith. The network boot system according to claim 1, wherein the network boot system is obtained and stored from a storage device.
  4. When the authentication of the user is normal and the storage device corresponding to the user is found out, the authentication server includes all or a part of the operating system necessary for starting the computer in the cache device, or an application program associated therewith To get all or part of
    The cache device acquires and stores all or part of an operating system necessary for starting the computer, or all or part of an application program associated therewith, from the storage device according to an instruction from the authentication server. The network boot system according to claim 1 or 2.
  5. A computer that does not have a storage device that stores an operating system in advance, a storage device that can be accessed from another device via a network, that stores an operating system necessary for starting up the computer, and a user who uses the computer An authentication server that has an authentication function and manages information of the storage device corresponding to a user, and a cache device that mediates communication between the computer and the storage device and temporarily stores data acquired from the storage device A network boot method for starting the computer in a network boot system comprising:
    A process in which the computer transmits an authentication request of a user who uses the computer to the authentication server;
    The authentication server authenticates a user in response to a user authentication request from the computer, and notifies the computer of information on the storage device corresponding to a user who has been authenticated successfully;
    A process in which the computer transmits a read request for a specified logical address to the storage device to the cache device;
    When the cache device receives a read request for a prescribed logical address to the storage device, all or part of the operating system necessary for starting the computer, or all or part of the application program associated therewith, Acquiring and storing from the storage device via a network;
    A network boot method, comprising: a step of fetching data requested to be read from the computer from the data acquired from the storage device and stored by the cache device and transferring the data to the computer.
  6. A computer that does not have a storage device that stores an operating system in advance, a storage device that can be accessed from another device via a network, that stores an operating system necessary for starting up the computer, and a user who uses the computer An authentication server that has an authentication function and manages information on the storage device corresponding to a user, and a cache device that mediates communication between the computer and the storage device and temporarily stores data acquired from the storage device A network boot method for starting the computer in a network boot system comprising:
    A process in which the computer transmits an authentication request of a user who uses the computer to the authentication server;
    The authentication server authenticates the user in response to the user authentication request from the computer, and when the user authentication is normal and the storage device corresponding to the user is found, the cache device is activated to start the computer. Instructing to obtain all or part of the required operating system, or all or part of the accompanying application program;
    The cache device acquires all or part of the operating system necessary for starting up the computer, or all or part of the application program associated therewith, from the storage device via the network according to an instruction from the authentication server. Memory process,
    A network boot method, comprising: a step of fetching data requested to be read from the computer from the data acquired from the storage device and stored by the cache device and transferring the data to the computer.
  7. In a network boot system comprising a computer that does not have a storage device that stores an operating system in advance, and a storage device that is accessible from another device via a network and stores at least an operating system necessary for starting the computer, A cache device that mediates communication between the computer and the storage device;
    A cache table for temporarily storing data acquired from the storage device in association with information on a logical address where the data is stored in the storage device;
    Means for receiving, from the computer, a read request designating information of the storage device including information on a range of logical addresses where the requested data is stored;
    The received read request is analyzed, and when the start address of the range of logical addresses specified in the read request is a specified logical address, all or part of the operating system necessary for starting the computer, or further to it Means for generating a read request for predetermined prefetched data relating to all or part of the accompanying application program and transmitting the read request to the storage device via a network;
    Means for storing data acquired from the storage device in response to the read request in the cache table;
    A network boot cache device comprising: means for retrieving data requested to be read from the computer from the data acquired from the storage device and stored in the cache table, and transferring the data to the computer .
  8. A computer that does not have a storage device that stores an operating system in advance, a storage device that can be accessed from other devices via a network, and that stores at least the operating system required to start the computer, and a user that has a user authentication function A cache device that mediates communication between the computer and the storage device in a network boot system including an authentication server that manages information on the storage device corresponding to
    A cache table that temporarily stores the data acquired from the storage device in association with the logical address information in which the data is stored in the storage device;
    Means for receiving, from the authentication server, an instruction to read out data relating to all or part of an operating system necessary for starting up the computer, or all or part of an application program associated therewith, to the storage device;
    Analyzing the received read instruction, generating a data read request for all or part of the operating system necessary for starting the computer, or all or part of the application program associated therewith, and transmitting the data via the network Means for transmitting to the storage device;
    Means for storing data acquired from the storage device in response to the read request in the cache table;
    Means for receiving, from the computer, a read request designating information of the storage device including information on a range of logical addresses where the requested data is stored;
    A network boot cache device comprising: means for retrieving data requested to be read from the computer from the data acquired from the storage device and stored in the cache table, and transferring the data to the computer .
JP2003388670A 2003-11-19 2003-11-19 Network boot system, network boot method, and network boot cache device Expired - Fee Related JP4440608B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2003388670A JP4440608B2 (en) 2003-11-19 2003-11-19 Network boot system, network boot method, and network boot cache device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2003388670A JP4440608B2 (en) 2003-11-19 2003-11-19 Network boot system, network boot method, and network boot cache device

Publications (2)

Publication Number Publication Date
JP2005149334A true JP2005149334A (en) 2005-06-09
JP4440608B2 JP4440608B2 (en) 2010-03-24

Family

ID=34695631

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2003388670A Expired - Fee Related JP4440608B2 (en) 2003-11-19 2003-11-19 Network boot system, network boot method, and network boot cache device

Country Status (1)

Country Link
JP (1) JP4440608B2 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009110407A (en) * 2007-10-31 2009-05-21 Toshiba Corp Cache method and cache device
JP2009176213A (en) * 2008-01-28 2009-08-06 Hitachi Software Eng Co Ltd Network boot system
WO2010116473A1 (en) * 2009-03-30 2010-10-14 富士通株式会社 Control server, boot server, network boot system, network boot method, boot image selection program, and boot image provision program
US8433888B2 (en) 2007-11-26 2013-04-30 Co-Conv, Corp. Network boot system
JP5195748B2 (en) * 2007-03-29 2013-05-15 富士通株式会社 Server management program, method, and apparatus
JP2014130476A (en) * 2012-12-28 2014-07-10 Fujitsu Ltd Distribution system, distribution method and program

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5195748B2 (en) * 2007-03-29 2013-05-15 富士通株式会社 Server management program, method, and apparatus
JP2009110407A (en) * 2007-10-31 2009-05-21 Toshiba Corp Cache method and cache device
JP4607937B2 (en) * 2007-10-31 2011-01-05 東芝ソリューション株式会社 Cache method and cache device
US8433888B2 (en) 2007-11-26 2013-04-30 Co-Conv, Corp. Network boot system
JP2009176213A (en) * 2008-01-28 2009-08-06 Hitachi Software Eng Co Ltd Network boot system
WO2010116473A1 (en) * 2009-03-30 2010-10-14 富士通株式会社 Control server, boot server, network boot system, network boot method, boot image selection program, and boot image provision program
US8468226B2 (en) 2009-03-30 2013-06-18 Fujitsu Limited Management server, boot server, network boot system, and network boot method
JP5333579B2 (en) * 2009-03-30 2013-11-06 富士通株式会社 Management server, boot server, network boot system, and network boot method
JP2014130476A (en) * 2012-12-28 2014-07-10 Fujitsu Ltd Distribution system, distribution method and program

Also Published As

Publication number Publication date
JP4440608B2 (en) 2010-03-24

Similar Documents

Publication Publication Date Title
US9047130B2 (en) Method, server and system for converging desktop application and web application
US9467513B2 (en) Method and apparatus for web based storage on-demand
CN100437530C (en) Method and system for providing secure access to private networks with client redirection
US7529810B2 (en) DDNS server, a DDNS client terminal and a DDNS system, and a web server terminal, its network system and an access control method
US9558353B2 (en) Wireless router remote firmware upgrade
US20100235329A1 (en) System and method of embedding second content in first content
US20050060316A1 (en) Extended file system
US8065275B2 (en) Systems and methods for cache optimization
US8086634B2 (en) Method and apparatus for improving file access performance of distributed storage system
EP1546924B1 (en) Method, system, and program for maintaining data in distributed caches
US7225264B2 (en) Systems and methods for delivering content over a computer network
JP5753665B2 (en) Client, mediation server and method for providing cloud storage
JP3967806B2 (en) Computerized method and resource nomination mechanism for nominating a resource location
US20050216668A1 (en) Mode device, administrative server, routing method and authentication method
DE60130633T2 (en) Secure Internet Clipboard
JP2004118824A (en) Storage system for content distribution
US20050240574A1 (en) Pre-fetching resources based on a resource lookup query
JP4242819B2 (en) Computer system having a terminal capable of working offline
JP5646650B2 (en) Real-time validation of web applications
US20020046262A1 (en) Data access system and method with proxy and remote processing
US7194532B2 (en) Distributed file management method and program therefor
US6711619B1 (en) Method, system, and apparatus for distributing and using computer-based applications over a network
DE60313108T2 (en) Method and system for controlling PXE-based boot decisions from a network policy directory
JPWO2003091889A1 (en) Collaboration server, collaboration system, session management method and program thereof
JPWO2005006204A1 (en) Database access control method, database access control device, proxy processing server device, database access control program, and recording medium recording the program

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20060522

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20080731

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20090526

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20090723

RD04 Notification of resignation of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7424

Effective date: 20090723

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20100105

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20100107

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20130115

Year of fee payment: 3

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

S531 Written request for registration of change of domicile

Free format text: JAPANESE INTERMEDIATE CODE: R313531

R350 Written notification of registration of transfer

Free format text: JAPANESE INTERMEDIATE CODE: R350

LAPS Cancellation because of no payment of annual fees