Disk-array device having storage-device recognition and identification of a storage area network link environment

The present invention relates to a disk array device that constitutes a storage area network (SAN).

Conventionally, a storage area network management system has been disclosed in which an integrated management mechanism for integrated control of a storage area network (SAN) is set, and switch zoning and access management between a host and a storage device are collectively managed. (See Patent Document 1).

<patcit num="1"><text>JP-A-2002-63063</text></patcit>

<p> However, as the storage area network (SAN) environment expands and the number of switch devices that switch the connection by the host bus adapter (HBA) of the server device or Fiber Channel increases, it is connected to the disk array device of the storage device. There was an inconvenience that it was difficult to know the connection destination port of Fiber Channel.</p><p> In addition, the storage area network (SAN) environment initially constructed on the customer side is also changing day by day due to version upgrades, etc., making it even more difficult to grasp the connection environment on the customer side.</p><p> Therefore, an object of the present invention is to provide a disk array device capable of grasping the connection environment of a storage area network (SAN) from the storage device side.</p>

<p> In order to solve the above problems and achieve the object of the present invention, the disk array device of the present invention is used.<u style="single">Attribute information of the switch device that switches the connection by Fiber Channel configured by the storage area network (SAN) connected to the storage device side, and the host bus of the server device connected to the switch device by Fiber Channel. -Information including the firmware version of the switch device and the driver version of the host bus adapter (HBA) as the attribute information of the adapter (HBA).</u>To get through the switch device<u style="single">, Host bus adapter (HBA) attribute information and switch device attribute information</u>There is a connection information management means for managing the combination of the above. As a result, the disk array device of the present invention can be used.<u style="single">Host bus adapter (HBA) attribute information and switch device attribute information</u>Can be obtained in a batch.</p><p> Further, the disk array device of the present invention is<u style="single">The storage device is connected to an operational information gathering application running on the computer, and the storage device is</u>Search the connection information management means for the combination information of the desired host bus adapter (HBA) attribute information and switch device attribute information.<u style="single">, Operation information collection application, the searched information</u>Collect and analyze<u style="single">To do</u>.. Thereby, the disk array device of the present invention can collect and analyze the attribute information of the host bus adapter (HBA) and the attribute information of the switch device on the storage device side.<u style="single">Operation information collection application</u>After collecting and analyzing<u style="single">When the host bus adapter (HBA) of the server device is connected to the storage device via the switch device.</u>When a data transfer timeout error occurs, information on the connection failure in the storage device is created, and failure analysis is performed from the collected combination information and the created connection failure information.</p><p> As a result, the disk array device of the present invention uses the firmware version of the switch device and the driver of the host bus adapter (HBA) as the attribute information of the switch device and the attribute information of the host bus adapter (HBA) of the server device. Information including the version of is acquired via the switch device, and the attribute information of the host bus adapter (HBA) and the attribute information of the switch device are combined and managed by the connection information management means, and the connection information management means is used. Combine information of the desired host bus adapter (HBA) attribute information and switch device attribute information<u style="single">Depending on the storage device</u>Search<u style="single">By operation information collection application</u>Collect<u style="single">Minutes</u>After analysis, collection and analysis<u style="single">When the host bus adapter (HBA) of the server device is connected to the storage device via the switch device.</u>Information about connection failures in storage devices when a data transfer timeout error occurs<u style="single">By operation information collection application</u>From the combination information created and collected and the information related to the created connection failure<u style="single">Operation information collection application</u>Since failure analysis is performed by, it is possible to grasp the connection environment of the storage area network (SAN). In addition, the disk array device of the present invention can grasp the connection environment on the customer side such as version upgrades and failures.</p>

<p> The disk array device of the present invention<u style="single">Information including the firmware version of the switch device and the driver version of the host bus adapter (HBA) as the attribute information of the switch device and the attribute information of the host bus adapter (HBA) of the server device.</u>Can be acquired in a batch, on the storage device side<u style="single">Host bus adapter (HBA) attribute information and switch device attribute information</u>Collect and analyze<u style="single">After collecting and analyzing, when a data transfer request is made from the storage device to the server device but a data transfer timeout error occurs, information on the connection failure in the storage device is created, and the collected combination information and the collected combination information and Perform failure analysis from the created connection failure information</u>As a result, it is possible to grasp the connection environment such as the introduction configuration on the customer side and the failure occurrence frequency statistical information.</p>

Hereinafter, embodiments of the present invention will be described with reference to the drawings as appropriate. First, the configuration of the disk array device according to the embodiment of the present invention will be described.

FIG. 1 is a diagram showing the collection of host bus adapter (HBA) information by the disk array device according to the present invention. In FIG. 1, the host bus adapter (HBA) 2 of the server device 1 is connected to port 3-1 of the FC switch device 3 by Fiber Channel (FC) 8. Further, port 3-1 of the FC switch device 3 is connected to the channel adapter (CHA) 6 of the storage device 6 by Fiber Channel (FC) 9. The server device 1, the FC switch device 3, and the storage device 6 constitute a disk array device based on a storage area network (SAN). In addition, the storage device 6 is connected to the operation information collection application (AP) 7 via the local area network (LAN) 11. Here, the operation information collection application (AP) 7 specifically operates on a personal computer (PC).

Here, in the disk array device according to the embodiment of the present invention, the host bus adapter (HBA) information management database (DB) 4 that acquires and manages the connection information of the storage area network (SAN) configuration is used. It is provided in the FC switch device 3.

Here, as the storage area network (SAN) configuration increases and the number of vendors and models of the host bus adapter (HBA) 2 and FC switch device 3 of the server device 1 increases, the device is connected to the storage device 6. It is becoming difficult to grasp the port of the other party.

In addition, even on the customer side who introduced these storage area network (SAN) configurations, the driver of the host bus adapter (HBA) 2 of the server device 1 and the firmware of the FC switch device 3 are upgraded from the configuration at the time of initial installation. This makes it even more difficult to understand the current storage area network (SAN) configuration. In addition, in the event of a Fiber Channel (FC) 8 or 9 connectivity failure, the destination customer is required to collect storage area network (SAN) configuration connectivity information as failure information. There was no other way but to confirm the information. Therefore, in the disk array device according to the embodiment of the present invention, the operation of collecting host bus adapter (HBA) information as described below is performed.

The operation of collecting host bus adapter (HBA) information in the disk array device configured as described above will be described below. In FIG. 1, the disk array device according to the embodiment of the present invention is the host bus adapter (HBA) of the server device 1 which complies with the GS-4 rule of the Fiber Channel rule connected to the storage device 5. FDMI (Fabric Management Interface) 10 defined in the GS-4 convention is used for 2 and FC switch device 3, and attribute information 14 of host bus adapter (HBA) 2 and attributes of FC switch device 3 are used. A host bus adapter (HBA) information management database (DB) 4 for registering information 13 is provided on the FC switch device 3 so that it can be collected from the storage device 5.

Each procedure showing a specific operation will be described below. First, the disk array device according to the embodiment of the present invention is switched from the host bus adapter (HBA) 2 of the server device 1 to the FC switch via the FDMI (Fabric Management Interface) 10 defined in the GS-4 convention. Register the attribute information of the host bus adapter (HBA) in the host bus adapter (HBA) information management database (DB) 4 of the device 3 (step S1). At this time, the disk array device according to the embodiment of the present invention registers the attribute information of the FC switch device from port 3-1 of the FC switch device 3 to the HBA information management DB 4 via FDMI10. In the host bus adapter (HBA) information management database (DB) 4, such connection information is managed in combination.

The reason for registering the host bus adapter (HBA) attribute information in the host bus adapter (HBA) information management database (DB) 4 of the FC switch device 3 in this way is defined in the GS-4 convention. This is because this information can be acquired by the existing FDMI (Fabric Management Interface) 10, and it is not possible to acquire the failure information of the normal data transfer by the normal data transfer procedure.

The above registration timing triggers command issuance when setting the initial connection state of the driver of the host bus adapter (HBA) 2 of the server device 1 connected by the FC switch device 3 and Fiber Channel (FC) 8 and 9. And. In this case, the command is issued by clicking the specified check box.

Here, as the information 12 collected in the host bus adapter (HBA) information management database (DB) 4, the attribute information 13 of the FC switch device 3 and the attribute information 14 of the host bus adapter (HBA) 2 are used. There is. The attribute information 13 of the FC switch device 3 is, for example, a switch model 13-1, a vendor name 13-2, and a firmware version 13-3. In addition, the attribute information 14 of the host bus adapter (HBA) 2 is, for example, the operating system (OS) version 14-1, the driver version 14-2 of the host bus adapter (HBA) 2, and the host. The model name of the bus adapter (HBA) 2 is 14-3.

Next, the disk array device according to the embodiment of the present invention is applied to the channel adapter (CHA) 6 of the storage device 5 to the host bus adapter (HBA) information management database (DB) 4 of the FC switch device 3. Search for host bus adapter (HBA) information (step S2). Here, the desired information is searched from the combination information of the connection information managed in the host bus adapter (HBA) information management database (DB) 4.

The reason for searching for information from the storage device 5 to the host bus adapter (HBA) information management database (DB) 4 of the FC switch device 3 in this way is that the normal data transfer procedure is used for normal data transfer. This is because information cannot be searched in the event of a failure.

The search timing is determined when the FC switch device 3 and the server device 1 are connected via the storage area network (SAN) to the storage device 5, when the server device 1 recognizes the storage device 5, or when the server device 1 to the storage device 5 One before the file transfer to.

Further, the search timing is not limited to this, and the search timing may be the time when the storage device 5 re-recognizes the server device 1 via the FC switch device 3. In this case, the storage device 5 reads the above information by the read operation, and transfers the above information to the operation information collection application (AP) 7 when the information can be transferred after being held once.

Then, the information retrieved from the channel adapter (CHA) 6 of the storage device 5 to the operation information collection application (AP) 7 via the local area network (LAN) 11 is collected and used for analysis (step). S3).

The reason for collecting and analyzing the information retrieved from the storage device 5 to the operation information collection application (AP) 7 in this way is that in the normal data transfer procedure, information collection and analysis can be performed in the event of a normal data transfer failure. Because it cannot be done.

As a result, the customer who introduced the storage area network (SAN) configuration at the present time without asking the vendor or customer of the host bus adapter (HBA) 2 and FC switch device 3 of the server device 1 Enables early access to connection information for storage area network (SAN) configurations.

As a result, when the customer upgrades the driver, he / she can refer to the firmware and determine whether or not the connection is possible even if the version is upgraded. In addition, when a failure occurs, the part where the failure occurs can be determined by the combination of the driver and the firmware. In addition, the host bus adapter (HBA) 2 and the FC switch device 3 can be upgraded together on the storage device 5 side. In addition, it is possible to prevent the host bus adapter (HBA) 2 and the FC switch device 3 from being upgraded together on the server device 1 side.

In addition, when a connection failure with the storage device 5 occurs, the customer environment can be obtained at an early stage, which enables early analysis and early improvement of the failure site. Furthermore, by collecting information on storage area network (SAN) configurations, it will be possible to clarify future evaluation targets and narrow down the evaluation man-hours.

FIG. 2 is a diagram showing failure analysis in host bus adapter (HBA) information collection. When the data transfer timeout error occurs when the host bus adapter (HBA) 2 of the server device 1 described above is connected to the storage device 5 via the FC switch device 3, when and where it occurred. By adding the function to track the history of the data, it is necessary to replace either the host bus adapter (HBA) 2, the FC switch device 3, or the package parts that compose them.

Here, the data transfer request is made from the storage device 5 to the server device 1, but since the data is not transferred, an error message is displayed on the storage device 5. In this case, the storage device 5 needs to collect the connection information before the error occurs, but the storage device 5 may collect the connection information after the error occurs depending on the situation.

Therefore, as in FIG. 1 described above, the disk array device according to the embodiment of the present invention is the host bus adapter of the server device 1 via the FDMI (Fabric Management Interface) 10 defined in the GS-4 convention. Registration of host bus adapter (HBA) attribute information from (HBA) 2 to the host bus adapter (HBA) information management database (DB) 4 of FC switch device 3 (step S1), storage device 5 Searching for host bus adapter (HBA) information from channel adapter (CHA) 6 to host bus adapter (HBA) information management database (DB) 4 of FC switch device 3 (step S2), storage device 5 Data transfer after the information retrieved from the channel adapter (CHA) 6 to the operational information collection application (AP) 7 via the local area network (LAN) 11 is collected, analyzed and used (step S3). When a timeout error occurs, the following operations are performed.

In this case, the operation information collection application (AP) 7 creates information about the connection failure in the storage device 5 from the channel adapter (CHA) 6 of the storage device 5 via the local area network (LAN) 11 (step). S4). Here, the operation information collection application (AP) 7 creates a time code threshold value when a frame error is detected due to frequent check conditions in the storage device 5.

Then, from the collected search information (step S3) and the created connection failure information (step S4), the operation information collection application (AP) 7 performs failure analysis when a connection failure occurs (step S5). Here, the operation information collection application (AP) 7 counts connection failures for each port and manages the threshold value. When a connection failure above a certain threshold occurs, a failure notification is given and the configuration information can be referred to to analyze when and where the failure occurred.

Regarding the information at the time of disconnection, when the server device 1 recognizes that it has not been connected to the storage area network (SAN) for a certain period of time, the host bus adapter (HBA) 2 or FC of the server device 1 The switch device 3 is determined to be disconnected from the storage area network (SAN) environment, and retains the old information.

As a result, in the event of a failure related to the connection with the storage device 5 in the storage area network (SAN), the customer environment becomes available at an early stage, so that the host bus adapter (HBA) 2, FC switch device 3 or By grasping the necessity of replacement of any of the package parts constituting these, early analysis and early improvement become possible.

FIG. 3 is a diagram showing whether or not information can be collected by combining the FC switch device and the host bus adapter (HBA) driver. In Figure 3, the host bus adapter (HBA) drivers 32-1-1, 32 of the server devices 31-1, 31-2, 31-2, 31-3, 31-4 connected to the storage device 34. -1-2, 32-2-1, 32-2-2, 32-3-1, 32-3-2, 32-4-1, 32-4-2, and FC switch device 33-1,33 For -2, FDMI (Fabric Management) defined in the above GS-4 convention depends on whether or not it complies with the GS-4 convention of the Fiber Channel convention. Whether or not to use Interface) is decided. Here, the host bus adapter (HBA) drivers 32-1-1, 32-1-2, 32-2-1, 32-2-2, 32-3-1, 32-3-2, 32- Versions 4-1 and 32-4-2 are operating system (OS) versions of server units 31-1, 31-2,31-2,31-3,31-4, host bus adapters ( Along with the model name of HBA), the attribute information of the host bus adapter (HBA) is collected in the host bus adapter (HBA) information management database (DB) of FC switch devices 33-1, 33-2. The combination of these attribute information is set at each version, for example.

Now, the host bus adapter (HBA) driver 32-1-1 of server device 31-1 is connected to FC switch device 33-1 by Fiber Channel (FC) 37-1-1, and FC switch device 33- 1 is connected to the channel adapter (CHA) 35-1 of the storage device 34 by Fiber Channel (FC) 37-1-2, and the channel adapter (CHA) 35-1 is logically stored as a disk array unit. It is connected to the area LU4.

In addition, the host bus adapter (HBA) driver 32-2-1 of server device 31-2 is connected to FC switch device 33-1 by Fiber Channel (FC) 37-2-1, and FC switch device 33- 1 is connected to the channel adapter (CHA) 35-2 of the storage device 34 by Fiber Channel (FC) 37-2-2, and the channel adapter (CHA) 35-2 is logically stored as a disk array unit. It is connected to the area LU3.

In addition, the host bus adapter (HBA) driver 32-3-2 of server device 31-3 is connected to FC switch device 33-2 by Fiber Channel (FC) 37-3-1, and FC switch device 33- 2 is connected to the channel adapter (CHA) 35-3 of the storage device 34 by Fiber Channel (FC) 37-3-2, and the channel adapter (CHA) 35-3 is logically stored as a disk array unit. It is connected to the area LU2.

In addition, the host bus adapter (HBA) driver 32-4-2 of server device 31-4 is connected to FC switch device 33-2 by Fiber Channel (FC) 37-4-1, and FC switch device 33- 2 is connected to the channel adapter (CHA) 35-4 of the storage device 34 by Fiber Channel (FC) 37-4-2, and the channel adapter (CHA) 35-4 is logically stored as a disk array unit. It is connected to the area LU1.

Here, in FIG. 3, as indicated by a cross, both the host bus adapter (HBA) driver 32-1-1 and the FC switch device 33-1 of the server device 31-1 are GS- of the Fiber Channel standard. The storage device 34 cannot collect the connection information of this combination because it does not comply with the 4 rules and does not support the FDMI (Fabric Management Interface) defined in the above GS-4 rules.

In addition, as shown by the circle, the host bus adapter (HBA) driver 32-2-1 of the server device 31-2 conforms to the GS-4 convention of the Fiber Channel convention, and the above GS-4 convention is used. It corresponds to the defined FDMI (Fabric Management Interface), but as shown by the cross, the FC switch device 33-1 does not comply with the GS-4 convention of the Fiber Channel convention and is not compliant with the GS-4 convention of the Fiber Channel convention. Since the FDMI (Fabric Management Interface) defined in the agreement is not supported, the storage device 34 cannot collect the connection information of this combination.

Also, as indicated by the cross, the host bus adapter (HBA) driver 32-2-1 of the server device 31-2 does not comply with the GS-4 convention of the Fiber Channel convention, and the above GS-4 convention is not compliant. Since the FDMI (Fabric Management Interface) defined in is not supported, the FC switch device 33-2 complies with the GS-4 convention of the Fiber Channel convention as shown by the circle, and the above GS-4. Although it supports FDMI (Fabric Management Interface) defined in the convention, the storage device 34 cannot collect connection information of this combination.

In addition, as indicated by a circle, both the host bus adapter (HBA) driver 32-4-2 and FC switch device 33-2 of server device 31-4 comply with the GS-4 rules of the Fiber Channel rules. Since it is compatible with the FDMI (Fabric Management Interface) defined in the above GS-4 convention, the storage device 34 can collect only the connection information of this combination.

In this way, the host bus adapter (HBA) driver and FC switch that comply with the GS-4 convention of the Fiber Channel convention and are compatible with the FDMI (Fabric Management Interface) defined in the above GS-4 convention. If the device and an unsupported host bus adapter (HBA) driver and FC switch device are mixed, the above-mentioned operation information collection application (AP) 7 should notify by display whether it is supported or not. To.

The connection information acquisition function described above is a function that presupposes a host bus adapter (HBA) driver and FC switch device that comply with the GS-4 standard of the Fiber Channel standard. If the FC switch device does not comply with the GS-4 standard, the connection information acquisition function described above should be applied to the storage area network (SAN) configuration configured by the FC switch device. I can't. Also, if the host bus adapter (HBA) driver does not comply with the GS-4 standard, the information of the host bus adapter (HBA) driver cannot be obtained.

Here, if there is an FC switch device that does not support the GS-4 standard, it can be found that the above-mentioned operation information collection application (AP) 7 cannot collect connection information of this combination. In this case, the operation information collection application (AP) 7 recommends changing the FC switch device to support the GS-4 standard, or notifies by a display that it is not supported.

Also, even if the host bus adapter (HBA) driver and FC switch device comply with the GS-4 convention, the unique functions of the FC switch device match the specific host bus adapter (HBA) driver. If not, the operation information collection application (AP) 7 obtains the collected connection information of this combination, determines whether or not the unique function of the FC switch device is applied, and displays the result.

This can encourage vendors of host bus adapter (HBA) drivers and FC switch devices to recommend support for the GS-4 convention. FIG. 4 is a diagram showing the configuration of the FC switch device. In the FC switch device shown in Fig. 4, the HBA attribute acquisition unit 15 is a host that conforms to the GS-4 convention of the Fiber Channel convention and is compatible with the FDMI (Fabric Management Interface) defined in the GS-4 convention. -Obtain the attribute information of the host bus adapter (HBA) from the bus adapter (HBA) driver via the FDMI (Fabric Management Interface) 10 defined in the GS-4 convention, and then obtain the host bus adapter (HBA) attribute information. HBA) It has a function to register in the information management database (DB) 4.

In addition, the switch attribute acquisition unit 16 conforms to the GS-4 convention of the Fiber Channel convention and is compatible with the FDMI (Fabric Management Interface) defined in the GS-4 convention. It has a function to acquire the attribute information of FC switch device 3 from and register it in the host bus adapter (HBA) information management database (DB) 4. Here, the host bus adapter (HBA) information management database (DB) 4 stores the above-mentioned host bus adapter (HBA) attribute information and FC switch device 3 attributes in the storage device in the FC switch device 3. Information is configured so that it can be stored via FDMI (Fabric Management Interface) 10 defined in the GS-4 convention.

FIG. 5 is a diagram showing a configuration of a storage device. In FIG. 5, the storage device includes a control cluster 21 and a control cluster 25, and the control cluster 21 and the control cluster 25 each have an independent power supply and are duplicated by a completely redundant structure, so that one of the systems fails. Even if the above occurs, both the control cluster 21 and the control cluster 25 are configured to be able to operate normally.

The control cluster 21 includes a channel adapter (CHA) 22-1 to a channel adapter (CHA) 22-4 and a cache memory 22-5, and sends a write instruction from the server device 1 to the channel adapter (CHA) 22. -1 ~ Channel adapter (CHA) 22-4 is configured to receive and register its write instructions in cache memory 22-5.

The control cluster 21 includes a disk adapter (DKA) 24-1 to a disk adapter (DKA) 22-4, and is configured to constantly monitor the contents of the cache memory 22-5. The control cluster 21 is equipped with a high-speed crossbar switch 23, and includes a channel adapter (CHA) 22-1 to a channel adapter (CHA) 22-4 and a cache memory 22-5, and a disk adapter (DKA) 24-1. ~ It is configured to switch the data flow to and from the disk adapter (DKA) 22-4.

The disk adapter (DKA) 24-1 to disk adapter (DKA) 22-4 take out the write data from the cache memory 22-5 according to the registered contents of the cache memory 22-5, and the hard disk of the disk drive (DKU). It is configured to write to the drive device (HDD) 29-1 to the hard disk drive device (HDD) 29-2.

The control cluster 21 and the control cluster 25 combine a plurality of hard disk drive devices (HDD) 29-1 to hard disk drive devices (HDD) 29-4 into one RAID (redundant array of inactive disks). A group is created, and this RAID group is logically divided to form a logical storage area LU. It should be noted that when reading data, the operation is opposite to that at the time of writing described above, so the description thereof will be omitted. Further, since the control cluster 25 operates in the same manner as the control cluster 21 described above, the description thereof will be omitted.

Each procedure showing a specific operation will be described below using a flowchart. FIG. 9 is a flowchart showing the registration operation of the attribute information of the HBA and FC switch devices. FIG. 9 shows the procedure for registering the attribute information of the HBA and FC switch devices in FIG. In FIG. 9, first, the disk array device according to the embodiment of the present invention is the host bus adapter (HBA) 2 of the server device 1 to the host of the FC switch device 3 via the FDMI (Fabric Management Interface) 10. Register the attribute information of the host bus adapter (HBA) in the bus adapter (HBA) information management database (DB) 4 (step S11). At this time, the disk array device according to the embodiment of the present invention registers the attribute information of the FC switch device from port 3-1 of the FC switch device 3 to the HBA information management DB4 via FDMI10 (step S12). ). As a result, the host bus adapter (HBA) information management database (DB) 4 manages such connection information in combination (step S13).

FIG. 10 is a flowchart showing an operation of collecting HBA attribute information and the like. FIG. 10 shows a procedure for collecting HBA attribute information and the like in FIG. 1 described above. In FIG. 10, first, the disk array device according to the embodiment of the present invention is the host bus adapter (HBA) 2 of the server device 1 to the host of the FC switch device 3 via the FDMI (Fabric Management Interface) 10. Register the attribute information of the host bus adapter (HBA) in the bus adapter (HBA) information management database (DB) 4 (step S21).

Next, the disk array device according to the embodiment of the present invention is applied to the channel adapter (CHA) 6 of the storage device 5 to the host bus adapter (HBA) information management database (DB) 4 of the FC switch device 3. Search for host bus adapter (HBA) information (step S22). Then, the information retrieved from the channel adapter (CHA) 6 of the storage device 5 to the operation information collection application (AP) 7 via the local area network (LAN) 11 is collected and used for analysis (step). S23).

FIG. 11 is a flowchart showing the operation of failure analysis in HBA information collection. FIG. 11 shows the operation procedure of the failure analysis in the HBA information collection in FIG. In FIG. 11, the disk array device according to the embodiment of the present invention is FDMI (Fabric Management). Host bus adapter from server unit 1 host bus adapter (HBA) 2 to FC switch unit 3 host bus adapter (HBA) information management database (DB) 4 via Interface) 10 Registration of attribute information of HBA) (step S31), host bus from channel adapter (CHA) 6 of storage device 5 to host bus adapter (HBA) information management database (DB) 4 of FC switch device 3 The adapter (HBA) information was searched (step S32), and the operation information collection application (AP) 7 was searched from the channel adapter (CHA) 6 of the storage device 5 via the local area network (LAN) 11. If a data transfer timeout error occurs after the information has been collected and analyzed and used (step S33), the following operations are performed.

In this case, the operation information collection application (AP) 7 creates information about the connection failure in the storage device 5 from the channel adapter (CHA) 6 of the storage device 5 via the local area network (LAN) 11 (step). S34).

Then, from the collected search information (step S3) and the created connection failure information (step S4), the operation information collection application (AP) 7 performs failure analysis when a connection failure occurs (step S35).

FIG. 6 is a diagram showing a combination table of the host bus adapter (HBA) driver and the firmware of the FC switch device. These items shown in Fig. 6 are required items for the combination information of the host bus adapter (HBA) driver and FC switch device. First, the firmware information of this host bus adapter (HBA) driver and FC switch device is shown in Fig. 1 for FDMI (Fabric Management). It is registered in the host bus adapter (HBA) information management database (DB) 4 of the FC switch device 3 via Interface) 10, and the FC switch device 3 acquires the combination information thereof. Next, the storage device 5 is connected to the host bus adapter (HBA) driver from the channel adapter (CHA) 6 to the host bus adapter (HBA) information management database (DB) 4 of the FC switch device 3. Search the firmware information of the FC switch device. As a result, the operation information collection application (AP) 7 collects the retrieved information from the channel adapter (CHA) 6 of the storage device 5 via the local area network (LAN) 11. Regarding the compatibility information on the combination of the host bus adapter (HBA) driver and the firmware of the FC switch device, specifically, on the monitor of the personal computer (PC) operated by the operation information collection application (AP) 7. By displaying the combination table together, it is possible to provide the compatibility information to the customer.

Regarding the firmware of the host bus adapter (HBA) driver and FC switch device, for example, the model names are divided according to the difference in the number of ports, but the host bus adapter (HBA) driver and FC switch that control the control If the firmware versions of the devices are the same, they can be considered equivalent in terms of Fiber Channel (FC) connectivity. In addition, when these versions are upgraded, the evaluation range is determined by whether or not the interface related to Fiber Channel (FC) has been changed.

Therefore, considering the connectivity of Fiber Channel (FC), the evaluation is carried out in consideration of the combination of the host bus adapter (HBA) driver and the firmware of the FC switch device. This is because it is not possible to evaluate all the firmware of the host bus adapter (HBA) driver and FC switch device.

Therefore, in FIG. 6, the evaluation information 46 indicating which FC switch device 44 firmware 45 version is suitable for the driver 43 version of the host bus adapter (HBA) 42 of the specific number 41 is summarized. If there is no match, a warning to that effect will be displayed.

For example, in this evaluation 46, approval by comprehensive evaluation (GA: general Admission), evaluation with restrictions only for specific customers (LA: limited support Admission), or guess evaluation (LLA:) that is not evaluated but is inferred from a close one. There is labelage limited support Admission). In addition, the operation count 47 displays the count value of the operation evaluation number, and the problem occurrence count 48 displays the count value of the problem occurrence number.

An example of a support matrix for actual display will be described below. FIG. 7 is a diagram showing an example of adding a status and count column to the example of the support matrix. For compatibility information on the combination of the host bus adapter (HBA) driver and the FC switch device firmware, see the individual host bus adapter (HBA) driver version and FC switch device firmware version. The combinations are displayed on the operation information collection application (AP) 7 as a form-style evaluation performance support matrix. This compatibility information is stored as a database (DB) on the operation information collection application (AP) 7. Specifically, the support matrix is displayed on the monitor of the personal computer (PC) operated by the operation information collection application (AP) 7.

The procedure for creating the support matrix shown in FIG. 7 will be described below using a flowchart. FIG. 12 is a flowchart showing the operation of creating the support matrix. In FIG. 12, first, the disk array device according to the embodiment of the present invention is the FDMI (Fabric Management) shown in FIG. Host bus adapter from server unit 1 host bus adapter (HBA) 2 to FC switch unit 3 host bus adapter (HBA) information management database (DB) 4 via Interface) 10 Registration of attribute information of HBA) (step S41), host bus from channel adapter (CHA) 6 of storage device 5 to host bus adapter (HBA) information management database (DB) 4 of FC switch device 3 The adapter (HBA) information was searched (step S42), and the operation information collection application (AP) 7 was searched from the channel adapter (CHA) 6 of the storage device 5 via the local area network (LAN) 11. After the information is collected and used for analysis (step S43), the operation information collection application (AP) 7 collects the configuration information of the storage device 5.

Next, the operation information collection application (AP) 7 performs the following processing from the collected firmware information of the host bus adapter (HBA) driver and the FC switch device, and the configuration information of the storage device 5.

First, the operation information collection application (AP) 7 is based on the collected information, the operating system (OS) 51 used for system operation, the host bus adapter (HBA) family 52 indicating the model name, and the host bus. The information of the adapter (HBA) driver version 53, the FC switch device family 54 indicating the model name, and the FC switch device firmware version 55 is displayed in an array in each column of the support matrix, but each column of the support matrix has already been displayed. If this combination is displayed in an array and status 56 is displayed, add +1 to the count 57 (step S44).

If either the version 53 of the host bus adapter (HBA) driver or the version 55 of the firmware of the FC switch device is different and it can be evaluated that there is no problem in the operation operation, this combination is used. Add the configuration itself as a production configuration (step S45). Therefore, by referring to the verified values of status 56 and count 57, it is possible to recommend a better combination of configurations that are compatible.

If this combination is not displayed in an array in each column of the support matrix, the combination configuration itself is added as an actual operation configuration.

In Figure 7, the operating system (OS) 51 is OS A, the host bus adapter (HBA) family 52 is HBA A, the host bus adapter (HBA) driver version 53 is 5.2.1, and the FC switch device. If family 54 is FC A and firmware version 55 of the FC switch device is 3.1.1b, status 56 has been verified and +1 is added to the count 57.

In addition, operating system (OS) 51 is OS A, host bus adapter (HBA) family 52 is HBA A, host bus adapter (HBA) driver version 53 is 5.3.0.7, and FC switch device family 54. If the firmware version 55 of the FC A and FC switch device is 3.0.2h, the status 56 has no combination verification, but it is estimated to be proven, and +1 is added to the count 57. Here, the reason why this combination has a track record by guessing is that this combination has not been directly verified, but it can be recognized as a track record by guessing from the other verified combinations shown above.

In this case, if the firmware version 55 of the FC switch device is 3.1.1b, the status 56 has been verified and the count 57 is +1. Therefore, this combination is recommended. If it does not comply with the GS-4 rules, status 56 will indicate an unsupported configuration.

Furthermore, the combination when the frequency of version upgrade is relatively high is displayed in the priority display column to correspond to this, and the combination when the frequency of version upgrade is relatively low is displayed in the fixed display column. May be good.

FIG. 8 is a diagram showing a display example of the support matrix. In FIG. 8, the host bus adapter (HBA) 61 indicating the model name, the host bus adapter (HBA) driver version 62, the microcode 63 indicating the firmware version of the storage device 5, and the firmware of the server device. Version 64, FC switch firmware version 65, Cascade 66 indicating the number of FC switch devices connected, Storage device 5 interface 67, Storage device 5 interface form topology 68, Host bus adapter (HBA) ) Display each information of topology 69 and status code 70 indicating the interface form of the driver in each column of the support matrix.

Here, for a specific customer, if the host bus adapter (HBA) 61 indicating the model name is the specific customer shown in the bottom column, a unique type is specified in Note 71 as shown on other page 1. It can be added. Specifically, the support matrix is displayed on the monitor of the personal computer (PC) operated by the operation information collection application (AP) 7.

As a result, it is possible to compare the combination to be evaluated with the combination configuration whose evaluation has been verified.

In addition, even if the evaluation has not been verified, it is possible to obtain and grasp the information of the actual operation configuration that has been introduced by the customer, and that information can be reflected in the evaluation.

Furthermore, in the case of a combination that does not exist in the evaluation performance support matrix but has an actual introduction configuration, it is possible to evaluate other combinations by assuming that it has been implemented and guessing. In addition, it is possible to narrow down the evaluation man-hours and evaluation targets.

Further, in the above-described embodiment, an example is shown in which an information database for registering the attribute information of the host bus adapter (HBA) and the attribute information of the FC switch device is provided on the switch so as to be collectable from the storage device. The operation information collection application (AP) 7 can be used to collect the host bus adapter (HBA) attribute information and the FC switch device attribute information in the information database on the FC switch device, not limited to the device. You may. Further, not limited to the connection information described above, the driver information of the crossbar switch or the disk in the storage device 5 may be collected and managed.

<figref num="1">It is a figure which shows the collection of the host bus adapter (HBA) information by the disk array apparatus which concerns on this invention.</figref><figref num="2">It is a figure which shows the failure analysis in the host bus adapter (HBA) information collection.</figref><figref num="3">It is a figure which shows the possibility of collecting information by the combination of the FC switch device and the host bus adapter (HBA) driver.</figref><figref num="4">It is a figure which shows the structure of the FC switch device.</figref><figref num="5">It is a figure which shows the structure of the storage device.</figref><figref num="6">It is a figure which shows the combination table of the firmware of a host bus adapter (HBA) driver and FC switch apparatus.</figref><figref num="7">It is a figure which shows the example which adds the status and the count column to the example of a support matrix.</figref><figref num="8">It is a figure which shows the display example of a support matrix.</figref><figref num="9">It is a flowchart which shows the registration operation of the attribute information of the HBA and FC switch apparatus.</figref><figref num="10">It is a flowchart which shows the collection operation of the attribute information of HBA.</figref><figref num="11">It is a flowchart which shows the operation of failure analysis in HBA information collection.</figref><figref num="12">It is a flowchart which shows the creation operation of a support matrix.</figref>

Code description

1 ... Server device, 2 ... Host bus adapter (HBA), 3 ... FC switch device, 4 ... Host bus adapter (HBA) Information management database (DB), 5. .. Storage Device, 6 ... Channel Adapter (CHA), 7 ... Operation Information Collection Application (AP), 8,9 ... Fiber Channel (FC), 10 ... FDMI, 11.. .Local area network (LAN), 12 ... information to be collected, 13 ... attribute information of FC switch device 3, 14 ... attribute information of host bus adapter (HBA) 2, 13-1 ... switch model, 13-2 ... vendor name, 13-3 ... firmware version, 14-1 ... operating system (OS) version, 14-2 ... host bus ... Adapter (HBA) 2 driver version, 14-3 ... Host bus adapter (HBA) 2 model name, 15 ... HBA attribute acquisition section, 16 ... Switch attribute acquisition section, 21 .. .Control Cluster 21, 22-1 ~ 22-4 ... Channel Adapter (CHA), 22-5 ... Cache Memory, 23 ... High Speed Crossbar Switch, 24-1 ~ 22-4 ... Disk -Adapter (DKA), 29 ... Disk drive (DKU), 29-1 to 29-2 ... Hard disk drive (HDD), 25 ... Control cluster, 26-1 to 26-4 .. .Channel Adapter (CHA), 26-5 ... Cache Memory, 27 ... High Speed Crossbar Switch, 28-1 ~ 28-4 ... Disk Adapter (DKA) Disk Adapter (DKA), 29- 3 ~ 29-4 ... Hard disk drive device (HDD), 31-1 ~ 31-4 ... Server device, 32-1-1, 32-1-2, 32-2-1, 32-2- 2, 32-3-1, 32-3-2, 32-4-1, 32-4-2, ... Host Bus Adapter (HBA), 33-1, 33-2 ... FC Switch Equipment, 34 ... Storage equipment, 35-1 ~ 35-4 ...Channel Adapter (CHA), 36-1 ~ 36-4 ... LU, 37-1-1, 37-1-2, 37-2-1, 37-2-2, 37-3-1, 37 -3-2, 37-4-1, 37-4-2 ... Fiber Channel (FC), 41 ... NO., 42 ... Host Bus Adapter (HBA), 43 ... Host Bus Adapter (HBA) 2 Driver Version, 44 ... FC Switch Device, 45 ... FC Switch Device Farm Version, 46 ... Rating, 47 ... Operation Count, 48 .. Problem count, 51 ... Operating system (OS), 52 ... Host bus adapter (HBA) family, 53 ... Host bus adapter (HBA) driver version, 54 ... FC switch device family, 55 ... FC switch device firmware version, 56 ... status, 57 ... count, 61 ... host bus adapter (HBA), 62 ... host. Bus adapter (HBA) driver version, 63 ... Storage device firmware microcode, 64 ... Server device firmware version, 65 ... FC switch device firmware version, 66. .. number of FC switch device cascade connections, 67 ... storage device interface, 68 ... storage device topology, 69 ... host bus adapter (HBA) driver topology, 70 ... status code , 71 ... NoteRating, 47 ... Operation count, 48 ... Problem count, 51 ... Operating system (OS), 52 ... Host bus adapter (HBA) family, 53 ... Host bus Adapter (HBA) driver version, 54 ... FC switch device family, 55 ... FC switch device firmware version, 56 ... status, 57 ... count, 61 ... host bus Adapter (HBA), 62 ... Host Bus Adapter (HBA) driver version, 63 ... Storage device firmware microcode, 64 ... Server device firmware version, 65 .. .FC switch device firmware version, 66 ... FC switch device cascade connections, 67 ... storage device interface, 68 ... storage device topology, 69 ... host bus adapter ( HBA) Driver Topology, 70 ... Status Code, 71 ... NoteRating, 47 ... Operation count, 48 ... Problem count, 51 ... Operating system (OS), 52 ... Host bus adapter (HBA) family, 53 ... Host bus Adapter (HBA) driver version, 54 ... FC switch device family, 55 ... FC switch device firmware version, 56 ... status, 57 ... count, 61 ... host bus Adapter (HBA), 62 ... Host Bus Adapter (HBA) driver version, 63 ... Storage device firmware microcode, 64 ... Server device firmware version, 65 .. .FC switch device firmware version, 66 ... FC switch device cascade connections, 67 ... storage device interface, 68 ... storage device topology, 69 ... host bus adapter ( HBA) Driver Topology, 70 ... Status Code, 71 ... NoteStatus code, 71 ... notesStatus code, 71 ... notes