Method for processing RRPP fault and node equipment

Abstract

The invention provides a method for processing RRPP faults and node equipment, and the method comprises the steps: judging whether a flow output port reaching a main node of a main ring exists or not when a common link and a non-common link of the main ring are recognized to fail at the same time, and transmitting a first notice to a sub-ring edge node if the flow output port reaching the main node of the main ring does not exist, and receiving a second notification sent by the sub-ring edge node, the second notification being sent to a sub-ring auxiliary edge node when the sub-ring edge node queries that a traffic output port reaching the main node of the main ring exists, and blocking a service port of the sub-ring auxiliary edge node according to the second notification. By means of the method, the loop problem between the sub-rings can be solved.

Description

Technical Field

[0001] This specification relates to the field of communication technology, and in particular to a method and node device for handling RRPP failures. Background Art

[0002] RRPP (Rapid Ring Protection Protocol) is a link layer protocol specifically designed for Ethernet rings, a proprietary implementation by H3C. When the Ethernet ring is intact, it prevents broadcast storms caused by data loops. When a link on the Ethernet ring is disconnected, it quickly restores communication links between nodes on the ring. Compared to the spanning tree protocol, RRPP offers faster convergence, and its convergence time is independent of the number of nodes on the ring, making it suitable for networks with larger diameters.

[0003] Hello: Health monitoring message, initiated by the master node, to check the loop integrity of the network.

[0004] Edge-Hello: A primary ring integrity check message, initiated by an edge node and received by an auxiliary edge node, to check the primary ring link between the edge node and the auxiliary edge node.

[0005] Major-Fault: A major ring fault notification message initiated by an auxiliary edge node. When the major ring link between the auxiliary edge node and the edge node is disconnected (no EDGE-HELLO message is received from the edge node within the specified time), the auxiliary edge node reports the major ring link fault to the edge node.

[0006] Common-Flush-FDB: Refresh FDB (Forwarding Database) message, initiated by the master node, notifies the transit node, edge node, or assistant edge node to update their respective MAC address forwarding table, ARP table, and ND table.

[0007] RPP configures devices on an Ethernet ring network as nodes with different roles on the RRPP ring. Each node detects the ring status and communicates topology changes by sending, receiving, and processing RRPP protocol messages. The ring's decision-making node, the master node, blocks or releases its secondary ports based on the ring status. This allows for rapid activation of backup links and elimination of loops when a device or link fails.

[0008] To prevent data packets from forming broadcast loops on the ring, the master node in an RRPP ring periodically sends Hello messages to monitor the ring network status. These Hello messages are sent from the primary port through the control VLAN, propagating through each transit node on the ring. They are received by the master node's secondary port, blocking the secondary port so that it can only receive RRPP protocol packets and cannot forward data packets in the protection VLAN.

[0009] If multiple subrings intersect the main ring and both public and non-public links fail simultaneously (this triggers the RRPP protocol to send a Major-Fault message to the auxiliary edge node), the main ring is detected as disconnected, the Hello message on the subring master node times out, and multiple subrings simultaneously release restrictions on their secondary ports, forming loops between the subrings. To prevent message loops between subrings, traditional RRPP uses a multi-homed subring broadcast storm suppression mechanism. This mechanism avoids loops by temporarily blocking edge ports at edge nodes.

[0010] When a public link and at least one non-public link fail, the multi-homed sub-ring broadcast storm suppression mechanism blocks the edge ports on the edge nodes. If no user traffic egress is available on the auxiliary edge node, even if user traffic egress is still available on the edge node, the blocked edge ports will prevent normal user traffic forwarding. Summary of the Invention

[0011] To overcome the problems existing in the related art, this specification provides a method for sending messages, an ADWAN controller and a node device.

[0012] According to a first aspect of an embodiment of this specification, a method for handling an RRPP failure is provided. The method is applied to a sub-ring auxiliary edge node, and the method includes:

[0013] When it is identified that both the public link and the non-public link of the primary ring fail at the same time, it is determined whether there is a traffic egress port to the primary node of the primary ring;

[0014] If there is no traffic outbound port reaching the master node of the primary ring, a first notification is sent to the edge node of the sub-ring;

[0015] receiving a second notification sent by the sub-ring edge node, where the second notification is sent by the sub-ring edge node to the sub-ring auxiliary edge node when the sub-ring edge node queries that there is a traffic outbound port arriving at the main node of the main ring;

[0016] According to the second notification, the service port of the sub-ring assistant edge node is blocked.

[0017] The method for identifying simultaneous failures of the public link and the non-public link of the primary ring includes:

[0018] When it is determined that no Edge-Hello message sent by the sub-ring edge node is received within a preset time, it is determined that both the public link and the non-public link of the main ring are faulty.

[0019] The determining whether there is a traffic outbound port reaching the primary ring master node includes:

[0020] Determine whether there is a routing table entry reaching the primary ring master node. If so, determine that there is a traffic egress port reaching the primary ring master node. If not, determine that there is no traffic egress port reaching the primary ring master node.

[0021] The sending of the first notification to the sub-ring edge node includes:

[0022] An AE-No-Output message is sent to the sub-ring edge node, so that after receiving the AE-No-Output message, the sub-ring edge node knows that the sub-ring auxiliary edge node has no traffic outbound port to the main ring master node.

[0023] The receiving the second notification sent by the sub-ring edge node includes:

[0024] Receives E-Output messages sent by the sub-ring edge node.

[0025] From the above examples, it can be seen that the introduction of the AE-No-Output message (first notification) and the E-Output message (second notification) changes the blocking point of the loop, thereby enabling user traffic to be forwarded.

[0026] According to a second aspect of an embodiment of this specification, a method for handling an RRPP failure is provided. The method is applied to a sub-ring edge node, and the method includes:

[0027] Receiving a first notification sent by a sub-ring auxiliary edge node, wherein the first notification is sent by the sub-ring edge node when the sub-ring edge node determines that there is no traffic egress port to the main node of the main ring under the condition that both the public link and the non-public link of the main ring fail simultaneously;

[0028] Trigger itself based on the first notification to determine whether there is a traffic outbound port that reaches the primary ring master node;

[0029] If so, a second notification is sent to the sub-ring assistant edge node, so that the sub-ring assistant edge node blocks the service port of the sub-ring assistant edge node according to the second notification.

[0030] According to a third aspect of an embodiment of this specification, a node device is provided, wherein the node device is configured as a sub-ring auxiliary edge node, and the node device includes:

[0031] A judgment module, configured to judge whether there is a traffic egress port to the master node of the primary ring when it is identified that both the public link and the non-public link of the primary ring fail at the same time;

[0032] a sending module, configured to send a first notification to a sub-ring edge node when no traffic outbound port reaches the main node of the main ring;

[0033] A receiving module, configured to receive a second notification sent by the sub-ring edge node, where the second notification is sent by the sub-ring edge node to the sub-ring auxiliary edge node when the sub-ring edge node queries that there is a traffic outbound port arriving at the main node of the main ring;

[0034] The processing module is configured to block the service port of the sub-ring auxiliary edge node according to the second notification.

[0035] The judgment module is specifically configured to determine that both the public link and the non-public link of the main ring are faulty when it is identified that no Edge-Hello message sent by the sub-ring edge node is received within a preset time.

[0036] The judgment module is specifically used to judge whether there is a routing table entry reaching the main node of the main ring. If so, it is determined that there is a traffic egress port reaching the main node of the main ring; if not, it is determined that there is no traffic egress port reaching the main node of the main ring.

[0037] According to a third aspect of an embodiment of this specification, a node device is provided, wherein the node device is configured as a sub-ring edge node, and the node device includes:

[0038] a receiving module, configured to receive a first notification sent by a sub-ring auxiliary edge node, wherein the first notification is sent by the sub-ring edge node when it is determined that there is no traffic egress port to the main node of the main ring under the condition that both the public link and the non-public link of the main ring fail simultaneously;

[0039] A judgment module, configured to trigger itself to judge whether there is a traffic egress port arriving at the primary ring master node according to the first notification;

[0040] The processing module is configured to send a second notification to the sub-ring auxiliary edge node if there is a traffic outbound port reaching the main node of the main ring, so that the sub-ring auxiliary edge node blocks the service port of the sub-ring auxiliary edge node according to the second notification.

[0041] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.

[0043] Figure 1 This is a schematic diagram of an RRPP networking architecture according to an exemplary embodiment of this specification.

[0044] Figure 2 This is a schematic diagram of an RRPP networking architecture according to an exemplary embodiment of this specification.

[0045] Figure 3 This is a flowchart of a method for handling an RRPP failure according to an exemplary embodiment of this specification. DETAILED DESCRIPTION

[0046] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with this specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of this specification, as detailed in the appended claims.

[0047] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. As used in this specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0048] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, such information should not be limited to these terms. These terms are merely used to distinguish information of the same type from one another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information without departing from the scope of this specification. Depending on the context, the term "if" as used herein may be interpreted as "when," "when," or "in response to determining."

[0049] The three common RRPP ring physical topologies are: single ring, intersecting ring, and tangent ring. Each networking form has different ways of dividing the RRPP domain. This paper mainly discusses intersecting rings. Figure 1 As shown, in the intersecting rings, in addition to the main node and the transmission node, the common nodes of the main ring and the sub-ring are edge nodes and auxiliary edge nodes. The ports connected to the main ring are common ports, and the ports only connected to the sub-ring are edge ports.

[0050] like Figure 2As shown, if multiple subrings intersect the main ring and both public and non-public links fail simultaneously (this triggers the auxiliary edge node to send a Major-Fault message in the RRPP protocol), the main ring is detected as disconnected, the Hello message on the subring master node times out, and multiple subrings simultaneously release restrictions on their secondary ports, forming loops between the subrings. To prevent message loops between subrings, traditional RRPP uses a multi-homed subring broadcast storm suppression mechanism to address this problem. This mechanism temporarily blocks edge ports at edge nodes to avoid loops.

[0051] However, the existing method has the following problems: when there is no user traffic outlet on the auxiliary edge node and there is a user traffic outlet on the edge node, the multi-homed sub-ring broadcast storm suppression mechanism will block the edge port on the edge node, resulting in the inability to forward user traffic normally.

[0052] To solve the above technical problems, the present disclosure provides a method for handling RRPP failures, such as Figure 3 As shown, the method is applied to a sub-ring auxiliary edge node, and the method includes:

[0053] S301: When it is identified that both the public link and the non-public link of the primary ring fail at the same time, determine whether there is a traffic egress port to the primary node of the primary ring;

[0054] S302: If there is no traffic outbound port reaching the master node of the primary ring, a first notification is sent to the edge node of the sub-ring;

[0055] S303: receiving a second notification sent by the sub-ring edge node, where the second notification is sent by the sub-ring edge node to the sub-ring auxiliary edge node when the sub-ring edge node finds that there is a traffic outbound port arriving at the main node of the main ring;

[0056] S304: Block the service port of the sub-ring assistant edge node according to the second notification.

[0057] The above method can be implemented as follows: after the auxiliary edge node sends a Major-Fault message to notify the main ring abnormality, the traffic egress port status is determined through a protocol between the auxiliary edge node and the edge node. When the auxiliary edge node has no traffic egress port and the edge node has a traffic egress port, the blockage of the edge node's edge port is released, and the blockage is sent to the edge node of the auxiliary edge node, so that user traffic can be forwarded normally.

[0058] Specifically, when the sub-ring auxiliary edge node (referred to as auxiliary edge node) does not receive the Edge-Hello message sent by the sub-ring edge node (edge node) within a preset time, the auxiliary edge node can determine that the public link and non-public link of the main ring are simultaneously faulty.

[0059] Based on the above situation, when the auxiliary edge node identifies that the public link and non-public link of the primary ring fail at the same time, the auxiliary edge node can perform traffic statistics on the protection VLAN traffic entering the node, and when it detects that the destination Mac of the traffic has no public port egress port.

[0060] Alternatively, after receiving the Common-Flush-FDB message from the sub-ring, the auxiliary edge node performs traffic statistics on the protection VLAN traffic entering the node, and detects that the destination Mac of the traffic does not have an egress port of the public port.

[0061] In this embodiment, when it is detected that the destination Mac of the traffic does not have an egress port of a public port, the edge node may be notified.

[0062] In an example, the auxiliary edge node may send an AE-No-Output message (first notification) to the edge node. The AE-No-Output message may be a newly defined RRPP type message, which indicates that the auxiliary edge node has no traffic outbound port.

[0063] When an edge node receives an AE-No-Output message, it extracts the destination MAC from the SYSTEM_MAC_ADDR in the message and compares it with its own MAC address table. If the MAC address table contains an entry with a public port as the outbound port, the edge node is considered to have an outbound port for the traffic.

[0064] In this embodiment, the edge node can set a first preset time. Before the first preset time expires, if the AE-No-Output message sent by the auxiliary edge node is not received, it means that the auxiliary edge node has a traffic outbound port, and the edge node can block the outbound port to prevent a sub-ring loop.

[0065] Before the first preset time expires, if the AE-No-Output message sent by the auxiliary edge node is received, the edge node extracts the destination Mac from the SYSTEM_MAC_ADDR of the message and compares it with its own Mac address table.

[0066] In this embodiment, when the edge node determines through the above steps that it has an egress port for traffic to the primary ring master node, it can send an E-Output message (second notification) to the auxiliary edge node. This E-Output message can be a newly defined RRPP type message, indicating that the edge node has an egress port for traffic. The RRPP TYPE field uses the unoccupied 0x0d field, and the destination Mac, which verifies the presence of a public port egress port, is filled in the SYSTEM_MAC_ADDR field. The remaining fields remain consistent with the original RRPP protocol.

[0067] In this embodiment, a Block-Release timer can also be defined with a minimum value, such as 1ms, to delay the edge node from unblocking the edge port. After the edge node sends an E-Output message to the edge port, it waits for the Block-Release timer to expire before unblocking the edge port, thus avoiding temporary loops.

[0068] It can be seen from the above example that when the public link and the non-public link of the main ring fail at the same time, the edge node can first block the egress port and determine whether it has received the first notification sent by the auxiliary edge node within the preset time. If not, no subsequent processing is required. If received, it determines whether it has an egress port that reaches the main node of the main ring. If so, it sends a second notification to the auxiliary edge node to enable the auxiliary edge node to block the service port, and the conversion node unblocks the edge port after waiting for the Block-Release timeout, thereby avoiding the interruption of the service caused by the conversion port blocking the egress port.

[0069] Based on the above embodiments, this embodiment further provides a method for handling RRPP failures, which is applied to a sub-ring edge node and includes:

[0070] Receiving a first notification sent by a sub-ring auxiliary edge node, wherein the first notification is sent by the sub-ring edge node when the sub-ring edge node determines that there is no traffic egress port to the main node of the main ring under the condition that both the public link and the non-public link of the main ring fail simultaneously;

[0071] Trigger itself based on the first notification to determine whether there is a traffic outbound port that reaches the primary ring master node;

[0072] If so, a second notification is sent to the sub-ring assistant edge node, so that the sub-ring assistant edge node blocks the service port of the sub-ring assistant edge node according to the second notification.

[0073] Based on the above method embodiments, an embodiment of the present disclosure further provides a node device, wherein the node device is configured as an auxiliary edge node in a sub-ring, and the node device includes:

[0074] A judgment module, configured to judge whether there is a traffic egress port to the master node of the primary ring when it is identified that both the public link and the non-public link of the primary ring fail at the same time;

[0075] a sending module, configured to send a first notification to a sub-ring edge node when no traffic outbound port reaches the main node of the main ring;

[0076] A receiving module, configured to receive a second notification sent by the sub-ring edge node, where the second notification is sent by the sub-ring edge node to the sub-ring auxiliary edge node when the sub-ring edge node queries that there is a traffic outbound port arriving at the main node of the main ring;

[0077] The processing module is configured to block the service port of the sub-ring auxiliary edge node according to the second notification.

[0078] The node device may be a routing device, a switching device, or a server.

[0079] The judgment module is specifically configured to determine that both the public link and the non-public link of the main ring are faulty when it is identified that no Edge-Hello message sent by the sub-ring edge node is received within a preset time.

[0080] The judgment module is specifically used to judge whether there is a routing table entry reaching the main node of the main ring. If so, it is determined that there is a traffic egress port reaching the main node of the main ring; if not, it is determined that there is no traffic egress port reaching the main node of the main ring.

[0081] Based on the above method embodiments, an embodiment of the present disclosure further provides a node device, wherein the node device is configured as a sub-ring edge node, and the node device includes:

[0082] a receiving module, configured to receive a first notification sent by a sub-ring auxiliary edge node, wherein the first notification is sent by the sub-ring edge node when it is determined that there is no traffic egress port to the main node of the main ring under the condition that both the public link and the non-public link of the main ring fail simultaneously;

[0083] A judgment module, configured to trigger itself to judge whether there is a traffic egress port arriving at the primary ring master node according to the first notification;

[0084] The processing module is configured to send a second notification to the sub-ring auxiliary edge node if there is a traffic outbound port reaching the main node of the main ring, so that the sub-ring auxiliary edge node blocks the service port of the sub-ring auxiliary edge node according to the second notification.

[0085] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The device embodiments described above are merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying any creative work.

[0086] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0087] Other embodiments of the present invention will readily occur to those skilled in the art upon consideration of the present invention and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present invention being indicated by the following claims.

[0088] It should be understood that the present description is not limited to the exact structure that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

[0089] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for handling RRPP failures, characterized in that: The method is applied to a sub-ring auxiliary edge node, and the method includes: When it is identified that both the public link and the non-public link of the primary ring fail at the same time, it is determined whether there is a traffic egress port to the primary node of the primary ring; If there is no traffic outbound port reaching the master node of the primary ring, a first notification is sent to the edge node of the sub-ring; receiving a second notification sent by the sub-ring edge node, where the second notification is sent by the sub-ring edge node to the sub-ring auxiliary edge node when the sub-ring edge node queries that there is a traffic outbound port arriving at the main node of the main ring; According to the second notification, the service port of the sub-ring assistant edge node is blocked.

2. The method according to claim 1, characterized in that Methods for identifying simultaneous failures of both common and non-common links on the primary ring include: When it is determined that no Edge-Hello message sent by the sub-ring edge node is received within a preset time, it is determined that both the public link and the non-public link of the main ring are faulty.

3. The method according to claim 1, characterized in that The determining whether there is a traffic outbound port reaching the primary ring master node includes: Determine whether there is a routing table entry reaching the primary ring master node. If so, determine that there is a traffic egress port reaching the primary ring master node. If not, determine that there is no traffic egress port reaching the primary ring master node.

4. The method according to claim 1, wherein The sending of the first notification to the sub-ring edge node includes: An AE-No-Output message is sent to the sub-ring edge node, so that after receiving the AE-No-Output message, the sub-ring edge node knows that the sub-ring auxiliary edge node has no traffic outbound port to the main ring master node.

5. The method according to claim 1, wherein The receiving a second notification sent by the sub-ring edge node includes: Receives E-Output messages sent by the sub-ring edge node.

6. A method for handling RRPP failures, characterized in that: The method is applied to a sub-ring edge node, and includes: Receiving a first notification sent by a sub-ring auxiliary edge node, wherein the first notification is sent by the sub-ring edge node when the sub-ring edge node determines that there is no traffic egress port to the main node of the main ring under the condition that both the public link and the non-public link of the main ring fail simultaneously; Trigger itself based on the first notification to determine whether there is a traffic outbound port that reaches the primary ring master node; If so, a second notification is sent to the sub-ring assistant edge node, so that the sub-ring assistant edge node blocks the service port of the sub-ring assistant edge node according to the second notification.

7. A node device, characterized in that: The node device is configured as a sub-ring auxiliary edge node, and the node device includes: A judgment module, configured to judge whether there is a traffic egress port to the master node of the primary ring when it is identified that both the public link and the non-public link of the primary ring fail at the same time; a sending module, configured to send a first notification to a sub-ring edge node when no traffic outbound port reaches the main node of the main ring; A receiving module, configured to receive a second notification sent by the sub-ring edge node, where the second notification is sent by the sub-ring edge node to the sub-ring auxiliary edge node when the sub-ring edge node queries that there is a traffic outbound port arriving at the main node of the main ring; The processing module is configured to block the service port of the sub-ring auxiliary edge node according to the second notification.

8. The node device according to claim 7, characterized in that: The judgment module is specifically configured to determine that both the public link and the non-public link of the main ring are faulty when it is identified that no Edge-Hello message sent by the sub-ring edge node is received within a preset time.

9. The node device according to claim 7, characterized in that: The judgment module is specifically used to judge whether there is a routing table entry reaching the main node of the main ring. If so, it is determined that there is a traffic outbound port reaching the main node of the main ring; if not, it is determined that there is no traffic outbound port reaching the main node of the main ring.

10. A node device, characterized in that: The node device is configured as a sub-ring edge node, and the node device includes: a receiving module, configured to receive a first notification sent by a sub-ring auxiliary edge node, wherein the first notification is sent by the sub-ring edge node when it is determined that there is no traffic egress port to the main node of the main ring under the condition that both the public link and the non-public link of the main ring fail simultaneously; A judgment module, configured to trigger itself to judge whether there is a traffic egress port arriving at the primary ring master node according to the first notification; The processing module is configured to send a second notification to the sub-ring auxiliary edge node if there is a traffic outbound port reaching the main node of the main ring, so that the sub-ring auxiliary edge node blocks the service port of the sub-ring auxiliary edge node according to the second notification.

Images