CN101938365B - Fault handling method and device for Ethernet - Google Patents

Abstract

The invention provides a fault processing method and device in the Ethernet. The method mainly includes: the management node receives the fault information reported by the communication nodes at both ends of the Ethernet link, and the management node, according to the fault information, and the communication nodes at both ends of the Ethernet link The heartbeat detection information between the Ethernet links and the failure information of the communication nodes at both ends are acquired. In the embodiment of the present invention, by setting a special management node and monitoring the state of the communication node through a special management communication channel, the communication link failure and communication node failure information in the Ethernet can be effectively obtained and distinguished, and the failure recovery is facilitated quickly.

Description

Method and device for troubleshooting in Ethernet

technical field

The invention relates to the technical field of Ethernet communication, in particular to a method and device for processing faults in the Ethernet.

Background technique

With the continuous development of Ethernet in MAN and WAN, operators pay more and more attention to the OAM (Operations Administrations and Maintenance, maintainability) of Ethernet equipment and links.

Existing OAM solutions focus on the management and maintenance of point-to-point Ethernet links, providing a complete Ethernet OAM solution. As an optional sublayer of the MAC (Media Access Control, Media Access Control) layer, the OAM sublayer provides an effective mechanism for monitoring the link operation status when it is in effect, and can be applied to any full-duplex, A point-to-point Ethernet link, or a simulated point-to-point Ethernet link.

In the existing OAM solution, link fault indication and location are performed through fatal event notification and common event notification.

Fatal event notification is implemented by the flag bits in OAM PDU (Protocol Data Unit, protocol data unit), mainly including:

Link Fault: Indicates that the local PHY (Physical Layer Device, physical layer device) Rx (Receiver, receiver) is faulty (the peer link signal is lost).

Dying Gasp: An unrecoverable local error has occurred.

Critical Event: An unknown critical fault occurs.

Common event notifications are implemented using the TLV (Type-Length-Value) field in OAM PDUs, mainly including:

False Symbol Period Event: The number of detected false symbols exceeds a defined threshold within a given time window.

Error Frame Event: The number of error frames detected within a given time window exceeds a defined threshold.

Error frame period event: The number of error frames detected in the quantified received frames exceeds the defined threshold.

Errored frame second event: The number of errored frame seconds detected within a certain number of seconds exceeds the defined threshold. An interval second is called an error frame second when one or more error frames are detected in frames received within an interval second.

The above-mentioned fatal event notification and common event notification are mainly for monitoring error events during reception, and at the same time, if an unrecoverable error occurs in the receiving device or equipment at the local end, it will try its best to notify the opposite end.

In the process of implementing the present invention, the inventors found that the solution of indicating and locating link faults through fatal event notification and ordinary event notification in the above-mentioned prior art has at least the following problems:

Although this scheme can find the failure of the receiving device and the communication link on the communication node, it does not stipulate how to notify the user of the found failure. At the same time, the failure of the communication node itself cannot be identified. The failure of the communication node itself refers to the failure of the core software or hardware inside the communication node, resulting in the failure of the entire communication node to operate normally. However, if the receiving device, the transmitting device, the receiving link or the transmitting link on the communication node fail, other parts of the communication node that have not failed can still work normally.

Contents of the invention

Embodiments of the present invention provide a method and device for processing faults in the Ethernet.

An embodiment of the present invention provides a fault handling method in Ethernet, the method comprising:

The management node receives the fault information reported by the communication node at the endpoint of the Ethernet link;

The management node obtains the failure information of the communication node according to the failure information and the heartbeat detection information between the management node and the communication node.

A device for processing faults in Ethernet provided by an embodiment of the present invention includes:

The fault information receiving module is used to receive the fault information reported by the communication node of the endpoint of the Ethernet link;

A fault processing module, configured to acquire fault information of the communication node according to the fault information received by the fault information receiving module and heartbeat detection information between the fault processing device and the communication node.

It can be seen from the technical solutions provided by the above-mentioned embodiments of the present invention that the embodiments of the present invention can effectively obtain and distinguish the communication nodes in the Ethernet by setting a special management node and monitoring the status of the communication nodes through a special management communication channel. Link failure and communication node failure information facilitates rapid failure recovery.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without any creative effort.

Fig. 1 provides the schematic diagram of the principle of setting the management node for the Ethernet full-duplex link provided by the embodiment of the present invention;

FIG. 2 is a schematic diagram of a communication node reporting to the management node that the receiver of the communication node has a failure provided by an embodiment of the present invention;

FIG. 3 is a schematic diagram of a communication node reporting a quality failure of the communication node to a management node according to an embodiment of the present invention;

4 is a schematic diagram of a communication node reporting to a management node a receiving link interruption fault of the communication node provided by another embodiment of the present invention;

FIG. 5 is a schematic diagram of a management node detecting a failure of a communication node itself provided by an embodiment of the present invention;

Fig. 6 is a specific implementation structural diagram of a fault processing device in an Ethernet provided by an embodiment of the present invention.

Detailed ways

In the embodiment of the present invention, a management node is configured for the Ethernet link, and the management node receives the fault information reported by the communication nodes at both ends of the Ethernet link. The management node obtains the failure information of the Ethernet link and the communication nodes at both ends according to the failure information and the heartbeat detection information between the management node and the communication nodes at both ends of the Ethernet link.

In order to facilitate the understanding of the embodiments of the present invention, several specific embodiments will be taken as examples for further explanation below in conjunction with the accompanying drawings, and each embodiment does not constitute a limitation to the embodiments of the present invention.

Embodiment one

A schematic diagram of the principle of setting a management node for an Ethernet communication system provided in this embodiment is shown in FIG. 1 . In Fig. 1, the first communication node and the second communication node are two communication nodes establishing a business communication relationship, and the Ethernet full-duplex link between the first communication node and the second communication node can be regarded as a bidirectional two-way link. a simplex channel. Each channel consists of a RX, TX (Transmitter, transmitter) and a unidirectional link.

Configure a management node for the above-mentioned first communication node and second communication node, and the management node communicates with the first communication node and the second communication node respectively through different management dedicated channels, and the management dedicated communication channel is not controlled by the first communication node. 1. The influence of RX/TX failure on the second communication node, that is, in the case of TX/RX failure on the first communication node and the second communication node, the management node can still communicate with the first communication node through the management dedicated communication channel . The second communication node performs communication, and the communication includes performing heartbeat detection and the like. The above-mentioned management node performs heartbeat detection with the first communication node and the second communication node on a regular basis, according to the information reported by the first communication node and the second communication node through the management dedicated communication channel, and with the first communication node and the second communication node Heartbeat detection results between communication nodes, monitor the operating status of the first communication node and the second communication node and the status of the communication link between the first communication node and the second communication node, and determine the specific fault after the fault is detected reason. In addition, heartbeat detection may also be performed periodically between the first communication node and the second communication node, so as to detect whether the link between the first communication node and the second communication node fails.

In this embodiment, if the first communication node detects that its own RX has failed, the first communication node reports to the management node that its RX has failed, as shown in FIG. 2 . In this case, the first communication node cannot receive any data sent by the second communication node, and the heartbeat detection between the first communication node and the second communication node will fail. Then, the first communication node sends a fatal event notification to the second communication node, for example, Critiacl Event OAM PDU (fatal event operation, management, maintenance protocol data unit), to notify the second communication node of its RX failure.

The first communication node reports to the management node that the RX of the node fails through the management dedicated communication channel. Whether the heartbeat detection between is normal. After detecting that the heartbeat detection between the management node and the first communication node is normal, the management node determines the RX failure information of the first communication node, and the first communication node itself does not fail, and notifies the user of the RX failure information of the first communication node. accident details.

Embodiment two

In this embodiment, if the first communication node detects frame error and wrong symbol failure in its receiving direction, and detects that the heartbeat detection between the second communication node and the second communication node is normal, the first communication node reports its reception to the management node. A schematic diagram of a link quality failure is shown in Figure 3 . In this case, the first communication node may determine that neither the RX of the first communication node nor the TX of the second communication node is faulty, and the quality of the link in the receiving direction of the first communication node is problematic. Then, the first communication node sends a general event notification to the second communication node, so as to notify the second communication node that the receiving link quality of the first communication node is faulty.

The first communication node reports the failure of the receiving link quality of the node to the management node. After receiving the quality failure information of the receiving link of the node reported by the first communication node, the management node checks the management node and the first communication channel through the management dedicated communication channel. Whether the heartbeat detection between nodes is normal. After detecting that the heartbeat detection between the management node and the first communication node is normal, the management node determines that the first communication node receives link quality failure information, and the first communication node itself does not failure, and notify the user of the failure information of the receiving link quality of the first communication node.

Embodiment Three

In this embodiment, if the first communication node does not detect its own RX failure, but detects that the heartbeat detection with the second communication node fails, the first communication node reports to the management node that its receiving link is interrupted. The schematic diagram is shown in Figure 4. In this case, the first communication node can conclude that the link in its receive direction is broken. After the receiving link of the first communication node is interrupted, the first communication node will not receive any notification or data sent by the second communication node, and when the quality failure of the receiving link occurs at the first communication node, the first communication node detects Wrong frame and wrong symbol faults to own receive direction. Then, the first communication node sends a fatal event notification to the second communication node, so as to notify the second communication node that the receiving link of the first communication node is interrupted.

The first communication node reports to the management node the receiving link interruption fault of the node. After receiving the receiving link interruption fault information of the node reported by the first communication node, the management node checks the management node and the first communication node through the management dedicated communication channel. Whether the heartbeat detection between nodes is normal, after checking that the heartbeat detection between the management node and the first communication node and the second communication node is also normal, the management node determines that the receiving link interruption fault information of the first communication node, the second A communication node itself does not fail, and notifies the user of the receiving link interruption failure information of the first communication node.

Embodiment Four

In this embodiment, if the first communication node itself fails, causing the first communication node to be unable to perform any normal processing, the schematic diagram of the management node detecting the failure of the first communication node itself is shown in FIG. 5 . In this case, the second communication node will detect that the heartbeat detection with the first communication node fails, heartbeat loss occurs, and it cannot receive any notification or data sent by the first communication node, and the second communication node The node does not detect that its RX fails, so the second communication node sends a fatal event notification to the first communication node, but the first communication node cannot process the fatal event notification.

The second communication node reports to the management node that the heartbeat detection with the first communication node fails, and that it cannot receive any notification or data information sent by the first communication node. After the management node receives the above information reported by the second communication node, it detects whether the heartbeat between the management dedicated communication channel and the first communication node is normal. Since the first communication node cannot perform any normal processing at this time, therefore, The management node detects that the heartbeat detection between the management node and the first communication node is abnormal. Therefore, the management node determines that the first communication node itself has a failure, and the management node notifies the user that the first communication node itself has a failure.

The embodiment of the present invention also provides a fault processing device in the Ethernet. The device can be a management node in the Ethernet communication system, and the device communicates with different communication nodes in the Ethernet through different dedicated management channels. The above-mentioned management dedicated communication channel is not affected by the RX/TX failure on the communication node, that is, in the case of a TX/RX failure on the communication node, the device can still communicate with the communication node through the management dedicated communication channel, and the communication Including heartbeat detection, etc.

Its specific implementation structure is shown in Figure 6, which may specifically include:

Fault information receiving module 61, used for receiving the fault information reported by the communication node of the endpoint of the Ethernet link;

The fault processing module 62 is configured to obtain the communication information according to the fault information received by the fault information receiving module and the heartbeat detection information between the fault processing device and the communication node at the end point of the Ethernet link. Node failure information.

Wherein the fault processing module 62 specifically includes: at least one of a first processing module, a second processing module, a third processing module and a fourth processing module, wherein,

The first processing module 621 is configured to receive the receiver failure information of the communication node at one end of the Ethernet link reported by the communication node at one end of the Ethernet link, and determine the device and the communication node at the one end through a management dedicated communication channel If the heartbeat detection between them is normal, then determine the receiver failure information of the communication node at the one end, and notify the user of the receiver failure information of the communication node at the one end;

The second processing module 622 is configured to receive the received link quality failure information of the communication node at one end of the Ethernet link reported by the communication node at one end of the Ethernet link, and determine the connection between the device and the one end through a management dedicated communication channel If the heartbeat detection between the communication nodes is normal, then determine the receiving link quality failure information of the communication node at the one end, and notify the user of the receiving link quality failure information of the communication node at the one end;

The third processing module 623 is configured to receive the received link interruption fault information of the communication node at one end of the Ethernet link reported by the communication node at one end of the Ethernet link, and the communication node between the communication node at one end and the communication node at the other end heartbeat detection failure information, and determine that the heartbeat detection between the device and the communication node at the one end and the other end is normal through the management dedicated communication channel, then determine that the communication node at the one end receives the link interruption failure information, and Notifying the user of the failure information of the receiving link interruption of the communication node at the one end;

The fourth processing module 624 is configured to receive the heartbeat detection failure information reported by the communication node at one end of the Ethernet link between the communication node at the one end and the communication node at the other end, and the communication node at the one end does not receive notification or data information of the communication node at the other end, and determine the heartbeat detection failure information between the device and the communication node at the other end through the management dedicated communication channel, then determine the failure information of the communication node at the other end itself, And notify the user of the failure information of the communication node at the other end.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented through computer programs to instruct related hardware, and the programs can be stored in a computer-readable storage medium. During execution, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the storage medium may be a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM) or a random access memory (Random Access Memory, RAM), etc.

In summary, the embodiment of the present invention can effectively obtain and distinguish communication link failure and communication node failure information in Ethernet by setting a special management node and monitoring the status of the communication node through a special management communication channel, which facilitates Fast recovery from failures.

In the embodiment of the present invention, the management node can also notify the user of communication link failure and communication node failure information in the Ethernet.

The above is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present invention can easily think of changes or Replacement should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (5)

1. a fault handling method in Ethernet, is characterized in that, described method comprises: The management node receives the fault information reported by the communication node of the endpoint of the Ethernet link, the management node communicates with the communication node through a dedicated management channel, and periodically performs heartbeat detection with the communication node; The management node obtains the failure information of the communication node according to the failure information and the heartbeat detection information between the management node and the communication node at the end of the Ethernet link, specifically including: The management node receives the receiver failure information of the communication node at one end of the Ethernet link reported by the communication node at one end, and determines that the heartbeat detection between the management node and the communication node at one end is normal; The management node determines the receiver failure information of the communication node at the one end, and notifies the user of the receiver failure information of the communication node at the one end; or, The management node receives the heartbeat detection failure information between the communication node at one end and the communication node at the other end reported by the communication node at one end of the Ethernet link, and the communication node at the one end does not receive the communication at the other end node notification or data information, and determine heartbeat detection failure information between the management node and the communication node at the other end; The management node determines the failure information of the communication node at the other end, and notifies the user of the failure information of the communication node at the other end. 2. The method according to claim 1, wherein the management node obtains the communication node information according to the fault information and the heartbeat detection information between the management node and the communication node. fault information, including: The management node receives the received link quality fault information of the communication node at one end of the Ethernet link reported by the communication node at one end, and determines the heartbeat detection between the management node and the communication node at the one end normal; The management node determines the receiving link quality failure information of the communication node at the one end, and notifies the user of the receiving link quality failure information of the communication node at the one end. 3. The method according to claim 1, wherein the management node obtains the communication node information according to the failure information and the heartbeat detection information between the management node and the communication node. fault information, including: The management node receives the receiving link interruption fault information of the communication node at one end of the Ethernet link reported by the communication node at one end of the Ethernet link, and the heartbeat detection failure between the communication node at the one end and the communication node at the other end information, and determine that the heartbeat detection between the management node and the communication nodes at the one end and the other end is normal; The management node determines the receiving link interruption fault information of the communication node at the one end, and notifies the user of the receiving link interruption fault information of the communication node at the one end. 4. a fault processing device in Ethernet, is characterized in that, specifically comprises: The fault information receiving module is used to receive the fault information reported by the communication node of the endpoint of the Ethernet link; A fault processing module, configured to acquire fault information of the communication node according to the fault information received by the fault information receiving module and heartbeat detection information between the fault processing device and the communication node; The fault processing device includes a management node in the Ethernet communication system, the management node communicates with the communication node through a dedicated management channel, and regularly performs heartbeat detection with the communication node; The fault processing module specifically includes at least one of the following modules: The first processing module is used to receive the communication node receiver failure information reported by the communication node at one end of the Ethernet link, and determine that the heartbeat detection between the failure processing device and the communication node at the one end is normal, Then determine the receiver failure information of the communication node at the one end, and notify the user of the receiver failure information of the communication node at the one end; The fourth processing module is used to receive the heartbeat detection failure information between the communication node at one end and the communication node at the other end reported by the communication node at one end of the Ethernet link, and the communication node at the one end does not receive the other notification or data information of the communication node at one end, and determine the heartbeat detection fault information between the fault processing device and the communication node at the other end, then determine the fault information of the communication node itself at the other end, and notify the user The failure information of the communication node at the other end itself. 5. The fault processing device according to claim 4, wherein the fault processing module further comprises at least one of the following modules: The second processing module is configured to receive the received link quality fault information of the communication node at one end of the Ethernet link reported by the communication node at one end of the Ethernet link, and the communication node between the communication node at the one end and the communication node at the other end The heartbeat detection is normal information, and it is determined that the heartbeat detection between the fault processing device and the communication node at the one end is normal, then determine the receiving link quality failure information of the communication node at the one end, and notify the user of the fault at the one end Receive link quality failure information of the communication node; The third processing module is configured to receive the received link interruption fault information of the communication node at one end of the Ethernet link reported by the communication node at one end of the Ethernet link, and the communication node between the communication node at the one end and the communication node at the other end Heartbeat detection fault information, and determine that the heartbeat detection between the fault processing device and the communication node at the one end and the other end is normal, then determine the receiving link interruption fault information of the communication node at the one end, and notify the user of the failure information The receiving link interruption fault information of the communication node at one end. the

Images