CN108259289B

CN108259289B - Loop network abnormity protection method and device

Info

Publication number: CN108259289B
Application number: CN201611244908.2A
Authority: CN
Inventors: 任莉; 潘德志; 许培
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-12-29
Filing date: 2016-12-29
Publication date: 2021-01-15
Anticipated expiration: 2036-12-29
Also published as: CN108259289A

Abstract

The embodiment of the application discloses a method and a device for protecting looped network abnormity, wherein the method comprises the following steps: the first node determines that a first port of the first node exits an Ethernet ring protection switching protocol (ERPS) ring, wherein the exiting ERPS ring is used for indicating that the first port does not process an ERPS protocol message in the state of exiting the ERPS ring; the first node blocking a second port, the second port being a port of the first node on the ERPS ring, the second port being different from the first port; the first node sends a first termination message to a second node, wherein the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first termination message is used for indicating that a first port of the first node exits the ERPS ring. By adopting the method and the device, the problem that some nodes can not normally communicate in the ERPS ring in the prior art can be solved.

Description

Loop network abnormity protection method and device

Technical Field

The present application relates to the field of network communication technologies, and in particular, to a method and an apparatus for protecting a ring network from an abnormality.

Background

The Ethernet Ring Protection Switching (ERPS) protocol is a Ring Protection protocol developed by the International Telecommunications Union (ITU), also called g.8032. The protocol is a link layer protocol specially applied to the Ethernet ring network, can prevent broadcast storm caused by a data loop when the Ethernet ring network is complete, is a protocol for breaking the loop by the Ethernet link layer, and can quickly recover communication among nodes on the Ethernet ring network when one link on the Ethernet ring network is disconnected.

The ERPS takes an ERPS ring as a basic unit and comprises a plurality of nodes, and the ERPS ring is provided with a ring network Protection link RPL (Ring Protection Link), namely two end ports on the RPL link are blocked, a ring network Protection link main node RPL Owner port and a ring network Protection link neighbor node RPL neighbor port are blocked, and other common ports are controlled, so that the states of the ports are switched between Forwarding (Forwarding) and blocking (distributing), and the purpose of eliminating the ring is achieved. However, in the prior art, only the processing mode of the node or the link under the normal condition and the fault condition is described, and other abnormal conditions are not described in relation to the node or the link, so that the node may not be able to normally communicate under some special conditions.

Disclosure of Invention

The embodiment of the application provides a method and a device for protecting a looped network from abnormality, which can solve the problem that some nodes in an ERPS loop in the prior art can not normally communicate.

In a first aspect, an embodiment of the present application provides a method for protecting a ring network from an exception, which may include:

a first node determines that a first port of the first node exits an ethernet ring protection switching protocol (ERPS) ring, wherein the exiting ERPS ring is used for indicating that the first port does not process an ERPS protocol message in the state of exiting the ERPS ring, and the first port is a port of the first node on the ERPS ring; the first node blocking a second port, the second port being a port of the first node on the ERPS ring, the second port being different from the first port; the first node sends a first termination message to a second node, wherein the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first termination message is used for indicating that a first port of the first node exits the ERPS ring. By defining the node exiting the ERPS ring and stipulating the exiting processing (such as sending the terminating message) of the node under the condition of exiting the ERPS ring, other nodes in the ERPS ring can sense the exit of the node and can carry out related setting according to the terminating message so as to avoid the problem of abnormal node communication possibly caused when the subsequent exiting node rejoins the ERPS ring.

With reference to the first aspect, in a first possible implementation manner, the determining, by the first node, that the first port of the first node exits an ethernet ring protection switching protocol ERPS ring specifically includes: the first node determines that a first port of the first node is ready to exit an Ethernet ring protection switching protocol (ERPS) ring. By implementing the embodiment of the application, the blocking of the second port and the sending of the first terminating message can be performed before the first port exits, so as to avoid a loop formed by the port exiting the ERPS loop prematurely.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the first terminating packet includes a MAC address of the first node. Through the MAC address of the node and the flow path of the terminating packet, the second node can specifically determine the source of the first terminating packet, that is, the specific node and port.

With reference to the first aspect, or with reference to the first possible implementation manner of the first aspect, or with reference to the second possible implementation manner of the first aspect, in a third possible implementation manner, the ERPS ring includes a ring protection link RPL, and ports at two ends of the RPL are a ring protection link master node RPL owner port and a ring protection link neighbor node RPL neighbor port. By implementing the embodiment of the application, the occurrence of an island situation can be effectively avoided under the condition that the ERPS ring comprises the RPL, and abnormal node communication is prevented.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the method further includes: and if the second port of the first node exits the ERPS ring, sending a second termination message to the second node, wherein the second termination message is used for indicating the second port of the first node to exit the ERPS ring.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner, the second terminating packet includes a media access control MAC address of the second node.

In a second aspect, an embodiment of the present application provides a method for protecting a ring network from an exception, which may include:

a second node receives a first termination message, wherein the first termination message is used for indicating a first port of the first node to exit an Ethernet ring protection switching protocol (ERPS) ring, the first port is a port of the first node on the ERPS ring, the first node and the second node are both on the ERPS ring, and the first node and the second node are different nodes; and if the second node has a blocked port on the ERPS ring, switching the state of the blocked port into a forwarding state. By implementing the embodiment of the application, the feedback that other nodes on the ERPS ring where the first node is located need to do for the node to exit (for example, switching the currently blocked port to the forwarding state) is defined under the condition that the first port of the first node exits, so that the problem that the second node may not normally communicate due to incapability of sensing under the condition that the port on the ERPS ring is rejoined after exiting can be effectively avoided.

With reference to the second aspect, in a first possible implementation manner, the first terminating packet includes a media access control MAC address of the first node; after the second node receives the first terminating message, the method further includes: the second node receives a second terminate message, where the second terminate message is used to indicate that a second port of the first node exits the ERPS ring, the second port is a port of the first node on the ERPS ring, and the second terminate message includes a Media Access Control (MAC) address of the second node; and if the second node judges that the MAC addresses in the second terminal message and the first terminal message are the same, controlling to execute a port initialization process. By implementing the embodiment of the application, the port initialization process is executed under the condition that the two ports on the same node are both quitted, so that the problem of ERPS looping caused under the condition that the two ports on the same node are both quitted can be avoided, and the broadcast storm is avoided.

With reference to the second aspect, or with reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, after the receiving, by the second node, the first terminating packet, the method further includes: and the second node adjusts the port parameters so that the ERPS ring is switched into a pending state. By implementing the embodiment of the application, the first terminating message can be received at the second node and is firstly adjusted to be in a pending state, so that the port can process more kinds of events.

With reference to the second aspect, or with reference to the first possible implementation manner of the second aspect, or with reference to the second possible implementation manner of the second aspect, in a third possible implementation manner, the ERPS ring includes a ring protection link RPL, and ports at two ends of the RPL are a ring protection link master node RPL owner port and a ring protection link neighbor node RPL neighbor port.

In a third aspect, an embodiment of the present application provides a ring network anomaly protection device, which may include:

a processing module, configured to determine that a first port of a first node exits an ethernet ring protection switching protocol (ERPS) ring, where the exiting ERPS ring is used to indicate that the first port does not process an ERPS protocol packet in a state of exiting the ERPS ring, and the first port is a port of the first node on the ERPS ring;

the processing module is further configured to block a second port, where the second port is a port of the first node on the ERPS ring, and the second port is different from the first port;

a sending module, configured to send a first termination message to a second node, where the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first termination message is used to indicate that a first port of the first node exits the ERPS ring.

With reference to the third aspect, in a first possible implementation manner, the processing module is configured to determine that the first port of the first node exits the ethernet ring protection switching protocol ERPS ring, and specifically:

determining that the first port of the first node is ready to exit an Ethernet ring protection switching protocol (ERPS) ring.

With reference to the third aspect, or with reference to the first possible implementation manner of the third aspect, in a second possible implementation manner, the first terminating packet includes a media access control MAC address of the first node.

With reference to the third aspect, or with reference to the first possible implementation manner of the third aspect, or with reference to the second possible implementation manner of the third aspect, in a third possible implementation manner, the ERPS ring includes a ring protection link RPL, and ports at two ends of the RPL are a ring protection link master node RPL owner port and a ring protection link neighbor node RPL neighbor port.

With reference to the third aspect, or with reference to the first possible implementation manner of the third aspect, or with reference to the second possible implementation manner of the third aspect, or with reference to the third possible implementation manner of the third aspect, in a fourth possible implementation manner, the sending module is further configured to:

and if the second port of the first node exits the ERPS ring, sending a second termination message to the second node, wherein the second termination message is used for indicating the second port of the first node to exit the ERPS ring.

With reference to the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner, the second terminating packet includes a media access control MAC address of the second node.

In a fourth aspect, an embodiment of the present application provides a looped network anomaly protection device, which may include:

a receiving module, configured to receive a first terminate message, where the first terminate message is used to indicate that a first port of a first node exits an ethernet ring protection switching protocol (ERPS) ring, the first port is a port of the first node on the ERPS ring, the first node and the second node are both on the ERPS ring, and the first node and the second node are different nodes;

and the processing module is used for switching the state of the blocked port into a forwarding state if the port of the second node on the ERPS ring has the blocked port.

With reference to the fourth aspect, in a first possible implementation manner, the first terminating packet includes a media access control MAC address of the first node;

the receiving module is further configured to:

after receiving a first termination message, receiving a second termination message, where the second termination message is used to indicate that a second port of the first node exits the ERPS ring, the second port is a port of the first node on the ERPS ring, and the second termination message includes a media access control MAC address of the second node;

the processing module is further configured to control execution of a port initialization procedure if the second node determines that the MAC addresses in the second terminating message and the first terminating message are the same.

With reference to the fourth aspect, or with reference to the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the processing module is further configured to:

after receiving the first terminating message, adjusting a port parameter to switch the ERPS ring to a pending state.

With reference to the fourth aspect, or with reference to the first possible implementation manner of the fourth aspect, or with reference to the second possible implementation manner of the fourth aspect, in a third possible implementation manner, the ERPS ring includes a ring protection link RPL, and ports at two ends of the RPL are a ring protection link master node RPL owner port and a ring protection link neighbor node RPL neighbor port.

In a fifth aspect, the present application provides a node device, where the node device includes a processor, and the processor is configured to support the node device to execute a corresponding function in the ring network exception protection method provided in the first aspect. The node device may also include a memory, coupled to the processor, that retains program instructions and data necessary for the node device. The node device may also include a communication interface for the node device to communicate with other devices or a communication network.

In a sixth aspect, the present application provides a node device, where the node device includes a processor, and the processor is configured to support the node device to execute a corresponding function in the method for protecting a ring network exception provided in the second aspect. The node device may also include a memory, coupled to the processor, that retains program instructions and data necessary for the node device. The node device may also include a communication interface for the node device to communicate with other devices or a communication network.

In a seventh aspect, the present application provides a computer storage medium for storing computer software instructions for the ring network anomaly protection device provided in the third aspect, which includes a program for executing the above aspects.

In an eighth aspect, the present application provides a computer storage medium for storing computer software instructions for the ring network anomaly protection device provided in the fourth aspect, which includes a program for executing the above-mentioned aspects.

In a ninth aspect, the present application provides a computer program, where the computer program includes instructions, and when the computer program is executed by a computer, the computer may execute the flow in the network slice resource mapping method in any one of the first aspect.

In a tenth aspect, the present application provides a computer program, where the computer program includes instructions, when the computer program is executed by a computer, the computer may execute the flow in the network slice resource mapping method in any one of the second aspects.

The embodiment of the application has the following beneficial effects:

according to the method and the device, under the condition that the first node determines that the first port of the first node exits the ERPS ring, the first termination message is sent to other second nodes except the first node on the ERPS ring, so that the other nodes can conveniently carry out state switching on the current blocked port of the first node according to the termination message sent by the first node, and the situation that the nodes cannot normally communicate under a special condition is avoided. That is, in the present application, by defining that a node exits an ERPS ring, and defining exit processing (for example, sending a near-end message) performed by the node when the node exits the ERPS ring, and defining feedback (for example, switching a currently blocked port to a forwarding state) that the node needs to exit to other nodes on the ERPS ring where the node is located, the problem that the node cannot normally communicate due to the inability of other nodes to sense when the port on the ERPS ring exits and rejoins is effectively avoided.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram of a ring network model provided in an embodiment of the present application;

fig. 2 is a schematic flowchart of a method for protecting a ring network from an anomaly according to an embodiment of the present application;

fig. 3 is a schematic flowchart of another ring network anomaly protection method provided in the embodiment of the present application;

fig. 4 is a schematic structural diagram of a looped network anomaly protection device provided in an embodiment of the present application;

fig. 5 is a schematic structural diagram of another ring network anomaly protection device provided in the embodiment of the present application;

fig. 6 is a schematic structural diagram of a node device according to an embodiment of the present application.

Detailed Description

The embodiments of the present application will be described below with reference to the drawings.

The terms "first," "second," "third," and "fourth," etc. in the description and claims of this application and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.

Hereinafter, some terms in the present application are explained to facilitate understanding by those skilled in the art.

1) The ERPS ring is formed by a group of interconnected two-layer switching devices configured with the same Virtual Local Area Network (VLAN), and is a basic unit of the ERPS protocol. One ERPS ring physically corresponds to one ring-connected ethernet topology.

2) And the nodes, namely the two-layer switching equipment added into the ERPS ring. Each node has and only two ports to join the same ERPS ring. The node may be a routing device or a switching device.

3) The link between the main node and the neighbor node is a ring network Protection link, and when the ERPS ring is normal, the port states of the ports at the two ends of the RPL are blocking states, which are called blocking ports, and are used for blocking data message transmission to prevent the ring, and the port states of other nodes connected with the ERPS ring are forwarding states; when there is node failure in the ERPS ring, the port states of the ports at the two ends of the RPL are switched to a forwarding state for transmitting data messages.

4) Port roles, the port roles specified in the ERPS protocol are mainly three types of RPL owner port, RPL neighbor port, and normal port.

5) RPL owner port, only RPL owner for an ERPS ring, is prevented from creating a loop in the ERPS ring by blocking the RPL owner port, depending on the user configuration. When the equipment where the RPL owner is located receives the fault message and learns that other nodes or links on the ERPS ring have faults, the equipment can automatically release the RPL owner port, and the port recovers the receiving and sending of the flow, thereby ensuring that the flow cannot be interrupted. The link where the RPL owner is located is the ring protection link RPL.

6) RPL neighbor port, RPL neighbor port refers to a port directly connected to an RPL inner port. Normally, both the RPL owner port and the RPL neighbor port are blocked to prevent loop generation. When the ERPS ring fails, both the RPL owner port and the RPL neighbor port are released. Introducing the role of the RPL neighbor port can reduce the number of times that a node on an ERPS ring refreshes a Forwarding DataBase (FDB) entry when a link where the RPL is located fails.

7) Normal ports, in the ERPS ring, the ports other than RPL owner and RPL neighbor are normal ports. The common port is responsible for monitoring the link state of the ERPS protocol directly connected with the common port, and informing other ports of the change message of the link state in time.

8) And brother ports, wherein a plurality of ports are arranged on the same node, but in the same ERPS ring, each node has and only has two ports to join the same ERPS ring (G.8032 ring), and the two ports are mutually called brother ports.

9) Idle State (Idle State), ITU-T g.8032 defines 2 states of Idle State (Idle State) and protection State (protection State), Idle State (Idle State, hereinafter, abbreviated as Idle State) is a normal operating State when there is no failure, and protection State is a State in which switching protection occurs after a link failure is detected. Under normal conditions, an ERPS ring is in an idle state, all nodes are connected in a ring mode, and an ERPS protocol ensures that the ring cannot be formed by blocking an RPL.

First, it should be noted that the port exit ERPS ring event defined in the present application specifically means that the port disables the ERPS, receives but does not process an ERPS protocol packet any more, and does not participate in ERPS protocol calculation any more, after the port exits, the state of the port is restored to a default state, and the default state is a forwarding state or a blocking state, and specifically, the factory setting or the manual setting of the node device is considered, and if the default state is the forwarding state, data can be transmitted. It should be noted that, in a normal state before exiting the ERPS ring, a port may be set to forward or block according to a state calculated by the ERPS protocol, so as to achieve the purpose of eliminating a loop. If a port exits, the sibling port of the exiting port needs to be switched or kept in a blocking state.

It should be emphasized that, when the ERPS ring is in the Idle state, if the RPL owner port on the ERPS ring is not exited, a No Request/RPL Blocked (NRRB) message is sent to other nodes in the ring at a fixed time interval (e.g. 5s) as a cycle, which indicates that all current links of the ERPS ring are normal. Therefore, when other nodes in the ERPS ring receive the NRRB message, it is known that the RPL Owner port in the ERPS ring is currently in a normal blocking state, and thus unnecessary blocking ports are not needed, and therefore, if a blocking port is present on a common port, the RPL Owner port is immediately released after receiving the NRRB message, and the RPL Owner port is switched to a forwarding state. The NRRB message belongs to a Ring Automatic Protection Switching (RAPS) message.

The releasing of the port mentioned in the present application refers to switching the state of the port from the blocking state to the forwarding state.

In order to facilitate understanding of the embodiment of the present application, based on the above, it is first necessary to describe and analyze an application scenario corresponding to the technical problem solved by the embodiment of the present application. Fig. 1 is a schematic diagram of a ring network model provided in an embodiment of the present application, please refer to fig. 1, where in the structure of the ERPS ring shown in fig. 1, the ring 1 is configured as a primary ring (i.e., a closed ring), the node C is configured as a primary node of the ring 1, the node D is configured as a neighbor node of the ring 1, and a link between the node C and the node D is an RPL of the ring 1. Port 1 of node C on RPL and port 2 of node D on RPL are blocking ports, RPL owner port and RPL neighbor port, respectively. In the prior art, when the RPL on the ERPS Ring is configured, that is, the blocking port on the ERPS Ring is fixed to the RPL ower port and the RPL neighbor port, if the ERPS Ring is in the Idle state and the RPL ower port or the RPL neighbor port does not acquire the exit and join information of the normal node, the Ring network Automatic Protection Switching No Request (R-APS NR) packet sent by the normal node on the ERPS Ring is not processed, so that the blocking state is always kept unchanged. Based on this, if the ERPS ring is in the Idle state, in some scenarios, the drop-out of the node may be added to form an "island," as follows:

the first situation is as follows:

(1) under the condition that the ring 1 is in the Idle state, the port 2 on the node C exits first, and the port 1 on the node B exits later, at this time, a sibling port of the port 2 on the node C, that is, an RPL owner port (port 1), is blocked, a sibling port corresponding to the port 1 on the node B, that is, a port 2, is blocked, and at this time, one of the port 1 of the node C and the port 2 of the node B is selected to be blocked, which is assumed to be the port 2 of the node B;

(2) at this time, the port 2 on the node D is still in a blocking state because the exit of the node port is not sensed;

(3) when the port 2 on the node C and the port 1 on the node B are successively added to the ERPS ring, because of the addition of the ports, an nr (no request) message needs to be retransmitted between the node C and the node B to select a blocked port, and it is assumed that the blocked port is set on the port 2 on the node B having a larger MAC address according to the size of the MAC address. It should be noted that, because the RPL owner port responsible for sending the NRRB packet in (1) is recalculated and blocked in (1), it does not send the NRRB packet to other ports any more, so port 2 on the node B is not released at this time, and remains blocked;

(4) therefore, the ERPS ring has two blocking ports, i.e., the RPL neighbor port on the node D and the port 2 on the node B, and at this time, the data traffic packet cannot reach the node C from a → B or from a → D, and therefore, the node C is isolated, becomes an "island," and cannot perform normal communication. Manual intervention by the user or waiting for the recovery timer WTR to time out (minimum 1min, default 5mins) is required to recover back to the situation where it is blocked only by the RPL owner port and the RPL neighbor port.

The reason for the above exception is that in the existing ERPS mechanism, the node exit event is undefined, and the related operations and processes after the node exits the ERPS ring are undefined. Therefore, when the port of the node exits and joins the ring again, other nodes cannot know the information, and therefore, the nodes a and D in the ERPS ring cannot sense the exit of the port 2 on C and the port 1 on B. And because the port exit defined in the present application is not equal to the port failure in the prior art, that is, if the port default exit state is set to the forwarding state, the port exit will also continue to pass through the data, and only the processing of the ERPS protocol packet is not performed. Therefore, the "false" that the current ERPS ring has no fault is caused to other nodes on the ERPS ring, so in case 1 in this application, the RPL neighbor port also "considers" itself to be in the Idle state, and therefore does not process the NR packet sent by other nodes, and therefore the RPL owner port continues to maintain the blocking state. Meanwhile, a blocked port is recalculated and determined between the ordinary nodes with the ports exiting or joining, and because the RPL neighbor port in case 1 is recalculated and blocked in (1), the NRRB message cannot be sent out, so the recalculated and determined blocked port on the ordinary node cannot be released, at this time, two blocked ports may be formed on different links, and thus the node between the two blocked ports cannot perform normal communication with other nodes on the ERPS ring, that is, the data message cannot be sent to the node, thereby forming an island.

Furthermore, in addition to the above case one, the following cases may also be included with the above "islanding" problem.

Case two:

(1) when the ring 1 is in the Idle state, the port 1 on the node B exits first, and the port 2 on the node C exits before the time when the port 1 on the node B has not received the NRRB packet sent by the port 1(RPL owner port) of the node C.

(2) (3) and (4) similarly to the case of case 1 described above, please refer to the description in case 1.

In this case two, port 2 of node C exits before its sibling port RPL ower port has not yet reached to send the NRRB message, so that the RPL ower port cannot continue to send the NRRB message because its sibling port 2 exits and is recalculated and blocked before the NRRB message is not sent, and the blocked port recalculated and determined on the normal node cannot be released, and finally two blocked ports that are not on the same link may be formed due to exit and join of the node, resulting in the islanding problem.

In summary, an "islanding" situation can occur when the following conditions are met: one is as follows: the ERPS ring is in idle state, namely no node on the ERPS ring fails; the second step is as follows: the RPL neighbor port remains blocked, that is, no exit event occurs to the RPL neighbor port itself and its sibling ports; and thirdly: the exit of the port with the node is added with a blocked port except the RPL neighbor port, which causes the re-determination, and during the period, the RPL owner port can not normally send out the NRRB message, so that the re-selected blocked port is released, wherein the reason that the RPL owner port can not normally send out the NRRB message can be the exit or the re-calculation of the RPL owner port, and the re-calculation is actually the exit of the brother port of the RPL owner port; fourthly, the method comprises the following steps: the reselected blocked port and the RPL neighbor port are not on the same link. If the four conditions are met, it is inevitable that a certain node in the ERPS ring cannot communicate with other nodes, and an island is formed.

Therefore, it should be noted that, in the embodiment of the present application, by defining the port exit event on the ERPS ring and the port exit needing to send the end-of-life message, the event that the node on the ERPS ring cannot sense the node exit and rejoin is solved, which is beneficial to ensuring smooth information among the nodes and avoiding the possible occurrence of abnormal condition of the ERPS ring. Furthermore, when the ERPS ring includes the RPL link, the embodiment of the present application may effectively prevent the node from forming the analyzed "island" condition, and ensure normal communication between the nodes.

The following is a combination of embodiments of the ring network anomaly protection method provided in the present application, and is directed to analyzing and solving the above technical problems provided in the present application.

Referring to fig. 2, fig. 2 is a schematic flow chart of a ring network anomaly protection method in the embodiment of the present application, and the ring network anomaly protection method in the embodiment of the present application will be described in detail from the first node side with reference to fig. 2. As shown in fig. 2, the method may include the following steps S201 to S203.

Step S201: the first node determines that the first port of the first node exits an Ethernet ring protection switching protocol (ERPS) ring.

Specifically, the exit ERPS ring is configured to instruct the first port not to process an ERPS protocol packet in the state of exiting the ERPS ring, where the first port is a port of the first node on the ERPS ring. For example, the first port of the first node is port 1 on node B in fig. 1. It should be noted that the node exiting the ERPS ring in this application may be due to a non-physical type failure of the node, or may be a node exiting the ERPS ring caused by manual setting, and the node may be added to the ERPS ring again after the non-physical type failure of the node is recovered or manually reset.

In a possible implementation manner, the determining, by the first node, that the first port of the first node exits the ethernet ring protection switching protocol ERPS ring specifically includes: the first node determines that a first port of the first node is ready to exit an Ethernet ring protection switching protocol (ERPS) ring. That is, the first node may execute the subsequent method flow before the first port intends to exit but has not exited, or may execute the subsequent method flow while determining that the first port exits the ERPS ring.

Step S202: the first node blocks a second port, the second port being a port of the first node on the ERPS ring, the second port being different from the first port.

Specifically, the second port is a port of the first node on the ERPS ring, that is, a sibling port of the first port, for example, the first port of the first node is port 1 on node B in fig. 1, and the second port of the first node is port 2 on node B in fig. 1. The second port of the sibling port of the first node needs to be switched or kept in a blocking state due to the exit of the first port, and in order to prevent looping, the second port needs to be blocked first, and then the exit of the first port needs to be performed.

It is understood that there may be a plurality of first nodes on the ERPS ring, that is, when ports of a plurality of nodes on the ERPS ring exit, the first nodes represent the plurality of exiting nodes.

Step S203: the first node sends a first terminating message to a second node.

Specifically, the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first near-end packet is used to indicate that the first port of the first node exits the ERPS ring. The method not only defines that the port is set to be in a default state in the state of exiting the ERPS ring, but also does not process the ERPS protocol message and does not participate in the calculation of the ERPS protocol; and defining the terminal message which needs to inform other nodes of the exit of the port from the ERPS ring, and enabling other nodes to sense the exit and the entrance of the node so as to perform related processing. The first terminating message is used for indicating the first port of the first node to exit the ERPS ring. Further, the first terminating packet may include a media access control MAC address of the first node. Specifically, it may be determined from which port of the first node the first terminating packet specifically originates, and a traffic path sent from the packet may be determined, for example, in fig. 1, if the terminating packet is sent out when exiting from port 1 on B, the traffic path is node C → node D → node a; if the end-of-line message is sent out when the port 2 on the node B exits, the flow path is node A → node D → node C.

Optionally, the specific time when the first port of the first node sends the first termination packet to other nodes on the ERPS ring except the first node may be before or at the same time when the first port exits the ERPS ring, because if the termination packet is sent after the first port exits the ERPS ring, it is likely that other nodes are not in time to perform related processing, and a loop is formed. And it is emphasized that the blocking of the sibling of the first port of the first node must be before the first port exits, otherwise looping may result.

Step S204: the second node receives the first terminating message,

specifically, after receiving the first terminating packet, the second node (e.g., nodes A, C and D in fig. 1) may store the first terminating packet first, so as to facilitate subsequent parsing. It should be noted that the second nodes are all the other nodes on the ERPS ring except the first node in step S201, that is, the other nodes on the ERPS ring except the first node in this application may be considered as the second nodes, and the application is only specifically described in detail with one of the second nodes.

Step S205: and if the second node has a blocked port on the ERPS ring, switching the state of the blocked port into a forwarding state.

Specifically, when the second node (i.e., the node on the ERPS ring other than the first node) in the ERPS ring learns that the port on the first node exits, and the exiting of the first port on the first node inevitably causes the blocking of the second port, the blocked port is inevitably present in the ERPS ring at this time, so that in order to avoid the above-mentioned analysis that the node is formed as an island due to too many blocked ports, the port on the second node in the current state of the blocked state can be released, that is, switched to the forwarding state. I.e. the other nodes (i.e. all second nodes) in the ERPS ring except the second port blocked by the first node need to switch the blocked port to the forwarding state. Therefore, even if the negotiation of the blocked port is performed again when the first port of the first node which exits subsequently joins again, only one blocked port is finally determined on the whole ERPS ring. The reason is that after the first port of the first node exits, only one blocking port (the second port of the first node) is reserved in the ERPS ring, and the blocking port is blocked due to the exit of the sibling port, so that the blocking port receives and processes the NR packet sent by other ports, and participates in the final calculation and determination of the blocking port, and therefore, according to the blocking port calculation method in the prior art, only one blocking port (usually, a port with a large MAC address) is finally determined, and therefore, a certain node cannot perform normal communication.

In a possible implementation manner, when the ERPS ring includes the ring network protection link RPL, since the ports at the two ends of the RPL are the main node RPL inner port of the ring network protection link and the neighboring node RPL neighbor port of the ring network protection link, under such a condition, the embodiment provided in the present application can further solve the analyzed islanding problem, and ensure that, when each node is dropped out and added again, the islanding problem is not caused, and communication between nodes is ensured.

It can be understood that, since the ERPS ring is divided into the cut-back/non-cut-back mode, when the ERPS link is recovered to be normal, whether to re-block the RPL owner port can be determined by setting the cut-back/non-cut-back mode of the ERPS. In the cut-back mode, if the failed link recovers, after waiting for the WTR time, the RPL owner port will be re-blocked, and the blocked link will be switched back to the RPL. In the non-cut-back mode, if the failed link recovers, the WTR Timer is not started, and the blocking link remains on the original failed link and is not switched back to the RPL. By default, the ERPS ring is in a cut-back mode. That is, in the cut-back mode, the eventually blocked port may revert back to the RPL owner port after WTR time.

According to the method and the device, under the condition that the first node determines that the first port of the first node exits the ERPS ring, the first termination message is sent to other nodes except the first node, namely the second node, on the ERPS ring, so that the other nodes can conveniently carry out state switching on the current blocked port of the first node according to the termination message sent by the first node, and the situation that the nodes cannot normally communicate under a special condition is avoided. That is, in the present application, by defining that a node exits an ERPS ring, and defining exit processing (for example, sending a near-end message) performed by the node when the node exits the ERPS ring, and defining feedback (for example, switching a currently blocked port to a forwarding state) that the node needs to exit to other nodes on the ERPS ring where the node is located, the problem that the node cannot normally communicate due to the inability of other nodes to sense when the port on the ERPS ring exits and rejoins is effectively avoided.

Referring to fig. 3, fig. 3 is a schematic flow chart of another method for protecting a ring network from an exception in the embodiment of the present application, and the method for protecting a ring network from an interaction side of a first node and a second node in the embodiment of the present application will be described in detail below with reference to fig. 3. As shown in fig. 3, the method may include the following steps S301 to S308.

Step S301: the first node determines that the first port of the first node exits an ethernet ring protection switching protocol (ERPS) ring, where the exiting ERPS ring is used to indicate that the first port does not process an ERPS protocol packet in the state of exiting the ERPS ring, and the first port is a port of the first node on the ERPS ring.

Step S302: the first node blocks a second port, the second port being a port of the first node on the ERPS ring, the second port being different from the first port.

Step S303: the first node sends a first termination message to a second node, wherein the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first termination message is used for indicating that a first port of the first node exits the ERPS ring.

Specifically, steps S301 to S303 may refer to steps S201 to S203 in the embodiment of fig. 2, which are not described herein again.

Optionally, the first node may block the second port first, then perform the sending of the first terminating message in step S302, and finally exit the first port, so that it may be ensured that there is a blocked port on the ERPS ring first, then determine to release the other blocked ports on the ERPS ring by sending the first terminating message, and finally exit the port, thereby effectively preventing the first port from looping before exiting the ERPS ring.

Step S304: the second node receives the first terminating message.

Specifically, step S303 may refer to step S202 in the embodiment of fig. 2, which is not described herein again.

Step S305: the second node adjusts port parameters so that the ERPS ring remains in a pending state.

Specifically, after receiving the terminating packet, optionally, all second nodes on the ERPS ring may adjust their port states, so that the entire ERPS ring is switched to the Pending state, because in the Pending state, the port may process a wider variety of events, for example, the processing of NR does not distinguish between an RPL owner port and an RPL neighbor port, and the packets of all ports are processed.

Step S306: and if the second node has a blocked port on the ERPS ring, switching the state of the blocked port into a forwarding state.

Specifically, step S306 may refer to step S205 in the embodiment of fig. 2, which is not described herein again.

Step S307: and if the second port of the first node exits the ERPS ring, sending a second terminating message to the second node.

Specifically, the second terminating message is used to indicate that the second port of the first node exits the ERPS ring. If another second port (for example, port 2 on node B in fig. 1) of the first node on the ERPS ring also exits the ERPS ring, a second termination message is also sent, where the second termination message is used to indicate that the second port of the first node exits the ERPS ring, and the second termination message includes a MAC address of the second node, so that the second node can identify which port of which node on the ERPS ring the termination message is sent from.

Step S308: and the second node receives a second terminating message.

Specifically, the second terminate message is used to indicate that a second port of the first node exits the ERPS ring, where the second port is a port of the first node on the ERPS ring, and the second terminate message includes a media access control MAC address of the second node. When the second node receives the second terminating message, the second node needs to compare with the first terminating message received and stored before, because if two exit ports sending the terminating message are from the same node, the two ports on the node are both in a state of exiting the ERPS ring, and the state of exiting the ERPS ring causes the node to be in a state of transparently transmitting data, that is, a reliable blocking port cannot be formed currently, and since the exit of the first port causes the release of blocking ports on other nodes before, a loop is likely to be formed at this time, and a broadcast storm is caused.

Step S309: and if the second node judges that the MAC addresses in the second terminal message and the first terminal message are the same, controlling to execute a port initialization process.

Specifically, when the second node determines that the MAC addresses in the second terminating message and the first terminating message are the same, it is determined that the second port and the first port are both ports on the first node, that is, the same-source port, and at this time, it is not possible to break a loop by controlling the port state on one node, and it is necessary to execute a port initialization procedure while maintaining the pending state on the ERPS ring, resume the blocking of the RPL owner port and the RPL neighbor port on the RPL, or reselect a blocked port.

The embodiment of the present application not only retains the beneficial effects of the embodiment corresponding to fig. 2, but also further provides a corresponding solution to various possible situations of port exit, such as a situation when two ports on one node both exit, so as to avoid an islanding situation on an ERPS ring caused by the exit and the join of the ports, and effectively ensure normal communication between nodes on the ERPS ring.

To facilitate better implementation of the above-described aspects of the embodiments of the present application, the present application also provides related apparatus for cooperating to implement the above-described aspects. The following is described in detail with reference to the schematic structural diagrams of the embodiments of the related apparatus provided in the present application and shown in fig. 4 to fig. 6:

referring to fig. 4, fig. 4 is a schematic structural diagram of an embodiment of a looped network anomaly protection device provided in the present application, where the device 10 may include: a processing module 101 and a sending module 102, wherein:

a processing module 101, configured to determine that a first port of a first node exits an ethernet ring protection switching protocol ERPS ring, where the exiting ERPS ring is used to indicate that the first port does not process an ERPS protocol packet in a state of exiting the ERPS ring, and the first port is a port of the first node on the ERPS ring;

a processing module 101, further configured to block a second port, where the second port is a port of the first node on the ERPS ring, and the second port is different from the first port;

a sending module 102, configured to send a first terminate message to a second node, where the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first terminate message is used to indicate that a first port of the first node exits the ERPS ring.

Specifically, the processing module is configured to determine that the first port of the first node exits the ethernet ring protection switching protocol ERPS ring, and specifically, the processing module is to: determining that the first port of the first node is ready to exit an Ethernet ring protection switching protocol (ERPS) ring.

Further, the first terminating packet includes a media access control MAC address of the first node.

Still further, the ERPS ring includes a ring network protection link RPL, and ports at two ends of the RPL are a ring network protection link main node RPL owner port and a ring network protection link neighbor node RPL neighbor port.

Still further, the sending module 102 is further configured to:

Still further, the second terminating packet includes a media access control MAC address of the second node.

In the present embodiment, the ring network anomaly protection device 10 is presented in the form of a module. A "module" herein may refer to an application-specific integrated circuit (ASIC), a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. In addition, the above processing module 101 can be implemented by the processor 301 of the ring network abnormality protection device 30 shown in fig. 6, and the sending module 102 can be implemented by the processor 301 of the ring network abnormality protection device 30 shown in fig. 6 controlling the communication interface 303.

It can be understood that, the functions of each module in the ring network anomaly protection device 10 may refer to the specific implementation manner in the method embodiments corresponding to fig. 2 to fig. 3, and are not described herein again.

Referring to fig. 5, fig. 5 is a schematic structural diagram of another embodiment of a ring network anomaly protection device provided in the embodiment of the present application, where the device 20 may include: a receiving module 201 and a processing module 202, wherein:

a receiving module 201, configured to receive a first terminate message, where the first terminate message is used to indicate that a first port of a first node exits an ethernet ring protection switching protocol ERPS ring, the first port is a port of the first node on the ERPS ring, the first node and the second node are both on the ERPS ring, and the first node and the second node are different nodes;

a processing module 202, configured to switch a state of a blocked port to a forwarding state if the port of the second node on the ERPS ring has the blocked port.

Specifically, the first terminating packet includes a media access control MAC address of the first node;

the receiving module 201 is further configured to: after receiving a first termination message, receiving a second termination message, where the second termination message is used to indicate that a second port of the first node exits the ERPS ring, the second port is a port of the first node on the ERPS ring, and the second termination message includes a media access control MAC address of the second node;

the processing module 202 is further configured to control to execute a port initialization procedure if the second node determines that the MAC addresses in the second terminating message and the first terminating message are the same.

Further, the processing module 202 is further configured to:

In the present embodiment, the ring network anomaly protection device 20 is presented in the form of a module. A "module" herein may refer to an application-specific integrated circuit (ASIC), a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. Furthermore, the processing module 202 can be implemented by the processor 301 of the ring network anomaly protection device 30 shown in fig. 6, and the receiving module 201 can be implemented by the processor 301 of the ring network anomaly protection device 30 shown in fig. 6 controlling the communication interface 303.

It is to be understood that the functions of each module in the ring network anomaly protection device 20 may be implemented in the method embodiments corresponding to fig. 2 to fig. 3, and are not described herein again.

As shown in fig. 6, fig. 6 is a schematic structural diagram of an embodiment of a node device provided in the embodiment of the present application, where the ring network anomaly protection device 10 and the ring network anomaly protection device 20 may be implemented by the structure of the node device in fig. 6, and the node device 30 includes at least one processor 301, at least one memory 302, and at least one communication interface 303. In addition, the node device may further include general components such as an antenna, which are not described in detail herein.

The processor 301 may be a general purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs according to the above schemes.

Communication interface 303 is used for communicating with other devices or communication Networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.

The Memory 302 may be, but is not limited to, a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.

The memory 302 is used for storing application program codes for executing the above scheme, and is controlled by the processor 301 to execute. The processor 301 is configured to execute application program code stored in the memory 302.

When the node device shown in fig. 6 is the ring network anomaly protection device 10, the code stored in the memory 302 may execute the above-provided ring network anomaly protection method executed by the ring network anomaly protection device 10, for example, it is determined that the first port of the first node exits from an ethernet ring protection switching protocol ERPS ring, where the exiting ERPS ring is used to indicate that the first port does not process an ERPS protocol packet in a state of exiting from the ERPS ring, and the first port is a port of the first node on the ERPS ring; blocking a second port of the first node on the ERPS ring, the second port being different from the first port; and sending a first termination message to a second node, wherein the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first termination message is used for indicating that a first port of the first node exits the ERPS ring.

When the node device shown in fig. 6 is the ring network anomaly protection device 20, the code stored in the memory 302 may execute the ring network anomaly protection method executed by the ring network anomaly protection device 20, for example, receive a first termination message, where the first termination message is used to indicate that a first port of a first node exits an ethernet ring protection switching protocol ERPS ring, the first port is a port of the first node on the ERPS ring, the first node and the second node are both on the ERPS ring, and the first node and the second node are different nodes; and if the second node has a blocked port on the ERPS ring, switching the state of the blocked port into a forwarding state.

It is understood that the functions of the modules in the node device 30 may refer to the specific implementation manner in the method embodiments corresponding to fig. 2 to fig. 3, and are not described herein again.

The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a program, and when the program is executed, the program includes some or all of the steps of any one of the ring network exception protection methods described in the above method embodiments.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like, and may specifically be a processor in the computer device) to execute all or part of the steps of the above-described method of the embodiments of the present application. The storage medium may include: a U-disk, a removable hard disk, a magnetic disk, an optical disk, a Read-Only Memory (ROM) or a Random Access Memory (RAM), and other various media capable of storing program codes.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A looped network abnormity protection method is characterized by comprising the following steps:

a first node determines that a first port of the first node exits an ethernet ring protection switching protocol (ERPS) ring, wherein the exiting ERPS ring is used for indicating that the first port does not process an ERPS protocol message in the state of exiting the ERPS ring, and the first port is a port of the first node on the ERPS ring;

the first node blocking a second port, the second port being a port of the first node on the ERPS ring, the second port being different from the first port;

the first node sends a first termination message to a second node, wherein the first node and the second node are both on the ERPS ring, the first node and the second node are different nodes, and the first termination message is used for indicating that a first port of the first node exits the ERPS ring.

2. The method according to claim 1, wherein the determining, by the first node, that the first port of the first node exits the ethernet ring protection switching protocol ERPS ring specifically includes:

the first node determines that a first port of the first node is ready to exit an Ethernet ring protection switching protocol (ERPS) ring.

3. The method of claim 1 or 2, wherein the first terminate message includes a media access control, MAC, address of the first node.

4. The method according to any of claims 1-2, wherein the ERPS ring includes a ring protection link RPL, and ports at both ends of the RPL are a ring protection link master node RPL inner port and a ring protection link neighbor node RPL neighbor port.

5. The method of any one of claims 1-2, further comprising:

6. The method of claim 5, wherein the second terminate message includes a Media Access Control (MAC) address of the second node.

7. An ethernet ring protection method, comprising:

a second node receives a first termination message, wherein the first termination message is used for indicating a first port of the first node to exit an Ethernet ring protection switching protocol (ERPS) ring, the first port is a port of the first node on the ERPS ring, the first node and the second node are both on the ERPS ring, and the first node and the second node are different nodes;

and if the second node has a blocked port on the ERPS ring, switching the state of the blocked port into a forwarding state.

8. The method of claim 7, wherein the first terminate message includes a Media Access Control (MAC) address of the first node;

after the second node receives the first terminating message, the method further includes:

the second node receives a second terminate message, where the second terminate message is used to indicate that a second port of the first node exits the ERPS ring, the second port is a port of the first node on the ERPS ring, and the second terminate message includes a Media Access Control (MAC) address of the second node;

and if the second node judges that the MAC addresses in the second terminal message and the first terminal message are the same, controlling to execute a port initialization process.

9. The method according to claim 7 or 8, wherein after the second node receives the first terminating message, further comprising:

and the second node adjusts the port parameters so that the ERPS ring is switched into a pending state.

10. The method according to any of claims 7-8, wherein the ERPS ring includes a Ring Protection Link (RPL), and the ports at both ends of the RPL are a ring protection link master node (RPL inner port) and a ring protection link neighbor node (RPL neighbor port).

11. A looped network anomaly protection device, comprising:

12. The apparatus of claim 11, wherein the processing module is configured to determine that the first port of the first node exits the ethernet ring protection switching protocol ERPS ring, and specifically:

13. The apparatus according to claim 11 or 12, wherein the first terminate message comprises a media access control, MAC, address of the first node.

14. The apparatus according to any of claims 11-12, wherein said ERPS ring comprises a ring protection link RPL, and the ports at both ends of said RPL are a ring protection link master node RPL inner port and a ring protection link neighbor node RPL neighbor port.

15. The apparatus of any of claims 11-12, wherein the sending module is further configured to:

16. The apparatus of claim 15, wherein the second terminate message comprises a Media Access Control (MAC) address of the second node.

17. An ethernet ring protection device, comprising:

a receiving module, configured to receive a first terminate message, where the first terminate message is used to indicate that a first port of a first node exits an ethernet ring protection switching protocol (ERPS) ring, the first port is a port of the first node on the ERPS ring, the first node and a second node are both on the ERPS ring, and the first node and the second node are different nodes;

18. The apparatus of claim 17, wherein the first terminate message includes a Media Access Control (MAC) address of the first node;

the receiving module is further configured to:

19. The apparatus of claim 17 or 18, wherein the processing module is further configured to:

20. The apparatus according to any of claims 17-18, wherein said ERPS ring comprises a ring protection link RPL, and the ports at both ends of said RPL are a ring protection link master node RPL inner port and a ring protection link neighbor node RPL neighbor port.