JP5921734B2 - Storage system, storage system management method, and computer system - Google Patents

Description

  The present invention relates to a storage system, a storage system management method, and a computer system that perform input / output processing for a plurality of logical storage devices to which at least some storage areas of the plurality of storage devices are allocated.

  In a storage system, it is possible to manage a plurality of logical storage devices that use a part of storage areas of a plurality of storage apparatuses as their storage areas. In the storage system, the logical storage device is provided so as to be recognizable to the host computer, and data input / output processing to the logical storage device by the host computer can be executed.

  In the storage system, when an input / output request is received from the host computer, the microprocessor provided in the storage system performs data write processing to the storage device, data read processing from the storage device, etc. in accordance with the input / output request. I / O processing is controlled.

  Some storage systems include a plurality of microprocessors for executing input / output processing with a storage device. In such a storage system, a microprocessor in charge of input / output processing for each logical storage device is preset, and when an input / output request is received from a host computer, the logical storage indicated by the input / output request A microprocessor in charge of input / output processing for the apparatus performs input / output processing based on the input / output request (see, for example, Patent Document 1).

Japanese Patent Laying-Open No. 2005-301802

  According to the technique described in Patent Document 1, since a microprocessor that performs input / output processing can be set according to the logical storage device indicated by the input / output request, the load on the microprocessor can be distributed. it can.

  However, in order to set the microprocessor in charge of the logical storage device, the storage system administrator himself / herself sets the logical storage device and the microprocessor in charge of the logical storage device when creating the logical storage device. There is a problem that it is necessary to define it, it is difficult to define, and it takes time and effort.

  Even when the logical storage device is created in consideration of the load on the microprocessor and the microprocessor that is responsible for the logical storage device is determined when the logical storage device is actually used, There is also a possibility that the processor load may not be properly distributed. However, in the conventional storage system, changing the charge of the logical storage device after use is not considered at all.

  Therefore, the present invention has been made in view of the above problems, and an object thereof is to provide a technique capable of easily changing a processor in charge of a logical storage device. Another object of the present invention is to provide a technique capable of easily setting a processor in charge of a logical storage device without an administrator being aware of it.

  In order to solve the above-described problem, a storage system according to an aspect of the present invention is a storage system that performs input / output processing for a plurality of logical storage devices to which at least a part of storage areas of a plurality of storage devices are allocated. A first interface unit connected to the storage device, a second interface unit connected to the storage device and performing data input / output processing with the storage device, and the logical storage device via the second interface unit. A plurality of control units each including at least one processor for controlling input / output processing with respect to the storage area; and a communication network that connects them in a communicable manner, wherein the first interface unit is a storage area of the logical storage device A management table for managing the control unit in charge of controlling input / output processing for the host computer, and the discussion from the host computer. A request delivery unit that delivers the input / output request to the control unit in charge of input / output processing of the logical storage device based on the management table when there is an input / output request to the storage device; A change determination unit that determines whether or not to change the control unit in charge of input / output processing for the logical storage device, and when the change determination unit determines to change the control unit, A setting unit that sets the management table so that the control unit different from the control unit in charge is in charge of input / output processing for the logical storage device;

It is a block diagram of the computer system which concerns on one Embodiment of this invention. FIG. 2A is a diagram showing an example of the configuration of a management table according to an embodiment of the present invention. FIG. 2B is a diagram illustrating an example of the structure of the LDEV number correspondence table. It is a figure explaining the queue in LM of MPPK concerning one embodiment of the present invention. It is a figure which shows an example of a structure of the information managed by LM and shared memory which concerns on one Embodiment of this invention. FIG. 5A is a diagram showing an example of the configuration of address correspondence information according to an embodiment of the present invention. FIG. 5B is a diagram showing an example of the configuration of RAID configuration information according to an embodiment of the present invention. FIG. 5C is a diagram showing an example of the configuration of HDD configuration information according to an embodiment of the present invention. It is a block diagram of the management console which concerns on one Embodiment of this invention. It is a figure which shows the LDEV management screen which concerns on one Embodiment of this invention. It is a figure which shows the tuning screen which concerns on one Embodiment of this invention. It is a flowchart of the LDEV addition process which concerns on one Embodiment of this invention. It is a flowchart of the path | pass setting process which concerns on one Embodiment of this invention. It is a flowchart of the LDEV reduction process which concerns on one Embodiment of this invention. It is a flowchart of the ownership securing process which concerns on one Embodiment of this invention. It is a flowchart of the tuning screen display process which concerns on one Embodiment of this invention. It is a flowchart of the tuning process which concerns on one Embodiment of this invention. 5 is a flowchart of MPPK replacement processing according to an embodiment of the present invention. It is a flowchart of the I / FPK replacement process according to an embodiment of the present invention. It is a flowchart of the path definition deletion process which concerns on one Embodiment of this invention. It is a flowchart of the access ensuring process which concerns on one Embodiment of this invention. It is a flowchart of the LDEV removal process which concerns on the 1st modification in one Embodiment of this invention. It is a flowchart of the tuning process which concerns on the 2nd modification in one Embodiment of this invention. It is a flowchart of the tuning process which concerns on the 3rd modification in one Embodiment of this invention. It is a flowchart of the load distribution automatic adjustment process which concerns on the 4th modification in one Embodiment of this invention.

  Embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below do not limit the invention according to the claims, and all combinations of features described in the embodiments are not necessarily essential to the solution means of the invention. Absent.

  FIG. 1 is a configuration diagram of a computer system according to an embodiment of the present invention.

  The computer system includes a host computer (not shown), a storage system 10, and a management console 20. The storage system 10 is connected to one or more host computers that read or write data via a cable or network. The network for connecting to the host computer may be a SAN (Storage Area Network), a LAN (Local Area Network), the Internet, a dedicated line, a public line, or the like, as long as it can perform data communication. Good. The protocol for the network or cable may be a fiber channel protocol or TCP / IP protocol, and any protocol can be used as long as data can be exchanged between the host computer and the storage system 10. It may be. The read request transmitted from the host computer includes, for example, a LUN (Logical Unit Number) and an LBA (Logical Block Address) in which data to be read is managed. Further, the write request transmitted from the host computer includes, for example, the LUN and LBA for writing the write target data and the write target data.

  The storage system 10 includes a plurality of host I / F units (I / FPK: I / F package) 100, a plurality of control units (MPPK: Micro processor package) 120, a plurality of shared memory units (memory PK) 130, A plurality of disk I / F units 140, an HDD (Hard Disk Drive) 170 as an example of a plurality of storage devices, and an internal network 150 are included. The internal network 150 connects each of the I / FPK 100, the MPPK 120, the shared memory unit 130, and the disk I / F unit 140. According to the internal network 150, each MP 121 of the MPPK 120 can communicate with any of the I / FPK 100, the shared memory unit 130, and the disk I / F unit 140.

  The I / FPK 100 has a plurality of host I / Fs 101. The host I / F 101 mediates exchange of information regarding input / output processing with the host computer. The host I / F 101 stores the management table 102 (FIG. 2A) in an internal local memory (not shown).

  FIG. 2A is a diagram showing an example of the configuration of a management table according to an embodiment of the present invention.

  The management table 102 has an entry including a path name field 102a and an MPPK number (MPPK #) field 102b. In this embodiment, there are entries for the number of path names that can be specified for the host I / F 101.

  The path name field 102a stores a path name (identification information) for referring to the LDEV (logical storage device) from the host computer. here. The LDEV is a logical storage device that can be referred to from the host computer. For example, at least a part of the storage areas of the plurality of HDDs 170 is allocated to the storage area of the LDEV. In the path name field 102a, for example, when the SCSI standard is used for communication with the host computer, a LUN (Logical Unit Number) is stored. Here, a plurality of path names can be defined for the same LDEV. The host computer transmits an input / output request by specifying a port for referring to the LDEV and the path name of the LDEV, for example, but the host I / F 101 transmits the WWN or the like included in the input / output request. It is possible to identify whether it is addressed to its own port by the port number.

  The MPPK # field 102b stores identification information (for example, an MPPK number) of the MPPK 120 in charge of the LDEV input / output process indicated by the path name in the path name field 102a of the same entry. When the MPPK # field 102b is empty (for example, -1 is stored), it means that input / output processing for the LDEV indicated by the path name of the same entry is impossible. When a plurality of path names are defined for the same LDEV, the MPPK # of each entry is the same number. Here, the MPPK right that can take charge of the LDEV input / output processing is referred to as the LDEV owner right.

  Returning to FIG. 1, the host I / F unit 101 can transfer the input / output processing for a certain LDEV to only one MPPK 120 having ownership by the management table 102. That is, the host I / F unit 101 receives an input / output request addressed to its own port from the host computer, acquires the MPPK # corresponding to the path name included in the input / output request from the management table 102, and An input / output request can be passed to the MPPK 120 of #. In this embodiment, the host I / F 101 number is added to the input / output request passed from the host I / F 101 to the MPPK 120. In this embodiment, the host I / F 101 adds an input / output request to a queue stored in the LM 122 of the MPPK 120.

  In the storage system 10, one or a plurality of LDEVs can be provided using the storage areas of the plurality of HDDs 170. In the storage system 10, a RAID (Redundant Array of Independent Disks) group can be configured by two or more HDDs 170 of the plurality of HDDs 170, and the storage area of the RAID group can be provided as the storage area of the LDEV.

  The disk I / F unit 140 has a plurality of disk I / Fs 141. For example, the disk I / F 141 is connected to the HDD 170 via a cable and is also connected to the internal network 150, and mediates a process of transferring data to be read or written between the internal network 150 side and the HDD 170. .

  The shared memory unit 130 includes a shared memory 131. The shared memory 131 may be a volatile memory, for example, a DRAM (Dynamic Random Access Memory). The shared memory 131 temporarily stores (caches) data to be written to the HDD 170 or temporarily stores (caches) data read from the HDD 170. In addition, the shared memory 131 stores information necessary for processing, such as LDEV control information, an LDEV number correspondence table, HDD configuration information, and the like. These pieces of information will be described later. For example, in a certain LDEV 160 among a plurality of LDEVs, the data stored in the storage area of the LDEV is stored in at least one of the shared memory 131 or the plurality of HDDs 170 and the data cached in the LDEV 160 is stored in the shared memory 131. The address and the storage location in the HDD 170 can be specified by the LDEV control information in the shared memory 131. In this embodiment, as will be described later, the LDEV control information is also stored in the LM 122 of the MPPK 120 having ownership.

  The MPPK 120 includes a plurality of MPs (micro processors) 121, a local memory (LM) 122, and a bus 123 that connects them.

  The LM 122 is used as an area for storing a queue (queue) of input / output requests transmitted from the host I / F 121.

  FIG. 3 is a diagram illustrating queues in the LM of MPPK according to an embodiment.

  In the LM 122 of the MPPK 120, the input / output request received from each host I / F 101 is stored as a queue 125. In this embodiment, the LM 122 stores a queue 125 corresponding to each host I / F 101 in which a path is defined.

  Returning to FIG. 1, the LM 122 is used as an area for storing programs and data for processing executed by the MP 121 or as a work area for storing data used for processing by the MP 121. In the present embodiment, the LM 122 stores LDEV control information for which it owns ownership, a part of the LDEV number correspondence table, HDD configuration information, and the like. These pieces of information will be described later. The LM 122 can be accessed from the MP 121 at a higher speed than the shared memory 131. This is because the access from the MP 121 to the shared memory 131 requires a communication overhead for passing through the internal network 151 for transferring data to be read and written and for exclusive control between the plurality of MPs 121 sharing the shared memory 131. is there.

  Each MP 121 executes an input / output process for the LDEV by executing a program stored in the LM 122. For example, each of the MPs 121 acquires (dequeues) one input / output request from any queue 125 stored in the LM 122 when the input / output process can be executed, and sends the input / output request to the LDEV according to the input / output request. Execute input / output processing. Other processing will be described later. Here, in this embodiment, a change determination unit, a setting unit, a change receiving unit, a load detection unit, a control information acquisition unit, an end request unit, a charge end unit, an end notification transmission unit, an identification information acquisition unit, an identification information deletion unit The deletion notification unit, identification information storage unit, expansion reception unit, charge determination unit, charge registration unit, reduction reception unit, charge detection unit, charge end unit, control information deletion unit, reduction request transmission unit, etc. The MP 121 is configured by executing a program stored in the LM 122. In addition, although each part was comprised when MP121 executed the program, for example, you may implement | achieve at least one part function part with a hardware.

  FIG. 2B is a diagram illustrating an example of the structure of the LDEV number correspondence table.

  The LDEV number correspondence table 132 stores an entry including an I / F number (I / F #) field 132a, a path name field 132b, and an LDEV number (LDEV #) field 132c. The I / F # field 132a stores the number of the host I / F 101. The path name field 132b stores a path name for referring to the LDEV from the host computer. The LDEV # field 132c stores identification information (LDEV number) of the LDEV corresponding to the LDEV having the same entry path name received by the host I / F 101 having the same entry I / F number.

  According to the LDEV number correspondence table 132, the MP 121 specifies the LDEV number based on the path name in the input / output request received from the host I / F 101 and the host I / F 101 number received together with the input / output request. be able to.

  In the present embodiment, the LDEV number correspondence table 132 is stored in the shared memory 131 and the LM 122. The LDEV number correspondence table 132 stored in the shared memory 131 has entries corresponding to all LDEVs in the storage system 10. On the other hand, the LDEV number correspondence table 132 stored in the LM 122 has only entries corresponding to the LDEV to which the MPPK 120 to which the LM 122 belongs has ownership.

  In the present embodiment, the MP 121 can identify the LDEV number having ownership by referring to the LDEV number correspondence table 132 of the LM 122 of the MPPK 120 to which the MP 121 belongs. The LDEV number that is the target of the input / output request can be quickly identified as compared with the above.

  FIG. 4 is a diagram illustrating an example of a configuration of information managed by the LM and the shared memory according to an embodiment of the present invention.

  The shared memory 131 stores control information (total control information) 133 related to all LDEVs. The overall control information 133 includes a plurality of pieces of information (individual information) 134 related to each LDEV. The individual information 134 includes control information (individual control information) 134b related to one LDEV and a lock word 134a that identifies the MPPK 120 having the ownership of the LDEV. For example, an identifier (for example, MPPK number) of any one MPPK 120 is stored in the lock word 134a. In this embodiment, basically, the MP 121 of the MPPK 120 in which the MPPK number to which the self belongs is not stored in the lock word 134a is used for processing, such as copying, editing, and deleting the individual control information 134b of the corresponding LDEV, and the host I Management is performed so that processing such as updating of the corresponding LDEV entry in the management table of / F101 cannot be performed.

  The LM 122 stores a lock presence / absence 124a for each LDEV and a pointer 124b. The lock presence / absence 124a of each LDEV is managed based on the LDEV number so that the MP 121 can access the lock presence / absence 124a for the corresponding LDEV. The presence / absence of ownership for the corresponding LDEV is stored in the lock presence / absence 124a. Here, having ownership is also referred to as having a lock. If the pointer 124b has the ownership of the corresponding LDEV, a pointer to the individual control information 124c of the corresponding LDEV stored in the LM 122 is stored. In the individual control information 124c, information having the same contents as the individual control information 134b of the corresponding LDEV stored in the shared memory 131 is stored. The individual control information 124c is associated with LDEV load information 124d. The LDEV load information 124d stores load information such as the number of input / output processes per unit time for the LDEV and the amount of data transferred per unit time. The LM 122 stores MPPK load information 124e. The MPPK load information 124e stores load information such as the operation rate of the MP 121 in the MPPK 120 to which the LM 122 belongs.

  Next, the LDEV individual control information 134b will be described in detail. The individual control information 124c has the same configuration as the individual control information 134b.

  The individual control information 134b includes address correspondence information 135 and RAID configuration information 136.

  FIG. 5A is a diagram showing an example of the configuration of address correspondence information according to an embodiment of the present invention.

  The address correspondence information 135 has an entry including an LDEV address field 135a and a cache address field 135b. Each position (address) in the storage area of the LDEV is stored in the LDEV address field 135a. The cache address field 135b stores the position (address) in the shared memory 131 when data corresponding to the LDEV address of the same entry is stored in the shared memory 131, that is, when it is cached. .

  According to the address correspondence information 135, if data corresponding to the LDEV address included in the input / output request is stored in the shared memory 131, the MP 121 acquires the address of the shared memory 131 in which the data is stored. can do.

  FIG. 5B is a diagram showing an example of the configuration of RAID configuration information according to an embodiment of the present invention.

  The RAID configuration information 136 includes a RAID number (RAID #) 136a, a size 136b, and an offset 136c. The RAID number 136a is an identifier (for example, a number) for identifying the RAID group in which the corresponding LDEV is stored in the storage system 10. The size 136b is the size of the storage area of the corresponding LDEV, that is, the storage capacity. The offset 136c is an offset value between the start position of the RAID group and the position of the RAID group in which the corresponding LDEV is stored.

  According to the RAID configuration information 136, the MP 121 can specify a RAID group in which a predetermined address of the LDEV is stored and a storage position (address) in the RAID group. That is, the RAID group can be specified by the RAID number, and the head position of the LDEV in the RAID group can be specified by the offset. Therefore, the corresponding address in the RAID group can be specified based on the LDEV address included in the input / output request.

  The shared memory 131 further stores HDD configuration information 137. The HDD configuration information 137 may be stored in the LM 122 of the MPPK 120.

  FIG. 5C is a diagram showing an example of the configuration of HDD configuration information according to an embodiment of the present invention.

  The HDD configuration information 137 has a plurality of entries including a RAID level field 137a and a plurality of HDD number (HDD #) fields 137b. The HDD configuration information 137 allows the MP 121 to access an entry for the corresponding RAID group based on the RAID number.

  The RAID level field 137a stores the RAID level in the corresponding RAID group. For example, RAID 1 or RAID 5 is stored in the RAID level field 137a. The HDD number field 137b stores an identifier (for example, an HDD number) of the HDD 170 constituting the corresponding RAID group.

  According to the HDD configuration information 137, the MP 121 of the MPPK 120 can grasp the HDD 170 that actually performs input / output and the position (address) in the HDD 170 from the RAID group and the address in the RAID group. That is, the RAID level of a RAID group can be grasped from the number of the RAID group that manages the LDEV that is the target of input / output processing. Then, from the position in the RAID group corresponding to the position of the LDEV to be input / output, the grasped RAID level, and the number of the HDD 170 constituting the RAID group, the addresses in the HDD 170 and the HDD 170 that actually perform the input / output can be grasped.

  Next, the management console 20 will be described.

  FIG. 6 is a configuration diagram of a management console according to an embodiment of the present invention.

  In the management console 20, a communication I / F 21, an input I / F 22, a display I / F 23, a memory 24, an HDD 25, and a CPU 26 (Central Processing Unit) are connected via a bus 27.

  The memory 24 includes, for example, a ROM (Read Only Memory) and a RAM (Random Access Memory), and stores a boot program and programs for executing various processes. The memory 24 is used as an area for storing programs and data, or as a work area for storing data used for processing by the CPU 26. The HDD 25 stores programs and various information that need to be stored even when the power is not turned on.

  For example, an input unit 28 that accepts an operation by a user (administrator) of the management console 20 such as a mouse or a keyboard is connected to the input I / F 22. The input I / F 22 outputs a signal from the input unit 28 to the CPU 26 as data. For example, a display unit 29 such as a liquid crystal display or a CRT is connected to the display I / F 23. The display I / F 23 includes, for example, a VRAM (Video Random Access Memory), generates image data corresponding to an image to be displayed under the control of the CPU 26, and causes the display unit 29 to display and output various screens. The communication I / F 21 is connected to the internal network 150 of the storage system 10 and mediates data exchange between the CPU 26 and each unit of the storage system 10 connected to the internal network 150 (for example, the MP 121 of the MPPK 120).

  CPU26 controls operation | movement of each part 21-25. Further, the CPU 26 reads out the program stored in the memory 24 and / or the HDD 25 to the RAM of the memory 24 and executes it. Here, in the present embodiment, the CPU 26 stores the expansion instruction reception unit, the control unit determination unit, the expansion instruction transmission unit, the collection unit, the change designation reception unit, the change instruction transmission unit, and the like mainly in the memory 24 and / or the HDD 25. It is configured by executing the programmed program.

  The CPU 26 displays various images on the display unit 29 via the display I / F 23. For example, the CPU 26 acquires information on the identification information of the LDEV stored in the shared memory 131 and the RAID group number to which the LDEV belongs, and based on the information, the display screen 29a of the display unit 29 via the display I / F 23. To display the LDEV management screen.

  FIG. 7 is a diagram showing an LDEV management screen according to an embodiment of the present invention.

  On the LDEV management screen 51, a RAID group display area 52 and an LDEV display area 53 are displayed. The LDEV management screen 51 displays a cursor 54 that can be moved within the screen by the user's operation on the input unit 28.

  In the RAID group display area 52, an image (RAID group image) 52a indicating each RAID group of the storage system 10 is displayed. In the LDEV display area 53, an image (LDEV image) 53a indicating the LDEV assigned to the specified RAID group is displayed.

  In the RAID group display area 52, when the user moves the cursor 54 onto the RAID group image 52a by the input unit 28 and continuously presses (double-clicks) the left button of the mouse of the input unit 28 twice, the CPU 26 The LDEV image 53a of the LDEV assigned to the RAID group corresponding to the RAID group image 52a where the cursor 54 is located is displayed in the LDEV display area 53.

  When the user clicks (right-clicks) the right button of the mouse of the input unit 28 with the cursor 54 positioned in the LDEV display area 53, the CPU 26 causes the LDEV processing window 55 to be displayed. In the LDEV processing window 55, for example, an LDEV addition button 55a for starting a process of adding a new LDEV to the RAID group, and a process of deleting an LDEV corresponding to the LDEV image 53a selected in the LDEV display area 53 Are displayed, an LDEV reduction button 55b for starting the process, a path setting button 55c for starting a process for setting an LDEV path corresponding to the LDEV image 53a selected in the LDEV display area 53, and the like. When there is an instruction from the cursor 54 to the LDEV addition button 55a, a screen for inputting information necessary for LDEV addition is displayed, and LDEV addition processing can be performed. In the LDEV addition process, the user may input, for example, the number and size of the LDEV to be added. For this reason, the administrator does not need to make settings while paying attention to the MPPK 120 responsible for the LDEV input / output processing. If there is an instruction from the cursor 54 to the LDEV reduction button 55b, processing for reducing the LDEV selected by the CPU 26 is started. In addition, when there is an instruction from the cursor 54 to the path setting button 55c, a screen for inputting information necessary for path setting is displayed, and path setting processing can be performed. In the path setting process, for example, the user may input the number of the host I / F 101 for setting the path and the path name. For this reason, it is not necessary for the administrator to specify the MPPK 120 in charge of LDEV input / output processing.

  Further, the CPU 26 acquires the load information of each MPPK 120 to MP 121 and the load information of the LDEV that each MPPK 120 has ownership of, and displays the tuning screen on the display screen 29 a of the display unit 29 via the display I / F 23.

  FIG. 8 is a diagram showing a tuning screen according to an embodiment of the present invention.

  On the tuning screen 60, a plurality of individual state display areas 61 indicating the state of each MPPK 120 are displayed. The tuning screen 60 also displays a cursor 65 that can be moved within the screen by a user operation on the input unit 28. The individual status display areas 61 corresponding to all the MPPKs 120 in the storage system 10 may be prepared and displayed as one screen, or may be prepared as a plurality of screens and the screens to be displayed may be switched.

  Each individual status display area 61 displays an MP load display area 62 for displaying the load information of the MP 121 in the corresponding MPPK 120, and an LDEV load display area 63 for displaying the load information of the LDEV for which the corresponding MPPK 120 has ownership. Is done.

  In the present embodiment, the MP load display area 62 displays a graph in which the vertical axis indicates the operation rate of the MP 121. In the present embodiment, in the LDEV load display area 63, a graph 63a in which the horizontal axis indicates the load of the LDEV is arranged and displayed in order from the LDEV with the highest load.

  According to the tuning screen 60, the user (administrator) of the management console 20 can easily visually grasp the load of the MP 121 of each MPPK 120, and the load of the LDEV for which each MPPK 120 has ownership. Can also be easily grasped visually.

  In the tuning screen 60, if there is an LDEV for which the MPPK 120 in charge of input / output processing is desired to be changed, an instruction to change it easily can be given. That is, on the tuning screen 60, the user moves the cursor of the input unit 28 while keeping the right button of the mouse of the input unit 28 pressed while the cursor 65 is positioned on the graph 63a indicating the LDEV that the user wants to change. After moving to the individual state display area 61 of the MPPK 120 that newly handles the graph 63a, the right button of the mouse is terminated. That is, when the LDEV graph 63a is dragged and dropped, the CPU 26 moves to the graph 63a. The corresponding LDEV is accepted as an instruction to make the MPPK 120 in the individual state display area 61 a new charge. For example, when the LDEV assigned to the first MPPK is assigned to the second MPPK, a graph showing the LDEV in the individual state display area 61 (upper left in the figure) corresponding to the first MPPK as shown by the broken line in FIG. The instruction may be performed by dragging and dropping 63a to the individual state display area 61 (upper right in the figure) corresponding to the second MPPK.

  Next, each process in the storage system according to the embodiment will be described. First, an LDEV addition process when adding a new LDEV in the storage system 10 will be described. This LDEV addition process is executed, for example, in an initial state where no LDEV is set in the storage system 10 or when an LDEV is added when an LDEV has already been set. In addition, similar processing is executed at the time of consolidation for integrating a plurality of storage systems into the storage system 10.

  FIG. 9 is a flowchart of LDEV addition processing according to an embodiment of the present invention.

  In the LDEV addition process, the CPU 26 of the management console 20 receives an LDEV addition request by an operation on the input unit 28 by the user. In the present embodiment, the CPU 26 receives the number of LDEVs to be added, the size of the LDEV, and the RAID group number by an operation on the input unit 28 by the user. At the time of consolidation, the user needs to specify these according to the setting information of each LDEV in the storage system before consolidation.

  Next, the CPU 26 selects the MPPK 120 that is in charge of input / output processing of the LDEV from the plurality of MPPKs 120 (step S11). Here, the CPU 26 may select the MPPK 120 by round robin, for example, or may select it randomly. Thus, when the LDEV is added, since the CPU 26 selects the MPPK 120 in charge of the LDEV, there is no need for the user to set it.

  Next, the CPU 26 transmits an LDEV addition instruction including the received LDEV number, LDEV size, and RAID group number to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S12). In the following description, the communication I / F 21 and the internal network 150 that mediate information may be omitted.

  The MP 121 of the destination MPPK 120 receives the LDEV addition instruction via the internal network 150. Next, the MP 121 stores the received RAID group number and size in the RAID configuration information 136 of the LDEV corresponding to the LDEV number in the LDEV addition instruction in the LM 122 and the shared memory 131. Further, a position that can be allocated in the corresponding RAID group is specified, and the offset of the position is stored in the RAID configuration information 136. Further, the MP 121 locks the individual control information of the LDEV. That is, the MP 121 stores the identifier of the MPPK 120 to which the MP 121 belongs in the corresponding LDEV lock word 134 a in the shared memory 131. Also, the MP 121 sets the lock presence / absence in the lock presence / absence field 124a of the corresponding LDEV in the LM 122, and sets a pointer to the individual control information 124c in the pointer 124b (step S13).

  Thereafter, the MP 121 transmits an LDEV addition completion notification indicating that the LDEV addition has been completed to the management console 120 (step S14).

  When the CPU 26 receives the LDEV addition completion notification in the management console 20, the CPU 26 causes the display unit 29 to display a result indicating that the LDEV addition has been completed (step S15).

  Note that when a plurality of LDEVs are added, the same processing as described above may be repeated. Further, at the time of consolidation, after the LDEV similar to the LDEV of the storage system before consolidation is added to the storage system 10 by the above processing, the data stored in the LDEV of the storage system before consolidation is added to the storage system 10. Will be stored.

  Next, a path setting process for making it possible to access the added LDEV from the host computer will be described.

  FIG. 10 is a flowchart of path setting processing according to an embodiment of the present invention.

  In the path setting process, the CPU 26 of the management console 20 receives a path setting request by an operation on the input unit 28 by the user. In this embodiment, the CPU 26 operates the input unit 28 by the user, and the host I / F 101 number (I / F number) that accepts input from the host computer, the path name indicating the LDEV, and the LDEV that sets the path. Number (LDEV number).

  Next, the CPU 26 selects the MPPK 120 as the transmission destination of the path setting instruction from the plurality of MPPKs 120 (step S21). Here, the CPU 26 may select the MPPK 120 by round robin, for example, or may select it randomly. As described above, when the path is set, the CPU 26 selects the MPPK 120 as the instruction transmission destination, so that the user need not select it. For this reason, it is not necessary to display the destination MPPK number on the display unit 28, and even if displayed, it is not necessary for the user to select the destination MPPK 120.

  Next, the CPU 26 transmits a path setting instruction including the received I / F number, path name, and LDEV number to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S22).

  The MP 121 of the destination MPPK 120 receives the path setting instruction via the internal network 150. Next, the MP 121 acquires, from the shared memory 131, the MPPK number of the MPPK 120 that has the ownership of the LDEV of the LDEV number included in the path setting instruction (step S23). The MPPK number of the MPPK 120 having the ownership can be obtained from the lock word 134a of the corresponding LDEV in the shared memory 131.

  Next, the MP 121 determines whether or not the MPPK 120 to which the MPPK 120 belongs has the ownership of the LDEV to which the path is set, based on whether or not the acquired MPPK number is the MPPK number of the MPPK 120 to which the MPPK 120 belongs (Step). S24).

  As a result, when the acquired MPPK number matches the MPPK number of the MPPK 120 to which the MPPK belongs, and the owner of the LDEV that is the path setting target is possessed (Yes in step S24), the MP 121, the LM 122 and the shared memory 131 In the LDEV number correspondence table 132, an entry including an I / F number, a path name, and an LDEV number in the path setting instruction is registered. Also, the MP 121 stores the received RAID group number and size in the RAID configuration information 136. Further, the MP 121 sets an entry including the path name instructing the path setting and the MPPK120MPPK number to which the MP121 belongs in the management table 102 of the host I / F 101 indicated by the I / F number instructing the path setting (step S25). Then, the MP 121 notifies the management console 20 of a path setting completion notification (step S26).

  On the other hand, if the acquired MPPK number does not match the MPPK number of the MPPK 120 to which the MPPK belongs, and does not have the ownership of the LDEV to which the path is set (No in step S24), the information related to the LDEV is updated. I can't do it. For this reason, the MP 121 includes the MPPK number of the MPPK 120 having the acquired ownership in the path setting failure notification and transmits it to the management console 20 (step S27).

  The CPU 26 of the management console 20 determines whether or not the path setting has been completed, that is, whether or not a path setting completion notification has been received (step S28). Is displayed on the display unit 29 (step S33).

  On the other hand, when the path setting is not completed, that is, when the path setting failure notification is received, the CPU 26 selects the MPPK 120 of the MPPK number included in the path setting failure notification as the transmission destination (step S29). Then, a path setting instruction including the I / F number, path name, and LDEV number is transmitted to the MPPK 120 (step S30).

  The MP 121 of the MPPK 120 that has received the path setting instruction executes the processing from step S23 to step S25 (step S31). Here, since the MPPK 120 has ownership, processing corresponding to step S25 is executed during step S31.

  Next, the MP 121 notifies the management console 20 of a path setting completion notification (step S32). Thereafter, the CPU 26 of the management console 20 that has received the path setting completion notification causes the display unit 29 to display a result indicating that the path setting has been completed (step S33).

  According to the path setting process described above, even if the MPPK 120 selected as the destination to which the path setting instruction is first transmitted does not have the owner right of the corresponding LDEV, the path is subsequently passed to the MPPK 120 having the owner right of the corresponding LDEV. A setting instruction can be transmitted to set a path. For this reason, the management console 20 does not need to keep track of MPPKs that have LDEV ownership. For this reason, even if the storage system 10 independently transfers the ownership of the LDEV without the involvement of the management console 20, the path setting can be performed without any trouble.

  Next, LDEV removal processing for removing the added LDEV will be described.

  FIG. 11 is a flowchart of LDEV removal processing according to an embodiment of the present invention.

  In the LDEV reduction process, the CPU 26 of the management console 20 receives an LDEV reduction request by a user operation on the input unit 28. In the present embodiment, for example, the CPU 26 receives the designation of the LDEV to be removed by an operation on the input unit 28 by the user when the LDEV management screen 51 is displayed. Next, the CPU 26 selects the MPPK 120 that causes the LDEV to be removed from the plurality of MPPKs 120 (step S41). Here, the CPU 26 may select the MPPK 120 by round robin, for example, or may select it randomly. In this way, when the LDEV is removed, the MPPK 120 to be removed is selected by the CPU 26, so that there is no need for the user to designate it.

  Next, the CPU 26 transmits an LDEV removal instruction including the LDEV number corresponding to the received LDEV to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S42).

  The MP 121 of the destination MPPK 120 receives the LDEV removal instruction via the internal network 150. Next, the MP 121 secures the ownership of the LDEV to be removed by executing an ownership securing process (step S43) described later.

  Next, the MP 121 acquires the I / F number and path name corresponding to the LDEV number of the LDEV to be removed from the LDEV number correspondence table 132 stored in the LM 122, and the host I / F corresponding to the I / F number. The entry including the path name is deleted from the management table 102 of F101. Furthermore, the MP 121 deletes the individual control information 124c and the LDEV load information 124d for the LDEV to be removed from the LM 122, sets the lock presence 124a corresponding to the LDEV to no lock, and makes the pointer 124b empty. Also, the MP 121 deletes the corresponding LDEV individual control information 134b from the shared memory 131 and releases the lock to the LDEV control information in the shared memory 131, that is, the empty value (for example, the lock word 134a of the corresponding LDEV (for example, , -1) is stored (step S44).

  Thereafter, the MP 121 notifies the management console 20 of an LDEV removal completion notification (step S45). The CPU 26 of the management console 20 that has received the LDEV removal completion notification causes the display unit 29 to display a result indicating that the LDEV removal has been completed (step S46).

  According to the LDEV removal processing described above, even if the MPPK 120 selected as the destination to which the LDEV removal instruction is first transmitted does not have the owner right of the corresponding LDEV, the LDEV can be removed. For this reason, the management console 20 does not need to keep track of MPPKs that have LDEV ownership.

  Next, the ownership securing process will be described.

  FIG. 12 is a flowchart of the ownership securing process according to an embodiment of the present invention.

  In performing the ownership securing process, the MP 121 has already acquired the LDEV number of the LDEV for which the ownership is secured. In the ownership securing process, the MP 121 of the MPPK 120 that secures the ownership refers to the lock of the target LDEV that secures the ownership of the shared memory 131. That is, the MP 121 acquires the MPPK number of the MPPK 120 having the ownership of the LDEV for which ownership is to be secured from the shared memory 131 (step S51).

  Next, the MP 121 determines whether or not the MPPK 120 to which the MPPK 120 belongs has the ownership of the LDEV for which ownership is to be secured based on whether or not the acquired MPPK number is the MPPK number of the MPPK 120 to which the MPPK 120 belongs (Step). S52).

  As a result, when the acquired MPPK number matches the MPPK number of the MPPK 120 to which the self belongs (Yes in step S52), it means that the owner right of the LDEV is obtained, so the owner right securing process is terminated. To do.

  On the other hand, if the acquired MPPK number does not match the MPPK number of the MPPK 120 to which the MPPK belongs (No in step S52), it means that the owner right of the LDEV is not possessed. The ownership release request including the LDEV number of the LDEV is transmitted to the MPPK 120 indicated by the acquired MPPK number, that is, the MPPK 120 having the ownership of the target LDEV, via the communication I / F 21 and the internal network 150 (step S53). ).

  The MP 121 of the destination MPPK 120 receives the ownership release request via the internal network 150. When receiving the ownership release request, the MP 121 obtains an I / F number and a path name corresponding to the LDEV number included in the ownership release request from the LDEV number correspondence table 132 stored in the LM 122. Next, the MP 121 empties (for example, −1) the MPPK number in the entry including the path name from the management table 102 of the host I / F 101 corresponding to the I / F number. As a result, a new input / output request for the target LDEV from the host I / F 101 can be prevented from being passed to the MPPK 120.

  Further, the MP 121 waits until input / output processing for the LDEV is completed. Here, the completion of the input / output processing for the LDEV can be grasped, for example, because there is no input / output request for the target LDEV in the queue stored in the LM 122 of the MPPK 120. As a result, it is possible to appropriately prevent a situation in which an input / output process to an already received LDEV is not executed.

  Thereafter, the MP 121 deletes the corresponding LDEV individual control information 134b from the shared memory 131 and releases the lock to the LDEV control information in the shared memory 131, that is, the empty value (for example, the lock word 134a of the corresponding LDEV (for example, , -1). In addition, the MP 121 deletes the individual control information 124c and the LDEV load information 124d for the target LDEV from the LM 122, sets the lock presence / absence 124a corresponding to the LDEV to no lock, and makes the pointer 124b empty (step S54). ).

  Next, the MP 121 transmits an ownership release response indicating that the ownership release has been performed to the requesting MPPK 121 (step S55).

  The MP 121 of the MPPK 120 that secures the ownership determines whether an ownership release response has been received within a predetermined time (step S56). As a result, when the ownership release response has not been received within the predetermined time (No in step S56), it is considered that a failure has occurred in the MPPK 120 that has transmitted the ownership release request, so that the MPPK 120 is blocked. Execute the process. Here, the process for closing the MPPK 120 includes, for example, a process for resetting the MPPK 120 and a process for stopping the supply of power to the MPPK 120. Next, the MP 121 acquires an I / F number and a path name corresponding to the target LDEV number from the LDEV number correspondence table 132 stored in the shared memory 131. Next, the MP 121 sets the MPPK number of the entry including the path name to an empty value (for example, −1) in the management table 102 of the host I / F 101 corresponding to the I / F number. In addition, the MP 121 unlocks the LDEV control information in the shared memory 131, that is, stores an empty value (for example, −1) in the corresponding LDEV lock word 134a (step S57).

  When step S57 is performed or when an ownership release response is received within a predetermined time (Yes in step S56), the MP 121 locks the control information of the target LDEV in the shared memory 131. That is, the own MPPK number is stored in the lock word 134a of the corresponding LDEV. Next, the MP 121 acquires the individual control information 134 of the target LDEV from the shared memory 131 and copies it to the LM 122. As a result, the individual control information 124c of the corresponding LDEV exists in the LM 122. Also, the MP 121 acquires an entry having the LDEV number of the target LDEV from the LDEV number correspondence table 132 of the shared memory 131 and stores it in the LM 122. In addition, the MP 121 sets the lock presence / absence 124a corresponding to the target LDEV of the LM 122 to be locked, and sets the pointer to the head of the individual control information 124c of the LM 122 in the pointer 124b. Further, the MP 121 acquires an I / F number and a path name corresponding to the LDEV number of the target LDEV from the LDEV number management table 132 of the LM 122. Next, the MP 121 stores its own MPPK number in the MPPK number of the entry including the path name in the management table 102 of the host I / F 101 corresponding to the I / F number (step S58). As a result, the MPPK 120 can secure ownership of the target LDEV and can execute input / output processing for the target LDEV.

  Next, a tuning screen display process for displaying a tuning screen will be described.

  FIG. 13 is a flowchart of tuning screen display processing according to an embodiment of the present invention.

  In the tuning screen display process, the CPU 26 of the management console 20 receives a load status display instruction by an operation on the input unit 28 by the user (step S61). When the load status display instruction is received, the following processing steps (steps S62 to S65) are executed for all the MPPKs 120 of the storage system 10.

  First, the CPU 26 selects one MPPK 120 from the plurality of MPPKs 120 of the storage system 10 according to round robin (step S62).

  Next, the CPU 26 transmits a load information request to the selected MPPK 120 (step S63).

  The MP 121 of the MPPK 120 that has received the load information request extracts the MPPK load information from the MPPK load information 124e of the LM 122 and transmits it to the management console 20 (step S64). The load information is extracted, and the load information is transmitted to the management console 20 together with the LDEV numbers (step S65). On the other hand, the management console 20 receives the MPPK load information, the LDEV load information, and the LDEV number transmitted from the MPPK 120.

  When the CPU 26 of the management console 20 receives the MPPK load information and the LDEV load information from all the MPPKs 120, the display unit displays a tuning screen 60 as shown in FIG. 8 based on the received information. 29 is displayed (step S66).

  Next, a tuning process for transferring the MPPK 120 in charge of LDEV to another MPPK 120 will be described.

  FIG. 14 is a flowchart of tuning processing according to an embodiment of the present invention.

  In the tuning process, the CPU 26 of the management console 20 receives the designation of the LDEV whose charge is to be changed and the designation of the MPPK to be a new charge by the user's operation on the input unit 28 (step S71). In the present embodiment, for example, the CPU 26 receives the designation of the LDEV whose charge is changed and the designation of the MPPK 120 to be newly assigned by the user's operation on the input unit 28 when the tuning screen 60 is displayed.

  Next, the CPU 26 selects the MPPK 120 designated by the user as the destination MPPK 120 (step S72). Next, the CPU 26 transmits an ownership transfer instruction including the LDEV number corresponding to the designated LDEV to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S73).

  The MP 121 of the destination MPPK 120 receives the ownership transfer instruction via the internal network 150. Next, the MP 121 secures the ownership of the migration target LDEV by executing the ownership securing process (step S43). As a result, the MP 121 of the MPPK 120 can execute input / output processing for the LDEV.

  Thereafter, the MP 121 notifies the ownership transfer completion notification to the management console 20 (step S74). The CPU 26 of the management console 20 that has received the ownership transfer completion notification causes the display unit 29 to display a result indicating that the transfer of ownership of the corresponding LDEV has been completed (step S75).

  According to the above tuning processing, the ownership of the LDEV already used can be easily transferred to another MPPK 120. For this reason, the load of the MPPK 120 in the storage system 10 can be easily and appropriately distributed.

  In the storage system 10, when a failure or the like occurs in any of the host I / F unit 100, MPPK 120, shared memory unit 130, disk I / F unit 140, and HDD 170, the failed part is removed and a new one is removed. Replacement (replacement) of attaching a part or a repaired part is performed. The processing of the storage system 10 when such replacement occurs will be described below.

  First, the MPPK replacement process when replacing the MPPK 120 will be described.

  FIG. 15 is a flowchart of MPPK replacement processing according to an embodiment of the present invention.

  In the MPPK replacement process, the CPU 26 of the management console 20 receives an input of the MPPK number to be replaced by a user operation on the input unit 28. Next, the CPU 26 selects the MPPK 120 corresponding to the MPPK number as the destination MPPK 120 (step S81).

  Next, the CPU 26 transmits an MPPK block instruction to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S82).

  The MP 121 of the destination MPPK 120 receives the MPPK block instruction via the internal network 150. Next, the MP 121 identifies the LDEV number of the LDEV to which the MPPK 120 to which the MP 121 belongs has ownership by referring to the lock presence / absence 124a stored in the LM 122. The MP 121 executes the following processing step (step S83) for each LDEV of each LDEV number as a processing target.

  The MP 121 obtains an I / F number and a path name corresponding to the LDEV number to be processed from the LM 122. Next, the MP 121 empties (for example, −1) the MPPK number in the entry including the path name from the management table 102 of the host I / F 101 corresponding to the I / F number. As a result, a new input / output request for the target LDEV from the host I / F 101 can be prevented from being passed to the MPPK 120.

  Further, the MP 121 waits until input / output processing for the LDEV is completed. Here, the completion of the input / output processing for the LDEV can be grasped, for example, because there is no input / output request for the target LDEV in the queue stored in the LM 122 of the MPPK 120. As a result, it is possible to appropriately prevent a situation in which input / output processing on an already accepted LDEV is not executed.

  Thereafter, the MP 121 unlocks the control information of the LDEV in the shared memory 131, that is, stores an empty value (for example, −1) in the lock word 134a of the corresponding LDEV (step S83).

  When the processing for all the LDEVs having ownership is completed, the MP 121 notifies the MPPK blockage completion notification indicating that the blockage of the MPPK is completed and can be replaced with the unlocked LDEV (ownership Including the list of LDEV numbers (unlocked LDEV list) of the LDEV) having been stored in the management console 20 (step S84).

  The CPU 26 of the management console 20 that has received the MPPK blockage completion notification displays the content for requesting the replacement of the MPPK 120 on the display unit 29 and performs a process of confirming whether or not the replacement of the MPPK 120 has been completed (step S85). Whether or not the MPPK 120 has been replaced can be grasped by the CPU 26 communicating with the MPPK 120.

  When the CPU 26 of the management console 20 confirms the replacement of the MPPK 120, the CPU 26 transmits an MPPK restart instruction including the LDEV number included in the unlock LDEV list to the replaced MPPK 120 (step S86). ).

  The MP 121 of the MPPK 120 that has received the MPPK restart instruction executes the following processing step (step S87) for all LDEVs with LDEV numbers included in the MPPK restart instruction as processing targets. That is, the MP 121 locks the control information for the processing target LDEV in the shared memory 131, that is, stores its own MPPK number in the lock word 134a of the target LDEV. Next, the MP 121 acquires the individual control information 134 of the target LDEV from the shared memory 131 and copies it to the LM 122. Also, the MP 121 acquires an entry having the LDEV number of the target LDEV from the LDEV number correspondence table 132 of the shared memory 131 and stores it in the LM 122. In addition, the MP 121 sets the lock presence / absence 124a corresponding to the target LDEV of the LM 122 to be locked, and sets the pointer to the head of the individual control information 124c of the LM 122 in the pointer 124b. Further, the MP 121 acquires an I / F number and a path name corresponding to the LDEV number of the target LDEV from the LDEV number management table 132 of the LM 122. Next, the MP 121 stores its own MPPK number in the MPPK number of the entry including the path name in the management table 102 of the host I / F 101 corresponding to the I / F number (step S87).

  When the processing for all the LDEVs to be processed is completed, the MP 121 transmits an MPPK restart completion notification indicating that the MPPK has been restarted to the management console 20 (step S88).

The CPU 26 of the management console 20 that has received the MPPK restart completion notification causes the display unit 29 to display a result indicating that the MPPK restart has been completed (step S89).
According to this MPPK replacement process, the MPPK 120 after the replacement can have the ownership of the LDEV owned by the MPPK 120 before the replacement, and as with the MPPK 120 before the replacement, Output processing can be executed.

  Next, I / FPK replacement processing when the host I / F unit is replaced will be described.

  FIG. 16 is a flowchart of I / FPK replacement processing according to an embodiment of the present invention.

  In the I / FPK replacement process, the CPU 26 of the management console 20 receives an input of the I / FPK number of the host I / F unit 100 to be replaced by a user operation on the input unit 28. Next, the CPU 26 selects an arbitrary MPPK 120 from the plurality of MPPKs 120 (Step S91).

  Next, the CPU 26 transmits an LDEV list sending instruction including the received I / FPK number to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S92).

  The MP 121 of the destination MPPK 120 receives the LDEV list sending instruction via the internal network 150. Next, the MP 121 reads the I / F of the host I / F 101 belonging to the host I / F unit 100 corresponding to the I / FPK number included in the LDEV list sending instruction from the LDEV number correspondence table 132 stored in the shared memory 131. An entry in which the F number is stored is extracted, and an LDEV list including the extracted entry is created (step S93). Here, the I / F number of the host I / F 101 belonging to the host I / F unit 100 corresponding to the I / FPK number is managed so that, for example, the I / FPK number is included in the I / F number. Can be identified by including the I / FPK number. Further, a table in which the I / FPK number and the I / F number of the host I / F to which the member belongs is prepared in advance in the shared memory 130, and the I / FPK number to the I / F number are prepared using the table. May be specified.

  Next, the MP 121 transmits the created LDEV list to the management console 20 (step S94).

  The CPU 26 of the management console 20 that has received the LDEV list starts execution of a path definition deletion process (step S95) described later for all the LDEVs in the LDEV list. As a result, the paths to all the LDEVs via the host I / F 101 of the host I / F unit 100 to be replaced are deleted.

  After the path deletion is completed, the CPU 26 of the management console 20 displays on the display unit 29 the content for requesting the replacement of the host I / F unit 100, and whether or not the replacement of the host I / F unit 100 is completed. A confirmation process is performed (step S96). Whether or not the host I / F unit 100 has been replaced can be determined by the CPU 26 communicating with the host I / F unit 100.

  When the CPU 26 of the management console 20 confirms the replacement of the host I / F unit 100, the CPU 26 executes the path setting process (step S97) shown in FIG. 10 for all the LDEVs in the LDEV list. Start. As a result, a path similar to that of the host I / F unit 100 before replacement is set, and the same state as before replacement can be reproduced using the replaced host I / F unit 100. After the path setting is completed, the CPU 26 of the management console 20 displays a result indicating that the resumption of the host I / F unit 100 is completed on the display unit 29 (step S98).

  Next, the path definition deletion process (step S95) will be described.

  FIG. 17 is a flowchart of path definition deletion processing according to an embodiment of the present invention.

  In the path definition deletion process, the CPU 26 of the management console 20 receives a path definition deletion request. In the present embodiment, the CPU 26 accepts an LDEV list entry (I / F number, path name, and LDEV number) transmitted from the MPPK 120 as a path definition deletion request. Next, the CPU 26 selects the MPPK 120 that is the transmission destination of the path definition deletion instruction from the plurality of MPPKs 120 (step S101). Here, the CPU 26 may select the MPPK 120 by round robin, for example, or may select it randomly.

  Next, the CPU 26 transmits a path definition deletion instruction including the I / F number, path name, and LDEV number to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S102).

  The MP 121 of the destination MPPK 120 receives the path definition deletion instruction via the internal network 150. Next, the MP 121 acquires from the shared memory 131 the MPPK number of the MPPK 120 having the ownership of the LDEV number of the LDEV number included in the path definition deletion instruction (step S103). The MPPK number of the MPPK 120 having the ownership can be obtained from the lock word 134a of the corresponding LDEV in the shared memory 131.

  Next, the MP 121 determines whether or not the MPPK 120 to which the MPPK 120 belongs has the ownership of the LDEV whose path definition is to be deleted based on whether or not the acquired MPPK number is the MPPK number of the MPPK 120 to which the MPPK 120 belongs ( Step S104).

  As a result, if the acquired MPPK number matches the MPPK number of the MPPK 120 to which the MPPK belongs, and the owner of the LDEV subject to path definition deletion is present (Yes in step S104), the MP 121 is stored in the LM 122. The I / F number and path name corresponding to the LDEV number included in the path definition deletion instruction are acquired from the LDEV number correspondence table 132. Next, the MP 121 deletes the entry including the path name from the management table 102 of the host I / F 101 corresponding to the I / F number. Further, the MP 121 waits until input / output processing for the LDEV is completed. Here, the completion of the input / output processing for the LDEV can be grasped, for example, because there is no input / output request for the target LDEV in the queue stored in the LM 122 of the MPPK 120. As a result, it is possible to appropriately prevent a situation in which input / output processing on an already accepted LDEV is not executed. Thereafter, the MP 121 deletes the entry corresponding to the LDEV number from the LDEV number correspondence table 132 of the LM 122 and the shared memory 131 (step S105). Next, the MP 121 notifies the management console 20 of a path definition deletion completion notification (step S106).

  On the other hand, if the acquired MPPK number does not match the MPPK number of the MPPK 120 to which the MPPK belongs, and does not have the ownership of the LDEV subject to path definition deletion (No in step S104), the information on the LDEV is updated. Since the MPPK number of the MPPK 120 having the acquired ownership is included in the path definition deletion failure notification, it is transmitted to the management console 20 (step S107).

  The CPU 26 of the management console 20 determines whether or not the path definition deletion has been completed, that is, whether or not a path definition deletion completion notification has been received (step S108). A result indicating that the path definition deletion is completed is displayed on the display unit 29 (step S113).

  On the other hand, when the path definition deletion has not ended, that is, when the path definition deletion failure notification is received (No in step S108), the CPU 26 stores the MPPK 120 of the MPPK number included in the path definition deletion failure notification. The destination is selected (step S109), and a path definition deletion instruction including the I / F number, path name, and LDEV number is transmitted to the MPPK 120 (step S110).

  The MP 121 of the MPPK 120 that has received the path definition deletion instruction executes the processing from step S103 to step S105 (step S111). Here, since the MPPK 120 has ownership, processing corresponding to step S105 is executed during step S111. Next, the MP 121 notifies the management console 20 of a path definition deletion completion notification (step S112). Thereafter, the CPU 26 of the management console 20 that has received the path definition deletion completion notification displays a result indicating that the path definition deletion has been completed on the display unit 29 (step S113).

  According to the path definition deletion processing described above, even if the MPPK 120 selected as the destination to which the path definition deletion instruction is first transmitted does not have the corresponding LDEV ownership, the MPPK 120 having the corresponding LDEV ownership is subsequently used. The path definition can be deleted by sending a path definition deletion instruction to. For this reason, the management console 20 does not need to keep track of MPPKs that have LDEV ownership. For this reason, even when the storage system 10 independently transfers the ownership of the LDEV without the involvement of the management console 20, the path definition can be deleted without any trouble.

  Next, when any of the MPPKs 120 is being replaced or when a failure occurs in any of the MPPKs 120, an access securing process for enabling input / output processing on the LDEV for which the MPPK 120 has ownership Will be explained.

  FIG. 18 is a flowchart of access securing processing according to an embodiment of the present invention.

  In the present embodiment, a pair of MPPKs 120 is determined in advance among a plurality of MPPKs 120, and one MPPK 120 is configured to execute input / output processing for the LDEV that the other paired MPPK 120 is in charge of during replacement or the like. Yes.

  In the access securing process, a life / death check is performed to check whether one MPPK 120 (referred to as a replacement MPPK) is operating with respect to another MPPK 120 (referred to as a target MPPK) (step S112). On the other hand, if the target MPPK 120 is operating, it transmits a survival response (step S113a). On the other hand, if the target MPPK 120 is being replaced or a failure has occurred, it transmits a survival response. Cannot be performed (step S113b).

  In the replacement MPPK 120, it is determined whether or not the MP 121 has a survival response from the target MPPK 120 for the confirmation of life and death (step S114). If there is a survival response (Yes in step S114), the processing by the target MPPK 120 is replaced. Since there is no need to perform this, the processing from step S112 is executed after a predetermined time has elapsed.

  On the other hand, when there is no survival response (No in step S114), it means that the input / output processing to the LDEV that the target MPPK 120 was in charge of cannot be performed, so the MP 121 of the replacement MPPK 120 is the target of the shared memory 131. The LDEV locked by the MPPK 120 is referred to. In other words, the MP 121 identifies all LDEVs for which the target MPPK 120 has ownership (step S115).

  Next, the MP 121 executes the following processing for all the specified LDEVs. First, the MP 121 locks the control information of the target LDEV in the shared memory 131, that is, stores its own MPPK number in the lock word 134a of the corresponding LDEV. Next, the MP 121 acquires the individual control information 134 of the target LDEV from the shared memory 131 and copies it to the LM 122. As a result, the individual control information 124c of the corresponding LDEV exists in the LM 122. Also, the MP 121 acquires an entry having the LDEV number of the target LDEV from the LDEV number correspondence table 132 of the shared memory 131 and stores it in the LM 122. In addition, the MP 121 sets the lock presence / absence 124a corresponding to the target LDEV of the LM 122 to be locked, and sets the pointer to the head of the individual control information 124c of the LM 122 in the pointer 124b. Further, the MP 121 acquires an I / F number and a path name corresponding to the LDEV number of the target LDEV from the LDEV number management table 132 of the LM 122. Next, the MP 121 stores its own MPPK number in the MPPK number of the entry including the path name in the management table 102 of the host I / F 101 corresponding to the I / F number (step S116). As a result, the replacement MPPK 120 can secure ownership of the target LDEV, and input / output processing for the target LDEV can be executed instead of the target MPPK 120.

  Next, the 1st modification in one Embodiment of this invention is demonstrated.

  In the embodiment described above, the following LDEV removal process may be executed instead of the LDEV removal process shown in FIG.

  FIG. 19 is a flowchart of LDEV removal processing according to the first modification of the embodiment of the present invention.

  In the LDEV reduction process according to the modified example, the CPU 26 of the management console 20 receives an LDEV reduction request by an operation on the input unit 28 by the user. In the present embodiment, for example, the CPU 26 receives the designation of the LDEV to be removed by the user's operation on the input unit 28 while the LDEV management screen 51 is displayed, and grasps the LDEV number of the corresponding LDEV. Next, the CPU 26 selects the MPPK 120 as the transmission destination of the LDEV removal instruction from the plurality of MPPKs 120 (step S121). Here, the CPU 26 may select the MPPK 120 by round robin, for example, or may select it randomly.

  Next, the CPU 26 transmits an LDEV removal instruction including the received LDEV number to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S122).

  The MP 121 of the destination MPPK 120 receives the LDEV removal instruction via the internal network 150. Next, the MP 121 acquires from the shared memory 131 the MPPK number of the MPPK 120 having the ownership of the LDEV with the LDEV number included in the LDEV removal instruction (step S123). The MPPK number of the MPPK 120 having the ownership can be obtained from the lock word 134a of the corresponding LDEV in the shared memory 131.

  Next, the MP 121 determines whether or not the MPPK 120 to which the MPPK 120 belongs has the ownership of the LDEV to be removed based on whether or not the acquired MPPK number is the MPPK number of the MPPK 120 to which the MPPK 120 belongs (Step S124). ).

  As a result, if the acquired MPPK number matches the MPPK number of the MPPK 120 to which the MPPK belongs, and the ownership of the LDEV to be removed is obtained (Yes in step S124), the MP 121 is stored in the LM 122. The I / F number and path name corresponding to the LDEV number of the LDEV to be removed are obtained from the LDEV number correspondence table 132, and the path name is obtained from the management table 102 of the host I / F 101 corresponding to the I / F number. Delete entries that contain. Furthermore, the MP 121 deletes the individual control information 124c and the LDEV load information 124d for the LDEV to be removed from the LM 122, sets the lock presence / absence 124a corresponding to the LDEV to no lock, and makes the pointer 124b empty. Also, the MP 121 deletes the corresponding LDEV individual control information 134b from the shared memory 131 and releases the lock to the LDEV control information in the shared memory 131, that is, the empty value (for example, the lock word 134a of the corresponding LDEV (for example, , -1) is stored (step S125), and then the MP 121 notifies the management console 20 of an LDEV removal completion notification (step S126).

  On the other hand, if the acquired MPPK number does not match the MPPK number of the MPPK 120 to which it belongs and does not have ownership of the LDEV to be removed (No in step S124), the information related to the LDEV is updated. I can't do it. For this reason, the MP 121 includes the acquired MPPK number of the MPPK 120 having the ownership in the LDEV removal failure notification and transmits it to the management console 20 (step S127).

  The CPU 26 of the management console 20 determines whether or not the LDEV removal has been completed, that is, whether or not the LDEV removal completion notification has been received (step S128), and if the LDEV removal completion notification has been received. Causes the display unit 29 to display a result indicating that the LDEV removal has been completed (step S133).

  On the other hand, when the LDEV removal has not ended, that is, when the LDEV removal failure notification is received, the CPU 26 selects the MPPK 120 of the MPPK number included in the LDEV removal failure notification as the transmission destination. (Step S129), an LDEV removal instruction including the LDEV number is transmitted to the MPPK 120 (Step S130).

  The MP 121 of the MPPK 120 that has received the LDEV removal instruction executes the processing from step S123 to step S125 (step S131). Here, since the MPPK 120 has ownership, processing corresponding to step S125 is executed during step S131. Next, the MP 121 notifies the management console 20 of an LDEV removal completion notification (step S132). Thereafter, the CPU 26 of the management console 20 that has received the LDEV removal completion notification causes the display unit 29 to display a result indicating that the LDEV removal has been completed (step S133).

  According to the LDEV removal processing described above, even when the MPPK 120 selected as the destination to which the LDEV removal instruction is first transmitted does not have the corresponding LDEV ownership, the MPPK 120 having the corresponding LDEV ownership is subsequently used. The LDEV removal instruction can be transmitted to the terminal so that the LDEV can be removed. For this reason, the management console 20 does not need to keep track of MPPKs that have LDEV ownership. For this reason, even when the storage system 10 independently transfers the ownership of the LDEV without the involvement of the management console 20, the LDEV can be reduced without any trouble. Further, the MP 121 that has received the LDEV removal instruction does not need to perform the ownership securing process for securing the ownership from the other MPPK 120 as shown in FIG. 11, so that the load on the MP 121 can be reduced.

  Next, a second modification of the present invention will be described.

  FIG. 20 is a flowchart of the tuning process according to the second modification example of the embodiment of the present invention.

  In the second embodiment, in the above-described embodiment, the management console 20 sets the LDEV and MPPK for which the administrator changes the charge in the tuning process as shown in FIG. Based on the load and the load of the LDEV, the LDEV whose charge is changed and the MPPK 120 which is responsible for the LDEV are automatically determined. It should be noted that the same processing steps as those in FIG.

  In the tuning process according to the second modification, the CPU 26 of the management console 20 selects the LDEV with the highest load as the LDEV whose charge is to be changed based on the load of each MPPK 120 and the load of each LDEV that have already been collected. Then, the MPPK 120 having the lowest load is selected as a new charge (step S142). Next, the CPU 26 of the management console 20 transmits an ownership transfer instruction including the LDEV number corresponding to the selected LDEV to the selected MPPK 120 via the communication I / F 21 and the internal network 150 (step S73).

  Thereafter, when the CPU 26 of the management console 20 receives the ownership transfer completion notification, the CPU 26 of the management console 20 records the contents of the executed LDEV ownership transfer in the log area of the HDD 25 (step S143).

  According to the tuning process, the ownership of the LDEV with the highest load can be transferred to the MPPK 120 with the lowest load, and the load on the MPPK 120 can be distributed without the intervention of the administrator.

  Next, a third modification of the present invention will be described.

  FIG. 21 is a flowchart of the tuning process according to the third modification of the embodiment of the present invention.

  The third modification is obtained by changing the selection method of the LDEV whose charge is changed in the second modification. It should be noted that the same processing steps as those in FIGS. 14 and 20 are denoted by the same reference numerals, and redundant description is omitted.

  In the tuning process according to the third modified example, the CPU 26 of the management console 20 changes an LDEV whose charge is changed to an LDEV that is below a certain threshold and has the highest load, based on the LDEV load that has already been collected. (Step S151), and the subsequent processing is performed. As a result, the MPPK 120 in charge of the LDEV with the highest load can be changed even if it is below a certain threshold.

  According to the above tuning process, the LDEV with the highest load is selected as the LDEV whose load is to be changed, among the LDEVs having a load equal to or lower than a predetermined threshold value, so that the load of the MPPK 120 is maintained while maintaining stability. Can be distributed.

  Next, a fourth modification of the present invention will be described.

  FIG. 22 is a flowchart of load balancing automatic adjustment processing according to a fourth modification of the embodiment of the present invention.

  In the fourth embodiment, the MPPK 120 voluntarily manages what the CPU 26 of the management console 20 requests load information from the MPPK 120 and collects additional information from the MPPK 120 as shown in FIG. The MPPK load information and the LDEV load information are transmitted to the console 20, and the management console 20 performs the same processing as in FIG. 21 based on the LDEV load information and the MPPK load information transmitted from the MPPK 120. It is a thing. In addition, the same number is attached | subjected to the processing step similar to FIG.13 and FIG.21, and the overlapping description is abbreviate | omitted.

  The MP 121 of the MPPK 120 transmits the MPPK load information to the management console 20 at an arbitrary time (step S161), and further transmits LDEV load information to the management console 120 (step S162). Note that the MP 121 of each MPPK 120 may transmit its own MPPK load information and LDEV load information to the management console 120, and any one MPPK 120 collects MPPK load information and LDEV load information from other MPPKs 120. Alternatively, they may be collectively transmitted to the management console 120.

  Next, the CPU 26 of the management console 20 starts subsequent processing based on the MPPK load information and the LDEV load information transmitted from the MPPK 120.

  According to this process, the load of the MPPK 120 can be distributed without the intervention of the administrator.

  As mentioned above, although this invention was demonstrated based on one Embodiment, this invention is not restricted to embodiment mentioned above, It can apply to other various aspects.

  For example, in each of the above embodiments, the HDD has been described as an example of the storage device. However, the present invention is not limited to this. For example, at least a part or all of the HDD may be a DVD drive or a magnetic tape drive. Alternatively, another storage device capable of storing data such as a flash memory device may be replaced.

  In the above embodiment, the LDEV addition setting and the path setting are executed at different timings. However, the present invention is not limited to this, and the LDEV addition setting and the path setting are performed simultaneously. It may be. For example, when an LDEV addition request is received (step S11), information required for path setting (I / F #, path name) is received, and the LDEV is added together with information required for path setting in the LDEV addition instruction. It is only necessary to transmit to the MP 121 of the MPPK 120 in charge (step S12), and the MP 121 performs the storage processing (step S13, step S25) of the RAID group configuration information and the LDEV number correspondence table. If path setting is performed simultaneously in this way, information necessary for path setting can be sent directly to the MPPK 120 in charge of the LDEV, and therefore processing that considers the case where it is transmitted to the MPPK 120 other than the charge (for example, S29) ~ S31) need not be performed. For this reason, it is possible to reduce the processing load in path setting and to shorten the time for path setting.

  In the above embodiment, the CPU 26 of the management console 20 performs the load distribution process. However, the present invention is not limited to this, and for example, any of the processes executed by the CPU 26 of the management console 20 is performed. The MP 121 of the MPPK 120 may be executed. In the above embodiment, the MPPK 120 having the lowest load is selected from all the MPPKs 120. However, the present invention is not limited to this. For example, the MPPK 120 selected by the administrator in advance is selected. It may be.

  In the above embodiment, the MPPK 120 is provided with a plurality of MPs 121. However, the present invention is not limited to this, and for example, one MP 121 may be provided.

  In the above embodiment, one of the paired MPPKs 120 secures the access right to the LDEV handled by the other when the other cannot operate. However, the present invention is not limited to this, When any of the other MPPKs 120 cannot operate, the MPPK 120 may secure the access right to the LDEV that the MPPK 120 is in charge of. You may make it ensure the access right with respect to LDEV which the MPPK120 takes charge of.

10 storage system, 20 management console, 100 host I / F unit, 101 host I / F, 120 MPPK, 121 MP, 122 LM, 130 shared memory unit, 140 disk I / F unit, 141 disk I / F, 150 internal Network, 170 HDD.

Claims (10)

A storage device that is connected to a host computer and a management computer and performs input / output processing for a plurality of logical storage devices to which at least some storage areas of the plurality of storage devices are allocated,
A plurality of first interface units each receiving an input / output request from the host computer to the logical storage device;
A second interface unit connected to the storage device and performing data input / output processing with the storage device;
A plurality of control units having at least one processor for controlling input / output processing for the storage area of the logical storage device via the second interface unit; and control of input / output processing for the storage area of the logical storage device. A shared memory having first management information including an identifier of the control unit in charge, information on a path to the logical storage device, and an identifier of the first interface unit related to the path;
Each of the plurality of first interface units includes:
The second management information, which is responsible for controlling the input / output processing for the storage area of the logical storage device and includes the identifier of the control unit that is the destination of the input / output request received from the host computer, A request delivery unit that delivers the input / output request to the control unit in charge of input / output processing of the logical storage device based on the second management information,
The control unit selected from the plurality of control units specifies a logical storage device corresponding to a path related to the first interface unit to be replaced from the first management information,
For each specified logical storage device, the control unit in charge of the logical storage device deletes the path corresponding to the logical storage device,
For the first interface unit after replacement, for each of the specified logical storage devices, the control unit in charge of the logical storage device sets a path corresponding to the logical storage device.
A storage device. The storage device according to claim 1,
When each of the plurality of control units receives a path deletion instruction,
If the logical storage device corresponding to the path specified in the path deletion instruction is not the logical storage device that the user is in charge of, the management computer is notified of the deletion failure,
If the logical storage device corresponding to the path specified in the path deletion instruction is the logical storage device that the user is in charge of, delete that path.
A storage device. The storage apparatus according to claim 1 or 2,
When each of the plurality of control units receives a path setting instruction,
If the logical storage device corresponding to the path specified by the path setting instruction is not the logical storage device that is in charge of itself, the management computer is notified of the setting failure,
If the logical storage device corresponding to the path specified in the path setting instruction is the logical storage device that the user is in charge of, set the path.
A storage device. The storage apparatus according to any one of claims 1 to 3,
Each of the plurality of control units, when deleting the specified path, notifies the management computer of the deletion completion,
When deletion completion is notified for each specified logical storage device, the replacement-target first interface unit can be replaced.
A storage device. The storage apparatus according to any one of claims 1 to 4,
When at least one of the path deletion for each specified logical storage device, the replacement of the first interface unit to be replaced, and the path setting for each specified logical storage device is completed, a result is obtained. Notify the management computer;
A storage device. A management method for a storage device connected to a host computer and a management computer and performing input / output processing for a plurality of logical storage devices to which at least some storage areas of the plurality of storage devices are allocated,
The storage device is
A plurality of first interface units each receiving an input / output request from the host computer to the logical storage device;
A second interface unit connected to the storage device and performing data input / output processing with the storage device;
A plurality of control units having at least one processor for controlling input / output processing for the storage area of the logical storage device via the second interface unit; and control of input / output processing for the storage area of the logical storage device. A shared memory having first management information including an identifier of the control unit in charge, information on a path to the logical storage device, and an identifier of the first interface unit related to the path;
Each of the plurality of first interface units includes:
The second management information, which is responsible for controlling the input / output processing for the storage area of the logical storage device and includes the identifier of the control unit that is the destination of the input / output request received from the host computer, A request delivery unit that delivers the input / output request to the control unit in charge of input / output processing of the logical storage device based on the second management information,
The storage device management method includes:
A logical storage device corresponding to a path related to the first interface unit to be replaced is identified from the first management information,
For each specified logical storage device, the control unit in charge of the logical storage device deletes the path corresponding to the logical storage device,
For the first interface unit after replacement, for each of the specified logical storage devices, the control unit in charge of the logical storage device sets a path corresponding to the logical storage device.
A storage apparatus management method. The storage apparatus management method according to claim 6, comprising:
For each of the specified logical storage devices, if the logical storage device corresponding to the path specified in the path deletion instruction is not the logical storage device in charge of the control unit that has received the path deletion instruction, the deletion failure is indicated. If the control unit notifies the management computer, and the logical storage device corresponding to the path specified in the path deletion instruction is a logical storage device in charge of the control unit that has received the path deletion instruction, The controller deletes the path,
A storage apparatus management method. A storage apparatus management method according to claim 6 or 7,
For each of the specified logical storage devices, if the logical storage device corresponding to the path specified in the path setting instruction is not the logical storage device in charge of the control unit that has received the path setting instruction, the setting failure is indicated. If the control unit notifies the management computer, and the logical storage device corresponding to the path specified in the path setting instruction is a logical storage device in charge of the control unit that has received the path setting instruction, The control unit sets the path,
A storage apparatus management method. The storage apparatus management method according to any one of claims 6 to 8, comprising:
When the management computer receives the completion of deletion of the specified path from the control unit for each of the specified logical storage devices, it displays a request for replacement of the first interface unit to be replaced.
A storage apparatus management method. The storage apparatus management method according to any one of claims 6 to 9,
When at least one of the path deletion for each specified logical storage device, the replacement of the first interface unit to be replaced, and the path setting for each specified logical storage device is completed, a result is obtained. Displayed by the management computer,
A storage apparatus management method.

Images