WO2016056050A1

WO2016056050A1 - Computer system and system for managing same

Info

Publication number: WO2016056050A1
Application number: PCT/JP2014/076698
Authority: WO
Inventors: 崇之永井; 味松　康行
Original assignee: 株式会社日立製作所
Priority date: 2014-10-06
Filing date: 2014-10-06
Publication date: 2016-04-14

Abstract

　In the present invention, a computer system has a plurality of host computers, each having at least one physical host port, and a storage system that is one or a plurality of storage devices, each having a plurality of storage ports. The physical host ports and the storage ports are connected in a one-to-one relation. Each of at least two host computers among the plurality of host computers can construct a Logical PARtition (LPAR) having a virtual host port. The storage system applies a first access control list indicating a first LPAR, for which access to a first logical volume used by the first LPAR is allowed, to each of at least two storage ports among the plurality of storage ports that the storage system has.

Description

Computer system and its management system

The present invention relates to control of access to a logical volume.

In a storage network, it is desirable to limit access to LUN (Logical Unit Number) to specific host computers. This is because if the software (including the operating system) on the host computer erroneously accesses a LUN (logical volume) that should not be accessed (I / O (Input / Output)), the data on the LUN is updated incorrectly. It is because it may be done.

Therefore, the LUN masking function is generally used as a technique for limiting access to the LUN to a specific host computer. This is realized by creating an access control list for the LUN for each port of the storage apparatus. The LUN access control list includes the WWN (World Wide Name) of the physical port of FC-HBA (Fibre Channel-Host Bus Adapter) that is allowed to access the LUN in the storage.

On the other hand, a plurality of logical partitions (hereinafter referred to as LPAR (Logical Partition)) are constructed on one physical host, each LPAR is regarded as an individual virtual host, and an OS (Operating System) is executed on that. Virtual computer systems that can be operated have been put into practical use. Thereby, one physical host can be operated as a plurality of independent hosts.

As a method for realizing an I / O request from an LPAR (virtual computer such as a virtual host), the hypervisor once accepts an I / O request issued from an OS (hereinafter referred to as a guest OS) on the LPAR, A method of re-execution via the OS on which the visor is operating or another OS dedicated to proxy execution (hereinafter referred to as I / O emulation method), and direct physical I / O device from the guest OS On the other hand, there is a method for requesting I / O execution (hereinafter referred to as an I / O pass-through method).

Regarding the LPAR live migration process in the I / O pass-through method, in Patent Document 1, the WWN of the HBA assigned to the migration target LPAR is taken over by the migration destination LPAR. As a result, access to the LUN from the migration destination LPAR can be continued without updating the LUN access control list in the storage apparatus.

Japanese Patent Laid-Open No. 2014-041395

In Patent Document 1, it is assumed that the HBA and the FC (Fibre Channel) port of the storage device are connected via an FC switch. For this reason, the storage ports that receive I / O requests issued from the LPAR are the same before and after the LPAR migration due to the function of the FC switch. An access control list for a LUN is applied in units of storage ports (for example, an access control list is assigned to a storage port). As described above, a storage port that receives an I / O request specifying the same LUN is LPAR migration. Therefore, the same LUN can be accessed from the LPAR even after LPAR migration.

On the other hand, if the storage port of the storage device and the physical port of the host computer are directly connected to each other by an FC cable or a PCIe (Peripheral Component Interconnect Express) bus (in other words, the storage port and the physical port correspond 1: 1) Storage port that receives an I / O request issued from the LPAR before and after the LPAR migration. An access control list that permits access from the LPAR to the LUN is not applied to a storage port that receives an I / O request from the LPAR after LPAR migration. Therefore, access from the LPAR to the LUN is impossible.

The computer system has a plurality of host computers each having at least one physical host port, and a storage system that is one or a plurality of storage devices each having a plurality of storage ports. The physical host port and the storage port are connected in a 1: 1 relationship. Each of at least two of the plurality of host computers can construct an LPAR having a virtual host port. The storage system has a first access control list indicating a first LPAR that is permitted to access the first logical volume used by the first LPAR, and at least two storages of the plurality of storage ports that the storage system has Applies to each of the ports. The storage system can apply the access control list to the storage port in response to an instruction from the management system of the computer system.

In an environment where the physical host port and storage port are directly connected, the migration destination LPAR can access the same logical volume even if the LPAR migration is executed without changing the setting of the storage system.

1 shows a physical configuration of a computer system according to a first embodiment. The structural example of a host computer is shown. 2 shows a configuration example of a storage apparatus. The structural example of a management server is shown. A connection configuration example of a plurality of host computers and a storage apparatus is shown. 2 shows a configuration example of an I / O port management table possessed by a host computer. 2 shows a configuration example of an LPAR management table held by a host computer. An example of the configuration of the LPAR management table of another host computer is shown. 2 shows an example of the configuration of a port management table that a storage apparatus has. The structural example of the host group management table | surface which a storage apparatus has is shown. 2 shows an example of the configuration of a RAID group management table that a storage apparatus has. The structural example of the volume management table which a storage apparatus has is shown. The structural example of the host group-volume related management table | surface which a storage apparatus has is shown. The structural example of the table size upper limit management table | surface which a storage apparatus has is shown. The structural example of the apparatus management table | surface which a management server has is shown. The structural example of the apparatus management table | surface which a management server has is shown. The structural example of the host-storage path management table which a management server has is shown. It is a part of flowchart of the LPAR creation process which the apparatus management module of a management server implements. It is the remainder of the flowchart of the LPAR creation process performed by the device management module of the management server. It is a flowchart of a LPAR migration process. 10 shows a configuration example of a resource group management table that a management server according to a second embodiment has. The difference from the LPAR creation processing according to the first embodiment in the LPAR creation processing according to the second embodiment will be described. 10 shows a configuration example of an LPAR operation schedule management table possessed by a host computer according to a third embodiment.

10 schematically shows LPAR scheduling processing (including creation and deletion of a host group) according to a third embodiment.

Hereinafter, embodiments will be described with reference to the drawings.

In the following description, the information of the embodiment will be described using expressions such as “aaa table” and “aaa list”, but these may be expressed in other than data structures such as tables and lists. Therefore, “aaa table”, “aaa list”, and the like can be referred to as “aaa information” to indicate that they do not depend on the data structure.

Also, in the following description, at least one of “name” and “ID” is used as an example of identification information of each information element, and these can be replaced with each other.

Further, in the following description, when explaining without distinguishing the same type of elements, names and reference signs are used (for example, the host computer 10000), and when explaining the same kind of elements separately, they are assigned to the elements. The identification information may be used (for example, HOST1).

In the following description, the process may be described with “program” as the subject, but the program performs the process defined by being executed by the processor using the memory and the communication port (communication control device). Therefore, the description of the processing may be a description of processing with the processor as the subject. Further, the processing disclosed with the program as the subject may be processing performed by a device (for example, a management system or a storage device) having a processor that executes the program. Further, part or all of the program may be realized by dedicated hardware. Various programs may be installed in each computer by a program distribution server or a storage medium.

FIG. 1 shows a physical configuration of a computer system according to the first embodiment.

The computer system has a storage device 20000 and a plurality of host computers 10000. A storage device 20000 and a plurality of host computers 10000 are connected to each other by a PCIe bus 46000. A plurality of host computers 10000 are mounted on the server chassis 15000. A storage server 20000 and a plurality of host computers 10000 are connected to a management server 30000 via a management network 45000. A management client 35000 of the management server 30000 and a service processor (SVP) 16000 mounted on the server chassis 15000 are also connected to the management network 45000. The management network 45000 is a communication network such as a LAN (Local Area Network).

The host computer 10000 receives, for example, a file I / O request from a client computer (not shown) and accesses the storage device 20000 based on the request (transmits an I / O request to the storage device 20000). A built-in network (for example, LAN) 47000 exists inside the server chassis 15000. The service processor 16000 is an example of a controller, and manages each host computer 10000 via the internal network 47000. The service processor 16000 may issue a failover instruction to at least one of the LPAR migration source and migration destination host computers 10000. The failover instruction is an instruction for migrating the LPAR from the migration source host computer to the migration destination host computer. For example, the failover (migration) target LPAR ID, the failover source host computer ID, and the migration destination host And a computer ID. The service processor 16000 is connected to the maintenance port 16100 inside the server chassis 15000 via a circuit such as an internal bus. By directly connecting a maintenance terminal to the maintenance port 16100, the administrator can operate the service processor 16000 without going through the management network 45000.

The management server 30000 is an example of a management system, and manages the computer system via the management network 45000. The management server 30000 can also issue a failover instruction to at least one of the LPAR migration source and migration destination host computers 10000. In other words, each host computer 10000 can receive a failover instruction from at least one of the service processor 16000 and the management server 30000. As a result, the service processor 16000 can detect a predetermined event in the server chassis 15000 and automatically perform a failover without an instruction from the management server 30000. In response to an instruction from the management server 30000 (for example, Failover can also be performed in response to a manual operation by the operator (administrator) of the management client 35000.

The management client 35000 is a computer that communicates with the GUI display processing module 32300 of the management server 30000 via the management network 45000 and displays various information on the WEB browser. The administrator manages devices in the computer system by referring to information displayed on the WEB browser on the management client. However, the management server 30000 and the management client 35000 may be configured by one server.

FIG. 2 shows a configuration example of the host computer 10000.

The host computer 10000 includes a management port 11100 connected to the management network 45000, a port 11000 connected to the internal network 47000, one or more I / O ports 14000 connected to the storage device 20000 via the PCIe bus, A memory 13000 and a processor 12000 are included, and these are connected to each other via a circuit such as an internal bus. The processor 12000 may be composed of one or more processors. The memory 13000 may be configured with one or more memories and may include a storage device such as an auxiliary storage device.

The memory 13000 stores an operating system 13100, an LPAR management program 13200, an I / O port management table 13300, an LPAR management table 13400, and an LPAR operation schedule management table 13500.

The LPAR management program 13200 logically divides physical resources (computer resources) such as the processor 12000 and the memory 13000 provided from the operating system 13100 to create an LPAR. The LPAR can also be called a management computer. The LPAR created by the LPAR management program 13200 recognizes a logical volume on the storage apparatus 20000 connected to the host computer 10000 as a storage area via the PCIe bus 46000.

In FIG. 2, the LPAR management program 13200 is described as existing in the memory 13000. However, the LPAR management program does not exist and the storage area provided by the operating system 13100 is used, and the I / O is stored in the storage area. A business application that performs O may exist instead. That is, there may be a host computer 10000 that cannot construct (execute) an LPAR.

In FIG. 2, the LPAR management program 13200 is described as existing in the memory 13000, but a virtualization control program exists instead of the LPAR management program, and the virtualization control program includes the processor 12000 and the memory 13000. It may take the form of providing virtual hardware to a virtual machine by abstracting and standardizing physical resources. In that case, the LPAR in the following description corresponds to a virtual machine, and the virtualization control program corresponds to an LPAR management program.

FIG. 3 shows a configuration example of the storage apparatus 20000.

The storage device 20000 is an example of a storage system, and a plurality of storage ports 21000 for connecting to the host computer 10000 via the PCIe bus 46000 and a management port 21100 for connecting to the management server 30000 via the management network 45000. And a memory 23000 for storing programs and management information, a RAID (RAID (Redundant Arrays of Inexpensive (or Independent) Disks)) group 24010 for storing data, and the data and management memory in the memory And a controller 25000 for controlling management information, which are connected to each other via a circuit such as an internal bus, etc. The memory 23000 may be composed of one or more memories, and the auxiliary storage device. Memory like A device may be included.

The memory 23000 includes a disk management program 23100, a port management table 23200, a host group management table 23300, a RAID group management table 23400, a volume management table 23500, a host group-volume related management table 23600, and a table size upper limit. The management table 23700 is stored. The disk management program 23100 communicates with the management server 30000 via the management port 21100, and with respect to the management server 30000, the port management table 23200, the host group management table 23300, the RAID group management table 23400, and the volume management table 23500. And the information included in at least one of the host group-volume related management table 23600 and the table size upper limit management table 23700 is provided to the storage apparatus 20000.

The RAID group 24010 includes a plurality of nonvolatile storage devices 24220. Instead of the RAID group 24010, one non-volatile storage device 24220 may be employed. A logical volume 24110 is provided based on one or more nonvolatile storage devices 24220 such as a RAID group 24010. The at least one logical volume 24110 may be a virtual logical volume such as a virtual volume according to Thin Provisioning.

The controller 25000 includes a processor that controls the storage device 20000 and a cache memory that temporarily stores data exchanged with the host computer 10000. Each controller 25000 is interposed between the storage port 21000 and the RAID group 24010, and exchanges data between them.

The storage system 20000 receives an access request (indicating an I / O request) specifying the logical volume 24110 provided to the host computer 10000 and receives the logical volume 24110 (for example, the storage device that is the basis of the logical volume 24110) 3 and the above-described storage device that provides the storage area, configurations other than those described in FIG. 3 and the above description may be used. For example, the storage controller and the storage device that provides the storage area are in separate housings. It may be stored in the body. For example, the memory 23000 and the controller 25000 may be storage controllers. Further, when the storage controller and the storage device exist in the same casing, or as an expression including another casing, the storage apparatus may be referred to as a storage system. The storage system may be a plurality of storage devices.

FIG. 4 shows a configuration example of the management server 30000.

The management server 30000 is an example of a management system, and a management port 31000 for connecting to the management network 45000, a processor 31100, a storage resource 33000, and an output device 31200 such as a display device for outputting processing results to be described later. And an input device 31300 such as a keyboard for an administrator to input instructions, which are connected to each other via a circuit such as an internal bus. Note that the storage resource 33000 may be one or more memories (for example, a semiconductor memory) or a mixture of non-volatile storage devices.

The management program 32000 is stored in the storage resource 33000. The management program 32000 includes a device management module 32100, a device communication module 32200, and a GUI display processing module 32300. Each module is provided as a program module of the storage resource 33000, but may be provided as a hardware module. Further, the management program 32000 may not be configured by modules as long as the processing of each module can be realized. In other words, the description of each module in the following description may be replaced with the description related to the management program 32000.

The storage resource 33000 further stores a device management table 33200, a host-storage path management table 33300, and a configuration table 93400. Configuration information is stored in the configuration table 93400. As an example of the configuration information, each item of the I / O port management table 13300 collected from each host computer 10000 managed by the device communication module 32200, each item of the LPAR management table 13400, and the LPAR operation schedule management table 13500 , Each item of the port management table 23200 collected from each managed storage, each item of the host group management table 23300, each item of the RAID group management table 23400, and each item of the volume management table 23500 And each item of the host group-volume relation management table 23600 and each item of the table size upper limit management table 23700. The configuration table 93400 may not store all the tables of the management target device or all the items in the table. The data representation format and data structure of each item stored in the configuration table 93400 may not be the same as that of the management target device. When the management program 32000 receives these items from the management target device, the management program 32000 may receive the items in the data structure or data representation format of the management target device.

The device communication module 32200 periodically or repeatedly accesses the managed device under management, and acquires configuration information of each component in the managed device. It should be noted that when the execution instruction is repeatedly issued, it is not necessarily strictly every fixed period, and it is only necessary to repeat it. Further, the device communication module 32200 instructs the managed device under management to change the configuration in response to a request from the administrator. After instructing the management target device to change the configuration, the configuration information of each component in the management target device is reacquired, and the configuration information stored in the configuration table 93400 is kept up-to-date.

The GUI display processing module 32300 displays the acquired configuration management information via the output device 31200 in response to a request from the administrator via the input device 31300. The input device and the output device may be separate devices, or one or more integrated devices.

The management server (management computer) has, for example, a display, a keyboard, a pointer device, and the like as input / output devices, but may be other devices. Further, a serial interface or an Ethernet interface is used as an alternative to the input / output device, and a display computer (for example, a management client 35000) having a display, a keyboard, or a pointer device is connected to the interface, and the display information is connected to the display computer. The input and display on the input / output device may be substituted by transmitting or receiving input information from the display computer to display on the display computer or accepting input.

In this specification, a set of one or more computers that manage a computer system (information processing system) and display display information can be referred to as a “management system”. A management computer that displays display information on a display device or a remote display computer can be called a management system, and a combination of a management computer and a display computer (for example, the management client 35000 in FIG. 1) can also be called a management system. it can. Further, in order to increase the processing speed and reliability, a plurality of computers may realize processing equivalent to that of the management computer. In this case, a plurality of computers (including display computers) are referred to as a management system. be able to.

FIG. 5 shows a connection configuration example of a plurality of host computers 10000 and a storage apparatus 20000.

PORT11 to PORT16 (multiple I / O ports 14000) of HOST1 to HOST3 are connected to PORT1 to PORT6 (multiple storage ports 21000) of storage device (SYS1) 20000 via PCIe bus 46000, respectively. Yes. In this embodiment, the host computer and storage I / O ports are connected by the PCIe bus, but the host computer and storage I / O ports need only be connected one-to-one. It may be connected by other means such as a cable. The number of PCIe buses connecting the I / O ports of the host computer and the storage device is not necessarily one per I / O port, and a plurality of I / O ports may be shared by one PCIe bus.

An example of the outline of the present embodiment will be described with reference to FIG. VOL1 is an example of the first logical volume, the access control list 21050 is an example of the first access control list, and each of the PORT11 to PORT16 is an example of the I / O port (physical host port) 14000. Each of PORT1 to PORT6 is an example of a storage storage port 21000, and LPAR1 is an example of a first LPAR. LPAR1 has a virtual host port, and VWWN1 is assigned to the virtual host port. VWWN is the WWN (World Wide Name) of the virtual host port.

The storage system, for example, in accordance with an instruction from the management server 30000, displays an access control list 21050 describing VWWN1 of LPAR1 that is permitted to access VOL1 used by LPAR1. Applies to each of the two storage ports. The at least two storage ports are a PORT1 connected to the PORT11 of the HOST1 that executes the LPAR1, and a storage port connected to a physical host port of another host computer capable of executing the LPAR that can be a migration destination of the LPAR1. In the example of FIG. 5, the access control list 21050 is applied to all storage ports other than PORT 1 in addition to PORT 1. LPAR1 can be migrated to either HOST2 or HOST3.

If either HOST2 or HOST3 is a host computer that cannot construct (execute) an LPAR, it may not be applied to the access control list 21050 for a storage port connected to the physical host port of the host computer. This is because such a host computer cannot be a migration destination of LPAR.

According to this embodiment, in the environment where the host I / O port (host computer I / O port) and the storage I / O port (storage device I / O port) are directly connected, there is no change in the storage device settings. Even if LPAR1 is migrated to either HOST2 or HOST3, LPAR1 can access VOL1 from the migration destination HOST2 or HOST3.

FIG. 6 shows a configuration example of the I / O port management table 13300 that the host computer 10000 has.

The I / O port management table 13300 includes a field 13310 for registering a device ID (host computer identifier), a field 13320 for registering an ID (I / O port identifier in the host computer), and an I / O port WWN. And a field 13340 for registering the type of I / O port. According to FIG. 6, for example, HOST 1 has PORT 11, PORT 11 has a WWN “11: 00: 00: 00: 00: 00: 01”, and PORT 11 is an I / O port for PCIe. is there.

FIG. 7A shows a configuration example of the LPAR management table 13400. FIG. 7A shows a configuration example of the LPAR management table 13400 of HOST 1 (FIG. 7B will be described later). In FIG. 7A, the number of processors is expressed as “NP”, the memory size is expressed as “MS”, and whether migration is possible is expressed as “Flag”.

The LPAR management table 13400 includes a field 13410 for registering a device ID (host computer identifier), a field 13420 for registering an ID (identifier of LPAR in the host computer), and the number of processors (number of processors assigned to the LPAR). ), A field 13440 for registering the memory size (the size of the memory allocated to the LPAR), a field 13450 for registering the virtual WWN (virtual WWN of the virtual host port of the LPAR), and the physical port ID A field 13460 for registering (the ID of the physical host port assigned to the LPAR), a field 13470 for registering the state (whether or not the LPAR is activated on the host computer), and other hosts of the LPAR And a field 13480 for registering the migration flag for. According to FIG. 7A, two processors, 4 GB of memory, and PORT1 are allocated to LPAR1 on HOST1, and LPAR1 is a virtual WWN “12: 00: 00: 00: 00: 00: 01” Have virtual host ports.

FIG. 8 shows a configuration example of the port management table 23200 that the storage apparatus 20000 has.

The port management table 23200 includes a field 23210 for registering a device ID (storage device identifier), a field 23420 for registering an ID (I / O port identifier in the storage device), and a WWN (I / O in the storage device). A field 23230 for registering the WWN possessed by the port, and a field 23240 for registering the type (type of I / O port in the storage apparatus). According to FIG. 8, PORT1 on the storage device (SYS1) has a WWN of “21: 00: 00: 00: 00: 00: 01”, and PORT1 is an I / O port for PCIe. .

FIG. 9 shows a configuration example of the host group management table 23300 that the storage apparatus 20000 has.

The host group management table 23300 includes a field 23310 for registering a device ID (storage device identifier), a field 23320 for registering an ID (host group identifier), and a port ID (storage I / O associated with the host group). A field 23330 for registering a port identifier) and a field 23340 for registering a connection permission WWN (a WWN of a virtual port registered in the host group). One record of the host group management table 23300 is an example of an access control list. According to FIG. 9, the virtual WWN “12: 00: 00: 00: 00: 00: 01” is associated with the host group (HG1) in the storage device (SYS1), and the access applied to PORT1. The control list has a virtual WWN “12: 00: 00: 00: 00: 00: 01” as the WWN of the virtual host port of the LPAR to which access is permitted.

FIG. 10 shows a configuration example of the RAID group management table 23400 that the storage device 20000 has.

The RAID group management table 23400 includes a field 23410 for registering a device ID (storage device identifier), a field 23420 for registering an ID (RAID group identifier), and a field 23430 for registering a RAID level (RAID group RAID level). And a field 23440 for registering a PDEV ID (identifier of each nonvolatile storage device constituting a RAID group) and a field 23450 for registering a capacity (capacity of a RAID group). According to FIG. 10, the RAID group (RG1) on the storage device (SYS1) has a RAID level of RAID1 and a capacity of 100 GB.

FIG. 11 shows a configuration example of the volume management table 23500 that the storage device 20000 has.

The volume management table 23500 includes a field 23510 for registering an apparatus ID (storage apparatus identifier), a field 23520 for registering ID (logical volume identifier), a field 23530 for registering capacity (logical volume capacity), and a RAID. A field 23540 for registering a group ID (identifier of a RAID group on which a logical volume is based), a field 23550 for registering a host ID (identifier of a logical volume allocation destination host), and an LPAR ID (logical volume allocation destination) Field 23560 for registering the identifier of the LPAR). According to FIG. 11, VOL1 of the storage device (SYS1) has a capacity of 20 GB, is based on the RAID group (RG1), and is assigned to LPAR1 of HOST1.

FIG. 12 shows a configuration example of the host group-volume related management table 23600 that the storage device 20000 has.

The host group-volume relation management table 23600 includes a field 23610 for registering a device ID (storage device identifier), a field 23620 for registering a volume ID (logical volume identifier), and a host group ID (associated with a logical volume). And a field 23630 for registering a host group identifier). According to FIG. 12, the host group (HG1) in the storage apparatus (SYS1) is associated with VOL1.

FIG. 13 shows a configuration example of the table size upper limit management table 23700 that the storage apparatus 20000 has.

The table size upper limit management table 23700 includes a field 23710 for registering a device ID (storage device identifier), a field 23720 for registering a table name (management table name in the storage device), and a record upper limit number (defined in the management table). And a field 23730 for registering the maximum number of possible records). According to FIG. 13, 256 records can be registered per storage I / O port in the host group management table 23300. That is, the number of access control lists applicable to one storage I / O port is 256.

FIG. 14A shows a configuration example of the device management table 33200 that the management server 30000 has.

The volume management table 23500 includes a field 33210 for registering a device ID (host computer or storage device identifier), a field 33220 for registering a type (whether the device is a host computer or a storage device), and a management IP address ( A field 33230 for registering the IP address of the apparatus, and a field 33240 for registering the host virtualization mode (whether the LPAR management program is installed in the host computer and the LPAR can be constructed in the host computer). According to FIG. 14A, the IP address of HOST1 is “192.168.11.13”, and the LPAR management program is installed in HOST1. 14B is also a device management table, but FIG. 14B will be described later.

FIG. 15 shows a configuration example of the host-storage path management table 33300 that the management server 30000 has.

The host-storage path management table 33300 includes a field 33310 for registering a path ID (path identifier such as a PCIe bus that directly connects the host I / O port and the storage I / O port), and a storage ID (storage device identifier). Register field 33320, register port ID (storage I / O port identifier) field 33330, and connect destination host port ID (host I / O port identifier directly connected to storage I / O port). A field 33340, and a field 33350 for registering a connection destination host ID (an identifier of a host computer having a host I / O port). According to FIG. 15, there is a path (PATH 1) that directly connects the PORT 11 of the HOST 1 to the PORT 1 of the storage apparatus (SYS 1).

In the host-storage path management table 33300, only paths in which a host I / O port and a storage I / O port are directly connected by a PCIe bus or the like are registered. The I / O port connected to the FC switch is not registered in this table. In addition, the host-storage path management table 33300 can be constructed on the management server 30000 by an administrator input through the input device 34100 of the management server 30000 or by the management server 30000 obtaining from the storage apparatus 20000.

FIGS. 16A and 16B are flowcharts of the LPAR creation process performed by the device management module 32100 of the management server 30000. FIG.

Through the GUI provided by the GUI display processing module 32300, the device management module 32100 receives the ID of the host computer in which the LPAR is defined, the number of processors to be allocated to the LPAR to be defined (created), and the memory from the administrator. The size is designated (step 61010).

In addition, the device management module 32100 receives the designation of the host I / O port ID assigned to the LPAR from the administrator through the GUI provided by the GUI display processing module 32300 (step 61020). By assigning a host I / O port to an LPAR, a virtual host port (virtual WWN) is assigned.

Next, the device management module 32100 refers to the device management table 33200, identifies the IP address of the host computer specified in Step 61010, and sends the specified IP address to the LPAR management program 13200 on that host. And LPAR creation instruction is transmitted (step 61030). The LPAR creation instruction is an instruction to create an LPAR, and includes, for example, the number of processors to be allocated to the LPAR, a memory size, and a host I / O port ID. If the instruction destination host does not have the number of processors and memory size included in the instruction, or if there is no LPAR construction function (that is, the host virtualization mode corresponding to the destination host is “No”). In the case of a host), the LPAR management program 13200 may return an error message to the device management module 32100.

When the LPAR management program 13200 has successfully created the LPAR in response to the LPAR creation instruction, the LPAR management program 13200 updates the LPAR management table 13400. As a result, a record corresponding to the created LPAR is added to the LPAR management table 13400 (a virtual WWN or the like of the created LPAR is registered in the LPAR management table 13400). The device management module 32100 receives a notification of the virtual WWN assigned to the created LPAR from the LPAR management program 13200 (step 61040).

Next, the device management module 32100 refers to the host-storage path management table 33300, the host ID column matches the host ID specified in step 61010, and the port ID is the host specified in step 61020. A record matching the I / O port ID is searched (step 61050).

If there is no corresponding record (step 61060: No), the LPAR creation process ends. In this case, for example, the host I / O port may be connected to the SAN. In this case, for example, the administrator can separately create a law and a group in normal SAN operation.

When the corresponding record exists (step 61060: Yes), the device management module 32100 refers to the host-storage path management table 33300 and stores the storage I / O directly connected to the host I / O port specified in step 61020. The ID of the O port and the ID of the storage having the storage I / O port are specified (step 61070). That is, the storage I / O port specified in step 61070 is a storage I / O port directly connected to the host I / O port of the host having the created LPAR.

Next, the device management module 32100 refers to the host-storage path management table 33300 and the device management table 33200, and the storage I / O directly connected to the host I / O port of the host whose host virtualization mode is “Yes”. A port is identified (step 61080). As a result, in the processing of the subsequent step, the access in which the created LPAR virtual WWN is described in the storage I / O port directly connected to the host I / O port of the host whose host virtualization mode is “No” No control list is applied, thereby reducing the possibility that the number of applied access control lists will reach the upper limit. Note that the storage I / O port specified in step 61080 is a storage I / O port directly connected to the host I / O port of the host that can be the migration destination of the created LPAR.

Next, the device management module 32100 refers to the device management table 33200 and identifies the IP address of the storage device identified in step 61070. Then, the device management module 32100 refers to the table size upper limit management table 23700 from the storage device identified in step 61070 (using the identified IP address), and identifies the record upper limit number for the host group management table 23300. (Step 61090).

Then, the device management module 32100 records, for each storage I / O port specified in

steps

61070 and 61080, the number of host groups, in other words, a record having the ID of the storage I / O port (record in the host group management table 23300). Is identified (step 61100). In other words, in this 61100, the storage I / O port directly connected to the host I / O port of the host having the created LPAR and the host I / O port of the host that can be the migration destination of the created LPAR are directly connected. The number of applied access control lists is specified for each storage I / O port.

The device management module 32100 determines, for each storage I / O port specified in

steps

61070 and 61080, whether the number of records (number of host groups) specified in step 61100 has reached the upper limit number of records specified in step 61090. (Step 61110).

When the number of host groups (access control list) does not reach the record upper limit number for each of the storage I / O port specified at step 61070 and at least one storage I / O port specified at step 61080 (step 61110: No), the device management module 32100 instructs the host LPAR management program 13200 to set the migration permission of the LPAR created in step 61030 to “permitted” (step 61120). The LPAR management program 13200 updates the LPAR management table 13400 in accordance with an instruction from the device management module 32100. In other words, the LPAR management program 13200 sets “permitted” in the LPAR management table 13400 as to whether migration of the LPAR created in Step 61030 is possible. Next, the device management module 32100 has a target storage I / O port (a storage I / O port in which the number of host groups has not reached the upper limit number of records) among the storage I / O ports specified in

steps

61070 and 61080. The disk management program 23100 of the storage apparatus is instructed to create a host group in which the virtual WWN identified in Step 61040 is set as the connection permission WWN in the target storage I / O port (Step 61130). In other words, the device management module 32100 instructs the storage device to apply the access control list describing the virtual WWN specified in step 61040 to the storage I / O port specified in step 61080. The disk management program 23100 updates the host group management table 23300 in accordance with instructions from the device management module 32100. That is, the disk management program 23100 registers the virtual WWN identified in step 61040 as the connection permission WWN corresponding to the target storage I / O port in the host group management table 23300. As a result, an access control list is newly added for all target storage I / O ports.

On the other hand, if the number of host groups has reached the maximum number of records for any storage I / O port identified in step 61080 (step 61110: Yes), the device management module 32100 determines that the host LPAR management program 13200 An instruction is given to set whether or not migration of the LPAR created in step 61030 is possible (step 61140). The LPAR management program 13200 updates the LPAR management table 13400 in accordance with an instruction from the device management module 32100. In other words, the LPAR management program 13200 sets “No” for the migration possibility of the LPAR created in Step 61030 in the LPAR management table 13400. Thus, the maximum number of LPARs to be migrated is determined by the upper limit number of records in the host group management table 23300. As a result, the maximum number of LPARs to be migrated can be limited to a number corresponding to the record upper limit number (access control list upper limit number per storage I / O port) of the host group management table 23300. In step 61140, the device management module 32100 notifies the administrator that the LPAR cannot be subject to failover through the GUI provided by the GUI display processing module 32300. Next, only the storage I / O port specified in step 61070 (storage I / O port directly connected to the host I / O port of the host having the created LPAR) is processed by the processing as in step 61130 to perform step 61040. A host group (access control list) in which the virtual WWN specified in step 1 is used as a connection permission WWN is added (step 61150). If the number of host groups has reached the maximum number of records for the storage I / O port identified in step 61070 (storage I / O port directly connected to the host I / O port of the host having the created LPAR), Processing may end in error.

After

step

61130 or 61150, the device management module 32100 allocates the logical volume on the storage identified in step 61070 to the LPAR created in step 61030 from the administrator through the GUI provided by the GUI display processing module 32300. The logical volume ID is designated (step 61160).

Next, the device management module 32100 instructs the disk management program 23100 on the storage identified in step 61070 to associate the host group defined in step 61130 or step 61150 with the logical volume specified by the administrator in step 61160. (Step 61170). The disk management program 23100 updates the host group-volume related management table 23600 (adds a record including the ID of the host group and the ID of the logical volume) according to the instruction from the device management module 32100, and The volume allocation destination host and the LPAR ID are registered in the record of the volume in the volume management table 23500.

The above is the LPAR creation processing performed by the device management module 32100.

FIG. 17 is a flowchart of the LPAR migration process.

The device management module 32100 receives, from the administrator, the specification of the migration target LPAR ID, the host ID where the LPAR exists, and the migration destination host ID through the GUI provided by the GUI display processing module 32300 ( Step 62010).

Next, the device management module 32100 refers to the LPAR management table 13400 and confirms whether or not the LPAR migration specified in Step 62010 is possible (Step 62020). If the LPAR migration availability is “NO”, the process ends.

If the migration permission of LPAR is “permitted” (step 62030: Yes), the device management module 32100 refers to the device management table 33200, and sets the host for each of the LPAR migration destination and migration source specified in step 62010. Specify the management IP address. After that, the device management module 32100 instructs the LPAR management program 13200 of the host for LPAR migration for each of the migration destination and the migration source (step 62040).

When the migration of the LPAR is completed, the migration source LPAR management program 13200 deletes the LPAR record from the LPAR management table 13400 of the migration source host (step 62050). On the other hand, when the migration of the LPAR is completed, the migration destination LPAR management program 13200 adds the migrated LPAR record to the LPAR management table 13400 of the migration destination host. As a result, the virtual WWN of the migration target LPAR is taken over from the migration source to the migration destination (step 62060).

The above is the LPAR migration process.

Hereinafter, specific examples of LPAR creation and LPAR migration will be described with reference to FIGS. However, in this embodiment, it is assumed that the LPAR management table possessed by HOST1, the host group management table 23300 and the host group-volume related management table 23600 possessed by SYS1 (storage device) are blank in the initial state. Further, it is assumed that the device management table 33200 has the contents shown in FIG. 14A.

The device management module 32100 receives the specification of the host ID of the LPAR creation destination, the number of processors to be assigned to the LPAR “2”, and the memory size “4 GB” from the administrator through the GUI.

Next, the device management module 32100 receives a specification of the ID “PORT11” of the host I / O port for creating the virtual HBA to be allocated to the LPAR from the administrator through the GUI.

Next, the device management module 32100 refers to the device management table 33200 and identifies the management IP address of the host designated by the administrator. According to the device management table 33200 shown in FIG. 14A, the management IP address of the HOST1 is “192.168.11.21”. Then, the LPAR management program on the host is instructed to create an LPAR. HOST1 (LPAR management program) updates the LPAR management table 13400. Specifically, the record in the first row of the table 13400 in FIG. 7A is added. The HOST 1 (LPAR management program) notifies the device management module 32100 of the virtual WWN “12: 00: 00: 00: 00: 00: 01” assigned to the LPAR.

Next, the device management module 32100 refers to the host-storage path management table 33300 and searches for a record in which the host ID column is “HOST1” and the port ID is “PORT11”. According to FIG. 15, the device management module 32100 identifies the ID “SYS1” of the storage directly connected to the PORT 11 from the host-storage path management table 33300.

Next, the device management module 32100 refers to the host-storage path management table 33300 and the device management table 33200, and is directly connected to the host whose host virtualization mode is “Yes” among the storage I / O ports of the SYS1. The storage I / O ports PORT1, PORT2, PORT3, and PORT4 are specified. PORT 1 is a storage I / O port directly connected to PORT 11.

Next, the device management module 32100 refers to the device management table 33200 (FIG. 14A) and identifies the management IP address “192.168.11.21” of SYS1. Then, the device management module 32100 specifies the number of records “256” in the host group management table 23300 from the table size upper limit management table 23700 (FIG. 13), and sets the host for each of PORT1, PORT2, PORT3, and PORT4. It is determined whether the number of groups has reached 256.

For PORT1 and PORT2 to PORT4, when the number of host groups has not reached the upper limit number of records, the device management module 32100 instructs HOST1 (LPAR management program) to set whether or not migration of LPAR1 is possible. Next, the device management module 32100 connects the virtual WWN “12: 00: 00: 00: 00: 00: 01” to each of PORT1, PORT2, PORT3, and PORT4 with respect to SYS1 (disk management program). Instruct to create a host group to be allowed WWN. The SYS1 (disk management program) updates the host group management table 23300 in accordance with an instruction from the device management module 32100. Specifically, HG1, HG2, HG3, and HG4 are created, and records in the first to fourth lines of the host group management table 23300 (FIG. 9) are added.

When the number of host groups has reached the upper limit number of records for at least one of PORT1 to PORT4, the device management module 32100 sets “No” to whether or not LPAR1 migration is possible for HOST1 (LPAR management program). Instruct them to do so. Next, the device management module 32100 creates a host group with the virtual WWN “12: 00: 00: 00: 00: 00: 01” as the connection permission WWN in PORT 1 for SYS1 (disk management program). Instruct them to do so. The SYS1 (disk management program) updates the host group management table 23300 in accordance with an instruction from the device management module 32100. Specifically, HG1 is created and a record in the first line of the host group management table 23300 (FIG. 9) is added.

Hereinafter, a case where HG1, HG2, HG3, and HG4 are created in the host group management table 23300 will be described.

Next, the device management module 32100 receives the designation of the logical volume ID “VOL1” assigned to the LPAR1 of the HOST1 from the administrator through the GUI.

Next, the device management module 32100 instructs SYS1 (disk management program) to associate each of HG1, HG2, HG3, and HG4 with VOL1. The SYS1 (disk management program) updates the host group-volume related management table 23600 (FIG. 12) in accordance with an instruction from the device management module 32100. Specifically, records from the first line to the fourth line in the table 23600 of FIG. 12 are added.

After the above LPAR creation processing is completed, the device management module 32100 receives the ID “LPAR1” of the LPAR to be migrated, the ID “HOST1” of the host in which LPAR1 exists, and the migration destination host from the administrator through the GUI. The migration instruction including the ID “HOST2” is received. Next, the device management module 32100 refers to the LPAR management table 13400 and confirms whether or not migration of LPAR1 designated by the administrator is possible. According to FIG. 7A, whether or not migration of LPAR1 is “permitted”, the device management module 32100 refers to the device management table 33200 (FIG. 14A), and the management IP addresses “192.168.11. 21 ”and“ 192.168.11.22 ”are specified. In addition, the device management module 32100 instructs the LPAR management program of each of the HOST1 and HOST2 to perform LPAR migration. When the migration of LPAR1 is completed, HOST1 (LPAR management program) deletes the LPAR management table 13400 (FIG. 7A) of HOST1 or the LPAR1 record (record in the first row). On the other hand, when the migration of LPAR1 is completed, HOST2 (LPAR management program) adds a record of LPAR1 (record in the first row) to the LPAR management table 13400 (FIG. 7B) of HOST2. 7A and 7B, the virtual WWN of LPAR1 is taken over from HOST1 to HOST2.

As a result of the above LPAR migration processing, when accessing the VOL 1 of the SYS 1 from the LPAR 1, the host I / O port that issues the I / O request changes from the PORT 11 to the PORT 13, and accordingly the storage I / O that receives the I / O request The O port changes from PORT1 to PORT3. However, since the host group HG3 (access control list) associated with the virtual WWN “12: 00: 00: 00: 00: 00: 01” is already applied to the PORT3, the LPAR1 to the VOL1 Access is possible, and there is no need to reconfigure the host group for the storage device.

In the above embodiment, the access control list (host group) describing the created virtual WWN of the LPAR is applied to all storage I / O ports corresponding to the host virtual mode “Yes”. A host group may be applied only to a storage I / O port directly connected to a host I / O port of a host computer that executes LPAR.

Example 2 will be described. At that time, differences from the first embodiment will be mainly described, and description of common points with the first embodiment will be omitted or simplified.

In the second embodiment, the device management module 32100 of the management server 30000 performs another LPAR creation process. In the computer system, it is conceivable to distribute a plurality of host computers 10000 connected to one storage apparatus 20000 to a plurality of different users (for example, customers or departments). Hereinafter, a group in which host computers distributed to specific users are registered is referred to as a “resource group” (or tenant). When executing the LPAR migration process, it is not normally performed that the migration target LPAR selects a host computer belonging to a resource group different from the resource group to which the LPAR belongs as a migration destination.

FIG. 18 shows a configuration example of the resource group management table 33400 that the management server 30000 has.

The resource group management table 33400 has a field 33410 for registering a group ID (resource group identifier) and a field 33420 for registering a resource ID (identifier of a host computer belonging to the resource group). According to FIG. 18, HOST1 and HOST2 belong to the resource group (GR1).

FIG. 19 illustrates a difference between the LPAR creation process according to the first embodiment and the LPAR creation process according to the first embodiment.

In step 61085, the device management module 32100 refers to the host-storage path management table 33300 and the resource group management table 33400, and among the storage I / O ports specified in step 61080, the same resource as the host specified in step 61010 A storage I / O port directly connected to a host belonging to the group is specified.

In step 61110, the device management module 32100 specifies the number of host groups for each storage I / O port specified in

steps

61070 and 61085. In step 61110, the device management module 32100 determines, for each storage I / O port specified in

steps

61070 and 61085, whether the record number (host group number) specified in step 61100 has reached the record upper limit number specified in step 61090. Judge whether or not. In step 61130, the device management module 32100 selects a target storage I / O port (a storage I / O port in which the number of host groups has not reached the record upper limit number) among the storage I / O ports specified in

steps

61070 and 61085. The disk management program 23100 of the storage apparatus having the storage apparatus is instructed to create a host group in which the virtual WWN specified in step 61040 is set as the connection permission WWN in the target storage I / O port.

Hereinafter, specific examples of LPAR creation and LPAR migration according to the second embodiment will be described with reference to FIGS. 6 to 15 and FIG. However, in this embodiment, it is assumed that the LPAR management table possessed by HOST1, the host group management table 23300 and the host group-volume related management table 23600 possessed by SYS1 (storage device) are blank in the initial state. Further, it is assumed that the device management table 33200 has the contents shown in FIG. 14B.

The processing up to step 61080 is the same as in the first embodiment.

In step 61085, the device management module 32100 refers to the host-storage path management table 33300 and the resource group management table 33400, and belongs to the same resource group as the HOST1 among the storage I / O ports PORT1 to PORT4 identified in step 61080. PORT1 to PORT4 directly connected to HOST2 are specified.

Processing after step 61090 is the same as that in the first embodiment.

According to the second embodiment, the storage I / O in which the application destination of the access control list in which the created LPAR virtual WWN is described is directly connected to the host computer belonging to the same resource group as the host computer in which the LPAR is created. Limited to ports. Thereby, the possibility that the number of applied access control lists reaches the upper limit can be reduced.

Example 3 will be described. At that time, the differences from the first and second embodiments will be mainly described, and the description of the common points with the first and second embodiments will be omitted or simplified.

In the third embodiment, the device management module 32100 of the management server 30000 performs LPAR scheduling processing. In a computer system, effective utilization of computer resources is performed by executing different tasks according to time zones on the same computer resources. In this case, it is conceivable to define an independent LPAR for each business and change the LPAR to be operated according to the time zone. In the time zone when the LPAR is not operated, the host group definition (application of the access control list) is not required for the logical volume assigned to the LPAR.

In the third embodiment, host group creation and deletion processing is performed in the LPAR scheduling processing in the management server 30000.

FIG. 20 shows a configuration example of the LPAR operation schedule management table 13500 of the host computer 10000.

The LPAR operation schedule management table 13500 includes a field 13510 for registering a device ID (host computer identifier), a field 13520 for registering an ID (LPAR identifier), and a field 13530 for registering an activation time (LPAR activation time). And a field 13540 for registering stop time (stop time of LPAR). According to FIG. 20, LPAR1 of HOST1 is scheduled to start at “09:00:00” and stop at “19: 00: 00: 00”.

FIG. 21 schematically illustrates LPAR scheduling processing (including creation and deletion of host groups) according to the third embodiment.

Hereinafter, host group creation and deletion according to the third embodiment will be described with reference to FIGS. 6 to 15 and FIG. However, in this embodiment, the LPAR management table of HOST 1 has the contents of FIG. 7A, the host group management table 23300 of SYS 1 has the contents of FIG. 9, and the volume management table 23500 has the contents of FIG. Assume that the relation management table 23600 has the contents shown in FIG.

The device management module 32100 periodically refers to the LPAR operation schedule management table 13500 and checks whether there is an LPAR that has reached the start time or end time. When the current time is 19: 00: 0, referring to the LPAR operation schedule management table 13500 shown in FIG. 20, LPAR1 is the stop time and LPAR2 is the start time.

The device management module 32100 first deletes the host group (access control list in which the virtual WWN of LPAR1 is described) associated with the virtual WWN of LPAR1 at the stop time. Referring to the host group management table 23300 shown in FIG. 9, the host groups including the virtual WWN “12: 00: 00: 00: 00: 00: 01” possessed by LPAR1 are HG1, HG2, HG3, and HG4. Therefore, the device management module 32100 deletes records related to the host groups HG1, HG2, HG3, and HG4 from the host group management table 23300 and the host-storage path management table 33300.

Next, the device management module 32100 creates a host group associated with the virtual WWN of LPAR2 that has become the start time. Referring to the volume management table 23500 shown in FIG. 11, the logical volume assigned to LPAR1 of HOST1 is VOL2. Therefore, the device management module 32100 creates a host group on SYS1 in accordance with the procedure after step 61040 of the LPAR creation processing shown in FIGS. 16A and 16B, and associates the created host group with VOL2 (HG5, FIG. 21). HG6, HG7, HG8).

According to the third embodiment, the access control list is applied only to the operating LPAR. Thereby, the possibility that the number of applied access control lists reaches the upper limit can be reduced.

As a modification of the third embodiment, the LPAR start time can be read as fillover start, and the LPAR stop time can be read as failover completion. Specifically, for example, the device management module 32100 synchronizes with the start of LPAR failover, and transfers the virtual LPAR to be migrated to the storage I / O port directly connected to the host I / O port of the failover destination host computer. After the host group associated with the WWN is applied and the failover of the LPAR is completed, the host associated with the virtual WWN of the LPAR from the storage I / O port directly connected to the host I / O port of the failover source host computer Cancel the group. According to this modification, the access control list is applied only to the LPAR that is actually migrated. Thereby, the possibility that the number of applied access control lists reaches the upper limit can be reduced.

Although several embodiments have been described above, these are merely examples for explaining the present invention, and the scope of the present invention is not limited to these embodiments. The present invention can be implemented in various other forms.

10000: host computer, 20000: storage device, 30000: management server, 46000: PCIe bus

Claims

A plurality of host computers each having at least one physical host port;
A storage system that is one or a plurality of storage devices each having a plurality of storage ports;
The physical host port and the storage port are connected in a 1: 1 relationship,
Each of at least two of the plurality of host computers is a host computer capable of constructing an LPAR (Logical Partition) having a virtual host port;
The storage system
Defining a plurality of logical volumes including a first logical volume used by the first LPAR;
Each of at least two storage ports of the plurality of storage ports included in the storage system includes a first access control list that is an access control list indicating a first LPAR that is permitted to access the first logical volume. Apply to
Computer system.
The first access control list includes a communication identifier of a virtual host port of the first LPAR.
The computer system according to claim 1.
The plurality of host computers are stored in one or a plurality of chassis,
A controller capable of controlling LPAR failover is also stored in at least one of the one or more chassis,
Each of the plurality of host computers is connected to a management system and the controller, and can receive an instruction to fail over the LPAR from the host computer to another host computer from at least one of the management system and the controller. ,
The computer system according to claim 1.
The maximum number of access control lists that can be applied to each storage port is determined.
The maximum number of LPARs to be migrated by failover is determined by the upper limit number of lists.
The computer system according to claim 1.
The maximum number of access control lists that can be applied to each storage port is determined.
The first access control list is not applied to a storage port connected to a physical host port of a host computer that does not execute LPAR.
The computer system according to claim 4.
The maximum number of access control lists that can be applied to each storage port is determined.
The at least two storage ports are the same as the storage port connected to the physical host port of the first host computer that executes the first LPAR and the tenant to which the first host computer of a plurality of tenants belongs. A storage port connected to each physical host port of one or more other host computers belonging to the tenant of
The plurality of tenants are a plurality of resource groups to which two or more host computers respectively belong.
The computer system according to claim 1.
The maximum number of access control lists that can be applied to each storage port is determined.
The first access control list includes a physical host port of the first host computer in which the first LPAR is defined when the first LPAR is defined but the first LPAR is not activated. Does not apply to storage ports connected to
The first access control list is applied to a storage port connected to a physical host port of the first host computer when the first LPAR is activated on the first host computer,
When the operation of the first LPAR is stopped, the first access control list is released from the storage port connected to the physical host port of the first host computer.
The computer system according to claim 1.
The maximum number of access control lists that can be applied to each storage port is determined.
In synchronization with the start of failover of the first LPAR, the first access control list is set and applied to the storage port corresponding to the physical host port of the host computer that is the failover destination of the first LPAR.
After completion of the failover of the first LPAR, the first access control list is released from the storage port corresponding to the physical host port of the host computer that is the failover source of the first LPAR.
The computer system according to claim 1.
A management system connected to each of the plurality of host computers and the storage system;
The physical host port and the storage port are connected by a PCIe bus,
The management system causes the storage system to define the plurality of logical volumes and to apply the first access control list to each of the at least two storage ports;
The first access control list includes a communication identifier of a virtual host port of the first LPAR;
The at least two storage ports include a storage port connected to a physical host port of a host computer that executes the first LPAR, and a physical port of another host computer that can execute LPAR that can be a migration destination of the first LPAR. A storage port connected to a host port,
The computer system according to claim 1.
The maximum number of access control lists that can be applied to each storage port is determined.
The management system is
If there is a storage port in which the number of access control lists has reached the list upper limit number in the at least two storage ports, the first LPAR is managed as an LPAR that cannot be a migration target, and the first Applying the first access control list only to a storage port connected to a physical host port of a host computer executing LPAR;
If there is no storage port in which the number of access control lists reaches the upper limit number of lists among the at least two storage ports, the first LPAR is managed as an LPAR that can be a migration target, and the at least two storage ports Applying the first access control list to each of the storage ports;
The computer system according to claim 9.
A plurality of host computers each having at least one physical host port; and a storage system that is one or a plurality of storage devices each having a plurality of storage ports, wherein the physical host port and the storage port are 1 1 is a management system of a computer system that is connected in a 1-to-1 relationship and in which each of at least two of the plurality of host computers can construct an LPAR (Logical PARtition) having a virtual host port. And
An interface device connected to the plurality of host computers and the storage system;
Storage resources,
A processor connected to the interface device and the storage resource and executing processing using the storage resource as appropriate;
The processor is
Causing the storage system to define a plurality of logical volumes including the first logical volume used by the first LPAR;
Each of at least two storage ports of the plurality of storage ports included in the storage system includes a first access control list that is an access control list indicating a first LPAR that is permitted to access the first logical volume. To apply to the storage system,
Management system.
The first access control list includes a communication identifier of a virtual host port of the first LPAR.
The management system according to claim 11.
The maximum number of access control lists that can be applied to each storage port is determined.
The maximum number of LPARs to be migrated by failover is determined by the upper limit number of lists.
The computer system according to claim 1.
A plurality of host computers each having at least one physical host port; and a storage system that is one or a plurality of storage devices each having a plurality of storage ports, wherein the physical host port and the storage port are 1 1 is a computer system control method in which each of at least two of the plurality of host computers can construct an LPAR (Logical PARtition) having a virtual host port. ,
Defining a plurality of logical volumes including a first logical volume used by the first LPAR in the storage system;
Each of at least two storage ports of the plurality of storage ports included in the storage system includes a first access control list that is an access control list indicating a first LPAR that is permitted to access the first logical volume. Apply to
Control method.