JPH0721059A - Erroneous log information managing method - Google Patents

Abstract

PURPOSE:To effectively use erroneous log information and to apply uniform and efficient countermeasure and preventive maintenance for failure by regulating the format/content of erroneous log information based on object oriented consideration. CONSTITUTION:In a client server system consisting of plural hierarchies, the failure detail information of hardware failure sampled at every unit in a peripheral device and the erroneous log information representing error statistical information in each hierarchy are stored in the specific areas of external memory devices 25, 29. After recorded information is read out periodically and it is sent to a high-order server sequentially and the information is collected comprehensively, a failure occurrence process list and an abnormal value list when the value exceeds the threshold value of the error statistical information are generated, and they are outputted to the output devices 26, 2A of the high- order server. A unification server 27, after transferring collected erroneous log information to a terminal 2B at a maintenance base, edits a list for maintenance, and sends it to the output device 2D of the maintenance terminal 2B, then, it is used by each peripheral device as feedback data.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention manages error log information indicating detailed error information and error statistical information collected for each unit in a peripheral device when a hardware error occurs in the computer and the peripheral device. In addition, the present invention relates to an error log information management method that outputs an edit list for troubleshooting and preventive maintenance.

[0002]

2. Description of the Related Art Conventionally, RAS, that is, reliability
(Reliability), Availability and Serviceability
Regarding (maintenance), a method was considered for a single product, such as collecting data for a certain product at fixed intervals and storing it in memory, but a comprehensive RAS for the product
The idea of as was not established yet. That is, in the case of a computer information processing system, there is no one that has considered a method of managing error log information from the viewpoint of system RAS including the operation of products to preventive maintenance, and the contents are not clear. It was In addition, there is no concept of effective use by returning error log information as feedback data to the vendors and maintenance bases in order to improve the operating quality of hardware products. On the other hand, a consistent error log information management method for uniform and efficient failure countermeasures and preventive maintenance has not been established. Incidentally, as a conventional method for collecting various data generated in the apparatus and writing the same in an external storage device at regular intervals, there is a "data collection recording device" described in Japanese Utility Model Laid-Open No. 4-111649. is there.

[0003]

Conventionally, an error log information management system having a function of collecting, collecting, editing, or transferring error log information capable of performing centralized / centralized management of the entire system has been known. , Not yet established. In this way, the error from the viewpoint of system RAS
Since the log information management method was not established, the data was sent to the vendor and the maintenance department at the maintenance base.
However, it was not possible to make effective use to improve the operation quality of hardware products by implementing feedback, or to implement uniform and efficient failure countermeasures and preventive maintenance. An object of the present invention is to solve the above-mentioned conventional problems and to perform an error management such that the system as a whole can be managed centrally / centrally.
An object of the present invention is to provide an error log information management method having each function of collecting, collecting, editing, or transferring log information.

[0004]

In order to achieve the above object, the error log information management method of the present invention comprises an external storage device (22, 25, 29, 2C) and an input / output device (2).
1, 24, 26, 28, 2A, 2D) and the like connected to the client (20), a plurality of sales office servers (23) for managing the clients (20), and sales office server.
In a client server system having a plurality of layers of an integrated server (27) for centrally managing the server (23) and a maintenance base (2B) connected to the integrated server (27), peripheral devices of each layer Fault detail information (51-5N) of hardware faults collected for each internal unit and error
The error log information (61 to 6M) indicating the statistical information is recorded in a specific area of the connected external storage device (22, 25, 29), and the recorded information is periodically read out to obtain a higher rank server. Information is collected in a high-order server all at once, and then edited to make it easier to see, and the failure occurrence transition list (see FIG. 10) and error information in the failure detailed information are displayed.
An abnormal value list (see FIG. 11) when the threshold value of the statistical information is exceeded is output to the output device (26, 2A) of the upper server, and the error log collected in the integrated server (27). After transferring the information to the maintenance base terminal (2B), the edited maintenance list is output to the maintenance terminal (2B) output device (2D).
It is characterized in that the maintenance list is used as feedback data for each peripheral device by outputting to the peripheral device.

[0005]

In the present invention, the format / content of the error log information is defined based on the object-oriented concept, so that the system as a whole can be centrally managed. That is, in order to maintain consistency, maintainability, and expandability of the item expression, which is a component of error log information indicating detailed error information and error statistical information collected for each unit in a peripheral device when a hardware error occurs. In addition, it is defined as primitive attribute information having various characteristics (that is, completely different properties), and defines the format / content of error log information that does not depend on software or system. And
In the event of a hardware failure, error log information indicating failure detailed information and error statistical information collected for each unit in the peripheral device is written to a specific area of the external storage device, and these are read periodically, Collected sequentially in a higher system. In the host system and the maintenance base, after collectively collecting, it is edited for easy viewing, and the failure occurrence transition list of the failure detailed information and the abnormal value list when the threshold of the error statistical information is exceeded are output from the output device. In addition, the error log information collected from the highest level system, for example, the integrated server or the sales point server, is classified for each maintenance base and transferred to the maintenance terminal provided in the maintenance base for maintenance. Output the edited maintenance list from the terminal output device.

[0006]

Embodiments of the present invention will now be described in detail with reference to the drawings. 1 and 2 are overall views showing a hierarchical system to which the present invention is applied. Here, a client server system including a client (customer), a sales office server (supplier) above it, and an integrated server above it is shown. In FIG. 2, reference numeral 20 denotes a client processing apparatus, which is an apparatus for processing various data, 21 denotes a display connected to the client processing apparatus 20,
A peripheral device composed of a plurality of units such as a hard disk and a printer. Reference numeral 22 denotes detailed error information and an error collected for each unit in the peripheral device when a hardware error occurs.
The external storage device records error log information indicating statistical information. Further, in FIG. 1, reference numeral 23 is a processing point server processing apparatus for processing data collected from clients, and 24 is an input for inputting various commands such as a keyboard display. When a hardware failure occurs at a sales office server, the device 25 is detailed failure information collected for each unit in the peripheral device connected to the server,
And an external storage device for recording the error log information indicating the error statistical information and the error log information collected from the client 20 located under the server, and 26 is various information in the sales office system. Is a printer that edits and outputs a list.

Further, the uppermost 27 in FIG. 1 is an integrated server processing device, which is an integrated server processing device for centralized / centralized management of all business office systems. A device for processing the data collected from the server, 28 is a keyboard
An input device for inputting various commands such as a hard disk display, and 25 is a detailed information of a failure collected for each unit in the peripheral device connected to the server when a hardware failure occurs in the sales office server. And an error indicating statistical information
Log information and all sales office servers under the integrated server 2
3 is an external storage device for recording the error log information collected from 3, 2A is a printer for editing various information of the entire system, and is a list output, and 2B is a processing device of a maintenance terminal provided at a maintenance base. Therefore, the integrated server processing device 27 is connected by a line. Also, 2C
Is an external recording device for recording while periodically receiving error log information centrally managed / centralized by the integrated server, and 2D is a printer for editing various information at the maintenance base and outputting the list. .

FIG. 3 is an explanatory diagram of each function of collecting, collecting, editing, or transferring error log information according to the present invention. In FIG. 3, 30 is a client processing device, 31
Is a sales office server processing device, 32 is an integrated server processing device,
33 is a maintenance terminal, 34, 35 and 36 are all error log information files, 37 and 39 are edit list outputs, and 38 is a received file. When the client processing device 30 detects a hardware failure, the client processing device 30 collects error log information indicating detailed error information and error statistical information in an error log information file 34 in an external storage device connected to the client processing device 30. To do. In addition, the server processing device 3
1 collects the error log information collected in the lower level client 30 and writes it in the error log information file 35 in the external storage device connected to the sales office server processing device 31. Further, when the sales office server processing device 31 detects a hardware failure, the error log information is stored in the external storage device connected to the sales office server 31.
Collect in the log information file 35.

Next, the integrated server processing device 32 collects the error log information collected in the subordinate office server processing device 31, and the external server connected to the integrated server processing device 32. Write to the error log information file 36 in the external storage device in the storage device. When the integrated server processing device 32 detects a hardware failure in the processing device, the integrated server processing device 32 returns an error.
The log information is collected in the error log information file 36 in the external storage device connected to the integrated server processing device 32. The integrated server processing device 32 edits the collected / collected error log information and outputs it as a list to the output device 37. On the other hand, the maintenance terminal 33 installed in the maintenance base edits the error log information of the maintenance base periodically transferred from the integrated server processing unit 32 via the line and outputs the list to the output unit 39. To do. FIG. 4 is a diagram showing the format structure of the error log information file recorded in the external storage device in FIG. In FIG. 4, 40 is an error log information file, 41 is a detailed error information management table recorded in a specific area in the error log information file 40, 4
Reference numeral 2 is an error statistical information management table. The formats of the fault detailed information management table 41 and the error statistical information management table 42 shown in FIG. 4 are shown below in FIGS. 5 and 6.

In FIG. 5, reference numeral 50 is a failure detail information management table of a collection of failure detail items (there are N pieces) of a unit in a peripheral apparatus at the time of a hardware failure, and 51 is a failure in the unit in the peripheral apparatus. It is the detailed item 1, and similarly 52 to 5N are the fault detailed items 2 to 2, respectively.
N. The fault detail item 1 includes an attribute information table 510 for the fault detail item 51. 511, 512,
... 51M is M primitive attribute information (A of the attribute information table 510 in the fault detail item 51).
ttribute). In the same way, detail item 5
There are M pieces of primitive attribute information for 2, ..., 5N, respectively. In FIG. 6, reference numeral 60 is an error statistical information management table of an aggregate of error statistical items (there are N pieces) for the unit in the peripheral device at the time of hardware failure, and 61 is an error for the unit in the peripheral device. -Statistics item 1 and similarly 62 to 6N are error statistics items 2 to N, respectively. Error statistics item 1
There is an attribute information table 610 in the error statistical item 61. 611, 612, ..., 61M are M pieces of primitive attribute information (Attribute) forming the attribute information table 610 in the error statistical item 61. Similarly, for the error statistical items 62, ... 6N,
There are M pieces of primitive attribute information. In this way, if the attribute information is unified, it is sufficient to edit according to the attribute information, which facilitates editing.

FIG. 7 is a diagram showing a format of the primitive attribute information of FIGS. 5 and 6. In FIG. 7, reference numeral 70 denotes an attribute identifier for each attribute information, which is given a unique identification number. Reference numeral 71 is a data length for the data content 72 of the attribute information. Further, 72 is a data content indicated by the attribute identifier 70, that is, a possible value of the attribute information of only the data length 71. The method is based on an object-oriented approach for generalization and standardization in which each attribute information has a modular structure common specification and flexibility, expandability, and maintainability are considered. Figure 8
It is a figure which shows the format of the failure detailed item at the time of mapping the attribute information table of FIG. Here, it is composed of M = 7 pieces of primitive attribute information. In FIG. 8, 80 is an item type indicating detailed items of failure, 81 is an installation location where the peripheral device is installed, 82 is a device name of the peripheral device, 83 is a date when a failure occurs in a unit in the peripheral device, and 84 is a peripheral device. Name of the fault in the device unit, 8
Reference numeral 5 is a fault code, and 86 is fault detail data indicating information of various registers and sensors when a fault occurs. The fault code 85 is a fault occurrence site code indicating which unit has a fault, and a fault phenomenon code indicating what kind of phenomenon and what cause. It is composed of the classification system of the fault cause code that is shown, which shows the resolution that can isolate the fault, and the total fault occurrence for the fault code when the fault occurs in a certain selected period. It is also a key item for outputting a failure occurrence transition list including items such as the number of cases and the failure occurrence date.

FIG. 9 is a diagram showing the format of error statistical items when the attribute information table in FIG. 6 is mapped. Here, it is composed of M = 9 pieces of primitive attribute information. In FIG. 9, 90 is an item type indicating an error statistical item, 91 is a device installation location in which the peripheral device is installed, 92 is a device name of the peripheral device, 93 is a unit name in the peripheral device, and 94 is in the peripheral device. The name of the error counter of the unit, 95 is an error counter, 96 is the number of times of activation when an input / output activation command is issued to the unit in the peripheral device, 97 is a threshold of the number of error occurrences, 98 is a threshold of the error occurrence rate Is shown. In addition, the error occurrence threshold 97
Is a threshold value which is determined when collecting in the upper system only the error statistical item in which the value of the error counter 95 exceeds the error occurrence number threshold value 97 by the collecting command from the upper system. Further, the error occurrence rate threshold 98 is set only for the error statistical items for which the value obtained by dividing the value of the error counter 95 by the number of activations 96 exceeds the error occurrence rate threshold 98 by the collection command from the upper system. It is a threshold value that is judged when collecting data in the host system. That is, these two items 97 and 98 are necessary items for minimizing the information amount of error statistical items collected in the host system and shortening the collection time. The values of the error occurrence count threshold value 97 and the error occurrence rate threshold value 98 are the same as those of the integrated service.
Initialization or updating of values is performed by inputting a command instruction from the input device 28 of the bar processing device 27 or the input device 24 of the sales office server processing device 23.

FIG. 10 is a diagram showing an example of the output format of the failure occurrence transition list according to the present invention. The detailed fault information management table of FIG. 5 is edited and used as a fault occurrence transition list to output devices 26, 2A in the sales office server 23 or integrated server 27, or an output device 2D in the maintenance terminal 28. When output to, the list format is as shown in FIG. In the items of the list, maintenance site name, equipment installation location, failure name, failure code, number of occurrences, failure detail data, failure occurrence date, etc. are output. The name and each value are output. FIG. 11 shows
It is a figure which shows the output format example of an error statistical item in this invention. The error statistical information management table shown in FIG. 6 is edited, and this is used as an abnormal value list in the error statistical information to output server 26 connected to sales office server 23 or integrated server 27 and maintenance terminal 28. , 2A, 2D, the list format is as shown in FIG. As the list items, maintenance site name, device installation location, device name, unit name, error counter name, error counter value, number of startups, error occurrence rate, etc. are output and correspond to each of these items. The specific name and each value are output.

FIGS. 12 to 17 are operation flowcharts of the error log information management method showing an embodiment of the present invention. FIG. 12 shows a client processing device 20, a branch server processing device 23, and an integrated server processing device 27.
A flow chart showing program execution in each processing unit 20, 23, 27 when error log information showing detailed error information and error statistical information is collected in an external storage device such as a hard disk is shown. There is. External storage devices 22, 25, 2 are provided in each of the processing devices 20, 23, 27 and the maintenance base 2B.
9 and 2C are connected and an error log information file is stored. In FIG. 12, first, the error statistical information management table 4 in the error log information file to be collected in the external storage device 22, 25, 29, 2C such as the hard disk.
An initial setting process is performed for 2 (step 100). As the initial setting method, the item type 90, the device installation place 91, the device name 92, the unit name 93, the error counter name 94, and the error counter value 9 in the error statistics item of FIG.
5, the number of activations 96, the error occurrence number threshold 97, and the error occurrence rate threshold 98 are initialized according to the information configured by the corresponding peripheral device and unit. Among the above items, the error occurrence count threshold value 97 and the error occurrence rate threshold value 98 can be initialized or changed by a command from the host system.

Next, it is judged whether or not the executions in the client processing device 20, the branch server processing device 23, and the integrated server processing device 27 are in the normal business process (step 101). If normal business processing is in progress, each time an I / O start-up command is issued to the peripheral unit,
The number of times of activation 96 in the error statistical item corresponding to the unit in the peripheral device of the error statistical information management table 60 is updated (step 102). Next, when a failure is detected in the peripheral device unit (step 103), it is determined whether or not the failure is a recoverable failure (step 104). If it is a recoverable failure, failure recovery processing is executed (step 105). Next, the value of the error counter 95 in the corresponding error statistical item of the error statistical information management table 42 of FIG. 4 collected in the external storage device is updated by 1 (step 106). Next, during failure recovery processing, it is determined whether failure recovery has succeeded (step 107). If the failure recovery is successful, business continuation processing is performed (step 109). On the other hand, when the failure recovery is unsuccessful, it is determined whether or not the number of retries of the failure recovery processing has exceeded the specified number (step 108). If the number of retries of the failure recovery processing is not over, the process returns to step 105 and the failure recovery processing is executed again.

When the number of retries of the failure recovery processing is over the specified number of times (step 108), the relevant peripheral unit is regarded as an unrecoverable failure and the failure detail items shown in FIG. After setting the item type 80, the device installation location 81, the device name 82, the fault occurrence date 83, the fault name 84, the fault code 85, and the fault detailed data 86 in the external storage device, refer to FIG. The following items are written in the additional mode after the fault detail item 5N of the fault detailed information management table 50 shown. That is, the failure detail items are set and collected in the external storage device (step 110), and then it is determined whether or not degenerate operation is possible (step 11).
1) If degenerate operation is possible, a process for switching to degenerate operation is performed (step 112). Then, the process returns to the first processing step 101 (A). If degenerate operation is not possible, system down processing is performed (step 11).
3). In step 104, if the peripheral device unit is an unrecoverable failure, the failure detail item is immediately collected (step 110).

FIG. 13 shows fault detail information and error statistical information collected by the client processing device 20 after the client processing device 20 receives the collection command from the sales office server processing device 23. The execution processing flow of the program in the processing device 20 when the error log information is transmitted to the sales office server 23 is shown. First, when the corresponding client processing device 20 receives a collection command from the sales office server processing device 23 (step 120), the processing device 20 extracts the failure detailed information management table 50 shown in FIG. All detail items of failure are transmitted to the sales office server processing device 23 (step 1).
21). After all the failure detail items have been completed, the failure detail information management table 50 is cleared (step 122).
Next, in the error statistical information management table 60 shown in FIG. 6 collected in the external storage device 22, the error counter 9
Only the error statistical item whose value of 5 exceeds the error occurrence threshold 97 or the error statistical item whose number of activations 96 divided by the value of the error counter 95 exceeds the error occurrence threshold 98 It is transmitted to the sales office server processing device 23 (step 123). After completing all the transmissions, the error statistical information management table 60 is cleared (step 124).

FIG. 14 shows detailed fault information collected by the sales office server processing device 23 after the sales office server processing device 23 receives the collection command from the integrated server processing device 27. The error log information indicating the error statistical information or the failure detailed information collected from the client processing device 20 below the branch server processing device 23 and the error log information indicating the error statistical information are integrated into the server. A program execution operation flow in the processing device 23 when transmitting to the processing device 27 is shown. First, the corresponding sales office server processing device 23 receives a collection command from the integrated server processing device 27 (step 130). Next, the failure detailed information management table 50 collected or collected by the sales office server processing device 23 is transferred to the integrated server processing device 27.
(Step 131). After all the transmissions have been completed, the fault detailed information management table 50 is cleared (step 132). Further, in the error statistical information management table 60 collected or collected in the external storage device, the error statistical item in which the value of the error counter 95 exceeds the error occurrence number threshold value 97, or the number of activations 96 Is divided by the value of the error counter 95 and exceeds the error occurrence rate threshold 98, only the error statistical items are transmitted to the integrated server processing device 27 (step 133). After all transmission is completed, the error statistical information management table 90 is cleared (step 134).

FIG. 15 shows a program in the processing device 23 when receiving the error log information collected by all the client processing devices 20 in the lower order according to the collection command from the sales office server processing device 23. The execution process flow is shown. First, when a collection command is input from the input device 24 of the branch server processing device 23, the processing device 23 causes the failure detailed information management table collected in all the client processing devices 20 below to follow the command. An instruction to collect the bull 50 and the error statistical information management table 60 is transmitted (step 140). Fault detail information management tables are sent from all the client processing devices 20 in the lower order.
The cable 50 and the error statistical information management table 60 are received and written in the external storage device 25 (step 141). When all of the above-mentioned tables 50 and 60 have been received, the branch server processing device 23 next sets the attributes set in the fault detailed information management table 50 and the error statistical information management table 60. Editing according to the information,
The failure occurrence transition list shown in FIG. 11 and the abnormal value list in the error statistical information shown in FIG. 11 are created (step 14
2). Next, these lists are output to the output device 26 (step 143).

In FIG. 16, according to the collection command from the integrated server processing unit 27, all the subordinate sales office servers are displayed.
The program execution processing flow of the processing device 27 when the error log information collected or collected by the processing device 23 is received is shown. First, when a collecting command is input from the input device 28 of the integrated server processing device 27,
The processing device 27 sends a collection instruction of the fault detailed information management table 50 and the error statistical information management table 60 collected or collected to all the branch office server processing devices 23 (step). 150). Next, the processing device 27
Is the fault detailed information management table 50 and the error statistical information management table from all the subordinate server server processing devices 23.
Bull 60 is received and these are written in the external storage device 29 (step 151). When all the reception is completed, it is edited according to the attribute information set in the fault detailed information management table 50 and the error statistical information management table 60, and the fault occurrence transition list shown in FIG. 10 and the error shown in FIG. An abnormal value list in the statistical information is created (step 152). These lists are output to the output device 2A (step 153). Next, the processing device 27 causes the fault detailed information management table 50 written in the external storage device 29.
Also, the error statistical information management table 60 is read out periodically, for example, on a daily, weekly or monthly basis, classified by maintenance base, and transferred to the maintenance terminal (step 154).

FIG. 17 shows the processing at the maintenance base when the detailed error information management table 50 and the statistical information management table 60 transferred from the integrated server processing device 27 are edited and output as a list. A program execution process flow in the device 2B is shown. The processing unit 2B receives the fault detailed information management table 50 and the error statistical information management table 60 which are periodically (daily, weekly, monthly) transferred from the integrated server processing unit 27. , These are external storage devices 2C
(Step 160). When all the reception is completed, it is edited according to the attribute information set in the fault detailed information management table 50 and the error statistical information management table 60, and the fault occurrence transition list shown in FIG. 10 and the error shown in FIG. An abnormal value list in the statistical information is created (step 161). The list is output to the output device 2D (step 162). After a certain period of time has passed, the detailed fault information management table 5 written in the external storage device 2C is displayed.
0 and the error statistical information management table 60 are cleared (step 163).

[0022]

As described above, according to the present invention,
Since it is possible to quantitatively manage error log information generated in various peripheral devices of a distributed system having a hierarchical relationship such as a client server system, at the same time effectively utilizing this information as feedback data, It is possible to carry out uniform and efficient fault countermeasures and preventive maintenance such as daily inspections, periodic inspections, and prior detection of abnormalities.

[Brief description of drawings]

FIG. 1 is a diagram showing a part of a configuration of a client server system showing an embodiment of the present invention.

FIG. 2 is a diagram showing another part of the configuration of the client server system.

FIG. 3 is an explanatory diagram showing each operation of collecting / collecting / editing / transferring error log information in FIGS. 1 and 2;

FIG. 4 is a main part format diagram of an error log information file recorded in the external storage device in FIGS. 1, 2 and 3.

5 is a format diagram of a fault detailed information management table and an attribute information table in FIG.

6 is a format diagram of an error statistical information management table and an attribute information table in FIG.

FIG. 7 is a diagram showing a format of primitive attribute information in FIGS. 5 and 6;

8 is a format diagram of fault detail items when the attribute information table in FIG. 5 is specifically mapped.

9 is a format diagram of error statistical items when the attribute information table in FIG. 6 is specifically mapped.

10 is an output format diagram of the failure occurrence transition list in FIG.

11 is an output format diagram of an abnormal value list of error statistical information in FIG.

FIG. 12 is a program execution processing flowchart of each processing apparatus in FIGS. 1 and 2;

FIG. 13 is a program execution processing flowchart of the client processing device in the case of transmitting the fault detail information and the error log information collected by the client in FIGS. 1 and 2 to the sales office server.

FIG. 14 is a program execution of the sales office server processing device in the case of transmitting the fault detail information and error log information collected or collected by the sales office server to the integrated server in FIGS. It is a processing flow chart.

FIG. 15 is a program execution processing flowchart of the sales office server processing apparatus when receiving the error log information collected by the client in FIGS. 1 and 2;

16 is a program execution processing flowchart of the integrated server processing device when receiving the error log information collected or collected by the sales office server in FIG. 1 and FIG.

FIG. 17 is a diagram showing a processing unit of a maintenance base in the case of editing the failure detailed information management table and error statistical information management table transferred from the integrated server and outputting the list in FIGS. It is a program execution processing flowchart.

[Explanation of symbols]

 20, 30 Client processing device 23, 31 Sales office server processing device 27, 32 Integrated server processing device 2B, 33 Maintenance terminal processing device 21 Peripheral device 22, 25, 29, 2C External storage device 26, 2A, 2D Output device 24,28 Input device 40 Error log information file 41,50 Fault detailed information management table 42,60 Error statistical information management table 51-5N Fault detailed item 91-9N Error statistical item 510 Attribute information Table 511-51M Attribute information 610-61M Attribute information 70 Attribute identifier 71 Data length 72 Attribute information possible values 80 Item type indicating detailed fault items 81, 91 Device installation location 82 Device name 83 Fault occurrence date 84, 92 Fault name 85 Fault code 86 Fault detailed data 90 Error item type indicating statistical items 93 Unit Name 94 Error counter name 95 Error counter value 96 Number of startups 97 Threshold number of error occurrences 98 Threshold value of error occurrence rate

Claims (1)

[Claims] 1. A client to which peripheral devices such as an external storage device and an input / output device are respectively connected, a plurality of business office servers that manage the clients, and an integrated server that centrally manages the business office servers, In addition, in the client server system including a plurality of layers of maintenance bases connected to the integrated server, detailed error information and error statistical information of the hardware error collected for each unit in the peripheral device of each layer are displayed. The error log information shown is recorded in a specific area of the connected external storage device, and the recorded information is read out periodically and sequentially transmitted to the upper server, so that the information can be collectively sent to the upper server. After collecting the data, edit it to make it easier to see, and output the failure occurrence transition list of the detailed error information and the abnormal value list when the threshold of the error statistical information is exceeded to the output device of the upper server. At the same time, the error log information collected by the integrated server is transferred to the terminal at the maintenance base, and the edited maintenance list is output to the output device of the maintenance terminal to save the maintenance list. An error log information management method characterized in that it is used as feedback data for each peripheral device.