CN101938365B - Fault handling method and device for Ethernet - Google Patents
Fault handling method and device for Ethernet Download PDFInfo
- Publication number
- CN101938365B CN101938365B CN200910088156A CN200910088156A CN101938365B CN 101938365 B CN101938365 B CN 101938365B CN 200910088156 A CN200910088156 A CN 200910088156A CN 200910088156 A CN200910088156 A CN 200910088156A CN 101938365 B CN101938365 B CN 101938365B
- Authority
- CN
- China
- Prior art keywords
- communication node
- node
- fault information
- fault
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 15
- 238000004891 communication Methods 0.000 claims abstract description 268
- 238000001514 detection method Methods 0.000 claims abstract description 49
- 238000012545 processing Methods 0.000 claims description 28
- 238000010586 diagram Methods 0.000 description 11
- 238000012423 maintenance Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000003672 processing method Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
Images
Landscapes
- Small-Scale Networks (AREA)
Abstract
The invention provides a fault handling method and a fault handling device for Ethernet. The method mainly comprises that: a management node receives fault information reported by communication nodes at two ends of an Ethernet link; the management node acquires the fault information of the Ethernet link and the communication nodes at two ends according to the fault information and the heartbeat detection information between the communication nodes at the two ends of the Ethernet link. In the embodiment of the invention, the special management node is set and a special management communication channel is used to monitor the states of the communication nodes, so the communication link fault information and the communication node fault information in the Ethernet can be acquired and differentiated effectively; and thus, quick fault clearing can be performed conveniently.
Description
Technical Field
The present invention relates to the field of ethernet communications technologies, and in particular, to a method and an apparatus for processing a fault in an ethernet network.
Background
With the continuous development of ethernet in metropolitan and wide area networks, operators pay more and more attention to OAM (Operations administration and maintenance) of devices and links of ethernet.
Existing OAM schemes focus on the management and maintenance of point-to-point ethernet links, providing a complete ethernet OAM solution. The OAM sublayer, as an optional sublayer of the MAC (Media Access Control) layer, provides an effective mechanism for monitoring the link operating state in case of validation, and can be applied to any full-duplex, point-to-point ethernet link, or analog point-to-point ethernet link.
In the existing OAM scheme, indication and location of link failure are performed by two types of notifications, fatal event notification and normal event notification.
The notification of the fatal event is realized by using a flag bit in an OAM PDU (Protocol Data Unit) s, and mainly includes:
link Fault: indicating a home PHY (Physical Layer Device) Rx (Receiver) failure (loss of peer link signal).
Dying Gasp: an unrecoverable home error occurs.
Critical Event: unknown critical faults occur.
The common event notification is implemented by using a TLV (Type-Length-Value) field in an OAM PDUs, and mainly includes:
error symbol period event: the number of erroneous symbols detected within a given time window exceeds a defined threshold.
Frame error event: the number of error frames detected within a given time window exceeds a defined threshold.
Error frame period event: the number of erroneous frames detected in a given number of received frames exceeds a defined threshold.
Error frame second event: the number of seconds of an erroneous frame detected within a certain number of seconds exceeds a defined threshold. A second interval is said to be an erroneous frame second when one or more erroneous frames are detected in frames received within the second interval.
The fatal event notification and the common event notification are mainly used for monitoring error events in receiving, and simultaneously, if the receiving device or equipment of the local terminal generates unrecoverable errors, the receiving device or equipment of the local terminal notifies the opposite terminal of the unrecoverable errors in the most effort.
In the process of implementing the present invention, the inventor finds that the above-mentioned prior art scheme for indicating and locating link failure through a fatal event notification and a general event notification has at least the following problems:
although this scheme can discover a failure of a receiving device on a communication node and a failure of a communication link, it does not specify how to notify a user of the discovered failure. And meanwhile, the condition of the fault of the communication node can not be identified. The communication node self fault means that core software or hardware in the communication node is in fault, so that the whole communication node cannot normally operate. And if the receiving device, the transmitting device, the receiving link or the transmitting link on the communication node fails, other parts on the communication node which do not fail can still work normally.
Disclosure of Invention
The embodiment of the invention provides a fault processing method and device in Ethernet.
The embodiment of the invention provides a fault processing method in an Ethernet, which comprises the following steps:
the management node receives fault information reported by a communication node of an end point of the Ethernet link;
and the management node acquires the fault information of the communication node according to the fault information and the heartbeat detection information between the management node and the communication node.
An embodiment of the present invention provides a fault processing apparatus in an ethernet network, including:
the fault information receiving module is used for receiving fault information reported by a communication node of an endpoint of the Ethernet link;
and the fault processing module is used for acquiring the fault information of the communication node 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.
It can be seen from the technical solutions provided by the embodiments of the present invention that, by setting a special management node and monitoring the state of the communication node through a special management communication channel, the embodiments of the present invention can effectively acquire and distinguish communication link failure and communication node failure information in the ethernet, thereby facilitating quick failure recovery.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a schematic diagram illustrating a principle of setting a management node for an ethernet full-duplex link according to an embodiment of the present invention;
fig. 2 is a schematic diagram of a communication node reporting to a management node that a receiver of the communication node fails according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating a communication node reporting a failure of a receiving link quality of the communication node to a management node according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a communication node reporting a failure of a receiving link interruption of the communication node to a management node according to another embodiment of the present invention;
fig. 5 is a schematic diagram of a management node detecting a failure of a communication node according to an embodiment of the present invention;
fig. 6 is a diagram of a specific implementation structure of a fault handling apparatus in an ethernet network according to an embodiment of the present invention.
Detailed Description
In the embodiment of the invention, an Ethernet link is configured with a management node, and the management node receives fault information reported by communication nodes at two ends of the Ethernet link. And the management node acquires the fault information of the Ethernet link and the communication nodes at the two ends according to the fault information and the heartbeat detection information between the management node and the communication nodes at the two ends of the Ethernet link.
For the convenience of understanding the embodiments of the present invention, the following description will be further explained by taking several specific embodiments as examples in conjunction with the drawings, and the embodiments are not to be construed as limiting the embodiments of the present invention.
Example one
The schematic diagram of the management node provided for the ethernet communication system in this embodiment is shown in fig. 1. In fig. 1, the first communication node and the second communication node are two communication nodes that establish a traffic communication relationship, and an ethernet full-duplex link between the first communication node and the second communication node can be regarded as two bidirectional simplex channels. Each channel consists of one RX, TX (Transmitter) and one unidirectional link.
The management node is configured to communicate with the first communication node and the second communication node through different dedicated management channels, the dedicated management channels are not affected by RX/TX faults on the first communication node and the second communication node, that is, in the case of TX/RX faults on the first communication node and the second communication node, the management node can still communicate with the first communication node and the second communication node through the dedicated management channels, and the communication includes heartbeat detection and the like. The management node performs heartbeat detection with the first communication node and the second communication node periodically respectively, monitors the running states of the first communication node and the second communication node and the communication link state between the first communication node and the second communication node according to the information reported by the first communication node and the second communication node through the management dedicated communication channel and the heartbeat detection result between the management node and the first communication node and between the management node and the second communication node, and judges a specific fault reason after detecting the fault. In addition, heartbeat detection may be performed between the first communication node and the second communication node periodically to detect whether a link between the first communication node and the second communication node has a failure.
In this embodiment, if the first communication node detects that its RX fails, the schematic diagram of the first communication node reporting to the management node that its RX fails is 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. The first communication node then sends a fatal Event notification, e.g., a criitiacl Event OAM PDU (fatal Event operations, administration, maintenance protocol data unit), to the second communication node to notify the second communication node of its RX failure.
The first communication node reports the RX failure of the first communication node to the management node through the special management communication channel, and after the management node receives the RX failure information of the first communication node reported by the first communication node, the management node checks whether the heartbeat detection between the first communication node and the first communication node is normal or not through the special management communication channel. After detecting that the heartbeat detection between the management node and the first communication node is normal, the management node determines the RX fault information of the first communication node, and the first communication node does not have a fault and informs the user of the RX fault information of the first communication node.
Example two
In this embodiment, if a failure of an error frame and an error symbol in the receiving direction of the first communication node is detected, and it is detected that the detection of the heartbeat with the second communication node is normal, a schematic diagram of reporting, by the first communication node, a failure of the receiving link quality to the management node is shown in fig. 3. In this case, the first communication node may determine that neither RX of the first communication node nor TX of the second communication node has failed, and that the link quality in the receiving direction of the first communication node has a problem. Then, the first communication node transmits a normal event notification to the second communication node to notify the second communication node of the reception link quality failure of the first communication node.
The first communication node reports the receiving link quality fault of the first communication node to the management node, after the management node receives the receiving link quality fault information of the first communication node reported by the first communication node, the management node checks whether heartbeat detection between the management node and the first communication node is normal through a management special communication channel, and after the heartbeat detection between the management node and the first communication node is detected to be normal, the management node determines the receiving link quality fault information of the first communication node, the first communication node does not have a fault, and informs a user of the receiving link quality fault information of the first communication node.
EXAMPLE III
In this embodiment, if the first communication node does not detect its RX failure, but detects that the heartbeat detection with the second communication node fails, a schematic diagram of the first communication node reporting its receive link failure to the management node is shown in fig. 4. In this case, the first communication node may infer a link outage in its receive direction. After the receiving link of the first communication node is interrupted, the first communication node will not receive any advertisement or data sent by the second communication node, and when the first communication node has a receiving link quality failure, the first communication node detects the error frame and error symbol failure in its own receiving direction. Then, the first communication node transmits a fatal event notification to the second communication node to notify the second communication node of the reception link interruption failure of the first communication node.
The first communication node reports the receiving link interruption fault of the first communication node to the management node, after the management node receives the receiving link interruption fault information of the first communication node reported by the first communication node, the management node checks whether heartbeat detection between the management node and the first communication node is normal or not through a management special communication channel, and after the heartbeat detection between the management node and the first communication node and between the management node and the second communication node are also normal, the management node determines the receiving link interruption fault information of the first communication node, the first communication node does not have a fault, and informs a user of the receiving link interruption fault information of the first communication node.
Example four
In this embodiment, if the first communication node itself fails, which results in that the first communication node cannot perform any normal processing, a schematic diagram of the management node detecting that the first communication node itself fails is shown in fig. 5. In this case, the second communication node may detect that the heartbeat detection between the second communication node and the first communication node is failed, the heartbeat is lost, and the second communication node cannot receive any notification or data sent by the first communication node, and the second communication node does not detect that its RX is failed, so the second communication node sends the fatal event notification to the first communication node, but the first communication node cannot process the fatal event notification.
And the second communication node reports the heartbeat detection between the second communication node and the first communication node to the management node, and fails to receive any notice or data information sent by the first communication node. After receiving the information reported by the second communication node, the management node detects whether the heartbeat detection between the management node and the first communication node is normal through the management dedicated communication channel. Then, the management node judges that the first communication node itself has a failure, and notifies the user that the first communication node itself has a failure.
The embodiment of the invention also provides a fault processing device in the Ethernet, which can be a management node in an Ethernet communication system and is respectively communicated with different communication nodes in the Ethernet through different management special channels. The management-dedicated communication channel is not affected by RX/TX failure at the communication node, i.e. in case of TX/RX failure at the communication node, the device may still communicate with the communication node via the management-dedicated communication channel, including performing heartbeat detection, etc.
The specific implementation structure is shown in fig. 6, and may specifically include:
a fault information receiving module 61, configured to receive fault information reported by a communication node of an endpoint of an ethernet link;
and a fault processing module 62, configured to obtain 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 apparatus and the communication node of the endpoint of the ethernet link.
The fault handling 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,
a first processing module 621, configured to receive receiver failure information of a communication node at one end of the ethernet link, where the receiver failure information is reported by the communication node at the one end of the ethernet link, and determine that heartbeat detection between the apparatus and the communication node at the one end is normal through a management dedicated communication channel, determine the receiver failure information of the communication node at the one end, and notify a user of the receiver failure information of the communication node at the one end;
a second processing module 622, configured to receive received link quality failure information of a communication node at one end of the ethernet link, where the received link quality failure information is reported by the communication node at the one end of the ethernet link, and if it is determined that heartbeat detection between the apparatus and the communication node at the one end is normal through a management dedicated communication channel, determine the received link quality failure information of the communication node at the one end, and notify a user of the received link quality failure information of the communication node at the one end;
a third processing module 623, configured to receive, from the communication node at one end of the ethernet link, received link interruption fault information of the communication node at the one end, and heartbeat detection fault information between the communication node at the one end and the communication node at the other end, and determine, by managing a dedicated communication channel, that heartbeat detection between the apparatus and the communication nodes at the one end and the other end is normal, determine the received link interruption fault information of the communication node at the one end, and notify a user of the received link interruption fault information of the communication node at the one end;
a fourth processing module 624, configured to receive heartbeat detection fault information between the communication node at one end of the ethernet link and the communication node at the other end, which is reported by the communication node at the one end of the ethernet link, and the notification or data information that the communication node at the one end does not receive the communication node at the other end, and determine heartbeat detection fault information between the apparatus and the communication node at the other end through a management dedicated communication channel, determine fault information of the communication node at the other end itself, and notify fault information of the communication node at the other end itself to a user.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
In summary, the embodiment of the present invention sets the special management node, and monitors the state of the communication node through the special management communication channel, so as to effectively obtain and distinguish the communication link failure and the communication node failure information in the ethernet, thereby facilitating fast failure recovery.
The embodiment of the invention can also inform the user of the communication link failure and the communication node failure information in the Ethernet through the management node.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (5)
1. A method for fault handling in an ethernet network, the method comprising:
the method comprises the steps that a management node receives fault information reported by a communication node of an end point of an Ethernet link, the management node communicates with the communication node through a management special channel, and the management node regularly performs heartbeat detection with the communication node;
the acquiring, by the management node, the fault information of the communication node according to the fault information and heartbeat detection information between the management node and the communication node of the endpoint of the ethernet link specifically includes:
the management node receives the receiver fault information of the communication node at one end reported by the communication node at the other end of the Ethernet link, and determines that the heartbeat detection between the management node and the communication node at the other end is normal;
the management node determines receiver fault information of the communication node at the one end and notifies the receiver fault information of the communication node at the one end to a user;
or,
the management node receives heartbeat detection fault 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 determines the heartbeat detection fault information between the management node and the communication node at the other end, wherein the communication node at one end does not receive the notification or the data information of the communication node at the other end;
and the management node determines the self fault information of the communication node at the other end and informs the self fault information of the communication node at the other end to a user.
2. The method according to claim 1, wherein the acquiring, by the management node, the fault information of the communication node according to the fault information and heartbeat detection information between the management node and the communication node specifically includes:
the management node receives the received link quality fault information of the communication node at one end reported by the communication node at the other end of the Ethernet link, and determines that the heartbeat detection between the management node and the communication node at the other end is normal;
and the management node determines the receiving link quality fault information of the communication node at one end and informs the receiving link quality fault information of the communication node at one end to a user.
3. The method according to claim 1, wherein the acquiring, by the management node, the fault information of the communication node according to the fault information and heartbeat detection information between the management node and the communication node specifically includes:
the management node receives the received link interruption fault information of the communication node at one end reported by the communication node at the other end of the Ethernet link and the heartbeat detection fault information between the communication node at one end and the communication node at the other end, and determines that the heartbeat detection between the management node and the communication nodes at one end and the other end is normal;
and the management node determines the receiving link interruption fault information of the communication node at one end and informs the receiving link interruption fault information of the communication node at one end to a user.
4. A fault handling apparatus in an ethernet network, comprising:
the fault information receiving module is used for receiving fault information reported by a communication node of an endpoint of the Ethernet link;
the fault processing module is used for acquiring the fault information of the communication node 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;
the fault processing device comprises a management node in an Ethernet communication system, wherein the management node is communicated with the communication node through a management special channel and is used for periodically carrying out heartbeat detection with the communication node;
the fault processing module specifically includes at least one of the following modules:
a first processing module, configured to receive the failure information of the communication node receiver reported by the communication node at one end of the ethernet link, and determine that heartbeat detection between the failure processing apparatus and the communication node at the one end is normal, determine the receiver failure information of the communication node at the one end, and notify a user of the receiver failure information of the communication node at the one end;
a fourth processing module, configured to receive heartbeat detection fault information between the communication node at one end of the ethernet link and the communication node at the other end, where the heartbeat detection fault information is reported by the communication node at the one end, and the heartbeat detection fault information between the communication node at the one end and the communication node at the other end is not received by the communication node at the one end, and determine the heartbeat detection fault information between the fault processing apparatus and the communication node at the other end, determine the fault information of the communication node at the other end itself, and notify the fault information of the communication node at the other end itself to a user.
5. The fault handling device of claim 4, wherein the fault handling module further comprises at least one of:
a second processing module, configured to receive received link quality failure information of the communication node at one end of the ethernet link, which is reported by the communication node at the one end of the ethernet link, and heartbeat detection normal information between the communication node at the one end and the communication node at the other end, and determine that heartbeat detection between the failure processing apparatus and the communication node at the one end is normal, determine received link quality failure information of the communication node at the one end, and notify a user of the received link quality failure information of the communication node at the one end;
a third processing module, configured to receive receiving link interruption fault information of the communication node at one end of the ethernet link, which is reported by the communication node at the one end of the ethernet link, and heartbeat detection fault information between the communication node at the one end and the communication node at the other end, and determine that heartbeat detection between the fault processing apparatus and the communication nodes at the one end and the other end is normal, determine receiving link interruption fault information of the communication node at the one end, and notify a user of the receiving link interruption fault information of the communication node at the one end.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910088156A CN101938365B (en) | 2009-07-03 | 2009-07-03 | Fault handling method and device for Ethernet |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910088156A CN101938365B (en) | 2009-07-03 | 2009-07-03 | Fault handling method and device for Ethernet |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101938365A CN101938365A (en) | 2011-01-05 |
| CN101938365B true CN101938365B (en) | 2012-10-03 |
Family
ID=43391514
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910088156A Active CN101938365B (en) | 2009-07-03 | 2009-07-03 | Fault handling method and device for Ethernet |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101938365B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5426782B2 (en) * | 2011-02-08 | 2014-02-26 | 三菱電機株式会社 | Communication system, communication line switching method, and master station apparatus |
| CN103684929B (en) * | 2013-12-27 | 2017-01-25 | 乐视云计算有限公司 | System and method for monitoring server status |
| CN104885407A (en) * | 2013-12-31 | 2015-09-02 | 华为技术有限公司 | Network function virtualisation NFV fault management apparatus, device, and method |
| CN106452957B (en) * | 2016-09-30 | 2019-09-10 | 邦彦技术股份有限公司 | Heartbeat detection method and node system |
| CN107347019A (en) * | 2017-04-20 | 2017-11-14 | 武汉迈力特通信有限公司 | The apparatus and method of MSTP system ethernet link failure fast transfers |
| CN112118145A (en) * | 2019-06-19 | 2020-12-22 | 北京沃东天骏信息技术有限公司 | Node state monitoring method, control device and monitoring device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1653686A1 (en) * | 2004-11-01 | 2006-05-03 | Lucent Technologies Inc. | Softrouter feature server |
| CN101141327A (en) * | 2007-10-11 | 2008-03-12 | 中兴通讯股份有限公司 | Method for detecting network node abnormality |
| CN101252500A (en) * | 2008-04-16 | 2008-08-27 | 杭州华三通信技术有限公司 | Intersect looped network, node and realizing method of random topology intersect looped network |
-
2009
- 2009-07-03 CN CN200910088156A patent/CN101938365B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1653686A1 (en) * | 2004-11-01 | 2006-05-03 | Lucent Technologies Inc. | Softrouter feature server |
| CN101141327A (en) * | 2007-10-11 | 2008-03-12 | 中兴通讯股份有限公司 | Method for detecting network node abnormality |
| CN101252500A (en) * | 2008-04-16 | 2008-08-27 | 杭州华三通信技术有限公司 | Intersect looped network, node and realizing method of random topology intersect looped network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101938365A (en) | 2011-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9237092B2 (en) | Method, apparatus, and system for updating ring network topology information | |
| CN101938365B (en) | Fault handling method and device for Ethernet | |
| EP1832044B1 (en) | Wireless communication path management methods and systems | |
| EP2456127B1 (en) | Method, system and apparatus for diagnosing physical downlink failure | |
| US20070115837A1 (en) | Scalable Selective Alarm Suppression for Data Communication Network | |
| US20090154337A1 (en) | Protection switching method based on change in link status in ethernet link aggregation sublayer | |
| JP2006229477A (en) | Failure detector | |
| CN107517117B (en) | IP layer OAM (operation administration and maintenance) alarm method and device and network node | |
| US8804491B2 (en) | Recovery method for ring-based network | |
| JP2013512615A (en) | Method and apparatus for supporting inconsistency detection | |
| CN108259068B (en) | Photovoltaic system safety control method, equipment and system | |
| US20080002569A1 (en) | Method and apparatus for identifying a fault in a communications link | |
| CN107431655B (en) | Method and apparatus for fault propagation in segment protection | |
| US7450519B2 (en) | Auto-negotiation monitor system, repeating-transmission apparatus, and auto-negotiation monitor method used therefor | |
| CN102340407B (en) | Protection switching method and system | |
| CN101599882B (en) | Method and device for achieving point-to-point far end loopback of Ethernet | |
| CN112825501B (en) | Signal degradation processing method, device and system | |
| JP2005268889A (en) | Transmission path switching system and operating method of the transmission path switching system | |
| CN101247287B (en) | Fault detection method of operation management maintenance mechanism | |
| US20120069970A1 (en) | Systems and methods of masking non-service affecting alarms in a communication system | |
| CN113300908B (en) | Link monitoring method and system based on unidirectional network boundary equipment | |
| JP5475706B2 (en) | Monitoring device, communication device, and network monitoring method | |
| JP2012080426A (en) | Communication device, communication system, communication method and communication program | |
| JP6301750B2 (en) | Relay device | |
| CN116488998A (en) | Network protection switching method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |