JP2010152704A - System and method for operational management of computer system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To confirm the operation of an OS disk image by a server in advance. <P>SOLUTION: The method for operational management in a management server of a computer system, the computer system comprising a server to be managed and an OS disk image adapted to operate on the server, the management server being used to manage association between the OS disk image and the server to be managed. The operational management method includes: acquiring I/O device recognition information that the OS disk image on a first server to be managed recognizes, acquiring physical device configuration information that indicates an I/O device configuration of a second server to be managed, determining, on the basis of the acquired I/O device recognition information and physical device configuration information, whether the OS disk image operates properly when loaded into the second server and executed. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an operation management system and management method for a computer system composed of a plurality of server computers.

  The present invention relates to operation management of a computer system that is composed of one or more computers (hereinafter referred to as servers) and executes business such as a company.

  With the advancement of computer storage technology and storage data management technology, hardware such as Central Processing Unit (CPU), memory, and IO device, which is the execution subject of calculation in the computer, and Operating System (OS) stored in the storage device ), Software such as business applications (hereinafter referred to as OS disk images. When loaded from the storage device to the main storage device, it is possible to freely change the association with software. Became.

  For example, in Patent Document 1, in a configuration in which a storage area network (SAN) storage device is used, a logical unit (LU) is created on a SAN storage device, an OS is stored in advance in the LU, and the SAN storage device or By limiting the servers that can logically access the LU to specific servers connected to the SAN by the SAN switch control program, the server and the OS can be associated exclusively. As another example, in Patent Document 2, an OS disk image is stored in a management server, and the OS disk image is called a deployment that is associated with a server by copying (restoring) the OS disk image to the main storage device of the server to be executed. There is a way.

  When a failure occurs in the server, the OS disk image of the server in which the failure has occurred is loaded into the spare server and executed, so that operations can be continued quickly or the OS disk image executed by the server can be replaced. By switching the usage according to the time zone, it is possible to easily realize the operation of sharing the hardware of the server in a plurality of operations and reducing the hardware cost, and it has become a noticeable technology.

JP2007-14013 US2005 / 0216911

  The OS controls each I / O device of the server using a unique device driver program (hereinafter, device driver). The device driver is a dedicated program for each I / O device such as a network interface card (NIC) or a host bus adapter (HBA). Even for the same I / O device, information such as an identifier for each I / O device is different. Information such as the identifier of the I / O device is setting information set by the OS. When changing the association between the server and the OS disk image in an operation that changes the association between the server and the OS disk image, such as deployment of an OS disk image or changing the connection to an LU that stores a new OS disk image If the OS has a device driver that matches the I / O device configuration of the associated server and the setting information is not set appropriately, the OS will not operate normally.

  The I / O device setting information is set based on logical information set for each I / O device, and physical location information and physical specific information of the I / O device connected to the server. There is physical information. For example, an IP address is set as logical information in the NIC, but the IP address is associated with a MAC address unique to each NIC, and even if a plurality of similar NICs are connected to the server, Are recognized by the OS as different NICs. If such setting information for the device driver is not compatible with the I / O device, the OS does not operate normally. Conversely, if the configuration of the I / O device does not match the OS disk image having the device driver and its setting information, a physically redundant I / O device configuration may be used. If the necessary I / O device configuration is not included, the OS does not operate normally.

  The present invention is an operation management system and management method configured as follows. An operation management method in a management server that manages association between an OS disk image of a computer system that includes a managed server and an OS disk image that operates on the managed server and the managed server, the first managed server I / O device recognition information recognized by the OS disk image above is collected, physical device configuration information indicating the configuration of the I / O device of the second managed server is collected, and the I / O device recognition information and the physical device are collected. Based on the configuration information, the OS disk image is loaded on the second managed server, and it is determined whether or not the operation is possible when it is executed.

  Another aspect of the present invention has the following configuration. An operation management method by a server that loads and executes an OS disk image and a management server that manages the OS disk image in association with the server, wherein the management server includes a first I / O device used by the OS disk image. First information stored in the I / O device recognition table, including an I / O device recognition table for storing information and an I / O device configuration table for storing second information related to an I / O device provided in the server Is included in the second information stored in the I / O device configuration table, and when included as a result of the determination, the OS disk image is associated with the server.

  According to still another aspect of the present invention, the management server includes information that is not included in the second information stored in the I / O device configuration table among the first information stored in the I / O device recognition table. In some cases, even if the information that is not included is changed, the information that is not included is changed within the changeable range in which the OS disk image can be executed by the server, and the first information including the changed information is the I / O device configuration. When included in the second information stored in the table, the OS disk image is associated with the server.

  According to the present invention, when an OS disk image is associated with a server, it can be confirmed in advance whether the OS disk image operates on the server.

  Hereinafter, embodiments of the present invention will be described using examples.

  A computer system configuration of this embodiment is shown in FIG. The managed servers 101 to 103 (hereinafter referred to as server 101) are managed servers of the management server 130. In the system of this embodiment, there are one or more servers. The processing units 131 to 136 of the management server 130 will be described later. The OS disk image 111 is a program (file) stored in an external storage device such as a storage device that can be accessed from the management server 130 and the server 101, and details thereof will be described later. The device recognition information table 120 is a table used by the management server 130 and is provided corresponding to each OS disk image 111.

  The server 101 is a computer configured as shown in FIG. The server (computer) 101 includes a CPU 201 that executes a program and a memory 204 that stores the program and data. The CPU 201 and the memory 204 are connected by a system bus 203 that is a data access communication path to the memory 204. The system bus 203 includes devices such as SCSI / FC (Small Computer System Interface / Fiber Channel) 207, NIC 208, and input / output device interface 209 via an IO bridge typified by PCI (Peripheral Component Interconnect). Interface) is connected. Programs such as OS and applications are read from the external storage device 211 to the memory 204 and executed by the CPU 201.

  In each of the managed servers 101 to 103, an individual job is operating. Application software related to business and basic software such as an OS are included in the OS disk image 111. The OS disk image 111 is a generic name for programs and data stored in the external storage device 211 or the like.

  An example of the external storage device 211 is an LU on an external storage device connected by a SAN or the like. In this embodiment, the configuration example of the OS disk image 111 will be described using the contents of a disk arranged on an LU. However, the OS disk image is not limited to the image on the LU, but it can be virtually displayed on the contents of the internal disk or on the file system of another OS as used in recent computer virtualization. You may use a single huge file built in

  FIG. 3 shows a configuration example of the OS disk image. The OS disk image 111 includes an OS kernel program 502 including a device driver 503, OS kernel data 504 including device driver setting information 505, an application program 506, and application data 507. The procedure for loading the OS disk image into the server 101 and executing it is as follows. A boot loader program is stored in the memory 204 of the server 101 in advance. The boot loader program is stored in the memory 204 by an initial loader program prepared as firmware that operates when the server 101 is powered on. In response to an instruction of the OS disk image to be loaded from the management server 130 to the boot loader program (an instruction with parameters such as the LU storing the OS disk image and the identifier of the OS disk image), the OS disk image is stored in the memory. 204. When loading is completed, the boot loader program starts the OS kernel program 502. The OS kernel program 502 executes the application program 506, and the business is started. As the application program 506 is executed, input / output commands and transmission / reception commands are issued, and the OS kernel program 502 uses the device driver 503 to execute these commands. Since the device driver program 503 operates based on the device driver setting information 505, the device driver setting information 505 is connected to the server 101 when the device driver 503 or the I / O device corresponding to the command does not exist or even if it exists. If the I / O device is not compatible, the server 101 does not operate normally. If the server 101 does not operate normally, it can be said that the OS does not operate normally.

  Each OS disk image is managed by the management server 130 in association with the device recognition information table 120. The device recognition information table 120 stores setting information of an I / O device recognized by the OS stored in the associated OS disk image 111 and its device driver. Details of the device recognition information table 120 will be described later.

  FIG. 4 shows a configuration example of the management server 130. The management server 130 includes processing units such as a server physical configuration acquisition unit 131, a device recognition information table management unit 132, a server physical configuration survey unit 133, an OS operation estimation unit 134, an OS operation determination unit 135, and a user interface 136. The management server 130 also stores a device recognition information table 120, a server allocation state management table 301, an investigation OS image 302, an OS disk image-device recognition table association table 303, and an operation determination rule 304.

  The server physical configuration acquisition unit 131 receives device recognition information transmitted from the server 101 and extracts difference information from the contents of the device recognition information table 120. The device recognition information table management unit 132 updates the contents of the device recognition information table 120 associated with the OS disk image 111 with the difference information extracted by the server physical configuration acquisition unit 131.

  The server physical configuration investigation unit 133 acquires the physical device configuration of the server 101.

  The OS operation estimation unit 134 estimates the OS behavior based on the device recognition information stored by the device recognition information table management unit 132 and the physical device configuration information acquired by the server physical configuration investigation unit 133.

  The OS operation determination unit 135 determines whether the OS operates normally based on the estimation result of the OS operation estimation unit 134.

  FIG. 5 shows the relationship between the server physical configuration acquisition unit 131 and the server-OS disk image association program. The server physical configuration acquisition unit 131 operates in cooperation with the server-OS disk image association program 401 in the external storage device 211. The server physical configuration acquisition unit 131 has a server allocation state management table 301.

  An example of the server allocation state management table 301 is shown in FIG. The server allocation status management table 301 stores a server identifier 601, an OS disk image management server identifier 602, and an allocation status 603 in association with each other.

  The server identifier 601 is an identifier for uniquely identifying the management target server 101 in the system managed by the management server 130. For example, when the server is a blade type system, the server uniquely identifies the chassis (enclosure) to which the server belongs in combination with the identifier. As another example, in a system in which managed servers are mounted on one or more racks, the server has an ID (rack number) that uniquely identifies the rack and the height at which the server is mounted on the rack. It can be uniquely identified by the position information (ID in the rack).

  The OS disk image management server identifier 602 is an identifier for uniquely identifying the management target server in the system managed by the management server 130. It may be the same as the server identifier 601. An example of the OS disk image management server identifier 602 when using the LU of the SAN storage device as the OS disk image storage location is the WWN of the Host Bus Adapter (HBA) owned by the server.

  The server allocation status 603 indicates the operating status of the server. If a task using an OS disk image with the managed server 101 is being executed, “assigned” is indicated. If no OS disk image is assigned (the managed server 101 is not executing a task), “ "No assignment".

  The server-OS disk image association program 401 has a server-OS disk image association table 411. An example of the server-OS disk image association table 411 is shown in FIG. The server-OS disk image association table 411 is composed of columns of an OS disk image management server identifier 701 and an OS disk image identifier 702. The OS disk image management server identifier 701 has the same contents as the OS disk image management server identifier 602 in the server allocation state management table 301. The server-OS disk image association program 401 manages the management target server 101 in the system using the OS disk image management server identifier 701. The OS disk image identifier 702 is an ID that uniquely identifies an OS disk image in the system. In this embodiment, the LU on the external SAN storage device is used as the OS disk image storage location. For example, an identifier for uniquely identifying the external SAN storage device and an LU for uniquely identifying the LU within the external SAN storage device Combine identifiers. A specific example is / STORAGE1 / LU001 when representing the LU with the LU number 1 in the SAN storage device STORAGE1.

  The device recognition information table management unit 132 holds an OS disk image-device recognition information association table 303 and a device recognition information table 120 corresponding to 1: 1 for each OS disk image.

  The OS disk image-device recognition information association table 303 is a table for managing the association between the OS disk image identifier and the corresponding device recognition information table 120. An example of the configuration of the OS disk image-device recognition information association table 303 is shown in FIG. The OS disk image / device recognition information association table 303 is managed as a set of an OS disk image identifier 801 and a device recognition table identifier 802.

  The device recognition information table 120 is a table that stores and updates device recognition information transmitted from the OS device recognition information transmission unit 140. A description will be given by taking a PCI device as an example of the device of the management target server 101.

  A configuration example of the device recognition information table is shown in FIG. The device recognition information table 120 includes a revision number 901, a bus number 902, a device number 903, a function number 904, a vendor ID 905, a device ID 906, a device unique ID 907, a used device driver 908, a driver correspondence setting 909, and an operation result 910.

  A bus number 902, a function number 903, and a function number 904 are information indicating a place where a PCI device is mounted. The vendor ID 905 and the device ID 906 are vendor and device identifiers that provide the corresponding PCI device. The device unique ID 907 is an identifier for uniquely identifying the corresponding device worldwide. A device such as a NIC or HBA has an identifier for uniquely identifying the device, such as a MAC address or World Wide Name (WWN). Since the OS may specify driver information in association with this identifier, individual IDs are collected and stored for the corresponding product. The used device driver 908 is an identifier for specifying the device driver program 505 used by the OS to operate the corresponding device. Normally, a combination of the device driver file name and version name is used.

  The device driver setting 909 is setting information associated with the corresponding device driver. This information includes device driver parameters and logical information associated with the device driver. Examples of logical information include setting an IP address for a NIC, for example. In addition, setting of teaming technology (sometimes referred to as Bonding technology) that treats a plurality of NICs logically as one device is also treated as an example of logical information.

  The items to be collected as device driver settings are determined in advance by the OS device recognition information transmission unit implementer to determine the items necessary for the OS operation determination unit 135 for the OS to be supported, and the OS device recognition information transmission unit 140 needs to be programmed to collect the necessary information.

  The operation record 910 is information indicating whether or not there is a record of actually running an application using the device driver 909. For example, the status related to the results such as “with operation results” and “without operation results” is recorded. A specific update example of the operation result 910 will be described later.

  Similar to the server physical configuration acquisition unit 131, the device recognition information table management unit 132 specifies an OS disk image associated with a server in cooperation with the server-OS disk image association program 401, and acquires the server physical configuration. The device recognition information acquired by the unit 131 is stored in the corresponding device recognition information table 120.

  In later operations, the system administrator changes the association between the server and the OS disk image for purposes such as server augmentation, usage changes, and load distribution by scale-out. At that time, the OS operation determination unit 135 determines whether or not the OS operation is possible by referring to the contents of the device recognition information table 120 and the device configuration information acquired by the server physical configuration investigation unit 133 to be described later. Suppresses execution of OS disk images in

  The server physical configuration investigation unit 133 executes the investigation OS on the management target server 101 and executes processing for acquiring device configuration information of the physical server. The server physical configuration investigation unit 133 stores the investigation OS disk image 302 on the management server 130. The OS for investigation is the OS disk image shown in FIG. 3, but since only the functions necessary for investigating the device are installed, unnecessary program code is not required and the size of the program code is small. The investigation OS transmits a physical device configuration information transmission message to the server physical configuration investigation unit 133. A configuration example of the physical device configuration information transmission message is shown in FIG. The physical device configuration information transmission message includes a bus number 1101, a device number 1102, a function number 1103, a vendor ID 1104, a device ID 1105, and a device unique identifier 1106. These pieces of information are the same type of information as the bus number 902 to the device unique ID 907 held in the device recognition information table 120. The device recognition information table 120 shows the device configuration at the time of operation of the OS disk image 111. The information of the physical device configuration information transmission message is obtained by investigating the current device configuration. Even if the management target server is the same as the management target server 101 when the device recognition information is acquired, the configuration is different when, for example, device parts are replaced. In addition, there is a high possibility that the managed servers 101 specified by different server identifiers 601 have different device configurations. These pieces of information are obtained by using predetermined means to obtain information in a predetermined format defined by the PCI specification, and details thereof are omitted.

  The OS operation estimation unit 134 receives the server identifier 601 in FIG. 6 and the OS disk image identifier 702 in FIG. 7 as inputs, the device recognition information table 120 associated with the OS disk image identifier 702, and the server physical configuration investigation unit When the OS disk image operates on the managed server 101 using the physical device configuration information transmission message (illustrated in FIG. 11) 133 acquired from the managed server 101 indicated by the server identifier 601, each Determine how the device is recognized.

  One example of the implementation form of the OS operation estimation unit is a program that simulates the logic of the OS device driver program and returns device recognition information as the operation result. The OS operation estimation unit 134 is implemented by a system provider (usually a management server system implementor) by a program. Assuming that the specifications of the OS device recognition operation are known, this program is a module that logically executes the same logic as the operation of the target OS, and can be implemented.

  As an example of another implementation form of the OS operation estimation unit 134, there is a method of preparing a virtual server dedicated to device recognition estimation. In this method, the same OS disk image 120 as the OS on the virtual server is prepared, the device configuration of the virtual server is rewritten with the device configuration information, and the device recognition information of the OS on the virtual server is changed to the device recognition information. Rewrite the settings in the table 120 to start the OS on the virtual server. After activation, the OS device recognition information transmission unit program is executed on the OS of the virtual server to acquire device recognition information, and the device driver setting 909 included in the device recognition information is returned as a result.

  The OS operation determination unit 135 receives a physical device configuration information transmission message (shown in FIG. 11) as an input and the device driver setting 909 estimated by the OS operation estimation unit 134 for each device, and the state of the device driver setting 909 is normal for the OS. It is determined whether or not it is in an operating state. The OS operation determination unit 135 refers to the OS operation determination rule 304 to determine whether or not the OS operates normally. The OS operation determination rule 304 is a rule that describes conditions for OS setting 909 necessary for the OS to operate normally, and is created in advance by an administrator or a system provider. One implementation example of the OS operation determination rule 304 is a program that determines whether or not an OS device driver setting for each device driver is set in advance. For example, the check item “The IP address associated with the NIC has a predetermined value” is an example of the OS operation determination rule 304.

  As another implementation example of the OS operation determination rule 304, there is a method in which the state determination is held as a table in the normal operation of the device driver instead of the program code. When implemented as a table, the OS device driver setting indicated by the OS operation determination rule 304 matches the device driver setting 909 as a result of the estimation by the OS operation estimation unit 134, and the performance confirmation procedure is defined in advance. If 1209 ends normally, it is determined that the operation is normal. The definition in advance is performed by a method such as a system operation manager that is created when the management system is constructed. One OS operation determination rule 304 exists for each device recognition information table 120 individually. That is, it means that there is a one-to-one correspondence with the OS disk image. FIG. 12 shows a configuration example when the OS operation determination rule 304 is held as a table. The OS operation determination rule 304 includes a bus number condition 1201, a device number condition 1202, a function number 1203, a minimum required number 1204, a maximum allowable number of times 1205, a vendor ID condition 1206, a device ID condition 1207, an OS setting 1208, and a result confirmation procedure. 1209.

  The bus number condition 1201 to the device ID condition 1207 are conditions for specifying a device to be subjected to the condition determination, and the data of the bus number 902 to the device ID 906 in the device recognition information table 120 are the bus number condition 1201 to the device. Those that match the condition indicated by the ID condition 1207 are determined. As examples of the bus number condition 1201 to the function number condition 1203 for specifying the position of the PCI device, a specific numerical value, an arbitrary numerical value, and a relative order in a certain group can be designated. As an example of the relative order, there is a condition such as “the Nth smallest value among devices with the same vendor ID and device ID”. Each condition may include one or more values. In that case, the OS operation determination unit 135 determines that the condition is satisfied when any of the values is met.

  In addition, the number of devices that satisfy the above conditions needs to fall between two numbers, ie, the minimum required number 1204 and the maximum allowable number 1205.

  The OS setting 1208 is a list of values of the OS setting 909 that should be satisfied when the OS operates. For example, if the IP address is an example of the judgment target of OS setting 1208, the conditions such as “IP address is equal to XX.XX.XX.XX”, “IP address setting is DHCP acquisition”, “IP address is not set”, etc. There is. When the device driver setting 909 of the device to be determined matches the OS setting 1208, it is determined that the OS operates.

  The result confirmation procedure 1209 is information indicating a procedure for confirming a result of actual application operation. The results confirmation procedure is written, for example, “Ping YY.YY.YY.YY”, “Confirming connection to database YY with SQL program”, “Run application communication test program A”, etc. The designated procedure is executed in the OS operation result flow described later. Each program has a pre-determined code that is returned as a result of normal termination, and when that value reaches a specific value, it is guaranteed that it can be confirmed that it is operating normally. Shall.

  Below, the operation | movement flow of each program of the management server 130 is demonstrated.

  First, an operation flow for collecting OS device recognition information will be described with reference to FIG. The OS device recognition information is performed in conjunction with the OS device recognition information transmission unit 140 operating on the management target server 101 and the server physical configuration acquisition unit 131 on the management server 130.

  An example of the operation flow of the OS device recognition information transmission unit 140 will be described with reference to FIG. First, the management target server is turned on (step 1001). The server power-on operation may be performed by any method. For example, a method in which a human presses the power button of the server at an arbitrary timing may be used. Other methods include a method specified by the operation administrator using the user interface of the management server, or a program that manages the power supply of the managed server automatically starts processing at the time scheduled in advance. Started by the method. In the case of the method specified by the operation manager using the user interface, the server identifier 601 is designated by a method such as selecting the server identifier 601 and the corresponding managed server is started. As an example of implementation for causing the operation administrator to select the server identifier 601, the management server 130 displays a list of server identifiers 601 held in the server allocation state management table 301 on the user interface of the management server and presents it to the operation administrator. There is a method for selecting one of them.

  In the managed server 101 whose power is turned on, the OS kernel program 502 is activated by the boot loader program 501 to enable the OS function. The OS device recognition information transmission unit program 508 is activated when the OS is activated (step 1002).

  The OS device recognition information transmission unit program 508 acquires the device driver recognition information 505 through an interface for accessing the OS function (step 1003). The acquired information is obtained by acquiring each item included in the device recognition information table shown in FIG. 9 for all devices included in the physical server on which the OS operates.

  The device recognition information transmission unit program 508 specifies a device recognition information transmission destination (step 1005). The device recognition information transmission destination must be the management server 130. As an example of specifying the device recognition information transmission destination, it is possible to use a management server address defined in advance in the setting file on the investigation OS by the operation administrator.

  A device recognition information message is transmitted to the device recognition information transmission destination selected in step 1005 (step 1006). The information transmission can be implemented by a method such as transmitting the device recognition information message to the management server through an interface such as a NIC.

  The OS device recognition information transmission unit program 508 waits for the performance confirmation procedure 1209 to be transmitted from the partner who transmitted the message in step 1006 (step 1007).

  When the OS device recognition information transmission unit program 508 receives the result confirmation procedure 1209 from the management server, it confirms the result procedure according to the method written in the result confirmation procedure 1209 (step 1008). The actual result confirmation procedure is described in the form of, for example, an individual confirmation program or a batch file describing the execution order of the programs. The OS device recognition information transmission unit program 508 sequentially executes the program and collects execution result information such as an end code returned to the OS.

  The OS device recognition information transmission unit program 508 transmits the execution result of the result confirmation procedure acquired in step 1008 to the device information transmission destination selected in step 1005, and ends the process (step 1009).

  An example of the operation flow on the management server 130 side that collects and stores data is shown in FIG.

  The management server 130 waits for reception of a device recognition information message (step 1011). The reception waiting may be implemented in the same manner as the reception processing of a network program using a normal NIC.

  The server physical configuration acquisition unit 131 receives the device recognition information message transmitted in step 1006 (step 1012).

  The server identifier 701 shown in FIG. 7 is acquired from the information included in the device recognition information message (step 1013). For example, in the example in which the OS disk image is an LU, the device unique ID 907 is referenced for the vendor ID 905 and the device ID 906 indicating that the device ID 906 is an HBA product, and information indicating the WWN of the HBA is extracted and used as the server identifier 701.

  The server physical configuration acquisition unit 131 passes the server identifier 701 to the device recognition information table management unit 132, and requests to acquire a list of OS device recognition information tables to be used with the server identifier 701. The device recognition information table management unit 132 refers to the server-OS disk image association table in FIG. 7 in cooperation with the path management program 401 to obtain the OS disk image identifier 702 corresponding to the server identifier (step 1014). Referring to the OS disk image-device recognition table association table shown in FIG. 8, the device recognition information table corresponding to the OS disk image identifier 702 is acquired, and the data in the table is returned to the server physical configuration acquisition unit 131 ( Step 1015).

  The server physical configuration acquisition unit 131 compares the device recognition information message acquired in step 1012 with each item of the device recognition information table acquired in step 1015, and extracts a difference (step 1016). The differences are as follows: (a) Devices having the same bus number 902, device number 903, function number 904, vendor ID 905, and device ID 906 in the device recognition information message, and corresponding devices exist in the device recognition information table. There are two types of differences: an item not to be processed, and (b) a device that exists in both the device recognition information message and the device recognition information table, and the corresponding used device driver 908 or device driver setting 909 is different. The extraction can be executed by comparing the bus numbers 902 to device driver settings 909 of the respective devices and confirming whether they correspond to the above (a) and (b).

  If a difference is found in step 1016, the difference information is updated in the device recognition information table (step 1017). Updating (a) adds a new item, and updating (b) overwrites an existing item.

  The server physical configuration information acquisition unit 131 refers to the OS operation determination rule 304 associated with the device recognition information table acquired in step 1015, and acquires all the result confirmation procedures 1209 included in the table (step 1018). ).

  The server physical configuration information acquisition unit 131 transmits the list of the result confirmation procedure 1209 acquired in step 1018 to the OS device recognition information transmission unit program 508 that has transmitted the device recognition information message in step 1012 (step 1019). The execution result is transmitted in a format such as a table in which two pieces of information are set, for example, so that each executed program and a set of the results can be confirmed.

  Finally, the server physical configuration information acquisition unit 131 waits for the OS device recognition information transmission unit to execute the result confirmation procedure 1209 transmitted in step 1019 and return the result (step 1020). When the result is received, it is confirmed whether or not each result indicates a normal end. If it is a normal return value, “with operation record” is written in the corresponding operation record 910 (step 1021).

  With the processing in FIG. 10, information related to OS device recognition and operation result information are collected in the management server 130. This information is later used as an input for determining whether or not the OS operates normally when the association between the OS disk image 111 and the managed server 101 is changed.

  Next, when the operation administrator changes the association between the OS disk image 111 and the managed server 101, whether or not the OS operates normally using the OS disk image 111 on the change target managed server 101. The operation flow for determination will be described with reference to FIG.

  The management server 130 receives the input of the server identifier 601 and the input of the OS disk image identifier 702 (step 1301). As an example of the item input method, there is a method in which the operation manager designates using the user interface of the management server. In the case of the method specified by the administrator using the user interface, the server identifier 601 and the OS disk image identifier 702 display the list of server identifiers 601 held by the management server 130 on the user interface of the management server and present them to the administrator. It can be specified by a method of selecting one of them by a method of selecting one of them.

  The management server 130 refers to the OS disk image identifier 702 input at step 1301 and acquires the corresponding device recognition information table 120 (step 1302). As the acquisition method, a method equivalent to the description in step 1015 may be used.

  If the corresponding device recognition information table 120 is found in step 1302, steps 1304 to 1310 are executed. If no corresponding table is found, steps 1311 to 1312 are executed (step 1303).

  The management server 130 passes the server identifier 601 acquired in step 1301 to the server physical configuration investigation unit 133 and requests server physical device configuration information. The server physical device configuration information investigation unit 133 executes the procedure shown in FIG. 14 (device configuration information acquisition processing from the physical server), and returns a device configuration information message to the management server (step 1304). Specific examples of processing contents will be described later.

  The management server 130 passes the device recognition information table 120 acquired in step 1302 and the device configuration information message acquired in step 1304 to the OS operation estimation unit 134, and the OS selects the device based on the input information. Requests to return the device driver recognition information table of the recognized result. The OS operation estimation unit 134 executes the above-described emulation processing and the like, and returns an OS device recognition information table as a result (step 1305).

  The management server 130 passes the device recognition information table acquired as a result of step 1305 to the OS operation determination unit 135, and the OS specified by the OS disk image identifier 702 is executed on the management target server 101 specified by the server identifier 601. Request to determine if it works. The OS operation determination unit 135 executes the procedure shown in FIG. 15 and returns an OS operation determination result (step 1306).

  If it is determined in step 1306 that the determination result is “OS operation record exists”, step 1310 is executed. If it is determined not to operate, step 1308 is executed (step 1307).

  It is confirmed whether or not motion estimation is performed by OS setting. As an example of the confirmation method, a flag indicating whether or not to perform an operation estimation by OS setting is prepared in advance, and a method of allowing an operation administrator to make a selection when building a management system, There is a method of displaying whether or not to perform the operation estimation by OS setting by displaying a dialog with the content such as “Do you estimate the operation by OS setting? (Y / N)”. Steps 1309 to 1310 are executed when the result of OS operation estimation is obtained, and steps 1311 and 1312 are executed when the result of operation estimation by OS setting is not obtained (step 1308).

  If the determination result in step 1306 is “confirm only OS setting” and if the result of operation estimation based on OS setting is obtained in step 1308, step 1310 is executed. If either condition is not satisfied, Steps 1311 and 1312 are executed (Step 1309).

  If it is determined in step 1306 that there is an OS operation result, if it is determined in step 1309 that only the OS setting is confirmed, or if the association between the OS disk image 120 and the managed server 111 is changed in step 1311 described later. When the instruction is issued, the association between the OS disk image 120 and the management target server 111 is actually changed (step 1310). When the OS disk image 120 is implemented as an LU on the SAN storage device, the association change instructs the path management program 401 to change the server-OS disk image association table, and actually the SAN storage. This is an operation for changing the association between the LU and the WWN as the server identifier 701 by setting the network settings of the device and SAN.

  When the determination result indicating that the OS is operating is not obtained, the management server 130 notifies the instructor (such as an operation manager) of the association change operation that the determination result indicating that the OS is operating is not obtained. To confirm whether or not to continue (step 1311). As an example of the notification method and confirmation method, there is a method that displays a dialog with a content such as “The specified server does not have an operation record. Do you want to continue the mapping change (Y / N)” on the user interface? . The administrator inputs inputs such as “Yes” and “No” as answers.

  If the result input in step 1311 is an instruction to continue the association changing operation, step 1310 is executed. If not, the process ends (step 1312).

  With the above operation flow, for example, when the administrator attempts to change the association between the OS disk image 120 and the managed server 101, the OS is a device in the combination of the OS disk image 120 and the managed server 101 specified by the administrator. It is possible to notify the administrator in advance that it will not operate at each level of recognition, logical setting assignment, and operation at the business level. It is possible to prevent a malfunction of the OS that is not originally intended to occur potentially due to replacement.

  An example of the device configuration information investigation flow referred to in step 1304 in FIG. 13 will be described with reference to FIG.

  The device configuration information investigation flow is executed by the management server 130 and the management target server 101 operating together.

  The management server instructs the managed server 101 to start the system using the investigation OS disk image 302 (step 1401). In response to an instruction from the management server, the managed server 101 turns on the power (step 1411), acquires the investigation OS disk image 302 from the management server 130, and executes it (step 1412). As an example of a method for realizing the steps 1401, 1411, and 1412, there is a method in which Wake-on-Lan and PXE boot are combined. The management server 130 and the managed server 101 communicate with each other through the NIC. The managed server 101 has a NIC corresponding to Wake-on-Lan, and receives a specific packet notified from the management server 130 and turns on the power. The management server 130 has a server function compatible with PXE boot, and distributes the investigation OS disk image to the management target server. The managed server 101 has a client function compatible with PXE boot, and acquires and executes an OS disk image for investigation.

  After starting, the investigation OS acquires the device configuration of the management target server 101 as shown in FIG. 11 (step 1413). For example, in the PCI device, the PCI bus number 1101 to the device ID 1105 are written at predetermined positions in the memory at the time of activation, and can be mounted by an operation of reading the contents.

  The investigation OS formats the device configuration information acquired in step 1413 into the physical device configuration information transmission message format shown in FIG. 11 and transmits it to the management server 130 (step 1414). Thereafter, the power is turned off (step 1415).

  The management server 130 acquires the physical device configuration information transmission message transmitted in step 1414 and delivers it to the component that requested the processing (step 1403).

  Finally, an example of the OS operation determination execution flow referred to in step 1306 in FIG. 13 will be described with reference to FIG.

  The OS operation determination unit 135 receives the physical device configuration information transmission message of FIG. 11 from other components and the OS device recognition information table (shown in FIG. 9) as a result of the OS operation estimation unit 134 estimating the OS operation. It is determined whether or not the OS operates by referring to the two. Hereinafter, the OS device recognition information table is referred to as a list X (step 1501).

  In the subsequent processing, a storage area for storing the result of OS operation determination is simply referred to as a determination result. The determination result may be a storage area secured in a memory or the like. It is assumed that the initial value of the determination result is “operation possible” (step 1502).

  The OS operation determination unit 135 repeatedly executes Steps 1503 to 1506 for each rule of the OS operation determination rule in FIG. 12 (Step 1503). Hereinafter, the item selected in this step is referred to as condition A.

  The OS operation determination unit 135 selects, from the devices included in the list X, a device that meets the condition A in accordance with the rules described above with reference to FIG. 12 (step 1504). Hereinafter, the list of devices selected as a result of this step is referred to as a list Y. When the number of selected devices falls within the range indicated by the minimum required number 1204 and the maximum allowable number 1205 in FIG. 12, Steps 1505 to 1507 are executed (Step 1505). If it does not fall within the above range, step 1510 is executed.

  Steps 1507 to 1509 are executed for the device driver information (hereinafter referred to as device driver information B) corresponding to each device selected in step 1504 (step 1506).

  It is confirmed whether the status of the operation results included in the device driver information B is “with operation results”. If “there is an operation record”, the process proceeds to processing of the next device driver information in the list Y (step 1507).

It is confirmed whether the device driver information B conforms to the OS setting 1208 included in the condition A. The confirmation method is performed by the method shown in the explanation of the OS setting 1208 in FIG. There may be a plurality of items such as an IP address and teaming in the OS setting 1208. In this case, it is checked whether each item is individually adapted (step 1508).
As a result, if it is found that it does not fit, step 1510 is executed. If it is found that it matches, the determination result is overwritten with the state of “confirm only OS setting” (step 1509).

  If there is no operation record and the OS setting condition B is not equal to the OS setting of the condition A, the determination result is overwritten with the “operation not possible” state, and step 1511 is executed (step 1510).

  The value of the determination result overwritten last in any one of the above processes is returned to another component as the determination result of the OS operation determination unit (step 1511).

  When changing the association between the OS disk image 111 and the managed server 101, the administrator's purpose is to select hardware for operating the business application from a plurality of candidates existing in the system. Many. Since a business application is included in a specific OS disk image 111, the number of options is generally limited to one. As a result, the operations performed when the operation manager changes the association between the OS disk image 111 and the managed server 101 are: (a) selecting the OS disk image 111; (b) management in which the OS disk image operates normally. Two procedures of searching for the target server 101 are executed in the order of (a) and (b).

  In the first embodiment, it is determined whether or not the OS operates normally when the combination of the server specified by the operation manager and the OS disk image specified by the administrator or the like is specified. In the method according to the first embodiment, in order to specify a server on which an OS disk image operates normally from a plurality of managed servers on the system, the operation administrator must check the OS operation determination of each server one by one. .

  In the second embodiment, in order to reduce the burden of confirmation by the operations manager, only the servers whose results have been confirmed are presented to the manager, and the manager or the like performs an operation of selecting an appropriate server. Like that.

  In the second embodiment, it is assumed that the system configuration is the same as that of the first embodiment. However, in the first embodiment, the server or OS disk image association operator such as the administrator performs the association change operation according to the operation flow of FIG. 13, but in the second embodiment, the server and the OS disk shown in FIG. Change as in the operation determination processing flow for image combination.

  First, the management server 130 receives the OS disk image identifier 702 as an input using the same method as in step 1301 (step 1601). At this time, it is not necessary to receive the server identifier 601 as an input.

  Next, steps 1603 to 1606 are executed for each server included in the server allocation state management table 301 (step 1602). Hereinafter, each of the servers is referred to as a server A. In the subsequent processing, a server operation guarantee list and a server operation ready list are used. These lists are data in a list format for recording the servers whose operations have been confirmed. The list is cleared before step 1601 is executed and step 1602 is repeated. The list may be stored in memory.

  It is confirmed whether or not the assigned state 603 corresponding to the server A in the server assignment state management table 301 is “assigned”. If it is not “allocated”, steps 1604 to 1606 are executed (step 1603).

  Steps 1302 to 1309 in FIG. 13 are executed using the server identifier 601 of server A and the OS disk image identifier input in step 1601 (step 1604). However, in step 1307, instead of the process of displaying “impossible to operate” using the user interface and requesting confirmation, the determination result “inoperable” is recorded, and steps 1605 to 1606 are executed.

  If the execution result of step 1604 is “OS operation record exists”, server A is added to the server operation guarantee list (step 1605).

  If the execution result of step 1604 is “OS operable”, server A is added to the server operable list (step 1606).

  After executing Steps 1602 to 1606 for all the servers A in the server allocation state management table 301, the management server 130 operates the operation guarantee list and the list of servers included in the operable list through a user interface or the like. (Step 1607). At this time, it is possible to distinguish whether each displayed server is included in the operation guarantee list or the operable list. For example, there is a method in which different icons are given to the servers in the list to indicate whether the operation is guaranteed or operable.

The operator selects one server from the servers displayed in step 1607 (step 1608).
The management server 1609 changes the association between the management target server 101 and the OS disk image 111 by the same processing as in step 1309 in FIG. 13 (step 1609).

  In the server allocation status management table, the allocation status of the entry corresponding to the server identifier selected in step 1608 is changed to “allocated” (step 1610).

  With the above operation, the administrator does not need to try the operation determination of the OS disk image 111 for all the servers, and can select from the servers for which the operation is guaranteed, thereby improving work efficiency. In addition, it is easy to compare whether the operation results have been guaranteed in the past or at a level that can be estimated to be logically operable, and there are a plurality of servers to which the OS disk image 111 is associated. This provides a useful support effect for the task of making a selection decision when selecting from the above candidates.

  FIG. 17 is a system configuration diagram of this embodiment. The management server and the management target server are different from those of the first embodiment in detail, and are therefore newly assigned numerals. Therefore, it does not necessarily indicate that the difference in the symbols is different.

  The management server 1 is connected to the management target server 2 via the management network 3. Although one server is illustrated as the server 2 to be managed, a plurality of servers may be used. The management server 1 and the server 2 are connected to a storage area network (SAN) 4 so as to access the LU 5 of the storage apparatus. The management server 1 and the server 2 are connected to a communication network 6 in order to communicate with other servers. In actual communication, the communication partner of the management server 1 is the server 2 to be managed, but the communication partner of the server 2 may be another server 2 to be managed, or a server or server 2 that is not a management target. It may be a client computer that receives the service.

  The server 2 prepares an HBA as an I / O device 7 for connecting to the SAN 4 and a NIC as an I / O device 7 for connecting to the communication network 6. In FIG. 17, HBA1 and HBA2 are shown as HBAs, and NIC1, NIC2, and NIC3 are shown as NICs.

  FIG. 17 shows a state in which the OS disk image described in the first embodiment is loaded on the server 2. As described above, the OS disk image includes the OS 20, the I / O driver (I / O device driver) 21, and the application program 25. In FIG. 17, the I / O driver 21 is illustrated as being included in the OS 20, and each I / O driver corresponds to the I / O device 7. The NIC 2 is prepared in the server 2, but it is illustrated that it is not used from the current OS disk image. The I / O drivers 21 associated with the HBA 1 and HBA 2 are both “driver 1”. This indicates that both the HBA 1 and the HBA 2 operate with the same “driver 1” as the type of the driver 21. However, since the setting information described above differs between HBA1 and HBA2, it may be prepared individually as an I / O device driver program including setting information, or the setting information may be prepared individually and the program shared. good.

  FIG. 18 shows an I / O device configuration table that the management server 1 has. The I / O device configuration table stores the ID 11 of each I / O device 7 included in the server 2 and the I / O device type 12 in association with each other. In FIG. 18, ID 11 and I / O device type 12 are shown as representative items to simplify the explanation and make it easier to understand, but the hardware of the I / O device 7 such as the vendor ID shown in FIG. 9. May include unique information. The contents of the I / O device configuration table are contents determined as specifications when the server 2 is constructed (installed), and the table is initially set via the user interface of the management server 1. In addition, the configuration of the I / O device 7 may be changed in accordance with the specification change even after the operation of the server 2 is started. However, even if the configuration of the I / O device 7 is changed, the setting of the I / O device configuration table may not be changed. In preparation for such a case, a process for acquiring the configuration of the I / O device 7 is provided. . This process will be described later.

  FIG. 18 corresponds to the configuration of the I / O device 7 included in the server 2 of FIG. HBA1 and HBA2 in FIG. 17 are the same I / O device type HBA, and ID11 is WWN1 and WWN2. The NIC indicates that the I / O device type 12 includes NIC (A) and NIC (B), the ID 11 of NIC (A) is MAC1, and the ID 11 of NIC (B) is MAC2 and MAC3. .

  FIG. 19 shows an I / O device recognition table provided in the management server 1 in order to manage information related to the I / O device 7 recognized (used) by the current OS disk image in the server 2. The I / O device configuration table of FIG. 18 is provided corresponding to the server 2, whereas the I / O device recognition table of FIG. 19 is provided corresponding to the OS disk image.

  The I / O device recognition table includes columns for I / O 14, driver type 15, I / O device type 16, I / O device ID 17, and I / O device 7 connection destination 18. The I / O 14 is a logical name or an identifier of the I / O device 7 that is used when the application program 25 accesses the I / O device 7. When a command (input / output command or transmission / reception command) for accessing the I / O device 7 is issued from the application program 25, the OS 20 executes the corresponding I / O device driver program of the driver type 15 and corresponding I / O device. The I / O device of O device type 16 and ID 17 is operated, and processing according to the command is executed with the partner indicated by the connection destination 18. As can be seen from the above description of the server 2, the contents of the I / O device recognition table are the contents set in the OS disk image. Therefore, when the OS disk image is generated, the I / O device recognition table is initialized through the user interface of the management server 1 according to the specification. In addition, the configuration change of the I / O device 7 and the specification of the OS disk image may be changed due to the specification change even after the operation of the OS disk image is started. However, even if the configuration of the I / O device 7 is changed, since the I / O device recognition table is provided corresponding to the OS disk image, the setting of the I / O device recognition table cannot always be changed. In preparation for such a case, a process for making the setting of the I / O device recognition table correspond to the configuration of the I / O device 7 and making the execution of the OS disk image in the server 2 impossible is not provided. This process will be described later.

  The I / O device recognition table in FIG. 19 corresponds to the configuration of the I / O device 7 used by the OS disk image on the server 2 in FIG. Specific table contents will be described later in an operation example in which the management server 1 uses the I / O device recognition table.

  20 is a system including another server 2 that attempts to load and execute the OS disk image of FIG. 17, or a server 2 that has been executing the OS disk image of FIG. 17 and that has elapsed from the configuration of FIG. It is a configuration. The configuration of the I / O device shown in FIG. 20 differs from the configuration of the I / O device shown in FIG. 17 in the following two points. The change of the mounting location (mounting position) in the server 2 of the HBA 2 and the NIC 3 do not exist. With such changes, even if the OS disk image including the application 25 shown in FIG. 17 is loaded and executed, an error may occur when accessing the NIC 3 and an error may occur when accessing the HBA 2.

  As described above, the I / O device configuration table of the management server 1 may not correspond to the configuration of the I / O device shown in FIG.

  Therefore, the OS disk image including the I / O device configuration acquisition program 22 is loaded on the server 2 and executed. This OS disk image corresponds to the investigation OS image shown in FIG. 4, and has an I / O device driver program corresponding to the type of I / O device mounted on the server 2 that is managed by the management server 1. ing.

  FIG. 21 shows a process flowchart of the I / O device configuration acquisition program 22. The I / O devices mounted on the server 2 are sequentially checked (S30). An unchecked I / O device is selected (S31). In order to find a driver type suitable for the selected I / O device, the operation of the I / O device driver program is sequentially checked (S32). An unchecked I / O device driver program is selected and executed (S33). The selection of the I / O device driver program uses a driver management table that the OS 20 has.

  FIG. 22 shows a driver management table. The driver management table has a driver type 40, a driver head address 41, a setting information head address 42, and setting information 43. The driver type 40, the driver head address 41, and the setting information head address 42 are set when the OS disk image is generated. Therefore, the selection of the I / O device driver program sequentially selects the I / O device driver program of the driver type 40 in the driver management table from the top. The selected I / O device driver program is executed from the head address (start address) at the driver head address 41. At the start of execution, the I / O device configuration acquisition program 22 delivers parameters so as to read the setting information of the I / O device set as firmware in the I / O device. If the I / O device driver program is compatible with the I / O device, the setting information can be read normally, but if it is not compatible, an error response can be obtained from the I / O device or no response can be obtained (timeout error). The setting information read normally is stored in the setting information area from the setting information head address 42. As shown in the setting information 43, the setting information area is sequentially divided into setting information and its capacity (number of bytes) from the top. In the driver 1 of FIG. 22, setting information is stored from the xxxx address of the setting information head address 42, and WWN is stored in m bytes therein.

  Returning to FIG. If the response from the I / O device driver program is an error response, the process returns to S32 and a new I / O device driver program is selected. If there is no compatible I / O device driver program, that fact is stored in association with the I / O device (S37). If the response from the I / O device driver program is a normal response, the I / O device type is acquired by referring to the setting information head address 42 and the setting information 43 (S35), and the ID of the I / O device is acquired. To do. When all the I / O devices mounted on the server 2 have been checked, the acquired I / O device type and ID of the I / O device are transmitted to the management server 1 via the management network 3 ( S38). In S37, if an I / O device for which there is no compatible I / O device driver program is stored, the stored content is also transmitted.

  In general, I / O device driver program interface specifications are published by I / O device vendors as I / O device specifications, so I / O device driver programs were used to identify I / O devices. When the firmware (ROM) address where the setting information is stored is disclosed, the I / O device configuration acquisition program 22 may directly read the setting information.

  When the I / O device type and the ID of the I / O device are received from the server 2, the management server 1 updates the I / O device configuration table as shown in FIG. 23 includes a No column 10 and an association flag column 13 in addition to the I / O device configuration table shown in FIG. The association flag column 13 will be described later. FIG. 23 shows the configuration of the I / O devices mounted on the server 2 of FIG. 20, but the No. 1, No. 3 and No. 4 I / O devices are the same as the configuration of FIG. O device IDs are different. 18 also indicates that there is no I / O device whose ID 11 of the I / O device shown in FIG. 18 is MAC3.

  The management server 1 copies the I / O device recognition table shown in FIG. 19, that is, the I / O device recognition table corresponding to the OS disk image to be executed, to the work area. FIG. 24A shows the copied I / O device recognition table. A change notification flag column 19 is added to the copied I / O device recognition table as shown in FIG.

  When the I / O device configuration table of FIG. 23 and the I / O device recognition table of FIG. 24 are prepared, the management server 1 executes the process shown in FIG.

  FIG. 25 is a flowchart of the OS disk image operation determination process in the server 2. The I / O devices in the I / O device recognition table are sequentially selected and checked (S50). It is determined whether or not an I / O device having the same I / O device type 16 and ID 17 of the selected I / O is in the I / O device configuration table (S52). If they do not match, the I / O device configuration table is sequentially checked (S54), and it is checked whether there is an I / O device type table that matches the I / O device type 16 (S56). Individually, I / O device type 16 is described as a representative, but the changeable range of information related to the I / O device used by the OS disk image, including the I / O device model, etc. Checked. If the I / O device type 16 matches the I / O device type table, it is checked whether the association flag 13 corresponding to the I / O device type 12 in the I / O device type table is on. (S58). When the association flag 13 is off, the ID 17 of the I / O device in the I / O device recognition table is changed, and the change notification flag 19 is turned on (S60). Subsequently, the association flag 13 of the I / O device configuration table is turned on. When the association is completed for all the I / O devices in the I / O device recognition table, the change contents regarding the I / O device whose change notification flag 19 is on are notified to the program that changes the OS disk image (S64, S66). ). A program for changing the OS disk image is provided in the management server 1 in order to change the OS disk image stored in the external storage device. A program for changing the OS disk image may be provided in the server 2, but when the OS disk image is executed at the next opportunity, the OS disk image stored in the external storage device has not been changed, so the operation is judged. The process needs to be executed again. If the association is not possible even after checking the I / O device configuration table in S54, the administrator can confirm that the OS disk image to be executed on the server 2 cannot be operated via the user interface of the management server 1. Is warned (S68).

  The process of FIG. 25 is shown by a specific example. When the I / O 1 in FIG. 24 is selected and the I / O device configuration table is checked (S52), since the I / O device type 12 and ID 11 of the No. 1 I / O device are the same, the association flag is set to ON. To do. FIG. 23 shows this state. Next, when I / O 2 in FIG. 24 is selected and the I / O device configuration table is checked (S52), there is no I / O device type 12 and ID 11 that are identical (S52), and the I / O device type 12 is Since there is a match (here, HBA) (S56) and the association flag 13 is off, the ID 17 of the I / O device recognition table is changed and the change notification flag 19 is turned on. This state is indicated by a change from WWN2 (I / O2 in FIG. 24A) to WWN3 (I / O2 in FIG. 24B). Similarly, the ID 17 of the I / O 6 is changed from MAC3 to MAC2.

  The I / O device recognition table in FIG. 24A has been described as being created by copying. However, if the original I / O device recognition table is sequentially changed, all I / O used by the OS disk image is stored in the server 2. This is because the I / O device recognition table cannot be returned to the original state when it cannot be associated with the I / O device. When all the I / O used by the OS disk image is associated with the server 2 I / O device, the contents of the I / O device recognition table changed in the work area can be written back to the original I / O device recognition table. That's fine.

  Thus, the I / O device recognition table is as shown in FIG. When the OS disk image changed according to the contents of the I / O device recognition table is loaded into the server 2, the correspondence between the I / O device driver 21 and the I / O device 7 is the same as the system configuration shown in FIG. Become. Specifically, the I / O device driver 21 and the I / O device 7 are newly associated with each other as indicated by a bidirectional arrow.

  According to the present embodiment, it is possible to confirm whether the I / O device configuration of the server to be executed matches the OS disk image before executing the OS disk image.

  The OS disk image has been used as a premise to regenerate the OS disk image as a whole when a part of the OS disk image needs to be modified. If some of the modifications are application program modifications, they must be regenerated. However, it is convenient to regenerate even when a change occurs in the I / O device configuration of the server as the execution environment. Damage. According to this embodiment, even if the server I / O device configuration does not match the OS disk image I / O device configuration (may be included), there are more cases where the setting information can be changed to cope with it. Convenience that could not be obtained.

  The first embodiment is an example of investigating whether or not an OS disk image is operated on a physical server designated by an administrator or the like immediately before the OS disk image is assigned. In the first embodiment, when the allocation of a large number of servers is changed, or when an immediate allocation change is necessary, it takes time until the OS disk image allocation is instructed by the administrator and the possibility is determined. Therefore, in this embodiment, the focus is particularly on the I / O device, and the operation of the administrator assigning the OS disk image to the physical server is accelerated.

  An example of the system configuration of the present embodiment is shown in FIG. In the present embodiment, in addition to the configuration of the first embodiment, a server configuration change detection module 2701 is newly introduced as an apparatus. Also, an OS disk image operation determination table 2702 is added to the management server 130.

  The server configuration change detection module 2701 is a module that manages the physical configuration of one or more managed servers. The server configuration change detection module 2701 includes a CPU and a memory, and is configured as a device that can execute a predefined program. In addition, it has a network interface and has a function of transmitting and receiving data by communicating with the management server. The server configuration change detection module 2701 has a function of detecting the configuration when an I / O device on the management target server is added. As an example of detection, when an I / O device is inserted into a slot, the microcode on the I / O device transmits an interrupt to the dedicated bus, and the server configuration change detection module 2701 acquires the interrupt. At this time, the server configuration change module is interrupted by the server module that acquires the configuration information of the server that caused the interrupt, and the I / O by the same method as the BIOS (Basic Input Output System) of the managed server. A function for acquiring device information is provided. In other words, when the server I / O device configuration is changed, the server configuration change detection module 2701 acquires content equivalent to the device configuration information acquired by the server physical configuration investigation unit 133 for only the changed portion. . The server configuration change detection module has a function of transmitting device configuration information including only the changed portion to the management server in the same procedure as the investigation OS.

  The detection flow can be executed only by the operations of the I / O device added to the managed server and the server configuration change module 2701 regardless of whether the OS is running on the managed server. The server configuration change module also detects when an I / O device is removed from the slot. The OS disk image operation determination table 2702 holds a list of operation determination results for each combination of an OS disk image managed by the management server and a managed server managed by the management server. As the operation determination result, a set of individual OS operation determination rules associated with the OS disk image and the results determined in steps 1504 to 1509 in FIG. 15 for the operation determination rules is recorded as a list. An example of the individual OS operation determination rule is one rule represented by each row of the operation determination rule 304 illustrated in FIG.

  Next, the operation flow in the present embodiment will be described. In the present embodiment, there are two changes compared to the first embodiment.

  First, as the first point, when the hardware configuration of the device is changed, the device configuration information including only the portion where the server configuration change detection module is changed is transmitted to the management server, and the OS operation estimation unit 134 for only the changed point. And the OS operation determination process flow shown in FIG. 15 are executed, and the OS operation determination result is stored in the OS disk image operation determination table 2702.

  The second change is that the operation determination process stored in FIG. 2702 is executed instead of executing the OS operation determination process flow in step 1604 in the operation determination process flow in the server and OS disk image combination shown in FIG. The subsequent determination is performed with the result of the case having the least operation record in the flow execution result list as the determination result of step 1604.

  FIG. 28 shows an example of an OS disk image operation determination table 2702 for executing the operation determination process flow and storing the OS operation determination result at the first change point. The OS disk image operation determination table 2702 is a table that stores an operation determination result for determining whether the OS disk image indicated by the OS disk image identifier 2801 operates on the server indicated by the operable server identifier 2802. In each operation determination result, as indicated by 2811 and 2812, the operation determination result obtained by executing steps 1502 to 1511 in FIG. 15 is stored for each rule included in the OS operation determination rule in FIG. To do.

It is a computer system structural example. It is a structural example of a server (computer). It is a structural example of an OS disk image. It is a structural example of a management server. It is a figure which shows the relationship between a server physical structure acquisition part and a server-OS disk image matching program. It is an example of a server allocation state management table. It is an example of a structure of a server-OS disk image matching table. It is an example of a structure of an OS disk image-device recognition information correlation table. It is a structural example of a device recognition information table. It is a flowchart of the operation | movement which collects OS device recognition information. It is an example of a structure of a physical device structure information transmission message. This is an OS operation determination rule. It is an operation | movement determination processing flowchart with a server and OS disk image combination. It is a device configuration information acquisition process flowchart from a physical server. It is a flowchart of OS operation | movement determination processing. It is a flowchart of the operation determination process in a server and OS disk image combination. It is a system configuration diagram. It is an I / O device configuration table. It is an I / O device recognition table. System configuration. It is a processing flowchart of an I / O device configuration acquisition program. It is a driver management table. It is an I / O device configuration table. It is an I / O device recognition table. It is a flowchart of OS operation | movement determination processing. System configuration. It is a computer system structural example. It is an OS disk image operation determination table.

Explanation of symbols

101 to 103, 2: server, 111: OS disk image, 120: device recognition information table, 130, 1: management server, 131: server physical configuration acquisition unit, 132: device recognition information table management unit, 133: server physical configuration Investigation unit 134: OS operation estimation unit 135: OS operation determination unit 136: User interface 140: OS device recognition information transmission unit

Claims (16)

An operation management system that manages the association between an OS disk image of a computer system and one or more managed servers that include one or more managed servers and an OS disk image that runs on the managed servers,
Software control information for determining the OS device control behavior included in the OS disk image on the first managed server, and a physical device configuration for specifying the I / O device to which the software control information is applied Means for collecting I / O device recognition information comprising a set of information;
Means for collecting physical device configuration information indicating the configuration of the I / O device of the second managed server;
Means for loading the OS disk image onto the second managed server based on the I / O device recognition information and the physical device configuration information and determining whether or not the operation is possible when the OS disk image is executed. Operation management system. 2. The operation management system according to claim 1, wherein the means for determining whether the operation is possible or not is performed based on a result of successful execution of the confirmation procedure by executing a predetermined confirmation procedure. 3. The operation management system according to claim 2, wherein the means for determining whether or not the operation is possible includes means for storing a plurality of the predetermined confirmation procedures and recording which of the plurality of confirmation procedures is performed. The OS disk image associated with the first management target server is associated with the second management target server when it is determined that the operation is possible by the means for determining whether the operation is possible. The operation management system according to claim 1. The OS disk image associated with the first managed server is not associated with the second managed server when it is determined that the operation is impossible by the means for determining whether the operation is possible. The operation management system according to claim 1. An apparatus for detecting addition and deletion of the I / O device of the second managed server, and an OS disk image operation determination table for storing a determination result by the determination unit;
In response to the notification of one of addition and deletion of the I / O device, the determination unit is configured to send information to the second managed server based on the I / O device recognition information and the physical device configuration information. Load the OS disk image, determine whether the operation is possible or not, and store the determination result in an OS disk image operation determination table that stores the determination result;
When the OS disk image associated with the first managed server is associated with the second managed server, the OS disk image operates with reference to the determination result stored in the OS disk image operation determination table. The operation management system according to claim 1, wherein availability is determined. A server for loading and executing an OS disk image and an operation management server for managing the OS disk image in association with the server;
An I / O device recognition table for storing first information about I / O devices used by the OS disk image;
The I / O device configuration table that stores second information related to the I / O device included in the server, and the first information stored in the I / O device recognition table are stored in the I / O device configuration table. An operation management server comprising: a processing unit that associates the OS disk image with the server when included in the stored second information. The processing unit, when there is information that is not included in the second information stored in the I / O device configuration table in the first information stored in the I / O device recognition table, The first information including the changed information is changed within the changeable range in which the OS disk image can be executed by the server even if the information that is not included is changed. 8. The operation management server according to claim 7, wherein when included in the second information stored in the O device configuration table, the OS disk image is associated with the server. An operation management method in a management server that manages association between an OS disk image of a computer system and one or more managed servers, and an OS disk image that operates on the managed server, and the managed server,
Software control information for determining the OS device control behavior included in the OS disk image on the first managed server, and a physical device configuration for specifying the I / O device to which the software control information is applied Collect I / O device recognition information consisting of information sets,
Collect physical device configuration information indicating the configuration of the I / O device of the second managed server,
Operation management characterized in that, based on the I / O device recognition information and the physical device configuration information, the OS disk image is loaded on the second management target server and whether or not the operation is executed is determined. Method. The operation management method according to claim 9, wherein the means for determining whether or not the operation is possible performs a predetermined confirmation procedure and makes a determination based on a record of successful execution of the confirmation procedure. The operation management method according to claim 10, wherein the determination of whether or not the operation is possible includes a plurality of the predetermined confirmation procedures, and records which of the plurality of confirmation procedures is performed. The OS disk image associated with the first management target server is associated with the second management target server when it is determined that the operation is possible by determining whether the operation is possible. The operation management method according to claim 9. The OS disk image associated with the first managed server is not associated with the second managed server when it is determined that the operation is impossible by determining whether the operation is possible. The operation management method according to claim 9. An apparatus for detecting addition and deletion of the I / O device of the second managed server and an OS disk image operation determination table;
When one of the addition and deletion of the I / O device is notified, the result of determining whether or not the operation when executed is stored in the OS disk image operation determination table;
10. The operation management method according to claim 9, wherein the OS disk image is associated with the second management target server with reference to the determination result stored in the OS disk image operation determination table. An operation management method by a server that loads and executes an OS disk image and a management server that manages the OS disk image in association with the server,
The management server stores an I / O device recognition table that stores first information related to an I / O device used by the OS disk image, and an I / O that stores second information related to an I / O device included in the server. O device configuration table
Determining whether the first information stored in the I / O device recognition table is included in the second information stored in the I / O device configuration table;
An operation management method characterized by associating the OS disk image with the server when included as a result of the determination. When the management server includes information that is not included in the second information stored in the I / O device configuration table among the first information stored in the I / O device recognition table, The first information including the changed information is changed within the changeable range in which the OS disk image can be executed by the server even if the information that is not included is changed. 16. The operation management method according to claim 15, wherein when included in the second information stored in the O device configuration table, the OS disk image is associated with the server.

Images