WO2016125294A1 - Computer system, management device, and method - Google Patents

Abstract

A management device transmits a first update instruction for giving an instruction of update to a first device, which is one of a first storage controller and a first server computer out of a plurality of server computers. When receiving a first update completion notification that indicates a completion of the update based on the first update instruction, the management device transmits a second update instruction for giving an instruction of update to a second device, which is the other one of the first storage controller and the first server computer. When receiving a second update completion notification that indicates a completion of the update based on the second update instruction, the management device transmits, to the first device or the second device, a first link connection instruction for giving an instruction of connection of a first link between the first device and the second device.

Description

Computer system, management apparatus and method

The present invention relates to a technique for managing a computer system.

A technique for maintaining system availability in a system having an active standby server configuration is known (Patent Document 1). This technology can maintain system availability by taking over the operation of the secondary server while the primary server is stopped by updating the firmware installed in the primary server.

Also, there is a technology for maintaining the availability of a computer system in a computer system having a server device and a storage system.

The storage system has two storage controllers and storage devices connected to these storage controllers. A host interface device is mounted on the storage controller. This host interface device is, for example, a fiber channel card for connecting to a server apparatus. A certain interface is defined between the firmware operating on the host interface device and the control software operating on the storage controller and including the driver of the host interface device. Control software and firmware with different interfaces cannot be combined. Therefore, in order to maintain the availability of the computer system, it is desirable that the control software is updated when the storage system is operating, and the firmware is also updated at the same timing.

For example, in the above storage system, one storage controller is stopped, the firmware and control software of the internal host interface device are updated, and then one storage controller is restarted. Next, after the other storage controller is stopped and the firmware and control software of the internal host interface device are updated, some storage controllers are restarted. In this case, since at least one storage controller is operating, the firmware and control software of the host interface device mounted on all the storage controllers in the storage system can be updated without stopping the storage system.

US Pat. No. 8,813,551

Incidentally, in recent years, vertical integrated systems, which are computer systems that integrate hardware such as storage, servers, and network devices, software such as databases, applications, and middleware, and tools that centrally manage them, have attracted attention. In the vertical integrated system, a system in which hardware and software are integrated in advance in a form that matches the business needs of the vendor is provided to the customer through operation verification. This allows customers to quickly install a system with the best configuration for their business when they need it and get it up and running immediately.

The vertical integrated system can ensure high I / O (Input or Output) performance between the server and storage by closely linking the server device and the storage system. In the vertical integrated system, the server apparatus and the storage system may be connected with a high-speed interface such as, for example, PCI Express (registered trademark) (hereinafter, PCIe). The connection at this time is performed via an interface device such as Non-Transparent Bridge (NTB). In this case, in order to maintain the operability of the vertically integrated system, it is necessary to make the link between the server apparatus and the storage system redundant. For example, by providing a plurality of ports on the storage system side of the interface device, and connecting a plurality of storage controllers in the same storage system to the plurality of ports, the link between the interface device and the storage system can be made redundant. That is, the link between the server device and the storage system can be made redundant.

In the conventional storage system described above, the host interface device firmware and the control software for controlling the host interface device and the storage device have a one-to-one relationship. However, in the vertically integrated system, since the interface device is shared by a plurality of storage controllers, the device program that is the firmware of the interface device and the storage program that controls the interface device have a one-to-many relationship.

In such a situation, it is difficult to update the device program and the storage program that controls the device program while maintaining the availability of the vertically integrated system.

In order to solve the above problems, a computer system according to one aspect of the present invention includes a storage apparatus, a plurality of server computers connected to the storage apparatus, and a management apparatus connected to the storage apparatus and the plurality of server computers. Prepare. The storage apparatus includes a storage device and first and second storage controllers connected to the storage device. Each of the plurality of server computers is connected to the first and second storage controllers. Each of the plurality of server computers has an interface device that stores a device program that controls communication with the first and second storage controllers. The first and second storage controllers respectively store storage programs that control the storage device and the interface device. The management apparatus controls the update order of the device programs of the plurality of server computers and the storage programs of the first and second storage controllers. Each of the plurality of server computers disconnects the link between the first and second storage controllers when updating the device program. Each of the first and second storage controllers disconnects links with a plurality of server computers when updating the storage program. The management device transmits a first update instruction for instructing the update to a first device that is one of the first storage controller and the first server computer of the plurality of server computers. When the management apparatus receives the first update completion notification indicating the completion of the update based on the first update instruction, the management apparatus applies to the second apparatus that is the other of the first storage controller and the first server computer. The second update instruction for instructing the update is transmitted. When the management device receives the second update completion notification indicating the completion of the update based on the second update instruction, the management device transmits the first device or the second device between the first device and the second device. A first link connection instruction for instructing connection of the first link is transmitted.

According to one aspect of the present invention, it is possible to update the device program on the interface device that connects the server apparatus and the storage controller and the storage program on the storage controller that controls the interface device while maintaining the availability of the computer system.

It is a hardware block diagram of the computer system which concerns on a present Example. It is a figure which shows an example of the software configuration of the computer system which concerns on a present Example. An example of the firmware version management table 231 is shown. An example of the storage micro version management table 232 is shown. An example of the update target IO module list 233 is shown. An example of the server apparatus-controller connection management table 234 is shown. An example of the server apparatus-controller state management table 235 is shown. An example of IO module firmware version information 211 is shown. An example of the version management table 222 is shown. An example of the operation version management table 223 is shown. It is an example of the flowchart of an update process. It is an example of the flowchart of a pre-process. It is an example of the flowchart of a list-up process. It is an example of the flowchart of a micro update process. It is an example of the flowchart of a firmware update process. It is an example of the flowchart of a connection establishment process. It is an example of the flowchart of the initialization process of the server apparatus-controller state management table 235. It is a figure explaining the computer system of the basic redundant structure of a present Example. It is a figure explaining the procedure of an update process.

Hereinafter, the present embodiment will be described with reference to the drawings.

In the following description, information may be described in terms of “kkk table”, “kkk list”, and “kkk information”, but the information may be expressed in a data structure other than a table or a list. The “kkk table”, “kkk list”, and “kkk information” can be replaced with each other to indicate that they do not depend on the data structure.

In the following description, the process may be described using “program” as a subject. However, the program is executed by the processor, so that the determined process can be appropriately performed with storage resources (for example, memory) and / or Alternatively, since the processing is performed using a communication interface device (for example, a communication port), the subject of processing may be a processor. On the contrary, the processing whose subject is the processor can be interpreted as being executed by executing one or more programs. The processor is typically a microprocessor such as a CPU (Central Processing Unit), but may include a hardware circuit that executes a part of the processing (for example, encryption / decryption, compression / decompression). .

Further, in the following description, when a description is made without distinguishing the same type of element, a reference symbol is used, and when a description is made with a distinction between the same type of element, the element is replaced with the reference number. An assigned identifier (eg, at least one of a number and a sign) may be used.

FIG. 1 is a hardware configuration diagram of a computer system according to the present embodiment. The computer system includes one or more server devices 100, one or more shared storage systems 120, and a management device 140. The management device 140 is connected to the server device 100 via the network 150. The management device 140 is connected to the shared storage system 120 via the network 160. An example of the networks 150 and 160 is a WAN (Wide Area Network) or a LAN (Local Area Network), but is not limited thereto. The server apparatus 100 and the management apparatus 140, and the shared storage system 120 and the management apparatus 140 may be directly connected without going through a network. In the following description and drawings, the shared storage system 120 may be simply abbreviated as the storage system 120.

The server apparatus 100 includes a plurality of server modules 110 (0 to n). Therefore, the server apparatus 100 is a server system including a plurality of server modules. Each server module 110 is a physical computer (server computer) including a processor 111, a memory 112, an IO module 113, and a network interface (I / F) 114. The server module 110 may have other configurations such as a storage medium and an input / output device (not shown). These components inside the server module 110 are connected to each other via an internal path.

The network interface 114 is an interface for connecting to the management apparatus 140 and is a device. The IO module 113 is an interface device for connecting the server module 110 and a storage controller 130 described later. In the present embodiment, the connection between the server module 110 and the storage controller 130 described later (for example, the connection between the processor 111 and the IO module 113 and the connection between the IO module 113 and the storage controller 130) includes, for example, The PCIe connection standard established by PCI-SIG is used. Thereby, high-speed processing of the entire computer system can be realized. However, the connection standard is not limited to this.

The processor 111 executes a program stored in the memory 112. When the processor 111 executes the program stored in the memory 112, the function of the server module 110 is realized.

The memory 112 stores a program executed by the processor 111 and information necessary for executing the program. The memory 112 includes a work area used by the program.

The storage system 120 includes a plurality of storage controllers 130 and one or a plurality of storage media 121. Each storage controller 130 is connected to the storage medium 121. Each storage medium 121 has a storage area for storing data used by an application executed by each server module 110. The storage system 120 provides LU (Logical Unit) to the server apparatus 100 based on the storage medium 121. The storage medium 121 is, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive), but may be any device that can store data. A plurality of storage media 121 may constitute a RAID (redundant array of inexpensive disks) volume. In the following description and drawings, the storage system 120 may be simply abbreviated as the storage system 120, and the storage controller 130 may be simply abbreviated as the controller 130.

The controller 130 controls the storage system 120. The controller 130 includes a processor 131, a memory 132, a pass-through IO module 133, a network interface (I / F) 134, a storage interface (I / F) 135, and an inter-controller interface (I / F) 136. These components of the controller 130 are connected to each other via an internal path. In the following description, the pass-through IO module 133 may be simply referred to as a pass-through 133.

The processor 131 executes a program stored in the memory 132. The processor 131 executes a program stored in the memory 132, thereby realizing the functions of the storage system 120.

The memory 132 stores a program executed by the processor 131 and information necessary for executing the program. The memory 132 includes a work area used by the program.

The pass-through 133 is an interface device for mediating the connection between the IO module 113 and the controller 130. For example, the pass-through 133 includes a retimer for increasing the signal strength and does not interpret the signal. Therefore, from the controller 130 (specifically, a storage micro 220 described later), the pass-through 133 is not directly visible, and the IO module 113 appears to be connected to the controller 130.

The network I / F 134 is an interface for connecting to other devices via the network 160. The storage I / F 135 is an interface for connecting to the storage medium 121. The inter-controller I / F 136 is an interface for connecting the storage controllers.

The management device 140 manages each server module 110 and each storage system 120. The management apparatus 140 includes a processor 141, a memory 142, a network interface (I / F) 143, and a network interface (I / F) 144. Each component of the management apparatus 140 is connected to each other via an internal path.

The processor 141 executes a program stored in the memory 142. When the processor 141 executes the program stored in the memory 142, the function of the management device 140 is realized.

The memory 142 stores a program executed by the processor 141 and information necessary for executing the program. The memory 142 includes a work area used by the program.

The network I / F 143 is an interface for connecting to other devices via the network 150. The network I / F 144 is an interface for connecting to other devices via the network 160.

FIG. 2 is a diagram illustrating an example of a software configuration of the computer system according to the present embodiment. The software configuration of the server module 110 will be described. The server module 110 stores the OS 200 and one or more applications 201 operating on the OS 200 in its own memory 112. The application 201 is, for example, database software, a hypervisor, a virtual desktop infrastructure, or the like, but the type of the application 201 is not limited to these.

The OS 200 is control software that controls the entire server module 110. The OS 200 includes a server IO module driver 202 that is a driver for controlling the IO module 113. The application 201 operates on the OS 200. The OS 200 formats the LU provided by the storage system 120 into a predetermined file system. At this time, the OS 200 divides the LU into predetermined logical blocks and assigns an identification number to each logical block. The file system manages data composed of one or more block data as a file. Since the file system and the like included in the OS 200 are publicly known, description thereof will be omitted.

The server IO module driver 202 is a driver that controls the IO module 113 from the server side. Further, the server IO module driver 202 includes an interface with a firmware update management module 230 described later of the management apparatus 140.

The software configuration of the IO module 113 will be described. The IO module 113 has firmware (FW) 210 and is controlled by the FW 210. The FW 210 includes an interface with the server IO module driver 202 and an interface with an IO module driver 221 (described later) included in the controller 130. The FW 210 includes IO module firmware (FW) version information 211. In the following description and drawings, the IO module firmware version information 211 may be simply referred to as FW version information 211. The FW version information 211 is information for managing the version of the FW 210.

The software configuration of the controller 130 will be described. The controller 130 stores a storage micro 220 that is control software for controlling the storage controller 13 and the storage medium 121 in the memory 132. The storage micro 220 is executed by the processor 131.

The storage micro 220 generates a plurality of LUs by logically dividing a RAID volume, for example, and provides the generated plurality of LUs to the server module 110. The storage micro 220 also holds management information (not shown) indicating the correspondence between the LU and the storage medium 121.

The storage micro 220 includes an IO module driver 221. The IO module driver 221 holds a version management table 222 and an operation version management table 223.

The version management table 222 is a table for managing the version of the FW 210 of the IO module 113 that the storage micro 220 can handle.

The operation version management table 223 is a table for managing the version of the FW 210 of the IO module 113. There may be versions that are included in the version management table 222 but are not included in the operation version management table 223.

The software configuration of the management apparatus 140 will be described. The management device 140 stores the firmware update management module 230 in the memory 142. In the following description and drawings, the firmware update management module 230 may be simply referred to as a management module. The management module 230 is executed by the processor 141. The management module 230 controls the update timing of the FW 210 of the IO module and the storage micro.

The management module 230 has a firmware version management table 231, a storage micro version management table 232, an update target IO module list 233, a server device / controller connection management table 234, and a server device / controller state management table 235.

The management module 230 exchanges the server IO module driver 202 and the IO module driver 221 with the version of the FW 210, the progress of the update, and the like, and appropriately controls and manages the update order of the FW 210 and the storage micro 220 of the IO module 113.

FIG. 3 shows an example of the firmware version management table 231. The firmware version management table 231 is a table for managing the FW version for each IO module 113. The management apparatus 140 generates and updates the firmware version management table 231 by acquiring the version information of the FW of the IO module from the server apparatus managed by itself. Each entry of the firmware version management table 231 includes a server device number 2310, a server module number 2311, an IO module number 2312, and a version 2313.

The server device number 2310 and the server module number 2311 are fields for storing the identification number of the server device on which the IO module 113 is mounted and the identification number of the server module. The IO module number 2312 is a field for storing position information of a slot in which the IO module is mounted in the corresponding server module. The FW version 2313 is a field for storing the version of the FW 210 of the IO module. For example, the version of the FW 210 of the IO module # 0 mounted on the server module # 0 of the server device # 0 is 2.0.

FIG. 4 shows an example of the storage micro version management table 232. The storage micro version management table 232 is a table for managing the version of the storage micro 220 for each controller 130. The management apparatus 140 generates and updates the storage micro version management table 232 by acquiring storage micro version information from the storage system managed by the management apparatus 140. Each entry of the storage micro version management table 232 includes a storage system number 2320, a controller number 2321, and storage micro version information 2322.

Storage system number 2320 and controller number 2321 are fields for storing the identification number of storage system 120 storing storage micro 220 and the identification number of controller 130. The storage micro version information 2322 is a field for storing the version of the storage micro 220.

FIG. 5 shows an example of the update target IO module list 233. The update target IO module list 233 is a list indicating whether or not an update of the FW mounted on the IO module 113 is necessary. The update target IO module list 233 includes a server device number 2330, an IO module number 2331, and an update target 2332.

The server device number 2330 and the in-server device IO module number 2331 are fields in which position information of the server module 110 in which the IO module 113 is mounted is stored. The update target 2332 is a field in which a flag indicating whether the FW 210 of the IO module 113 needs to be updated is stored. The update target 2332 stores, for example, “1” indicating that update is necessary or “0” indicating that update is not necessary.

FIG. 6 shows an example of the server device / controller connection management table 234. The server device / controller connection management table 234 is a table for managing a connection relationship between the server device and the controller 130. Each entry of the server device / controller connection management table 234 includes a server device number 2340, a server module number 2341, an IO module number 2342, a connection destination controller (1) 2343, and a connection destination controller (2) 2344. The connection destination controller (1) 2343 includes a connection destination system number (1) 23430 and a connection destination controller number (1) 23431. The connection destination controller (2) 2344 includes a connection destination system number (2) 23440 and a connection destination controller number (2) 23441.

The server device number 2340 and the server module number 2341 are fields for storing the identification number of the server device 100 in which the IO module 113 is mounted and the identification number of the server module 110. The IO module number 2342 is a field for storing position information of the slot in which the IO module 113 is mounted in the corresponding server module 110. The connection destination controller (1) 2343 is a field related to one controller 130 connected to the IO module 113. Specifically, in each field of the connection destination system number (1) 23430 and the connection destination controller number (1) 23431, the identification number of the storage system 120 to which the IO module 113 is connected and the identification number of one controller 130 are stored. Are stored respectively. The connection destination controller (2) 2344 is a field related to the other controller 130 connected to the IO module 113. Specifically, in the fields of the connection destination system number (2) 23440 and the connection destination controller number (2) 23441, the identification number of the storage system 120 to which the IO module 113 is connected and the identification number of the other controller 130 are stored. Are stored respectively.

FIG. 7 shows an example of the state management table 235 between the server device and the controller. The server apparatus / controller state management table 235 is a table for managing a link establishment state between the server apparatus 100 and the controller 130. Each entry in the server device / controller state management table 235 includes a server device number 2350, a server module number 2351, an IO module number 2352, a controller (1) connection state 2353, and a controller (2) connection state 2354.

The server device number 2350 and the server module number 2351 are fields for storing the identification number of the server device 100 in which the IO module 113 is mounted and the identification number of the server module 110. The IO module number 2352 is a field for storing position information of the slot in which the IO module 113 is mounted in the corresponding server module 110. The controller (1) connection state 2353 is a field for storing the connection state between the IO module and the controller 130 of the connection destination controller (1) 2343 in the server device / controller connection management table 234. The controller (2) connection state 2354 is a field for storing the connection state between the IO module 113 and the controller 130 of the connection destination controller (2) 2344 in the server device / controller connection management table 234. In the controller (1) connection state 2353 and the controller (2) connection state 2354, for example, “connection” indicating that the link is established between the IO module 113 and the controller 130, and the link is established. “Disconnection” indicating that there is no connection, “blocking” indicating that a failure has occurred in the connection, and the like are stored.

FIG. 8 shows an example of the FW version information 211. FW version information 211 includes FW version 2110.

FIG. 9 shows an example of the version management table 222. The version management table 222 includes a corresponding FW version 2220 that is a version of the FW 210 that the storage micro 220 can support.

FIG. 10 shows an example of the operation version management table 223. The operation version management table 223 includes an operating FW version 2230 and a valid bit 2231. The operating FW version 2230 is a field for storing the version of the FW 210 acquired from the IO module 213. The valid bit 2231 is a field for storing a flag indicating whether or not the operating FW version 2230 is valid. For example, the valid bit 2231 is valid when it is “1” and invalid when it is “0”. When invalid, it indicates that the currently operating version of the FW is not compatible with the currently operating storage micro 220. In this case, the currently operating storage micro 220 can support the version of the FW 210 indicated by the version management table 222.

The operation of the computer system is described below.

FIG. 17 is an example of a flowchart of the initialization process of the server device / controller state management table 235. The initialization process may be performed when the computer system is constructed, or may be performed before an update process (FIG. 11) described later. This process is performed by the server IO module driver 202 of each server module 110. Hereinafter, as an example, processing performed by the server IO module driver 202 of an arbitrary server module will be described. Hereinafter, this server IO module driver is abbreviated as a server driver. In the following description, an IO module corresponding to this server driver is referred to as a connection module. Furthermore, in the following description, a storage system and a storage controller connected to the server module are referred to as a connection system and a connection controller.

The server driver acquires the identification numbers of the connection system and the connection controller, and notifies the management module 230 of the acquired identification numbers (S700).

The storage micro 220 of the connection controller acquires the identification numbers of the server device 100 and the server module 110 having the connection module and notifies the management module 230 (S701).

The management module 230 creates a server device / controller state management table 235 based on the identification number of each device notified from the server driver and the storage controller storage micro 220 (S702).

After the initialization process, the management module 230 may display the server device / controller state management table 235 on an output device (not shown) connected to itself. Thereby, the user can check the table 235 against the actual connection state.

The processor 141 of the management device 140 performs update processing according to the management module 230 stored in the memory 142. Here, an update process in a computer system of a specific example will be described. FIG. 18 is a diagram for explaining a connection state between the processors 111 and IO modules 113 in the two server modules 110 and the two controllers 130 in the computer system of the specific example.

Servers # 0 and # 1 are processors 111 in the server module 110. The IO module # 0 is connected to the server # 0 and to the controllers # 0 and # 1. The IO module # 1 is connected to the server # 1 and to the controllers # 0 and # 1.

In the following description, a storage micro that is mounted on the controllers # 0 and # 1 and is an update target may be referred to as a target micro. Further, the controllers # 0 and # 1 may be referred to as target controllers, and the storage system 120 equipped with the target controller may be referred to as a target system. Furthermore, IO modules # 0 and # 1 are each referred to as a target IO module, and an FW that is mounted on the target IO module and is an object of update may be referred to as a target FW. Furthermore, the servers # 0 and # 1 may be referred to as target servers. When the controller 130 updates the storage micro, the controller 130 disconnects the link between itself and the IO module connected thereto. For example, when the target controller updates the target micro, the target controller disconnects the link with the target IO module connected to itself.

Also, when the server updates the FW of the IO module 113 connected to itself, the server disconnects the link between itself and the controller 130 connected to itself. For example, when the server # 0 updates the FW of the IO module # 0 connected to the server # 0, the server # 0 disconnects the link between the IO module # 0 and the controllers # 0 and # 1. For example, when the server # 1 updates the FW of the IO module # 1 connected to itself, the server # 1 disconnects the link between the IO module # 1 and the controllers # 0 and # 1.

FIG. 11 is an example of a flowchart of the update process.

The update process is a process for updating the target micro and the target FW in cooperation with each other. The update process is started when the management module 230 receives an update instruction.

The management module 230 receives the update instruction and performs pre-processing (S100). The pre-processing is processing for determining whether update processing is necessary. Details of this step will be described later. When the management module 230 determines that the update process is not necessary, the management module 230 ends the update process without performing the following steps.

The management module 230 performs a list-up process in which the target IO module is listed and registered in the update target IO module list 233 (S101). In this embodiment, for example, IO modules # 0 and # 1 are listed. Details of this processing will be described later.

The management module 230 performs a micro update process for updating the target micro 220 (S102). Details of this processing will be described later. Here, for example, the target micro installed in the target controller # 0 is updated.

The management module 230 determines whether the firmware (FW) update process for updating the target FW is completed for all target IO modules (S103). Specifically, for example, the management module 230 corresponds to the server device number 2330 and the IO module number 2331 of all the target IO modules listed (IO modules # 0 and # 1) in the update target IO module list 233. It is determined whether the update target 2332 to be updated is “0”. If the update target 2332 of all target IO modules is “0” (Yes in S103), it means that all target FWs have been updated, and the management module 230 advances the process to S107. On the other hand, if the update target 2332 of at least one target IO module is “1” (No in S103), it means that there is a target FW that has not yet been updated, and the management module 230 advances the process to S104. .

The management module 230 selects one target server connected to one target IO module whose target FW is not updated based on the update target IO module list 233, and selects the selected target server (hereinafter referred to as a selection target server). ) Is instructed to transfer the job running on the selection target server to another target server (S104).

The management module 230 performs FW update processing for updating the target FW on the target IO module connected to the selection target server (S105). Details of this processing will be described later. Here, for example, the FW mounted on one of the IO modules # 0 and # 1 is updated.

The management module 230 performs connection establishment processing for connecting a link between the target controller on which the updated target micro is mounted and the target IO module on which the updated target FW is mounted (S106). Details of this processing will be described later. After S106, the management module 230 returns the process to S103. Thereby, the firmware update process and the connection establishment process can be sequentially executed for all the target FWs.

The management module 230 performs a micro update process for updating the target micro (S107). Details of this processing will be described later. Here, for example, the target micro installed in the target controller # 1 is updated.

The management module 230 performs connection establishment processing for connecting a link between the target controller on which the updated target micro is mounted and the target IO module on which the updated target FW is mounted (S108). Details of this processing will be described later.

With the above update processing, all of the target FW and target micro can be updated while maintaining the availability of the computer system, that is, while maintaining the state where the server module of any target server can access the storage device. In addition, an update process for updating all target FWs and target micros in cooperation with each other can be executed with only one update instruction input by the user.

Specifically, in the update process, the following steps are performed according to an instruction from the management module 230.
(1) Of the two target controllers, the micro-update process (S102) is performed for one target controller (for example, target controller # 0).
(2) The FW update process (S105) is performed for one target IO module (for example, target IO module # 0) among a plurality of target IO modules (for example, target IO modules # 0 and # 1).
(3) A connection establishment process (S106) is performed.
In (1), all the links between the target controller # 0 and all target IO modules (for example, target IO modules # 0, # 1) connected to the target controller # 0 are disconnected, and the target controller # 0 The target micro is updated, the link between the target IO module # 0 and the target controller # 1 is disconnected in (2), and the target FW of the target IO module # 0 is updated. In (3), the target IO module is updated. The link between # 0 and the target controller # 0 is connected. That is, after the micro update process of one target controller # 0 is performed, the FW update process of one target IO module # 0 is performed, and the connection establishment process of these target controller # 0 and target IO module # 0 continues. Done. Thereby, the other target IO module # 1 can continue to access the storage device via the other target controller # 1. Therefore, the availability of the computer system can be maintained. As a result, for one target IO module # 0, there is a period in which the link between both target controllers # 0 and # 1 is disconnected and access to the storage device of the target server # 0 is blocked. It is suppressed only when updating its own target FW. The link newly established in (3) is a link between the target controller and the target IO module based on the new version of the target micro and target FW that have been updated.

Further, according to the instruction from the management module 230, first, the update process of the first controller # 0 is performed, the FW update process of all the target IO modules (S105), all the target IO modules, and the one controller # 0. After the connection establishment process (S106) is completed, the update process of the other controller # 1 is performed. As a result, all the target servers # 0 and # 1 can continue to access the storage device via any of the target controllers when the FW update process is not performed for the target IO modules # 0 and # 1.

Further, after the link between one target controller # 0 and one target IO module # 0 is connected according to an instruction from the management module 230, update processing (S105) and connection establishment of the other target IO module # 1 Processing (S106) is performed sequentially. As a result, each link between the other target IO module # 1 and the target controllers # 0 and # 1 is disconnected and access to the storage device of the target server # 1 is blocked. Suppressed only when updating FW.

In this specific example, the target server is limited to two server modules, but there may be three or more target servers. In the update process of the present embodiment, the management module 230 first instructs the update process of the first controller # 0, then instructs the FW update process (S105) of all target servers, and then all The connection establishment process (S106) between the target server and one controller # 0 is instructed, but the present invention is not limited to this. For example, instead of the micro update process of S102, the management module 230 may select one target server and instruct the selection target server to perform the FW update process (S105) of the target IO module. In this case, after the FW update process of the selection target server, the micro update process is instructed to one target controller, and after the completion notification indicating the completion of the micro update is received, the selection target server or one target controller is notified. The connection establishment process (S106) for connecting the link between the selection target server and one target controller may be indicated. After this connection establishment process, the management module 230 may instruct the remaining target server and target controller in the FW update process and the micro update process in any way.

Furthermore, when updating the target FW, the job on the target server having the target IO is migrated to another target server, so that the application running on the target server can access the storage device while maintaining the target FW. And the target micro can be updated.

FIG. 12 is an example of a flowchart of pre-processing. The pre-processing is the processing of S100 in FIG.

The management module 230 receives the update instruction input by the user (S200). The update instruction is an instruction input from the input device connected to the management apparatus 140 by the user. For example, the user inputs one or more of the identification number of the computer system to be updated, the identification number of the IO module 113 to be updated, and the identification number of the controller 130 to be updated to the input device. To do. For example, when the update instruction includes the identification number of the computer system, the management module 230 refers to the configuration information of the computer system (not shown) stored in the memory 142 of the management apparatus 140 and determines the target IO module from the identification number of the computer system. And the target controller may be specified. For example, when the update instruction includes an identification number of one of the target IO module and the target controller, either one of the identification numbers may be specified. The update instruction may include an updated version of the FW and storage micro that are to be updated.

The management module 230 checks whether the storage micro 220 and the FW 210 included in the update instruction need to be updated in cooperation with the target micro and the target FW (S201). Specifically, for example, the management module 230 determines the version of the currently operating FW 210 and storage micro 220 for the IO module 113 and the controller 130 based on the update instruction based on the firmware version management table 231 and the storage micro version management table 232. Get each. Then, the management module 230 checks whether it is necessary to update both the acquired FW 210 and the storage micro 220 and to perform these updates at the same timing. For example, even if both the currently operating FW 210 and the storage micro 220 can be updated, if the currently operating storage micro 220 can support the updated new version of the FW 210, only the currently operating FW 210 is used. Update it. For this reason, in such a case, it is not necessary to update both in a series of update processes.

If the target micro and the target FW need to be updated, the management module 230 advances the process to S202. When these coordinated update processes are not necessary, the management module 230 notifies the user that these coordinated update processes are not necessary, and ends the preliminary process and the update process. In this case, the user updates the target micro and the target FW one by one as necessary. Further, for example, regarding the notification to the user, the management module 230 may display the fact on the screen of the output device connected to the management device 140. The same applies to the following.

The management module 230 may acquire the version of the target micro and the target FW from the target storage system and the target server without using the firmware version management table 231 and the storage micro version management table 232, respectively.

The management module 230 checks whether the updated FW and storage micro version are compatible for the IO module 113 and the controller 130 based on the update instruction (S202). If there is compatibility, the management module 230 advances the process to S203. If there is no compatibility, the management module 230 notifies the user that the update is not possible, and ends the pre-processing and the update processing.

The management module 230 checks whether a failure of the computer system has occurred (S203). Specifically, for example, the management module 230 checks whether there is a blocked controller 130 based on the server device / controller state management table 235. If a failure has occurred, the management module 230 gives notice to the user that update processing cannot be performed because failure recovery is prioritized, and ends the pre-processing and update processing.

By pre-processing, it is possible to determine whether or not update processing in cooperation between the target micro and the target FW is necessary for the FW 210 and the storage micro 220 on the IO module 113 and the controller 130 based on the update instruction.

FIG. 13 is an example of a flowchart of the listing process. The list-up process is the process of S101 in FIG.

The management module 230 lists the target IO modules based on the server device / controller connection management table 234 (S300).

The management module 230 checks the connection state between the listed target IO module and the target controller (S301). Specifically, for example, the management module 230 determines, based on the server device / controller state management table 235, between all the target IO modules listed between the controllers 130 physically connected for each target IO module. Check the link connection status.

The management module 230 determines the target IO module, registers the target IO module, and creates the update target IO module list 233 (S302). For example, the management module 230 selects an IO module whose connection state with a physically connected controller from among the listed IO modules 113 is “connected” based on the server device / controller state management table 235. The module is registered in the update target IO module list 233 as a module.

By the list-up process, the IO module 113 whose connection state with the controller is “connected” can be determined as the target IO module to be subjected to the update process. Further, the target controller is also determined by determining the target IO module. This is because the IO module 113 disconnected from the controller 130 can individually update the FW 210 without using the update process.

FIG. 14 is an example of a flowchart of the micro update process. The micro update process is the process of S102 and S107 in FIG. For example, in S102, the controller # 0 is the target controller and the target micro on the controller # 0 is updated. In S107, the controller # 1 is the target controller and the target micro on the controller # 1 is updated.

The management module 230 instructs the target micro of any target controller to update the target micro (S400).

The target micro receives the update instruction. Based on the update instruction, the target micro disconnects all the connection states of the target IO modules physically connected to its target controller (S401).

Specifically, for example, the target micro transmits a stop request to stop the I / O transmitted from the target server to the target IO module. The target IO module switches so that I / O from the target server is transmitted to the target micro of the target controller different from the transmission source of the stop request. Then, after transmitting all the I / O before switching stored in its own queue, the target IO module notifies the target of the stop request transmission source that the transmission of the I / O is completed. The target micro receives the notification and disconnects the connection state between itself and the target IO module to which the stop request is transmitted. Thereby, the I / O transmitted to the target IO module can be transmitted without leaving the target controller.

The target micro updates itself (S402). Updating the target micro may follow conventional procedures. For example, the management device 140 sends the update program of the target micro stored in the disk in the management device to the target micro via the network 160, and the target micro stores the received update program in the memory 132, and then Update itself by restarting. Note that the target controller is temporarily suspended while the target micro is being updated.

The target micro updates the version management table 222 based on its version after the update (S403).

The target micro updates the valid bit 2231 of the operation version management table 223 to “0”. (S404).

The target micro restarts itself (S405). After the restart, the target micro transmits an update completion notification of the target micro to the management module 230. Here, the target micro cannot reconnect its own target controller to the target IO module disconnected in S401. This is because the target FW is not yet compatible with the target micro because the target FW has not yet been updated.

The management module 230 receives an update completion notification. Then, the management module 230 updates the server device / controller state table 235 and the storage micro version management table 232 (S406, 407), and ends the micro update process.

The target micro of the target controller can be updated by the micro update process. In addition, the management module 230 can update the various tables based on the notification from the target controller, thereby grasping the update of the target micro and the connection state of the target controller.

Here, the micro update process in S102 and S107 of FIG. 11 has been described. However, in S107, unlike S102, there may be no target IO module connected to the target controller on which the target micro operates. In this case, the disconnection of the link between the target IO module and the target controller (S401) and the update of the server device / controller state management table 235 (S406) are not performed.

FIG. 15 is an example of a flowchart of the FW update process. The FW update process is the process of S105 in FIG.

The management module 230 refers to the update target IO module list 233 and transmits an FW update instruction to update the target FW whose update target 2332 is “1” to the target server (S500). Here, the FW that is the target of the FW update instruction is the target FW on the target IO module that is physically connected to the target controller on which the micro update process has been performed and is in a disconnected state.

The server driver of the target server (hereinafter referred to as the target server driver) receives the FW update instruction, and disconnects the link between the target IO module and the target controller included in the instruction (S501). Note that the target server driver may disconnect the link between the target server and the target IO module as necessary.

The target driver performs target FW update (S502). The update of the target FW may be a procedure for updating the FW in the conventional IO module.

When the link between the target server and the target IO module is disconnected, the target server driver establishes the link (S503). Then, the target server driver transmits a completion notification indicating that the update of the target FW of the target IO module is completed to the management module 230.

The management module 230 receives a completion notification. Then, the management module 230 updates the firmware version management table 231 and the update target IO module list 233 based on the completion notification (S504, 505), and ends the FW update process.

The target FW can be updated to a version compatible with the updated target micro by the FW update process. When the target server driver needs to be updated in accordance with the update of the target FW, the target server driver can update the target server driver in accordance with the update timing of the target FW.

FIG. 16 is an example of a flowchart of connection establishment processing. The connection establishment process is the process of S106 and S108 in FIG. For example, in S106, a link between the controller # 0 and the IO module # 0 or a link between the controller # 0 and the IO module # 1 is connected. In S108, the controller # 1 and the IO module # 0 are connected. And # 1 are connected.

The management module 230 instructs the target server driver to connect the target IO module and the target controller (S600). Specifically, for example, the management module 230 is based on the update target IO module list 233 and the server device / controller state management table 235, the update target 2332 is “0”, and the connection state 2353 with the target controller. (Or 2354) transmits a connection instruction between the target IO module and the target controller in the “disconnected” state to the target server.

The target server receives the connection instruction and passes the connection instruction to the server IO module driver 202 corresponding to the target IO module. Based on the connection instruction, the server IO module driver 202 instructs the target IO module to reconnect to the target controller in the disconnected state. The target IO module transmits a connection request to the target controller based on the reconnection instruction (S601). The target controller receives the connection request and passes the connection request to the target micro.

The target micro acquires the FW version information 211 from the target IO module that is the source of the connection request (S602). Thereby, the target controller can acquire the version of the target FW currently operating on the target IO module in the disconnected state.

The target micro determines whether or not the operation version management table 223 valid bit 2231 is “1” (S603). If the valid bit 2231 is “0” (No in S603), it means that the operation version management table 223 is not valid, and the target micro advances the process to S608.

On the other hand, when the valid bit 2231 is “1” (Yes in S603), it means that the operation version management table 223 is valid, so the operating FW version 2230 and the version of the target FW acquired in S602 match. It is determined whether or not to perform (S604).

If it matches the acquired version (No in S604), the target micro establishes a connection between the target controller and the target IO module (S605). Then, the target micro transmits a completion notification indicating that the connection has been completed to the management module 230. The management module 230 receives the completion notification, updates the server-controller / controller state management table 235 (S606), and ends the connection establishment process.

On the other hand, if it does not match the acquired version (No in S604), the target micro notifies the management module 230 that the connection between the target controller and the target IO module is impossible (S607). The establishment process is terminated. When receiving the notification, the management module 230 may notify the user through the output device that the connection between the target controller and the target IO module is impossible.

In S608, the target micro determines whether or not the version of the target FW acquired in S602 is included in the corresponding FW version 2220 of the version management table 222. If the acquired version is included (Yes in S608), the target micro determines the version of the target FW corresponding to itself as the acquired version. Then, the target micro sets the acquired version in the operating FW version 2230 of the operation version management table 223, and sets the valid bit 2231 to “1” (S609). Then, the target micro establishes a connection between the target controller and the target IO module (S605), and transmits a connection completion notification to the management module 230. The management module 230 receives the completion notification, updates the server-controller / controller state management table 235 (S606), and ends the connection establishment process.

On the other hand, when the acquired version is not included (No in S608), the target micro notifies the management module 230 that the connection between the target controller and the target IO module is impossible (S607). Then, the connection establishment process is terminated.

In the connection establishment process, based on an instruction from the management module 230, it can be confirmed whether or not the target controller can connect to the target IO module. As a result, the target IO module on which the updated FW operates can be connected only to the target controllers that can be connected to each other. That is, the target IO module is not connected to the target controller on which the target micro that does not correspond to the target FW operates, but is connected only to the target controller on which the target micro corresponding to the target FW operates.

Also, the target micro manages the version of FW that can be handled by itself. Thereby, by acquiring the version of the updated target FW from the target IO, it is possible to determine whether or not the target micro can connect the IO module to itself.

When the target IO module and the target controller are connected, the management module 230 can manage the connection state. When the target IO module and the target controller cannot be connected, the fact can be notified to the user via the management module 230.

In this case, the connection establishment process is started when the management module 230 transmits a connection instruction between the target IO module and the target controller to the target server driver of the target server. However, the connection establishment process may be performed in any way. For example, the management module 230 may specify a target IO module as a connection destination for the target micro of the target controller.

Although the connection establishment process in S106 of FIG. 11 has been described here, the connection establishment process in S108 of FIG. 11 is basically the same. However, in S106, one target IO module issued a reconnection request to the target controller. However, in S108, all IO modules 113 that updated the target FW issued reconnection requests to the target controller. You may make it take out. In this case, the already established link between the IO module 113 and the target controller is processed while being connected.

Here, the procedure of the update process in the specific example computer system will be briefly described. FIG. 19 is a diagram for explaining the procedure of the update process.

(1) is the initial state. In the description, the link between the IO module # 0 in the server # 0 and the controller # 0 is the first link, the link between the IO module # 1 in the server # 1 and the controller # 0 is the second link, The link between the IO module # 0 controller # 1 in the server # 0 is the third link, and the link between the IO module # 1 of the server # 1 and the controller # 1 is the fourth link.

The management module 230 performs a first micro-up process after the pre-process (S100) and the list-up process (S101) (S102).

In the first micro-up process, the management module 230 stops (2) the controller # 0 and disconnects the first and second links and updates the controller # 0 based on the server device controller pipe state management table 235 as an update instruction. An instruction to update (3) the target micro is transmitted to the controller # 0. Controller # 0 performs (2) and (3) based on the update instruction.

The management module 230 performs a first firmware update process via S103 and S104 (S105).

In the first firmware update process, the management module 230 stops (4) the server # 0 and disconnects the third link as a firmware update instruction on the basis of the server device controller pipe state management table 235, and targets the IO module # 0. An instruction to update the FW (5) and restart the server # 0 (6) is transmitted to the server # 0. The server # 0 performs (4) to (6) based on the update instruction, and transmits an update completion notification to the management module 230.

The management module 230 transmits a first link connection instruction for connecting the first link to the target server module of the server # 0. The target server module transmits a connection instruction according to the first link connection instruction to the controller # 0. Controller # 0 performs connection establishment processing in response to the instruction (S106).

Thereby, the target micro of controller # 0 in the specific example computer system can be updated in a state where at least one of the first to fourth links is connected. Therefore, at least one of the servers # 0 and # 1 can access the storage device, that is, the target micro can be updated while maintaining the availability of the computer system.

The management module 230 performs the second firmware update process through S103 and S104 (S105).

In the second firmware update process, the management module 230 stops (7) server # 1 and disconnects the fourth link as a firmware update instruction based on the server device controller pipe state management table 235, and targets the IO module # 1. An instruction to update (8) the FW and restart the server # 1 (9) is transmitted to the server # 1. The server # 1 performs (7) to (9) based on the update instruction, and transmits an update completion notification to the management module 230.

The management module 230 transmits a second link connection instruction for connecting the second link to the target server module of the server # 1. The target server module transmits a connection instruction according to the second link connection instruction to the controller # 0. Controller # 0 performs connection establishment processing for the second link in response to the instruction (S106).

This makes it possible to update the target micro of the IO module # 0 in the specific example computer system with at least one of the first to fourth links connected. Therefore, the target FW can be updated while maintaining the state in which the application can access the storage device, that is, the availability of the computer system.

The management module 230 performs a second micro-up process (S107).

In the second micro-up process, the management module 230 instructs to stop (10) the controller # 1 and update (11) the target micro of the controller # 0 based on the server device controller pipe state management table 235 as an update instruction. Is transmitted to the controller # 1. The controller # 1 performs (11) based on the update instruction, and transmits an update completion notification to the management module 230.

The management module 230 transmits a third connection instruction for connecting the third and fourth links to the target server module of the server # 0 or the server # 1. The target server module transmits a connection instruction according to the third link connection instruction to the controller # 1. In response to the instruction, the controller # 1 performs connection establishment processing for the third and fourth links (S108).

Thereby, the target FW of the IO module # 1 and the target micro of the controller # 1 in the specific example computer system can be updated in a state where at least one of the first to fourth links is connected. Therefore, the target micro and the target FW can be updated while maintaining the state in which the application can access the storage device, that is, the availability of the computer system. In addition, a series of update processes for updating all of the target FW and the target micro can be executed with only one update instruction input by the user.

In the present embodiment, the management module 230 transmits the first to third link connection instructions to the target server module of the target server, but may transmit it to the target micro of the target controller.

The various software illustrated in the present embodiment can be stored in various recording media (for example, non-temporary storage media) such as electromagnetic, electronic, and optical, and through a communication network such as the Internet. It can be downloaded to a computer.

In this embodiment, the update process is performed by the management module 230 stored in the management apparatus 140. However, what if the computer system has a function realized by the processor executing the management module 230? It may be a simple configuration. For example, a part or all of the management module 230 may be stored in a device different from the management device 140 and performed by another processor. Further, in this embodiment, an example using software control of the management module 230 has been described, but a part thereof can be realized by hardware.

The server program corresponds to the server IO module driver 202 and the like, the device program corresponds to the firmware 220 and the like, and the storage program corresponds to the storage micro 220 and the like. The link information corresponds to the server device / controller state management table and the like, and the corresponding version information corresponds to the operation version management table 223 and the like.

Although the present invention has been described in detail with reference to the accompanying drawings, the present invention is not limited to such specific configurations, and various modifications and equivalents within the spirit of the appended claims Includes configuration.

100 Server device 110 Server module 113 IO module 120 Shared storage system 130 Storage controller 140 Management device 200 OS
201 Application 202 Server IO Module Driver 210 Firmware 211 IO Module Firmware Version Information 220 Storage Micro 221 Storage IO Module Driver 222 Version Management Table 223 Operation Version Management Table 230 Firmware Update Management Module 231 IO Module Firmware Version Management Table 232 Storage Micro Version Management Table 233 Update target IO module list 234 Server device / controller connection management table 235 Server device / controller state management table

Claims (15)

1. A storage device;
   A plurality of server computers connected to the storage device;
   A management device connected to the storage device and the plurality of server computers,
   The storage device
   A storage device;
   First and second storage controllers connected to the storage device,
   Each of the plurality of server computers is connected to the first and second storage controllers,
   Each of the plurality of server computers has an interface device that stores a device program for controlling communication with the first and second storage controllers,
   The first and second storage controllers respectively store storage programs for controlling the storage device and the interface device;
   The management device controls the update order of the device programs of the plurality of server computers and the storage programs of the first and second storage controllers,
   Each of the plurality of server computers disconnects the link between the first and second storage controllers when updating the device program,
   Each of the first and second storage controllers disconnects the link with the plurality of server computers when updating the storage program,
   The management device
   (*) A first update instruction for instructing the update is transmitted to the first device that is one of the first storage controller and the first server computer of the plurality of server computers.
   (*) When the first update completion notification indicating completion of the update based on the first update instruction is received, for the second device that is either the first storage controller or the first server computer, Sending a second update instruction to instruct the update;
   (*) When the second update completion notification indicating completion of the update based on the second update instruction is received, the first device or the second device is notified of the second update between the first device and the second device. Transmitting a first link connection instruction instructing connection of one link;
   Computer system.
2. The computer system according to claim 1,
   The first device is the first storage controller;
   The second device is the first server computer;
   Computer system.
3. The computer system according to claim 2,
   The management device
   (*) When the first link connection completion notification based on the first link connection instruction is received, a third update instruction for instructing the update is transmitted to the second server computer among the plurality of server computers. And
   (*) When the third update completion notification indicating completion of the update based on the third update instruction is received, the second server computer and the first storage controller are sent to the second server computer or the first storage controller. Transmitting a second link connection instruction for instructing connection of the second link between the storage controllers;
   Computer system.
4. The computer system according to claim 3,
   The management device
   (*) When the second link connection completion notification based on the second link connection instruction is received, a fourth update instruction for instructing the update is transmitted to the second storage controller;
   (*) When the fourth update completion notification indicating completion of the update based on the fourth update instruction is received, either the first or second server computer or the second storage controller Transmitting a third link connection instruction for instructing a connection between a third link between the first server computer and the second storage controller and a fourth link between the second server computer and the second storage controller;
   Computer system.
5. A computer system according to claim 4, wherein
   The management device is
   Storing link information indicating a connection state of a link between each of the plurality of server computers and the first and second storage controllers;
   In response to the first update completion notification and the second update completion notification, the link information is updated,
   When the first server computer receives the first link connection instruction, the first server computer transmits the first link connection request to the first storage controller in response to the first link connection instruction. ,
   The first storage controller is
   In response to the first link connection request, the first link is connected,
   Sending the first link connection notification to the management device;
   A computer system in which the management device updates the link information in response to the first link connection notification.
6. The computer system according to claim 5,
   The first server computer stores an updated first version of the first device program of the first server computer;
   The first storage controller acquires and stores the first version from the first server computer;
   Corresponding version information indicating a version of a device program that can correspond to an updated version of the first storage program of the first storage controller is stored, and when the first storage controller receives the first link connection request Determining whether the first version is valid in response to the first link connection request;
   When the first version is invalid, it is determined whether the second version of the first device program included in the first link connection request is included in the corresponding version information;
   A computer system for connecting the first link when the second version is included in the corresponding version information.
7. A computer system according to claim 6, wherein
   The first storage controller is
   A computer system that transmits a notification to the management apparatus that the first link cannot be connected when the second version is not included in the corresponding version information.
8. The computer system according to claim 5,
   When the second server computer receives the second link connection instruction, the second server computer transmits a second link connection request to the first storage controller in response to the second link connection instruction.
   The first storage controller is
   In response to the second link connection request, connect the second link,
   Sending the second link connection completion notification to the management device;
   The management apparatus updates the link information in response to the second link connection completion notification.
9. A computer system according to claim 8, wherein
   Each of the first and second server computers, when receiving the third link connection instruction, transmits a third link connection request to the second storage controller in response to the third link connection instruction,
   The second storage controller is
   In response to the third link connection request, the third and fourth links are connected,
   A third link connection completion notification indicating completion of connection of the third and fourth links is transmitted to the management device;
   The management device is a computer system that updates the link information in response to the third link connection completion notification.
10. A computer system according to claim 9, wherein
    The first storage controller is
    When the first update instruction is received, a stop request for stopping I / O (Input or Output) transmitted from the first interface device of the first server computer to the first storage controller is issued to the first interface. Send it to the device,
    The first interface device is
    Switching the I / O to be transmitted to the second storage controller via the second link;
    After transmitting all the I / O before switching to the first storage controller, a completion notification indicating completion of transmission of the I / O is sent to the first storage controller,
    The first storage controller receives the completion notification and disconnects the first link;
    Computer system.
11. The computer system according to claim 2,
    Each of the plurality of server computers includes a memory and a processor connected to the memory and the interface device.
    The memory stores a server program,
    The processor controls the interface device according to the server program;
    A first processor of the first server;
    When receiving the second update instruction, the server link between the first interface device and the first processor is disconnected;
    A computer system that updates the first device program, connects the server link, and transmits the second update completion notification to the management apparatus.
12. The computer system according to claim 11,
    Each of the plurality of server computers, between each internal processor and interface device, between each interface device and the first storage controller, and between each interface device and the second storage controller is PCI Express. Connected computer system.
13. A computer system according to claim 4, wherein
    When the second server computer is two or more server computers,
    The management device
    Select any one of the second server computers as a selected server computer in order,
    Transmitting the third update instruction and the second link connection instruction to the selected server computer;
    Computer system.
14. A management device connected to a storage device having a storage device, first and second storage controllers, and a plurality of server computers connected to the storage device,
    Management memory,
    A management processor connected to the management memory;
    With
    The storage apparatus includes a storage device, and first and second storage controllers connected to the storage device,
    Each of the plurality of server computers has an interface device that stores a device program for controlling communication with the first and second storage controllers,
    The first and second storage controllers respectively store storage programs for controlling the storage device and the interface device;
    The management processor controls the update order of the device programs of the plurality of server computers and the storage programs of the first and second storage controllers,
    Each of the plurality of server computers disconnects the link between the first and second storage controllers when updating the device program,
    Each of the first and second storage controllers disconnects the link with the plurality of server computers when updating the storage program,
    The management processor is
    (*) A first update instruction for instructing the update is transmitted to the first device that is one of the first storage controller and the first server computer of the plurality of server computers.
    (*) When the first update completion notification indicating completion of the update based on the first update instruction is received, for the second device that is either the first storage controller or the first server computer, Sending a second update instruction to instruct the update;
    (*) When the second update completion notification indicating completion of the update based on the second update instruction is received, the first device or the second device is notified of the second update between the first device and the second device. Transmitting a first link connection instruction instructing connection of one link;
    Management device.
15. A method of controlling a storage device and a plurality of server computers connected to the storage device,
    The storage apparatus includes a storage device and first and second storage controllers connected to the storage device, and each of a plurality of server computers is connected to the first and second storage controllers. Each of the server computers has an interface device that stores a device program for controlling communication with the first and second storage controllers,
    Storing storage programs for controlling the storage device and the interface device, respectively, using the first and second storage controllers;
    Using the management device connected to the storage device and the plurality of server computers, the update order of the device programs of the plurality of server computers and the storage programs of the first and second storage controllers is controlled. And
    When updating the device program using each of the plurality of server computers, the link between the first and second storage controllers is disconnected,
    When updating the storage program using each of the first and second storage controllers, the link between the plurality of server computers is disconnected,
    Using the management device,
    (*) A first update instruction that instructs the update is transmitted to the first device that is one of the first storage controller and the first server computer of the plurality of server computers. (*) When the first update completion notification indicating completion of the update based on the first update instruction is received, the update is instructed to the second device that is the other of the first storage controller and the first server computer Send a second update instruction,
    (*) When the second update completion notification indicating completion of the update based on the second update instruction is received, the first between the first device and the second device with respect to the first device or the second device. Transmitting a first link connection instruction indicating a link connection.
    
    

Images