WO2010146705A1 - Système d'informations et procédé de traitement - Google Patents

Système d'informations et procédé de traitement Download PDF

Info

Publication number
WO2010146705A1
WO2010146705A1 PCT/JP2009/061207 JP2009061207W WO2010146705A1 WO 2010146705 A1 WO2010146705 A1 WO 2010146705A1 JP 2009061207 W JP2009061207 W JP 2009061207W WO 2010146705 A1 WO2010146705 A1 WO 2010146705A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
storage device
interface
identification information
program
Prior art date
Application number
PCT/JP2009/061207
Other languages
English (en)
Japanese (ja)
Inventor
正生 竹内
薫 宮本
Original Assignee
富士通株式会社
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 富士通株式会社 filed Critical 富士通株式会社
Priority to PCT/JP2009/061207 priority Critical patent/WO2010146705A1/fr
Publication of WO2010146705A1 publication Critical patent/WO2010146705A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Definitions

  • the present invention relates to an information processing apparatus.
  • a technique is known in which a part or all of the storage areas of a single or a plurality of physical storage devices are combined and used as a virtual storage device called a single or a plurality of logical units.
  • a virtual storage device (virtual storage device) is different from a physical storage device that physically exists individually, for example, by combining a plurality of physical storage devices and using a part or all of the combined storage areas.
  • the virtual storage device includes one in which a part of the storage area of one physical storage device is provided as one virtual storage device.
  • An example of a system including a virtual storage device is a storage area network (SAN).
  • SAN storage area network
  • a security function is provided for data protection of a virtual storage device in which an operating system (OS) is installed.
  • OS operating system
  • a computer that uses a virtual storage device in a SAN environment is referred to as a management target server.
  • the security function in the SAN environment the identification information of the managed server that can access each virtual storage apparatus is registered in the SAN environment.
  • the security function of the SAN environment is executed using WWN (World Wide Name) which is unique identification information assigned to the Fiber Channel port mounted on each managed server. That is, the control unit that controls the SAN environment associates the logical unit in which the operating system is installed with the identification information of the management target server, for example, the WWN assigned to the Fiber Channel port. Then, the control unit that controls the SAN environment permits access to the logical unit from the Fiber Channel port having the WWN associated with one logical unit.
  • WWN World Wide Name
  • the setting for the security function is executed by the managed server performing a network boot from the management server that manages the computer system.
  • JP 2008-112303 A JP2008-112433 JP2007-94611
  • a computer system including a virtual storage device such as a conventional SAN environment is premised on the existence of a management server that manages the computer system. That is, the managed server in the computer system is activated by network boot from the management server. Then, by network boot, the managed server sets the identification information held in the management server to an interface such as a Fiber Channel port. Next, the managed server makes a boot request for the OS of the managed server itself to the virtual storage apparatus using the identification information set in the interface by network boot. Then, access to the virtual storage apparatus from the interface in which the identification information is set by network boot is permitted, and the OS of the management target server is started from the virtual storage apparatus.
  • the management target server There was a problem that the device itself could not be started separately from the connected network.
  • one aspect of the present technology provides a network boot from a management server connected via a network in a computer system including a storage device that allows a computer to access from an interface capable of setting or changing computer identification information.
  • the startup of the computer is realized without depending on.
  • One aspect of the present technology can be exemplified as an information system including at least one information processing apparatus and a first storage device connectable to the information processing apparatus.
  • the information processing apparatus includes a first interface to which the first storage device can be connected, identification information can be set, a second interface that can be connected to the second storage device using the identification information, and a control unit.
  • the first storage device stores a first program that controls setting of identification information in the second interface and starting of the second program from the second storage device connected to the second interface.
  • the control unit has a first activation unit that accepts an activation instruction and activates the first program from the first storage device, and the first program sets the control unit to set identification information in the second interface. And a recognition processing unit for causing the second storage device to recognize the identification information set in the second interface, access the second storage device by the recognized identification information, and start the second program from the second storage device To function as a second activation unit.
  • the computer can be started without depending on a network boot from a management server connected via a network. Is realized.
  • FIG. 10 is a diagram illustrating an information system according to a second embodiment.
  • FIG. 1 and FIG. 2 describe a comparative example of a computer system including a SAN environment.
  • FIG. 1 is a diagram illustrating a system configuration of a computer system 200 according to a comparative example.
  • the computer system 200 of FIG. 1 is activated by network boot.
  • the computer system 200 includes a managed server 1, a management server 4, and a SAN 2.
  • the managed server 1 has a network interface card (NIC) 13, and the management server 4 has a NIC 43.
  • the NIC 13 and the NIC 43 are connected by a network switch 3.
  • the NIC 13, the NIC 43, and the like are also called LAN boards, LAN cards, etc., and are interfaces that connect a computer to Ethernet, for example.
  • the network switch 3 is, for example, a hub.
  • a network in which the NIC 13 and the NIC 43 are connected by the network switch 3 is called a management LAN.
  • SAN 2 includes an FC switch 21 and a storage 22.
  • each managed server 1 includes a host bus adapter (HBA) 12.
  • the storage 22 is connected to the HBA 12 of the management target server 1 by the FC switch 21.
  • the SAN 2 identifies access from the management target server 1 by WWN.
  • the WWN includes WWNN (World Wide Node Name) that is identification information of the HBA 12 and WWPN (World Wide Port Name) that is identification information of the port of the HBA 12.
  • the WWN may include one WWNN and a plurality of WWPNs.
  • the HBA 12 may access the storage 22 of the SAN 2 using one of a plurality of ports specified by a plurality of WWPNs. For example, when one port cannot be used due to a failure or the like, the other non-failed port is used among the plurality of ports specified by the plurality of WWPNs.
  • WWN including WWNN and WWPN
  • WWN there are WWN set to be uniquely identifiable in the world at the time of factory shipment, and virtual WWN uniquely identifiable in the SAN environment.
  • the virtual WWN that is, the virtual WWNN and the virtual WWPN can be set by a WWN change program provided by the manufacturer of the HBA 12.
  • FIG. 2 is a flowchart illustrating processing at the time of starting the computer system 200 according to the comparative example.
  • the user of the computer system 200 requests the management server 4 to register virtual WWNNs and virtual WWPNs for the number of ports (P101).
  • the management server 4 holds virtual WWNNs and virtual WWPNs for the number of ports in the management server 4 (P102). Next, the management server 4 turns on the power of the managed server 1 (P103). The managed server 1 makes a network boot request to the management server 4 after the POST (Power On On Self Test) process (P104). The management server 4 returns the virtual WWN and WWN change program set in the managed server 1 (P105). Then, the management target server 1 executes the received WWN change program.
  • POST Power On On Self Test
  • P105 Power On On Self Test
  • the management target server 1 executes the received WWN change program.
  • the process of the managed server 1 that executes the WWN change program will be described as the process of the WWN change program.
  • the WWN change program determines whether the WWN has already been set in the HBA 12 using the virtual WWNN and the virtual WWPN for the number of ports. If the virtual WWNN and the virtual WWPN are not set in the HBA 12, the WWN change program changes the WWN of the HBA 12 (P106). The WWN change program executes a re-recognition command of the HBA 12 in order to make the SAN control unit recognize the changed WWN (P107). Then, the WWN change program starts up the OS existing on the SAN that recognizes the WWN from the HBA 12 in which the WWN recognized in the SAN is set (P108).
  • the management server 4 is used to boot the managed server 1. Therefore, the managed server 1 cannot be booted when the management server 4 is not operating.
  • the managed server 1 is booted randomly after OS maintenance or application installation. Therefore, if the management target server 1 is booted when the management server 4 is stopped, such as when maintenance of the management server 4 is performed, the OS of the management target server 1 cannot be booted, and the business is stopped.
  • the network failure of the management LAN includes a failure of the network switch 3, a failure of the NIC 43 of the management server 4, and a failure of the NIC 13 of the management target server 1.
  • any failure is originally a failure that does not affect the OS of the managed server 1, the OS of the managed server 1 is used when the managed server 1 is booted when these failures occur. The business by the management target server 1 stops.
  • the managed server 1 sets the virtual WWN of the HBA 12 by network boot from the management server 4.
  • a server management unit 5 connected to one or a plurality of management target servers 1 through an input / output interface is introduced.
  • FIG. 3 illustrates a system configuration diagram of the information system 10 according to the first embodiment.
  • the information system 10 according to the first embodiment includes managed servers 1-1 to 1-4, a management server 4, a SAN 2, and server management units 5-1, 5-2.
  • the management target servers 1-1 to 1-4, etc. are collectively referred to, they are simply referred to as the management target server 1.
  • the number of management target servers 1 is not limited to the four shown in FIG.
  • the server management units 5-1, 5-2, etc. are collectively referred to simply as the server management unit 5.
  • the number of server management units 5 is not limited to the two shown in FIG.
  • the managed server 1 has a NIC 13.
  • the management server 4 has a NIC 43.
  • the managed server 1 and the management server 4 are connected by the network switch 3 through the NIC 13 and the NIC 43.
  • the managed server 1 has an HBA 12 and is connected to the SAN environment.
  • the server management unit 5 is connected to the input / output interface of the managed server 1 and is recognized by the managed server 1 as a local storage device.
  • the local storage device refers to a storage device connected to the input / output interface of the management target server 1 instead of connection through a network such as LAN or connection using WWN such as FC.
  • the “storage device connected to the input / output interface of the managed server 1” means an OS called BIOS, boot loader, or IPL (Initial Program Loader) of the managed server 1 before the OS of the managed server 1 is started. It can also be referred to as a storage device that can be accessed from a startup program.
  • the server management unit 5 connected to the input / output interface of the managed server 1 is referred to as a local virtual storage device.
  • the local virtual storage apparatus divides the area in its own apparatus into a plurality of areas, and provides a storage area for each managed server 1 to the plurality of managed servers 1.
  • Each storage area of the local virtual storage device functions as a unique storage device for each of the plurality of managed servers 1.
  • the local virtual storage device has a master boot record (MBR) like other storage devices.
  • the MBR of the local virtual storage device is individually provided for each of the plurality of management target servers 1.
  • the local virtual storage device identifies access from each of the plurality of managed servers 1 and allows access to the MBR of each managed server 1.
  • Each MBR of the local virtual storage device holds a WWN setting program for setting a virtual WWN in the HBA 12 of the managed server 1 and a set virtual WWN value at the time of a boot request from each of the managed servers 1. ing.
  • the management server 4 can write the virtual WWN in advance in the MBR of the server management unit 5 before the managed server 1 is booted.
  • the virtual WWN written in the MBR is set in the management server 4 by the user in advance.
  • the managed server 1 executes the boot from the server management unit 5 instead of the network boot from the management server 4.
  • the server management unit 5 first loads the WWN setting program held in the MBR and the set virtual WWN value into the memory of the managed server 1 to control the CPU of the managed server 1. Move to the WWN setting program. That is, the CPU of the management target server 1 starts the WWN setting program. Then, the CPU of the managed server 1 that executes the WWN setting program sets the virtual WWN loaded from the MBR into the memory of the managed server 1 in the HBA 12 of the managed server 1. Then, the CPU of the managed server 1 that executes the WWN setting program recognizes the virtual WWN newly set in the HBA 12 in the SAN environment, and then starts the OS from the SAN environment.
  • the SAN environment refers to a virtual storage device provided by the SAN 2 and includes, for example, an FC switch controlled by a CPU and a physical storage device connected to the FC switch.
  • the server management unit 5 that functions as a local virtual storage apparatus causes the WWN setting program to be managed by the managed server 1.
  • the CPU starts up.
  • the CPU of the managed server 1 executes the WWN setting program, thereby setting the virtual WWN for the HBA 12, executing the recognition command for causing the SAN environment to recognize the virtual WWN set for the HBA, and the recognized virtual WWN.
  • the OS is booted by access to the SAN environment from the HBA 12 identified by.
  • the SAN 2 has an FC switch 21 and a storage 22.
  • the storage 22 is, for example, a storage device such as one or a plurality of hard disk devices.
  • the SAN 2 can combine storage areas of the plurality of hard disk devices.
  • the SAN 2 can partition the combined area into a plurality of logical units. Even when the storage 22 is a single hard disk device, the SAN 2 can divide the storage area of the single hard disk device into a plurality of logical units.
  • a logical unit is a storage area that can be accessed as a single virtual storage device by combining unit areas called blocks or segments, which are units of storage areas in the hard disk.
  • a logical unit is sometimes called the term “partition” in a computer having an OS.
  • the FC switch 21 has a CPU and a memory.
  • the FC switch 21 has a fiber channel port for connection with the management target server 1.
  • the FC switch 21 has an input / output port for connection to the storage 22.
  • the CPU of the FC switch 21 manages the logical unit obtained by dividing the storage area of the storage 22 in association with the WWN of the HBA 12 of the management target server 1. For example, the CPU of the FC switch 21 receives an access request from the HBA 12 identified by WWN. When the WWN included in the access request from the HBA 12 is registered in association with the logical unit of the storage 22, the access request from the HBA 12 is permitted. Then, in accordance with the access request, data is written to the corresponding logical unit, or data is read from the corresponding logical unit and delivered to the HBA 12. Details of the managed server 1 and the server management unit 5 will be described below with reference to FIGS. 4 and 5.
  • FIG. 4 illustrates a detailed configuration of the management target server 1.
  • the managed server 1 has a CPU 11, a memory 14, a NIC 13, an HBA 12, an input / output interface 17, and a switch 18.
  • the CPU 11 executes the computer program expanded in the memory 14 and provides the function of the management target server 1.
  • a computer program is expanded in the memory 14.
  • the computer program in the memory 14 includes, for example, control programs such as BIOS and OS, and business applications.
  • the memory 14 includes a nonvolatile ROM (Read Only Memory) and a volatile DRAM (Dynamic Random Access Memory).
  • the management server 4 is connected to the NIC 13 through the network switch 3 of FIG.
  • the management server 4 can execute various settings on the management target server 1, for example, the setting of the boot disk BIOS.
  • the managed server 4 can also turn on the managed server 1 by controlling the switch 18. However, when the managed server 1 described in the first embodiment is started, the NIC 13 and the NIC 43 between the managed server 1 and the management server 4 may not be connected.
  • the server management units 5-1, 5-2, etc. are connected to the input / output interface 17.
  • the server management unit 5-1 and the like are collectively referred to as a server management unit 5.
  • the server management unit 5 is connected to the CPU 11 through the input / output interface 17 and behaves as a local virtual storage device.
  • the term “local” is not a connection through an adapter having a WWN set or a connection through a management LAN like the HBA 12, but the server management unit 5 is connected to the input / output interface 17 of the managed server 1. It is.
  • the local virtual storage device may not be a physical hard disk device, and may function as a storage device that receives an access request from the management target server 1, for example.
  • the local virtual storage device can be accessed by a boot program such as a BIOS, a boot loader, or an IPL of the managed server 1 before the OS of the managed server 1 is started. Further, the server management unit 5 may not be provided for one managed server 1, and a plurality of managed servers 1 may share one server management unit 5.
  • a boot program such as a BIOS, a boot loader, or an IPL of the managed server 1 before the OS of the managed server 1 is started.
  • the server management unit 5 may not be provided for one managed server 1, and a plurality of managed servers 1 may share one server management unit 5.
  • the CPU 11 executes the BIOS of the memory 14.
  • the CPU 11 starts processing from the MBR of the server management unit 5-1 set as a startup disk in the BIOS.
  • the boot program will be described using BIOS as an example.
  • the activation program is not limited to the BIOS.
  • FIG. 5 illustrates a detailed configuration of the server management unit 5.
  • the server management unit 5 includes a CPU 51, an input / output interface 57, a NIC 53, a memory 54, and a virtual storage control interface 55.
  • the NIC 53 is connected to the NIC 43 of the management server 4 through the network switch 3.
  • the input / output interface 57 is connected to the input / output interface 17 of the management target server 1.
  • the input / output interface 57 is an interface exemplified by USB, SCSI, IDE, and the like.
  • the CPU 51 executes a computer program developed on the memory 54 so as to be executable, and provides the function of the server management unit 5.
  • the CPU 51 executes a computer program in the memory 54 as the virtual storage control interface 55. Then, the CPU 51 communicates with the management server 4 through the NIC 53 and accepts settings from the management server 4. That is, the server management unit 5 provides a communication function to the management server 4 through the virtual storage control interface 55. That is, the virtual storage control interface 55 functions as a communication device on the network that communicates with the management server 4 through the network switch 3 by the NIC 53.
  • the CPU 51 executes a computer program in the memory 54 as the local virtual storage 56.
  • the CPU 51 receives an input / output request, for example, an activation request from the managed server 1 through the input / output interface 57. That is, the server management unit 5 functions as a virtual storage device that is locally connected to the management target server 1 through the input / output interface 57.
  • the CPU 51 provides the storage area on the memory 54 to the management target server 1 as a storage area of a virtual storage device.
  • the virtual storage device on the memory 54 is referred to as a local virtual storage 56 in the first embodiment.
  • the CPU 51 determines the managed server 1-1 of the input / output request source from the address of the bus connected to the input / output interface 57 , 1-2 are identified. Therefore, the CPU 51 can provide individual storage areas to the plurality of managed servers 1-1 and 1-2.
  • the management target server 1 is connected to the input / output interface 17 and issues an input / output request to the CPU 51 through the bus, and inputs / outputs data from an area of the memory 54 allocated to the own device.
  • An MBR is created in the local virtual storage 56.
  • the MBR of the local virtual storage 56 is an area that is executed first when a boot request is made from the managed server 1 to the local virtual storage 56. Since the storage area of the local virtual storage 56 is individually divided for the plurality of managed servers 1-1 and 1-2, the managed servers 1-1 and 1 are divided into the divided areas. There is a separate MBR for -2.
  • FIG. 6 illustrates the MBR structure for one managed server 1 in the local virtual storage 56.
  • the MBR of the local virtual storage 56 stores a WWN definition database 561 and a WWN change program 562.
  • the CPU 51 of the server management unit 5 identifies the boot request source managed server 1 from the boot request source bus address. Then, the CPU 51 loads the MBR of the local virtual storage 56 corresponding to the identified managed server 1 into the memory 14 of the managed server 1.
  • the MBR to be loaded includes a WWN definition database 561 and a WWN change program 562.
  • the CPU 11 of the managed server 1 transfers control to the WWN change program 562.
  • processing performed by the CPU 11 executing the WWN change program 562 will be described simply as processing of the CPU 11.
  • the CPU 11 of the management target server 1 reads the virtual WWN designated as the HBA 12 of the management target server 1 from the WWN definition database 561 loaded from the MBR, and sets it in the HBA 12 of the own apparatus, that is, the management target server 1.
  • the CPU 11 of the managed server 1 executes a SAN 2 recognition command to cause the SAN switch 2 to recognize the virtual WWN set in the HBA 12.
  • the SAN 2 recognition command is a command that notifies the CPU of the SAN switch 2 of the FC switch 21 that a virtual WWN has been set in the HBA 12 of the managed server 1.
  • the SAN 2 recognition command includes server specifying information for specifying the managed server 1 as a parameter to be notified to the SAN 2 and a virtual WWN set in the HBA 12.
  • the server specifying information for specifying the management target server 1 is, for example, information that the SAN 2 can specify by specifying the management target servers 1-1 and 1-2.
  • association between server specifying information for specifying each managed server 1 and a logical unit number for specifying a logical unit used by each managed server 1 is set in advance by a user operation.
  • the memory of the FC switch 21 is stored.
  • the association between the server specifying information for specifying each managed server 1 and the logical unit number for specifying the logical unit used by each managed server 1 is performed by, for example, a user operation through a management terminal (not shown). . Further, for example, after the managed server 1 connected to the SAN 2 through the HBA 12 performs a predetermined authentication process, the individual managed server 1 is associated with the logical unit used by the individual managed server 1. Also good.
  • the SAN 2 FC switch 21 When receiving the recognition command, the SAN 2 FC switch 21 recognizes the virtual WWN set in the HBA 12 of the management target server 1. Then, the FC switch 21 associates the recognized virtual WWN with the logical unit number of the logical unit corresponding to the management target server 1 and holds it in the memory. Then, the CPU 11 of the managed server 1 requests the SAN 2 to boot the OS of the managed server 1 through the HBA 12 in which the virtual WWN is set and recognized by the SAN 2. Then, the virtual WWN is set, the SAN 2 receives a boot request through the HBA 12 recognized by the SAN 2, and starts the OS on the CPU 11 of the management target server 1.
  • FIG. 7 illustrates the structure of the WWN definition database 561.
  • the WWN definition database 561 is constructed in the MBR of the local virtual storage 56. Each record of the WWN definition database 561 is written into the local virtual storage 56 of the server management unit 5 by the management server 4 in accordance with a user operation.
  • the WWN definition database 561 holds server specifying information for specifying the management target server 1, a virtual WWNN, and one or more virtual WWPNs in association with each other.
  • the server specifying information is, for example, the address or identifier of the managed server 1 on the bus to which the input / output interface 17 of the managed server 1 and the input / output interface of the server management unit 5 are connected.
  • Examples of the bus to which the input / output interface 17 of the managed server 1 and the input / output interface of the server management unit 5 are connected include SCSI, USB, and PCI. Therefore, as server specific information, the address of the management object server 1 in SCSI can be illustrated, for example. Moreover, as server specific information, the identifier of the management object server 1 connected by USB can be illustrated, for example.
  • Fig. 8 illustrates the structure of the local virtual storage definition table.
  • the local virtual storage definition table is a table for designating a plurality of managed servers 1 connected to the server management unit 5 and addresses in the memory 54 of the local virtual storage 56 provided to each managed server 1.
  • the CPU 51 of the server management unit 5 sends data to the storage area specified by the address in the memory 54 defined in the local virtual storage definition table. Input and output.
  • the local virtual storage definition table includes server specifying information for specifying the managed server 1 and an address on the memory 54 for the managed server 1 specified by the server specifying information.
  • the server specifying information for specifying the management target server 1 is, for example, the address or identifier of the management target server 1 on the bus to which the input / output interface 57 and the input / output interface 17 are connected. Therefore, the CPU 51 of the server management unit 5 converts the access from the managed server 1 into the access to the memory 54 by the local virtual storage definition table, and inputs / outputs data between the managed server 1 and the memory 54. To do.
  • FIG. 9 is a flowchart illustrating the processing of the WWN change program 562 executed by the CPU of the server management unit 5.
  • the user requests the management server 4 to register the virtual WWNN set in the HBA 12 and the virtual WWPN for the number of ports (P1).
  • the management server 4 writes the virtual WWNN and the virtual WWPN for the number of ports in the MBR WWN definition database 561 in the local virtual storage 56 through the virtual storage control interface 55 (P2).
  • P1 and P2 may be performed at a different time before the management target server 1 is started. That is, the processing of P1 and P2 may be executed offline regardless of the activation of the management target server 1.
  • the management server 4 connects the local virtual storage 56 to the managed server 1 through the virtual storage control interface 55 (P3).
  • connecting the local virtual storage 56 to the managed server 1 means setting the local virtual storage 56 of the server management unit 5 as a boot storage device in the BIOS of the managed server 1. Therefore, in this information system, before starting the managed server 1, the ROM 14 storing the BIOS of the managed server 1, the memory 14 including the RAM storing the data processed by the BIOS, and the data are stored in the memory 14.
  • the CPU 11 that executes the program to be executed, for example, the BIOS, and the server management unit 5 are energized.
  • connection processing of the local virtual storage 56 indicated by P3 may not be executed as a series of procedures shown in FIG.
  • the local virtual storage 56 that is, the process of connecting the server management unit 5 to the management target server 1 may be executed offline at a separate timing.
  • the connection processing of the server management unit 5 to the management target server 1 may be executed according to the user's manual operation on the BIOS of the management target server 1.
  • the management server 4 turns on the power of the managed server 1 (P4).
  • the managed server 1 starts up the WWN change program 562 recorded in the MBR in the local virtual storage 56 on its own CPU 11 (P5).
  • the BIOS of the managed server 1 selects the local virtual storage 56 of the server management unit 5 as the boot disk and the boot process from the MBR.
  • the WWN change program 562 is started by the CPU 11 by the boot process from the MBR.
  • the CPU 11 of the managed server 1 that executes the activated WWN change program 562 receives the virtual WWNN defined in the MBR in the local virtual storage 56, the virtual WWPN for the number of ports, and the setting value of the virtual WWN of the HBA 12 Compare. Then, the CPU 11 of the managed server 1 determines whether or not a virtual WWN is set for the HBA 12.
  • the virtual WWN is a value set by the user in the WWN definition database 561 through the management server 4.
  • a WWN that can be uniquely identified in the world at the time of factory shipment is set in the HBA 12. Therefore, when the virtual WWN is not set, the WWN value set in the HBA 12 and the WWN value in the WWN definition database 561 do not match.
  • the WWN value set in the HBA 12 does not match the WWN value of the WWN definition database 561.
  • the WWN value set in the HBA 12 matches the WWN value in the WWN definition database 561.
  • the CPU 11 of the managed server 1 sets the WWN in the HBA 12 (P6).
  • the CPU 11 of the managed server 1 executes an HBA re-recognition command to make the SAN 2 recognize the changed WWN (P7).
  • the relationship between the logical unit number and WWN is held in the memory of the FC switch 21.
  • the WWN change program 562 activates the OS existing on the SAN 2 through the HBA 12 (P8). Since the changed virtual WWN has already been recognized by the SAN 2 by the process of P7, the OS startup from the P8 is the same as the normal boot operation.
  • FIG. 10 illustrates the process of setting the virtual WWN in the HBA 12, that is, details of P6 in FIG.
  • the managed server 1 starts the WWN change program 562 from the local virtual storage 56 (P61).
  • the CPU of the managed server 1 that executes the WWN change program 562 reads the virtual WWNN and the virtual WWPN (P62).
  • the CPU of the management target server 1 determines whether or not the virtual WWN, that is, the virtual WWNN and virtual WWP read in P62 are already set in the HBA 12 (P63). If the virtual WWNN and virtual WWP read in P62 are not set in the HBA 12, the CPU of the managed server 1 sets the virtual WWNN and virtual WWPN in the HBA (P64).
  • the SAN 2 manages the managed server 1.
  • the OS can be booted.
  • the local virtual storage 56 can be accessed from the BIOS before the OS of the managed server 1 is started. That is, in the first embodiment, the local virtual storage 56 is provided as a device that can be accessed by the BIOS of the managed server 1 without using identification information on the network, such as a management LAN or FC.
  • the HBA 12 of the managed server 1 in accordance with the WWN definition database 561 with a simple configuration without the management LAN or the management server 4, and to start the OS of the managed server 1 from the SAN 2. it can. That is, even if the management server 4 is booted when the management server 4 is stopped, such as during maintenance of the management server 4, the OS of the management target server 1 can be started to continue the business.
  • the managed server 1 can be booted even when a failure occurs in the network. That is, even if the managed server 1 is booted when the network switch 3 fails, the NIC 43 of the management server 4 fails, or the NIC 13 of the managed server 1 fails, the OS of the managed server 1 is started and the business is started. Can continue.
  • the WWN definition database 561 in the local virtual storage 56 can be virtual WWN according to user operation. Therefore, the user can change the HBA 12 to a desired virtual WWN by setting the virtual WWN in the local virtual storage 56 and starting the managed server 1.
  • the uses of the information system including the server management unit 5 and the management target server 1 according to the first embodiment are listed below as examples.
  • the information system 10 including the managed server 1 and the SAN 2 it is effective when the OS of the managed server 1 is booted by changing the hardware configuration of the managed server 1, updating the computer program, or the like.
  • start the WWN change program from the server management unit 5 set the WWN on the HBA 12, recognize the WWN for the SAN 2, and start the OS of the managed server 1 from the SAN 2.
  • Easy to implement. When replacing the SAN2, when the managed server 1 itself is replaced, it is easy to start the WWN change program from the server management unit 5, the WWN recognition process for the SAN2, and the OS of the managed server 1 from the SAN2.
  • the information system 100 includes an information processing device 101 and a first storage device 105.
  • the information processing apparatus 101 includes a control unit 111, a first interface 117, and a second interface 112.
  • the first storage device 105 is connected to the first interface 117.
  • the management target server 1 of the first embodiment can be exemplified.
  • examples of the control unit 111 include the CPU 11 and the memory 14 of the management target server 1 of the first embodiment.
  • the first interface 117 the input / output interface 17 of the first embodiment can be exemplified. More specifically, the first interface is an interface such as USB, SCSI, or IDE.
  • the second storage device 102 is connected to the second interface. As the second interface 112, the HBA 12 of the first embodiment can be exemplified.
  • the server management unit 5 of the first embodiment can be exemplified.
  • the SAN 2 of the first embodiment can be exemplified.
  • the control unit 111 includes a first activation unit 119. Further, the control unit 111 may be provided with a reception unit 118 that receives an activation instruction for the information processing apparatus 101. As the receiving unit 118, the switch 18 of the management target server 1 of the first embodiment can be exemplified. That is, for example, the receiving unit 118 may detect the pressing of the switch 18 in FIG. The accepting unit 118 may accept an activation instruction by receiving an activation command from the management server 104 via the management LAN.
  • the first activation unit 119 can be exemplified as a CPU that executes an activation program such as a BIOS, a boot loader, or an IPL.
  • the MBR of the first storage device 105 is registered as an access area at the time of activation. Therefore, the first activation unit 119 accesses the first storage device 105 through the first interface, and controls the first program stored in the MBR of the first storage device 105 and the identification information set in the second interface 112. The data is loaded into the memory of the unit 111. Then, the first activation unit 119 activates the first program. As a result of activation by the first activation unit 119, the control unit 111 transfers control to the first program.
  • the control unit 111 that executes the first program operates as a setting unit, and sets identification information loaded from the MBR to the memory in the second interface 112.
  • the identification information set in the second interface 112 is WWN when the second interface 112 is an HBA connected to the FC.
  • the control unit 111 that executes the first program then operates as a recognition processing unit and causes the second storage device 102 to recognize the identification information set in the second interface 112. .
  • the identification information set in the second interface 112 is transmitted to the second storage device 102 by the recognition command together with the specific information for specifying the information processing device 101. Then, the second storage device 102 receives the identification information of the second interface 112 of the information processing device 101 and stores it together with the logical unit number of the logical unit for the information processing device 101.
  • the control unit 111 that executes the first program operates as a second activation unit, and requests the second storage device 102 to activate the second program.
  • the activation request for the second program is transmitted to the second storage device 102 through the second interface 112.
  • the second storage device 102 Upon receiving the activation request for the second program, the second storage device 102 recognizes the activation request from the information processing apparatus 101 from the identification information included in the activation request, and from the logical unit corresponding to the identification information, 2 Start the program.
  • the second program is an OS that controls the information processing apparatus 101.
  • a third interface may be provided in the first storage device 105 so that it can communicate with the management server 104.
  • the management server 4 stores the identification information of the second interface 112 in the identification information storage unit 154A of the first storage device 105 in advance through the third interface. Also good.
  • one first storage device 105 is used for one information processing apparatus 101.
  • an information system including a plurality of information processing apparatuses 101, 101-N and the like and one first storage device 105 may be configured.
  • the identification information set in the second interface 112 of each information processing device can be stored in the first storage device 105 together with the specific information specifying each information processing device. That's fine.
  • the control part 111 which performs a 1st program should just acquire the identification information corresponding to the own apparatus loaded into the memory of the control part 111 with the 1st program from the 1st memory
  • Managed server 2 SAN 3
  • Network switch 4 Management server 5
  • Server management unit 10 100, 200 Information system 11, 51 CPU 12 HBA 13, 43, 53 NIC 14, 54 Memory 18 Switch 55 Local virtual storage control interface 56 Local virtual storage 102
  • Second storage device 105 First storage device 111
  • First activation unit 112 Second interface 117 First interface 561 WWN definition database 562 WWN change program

Abstract

L'invention concerne un système d'informations comprenant : au moins un dispositif de traitement d'informations ayant une première interface, une deuxième interface et une unité de commande; et un premier dispositif de stockage qui peut être connecté au dispositif de traitement d'informations. L'unité de commande a une première unité de démarrage qui démarre un premier programme à partir d'un premier dispositif de stockage à la réception d'une instruction de démarrage. Le premier programme amène l'unité de commande à fonctionner comme : une unité de paramétrage pour paramétrer un identifiant de la deuxième interface; une unité de traitement de reconnaissance pour amener un second dispositif de stockage à reconnaître un identifiant paramétré de la deuxième interface; et une seconde unité de démarrage qui accède au second dispositif de stockage à l'aide de l'identifiant reconnu et démarre le second programme dans le second dispositif de stockage.
PCT/JP2009/061207 2009-06-19 2009-06-19 Système d'informations et procédé de traitement WO2010146705A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/061207 WO2010146705A1 (fr) 2009-06-19 2009-06-19 Système d'informations et procédé de traitement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2009/061207 WO2010146705A1 (fr) 2009-06-19 2009-06-19 Système d'informations et procédé de traitement

Publications (1)

Publication Number Publication Date
WO2010146705A1 true WO2010146705A1 (fr) 2010-12-23

Family

ID=43356043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2009/061207 WO2010146705A1 (fr) 2009-06-19 2009-06-19 Système d'informations et procédé de traitement

Country Status (1)

Country Link
WO (1) WO2010146705A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2645252A1 (fr) * 2012-03-29 2013-10-02 Fujitsu Limited Système de traitement d'informations et procédé de réglage d'adresse virtuelle

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008112303A (ja) * 2006-10-30 2008-05-15 Fujitsu Ltd ストレージ仮想化スイッチ
JP2008305073A (ja) * 2007-06-06 2008-12-18 Hitachi Ltd ファイル共有システム及びファイル共有装置の起動方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008112303A (ja) * 2006-10-30 2008-05-15 Fujitsu Ltd ストレージ仮想化スイッチ
JP2008305073A (ja) * 2007-06-06 2008-12-18 Hitachi Ltd ファイル共有システム及びファイル共有装置の起動方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
TADAAKI FUJIMAKI: "Server Shuyaku no Kadai o Kaiketsu suru Blade Server PRIMERGY BX620 S4 no Shin Gijutsu", FUJITSU, vol. 58, no. 5, 10 September 2007 (2007-09-10), pages 407 - 412 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2645252A1 (fr) * 2012-03-29 2013-10-02 Fujitsu Limited Système de traitement d'informations et procédé de réglage d'adresse virtuelle

Similar Documents

Publication Publication Date Title
US8407514B2 (en) Method of achieving high reliability of network boot computer system
US7657786B2 (en) Storage switch system, storage switch method, management server, management method, and management program
US8015396B2 (en) Method for changing booting configuration and computer system capable of booting OS
US7552209B2 (en) Computer system managing an access to a storage system
JP4681505B2 (ja) 計算機システム、管理計算機及びプログラム配布方法
US8069368B2 (en) Failover method through disk takeover and computer system having failover function
US7321927B2 (en) Controlling method, computer system, and processing program of booting up a computer
US20060155837A1 (en) Diskless computer operation management system
US20040230787A1 (en) Method and apparatus for dynamically modifying a computer system configuration
US20090132683A1 (en) Deployment method and system
JP2009536375A (ja) 拡張可能なインターネットエンジン用のｉＳＣＳＩブートドライブシステムおよび方法
TWI581589B (zh) 網際網路小型電腦系統介面啓動參數部署系統及其方法
JP5149732B2 (ja) 仮想計算機システム
US7082462B1 (en) Method and system of managing an access to a private logical unit of a storage system
WO2010146705A1 (fr) Système d'informations et procédé de traitement
JP4498956B2 (ja) ネットワークブートシステム、単位記憶ユニットのマウント方法およびプログラム
JP5484434B2 (ja) ネットワークブート計算機システム、管理計算機、及び計算機システムの制御方法
US8271772B2 (en) Boot control method of computer system
JP2005322254A (ja) 計算機システム、及び該計算機システムに用いられる計算機並びに記憶装置
JP2007293922A (ja) 計算機システム、及び該計算機システムに用いられる計算機並びに記憶装置
JP2007200356A (ja) 計算機システム、及び該計算機システムに用いられる計算機並びに記憶装置
JP2011018254A (ja) 計算機システム及びそのブート制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09846198

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09846198

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP