JP2000215086A - Device and method for gathering fault information of fc-al and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To actualize a method which bypasses a device connected to a hub through association of various monitors, port by port, executes T and D to gather fault information, and manages it in a pair with log information if a fault occurs to a FC-AL(fiber channel arbitrated loop) system. SOLUTION: A syslog monitor 26 monitors a syslog file 21 and when log information of a FC-AL fault is present, a loop closure monitor 27 closes the loop through fault closure and switches it to an alternative loop. A hub control indication monitor 28 forces one connection port of a node or device connected to the faulty loop to bypass the hub by using a hub management AP 29. A T and D execution indication monitor 2A instructs a T and D executing means 2B to execute T and D. A T and D execution result monitor 2C checks the execution result in a T and D execution result file 24 and outputs an error to an FC-AL fault information file 22 in a pair with the log information if the error is found.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer system (hereinafter, referred to as a node) in which a disk array device is connected to a fiber channel arbitrated loop (hub) via a hub.
Bitrated Loop, hereinafter referred to as FC-AL. The present invention relates to an FC-AL fault information collecting device and a fault information collecting method in a system connected to the system.

[0002]

2. Description of the Related Art A failure in a system configuration in which a plurality of nodes and an array device are FC-AL connected via a hub is as follows.
A point-to-point connection between the node and the disk array device makes it difficult to locate the failure point compared to the failure in the system configuration, but it is necessary to quickly and accurately locate the failure point There is no difference. Conventionally, an example of a diagnostic program starting method for collecting fault information in this type of system is disclosed in Japanese Unexamined Patent Publication No.
No. 49541. This technique is a diagnostic program start-up method having a log file for storing abnormality information generated in an operating device, a log information rewriting management means for managing rewriting of log information in a log file, and a log file entire area. Log information analyzing means for analyzing the contents of the log file in response to the update of the log file, diagnostic program starting means for starting a diagnostic program with reference to the analyzed log information, and diagnostic result display means, An object of the present invention is to effectively utilize information recorded in a file and to detect an abnormality of an apparatus at an early stage.

[0003]

However, this prior art has the following problems. The first problem is that information on the system at the time of the failure cannot be collected. The reason is that the log file is evacuated when the entire area of the log file is updated, the contents of the evacuated log file are analyzed, and the diagnostic program is started and executed by referring to the analyzed log information. . In other words, because the diagnostic program is not immediately executed when a failure occurs, it is not possible to collect system operation information at the time of the failure, and it is not possible to collect failure information in cases where it is difficult to identify the failure location such as an intermittent failure The nature is high. Also,
The second problem is that it is not possible to reconfirm the execution result of the diagnostic program and to grasp which abnormality information in the log file corresponds to the diagnostic result. The reason is that the execution result of the diagnostic program is displayed, but is not output to a file, and is not associated with the abnormal information in the log file.

Therefore, in this technique, the means for analyzing the abnormal information of the detected log file, determining the device to be diagnosed and the diagnostic program, and activating the diagnostic program is the best, but the execution result of the diagnostic program is the best. If it becomes necessary to reconfirm the error, or if the relationship between the abnormality information in the log file and the execution result of the diagnostic program is associated with each other, the result of the previously executed diagnostic program cannot be used. Further, a third problem is that collection of fault information for intermittent faults is not considered. The reason is that it is not considered to monitor the operation status of the system for a long time and collect the fault information.
Intermittent failures, unlike fixed failures, do not remain as failures, so failure of a single execution of the diagnostic program does not cause failures, and in some cases errors are not detected. This reduces the accuracy of failure information and delays maintenance work. And maintenance omissions can occur. Therefore, an object of the present invention is to record a failure information collection device of FC-AL, a failure information collection method, and a processing procedure according to the method, which can automatically collect more detailed failure information and operation information of a system when a failure occurs. It is to provide a recording medium. Another object of the present invention is to provide an FC-AL fault information collecting apparatus, a fault information collecting method, and a processing procedure according to the method, which can obtain information necessary for fault location identification with a small number of steps. An object of the present invention is to provide a recorded recording medium. Further, another object of the present invention is to provide an FC-AL fault information collecting apparatus, a fault information collecting method, and a recording medium on which a processing procedure according to this method can be collected even when an intermittent fault occurs. It is in.

[0005]

According to the FC-AL fault information collecting apparatus of the present invention, a plurality of nodes and a plurality of disk array devices are connected via a hub to a fiber channel arbitrated loop (FC-AL). In the failure information collection device in the connected system, each of the nodes includes a system log file for managing log information collected when a failure occurs in the system or the device, and log information and T & D related to FC-AL. FC-AL failure information file for managing the execution result of T & D execution result file for managing the execution result of T & D, a syslog monitoring monitor for monitoring the output contents of the syslog file, and FC-AL
When there is log information of a failure, a loop closure monitor that performs closure of the failure loop and switches to an alternative loop, a hub management application having a function of forcibly bypassing the hub on a port basis, and after switching the loop, Using a management application, a hub control instruction monitor forcibly bypassing a connection port of one of the nodes or disk array devices connected to the failed loop from the hub, and executing T & D according to an instruction from the hub control instruction monitor T & D execution instruction monitor for instructing, T & D execution means for executing T & D and outputting the result to the T & D execution result file, and checking the execution result of T & D to the FC-AL failure information file if there is error information It has a T & D execution result monitoring monitor to output the above series of processes to the fault loop. And performing repeated for all of the nodes and disk array device being. Further, in the FC-AL failure information collection method of the present invention, a plurality of nodes and a plurality of disk array devices are connected via a hub to a Fiber Channel arbitrated system.
In the method for collecting fault information in a loop (FC-AL) connected system, a procedure for monitoring the output contents of a syslog file collected when a fault occurs in the system or the device, and a log of the FC-AL fault by the monitoring. When the information is present, a procedure for closing the failed loop to switch to the alternative loop, and after the switching of the loop, connected to the failed loop using a hub management application having a function of forcibly bypassing the hub on a port basis. Check the procedure for forcibly bypassing the connection port of one of the connected nodes or disk array devices from the hub, executing the T & D, outputting the T & D execution result to a file, and checking the T & D execution result. F if there is error information
Outputting to a C-AL failure information file, and repeating the above series of processing for all the nodes and disk array devices connected to the failure loop. The recording medium of the present invention is characterized by recording a program for executing each procedure of the above method. In the present invention, the log information of the FC-AL failure in the system log information is provided by a syslog monitoring monitor that monitors the system log information collected when a failure occurs in the system or the device at certain intervals. It checks for the presence or absence, and if the log information exists, outputs the log information to the FC-AL failure information file and instructs the loop closure monitor that closes the failure loop to operate. The loop blocking monitor closes the failed loop, switches the operation to the alternative loop, and then to the hub control monitor that enables the node and disk array device connected to the failed loop to be forcibly bypassed from the hub on a port basis. Instruct operation. The hub control monitor interfaces with the management AP of the hub, and forcibly bypasses the connection port of one of the nodes and disk array devices connected to the failed loop from the hub, and performs test / test.
Instructs the T & D execution instruction monitor that inputs the diagnostic program (T & D) to operate. The T & D execution instruction monitor inputs a T & D command to execute T & D, outputs an execution result to a T & D execution result file, and instructs a T & D execution result monitoring monitor that checks the T & D execution result. The T & D execution result monitoring monitor checks whether there is T & D error information in the T & D execution result, and if the error information exists, outputs it to the FC-AL failure information file in combination with the previous log information, If the error information does not exist, delete the FC-AL failure information file without outputting it. This series of processing is repeated until the processing for all the nodes and the disk array device is completed while repeatedly performing the forced bypass and the T & D execution one by one for the nodes and the disk array devices connected to the failure loop. Further, the processing for all the nodes and the disk array device connected to the failure loop is repeatedly performed until the predetermined number of times of T & D execution / time is satisfied. The collected failure information is automatically notified to the maintenance center by the T & D execution result monitoring monitor and used for maintenance work by maintenance personnel to identify the failure location. As a precondition in the present invention, the hub uses an intelligent hub that can be forcibly bypassed by the hub management AP, and
The hub management AP has a forced bypass function for each port of the hub, and has an application interface capable of receiving a forced bypass instruction from a hub control monitor via Ethernet and controlling the hub. .

[0006]

Next, embodiments of the present invention will be described with reference to the drawings. FIG. 2 shows an example of a system configuration to which the present invention is applied. This system uses multiple nodes
11n (3 in the embodiment of 1 ≦ n) and a plurality of fibers
Channel cable (hereinafter referred to as FC cable) 12n
(6 in the embodiment of 1 ≦ n) and a plurality of hubs 13n (1 ≦ n
n In the embodiment, four) and a plurality of disk array devices 1
4n (1 ≦ n, 5 in the embodiment).
A channel portion connecting the node 11n and the disk array device 14n is configured in an FC-AL connection mode via a hub 13n in the middle, and the node 11n or the disk array device 14n is connected to the hub 13n by an FC cable 12n. . The FC-AL is a duplex configuration of an operation loop 15 used during operation and a standby loop 16 used when the operation loop 15 becomes unavailable due to a failure or the like. The node 11n or the disk array device 14n Connected to 16. Referring to FIG.
Node 111 according to one embodiment (first embodiment) of the present invention
Is shown, and the relationship between software (including a monitor) and various files is clarified. The files in the node 111 include a syslog file 21 for managing system log information, FC-AL-related log information and T
FC-AL failure information file 2 for managing & D execution results
2, configuration information file 23 for managing system configuration information, T & D execution result file 24 for managing T & D execution results, collection of monitor control information, T & D execution / end information, and fault information It comprises a control information file 25 for managing the situation.

The software (hereinafter referred to as SW) in the node 111 is connected to a syslog monitoring monitor 26 for monitoring the output contents of the syslog file 21 and a loop closing monitor 27 for closing a faulty loop. A hub control instruction monitor 28 (which is an interface to the hub management AP 29) for instructing a device to be forced, a hub management AP 29 forcibly bypassing the hub 111 in port units, and a T & D execution instruction monitor 2A for instructing T & D execution And T & D execution means 2B, and a T & D execution result monitoring monitor 2C for automatically notifying the failure information at the end of monitoring the execution result of T & D and collecting failure information. The relationship between SWs and the relationship between SWs and files are as shown in FIG. Note that all the nodes 11n have the same configuration having the same SW and file as shown in FIG. FIG. 3 shows various monitors and T & D used in practicing the present invention.
7 shows the configuration of a control information file 25 for managing the control information of D, the execution and termination information of T & D, and the collection status of fault information. Syslog monitoring interval 31 in this control information file 25,
FC-AL failure message code 32 and T & D termination condition (number of times /
The time) 33, the T & D name 34, and the T & D error code 35 need to be registered in advance by a maintenance person or a user. sysl
The og monitoring interval 31 indicates the timing at which the syslog monitoring monitor 26 monitors (searches) the syslog file 21. FC-AL failure message code 32 is a code that can recognize and determine that a failure has
The monitoring monitor 26, based on the output contents of the syslog file 21,
This is a key code used to check whether there is FC-AL fault information.

The T & D end condition (number / time) 33 indicates the end condition at the time of executing the T & D by the number of times or the time. When this condition is satisfied, the execution of the T & D for the fault information of the FC-AL is ended. . The T & D name 34 indicates the name of the T & D to be executed. The T & D error code 35 is a code capable of recognizing and judging that an error has occurred in the execution result of the T & D.
This is the key code used to check for the presence of T & D error information based on the output contents of 24. The index code 36 is used to store FC-AL failure log information output by the syslog monitoring monitor 26 to the FC-AL failure information file 22 and T
The & D execution result monitoring monitor 2C is a unique code that is a key used when paired with the T & D error information extracted from the T & D execution result file 24 and output to the FC-AL failure information file 22. This T & D error information is based on the FC & AL failure log information extracted by the syslog monitor 26.
Is included in the execution result. The operation loop (before shutdown) 37 indicates the operation loop before the loop shutdown, and the operation loop (after shutdown) 38
Indicates an operation loop after the loop is closed. Bypass device information
Reference numeral 39 denotes bypassed device information (HW path, special file name, etc.). The hub bypass status 3A indicates whether or not the bypass for all devices connected in a loop has been completed. The T & D execution count 3B indicates the number of T & D executions, and is used when the hub control instruction monitor 28 determines whether or not the T & D has been completed. The T & D execution start time 3C indicates the T & D execution start time, and is used when the hub control instruction monitor 28 determines whether or not the T & D is about to end. Error information collection status 3D is syslog
This indicates whether the work of collecting the failure information for the FC-AL failure log information extracted by the monitoring monitor 26 has been completed.

FIG. 4 shows management items and examples of management information of the FC-AL failure information file 22 among failure information collected by various monitors when the present invention is carried out. The collected timing and the location of the base information will be described later. The FC-AL failure information file 22 performs generation management, and after completion of the failure information collection work, is automatically notified to the maintenance center by the T & D execution result monitoring monitor 2C. Next, referring to FIGS.
The operation of the present embodiment will be described in detail. The various monitors shown in FIG. 1 start up when the system starts up, and become operable. Hereinafter, the operation of each monitor will be described with reference to the flowcharts shown in FIGS. FIG. 5 shows a processing flow of the syslog monitoring monitor 26. The syslog monitoring monitor 26 performs the following processing for each syslog monitoring interval 31 of the control information file 25 registered in advance by a maintenance person or a user. First, the output contents of the syslog file 21 are searched (step 51 in FIG. 5), and the control information file 25 is searched.
The FC-AL error message code 32 is obtained from the server, the index code 36 is set (step 52), and the obtained FC-AL
It is checked whether there is log information matching the failure message code 32 (step 53). As a result, when matching log information is detected (step 54), the log information is extracted (step 55), and device information such as an HW path and a special file name for the failed device is obtained from the configuration information file 23 (step 56). ), Adding a unique index code and device information of the faulty device to the FC-AL fault information file 22
(Step 57), an operation instruction is issued to the loop closing monitor 27 to close the faulty loop (step 58), and the process is terminated. On the other hand, if there is no log information that matches the acquired FC-AL failure message code 32 (step
In the step 54), the output processing to the FC-AL failure information file 22 (steps 55 to 57) and the operation instruction to the loop closing monitor (step 58) are not performed, and the processing ends.

FIG. 6 shows a processing flowchart of the loop closing monitor 27. The loop block monitor 27 searches the configuration information file 23 to obtain operation loop (failed loop) information and loop information of the alternative path (step 61), and instructs parameters to the loop block execution command (step 62).
The operation loop (failure loop) information before the closure is set and updated in the operation loop (before closure) 37 of the control information file 25 (step 63), and a loop closure execution command is input (step 64). Then, execute loop blocking (step 6
5), the operation loop (alternate path) information after the blockage is set in the operation loop (after the blockage) 38 of the control information file 25 and updated (step 66), and the hub is used to instruct the loop-connected device to forcibly bypass. An operation instruction is issued to the control instruction monitor 28 (step 67), and the process is terminated. FIG. 7 shows a processing flowchart of the hub control instruction monitor 28. The hub control instruction monitor 28 searches the control information file 25 and finds an operation loop (before blocking) 37, bypass device information 39, hub bypass status 3A, and T & D end condition (number of times /
Time) 33, the number of T & D executions 3B, and the T & D execution start time 3C are obtained (step 71), and the T & D end condition is satisfied based on the obtained T & D end condition 33 and T & D execution number 3B or T & D execution start time 3C. It is checked whether or not it has been performed (step 72). As a result, if the termination condition is not satisfied (step 7
3) Retrieve the configuration information file 23 and acquire information on the device connected to the port next to the port to which the device of the acquired bypass device information 39 is connected among the connected devices of the closed loop ( Step 74), the bypass control status is checked based on the acquired bypass device information 39 and the information of the device connected to the next port (Step 7).
Five).

If the processing has not been completed for all the devices (step 76), an interface parameter to the hub management AP 29 is specified (step 77), and the hub management AP 29 is interfaced (step 78). The port on the hub is forcibly bypassed according to the control instruction from the hub control monitor 28 (step 79), the hub management AP 29 returns the control result (step 7A), and the device that forcibly instructed the bypass device information 39 in the control information file 25 to the bypass device information 39. The information is set and updated (step 7B), and an operation instruction is issued to the T & D execution instruction monitor 2A to make the T & D execution means 28 function (step 7).
C), end the process. If the hub control has been completed for all devices (step 76), the control information file 25
The end status is set and updated in the hub bypass status 3A (step 7D), and the process ends. When the end condition is satisfied (step 73), the end information is set and updated in the failure information collection status 3D of the control information file 25 (step 7E), and the process ends. FIG. 8 shows a processing flowchart of the T & D execution instruction monitor 2A. The T & D execution instruction monitor 2A searches the configuration information file 23, acquires device information such as the HW path and the special file name of the failed device (Step 81 in FIG. 8), and acquires the control information file 25.
Then, the T & D name 34 and the index code 36 are obtained (step 82), and the parameters such as the obtained T & D name 34 are specified in the T & D execution command (step 83). Also, the control information file 25 is updated by setting the number of times of T & D execution (initial value = 0 is added when the T & D of the same name is repeatedly executed) 3B and the T & D execution start time 3C (step 84). (Step 85), the T & D execution means 2B is made to function, and the execution result is added to the obtained index code 36 and stored in the T & D execution result file 24 (Step 8).
6) Instruct the T & D execution result monitor 2C to monitor the T & D execution result (step 87), and end the process. FIG. 9 shows a processing flowchart of the T & D execution result monitoring monitor 2C. The T & D execution result monitoring monitor 2C acquires the T & D error code 35, the index code 36, and the failure information collection status 3D from the control information file 25 (Step 91 in FIG. 9), and performs syslog based on the acquired failure information collection status 3D. The monitoring monitor 26 checks the collection status of the fault information for the extracted FC-AL fault log information (step 92). As a result, if the information collection has not been completed (step 9
3), search the T & D execution result file 24 (step 94),
It is checked whether there is error information that matches the acquired T & D error code 35 (step 95).

When matching error information is detected (step 96), the error information is extracted (step 97), and the FC-AL failure information file 22 is searched and positioned using the obtained index code 36 as a key (step 98). FC-AL in association with the log information output by the syslog monitoring monitor 26
The data is output to the failure information file 22 (step 99), the T & D execution result file 24 is deleted (step 9A), and an operation instruction is issued to the hub control instruction monitor 28 to forcibly bypass the next device connected in a loop (step 9B). ), And terminate the process. On the other hand, if there is no error information that matches the acquired T & D error code 35 (step 96), the output processing to the FC-AL failure information file 22 (steps 97 to 99) is not performed, and the T & D execution result file 24 is output. Delete (step 9A)
An operation instruction is issued to the hub control instruction monitor 28 (step 9B),
The process ends. If the information collection has been completed (step 93), the failure information in the FC-AL failure information file 22 is automatically notified to the maintenance center (step 9C), and the process is terminated.

Next, another embodiment of the present invention will be described. Referring to FIG. 10, in the present embodiment, the first embodiment shown in FIG. 1 independently collects information for each node 11n, while the nodes 17n cooperate and a certain node 17n When the syslog monitor 26 detects FC-AL fault information, the syslog monitor monitor operation instructing means 2d
An operation instruction is sent to the other node 17n to the syslog monitor 26 via the network. The node 17n that has received the start instruction of the syslog monitoring monitor 26 starts the same processing as in the first embodiment, and the collected failure information of the FC-AL is transmitted to a certain node in the system via the network. Stores and manages FC-AL failure information for all nodes 17n that make up the system. Each node 17n performs the same processing as in the first embodiment independently for each node 17n.
If AL error information is detected, this will trigger the local syslog
By monitoring the file 21 and collecting the failure information of the FC-AL, the accuracy of the failure information can be improved. this is,
This is particularly useful when trouble information is difficult to collect, such as during an intermittent trouble. In addition, by centrally managing the failure information of the FC-ALs of all the nodes 17n in a certain node 17n, the maintenance staff only needs to refer to the failure information of the centrally managed file to specify the failure location. This embodiment is also excellent in that the number of steps for detecting failure information can be reduced. The processing procedure of the FC-AL fault information collection method may be programmed, recorded on a recording medium such as a semiconductor memory or a magnetic disk, read by a node, and executed.

[0014]

The first effect of the present invention is that immediately after a failure occurs in the system, the failure loop is automatically closed by the cooperation of various monitors and the management AP, and all the nodes connected to the loop are connected to the disk array. Assuming the devices to be simulated, disconnect the connection ports on the hub one by one from the loop by using the forced bypass function, and perform a series of operations to execute T & D sequentially without human intervention, and identify the fault location In order to obtain the necessary information to perform the operation, it is possible to automatically collect more detailed failure information and operation information of the system at the time of failure occurrence, and to reduce the number of T & D execution work and information collection work by maintenance personnel. It is possible to do. The second effect is that FC-AL fault information is extracted and managed in a separate file from a large amount of syslog, and T & D execution results are added to that information and managed. Can be confirmed immediately, and the number of steps for detecting failure information can be reduced. Also, the third
The effect of is to execute T & D multiple times in a preset number of times or within the time considering the case where no error is detected in one T & D execution and necessary information for pinpointing the failure cannot be collected. It is possible to reliably detect errors, increase the accuracy of fault information, and increase the possibility that fault information will be collected even in cases where it is difficult to identify a fault location such as an intermittent fault. That is. The fourth effect is that if the collected fault information is automatically reported to the maintenance center, even if there is a skill difference between the maintenance bases, the fault information sent by a highly skilled maintenance person in the maintenance center can be obtained. By analyzing the error, it is possible to specify a failure location with a high probability, and it is possible to instruct maintenance staff at the site to replace a simulated part or the like based on the analysis result.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a first embodiment of the present invention.

FIG. 2 is a diagram showing a system to which the present invention is applied.

FIG. 3 is a view showing an example of the contents of a control information file 25 in FIG. 1;

FIG. 4 is a view showing an example of the contents of an FC-AL failure information file 22 in FIG. 1;

FIG. 5 is a processing flowchart of a Syslog monitoring monitor 26 in FIG. 1;

FIG. 6 is a processing flowchart of a loop closing monitor 27 in FIG. 1;

FIG. 7 is a processing flowchart of a hub control instruction monitor 28 in FIG. 1;

FIG. 8 is a processing flowchart of a T & D execution instruction monitor 2A in FIG. 1;

FIG. 9 is a processing flowchart of a T & D execution result monitoring monitor 2C in FIG. 1;

FIG. 10 is a block diagram showing a second embodiment of the present invention.

[Explanation of symbols]

 11n, 17n (1 ≦ n) Node 12n (1 ≦ n) FC cable 13n (1 ≦ n) Hub 14n (1 ≦ n) Disk array device 15 FC-AL cable (operation) 16 FC-AL cable (standby) 21 syslog file 22 FC-AL fault information file 23 configuration information file 24 T & D execution result file 25 control information file 26 syslog monitoring monitor 27 loop closing monitor 28 hub control instruction monitor 29 hub management AP 2A T & D execution instruction monitor 2B T & D execution means 2C T & D Execution result monitoring monitor 2D syslog monitoring monitor operation instruction means

Claims (18)

[Claims] 1. A failure information collecting apparatus in a system in which a plurality of nodes and a plurality of disk array devices are connected via a hub through a fiber channel arbitrated loop (FC-AL), wherein each of the nodes comprises: A syslog file for managing log information collected when a failure occurs in the system or device, and a log file for managing FC-AL-related log information and T & D execution results
An FC-AL failure information file, a T & D execution result file for managing T & D execution results, a syslog monitoring monitor for monitoring the output contents of the syslog file, and log information of FC-AL failures by the monitoring A loop closing monitor for closing a failed loop and switching to an alternative loop, a hub management application having a function of forcibly bypassing the hub on a port basis, and after switching the loop, using the hub management application to perform the fault. A hub control instruction monitor that forcibly bypasses a connection port of one of the nodes or disk array devices connected to the loop from the hub, and a T & D execution instruction monitor that issues a T & D execution instruction according to an instruction from the hub control instruction monitor. Execute T & D and output the result to the T & D execution result file T for outputting the row unit, to check the execution result of T & D to the FC-AL fault information file any error information
An FC-AL failure information collection device, comprising: a & D execution result monitoring monitor, wherein the above series of processing is repeated for all the nodes and the disk array devices connected to the failure loop. 2. The system according to claim 1, further comprising a means for instructing, when the syslog monitoring monitor detects FC-AL failure information, an activation instruction to the syslog monitoring monitor of another node via a network. 2. The FC-AL failure information collection device according to claim 1, wherein: 3. The system according to claim 1, wherein the system log monitor monitors the system log file at predetermined time intervals and outputs only log information on FC-AL failures to the FC-AL failure information file. FC according to claim 1 or claim 2.
-AL failure information collection device. 4. The FC-AL fault information collection device according to claim 1, wherein the series of processes is continuously performed a preset number of times or for a predetermined time. 5. The FC-AL according to claim 1, wherein the log information and the T & D error information collected in the series of processes are managed in pairs.
Failure information collection device. 6. The T & D execution result monitoring monitor automatically notifies the maintenance center of the failure information collected by the series of processes.
The FC-AL failure information collection device according to any of the above. 7. A failure information collecting method in a system in which a plurality of nodes and a plurality of disk array devices are connected via a hub through a fiber channel arbitrated loop (FC-AL). A procedure for monitoring the output contents of a syslog file collected when a failure occurs, a procedure for closing a failure loop and switching to an alternative loop when log information of an FC-AL failure exists by the monitoring; and After switching, forcibly bypassing one connection port of a node or a disk array device connected to the failed loop from the hub using a hub management application having a function of forcibly bypassing the hub on a port basis. , T & D execution procedure, T & D execution result output to file, T & D execution If there is an error information to check the results FC-AL
Outputting a failure information file to the failure information file, and repeating the above series of processes for all the nodes and disk array devices connected to the failure loop. 8. A method has been added in which, when failure information of FC-AL is detected by monitoring the output contents of the syslog file, an instruction to start the monitoring of the output contents of the syslog file is issued to another node via a network. The method for collecting FC-AL failure information according to claim 7, wherein: 9. The FC according to claim 7, wherein the system log file is monitored at predetermined time intervals, and only the log information of the FC-AL failure is output to the FC-AL failure information file. -AL Failure information collection method. 10. The method according to claim 7, wherein the series of processing is continued for a preset number of times or time.
9. The method for collecting FC-AL failure information according to any one of claims 9 to 9. 11. The FC-AL failure information collection method according to claim 7, wherein the log information and the T & D error information collected in the series of processing are managed in pairs. . 12. The FC-AL fault information collection method according to claim 7, wherein the fault information collected by the series of processing is automatically notified to a maintenance center. 13. A failure in a system or a device in a failure information collecting method in a system in which a plurality of nodes and a plurality of disk array devices are connected via a hub through a fiber channel arbitrated loop (FC-AL). A procedure for monitoring the output contents of a syslog file collected when an error occurs, a procedure for closing a failure loop and switching to an alternative loop when log information of an FC-AL failure exists by the monitoring; After switching, forcibly bypassing one connection port of the node or the disk array device connected to the failed loop from the hub using a hub management application having a function of forcibly bypassing the hub on a port basis, T & D execution procedure, T & D execution result output to file, T & D execution result Check the result and if there is error information, FC-AL
And outputting the information to a failure information file. The recording medium stores a program for repeatedly executing the above series of processing for all the nodes and the disk array device connected to the failure loop. 14. When the failure information of the FC-AL is detected by monitoring the output contents of the syslog file, an instruction to monitor the output contents of the syslog file is issued to another node via a network. Claim 12
The recording medium according to the above. 15. The system monitors the syslog file at predetermined time intervals and stores only FC-AL failure log information in the FC-AL.
2. The output to a failure information file.
15. The recording medium according to 3 or 14. 16. The recording medium according to claim 13, wherein the series of processing is continuously performed a preset number of times or for a predetermined time. 17. The recording medium according to claim 13, wherein said log information and T & D error information collected in said series of processing are managed in pairs. 18. The recording medium according to claim 13, wherein fault information collected by said series of processing is automatically notified to a maintenance center.