JP5104320B2 - Computer system, computer main body, startup method, and initialization program - Google Patents

Description

  The present invention relates to a computer system started from a peripheral device connected to a computer main body, and more particularly to a computer system started from a peripheral device connected to a computer main body by a fiber channel.

  Fiber Channel (hereinafter referred to as FC) is a type of gigabit-class network technology that is used to connect computers and peripheral devices when constructing large-scale storage mainly in storage area networks. It is used as one of data transfer methods. FC can be constructed using not only optical fiber cables but also copper coaxial cables and twisted pair cables.

  The FC has a performance suitable for connecting an external storage device to a computer device such as a server that requires a large-scale storage. Hereinafter, an external storage device connected to a computer device via an FC is referred to as an FC device.

  As a technique regarding a computer system in which peripheral devices are connected by an interface such as FC, there are the following techniques, for example. Patent Document 1 discloses a technique in which a plurality of I / O processes are divided and controlled by priority and non-priority, and non-priority I / O is operated while suppressing the processes. Patent Document 2 discloses a technique in which one of a plurality of channels connected to the same FC device is normally used and the other is a retry channel. Patent Document 3 discloses a technique for facilitating computer settings by storing a WWN (World Wide Name), business identification information, and area identification information in association with each other in a storage system. . Non-Patent Document 1 defines a typical command in FC such as GID_FT described later.

JP 2002-108567 A JP 2005-208971 A JP 2007-164305 A "Fibre Channel-Generic Services-5 (FC-GS-5) Rev8.51" The American National Standard Institute T11 technical committee

  A computer system connected to an FC device may install an operating system (OS) on the FC device and use it as a boot disk. In such a case, the system startup (boot) time required from the initialization of the FC device to the startup of the OS needs to be as short as possible.

  However, if an FC device other than the boot disk is connected to the FC channel to be booted, the OS cannot be started until all of those FC devices are initialized, so it takes time to start the system. Take it. In particular, in a system in which a large number of FC devices are connected, it takes a long time to initialize the FC devices.

  Therefore, in order to omit the time required for the initialization of the FC device, it is usually performed that only the boot disk can be accessed from the FC channel and other FC devices cannot be accessed. Specifically, only the boot disk is directly connected to the FC channel, or the zoning function of the FC switch is used.

  However, if the FC device other than the boot disk is not connected in this way, the transfer speed is high, and a large-scale storage can be easily constructed by connecting a large number of FC devices. I can't.

  In addition, one FC device is often shared by multiple computers, and one computer system often has multiple FC channels, but the boot disk that boots a specific computer can only be referenced from one FC channel. It needs to be possible. If this is not done, problems will arise in terms of the operation of the OS in the computer and the OS license (license). Therefore, the computer system needs to be set so that the boot disk cannot be referred to from other FC channels.

  Patent Documents 1 to 3 and Non-Patent Document 1 described above are configured so that a system can be started at high speed even when an FC device other than a boot disk is connected to an FC channel for booting, and a boot disk from another FC channel. Is not provided. The same applies to the technology combining these documents.

  An object of the present invention is to provide a computer system and a computer main body capable of starting the system at high speed even when an FC device other than the boot disk is connected to the FC channel for booting when the computer system is started using the FC device as a boot disk An FC switch, a startup method, a transmission method, and an initialization program are provided.

  In order to achieve the above object, a computer system according to the present invention includes identification information of the first FC device and the second FC device connected to the computer main body, and an operation system in which the first FC device operates on the computer main body. A first device that is a boot device, including a priority device table that includes a boot identification code indicating that the computer is installed, and a boot device that reads the priority device table when the computer body is booted. And an initialization unit that issues an initialization command to the device and issues an initialization command to the second FC device after the initialization of the first FC device is completed.

  In order to achieve the above object, a computer main body according to the present invention is a computer main body connectable to a first FC device and a second FC device, and the identification information of the first FC device and the second FC device. And a priority device table including a boot identification code indicating that the first FC device is a boot device in which an operation system operating on the computer main body is installed, and the priority device table is read when the computer main body is booted. Referring to the boot identification code, issue an initialization command to the first FC device, which is the boot device, and issue an initialization command to the second FC device after the initialization of the first FC device is completed. And an initialization means.

  In order to achieve the above object, a startup method according to the present invention is a method of starting a computer system in which a first FC device and a second FC device are connected to a computer main body, the first FC device and Priority for storing in the computer main body a priority device table including identification information of the second FC device and a boot identification code indicating that the first FC device is a boot device in which an operation system operating on the computer main body is installed A device table storage step, a boot identification code reference step for reading the priority device table and referring to the boot identification code, and a first initialization step for issuing an initialization command to the first FC device as a boot device; Confirm that the first initialization process is complete. And having a step, and a second initialization step of issuing an initialization command to the second FC devices after completion confirming step.

  In order to achieve the above object, the initialization program according to the present invention provides a first FC device and a second FC device when the first FC device and the second FC device are started up in a computer system connected to the computer main body. An initialization program for initializing the second FC device is installed in the computer main body, the identification information of the first FC device and the second FC device, and the operation system in which the first FC device operates on the computer main body A process of reading a priority device table including a boot identification code indicating that the boot device is being used and referring to the boot identification code, and a first command for issuing an initialization command to the first FC device that is the boot device Initialization process and a confirmation process for confirming that the first initialization process has been completed. When, characterized in that to execute a second initialization process of issuing an initialization command to the second FC devices after confirmation process.

  Since the present invention is configured to read the priority device table as described above, refer to the boot identification code, and first issue an initialization command to the boot device, the initialization of the boot device is completed. Thus, it is possible to initialize other FC devices while continuing the boot operation, and to make it impossible to refer to the boot disk from the FC channel that is not booted. As a result, an excellent computer system, a computer main body, an FC switch, a startup method, a transmission method, and an excellent computer system that can start up the system at high speed even when an FC device other than a boot disk is connected to the FC channel to be booted, and An initialization program can be provided.

[First Embodiment]
FIG. 1 is a block diagram showing a configuration of a computer system 1 according to the first embodiment of the present invention. The computer system 1 includes a computer main body 2, an FC switch 70, and disk devices 80 to 82. The computer main body 2 includes a CPU 10, a main memory 20, a chip set 30, an I / O port 50, and FC cards 60 and 61 built in the computer main body 2.

  The CPU 10 is an arithmetic processing unit having a central function of the computer main body 2 and executes an OS, a BIOS, an application program, and the like. The CPU 10 is connected to the chipset 30 via an external bus, and is connected to each device from there to send and receive signals.

  The main memory 20 is a RAM that is also connected to the chip set 30 and is used as a reading area for programs executed by the CPU 10 and a work area for writing processing data.

  The I / O port 50 has a plurality of slots 51 to 54, and can connect various peripheral devices. Note that the number of slots is not limited to four. The CPU 10 and the main memory 20 can access peripheral devices connected to the slots 51 to 54 via the chipset 30.

  Now, an FC card 60 that is an interface for connecting an FC device is connected to the slot 51. Similarly, the FC card 61 is also connected to the slot 53. The selection of the slot used for connection is not limited to this form, and the slots 52 and 54 that are vacant in FIG. 1 may be used. The FC cards 60 and 61 are connected to the FC switch 70 and are formed as different FC channels. Hereinafter, the FC channel of the FC card 60 is referred to as a first FC channel, and the FC channel of the FC card 61 is referred to as a second FC channel.

  An FC channel that is set so that the computer main body 2 can be booted is called a boot channel. The first FC channel is a boot channel, and the second FC channel is not a boot channel. A method for setting a specific FC channel as a boot channel will be described later.

  The FC switch 70 has a local memory area 71, and a boot disk table 110 described later is stored in the local memory area 71.

  To the FC switch 70, disk devices 80 to 82 which are FC devices are connected. The FC switch 70 can access any of the disk devices 80 to 82 from either of the FC cards 60 and 61. In the disk device 80, an OS main body operating on the computer main body 2 is installed. Hereinafter, the disk device in which the main body of the OS is installed is referred to as a boot disk. The disk device 80 is a boot disk, and the disk devices 81 and 82 are not boot disks.

  The chipset 30 has a service processor 40 (hereinafter referred to as SP40). The SP 40 is an embedded system that controls the computer system 1 and can control booting and diagnosis of the computer system 1 from the outside via the SP 40. The storage area of the SP 40 stores a BIOS 41, a boot program 42, a priority device table 100 described later, and the like.

  When the computer system 1 is booted, the FC driver 22 which is a device driver corresponding to the FC card 60 is secured on the main memory 20 after first performing a self test by the BIOS 41 under the control of the SP 40. 22b. The FC driver 23 corresponding to the FC card 61 is also loaded in a different area from the FC driver 22 on the main memory 20.

  Under the control of the SP 40, the boot program 42 is loaded into the OS area on the main memory 20, and the boot program 42 instructs the initialization of the FC channel to which the boot disk is connected. The main body of the OS 21 is loaded from the boot disk connected to the FC channel into the OS area, and the operation of the OS 21 is thereby started.

  In addition, the BIOS 41 and the boot program 42 are set in advance to set the first FC channel as the boot channel. There is no such setting for the second FC channel. Note that the method of setting a specific FC channel as a boot channel is not limited to this, and various methods can be adopted depending on the configuration of the computer system.

  In the FC driver 22 area, the priority device table 100 is also read from the SP 40 and stored in the FC driver area 22 b together with the FC driver 22. Since the first FC channel is a boot channel, the priority device table 100 is read, but the FC driver 23 does not read the priority device table 100 in the second FC channel that is not the boot channel.

  Incidentally, FIG. 1 merely shows a simplified configuration and connection relationship of main hardware in order to explain the present embodiment. Many other devices are used to configure the computer system 1, but these are well known to those skilled in the art and will not be described in detail. Further, a person skilled in the art arbitrarily selects a plurality of blocks described in FIG. 1 as one device or circuit, or conversely, a single block is divided into a plurality of devices or circuits. To the extent possible, it is included in the scope of the present invention.

  FIG. 2 is a conceptual diagram showing the configuration of the priority device table 100 stored in the SP 40 shown in FIG. The priority device table 100 includes a DID (Device ID) number 101 that is an FC device identification number and a boot identification code 102 corresponding to each DID number 101.

  If the boot identification code 102 is “1 (000001b)”, the device is set as a boot disk. If the boot identification code 102 is “0 (000000b)”, the device is not a boot disk. Instead of the DID number 101, a WWN (World Wide Name) for identifying the FC device may be used.

  In the example shown in FIG. 1, only the disk device 80 is set as the boot disk, and the disk devices 81 and 82 are not boot disks. However, the disk devices 81 and 82 are set as priority initialization devices described later by being placed in the priority device table 100.

  In the initialization process of the FC channel, the normal boot program issues a GID_FT command to the FC switch 70 to obtain a list of accessible DID numbers 101 of FC devices, and for all the obtained FC devices with the DID number 101 Initialize the FC devices by executing initialization commands such as PLOGI command and PRLI command all at once. Other responses cannot be performed until responses are returned from all FC devices that have issued commands. Therefore, an I / O command issued to the boot disk cannot be executed.

  In the present embodiment, the FC driver 22 reads the priority device table 100 and issues a GID_FT command to the FC switch 70 to acquire a list of accessible FC devices. It is confirmed whether or not the DID number 101 whose boot identification code 102 is “1” (which is a boot disk) exists in the list of accessible FC devices acquired from the FC switch 70. If it exists, an I / O command is issued only to the boot disk, and initialization processing of only the boot disk is performed first.

  The initialization process for other FC devices that are not boot disks is performed after the initialization process for only the boot disk is completed and the FC driver 22 is notified of this. Accordingly, the execution of the I / O command for the boot disk associated with the startup of the OS has priority over the FC device other than the boot disk, and the initial process for the FC device other than the boot disk is performed at the timing when the I / O command is not issued. Processing is performed.

  In this embodiment, the initialization command is not issued to all the DID numbers 101 at once, but the initialization commands are issued one by one from the top of the list of DID numbers 101 obtained by the GID_FT command. Before issuing the initialization command, it is checked whether an I / O command for the boot disk has been issued. If there is an I / O command, the I / O command is executed. Issue one initialization command at a time. As a result, it is possible to initialize other FC devices while giving priority to the I / O command for the boot disk, so that startup of the OS is not delayed.

  FIG. 3 is a conceptual diagram showing processing for registering the boot identification code 112 in the FC switch 70 shown in FIG. Here, the computer system 1 is booted from the disk device 80 by the first FC channel (FC card 60). In the present embodiment, the zoning function of the FC switch 70 is not used so that the FC device to be booted can be connected to an FC device in another FC channel.

  However, it is necessary to protect the boot disk so that it cannot be accessed from an FC channel other than the FC channel to be booted. In the example of FIG. 3, the disk device 80 that is a boot disk can be accessed only from the first FC channel (FC card 60) that is the boot channel, and the second FC channel (FC card 61) that is not the boot channel. Must be inaccessible. The disk devices 81 and 82 that are not boot disks need to be accessible from both the first and second FC channels.

  Specifically, initialization for the boot disk is performed by issuing a dedicated command in which the boot identification code 102 is added to the PLOGI command described above. This dedicated command is called Boot-PLOGI command. The FC switch 70 recognizes that it is a Boot-PLOGI command if the boot identification code 102 is added to the PLOGI command, and stores the DID of the boot disk in the boot disk table 110 provided in the local memory area 71 in the FC switch 70. Register with number 101.

  Similarly to the priority device table 100, the boot disk table 110 has a DID number 111 and a boot identification code 112. The FC driver 22 can obtain a currently accessible FC device list 113 by issuing a command to the FC switch 70. The DID number 111 and the boot identification code 112 of the FC device registered in the boot disk table 110 are included in the FC device list 113 and returned to the FC driver 22.

  In the FC switch 70, when a list of FC devices that can be accessed by a GID_FT command or the like is requested from the connected FC channel, a boot is performed using the reserved area in the reply data 180 in the FC device list 113 to be transmitted. Control to transmit the identification code.

  FIG. 4 is a conceptual diagram showing a format of reply data 180 that the FC switch 70 shown in FIG. 3 transmits to the FC channel in response to the GID_FT command (Accept). One entry of this data consists of a total of 4 bytes, 1 byte for the control 181 and 3 bytes for the port identifier 182. When the DID number 111 is set in the port identifier 182 and the first bit of the control 181 is 1, it indicates that the entry is the last entry. At this time, 7 bits other than 1 of the first bit of the control 181 are not used and are reserved areas (represented by r). The boot identification code 112 can be set in 7 bits of this reserved area.

  When the boot channel reads the boot identification code 102 from the priority device table 100, the boot channel holds the value of the boot identification code 102 as the FC channel boot identification code 22c. The boot identification code 22c of the FC channel that is not the boot channel is “0”. Therefore, when the boot disk table 110 is read from the FC switch 70 using a command, the boot identification code 22c of the FC channel that is not the boot channel does not match the boot identification code 112 of the boot disk table 110.

  If the boot identification code 22c and the boot identification code 112 do not match, it means that the FC device has already been used as a boot disk by another FC channel or computer. For this reason, the FC switch 70 performs control so as not to access FC devices whose boot identification codes 22c and 112 do not match. In this way, the boot disk can be accessed only from the boot channel.

  FIG. 5 is a flowchart showing processing performed by the FC switch 70 shown in FIGS. 3 and 4 in response to a command from the FC driver 22. When the process is started (step S500), the FC switch 70 waits for reception of a command from the FC driver 22 (step S501). When the command is received, it is determined whether the command is a Boot-PLOGI command or a GID_FT command (steps S502 and S504).

  If the command is a Boot-PLOGI command, the boot identification code 102 is registered in the boot disk table 110 together with the DID number 101 (step S503), and the process returns to step S501. If it is a GID_FT command, the DID number 111 and the boot identification code 112 of the boot disk table 110 are included in the FC device list 113 and returned to the FC driver 22 (step S504), and the process returns to step S501. If it is another command, normal processing corresponding to the command is performed (not shown here), and the process returns to step S501.

  Note that the operation content of each step according to the flowchart of FIG. 5 can be configured to be executed as a program (firmware or the like) that operates on a computer provided in advance in the FC switch 70.

  6 is an image diagram showing an execution image of processing for initializing only the boot disk and processing for initializing other FC devices during execution of an I / O command to the boot disk in the computer system 1 shown in FIG. It is. First, a boot program for reading the OS body from the disk device 80 as a boot disk is loaded from the SP 40 into the OS 21 area of the main memory 20. The boot program instructs the start of initialization processing of the FC channel that controls the FC card 60 connected to the slot 51 (arrow (A)).

  Since the FC driver 22 initializes the boot channel, the priority device table 100 stored in the area of the FC driver 22 is read in response to the instruction to start the initialization process (arrow (B)), and the boot disk is read from there. The boot identification code 102 is taken out and stored as the boot identification code 22c of the FC driver 22 in the FC driver area 22b. Then, a GID_FT command is issued to the FC switch 70 to check whether there is an FC device with the DID number 101 in the priority device table 100.

  If the FC device indicated by the DID number 101 in the priority device table 100 exists in the accessible FC device list received from the FC switch 70, the boot program sends a Boot-PLOGI command to the FC switch 70 ( Arrow (C)). The FC switch 70 recognizes the Boot-PLOGI command and stores the boot identification code 112 and the corresponding DID number 111 in the boot disk table 110 shown in FIG.

  When the initialization of the disk device 80, which is a boot disk, is completed, the completion of initialization is reported from the disk device 80 to the boot program via the FC driver 22 (arrow (D)). As a result, the initialization of the boot disk is completed, and the boot program issues an I / O command for reading the OS body from the disk device 80 (arrow (F)).

  On the other hand, the FC driver 22 that has received the initialization of the boot disk initializes FC devices other than the boot disk (arrow (E)). The initialization process of the FC devices other than the boot disk creates an FC device list excluding the boot disk as shown in FIG. 2B from the FC device list received from the FC switch 70, and the first DID thereof. Initialization is performed in order from the number 101. At that time, before executing the initialization process, it is confirmed whether the I / O command for the boot disk indicated by the arrow (F) is issued. If it is issued, the process of the I / O command is given priority. Control is performed (arrow (G)).

  When initialization of the FC devices other than the boot disk is completed, the OS that has been booted up and booted is notified that the FC device connection configuration has been changed (arrow (H)).

  7 to 8 are flowcharts showing processing by the FC drivers 22 to 23 related to initialization of the FC cards 60 to 61 of the present embodiment shown in FIG. The FC card 60 is a boot channel, and the FC card 61 is not a boot channel. However, the FC drivers 22 and 23 corresponding to the respective FC cards are the same computer program, and it is determined whether or not the FC channel initialized by itself is a boot channel. The operation corresponding to each case is performed. Accordingly, in the following description, it is assumed that the FC driver 22 is the main operation, but it should be understood that the FC driver 23 can also perform the same operation.

  When the process of the FC driver 22 is started (step S200), it is determined whether or not the current process is the boot channel initialization process by the boot program by determining the initial setting in the boot program 42 (step S201). ).

  If the FC channel is to be booted, the priority device table 100 is acquired from the SP 40, the boot identification code 102 and the DID number 101 of the boot disk are extracted and used as the boot identification code 22c in the FC driver area 22b (step S202). ), The process proceeds to step S204. If it is not an initialization process for the FC channel to be booted, the boot identification code 22c = 0 is set (step S203), and the process proceeds to step S204.

  The FC driver 22 acquires the FC device list 113 from the FC switch 70 (step S204), and determines whether or not the boot identification code 102 included in the priority device table 100 is 0 (step S205). If the boot identification code 102 = 0, the process proceeds to step S206, and if not 0, the process proceeds to step S207. If the boot identification code 102 = 0, it means that no boot disk is specified in the priority device table 100.

  If the boot disk is not designated, the boot identification code 22c = 0 is set at step S206 (step S206). Subsequently, it is determined whether or not a disk is designated as priority initialization in the priority device table 100 (step S208). This means that the FC devices listed in the priority device table 100 other than the boot disk are designated as priority initialization. If there is no specified disk, normal initialization processing of the FC channel is performed (step S209, details are shown in FIG. 9 described later), and the initialization completion is notified to the OS (step S210), and the processing is terminated. (Step S216).

  If there is a disk designated as priority initialization in step S208, it is determined whether the disk is currently connected (step S211). If not connected, the process returns to step S209. If it is connected, the process proceeds to step S212 described later.

  If a boot disk is specified in step S205, the boot identification code 102 specified in the priority device table 100 is set in the boot identification code 22c held by the FC channel (step S207), and the process proceeds to step S212 described later. .

  If there is a boot disk or a disk to be preferentially initialized, initialization processing is performed on the disk (step S212, details are shown in FIG. 9 described later), and the OS is notified of initialization completion (step S213). ). The OS notified of the completion of initialization loads the main body of the OS from the boot disk by the boot program 42 and continues booting. In parallel with this, the FC driver 22 also performs initialization processing for the remaining FC devices (step S214, details are shown in FIG. 10 described later), and notifies the OS of the configuration change of the FC device (step S215). ), And the process ends (step S217).

  FIG. 9 is a flowchart showing the details of the initialization process of the FC device shown as steps S209 and 212 in FIGS. When the process is started (step S300), the FC driver 22 determines whether or not the boot identification code 22c held by the FC channel is 0 (step S301). When this process is called from step S209, since the boot identification code 22c = 0, the process proceeds to step S304 and issues an initialization command to all devices listed in the FC device list 113 acquired in step S204. Then, the process proceeds to step S306.

  If the boot identification code 22c ≠ 0 in step S301, the process proceeds to step S302, and the determination is made based on the boot identification code 112 of the boot disk in the FC device list 113 acquired in step S204. If the boot identification code 112 of the boot disk is 0, or if the boot identification code 112 of the boot disk matches the boot identification code 22c of the FC channel, the process proceeds to step S303, and the boot identification for only the boot disk is performed. The attached initialization command (Boot-PLOGI) is issued and the process proceeds to step S306.

  If it is determined in step S302 that the boot identification code 112 of the boot disk is not 0 and the boot identification code 112 of the boot disk does not match the boot identification code 22c of the FC channel, the process proceeds to step S305 where The initialization command is issued, and the process proceeds to step S306.

  The FC driver 22 that issued the initialization command in step S303 (or 304, 305) waits for a reply from the FC device that issued the initialization command, and determines whether or not there has been a normal reply from all the FC devices ( Step S306). If there is a normal reply from all the FC devices, a reporting FC device list is created for all the FC devices (step S307), and the process ends (step S309). If there is an FC device that has not been normally replied and failed to be initialized, a reporting FC device list is created only for those FC devices that have had a normal reply (step S308), and the process is ended (step S309). The reporting FC device list is used when notifying the OS of the completion of initialization in step S210 or 213.

  FIG. 10 is a flowchart showing details of the initialization processing of the remaining FC devices shown as step S214 in FIG. When the process is started (step S400), the FC driver 22 creates a list of FC devices excluding the boot disk that has already been initialized (step S401), and uses the start address of the area storing the device list as a pointer. Setting is made (step S402).

  Subsequently, it is determined whether or not an I / O command for the boot disk has been issued (step S403). If it has been issued, the I / O command is executed (step S404), and the process returns to step S403. When it is confirmed that the I / O command for the boot disk has not been issued, a normal initialization command is issued to the FC device indicated by the pointer (step S405), and a reply from the FC device is waited for (step S405). S406).

  If there is a normal reply in step S406, the FC device is listed in the reporting FC device list, the pointer is updated to indicate the next FC device (step S407), and the process proceeds to step S409. If there is no normal reply, only the pointer is updated to indicate the next FC device (step S408), and the process proceeds to step S409.

  In step S409, it is determined whether or not initialization of all FC devices has been completed. If not completed, the process returns to step S403, and if completed, the process ends (step S410). The reporting FC device list is used when notifying the OS of the configuration change of the FC device in step S215.

  7 to 10 can be configured to be executed as the FC driver 22 which is a program operating in the computer main body 2, or executed in other programs or forms. You may comprise.

  By adopting the above configuration, only the boot disk is initialized in advance, so even if the configuration has many FC devices connected, the initialization process can be completed at high speed and the system can be started at high speed. Can do. Further, even if the zoning function of the FC switch is not used, access to the boot disk from other than the boot channel can be prevented during the boot process. Of course, after the initialization of the FC device is completed, the FC device other than the boot disk can be accessed from the boot channel. At this time, since priority is given to the I / O processing to the boot disk, processing such as OS startup on the boot disk is not delayed.

[Second Embodiment]
Next, a second embodiment of the present invention will be described. Since the configuration and operation of the system are almost the same as those of the first embodiment shown in FIGS. 1 to 10, they are not shown, and only the differences will be described briefly.

  In the first embodiment, the priority device table 100 shown in FIGS. 1 and 2 is stored in the SP 40, and only the FC driver 22 connected to the boot disk reads it during the initialization process. The FC driver 23 that is not the boot channel does not read the priority device table 100 and sets the boot identification code 22c = 0 in step S203 of FIG.

  On the other hand, in the second embodiment, the FC cards 60 and 61 have the priority device table 100 corresponding to each FC channel. Each priority device table 100 may be stored in the SP 40 or may be stored in each of the FC cards 60 and 61. In the priority device table 100 corresponding to the FC channel that is not the boot channel, the boot identification code 102 = 0 is stored from the beginning. Therefore, steps 201 and 203 in FIG. 7 are omitted.

  Except for the above, the configuration and the content of the processing are the same as those of the first embodiment, and thus description thereof is omitted. However, in the second embodiment, the initialization process can be performed for each FC channel. Therefore, even in a computer system to which a large number of FC channels are connected, FC by initializing all FC devices is performed. This is superior to the first embodiment in that it is not necessary to consider the delay of the channel initialization process.

  Although the present invention has been described with the specific embodiments shown in the drawings, the present invention is not limited to the embodiments shown in the drawings, and is known so far as long as the effects of the present invention are achieved. It goes without saying that any configuration can be adopted.

  It can be applied to all computer systems to which peripheral devices can be connected by Fiber Channel. In particular, it is suitable for a computer system to which a large number of FC devices are connected.

It is a block diagram which shows the structure of the computer system which concerns on the 1st Embodiment of this invention. It is a conceptual diagram which shows the structure of the priority device table memorize | stored in SP shown in FIG. It is a conceptual diagram which shows the process in which a boot identification code is registered into the FC switch shown in FIG. FIG. 4 is a conceptual diagram showing a format of reply data that the FC switch shown in FIG. 3 transmits to the FC channel in response to a GID_FT command (Accept). 5 is a flowchart showing processing performed by the FC switch shown in FIGS. 3 and 4 in response to a command from an FC driver. FIG. 2 is an image diagram showing an execution image of processing for initializing only a boot disk and processing for initializing other FC devices during execution of an I / O command to the boot disk in the computer system shown in FIG. 1. 3 is a flowchart showing processing by an FC driver related to initialization of the FC card of the present embodiment shown in FIG. 1. FIG. 7 is a continuation of FIG. 9 is a flowchart showing details of FC device initialization processing shown as steps S209 and 212 in FIGS. FIG. 9 is a flowchart showing details of initialization processing for the remaining FC devices shown as step S214 in FIG. 8. FIG.

Explanation of symbols

1 Computer System 2 Computer Body 10 CPU
20 Main memory 21 OS
22 FC driver (initialization means, initialization program)
22b FC driver area (boot identification storage area)
22c, 102, 112 Boot identification code 23 FC driver 30 Chipset 40 Service processor (SP)
41 BIOS
42 Boot program 50 I / O port 60 FC card (first FC channel)
61 FC card (second FC channel)
70 FC switch 71 Local memory area (local memory)
80 disk unit (first FC device)
81-82 Disk device (second FC device)
100 Priority device table 101, 111 DID number (FC device identification information)
110 Boot disk table 113 FC device list

Claims (20)

Identification information of the first FC device and the second FC device connected to the computer main body, and a boot identification code indicating that the first FC device is a boot device in which an operation system operating on the computer main body is installed A priority device table including
When booting the computer main body, the priority device table is read, the boot identification code is referred to, an initialization command is issued to the first FC device which is a boot device, and the first FC device is And an initialization unit that issues an initialization command to the second FC device after initialization is completed.   The computer system according to claim 1, wherein the initialization command for the second FC device is issued at a timing when an I / O command for the first FC device is not issued.   3. The computer system according to claim 2, wherein the initialization unit stores the boot identification code of the priority device table in a boot identification storage area in the computer main body. The computer main body is
A first FC channel that is accessible to the first FC device and the second FC device, and boots the computer main body from the first FC device;
A second FC channel accessible to the first FC device and the second FC device;
The initialization means does not refer to the priority device table when initializing the second FC channel, and does not store a boot identification code in the boot identification storage area. Computer system. The computer main body is
A first FC channel that is accessible to the first FC device and the second FC device, and boots the computer main body from the first FC device;
A first priority device table corresponding to the first FC channel and including the boot identification code;
A second FC channel accessible to the first FC device and the second FC device;
The computer system according to claim 3, further comprising a second priority device table corresponding to the second FC channel and not including the boot identification code. The initialization command issued to the first FC device by the initialization means includes boot identification information,
The first FC channel and the second FC channel are connected to the computer main body via an FC switch,
When the FC switch receives an initialization command including the boot identification information, the FC switch has a local memory for storing a boot disk table including identification information of the FC device that is the target of the initialization command and a boot identification code The computer system according to claim 4, wherein the computer system is a computer system. The FC switch receives the FC device list including the boot identification code of the FC device included in the boot disk table when the initialization unit requests an FC device list accessible by the FC switch. Reply to the
The initialization unit corresponding to the second FC channel compares the boot identification code included in the FC device list returned from the FC switch with the boot identification code stored in the boot identification storage area, and differs. 7. The computer system according to claim 6, wherein the operation system is set so as not to access the FC device corresponding to the boot identification code.   8. The computer system according to claim 1, wherein one or both of the first FC device and the second FC device includes a plurality of FC devices. 9.   The priority device table includes at least one or more identification information of a priority initialization FC device that is not the boot device, and the initialization unit prioritizes the priority initialization FC device immediately after initialization of the boot device is completed. 9. The computer system according to claim 1, wherein the computer system is initialized. A computer main body connectable with the first FC device and the second FC device,
Priority including identification information of the first FC device and the second FC device, and a boot identification code indicating that the first FC device is a boot device in which an operation system operating on the computer main body is installed A device table,
When booting the computer main body, the priority device table is read, the boot identification code is referred to, an initialization command is issued to the first FC device which is a boot device, and the first FC device is A computer main body comprising initialization means for issuing an initialization command to the second FC device after initialization is completed.   11. The computer main body according to claim 10, wherein the initialization command for the second FC device is issued at a timing when an I / O command for the first FC device is not issued.   12. The computer main body according to claim 11, wherein the initialization unit has a boot identification storage area for storing the boot identification code of the priority device table. A first FC channel that is accessible to the first FC device and the second FC device, and boots the computer main body from the first FC device;
A second FC channel accessible to the first FC device and the second FC device;
The initialization means does not refer to the priority device table when initializing the second FC channel, and does not store a boot identification code in the boot identification storage area. The computer body. A first FC channel that is accessible to the first FC device and the second FC device, and boots the computer main body from the first FC device;
A first priority device table corresponding to the first FC channel and including the boot identification code;
A second FC channel accessible to the first FC device and the second FC device;
13. The computer main body according to claim 12, further comprising a second priority device table corresponding to the second FC channel and not including the boot identification code. The first FC channel and the second FC channel can be connected to the computer main body via an FC switch,
The computer main body according to any one of claims 13 and 14, wherein the initialization command issued to the first FC device by the initialization means includes boot identification information. .   The initialization means corresponding to the second FC channel compares the boot identification code included in the FC device list acquired from the FC switch with the boot identification code stored in the boot identification storage area, and is different. The computer main body according to claim 15, wherein the operation system is set so as not to access the FC device corresponding to the boot identification code. A method of starting a computer system in which a first FC device and a second FC device are connected to a computer body,
Priority including identification information of the first FC device and the second FC device, and a boot identification code indicating that the first FC device is a boot device in which an operation system operating on the computer main body is installed A priority device table storing step of storing a device table in the computer body;
A boot identification code reference step of reading the priority device table and referring to the boot identification code;
A first initialization step of issuing an initialization command to the first FC device which is a boot device;
A completion confirmation step for confirming that the first initialization step is completed;
And a second initialization step of issuing an initialization command for the second FC device after the completion confirmation step. The second initialization process, and issues an initialization command for the second FC device at a timing that is not issued I / O command for the first FC device, to Claim 17 The startup method described. An initialization program for initializing the first FC device and the second FC device when starting the computer system in which the first FC device and the second FC device are connected to the computer main body. In the computer body,
Priority including identification information of the first FC device and the second FC device, and a boot identification code indicating that the first FC device is a boot device in which an operation system operating on the computer main body is installed Processing for reading the device table and referring to the boot identification code;
A first initialization process for issuing an initialization command to the first FC device which is a boot device;
A confirmation process for confirming that the first initialization step is completed;
An initialization program for executing a second initialization process for issuing an initialization command for the second FC device after the confirmation process. The second initialization, and issues an initialization command for the second FC device at a timing that is not issued I / O command for the first FC device, to Claim 19 The initialization program described.

Images