JPH01243746A - Fault diagnostic system - Google Patents

Abstract

PURPOSE:To clearly display candidate parts of fault parts from the ones at higher probability by separating the fault part in a fault state generated in a network based on fault information and the fault generation history information of the fault parts. CONSTITUTION:A center device 100 successively execute polling to multiplexing devices 101 and 102, and the fault information is collected as its response data. At such a time, the center 100 first exchanges commands to set a connection with the multiplexing device 101 and 102, and after the completion of the connection setting, it collects the fault information. Based on the fault information and the fault generation history information of the fault part, the fault part in the fault state generated in the network is separated.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a fault diagnosis method, and particularly to a fault diagnosis method suitable for fault diagnosis in fault situations where it is difficult to collect fault information.

[Conventional technology]

Traditionally, network management has mainly focused on modem networks, but as the use of high-speed digital lines increases, the management of networks consisting of multimedia multiplexing equipment has become important. ing. The functions required of a management system for a multimedia multiplexing device are discussed, for example, in "Nikkei Communication" (July 7, 1986 issue, pages 101-103). Here, an overview of the display function, system configuration function, channel configuration function, two-line configuration change function, route configuration function, alarm function, monitoring function, and diagnostic function is mainly described.

[Problem to be solved by the invention]

Conventionally, as a fault diagnosis method, which is one of the fault management functions mentioned above, each multimedia multiplexing device (hereinafter referred to as
1p, (hereinafter referred to as the "multiplexer") by an interrupt, or from the network management center (hereinafter referred to as the "multiplexer").
1. The location of the fault has been isolated based on fault information collected by polling from the multiplexer (called a "center") to the multiplexing device.

However, up until now, the method has been to collect one piece of fault information, start diagnosis based on this information, and proceed to isolate the location of the fault while analyzing the information collected one after another. With this method, it takes time to collect the fault information, and if the fault information cannot be collected, problems may occur in troubleshooting the fault.

It is an object of the present invention to solve the above-mentioned problems in conventional fault diagnosis methods, and to provide an information network in which fault information is collected by polling from a center to each multiplexer without any problems.

The object of the present invention is to provide a fault diagnosis method that makes it possible to isolate the faulty part.

[Means to solve the problem]

The above-mentioned object of the present invention is that the present invention is composed of a center, a plurality of communication nodes managed by the center, and a plurality of communication lines connecting these, and that network management information is collected by polling from the center to each of the communication nodes. In an information network where a fault occurs in a network, the fault location in a fault situation that occurs in the network is isolated based on the information collected by the polling, fault information indicating that fault information cannot be collected, and fault occurrence history information of the fault location. This is achieved using a characteristic fault diagnosis method.

[Effect]

In the present invention, the center sequentially transmits polling messages to the multiplexing devices constituting the network to be managed, and collects failure information accumulated in each multiplexing device. At this time, the center communicates with the destination multiplexer,
First, commands for setting up a connection are sent and received, and after the connection setting is completed, failure information can be collected. Therefore, if fault information is successfully collected, the fault location can be isolated based on that information.

On the other hand, if fault information cannot be collected, it is likely that a fault has occurred during connection setup as described above or during subsequent fault information collection, and these may occur at the center in the form of response monitoring timeouts at each level. will be recognized. Therefore, if fault information cannot be collected, the fault location can be isolated based on the combination of timeouts detected at the center and the fault occurrence history information of the fault location corresponding to these combination results.

〔Example〕

Embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 2 shows the basic configuration of a network consisting of multiplexing devices showing one embodiment of the present invention.
0 is the center, 101 and 102 are multiplexers, 104 and 1
05 is a remote control adapter (hereinafter referred to as "adapter"), and 103 is a high-speed digital line.

The center 00 polls the multiplexing devices 101 and 102 in turn and collects failure information as response data. Here, the fault information is automatically collected by the multiplexing device regarding the status of the main unit, the high-speed digital line connected thereto, and the subscriber line. During polling, the center 100 and the polling destination multiplexing device,
For example, first, a logical transport connection is established between the adapters 105 of the multiplexing device 102.

Here, the adapters 104 and 105 constitute a management information network.

As shown in FIG. 3, after transmitting the transport connection setting command 106, the center 100 starts time monitoring for a response 107 from the adapter 105. adapter 1
Upon receiving the command 106, the node 05 sends a response 107 back to the center 100, and also sends a polling message 108 added to the transport connection setting command 106 to the multiplexing device 102. The multiplexing device 11102 returns a failure information message 109 as a response. When the center 100 receives the response 107, it cancels time monitoring and newly starts time monitoring of the failure information message 109. When the failure information message 109 is received, monitoring is canceled for one hour and failure diagnosis begins.

For example, assuming that a failure has occurred in the high-speed digital line 103, a retryout will occur at the data link level between adapters 104 and 105, and the transform connection setting command 106 will not arrive at the remote control adapter 105. Become. Therefore, response 10
7 is of course not returned to the center 100, so the response 10 is
7 time monitoring will time out. This timeout is set to management network retryout (hereinafter referred to as "management network RO").
It is called J). In addition, the above adapters 104 and 105
A tryout at the data link level between the two is detected by the adapter 104 because the data link level response 110 is not returned to the adapter 104, and the report message 11
1 is reported to the center 100. This is called a data link retryout (hereinafter referred to as "data link ROJ"). Therefore, if a failure occurs in the high-speed digital line 103, failure information cannot be collected from the multiplexer 102, but the failure information can be collected from the adapter 104. Since it is possible to detect data link Y ri 0 of
03.

Next, if a failure occurs in the multiplexer 102 main body, the polling message 108 is sent to the multiplexer 102.
2, so of course failure information message 109 is sent.
will not be returned to the center 100. Therefore, the time monitoring of the failure information message 109 will time out.

This timeout can be set as application timeout (
(hereinafter referred to as "rAP timeout"). In this case, data link RO and management network I 0 will not occur, and
Since only an AP timeout occurs, it can be determined that the multiplexing device 102 is the faulty part.

As described above, failure diagnosis can be performed by using failure information that is automatically collected by the multiplexing device as failure information that cannot be collected at the center. However, in the above example, the fault location can be determined at one location, but generally there are multiple candidates.

In order to determine which candidate is the most likely, the frequency of failure occurrence of failure parts is maintained as historical information, and the failure parts are narrowed down based on this information. Hereinafter, details of the processing of the center 100 will be explained for each step according to the flowchart of FIG.

Step 200: Select a multiplexer to send the polling message.

Step 210: Send a polling message to the selected multiplexer.

Step 220: Determine whether failure information from the multiplexing device has been collected.

Step 230: Now that the fault information has been collected, fault isolation is performed based on that information.

Step 240: Since failure information could not be collected, check whether a data link level raw report has been received.

Step 250: If a report of the occurrence of data link I has been received, confirm that the occurrence of management w4RO has been detected.

Step 260: Refer to the failure occurrence M layer information of the failure part.

Step 270: It is determined that the faulty part is a high-speed digital line with probability 1. It also updates the failure occurrence history information of the high-speed digital line.

Step 280: If no report of data link RO occurrence has been received, check whether the occurrence of management W4RO has been detected.

Steps 290 and 300: If the occurrence of a management network error 0 is detected, refer to the failure occurrence history information of the failure part and determine that the failure part is the adapter with a probability of 1. Additionally, the failure history information of the adapter is updated.

Step 300: If the occurrence of management network RO is not detected.

Confirm that AP timeout is detected.

Steps 320 and 330: In this case, referring to the failure history information of the failed part, it is determined that the failed part is a multiplexing device with a probability of 1. Also,
Update the failure history information of the multiplexing device.

Next, a specific configuration example will be explained using FIG. 4. Fourth
The figure shows an example of the configuration of a network composed of multiplexing devices. In the figure, 100 is the center, 4, 6 . to, 1
4 is a multiplexing device, 2.7° 11.15 is the adapter,
5,9,13. ] 7 is high-speed digital line, 18.1
9 is a control line connecting the multiplexer 4 and the adapter 2 (corresponding to high-speed digital JLt times'l1A5 and 9, respectively)
, 20, 21 Control for connecting iLs heavy equipment R6 and adapter 7, @(high-speed digital lines 5 and 1, respectively)
7), 22°23 is the multiplexer 10 and adapter 1
1 (respectively high-speed digital line 9,
13), 24 and 25 are control lines connecting the multiplexer 14 and the adapter 15 (corresponding to the high-speed digital line 1
7, 13), 1.3 corresponds to center 100 and multiplex bag W!, respectively. Communication line connecting i4 and adapter 2,
8, 12.16 are multiplexing devices 6, 10.
14 and the adapter 7.11°15 are shown.

Computers, etc. are connected to the subscriber line side of each multiplexer and communicate with each other, and data is exchanged between the multiplexers via high-speed digital lines 5, 9, 13, and 17. . Adapters 2.7.11 and 15 are
Fault information on the multiplexer main bodies 4゜6.10 and 14 and the high-speed digital lines connected to them is sent to the center 10.
0 is a packet switch that constitutes a management information network for collecting data through polling. When polling each multiplexing device from the center 100, a case will be explained in which the route taken by the polling message is polling the multiplexing devices 6 from the remote 1 to.

The polling message first enters the adapter 2, and the network management function of the adapter 2 recognizes from the address in the polling message that the destination is not multiplex bag R4, and sends the polling message to the control line 18 according to the routing information in the polling message. Send out.

The message contained in the multiplexing bag Wi4 is sent to the high-speed digital line 5 corresponding to the control line 18, and is sent to the multiplexing device l.
! Enter 6. Furthermore, it is sent from the multiplexer 6 to the adapter 7 via the control s20 corresponding to the high-speed differential circuit 5. What is the network management function of adapter 7?

Since the destination is the multiplexer 6, the polling message is sent to the communication line 8. When the multiplexer 6 receives the polling message, it creates response data and sends it for one communication wA.
Send on 8th. The sent response data reaches the center 100 by following the reverse route.

Table 1 shows the fault isolation results based on the responses obtained when polling a (remote) multiplexed bag w114 that is not directly connected to the center 100. Status word which is fault information (response data from multiplexer)
If the message cannot be received, AP timeout, management 1
Will detect wRO or data link RO6
For example, when only the management network RO is detected, the fault location is the communication cycle fil with a probability of 0.5 and the input port of adapter 2 with a probability of 0.3 based on the past occurrence history information of the fault location.

With probability 2, this is the management function of adapter 2. This means that only the management network RO is detected, which means that no transport connection is set up between the center 100 and the adapter 15, and no data link RO is occurring between the adapters on the way. This means that
The faulty part may be the communication line 1, the input port of the adapter 2, or the management function of the adapter 2. It is concluded from the occurrence history information of each fault location that a fault has occurred with the above probability. Furthermore, if a failure actually occurs in the communication line 1, for example, the failure occurrence history information of the communication line 1 will be updated later.

As described above, according to this embodiment, if the status word, which is fault information, can be collected from the multiplexing device, fault diagnosis is performed based on the fault information, and if the status word cannot be collected, the multiplexing device communicates with the center 100. Fault diagnosis can be performed by using the response monitoring timeout detection function of each layer of the management information transfer protocol between the storage devices and the matching function of the timeout result and the history information of the failure occurrence of the corresponding failure part.

Note that the above embodiment is explained as an example, and
It goes without saying that the present invention is not limited to this.

〔Effect of the invention〕

As described above, according to the present invention, the network management center includes a network management center, a plurality of communication nodes managed by the network management center, and a plurality of communication lines connecting these nodes, and network management information is transmitted from the network management center. In the information network that is collected by polling each of the communication nodes, a failure situation that has occurred in the network is based on the information collected by the polling, failure information that KC damage information cannot be collected, and failure occurrence history information of the failure part. Since the fault parts are separated in the following manner, the candidate parts of the fault parts corresponding to the fault situation can be specified in order of probability, and this has the effect of shortening the time from fault detection to repair.

4. Full description of the drawings Fig. 1 is a flowchart showing the operation of the management center of a network showing one embodiment of the present invention, Fig. 2 is a basic configuration diagram of the network of the embodiment, and Fig. 3 is a flowchart showing the operation of the management center of the network according to an embodiment of the present invention. An explanatory diagram showing an example of a transfer sequence of management information of the conversion device 1m,
FIG. 4 is a block diagram showing an example of the configuration of the network according to the embodiment.

2.7. L, 1, 15, 104, 105... Adapter, 4.6, 10, 14, 101, 102... Multiplexer, 5, 9, 13, 1.7, 103... High speed digital bowl 1 Figure￥2 Figure/I! '／

Claims (1)

[Claims] 1. Consists of a network management center, multiple communication nodes managed by the network, and multiple communication lines connecting these, and network management information is collected by polling from the network management center to each communication node. The present invention is characterized in that a failure part in a failure situation occurring in a network is isolated based on information collected by polling, failure information that failure information cannot be collected, and failure occurrence history information of the failure part in an information network where the failure occurs in the network. Fault diagnosis method.