JPH09219747A - Fault information analysis system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accurately clear up the cause of the faulty diagnosis of result in a short time by collecting and analyzing the types of tests carried out and the device failure information when a diagnostic route retrieval means detects a failure of the component device to be diagnosed. SOLUTION: When each diagnostic means 120 diagnoses every its corresponding component device 110 and detects a failure of the device 110, a diagnostic route detection means 101 collects and analyzes the types of tests carried out when the failure is detected and the device failure information indicating the diagnostic result via the means 120. Then the means 101 retrieves the diagnostic route showing every device 110 concerned in the diagnosis among those prepared diagnostic routes. A suspected device priority retrieval means 102 decides the suspicion priority of devices 110 included in the diagnostic route detected by the means 101. A suspected device diagnosis start means 103 successively starts the means 120 corresponding to the devices 110, based on the suspicion priority decided by the means 102.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a failure information analysis method for an exchange, and more particularly to a failure information analysis method for an exchange which is composed of a plurality of constituent devices and which has diagnostic means for diagnosing various constituent devices.

[0002]

2. Description of the Related Art FIG. 6 is a diagram illustrating a conventional exchange. The exchange (10) shown in FIG. 6 has a main memory (M
M) (11), central controller (CC) (12), auxiliary storage (FM) (13), inter-processor communication controller (I)
PC) (14) Further maintenance terminal device (CNS) (15)
And a plurality of constituent devices (1).

The call processing unit (2) controls each of the above-mentioned components (1) and executes various call processes required by the exchange (10). Corresponding to the above-mentioned various constituent devices (1), various diagnostic programs (4) for diagnosing the normality of the respective corresponding types of constituent devices (1) are prepared, and the diagnostic execution control unit (3) During normal times of call processing by the call processing unit (2), the corresponding diagnostic programs (4) are activated to diagnose the normality of each of the above-mentioned constituent devices (1).

Each of the activated diagnostic programs (4) diagnoses the designated constituent device (1) and notifies the diagnostic execution control section (3) of the execution result. If the diagnosis result is defective, the diagnostic program (4) includes the component device (1) that is the target of the diagnosis, and device defect information (NG) that indicates the diagnostic content such as the type of the test that detected the defect. , And notifies the diagnosis execution control unit (3).

The diagnostic execution control unit (3), based on the device failure information (NG) notified from the diagnostic program (4),
The diagnostic dictionary for searching the suspected range of the exchange (10) is built in, and the portion related to the device failure information (NG) notified from the diagnostic program (4) is the diagnostic dictionary information (DXY).
The maintenance terminal device (CNS) together with the device failure information (NG) notified by the diagnostic program (4).
(15) and so on.

[0006] The maintenance person uses the device failure information (NG) output from the diagnostic execution control unit (3) and the diagnostic dictionary information (DX).
Y) is analyzed, and the suspected device is addressed to one and the diagnosis is repeated to find the cause of the failure.

[0007]

As is apparent from the above description, in the conventional exchange (10), when the diagnostic program (4) detects a defect of the constituent device (1), the diagnostic execution control unit ( 3) device defect information (NG) indicating the diagnosis content notified from the diagnostic program (4), and diagnostic dictionary information (DXY) related to the device defect information (NG) extracted from the prepared diagnostic dictionary. After that, the maintenance person analyzes the output device failure information (NG) and the diagnostic dictionary information (DXY), repeats the diagnosis for one suspected device, and investigates the cause of the failure.

Therefore, the knowledge and experience of the maintenance person greatly influences the investigation of the cause of the failure. For example, although the route of the apparatus through which the command is executed is different depending on the executed command, the maintenance person is informed of the other apparatus. When the device failure information (NG) is generated due to the device failure other than the device to be diagnosed, the instruction execution path is not notified, so it is easy to overlook and it is difficult to accurately grasp the phenomenon. Therefore, it has always been difficult to quickly obtain accurate investigation results.

An object of the present invention is to make it possible to accurately determine the cause of a result defect diagnosis in a short time.

[0010]

FIG. 1 is a diagram illustrating the principle of the present invention. In FIG. 1, reference numeral 100 denotes an exchange which is a target of the present invention, 110 denotes a constituent device of the exchange (100), and 120 denotes a diagnostic means for executing diagnosis of various constituent devices (110).

101 is an exchange (100) according to the present invention.
It is a diagnostic route search means provided in the. 102 is a suspected device priority order search means provided in the exchange (100) according to the present invention.

103 is an exchange (100) according to the present invention.
It is a suspicious device diagnosis starting means provided in the. The diagnostic route search means (101) detects a defect when the diagnostic means (120) performs a diagnosis of the corresponding constituent device (110) and detects a defect in the constituent device (110) to be diagnosed. A plurality of diagnostics that have in advance a diagnostic route indicating each constituent device (110) involved in the diagnosis by collecting and analyzing the test type executed at a time and the device failure information indicating the diagnostic result from the diagnostic means (120). Search from the route.

The suspected device priority search means (102)
The suspicious priority of each constituent device (110) included in the diagnostic route detected by the diagnostic route search means (101) is determined.
The suspected device diagnosis activation means (103) is based on the suspected priority order determined by the suspected device priority order search means (102).
Diagnostic means (12) corresponding to each suspected constituent device (110)
0) are sequentially activated.

It is considered that the diagnostic route search means (101) displays the detected diagnostic route to the tester.
Further, it is considered that the suspected device priority order search means (102) displays the determined suspected priority order of each constituent device (110) to the tester.

Therefore, the suspected constituent devices related to the diagnosis of the result defect are automatically diagnosed sequentially from the device having the highest suspected priority order, so that the precise cause is not affected by the knowledge and experience of the maintenance person. The investigation can be executed in a short time, and the reliability and maintainability of the exchange can be greatly improved.

[0016]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. 2 is a diagram showing an exchange according to an embodiment of the present invention, FIG. 3 is a diagram showing an example of device failure information which is a target of FIG. 2, and FIG. 4 is a diagram showing an example of a diagnostic route diagram in FIG. FIG. 5 is a diagram illustrating the priority suspicion information in FIG. 2. The same reference numerals indicate the same objects throughout the drawings.

The exchange (10) shown in FIG. 2 comprises the respective constituent devices (1) of the conventional exchange (10) shown in FIG. 6, a call processing section (2), a diagnostic execution control section (3) and In addition to having various diagnostic programs (4), a search processing information table (5) containing a diagnostic route diagram (51), priority suspect information (52), and startup diagnostic program information (53) is provided. A diagnostic route search unit (31) and a priority suspect information search unit (3) are included in the execution control unit (3).
2) and a suspicious device diagnosis starting unit (33) are provided.

The exchange (10) is replaced by the exchange shown in FIG.
Machine (100) and main memory (MM) (1
1), central controller (CC) (12), auxiliary storage device
(FM) (13), inter-processor communication controller (IPC)
(14), maintenance terminal device (CNS) (15), etc.
The constituent device (1) corresponds to the constituent device (110) in FIG.
Corresponding, and execution control is performed by the diagnostic execution control unit (3).
MM diagnostic program (4 _MM), CC diagnostic program
(4_CC), FM diagnostic program (4_FM), IPC diagnostic program
Program (4_IPC), CNS diagnostic program (4_MT)etc
Various diagnostic programs (4) including
Corresponds to means (120).

On the other hand, the diagnostic route search unit (31) in the diagnostic execution control unit (3) and the diagnostic route diagram (51) in the search processing information table (5) are the same as the diagnostic route search means (101) in FIG. Correspondingly, the priority suspicious information search unit (32) in the diagnosis execution control unit (3) and the priority suspicious information (52) in the search processing information table (5) are the suspicious device priority search means (102) in FIG. 1), the suspected device diagnosis start-up unit (33) in the diagnosis execution control unit (3) and the start-up diagnosis program information (53) in the search processing information table (5) correspond to the suspected device diagnosis start-up means (FIG. 1). 103).

In the search processing information table (5), the diagnostic execution control section (3) has a diagnostic path diagram (51) corresponding to each command (also called a command) of various diagnostic programs (4).
The priority suspect information (52) is stored in advance.

The diagnostic path diagram (51) shows the constituent devices (1) related to execution when the diagnostic execution control unit (3) executes each command [single name command] of each diagnostic program (4). Each route is illustrated.

FIG. 4 shows an example of the diagnostic path diagram (51), in which the diagnostic execution control unit (3) uses the 0-system main storage device (M).
MM diagnostic program (4) for M ₀ ) (11 ₀ ).
_In the process of executing _MM ), when a certain command (command) not shown is executed, the 0-system central controller (CC ₀ )
The system 0 main memory (MM ₀ ) (11 ₀ ) passes through (12 ₀ ), the auxiliary memory (FM ₀ ) (13 ₀ ) and the inter-processor communication controller (IPC ₀ ) (14 ₀ ). It illustrates being diagnosed.

Further, the priority suspect information (52) is a diagnostic route diagram (when the diagnostic execution control unit (3) executes each command [single name command] of each diagnostic program (4) and a device failure occurs. 51 shows the suspected priority order as the cause of the failure among the related constituent devices (1) shown in 51).

FIG. 5 shows an example of the priority suspect information (52), in which the diagnostic execution control unit (3) targets the 0-system main memory (MM ₀ ) (11 ₀ ) for the MM diagnostic program (4). _{If the} same command [command] as the diagnostic path diagram (51) shown in FIG. 4 is executed in the process of executing
The system central controller (CC ₀ ) (12 ₀ ) is the first suspected priority order, the 0 system auxiliary storage device (FM ₀ ) (13 ₀ ) is the second suspected priority order, and the 0 system inter-processor communication controller (IPC ₀ )
(14 ₀ ) indicates the third suspected priority order, and when the above three types of constituent devices (1) are not found to be the cause of the failure, the 0-system main memory device ( MM
₀ ) (11 ₀ ) has no choice but to judge that it is the cause of the failure.

Therefore, in the search processing information table (5), the number of diagnostic programs (4) held by the exchange (10) and the number of commands [single name command] constituting each diagnostic program (4). This means that the diagnosis path diagrams (51) and the priority suspicion information (52) are built in by the number obtained by multiplying by.

2 to 5, the diagnosis execution control unit (3) starts the MM diagnosis program (4 _MM ) and executes the diagnosis of the main memory (MM) (11), and as a result, the MM diagnosis program (4) is executed. 4 _MM ), the device failure information (NG) as shown in FIG. 3 is notified to the diagnosis execution control unit (3).

The device failure information (NG) shown in FIG.
The first line [\ DER MM0,5 /] indicates the device to be diagnosed [the fifth phase of the 0-system main memory (MM) (11)], and the second line [MM PHASE5 NG] is the device failure. Of the occurrence of [the occurrence of a defect in the fifth phase of the diagnosis of the main memory (MM) (11)], the third line [TEST
NO. 30] indicates a device failure occurrence test number [device failure occurred in the 30th test], and the fourth line [COR
= 12345678, ANS = 12341234],
Failure result [Correct answer of the test in the third row (COR = 12345
678) and the obtained wrong answer (ANS = 1234123)
4)] is shown.

The diagnostic execution control unit (3) uses the MM diagnostic program (4 _MM ) to determine device failure information (N) as shown in FIG.
When G) is collected, the diagnostic route search unit (31) is activated. The activated diagnosis path search unit (31) determines the device to be diagnosed [¥ DER M] from the collected device failure information (NG).
M0,5 /] and device failure occurrence test number [TEST
NO. 30] and the search processing information table (5) is referred to, and the diagnosis target device [¥ DER MM0,5
/] And the device failure occurrence test number [TESTNO. 3
0] and a diagnostic route map (51) corresponding to the extracted diagnostic route diagram (51) as shown in FIG. 4, and the collected device is displayed on the display of the maintenance terminal device (CNS) (15). It is displayed together with the defect information (NG) [see FIG. 3].

Subsequently, the diagnosis execution control section (3) activates the priority suspect information retrieval section (32). The activated suspected information retrieval unit (32) activates the diagnosis target device [¥ DER that the diagnosis route retrieval unit (31) has extracted from the device failure information (NG).
MM0,5 /] and device failure occurrence test number [TEST
NO. 30] and the priority suspicious information (52) corresponding to the above, and the priority suspicious information (52) as shown in FIG. 5 is extracted and displayed on the display provided in the maintenance terminal device (CNS) (15).

Subsequently, the diagnosis execution control unit (3) starts the suspected device diagnosis starting unit (33). The activated suspected device diagnosis activation unit (33) starts the 0th system central control device (CC ₀ ) (CC ₀ ) In order to execute the diagnosis for 12 ₀ ), the search processing information table (5) is referred to, and the CC diagnosis program (4 _CC ) is set to the central control unit (CC ₀ ) (12 ₀ ) of the 0 system as the diagnosis target. The startup diagnostic program information (53) such as parameters required for execution is extracted, and the diagnostic startup command [single name command] [¥
DER CC0 / ...... Startup diagnostic program information (5
3) ...], and the diagnosis execution control unit (3) starts executing the CC diagnosis program (4 _CC ).

When the diagnosis execution control unit (3) executes the CC diagnosis program (4 _CC ) and the central control unit (CC ₀ ) (12 ₀ ) to be diagnosed receives a notification that it is normal, the diagnosis is executed. after displaying on the display of the target central controller (CC ₀₎ (12 ₀₎ maintenance terminal diagnostic result [= normal] of (CNS) (15), starting the diagnostic program information (5
Instruct 3) to start diagnosis of the second suspected priority order.

The start diagnostic program information (5
3) executes diagnosis on the 0th system auxiliary storage device (FM ₀ ) (13 ₀ ) which is the second suspicion priority order based on the priority suspicion information (52) extracted by the priority suspicion information retrieval unit (32). In order to do so, the search processing information table (5) is referred to, and parameters required for executing the FM diagnostic program (4 _FM ) with the 0-system auxiliary storage device (FM ₀ ) (13 ₀ ) as the diagnostic target The boot diagnostic program information (53) of is extracted and the boot diagnostic program information (53) extracted is used to execute the diagnostic boot command [single name command] [\ DER FM0 /
...... Startup diagnostic program information (53) ...] is created, and the diagnostic execution control unit (3) starts executing the FM diagnostic program (4 _FM ).

When the diagnosis execution control unit (3) executes the FM diagnosis program (4 _FM ) and as a result receives the notification that the auxiliary storage device (FM ₀ ) (13 ₀ ) to be diagnosed is normal, the diagnosis is executed. After the diagnosis result [= normal] of the target auxiliary storage device (FM ₀ ) (13 ₀ ) is displayed on the display of the maintenance terminal device (CNS) (15), the startup diagnostic program information (5
Instruct 3) to start diagnosis of the third suspected priority order.

The start diagnostic program information (5
3), to the basis of the priority suspected information priority suspected information retrieval unit (32) is extracted (52), the third is suspected priority 0-series processing apparatus communication controller (IPC ₀₎ (14 ₀₎ In order to execute the diagnosis, the search processing information table (5) is referred to, and the 0-system inter-processor communication control unit (IPC ₀ )
(14 ₀₎ IPC Diagnostics program (4 as a diagnostic target
The start diagnostic program information (53) such as parameters required to execute _IPC ) is extracted, and the diagnostic start command [single name command] [\ DER IPC0 / is used by using the extracted start diagnostic program information (53). ...... Startup diagnostic program information (53) ...] is created, and the diagnostic execution control unit (3) starts executing the IPC diagnostic program (4 _IPC ).

When the diagnostic execution control unit (3) executes the IPC diagnostic program (4 _IPC ) and receives a notification that the inter-diagnosis processing unit communication control unit (IPC ₀ ) (14 ₀ ) is normal. It is displayed on the display of the diagnosis target processor communication controller (IPC ₀₎ maintenance terminal diagnostic result [= normal] of _{(14 0) (CNS) (} 15).

The maintenance person uses the maintenance terminal device (CNS) (1
5) Device defect information (N) displayed on the display
G), diagnostic route map (51) and priority suspect information (52)
According to the suspected priority order shown in the priority suspect information (52), each suspected constituent device [= central controller (CC ₀ ) (1
2 ₀ ), the auxiliary storage device (FM ₀ ) (13 ₀ ), the inter-processor communication control device (IPC ₀ ) (14 ₀ )], the diagnosis results (all are normal) sequentially executed are recognized, and a failure occurs. It is determined that there is no cause other than the 0-system main memory (MM ₀ ) (11 ₀ ).

Thereafter, the maintenance person replaces the device to be diagnosed [system 0 main memory (MM) (11) with a unit whose normality is guaranteed, and executes the diagnosis by the MM diagnostic program (4 _MM ) again, When the device failure information (NG) is recovered,
Investigate the cause of failure by analyzing the affected device in detail.

In the above process, the 0-system central controller (C
C ₀ ) ( ₁₂₀ ) [first suspected priority order], 0-system auxiliary storage device (FM ₀ ) (13 ₀ ) [second suspected priority order], and 0-system inter-processor communication control device (IPC ₀ ) (14) ₀ )
If the device failure information (NG) is output to the diagnosis result of any one of the [third suspected priority orders] [for example, the 0-system central controller (CC ₀ ) ( ₁₂₀ )], the 0-system main storage device (MM
₀ ) (11 ₀ ) the failure analysis processing is temporarily suspended, and the newly output 0-system central controller (CC ₀ ) (12 ₀ )
As target device defect information regarding diagnosis (NG) of, performs fault analysis process in the process similar to that described above, 0 central control unit (CC ₀₎ (12 ₀₎ after the failure analyzing process is completed regarding, interrupted 0 system main memory (MM ₀ ) (1
The failure analysis process for ₁₀ ) is restarted.

As is apparent from the above description, according to the embodiment of the present invention, when the diagnostic execution control unit (3) executes the MM diagnostic program (4 _MM ) and the device failure information (NG) is output. Then, the diagnostic route search unit (31) automatically extracts the diagnostic route map (51), and the priority suspicious information search unit (32).
Automatically extracts the priority suspect information (52), and the start diagnosis program information (53) sequentially executes the diagnosis program (4) of the suspected constituent device (1) to the diagnosis execution control unit (3) according to the suspect priority order. Then, the cause of the failure will be investigated.

It should be noted that FIGS. 2 to 5 are merely one embodiment of the present invention. For example, the diagnostic target constituent device (1), device failure information (NG), diagnostic route diagram (51) and priority suspect information. (52) is not limited to those shown in the drawings, and various modifications can be considered, but the effect of the present invention does not change in any case. It goes without saying that the exchange (100) to which the present invention is applied is not limited to the exchange (10) shown.

[0041]

As described above, according to the present invention, in the exchange, the suspected constituent devices related to the diagnosis of the result defect are automatically diagnosed sequentially from the device having the highest suspected priority order. Also, it is possible to carry out an accurate investigation of the cause in a short time without being influenced by experience, and the reliability and maintainability of the exchange are greatly improved.

[Brief description of drawings]

FIG. 1 is a principle diagram of the present invention.

FIG. 2 is an exchange according to an embodiment of the present invention.

[Fig. 3] Target device failure information of Fig. 2

FIG. 4 is a diagnostic route diagram in FIG.

FIG. 5: Priority suspect information in FIG.

FIG. 6 Conventional exchange

[Explanation of symbols]

1, 110 Configuration device 2 Call processing unit 3 Diagnostic execution control unit 4 Diagnostic program 4 _MM MM diagnostic program 4 _CC CC diagnostic program 4 _FM FM diagnostic program 4 _IPC IPC diagnostic program 4 _MT CNS diagnostic program 5 Search processing information table 10, 100 Exchange 11 Main storage (MM) 12 Central control (CC) 13 Auxiliary storage (FM) 14 Inter-processor communication control (IPC) 15 Maintenance terminal (CNS) 31 Diagnostic route search 32 Priority suspect information search 33 Suspected Device Diagnosis Starting Unit 51 Diagnosis Route Diagram 52 Priority Suspicion Information 53 Startup Diagnosis Program Information 101 Diagnosis Route Searching Means 102 Suspected Device Priority Searching Means 103 Suspected Device Diagnosis Starting Means 120 Diagnostic Means

Claims (3)

[Claims] 1. A switching system comprising a plurality of constituent devices and comprising respective diagnosing means for diagnosing the various constituent devices, wherein as a result of the diagnosing means carrying out the diagnosis of the corresponding constituent devices, When a defect of the target component device is detected, the test type executed at the time of defect detection and device defect information indicating the diagnosis result are collected and analyzed from the diagnostic means, and each component device involved in the diagnosis is collected. The diagnostic route shown
A diagnostic route search means for searching from a plurality of diagnostic routes held in advance; a suspected device priority search means for determining a suspected priority of each constituent device included in the diagnostic route detected by the diagnostic route search means; A fault information analysis method, further comprising: a suspected device diagnosis activation means for sequentially activating diagnostic means corresponding to each suspected constituent device based on the suspected priority order determined by the suspected device priority order search means. 2. The fault information analysis method according to claim 1, wherein the diagnostic route search means displays the detected diagnostic route to a tester. 3. The fault information analysis method according to claim 1, wherein the suspected device priority search means displays the determined suspected priority order of each of the constituent devices to a tester.