JPH05102995A - Fault part specifying method for duplexed system bus - Google Patents

Abstract

PURPOSE:To early detect a fault by transmitting data while duplexing two buses, returning the data from the reception side to a return transmission source and specifying a suspicious part according to the presence/absence of the fed- back data, route and status information. CONSTITUTION:A transmission side node M sets a return system designating area to the transfer format of data and transmits the data to a reception side node N after adding a return communication ID, return system designation data and transmission status. The node subscribes reception status into the return system designating area based on the return ID and the designatior data in the transmitted data and afterwards, a bus transmission/reception part 2 transmits the data through a designated system to the node M again. The node M specifies a fault system and the fault part according to the transmission/ reception status. Thus, the early detection of the fault and the reconstitution of the system can be effectively executed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention performs maintenance / inspection or failure recovery of a duplicated system bus in consideration of detection of a failure and restoration from the failure. The present invention relates to a part specifying method.

[0002]

2. Description of the Related Art Conventionally, in a network architecture in which several nodes having information and communication processing functions such as a host computer, a terminal control device, a remote processing device, and a terminal device are connected by a duplicated system bus, In order to perform failure recovery in the event of a node failure, disconnect the failed node from the system bus and then perform a system bus failure condition test or node failure test individually to determine the location of the failure. It is identified and repaired.

[0003]

However, in the conventional fault detection method, since the node fault test and the system bus fault condition test are performed under the condition different from the actual online operation, a more accurate fault is detected. It is extremely difficult to identify the part and investigate the cause of the abnormality, and the failure cannot be found in the test results. When the node is connected to the system again, the failure occurs again.

Further, the system operation must be started only by the test before the node is incorporated into the system, and the system configuration is extremely unreliable in system construction. An object of the present invention is to eliminate the above-mentioned conventional problems and provide a method of identifying a faulty part of a duplicated system bus.

[0005]

In order to solve the above-mentioned problems, the method for identifying a faulty part of a duplicated system bus according to the present invention is independent of the duplicated system bus and the system bus. In each of the nodes of the communication system including at least two nodes capable of controlling transmission / reception of data, a loopback system designation area for writing a loopback communication ID and loopback system designation data is provided in a bus transfer format of communication data, A step of changing the loopback system designation data to create communication data, and setting a loopback communication ID only when loopback communication is performed;
A step of adding a transmission status to the communication data, selecting one of the duplicated system buses to send the communication data, and a return communication ID from the return system designated area of the received communication data. When it is read and the ID identifies that the communication data is loopback communication, the loopback system designation data is further read, and a reception status is added to the received communication data on the system bus designated by the data, and then the loopback communication is designated again. As a result of the combination of the step of sending back the communication data and the system bus that has transmitted the communication data and the loopback system designation data in the loopback system designation area, the transmission status and the reception status of the communication data received by looping back. Two
And a step of identifying which one of the duplicated system buses has failed.

[0006]

Operation: One of the duplicated system buses is a 0-system bus,
The other is a 1-system bus. Callback ID of the call-back system designated area in the communication data transfer format at the source node
Is set, and whether a failure has occurred in system 0 or system 1 of the selected transmission system bus or system 0 or system 1 of the reception system bus depending on the transmission / reception status of the communication data depending on the combination of the transmission system bus and the reception system bus. It is possible to identify whether a failure has occurred in the system.

[0007]

An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 represents a network architecture for implementing one embodiment of the present invention.

In FIG. 1, there is a data transmission / reception control unit 3 and a bus transmission / reception unit 1 which form a node M. The bus transmission / reception unit 1 and the data transmission / reception control unit 3 are bus driver units of the data transmission / reception control unit 3. 4 and the local bus 10. Interface 6 for bus transceiver 1
And the interface 7, and the interface 6 is connected to the 0-system bus 100.
Are each connected to the 1-system bus 200. The 0-system bus 100 and the 1-system bus 200 form a loop.

The data transmission / reception control unit 12 and the bus transmission / reception unit 2 which compose the node N are the data transmission / reception control unit 1
2 are connected via the bus driver unit 5 and the local bus 11. The interface 8 in the bus transceiver unit 2 is connected to the 0-system bus 100, and the interface 9 is connected to the 1-system bus 200.

The data transmission / reception control unit 3 and the data transmission / reception control unit 12 have a built-in function for detecting data loopback communication with another node and a function for looping back and transferring the received data to the bus transceivers 1 and 2 again. ing. Further, when performing the return communication between the nodes, a return system designation area for writing the return communication ID and the return system designation data for designating the return bus is added to the data transfer format. However, in the normal data communication state, such a folding system designation area is not added.

The return communication operation between the node M and the node N in the above configuration will be described below.

When the transmitting node M attempts to perform loopback communication, the node M sets the loopback system designation area in the data transfer format and adds the loopback communication ID, loopback system designation data, and transmission status. , It is transmitted to the partner node N that this data communication is loopback communication, and the system that transfers the loopback data is designated.

In the node N on the receiving side, based on the loopback ID and the loopback designating data in the transferred data, after the reception status is added to the loopback system designated area of the received communication data, the bus transmitting / receiving unit is again provided. 2 transmits the received data to the node M via the designated system.

The node M, which is the transmitting side, identifies the following failure system and failure part based on the transmission / reception status of the data that has been returned after being returned. However, there are the following four types of communication system setting patterns (A) to (B). (A) Return communication operation (A) The data transmission / reception control unit 3 of the node M exchanges data with the bus transmission / reception unit 1 via the bus driver unit 4 and the interface 8 of the node N via the interface 6 and the 0-system bus 100. The data is transferred to the bus transceiver 2 (arrow 21 in FIG. 2).

(B) In the node N, the data received from the node M is loop-transferred to the bus transmitting / receiving unit 2 as it is to the interface 6 of the node M and the bus transmitting / receiving unit 1 via the interface 8 and the 0-system bus 100 ( Figure 2
Arrow 22). (B) Return communication operation (a) The data transmission / reception control unit 3 of the node M communicates with the bus transmission / reception unit 1 via the bus driver unit 4 and the data with the interface 9 of the node N via the interface 7 and the 1-system bus 200. The data is transferred to the bus transmitting / receiving unit 2 (arrow 23 in FIG. 3).

(A) In the node N, the data received from the node M is loop-transferred as it is to the bus transmitting / receiving unit 2 to the interface 6 of the node M and the bus transmitting / receiving unit 1 via the interface 8 and the 0-system bus 100 ( Figure 3
Arrow 24). (C) Return communication operation (a) The data transmission / reception control unit 3 of the node M communicates with the bus transmission / reception unit 1 via the bus driver unit 4 and the data with the interface 8 of the node N via the interface 6 and the 0-system bus 100. The data is transferred to the bus transmitting / receiving unit 2 (arrow 25 in FIG. 4).

(B) In the node N, the data received from the node M is loop-transferred as it is to the bus transceiver 2 to the interface 7 of the node M and the bus transceiver 1 via the interface 9 and the 1-system bus 200 (FIG. 4 arrow 26). (D) Return communication operation (a) The data transmission / reception control unit 3 of the node M exchanges data with the bus transmission / reception unit 1 via the bus driver unit 4 and the interface 9 of the node N via the interface 7 and the 1-system bus 200. The data is transferred to the bus transmitting / receiving unit 2 (arrow 27 in FIG. 5).

(B) In the node N, the data received from the node M is sent back to the bus transmitting / receiving unit 2 as it is, to the interface 7 of the node M and the bus transmitting / receiving unit 1 via the interface 9 and the 1-system bus 200 (FIG. 5 arrow 28).

As a result of the data transfer of the above (A) to (D),
Depending on the transmission / reception status of the data that has been returned after being returned, if the data has an error or if the result of loss is that the data has not been returned at all, the following judgment can be made.

Here, f (A) = 0 means that an error has occurred in the return data in the process (A), and f (A) = 1 means that no error has occurred. I shall. (1) When f (A, B, C, D) = (1, 1, 1, 1), no error occurs in any of the above operations (A) to (D), and any bus and It also indicates that the node has no failures. (2) f (A) = (0), that is, 0 bus 1
When a failure occurs somewhere in 00.

Then, as a result of performing the operation (D), f
With (D) = (1), it was confirmed that no failure occurred anywhere in the 1-system bus 200. After that, operation (B),
(C) is performed. As a result, f (B, C) = (1,
If it is 0), it is confirmed by the operation (D) that the system 1 bus 200 has no error.
A failure has occurred in the 0 transmission system (arrow 21 in FIG. 2).

Contrary to the above, if the result of performing the operations (B) and (C) is f (B, C) = (0,1), then 0
A failure has occurred in the loopback system (arrow 22 in FIG. 2) of the system bus 100. (3) f (D) = (0), that is, system 1 bus 2
When a failure occurs somewhere in 00.

Then, as a result of performing the operation (A), f
With (A) = (1), it was confirmed that no error occurred anywhere on the 0-system bus 100. After that, operation (B),
(C) is performed, and as a result, f (B, C) = (1,0)
If it is, it is confirmed by the operation (A) that there is no error in the 0-system bus 100, so an error has occurred in the loop-back system (arrow 28 in FIG. 5) of the 1-system bus 200. ..

Contrary to the above, if the results of performing the operations (B) and (C) are f (B, C) = (0,1), then 1
A failure has occurred in the transmission system (arrow 27 in FIG. 5) of the system bus 200.

As described above, in the node station which has issued the return communication, the failure system and the failure part can be identified by the combination of the transmission system return system and the transmission / reception status.

[0026]

As described above, according to the present invention, in order to improve the reliability of the system itself, two buses are duplicated, test data is sent out on the system bus, and the received data is received by the receiving side. Is returned to the sender, and the suspected part can be identified online based on the presence / absence of the returned data, route, and transmission / reception status information, so early detection of a failure and system reconfiguration due to a failure can be performed more effectively. It will be possible.

[Brief description of drawings]

FIG. 1 is a diagram representing a network architecture for implementing an embodiment of the present invention.

FIG. 2 is an explanatory diagram of a return communication operation (A).

FIG. 3 is an explanatory diagram of a return communication operation (B).

FIG. 4 is an explanatory diagram of a return communication operation (C).

FIG. 5 is an explanatory diagram of a return communication operation (D).

[Explanation of symbols]

1, 2 bus transmission / reception unit 3, 12 data transmission / reception control unit 4, 5 bus driver unit 6, 7, 8, 9 interface 10, 11 local bus 1000 system bus 200 1 system bus 21, 22, 23, 24, 25, 26, 27, 28 arrows

Claims (1)

[Claims] 1. A communication data bus at each node of a communication system comprising a duplicated system bus and at least two nodes capable of controlling data transmission / reception by independently using the system buses. A loopback communication designation area for writing a loopback communication ID and loopback system designation data is provided in the transfer format, communication data is created by changing the loopback system designation data, and loopback communication I is performed only when loopback communication is performed.
Setting D, adding a transmission status to the communication data, selecting one of the duplicated system buses to send the communication data, and returning the received communication data. When the loopback communication ID is read from the system designation area and it is identified that the communication data performs the loopback communication by the ID, the loopback system designation data is further read and the communication data received by the system bus designated by the data is received. The step of sending back the reply data after adding the reception status to the result of the combination of the system bus that transmitted the communication data and the reply system designation data in the reply system designation area Depending on the transmission status and the reception status, a failure may occur in any of the duplicated system buses. Duplexed system bus Failure Point method for identifying whether the and performing.