Control device and control program

Abstract

To specify an abnormal part when a slight abnormality which is restored by repetition of retry occurs.SOLUTION: A control device 1 is connected with a first storage device 2 and a second storage device 3 and comprises a control unit 110 which updates, when an abnormality occurs on a communication path from the first storage device 2 to the second storage device 3, a statistic point corresponding to the communication path on which the abnormality occurs and prohibits use of the communication path on which the statistic point exceeds a threshold.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a control device and a control program. [Background technology]

[0002] A virtual tape storage device is composed of a primary storage with small capacity but high speed data transfer, a secondary storage with low speed data transfer but large capacity, and a control server that controls them as hierarchical storage. In order to provide a high speed data transfer and large capacity storage environment with a hierarchical storage configuration, recently updated data and frequently used data are stored in the primary storage. The updated data is then sequentially backed up to the secondary storage, and data is transferred between the primary and secondary storage in this manner.

[0003] The status monitoring function in a storage system monitors the status of each unit, such as a Fiber Channel (FC) card or a Hard Disk Drive (HDD), and when a clear unit failure occurs, it is detected, the faulty part is identified, and the unit is automatically disconnected. In addition, a maintenance worker performs recovery work on the disconnected unit, and the device is restored to a normal operating state. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2000-148655 A [Patent Document 2] JP 2009-259031 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in a process using multiple units such as data transfer, if a minor anomaly (hereinafter referred to as an anomaly meaning an abnormal condition that is not clearly a failure but is not) occurs that can be fixed by repeated retries, the status monitoring function cannot identify the location of the anomaly. This means that disconnection and recovery work cannot be carried out, and the anomaly continues, which is an issue.

[0006] Furthermore, the transfer path between units that appears to be one is actually made up of a combination of multiple paths, and as the number of connected units increases, the number of path combinations becomes enormous, making it even more difficult to identify the location of the abnormality.

[0007] In one aspect, the purpose is to identify the location of an abnormality when a minor abnormality occurs that can be resolved by repeated retries. [Means for solving the problem]

[0008] In one aspect, the control device is connected to a first storage device and a second storage device, and includes a control unit that, when an abnormality occurs in a communication path from the first storage device to the second storage device, updates a statistical point corresponding to the communication path in which the abnormality occurred, and disables the communication path for which the statistical point exceeds a threshold value. Effect of the Invention

[0009] In one aspect, when a minor abnormality occurs that can be resolved by repeated retries, the location of the abnormality can be identified. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a block diagram illustrating an example of the configuration of a storage system according to an embodiment. [Diagram 2] 2 is a block diagram illustrating an example of a hardware configuration of a control server illustrated in FIG. 1. [Diagram 3] 2 is a diagram illustrating an example of a system configuration table shown in FIG. 1. [Figure 4] 2 is a diagram illustrating an example of a data transfer path monitoring table shown in FIG. 1. [Diagram 5] 2 is a diagram illustrating a first example of the data transfer path monitoring table illustrated in FIG. 1; [Figure 6] 1. FIG. 4 is a diagram illustrating a second example of the data transfer path monitoring table illustrated in FIG. [Figure 7] 1. FIG. 4 is a diagram illustrating a third example of the data transfer path monitoring table illustrated in FIG. [Figure 8] 1. FIG. 4 is a diagram illustrating a fourth example of the data transfer path monitoring table illustrated in FIG. [Figure 9] 1. FIG. 13 is a diagram illustrating a fifth example of the data transfer path monitoring table illustrated in FIG. [Figure 10] 10 is a flowchart illustrating a process of isolating an abnormal portion in an embodiment. [Figure 11] 11 is a flowchart illustrating a preparation process according to an embodiment. [Figure 12] 11 is a flowchart illustrating a statistical point addition process in the embodiment. [Figure 13] 10 is a flowchart illustrating an abnormal route narrowing down estimation process according to an embodiment. [Figure 14] 10 is a flowchart illustrating a maintenance work process for an estimated abnormal portion in the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] [A] Embodiment An embodiment will be described below with reference to the drawings. However, the embodiment described below is merely an example, and there is no intention to exclude the application of various modified examples and techniques not specified in the embodiment. In other words, the present embodiment can be implemented with various modifications within the scope of the gist of the embodiment. In addition, each figure does not intend to include only the components shown in the figure, but can include other components, etc.

[0012] [A-1] Configuration example FIG. 1 is a block diagram illustrating a configuration example of a storage system 100 according to an embodiment.

[0013] The storage system 100 includes a control server 1, a primary storage 2, and a secondary storage 3.

[0014] The primary storage 2 may be, for example, a disk array device, and includes a plurality of Channel Adapters (CA) 21 (CA:1 to CA:4 in the example shown in FIG. 1). Each CA 21 includes a monitoring unit ("S" in FIG. 1) used to monitor the state of the CA 21.

[0015] The secondary storage 3 may be, for example, a tape library device, and includes a plurality of tape drives (DRVs) 31 (DRV:1 to DRV:4 in the example shown in FIG. 1). Each DRV 31 includes a monitoring unit ("S" in FIG. 1) used to monitor the status of the DRV 31.

[0016] The control server 1 is an example of a control device (in other words, a computer) and includes multiple FC cards 171 (FC:1 to FC:4 in the example shown in FIG. 1). Multiple FC ports (P) 172 are attached to each FC card 171. Specifically, P:1 and P:2 are attached to FC:1, P:3 and P:4 are attached to FC:2, P:5 and P:6 are attached to FC:3, and P:7 and P:8 are attached to FC:4. Each FC card 171 and each P172 is provided with a monitoring unit ("S" in FIG. 1) used to monitor the status of the FC cards 171 and P172.

[0017] The control server 1 includes the functions of a system control unit 110 and a system management unit 120 .

[0018] The system control unit 110 is a component that controls all processes (e.g., data transfer, information collection of installed hardware, and incorporating / disconnecting hardware from the system) on the control server 1. The system control unit 110 functions as a status monitoring unit 111, a statistical point addition processing update unit 112, and an abnormality location estimation unit 113.

[0019] The system management unit 120 is a component that manages various information on the control server 1, and updates the information it manages and calls up current information in response to instructions from the system control unit 110. The system management unit 120 includes a system configuration table 121 and a data transfer path monitoring table 122 that includes statistical point addition information.

[0020] The system configuration table 121 will be described later with reference to FIG. 3 and the like, and the data transfer path monitoring table 122 will be described later with reference to FIG.

[0021] The status monitoring unit 111 uses the data transfer path monitoring table 122 to monitor an abnormal state for each data transfer path.

[0022] When a minor abnormality occurs, the statistical point addition processing update unit 112 adds a statistical point addition for each used route in the data transfer path monitoring table 122. When the statistical point addition processing update unit 112 updates the statistical point addition of the data transfer path monitoring table 122 and the statistical point addition of a certain route reaches a new predetermined reference point, the statistical point addition processing update unit 112 acquires information for all routes included in the data transfer path monitoring table 122.

[0023] The abnormality location inferring unit 113 searches for any other routes whose statistical points have reached a predetermined reference point, based on the information for all routes received in the data transfer route monitoring table 122. If no such route is found, the abnormality location inferring unit 113 temporarily disables the use of all routes that use the same FC card 171, and if any such route is found, it checks whether there are any common points between the routes.

[0024] If there are no common points, the abnormality location estimation unit 113 temporarily prohibits the use of all routes that use the same FC card 171, and if there are common points, it checks whether there is one common point or multiple common points.

[0025] If there is one common location, the abnormality location estimation unit 113 estimates that location as the abnormality location, and if there are multiple common locations, temporarily prohibits the use of all routes that simultaneously use the common location.

[0026] FIG. 2 is a block diagram illustrating an example of a hardware configuration of the control server 1 illustrated in FIG.

[0027] As shown in FIG. 2, the control server 1 includes a central processing unit (CPU) 11, a memory 12, a display control device 13, a storage device 14, an input interface (IF) 15, an external recording medium processing device 16, and a communication IF 17.

[0028] The memory 12 is an example of a storage unit, and is illustratively a Read Only Memory (ROM) and a Random Access Memory (RAM). Programs such as a Basic Input / Output System (BIOS) may be written in the ROM of the memory 12. The software programs in the memory 12 may be appropriately read and executed by the CPU 11. The RAM of the memory 12 may be used as a temporary storage memory or a working memory.

[0029] The display control device 13 is connected to a display device 131 and controls the display device 131. The display device 131 is a liquid crystal display, an organic light-emitting diode (OLED) display, a cathode ray tube (CRT), an electronic paper display, or the like, and displays various information for an operator, etc. The display device 131 may be combined with an input device, for example, a touch panel. The display device 131 displays various information for a user of the control server 1.

[0030] The storage device 14 is a storage device with high IO performance, and may be, for example, a dynamic random access memory (DRAM), a solid state drive (SSD), a storage class memory (SCM), or a hard disk drive (HDD).

[0031] The input IF 15 may be connected to input devices such as a mouse 151 and a keyboard 152, and may control the input devices such as the mouse 151 and the keyboard 152. The mouse 151 and the keyboard 152 are examples of input devices, and an operator performs various input operations via these input devices.

[0032] The external recording medium processing device 16 is configured so that the recording medium 160 can be attached thereto. The external recording medium processing device 16 is configured so that, when the recording medium 160 is attached thereto, the information recorded on the recording medium 160 can be read. In this example, the recording medium 160 is portable. For example, the recording medium 160 is a flexible disk, an optical disk, a magnetic disk, a magneto-optical disk, a semiconductor memory, or the like.

[0033] The communication IF 17 is an interface for enabling communication with an external device, such as the FC card 171 or P172 shown in FIG.

[0034] The CPU 11 is an example of a processor, and is a processing device that performs various controls and calculations. The CPU 11 realizes various functions by executing an Operating System (OS) and programs loaded into the memory 12. The CPU 11 may be a multiprocessor including multiple CPUs, a multicore processor having multiple CPU cores, or a configuration having multiple multicore processors.

[0035] The device for controlling the overall operation of the control server 1 is not limited to the CPU 11, and may be, for example, any one of MPU, DSP, ASIC, PLD, and FPGA. The device for controlling the overall operation of the control server 1 may be a combination of two or more of CPU, MPU, DSP, ASIC, PLD, and FPGA. Note that MPU is an abbreviation for Micro Processing Unit, DSP is an abbreviation for Digital Signal Processor, and ASIC is an abbreviation for Application Specific Integrated Circuit. Also, PLD is an abbreviation for Programmable Logic Device, and FPGA is an abbreviation for Field Programmable Gate Array.

[0036] FIG. 3 is a diagram illustrating an example of the system configuration table 121 shown in FIG.

[0037] The system configuration table 121 is compiled by the system management unit 120 and includes hardware information of the FC card 171 installed in the control server 1, as well as hardware information of the CA21 of the primary storage 2 connected via the FC card 171, and hardware information of the DRV31 of the secondary storage 3.

[0038] In the system configuration table 121, unit types, unit names, unit World Wide Names, unit statuses, and statistical points are associated with each other.

[0039] In FIG. 3, for example, for the unit type "Channel Adapter", a unit name "CA:1", a unit World Wide Name "************", a unit status "active", and a statistical score "0" are registered.

[0040] FIG. 4 is a diagram illustrating the data transfer path monitoring table 122 shown in FIG.

[0041] The data transfer path monitoring table 122 is generated based on the system configuration table 121, and statistical point addition information for each data transfer path in the storage system 100 is registered.

[0042] In the system configuration table 121, a path name, a configured path, a path state, and a statistical score are associated with each other.

[0043] In FIG. 4, for example, the route name "Route #1" has the route configuration "CA:1, P1-FC:1, FC:3-P5, DRV:1", the route status "Available", and the statistical score "0" registered.

[0044] The abnormality portion estimation unit 113 periodically refers to the data transfer path monitoring table 122, and when the statistical score of a certain path reaches a predetermined reference point, searches for the presence or absence of other paths whose statistical scores have also reached the predetermined reference point.

[0045] When there is another route that has reached the reference point, the abnormal portion estimation unit 113 checks whether or not there is a common portion between the routes. On the other hand, when there is only one common portion, the abnormal portion estimation unit 113 estimates that the common portion is the abnormal portion.

[0046] FIG. 5 is a diagram showing a first example of the data transfer path monitoring table 122 shown in FIG.

[0047] In the example shown in Figure 5, when route #1 and route #5 reach a reference value (for example, a statistical score of "10"), the only common location is "FC:1", and the abnormality location estimation unit 113 estimates that "FC card #1" is the suspect location.

[0048] FIG. 6 is a diagram showing a second example of the data transfer path monitoring table 122 shown in FIG.

[0049] In the example shown in FIG. 6, when route #1 and route #2 reach a reference value (for example, a statistical score of "10"), there are two common points, "FC:1" and "FC:3", and no abnormal points can be estimated.

[0050] Therefore, the abnormality portion estimation unit 113 sets all paths that simultaneously use the common portion to "prohibited" and continues the operation of the storage system 100. Thereafter, the abnormality portion estimation unit 113 repeats the process of checking whether there is a common portion between the path whose statistical score has reached the reference point and the prohibited path, and estimates the matching common portion as a suspected portion.

[0051] FIG. 7 is a diagram showing a third example of the data transfer path monitoring table 122 shown in FIG.

[0052] If there are two common locations, "FC:1" and "FC:3", the abnormality location estimation unit 113 sets routes #1, #2, #3, and #4, which use them simultaneously, to "prohibited use". After that, when route #5 reaches a reference value (for example, statistical points of "10"), the only common location is "FC:1", and the abnormality location estimation unit 113 estimates that "FC card #1" is the suspect location.

[0053] The route status of route #5 (see "*") may be either usable or unusable.

[0054] If there is no other route that has reached the reference point, the abnormality portion estimating unit 113 sets all routes that use all of the same FC cards 171 as the route in question as "prohibited from use."

[0055] FIG. 8 is a diagram showing a fourth example of the data transfer path monitoring table 122 shown in FIG.

[0056] In the example shown in Figure 8, if only route #1 reaches a reference value (for example, statistical score "10"), the abnormality location estimation unit 113 will set route #1, route #2, route #3, and route #4, which all use the same FC card 171, including route #1, to "prohibited for use."

[0057] The abnormality location inferring unit 113 continues the operation of the storage system 100, and searches for the presence or absence of another path that will cause the statistical score to reach a predetermined reference point.

[0058] When a route occurs in which the statistical score has reached a reference point, the abnormality portion estimation unit 113 checks whether or not there is a common portion between the routes.

[0059] When there is one common location, the abnormality location estimating unit 113 estimates the common location as the abnormality location, similarly to the first example shown in FIG.

[0060] On the other hand, if there are multiple common locations, the abnormality location cannot be inferred, so the abnormality location inferring unit 113 sets all paths that simultaneously use the common locations as "prohibited" and allows the storage system 100 to continue operating.

[0061] Thereafter, similar to the third example shown in FIG. 7, the abnormality location estimation unit 113 repeats the process of checking whether there are any common points between the route whose statistical score reaches the reference point next and the prohibited route, and estimates the matching common points as suspect locations.

[0062] FIG. 9 is a diagram showing a fifth example of the data transfer path monitoring table 122 shown in FIG.

[0063] In the example shown in Figure 9, after routes #1, #2, #3, and #4 were all set to "prohibited for use," only routes #13, #14, #15, and #16 were used for a while, so it is assumed that there were no common points with routes #1 to #4 and no statistical points were added.

[0064] In this case, the abnormality portion estimating unit 113 continues the operation of the storage system 100 and monitors the tendency of statistical points to be added due to the use of paths other than paths #13 to #16.

[0065] The storage system 100 equipped with the secondary storage 3 (in other words, a tape library device) has a function called "load balancing," which controls the frequency of use of paths used during data transfer so that it is even over the long term. Therefore, there is always an opportunity for each path to be used.

[0066] Thereafter, it is possible to estimate the suspected portion by processing similar to that of the first example shown in FIG. 5 or the third example shown in FIG.

[0067] After the maintenance work on the suspected portion is completed, the status monitoring unit 111 lifts the prohibition on the use of the “path including the abnormal portion” and resets the statistical points added to the data transfer path monitoring table 122 .

[0068] [A-2] Example of operation The process of isolating an abnormal portion in this embodiment will be described with reference to the flow chart (steps S1 to S12) shown in FIG.

[0069] The status monitoring unit 111 generates the data transfer path monitoring table 122 (step S1).

[0070] The status monitoring unit 111 judges whether an abnormality has occurred in any of the paths within the storage system 100 (step S2).

[0071] If no abnormality has occurred (see the NO route from step S2), the process in step S2 is repeatedly executed.

[0072] On the other hand, if an abnormality has occurred (see the YES route from step S2), the state monitoring unit 111 records the abnormal state (step S3), and the process of narrowing down the abnormal location starts.

[0073] The abnormality location estimating unit 113 determines whether or not it is possible to identify the failure location (step S4).

[0074] If the fault location can be identified (see the YES route in step S4), the abnormality location estimating unit 113 isolates the identified abnormality location (step S5), and the abnormality location isolation process ends.

[0075] On the other hand, if the fault location cannot be identified (see the NO route from step S4), the abnormality location estimating unit 113 determines whether the abnormality location can be identified (step S6).

[0076] If the abnormality location can be identified (see the YES route in step S6), the abnormality location estimating unit 113 separates the identified abnormality location (step S7), and the abnormality location separation process ends.

[0077] On the other hand, if the abnormal location cannot be identified (see the NO route from step S6), the statistical point addition process update unit 112 statistically tallies the abnormal situation (step S8).

[0078] The statistical score processing update unit 112 calculates the statistical score (step S9).

[0079] The abnormality portion estimation unit 113 narrows down the abnormal portions based on the statistical score (step S10).

[0080] The abnormality location estimating unit 113 determines whether or not an abnormality location can be identified (step S11).

[0081] If the abnormal location cannot be identified (see the NO route from step S11), the process returns to step S2.

[0082] On the other hand, if it is possible to identify the abnormality (see the YES route in step S11), the abnormality portion estimation unit 113 separates the estimated abnormality portion (step S12), and the abnormality portion separation process ends.

[0083] Next, the preparation process in this embodiment will be described with reference to the flowchart (steps S21 to S25) shown in FIG.

[0084] The status monitoring unit 111 collects hardware information of the FC card 171 mounted in the control server 1 (step S21).

[0085] The state monitoring unit 111 collects hardware information of the CA 21 of the primary storage 2 connected via the FC card 171 (step S22).

[0086] The state monitoring unit 111 collects hardware information of the DRV 31 of the secondary storage 3 (step S23).

[0087] The state monitoring unit 111 generates device configuration information (in other words, a system configuration table 121) from the collected information (step S24).

[0088] The state monitoring unit 111 generates the data transfer path monitoring table 122 based on the generated device configuration information (in other words, the system configuration table 121) (step S25), and the preparation process then ends.

[0089] Next, the statistical point addition process in the embodiment will be described with reference to the flowchart (steps S31 to S35) shown in FIG.

[0090] The statistical point addition process update unit 112 executes data transfer within the storage system 100 (step S31).

[0091] The statistical point addition process update unit 112 determines whether the data transfer has been normally executed (step S32).

[0092] If the data transfer has been normally executed (see the YES route from step S32), the statistical point addition process ends.

[0093] On the other hand, if the data transfer has not been performed normally (see the NO route from step S32), the statistical point increment process update unit 112 increments the points in the data transfer path monitoring table 122 (step S33).

[0094] The data transfer path monitoring table 122 judges whether the statistical addition point in the data transfer path monitoring table 122 exceeds a reference value (step S34).

[0095] If the statistical point addition does not exceed the reference value (see the NO route from step S34), the statistical point addition process ends.

[0096] On the other hand, if the statistical point addition exceeds the reference value (see the YES route in step S34), the statistical point addition processing update unit 112 sets a flag in the data transfer path monitoring table 122 (step S35). That is, the statistical point addition processing update unit 112 changes the path status in the data transfer path monitoring table 122 shown in Fig. 4 from "available" to "unavailable". Then, the statistical point addition processing ends.

[0097] Next, the abnormal route narrowing down estimation process in the embodiment will be described with reference to the flowchart (steps S41 to S49) shown in FIG.

[0098] The abnormality portion inferring unit 113 refers to the data transfer path monitoring table 122 (step S41).

[0099] The abnormality portion estimating unit 113 determines whether there is any new route that has exceeded the reference value (step S42).

[0100] If there is no new route that exceeds the reference value (see the NO route in step S42), the abnormality portion estimation unit 113 waits for a certain period of time (step S43), and the process returns to step S41.

[0101] On the other hand, if there is a new route that exceeds the reference value (see the YES route in step S42), the abnormal portion estimating unit 113 determines whether there are multiple routes that exceed the reference value (step S44).

[0102] If there are not multiple routes that exceed the reference value (see the NO route in step S44), the abnormality location estimating unit 113 prohibits the use of all routes that use the same FC card 171 as the route in question (step S45). Note that the abnormality location estimating unit 113 leaves behind any routes that use at least one different FC card 171. Then, the process proceeds to step S43.

[0103] On the other hand, if there are multiple routes that exceed the reference value (see the YES route in step S44), the abnormality portion estimation unit 113 determines whether the multiple routes that exceed the reference value have a common portion (step S46).

[0104] If there is no common portion (see NO route from step S46), the process proceeds to step S45.

[0105] On the other hand, if there is no common location (see the YES route from step S46), the abnormality location estimating unit 113 determines whether there is one common location (step S47).

[0106] If the number of common locations is not one (see NO route in step S47), the abnormality location estimating unit 113 prohibits the use of all routes that simultaneously use the common location (step S48), and the process returns to step S43.

[0107] On the other hand, if there is one common location (see the YES route in step S47), the abnormality location estimation unit 113 estimates the common location as an abnormality location (step S49), and the abnormality route narrowing-down estimation process ends.

[0108] Next, the maintenance work process for the estimated abnormal portion in this embodiment will be described with reference to the flowchart (steps S51 to S53) shown in FIG.

[0109] Maintenance work is carried out on the isolated abnormal portion (step S51).

[0110] The status monitoring unit 111 updates the data transfer path monitoring table 122 and lifts the prohibition on the use of the path including the abnormal portion that has been maintained (step S52).

[0111] The status monitoring unit 111 updates the data transfer path monitoring table 122 and resets the statistical points of the path including the abnormal portion that has been maintained (step S53).

[0112] [B] Effect According to the control device and the control program in the above-described embodiment, for example, the following advantageous effects can be obtained.

[0113] When an abnormality occurs in the communication path from the first storage device to the second storage device, the statistical score adding process update unit 112 updates the statistical score corresponding to the communication path in which the abnormality occurs. The abnormality location estimation unit 113 disables the communication path in which the statistical score exceeds the threshold value.

[0114] This makes it possible to identify the location of the abnormality when a minor abnormality occurs that can be recovered by repeated retries. Specifically, in a virtual tape storage device, even minor abnormalities that can be recovered by repeated retries can be detected by the status monitoring function, and the device can be quickly restored to normal by performing maintenance work. In addition, the path containing the abnormality is prohibited from use until the maintenance work is completed, making it possible to suppress performance degradation of the device.

[0115] When there are multiple communication paths whose statistical points exceed the threshold, the abnormality portion estimation unit 113 disables the use of the multiple communication paths.

[0116] This makes it possible to prevent the use of multiple paths, including the abnormal part, until the maintenance work is completed, thereby making it possible to prevent a decrease in performance of the device.

[0117] When there are multiple common paths among the multiple communication paths, the abnormality portion estimating unit 113 prohibits the use of any of the multiple communication paths that use the common paths.

[0118] This makes it possible to prevent the use of the common route including the abnormal part until the maintenance work is completed, thereby making it possible to prevent a decrease in the performance of the device.

[0119] When there is one common path among a plurality of communication paths, the abnormality portion estimating unit 113 estimates the common path as an abnormality portion.

[0120] This allows the location of the abnormality to be accurately estimated.

[0121] [C] Other The disclosed technology is not limited to the above-described embodiment, and various modifications can be made without departing from the spirit of the present embodiment. Each configuration and each process of the present embodiment can be selected as necessary, or can be combined as appropriate.

[0122] [D] Additional Notes The following supplementary notes are further disclosed regarding the above embodiment.

[0123] (Appendix 1) A control device connected to a first storage device and a second storage device, When an abnormality occurs in a communication path from the first storage device to the second storage device, updating a statistical point corresponding to the communication path in which the abnormality occurs; Disable the communication path for which the statistical point exceeds the threshold value; A control device having a control unit.

[0124] (Appendix 2) The control unit is When there are a plurality of communication paths whose statistical points exceed a threshold, the plurality of communication paths are prohibited from use. 2. The control device according to claim 1.

[0125] (Appendix 3) The control unit is When there are a plurality of common paths among the plurality of communication paths, the paths that use the common paths among the plurality of communication paths are prohibited from use. 3. The control device according to claim 2.

[0126] (Appendix 4) The control unit is When there is one common path among the plurality of communication paths, the common path is estimated as an abnormality location. 4. The control device according to claim 2 or 3.

[0127] (Appendix 5) A computer connected to the first storage device and the second storage device, When an abnormality occurs in a communication path from the first storage device to the second storage device, updating a statistical point corresponding to the communication path in which the abnormality occurs; Disable the communication path for which the statistical point exceeds the threshold value; A control program that executes processing.

[0128] (Appendix 6) When there are a plurality of communication paths whose statistical points exceed a threshold, the plurality of communication paths are prohibited from use. 6. The control program according to claim 5, which causes the computer to execute a process.

[0129] (Appendix 7) When there are a plurality of common paths among the plurality of communication paths, the paths that use the common paths among the plurality of communication paths are prohibited from use. 7. The control program according to claim 6, which causes the computer to execute a process.

[0130] (Appendix 8) When there is one common path among the plurality of communication paths, the common path is estimated as an abnormality location. 8. The control program according to claim 6 or 7, which causes the computer to execute a process. [Explanation of symbols]

[0131] 100: Storage systems 1: Control server 11: CPU 110: System control unit 111: Status monitoring unit 112: Statistical point addition processing update section 113: Abnormal location estimation section 12: Memory 120: System Management Department 121: System configuration table 122: Data transfer path monitoring table 13: Display control device 131:Display device 14:Storage device 15: Input IF 151: Mouse 152: Keyboard 16: External recording medium processing device 160: Recording media 17: Communication Interface 171:FC Card 172 :P 2: Primary storage 21 :CA 3: Secondary storage 31 :DRV

Claims

1. A control device connected to a first storage device and a second storage device, When an abnormality occurs in a communication path from the first storage device to the second storage device, a statistical point corresponding to the communication path in which the abnormality occurs is updated; Disable the communication path for which the statistical point exceeds the threshold value; A control device having a control unit.

2. The control unit is When there are a plurality of communication paths whose statistical points exceed a threshold, the plurality of communication paths are prohibited from use. The control device according to claim 1 .

3. The control unit is When there are a plurality of common paths among the plurality of communication paths, the paths that use the common paths among the plurality of communication paths are prohibited from use. The control device according to claim 2.

4. The control unit is When there is one common path among the plurality of communication paths, the common path is estimated as an abnormality location. The control device according to claim 2 or 3.

5. A computer connected to the first storage device and the second storage device, When an abnormality occurs in a communication path from the first storage device to the second storage device, a statistical point corresponding to the communication path in which the abnormality occurs is updated; Disable the communication path for which the statistical point exceeds the threshold value; A control program that executes processing.

Images