Method for processing RRPP multi-ring fault and network equipment
By assisting the edge nodes in the RRPP ring network to send Major-Fault messages, identify and handle main ring failures, the problem of excessive convergence time in the prior art is solved, and faster failure recovery and service transmission are achieved.
Patent Information
- Application Number
- CN202510866373.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-25
- Publication Date
- 2025-08-12
AI Technical Summary
In the RRPP ring network, when the public link and non-public link of the main ring fail at the same time, the prior art needs to wait for the Edge-Hello message and the Hello message of the main ring sub-ring, resulting in the routing convergence time being too long and affecting user services.
When the main ring's public link and non-public link fail at the same time, the main node's blocking service sub-port port will be directly opened to reduce the dependence on Hello packet timeout and shorten the fault convergence time.
It effectively shortens the failure convergence time of the RRPP ring network, improves the switching performance of user services, and reduces the risk of loop formation.
Smart Images
Figure CN120474867A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a method and network device for handling RRPP multi-ring 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] Master node: Each ring has only one master node. The master node is the initiator of the active detection mechanism for the ring network status and the decision maker for executing operations after the network topology changes.
[0006] Edge node: A special node located on both the main ring and the sub-ring. It is a master node or transit node on the main ring and an edge node on the sub-ring.
[0007] Assistant Edge Node: A special node located on both the primary ring and a sub-ring. It serves as a master or transit node on the primary ring and an assistant edge node on a sub-ring. Assistant edge nodes work in pairs with edge nodes to monitor the integrity of the primary ring and prevent loops.
[0008] RRPP configures devices on an Ethernet ring network as nodes with different roles within the 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.
[0009] When a ring failure occurs, the Edge-Hello message from the auxiliary edge node and the Hello message from the master node of the primary ring's sub-ring must time out simultaneously. In RRPP implementations, the time it takes for these two messages to time out varies. Edge nodes send Edge-Hello messages several times more frequently than Hello messages. Therefore, the Hello message timeout period for the master node of the sub-ring and primary ring is longer, affecting routing convergence. Summary of the Invention
[0010] To overcome the problems existing in the related art, this specification provides a method and network device for handling RRPP multi-ring failures.
[0011] According to a first aspect of an embodiment of this specification, a method for handling an RRPP multi-ring failure is provided. The method is applied to an auxiliary edge node of a sub-ring, and the method includes:
[0012] When it is identified that both the public link and the non-public link of the primary ring are faulty at the same time, a Major-Fault message is sent through each valid output port;
[0013] The primary ring master node that receives the Major-Fault message opens the blocked service secondary port.
[0014] The method for identifying simultaneous failures of a public link of the primary ring and a non-public link of the primary ring includes:
[0015] When the auxiliary edge node does not receive the Edge-Hello message sent by the edge node within a preset time, it is determined that both the public link of the primary ring and the non-public link of the primary ring are faulty.
[0016] The method for determining the auxiliary edge node includes:
[0017] An edge node of a sub-ring is determined, and another sub-ring node connected to the edge node via a public link is designated as an auxiliary edge node.
[0018] The above embodiments demonstrate that by changing the way Major-Fault messages are sent and processed, RRPP convergence time is shortened when both the public and non-public links of the primary ring fail simultaneously. This eliminates the need for the RRPP ring network to wait for Hello message timeouts. Instead, convergence only requires the Edge-Hello message timeout plus the Release-Delay. This improves failover performance for the user's RRPP ring network.
[0019] According to a second aspect of an embodiment of this specification, a method for handling an RRPP multi-ring failure is provided. The method is applied to a master edge node of a sub-ring, and the method includes:
[0020] Receive a Major-Fault message sent by an auxiliary edge node of a sub-ring, wherein the Major-Fault message is sent by the auxiliary edge node of the sub-ring when the auxiliary edge node of the sub-ring identifies that a public link of the main ring and a non-public link of the main ring are simultaneously faulty;
[0021] After the waiting delay time expires, the Major-Fault message is sent to the primary ring, so that the master node of the primary ring opens the blocked service secondary port after receiving the Major-Fault message.
[0022] According to a third aspect of an embodiment of this specification, a method for handling an RRPP multi-ring failure is provided. The method is applied to a master node of a primary ring, and the method includes:
[0023] Receiving a Major-Fault message sent by the auxiliary edge node, wherein the Major-Fault message is sent through each valid output port when the auxiliary edge node identifies that the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty;
[0024] Open the blocked secondary service port based on the Major-Fault message.
[0025] According to a fourth aspect of an embodiment of this specification, a network device is provided, wherein the network device is located in an auxiliary edge node of a sub-ring in an RRPP multi-ring, and the network device includes:
[0026] An identification module, configured to identify whether the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty;
[0027] The sending module is used to send a Major-Fault message through each valid output port when it is identified that the public link and the non-public link of the primary ring fail at the same time, so that the primary ring master node that receives the Major-Fault message opens the blocked service secondary port.
[0028] The identification module is specifically configured to determine that both the public link of the primary ring and the non-public link of the primary ring are faulty when the auxiliary edge node does not receive an Edge-Hello message sent by the edge node within a preset time.
[0029] Wherein, the network device further includes:
[0030] The determination module is used to determine the auxiliary edge node.
[0031] According to a fourth aspect of an embodiment of this specification, a network device is provided, the network device being disposed at a master edge node of a sub-ring, the network device comprising:
[0032] A receiving module, configured to receive a Major-Fault message sent by an auxiliary edge node of a sub-ring, wherein the Major-Fault message is sent when the auxiliary edge node of the sub-ring identifies that a public link of the main ring and a non-public link of the main ring are simultaneously faulty;
[0033] The sending module is used to send the Major-Fault message to the primary ring after the delay time expires, so that the master node of the primary ring opens the blocked service secondary port after receiving the Major-Fault message.
[0034] According to a fifth aspect of an embodiment of this specification, a network device is provided, the network device being placed at a master node of a primary ring, the network device comprising:
[0035] A receiving module, configured to receive a Major-Fault message sent by an auxiliary edge node, wherein the Major-Fault message is sent by the auxiliary edge node through each valid output port when the auxiliary edge node identifies that the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty;
[0036] The processing module is used to open the blocked service secondary port according to the Major-Fault message.
[0037] 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
[0038] 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.
[0039] Figure 1 This is a schematic diagram of an RRPP ring network architecture according to an exemplary embodiment of this specification.
[0040] Figure 2 This is a schematic diagram of an RRPP ring network architecture according to an exemplary embodiment of this specification.
[0041] Figure 3 This is a schematic diagram of an RRPP ring network architecture according to an exemplary embodiment of this specification.
[0042] Figure 4 This is a flowchart of a method for handling RRPP multi-ring failures according to an exemplary embodiment of this specification.
[0043] Figure 5 This is a schematic diagram of an RRPP ring network architecture according to an exemplary embodiment of this specification.
[0044] Figure 6 This is a schematic diagram of an RRPP ring network architecture according to an exemplary embodiment of this specification. DETAILED DESCRIPTION
[0045] 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.
[0046] 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.
[0047] 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."
[0048] Currently, if Figure 1 As shown in the figure, RRPP configures devices on an Ethernet ring as nodes with different roles within the 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.
[0049] like Figure 2 As shown in the figure, 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.
[0050] If a link failure occurs, RRPP handles the failure using either the polling mechanism or the link-down alarm mechanism. If the ring encounters complex conditions, such as nodes that do not support RRPP, the link-down alarm mechanism may not be effective. In such cases, the polling mechanism is primarily relied upon. If the master node fails to receive its own Hello message within the specified time, it switches to the Failed state, deactivates its secondary port, and sends a Common-Flush-FDB message from both the primary and secondary ports to notify all transit nodes on the ring to refresh their MAC and ARP entries.
[0051] like Figure 3 As 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.
[0052] Specifically, after a link failure occurs, the Edge-Hello message on the assistant edge node times out. Therefore, it detects the interruption of the sub-ring protocol message channel and immediately sends a Major-Fault message from its edge port to the edge node via the sub-ring link. Upon receiving the Major-Fault message, the edge node temporarily blocks its own edge port.
[0053] A primary ring failure disrupts the subring protocol message channel. The subring master node cannot receive its own Hello message within the specified time, so it transitions to the Failed state and disables its secondary port. Similarly, the primary ring master node disables its secondary port after the Fail timer expires. Traffic forwarding resumes in the direction of the subring master node, auxiliary edge node, and then the primary ring master node.
[0054] However, because the Edge-Hello message from the auxiliary edge node and the Hello message from the master node of the primary ring's subring both timed out simultaneously, in RRPP implementations, the time it takes for these two messages to time out differs. Edge nodes send Edge-Hello messages several times more frequently than Hello messages, so the Hello messages from the master node of the subring and primary ring take longer to time out. This prolongs routing convergence and impacts user services.
[0055] In order to solve the above technical problems, the embodiment of the present disclosure provides a method for handling RRPP multi-ring failures, which is applied to the auxiliary edge node of the sub-ring, such as Figure 4As shown, the method includes:
[0056] S401: When it is identified that both the public link of the primary ring and the non-public link of the primary ring are faulty at the same time, a Major-Fault message is sent through each valid output port;
[0057] S402 enables the primary ring master node that has received the Major-Fault message to open a blocked service secondary port.
[0058] To illustrate this solution in detail, this embodiment describes a scenario where multiple sub-rings intersect with a main ring and a public link and a non-public link of the main ring fail simultaneously.
[0059] Multiple sub-rings intersect with the main ring, such as Figure 5 The network diagram can be summarized as follows. Circles represent unrelated switches or RRPP transmission nodes in the network. Edge nodes periodically send Edge-Hello messages to auxiliary edge nodes via the public and non-public links of the primary ring.
[0060] When the public link of the primary ring and one or more non-public links fail at the same time, the primary ring link between the edge node and the auxiliary edge node will be completely disconnected.
[0061] In this embodiment, the administrator may refer to an edge node on a sub-ring, such as Figure 5 As shown, the Edge node is designated as the edge node of the sub-ring, and the corresponding Assistant edge node of the sub-ring connected through the public link of the main ring is the auxiliary edge node of the sub-ring.
[0062] In this embodiment, the Edge node sends EdgeHello messages through the public links of the primary ring and the non-public links of the primary ring. Under normal circumstances, the Assistant edge node can receive the Edge Hello message within the specified time. However, if the public links of the primary ring and the non-public links of the primary ring fail at the same time, the Assistant edge node will no longer be able to receive the Edge Hello message within the specified time. Therefore, in this embodiment, if the Assistant edge node does not receive the Edge Hello message within the specified time, the Assistant edge node can determine that the public links of the primary ring and the non-public links of the primary ring have both failed.
[0063] In step S401, when the auxiliary edge node (i.e., the auxiliary edge node of the sub-ring) identifies that both the public link of the primary ring and the non-public link of the primary ring have failed, the auxiliary edge node sends a Major-Fault message to all RRPP ports (valid ports), that is, it sends the Major-Fault message to the public ports and all edge ports of the primary ring, so that all master nodes in the RRPP domain can receive the Major-Fault message (i.e., all nodes except the failed node or the link-unreachable node receive the Major-Fault message).
[0064] like Figure 6 As shown in the figure, when the two edge nodes (assistant edge nodes) are reachable to the master node, the Assistant edge node (assistant edge node) sends the Major-Fault message to the Master node (master node in the main ring) in the direction of the arrow.
[0065] When the network is normal, the Master node usually blocks the service port S to prevent service loops. In this example, when the Master node receives the Major-Fault message, it opens the service port S to enable the transmission of service messages.
[0066] It can be seen from the above embodiments that in this embodiment, when the auxiliary edge node identifies that the public link of the main ring and the non-public link of the main ring fail at the same time, the auxiliary edge node can send a Major-Fault message to the main node in the main ring. When the main node (the main node in the main ring) receives the Major-Fault message, it can open the blocked service port to ensure the transmission of the service message. Since the main node does not need to wait for the Hello message to time out, it can release the service secondary port of the main node, which effectively improves the convergence speed of the main node.
[0067] To accommodate the solution disclosed herein, when an edge node (an edge node on a subring) receives a Major-Fault message from an auxiliary edge port, it not only maintains the original RRPP protocol's blocked edge port but also forwards the message to the public port on the primary ring. To reduce the number of Major-Fault messages sent to the primary ring, the edge node can forward only Major-Fault messages from a single subring in the ring group.
[0068] In the original RRPP protocol, the transit nodes on the primary ring will not receive the Major-Fault message. In this embodiment, the transit nodes on the primary ring are added to process the Major-Fault message, that is, forward it along the RRPP ring.
[0069] The transit node on the sub-ring maintains consistency with the original RRPP protocol and continues to forward the Major-Fault message along the RRPP ring.
[0070] The master node on a subring maintains RRPP forwarding for Major-Fault messages. To prevent temporary loops caused by edge nodes not blocking their secondary ports in time to release them, the subring master node starts a very short Release-Delay timer (for example, 1ms) after receiving a Major-Fault message. This timer provides time for the edge node to block its edge port. After the Release-Delay expires, the master node releases the secondary port and sends a Common-Flush-FDB message to notify the subring transit nodes, prompting them to update their respective MAC address and ARP / ND entries.
[0071] In the original RRPP protocol, the master node on the primary ring would not receive Major-Fault messages. In this embodiment, when the master node on the primary ring receives a Major-Fault message, it directly releases the secondary port and sends a Common-Flush-FDB message to the primary ring, without waiting for the Hello message to time out. To ensure protocol consistency, the master node on the sub-ring also transparently transmits Major-Fault messages, as does the master node on the sub-ring.
[0072] by Figure 6 As shown in Figure a, after the Edge-Hello timeout, the auxiliary edge node sends a Major-Fault message. After receiving this message, all sub-ring master nodes wait for the Release-Delay to release their secondary ports and begin sending Common-Flush-FDB messages. Upon receiving the Major-Fault message, the edge port blocks the edge port and transparently transmits the Major-Fault message from a sub-ring to the main ring. Upon receiving the Major-Fault message, the master node in the main ring also releases its secondary port and sends a Common-Flush-FDB message, completing the ring convergence. Compared to traditional RRPP, the ring convergence time is shortened to the Edge-Hello timeout + the Release-Delay.
[0073] Based on the above method embodiment, the present disclosure also provides a method for handling RRPP multi-ring failures. The method is applied to a master edge node of a sub-ring, and the method includes:
[0074] Receive a Major-Fault message sent by an auxiliary edge node of a sub-ring, wherein the Major-Fault message is sent by the auxiliary edge node of the sub-ring when the auxiliary edge node of the sub-ring identifies that a public link of the main ring and a non-public link of the main ring are simultaneously faulty;
[0075] After the waiting delay time expires, the Major-Fault message is sent to the primary ring, so that the master node of the primary ring opens the blocked service secondary port after receiving the Major-Fault message.
[0076] Based on the above method embodiment, the present disclosure further provides a method for handling RRPP multi-ring failures. The method is applied to a master node of a primary ring, and the method includes:
[0077] Receiving a Major-Fault message sent by the auxiliary edge node, wherein the Major-Fault message is sent through each valid output port when the auxiliary edge node identifies that the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty;
[0078] Open the blocked secondary service port based on the Major-Fault message.
[0079] Based on the above method embodiments, an embodiment of the present disclosure further provides a network device, wherein the network device is placed in an auxiliary edge node of a sub-ring in an RRPP multi-ring, and the network device includes:
[0080] An identification module, configured to identify whether the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty;
[0081] The sending module is used to send a Major-Fault message through each valid output port when it is identified that the public link and the non-public link of the primary ring fail at the same time, so that the primary ring master node that receives the Major-Fault message opens the blocked service secondary port.
[0082] The identification module is specifically configured to determine that both the public link of the primary ring and the non-public link of the primary ring are faulty when the auxiliary edge node does not receive an Edge-Hello message sent by the edge node within a preset time.
[0083] Wherein, the network device further includes:
[0084] The determination module is used to determine the auxiliary edge node.
[0085] Based on the above method embodiments, an embodiment of the present disclosure further provides a network device, which is placed at a master edge node of a sub-ring, and includes:
[0086] A receiving module, configured to receive a Major-Fault message sent by an auxiliary edge node of a sub-ring, wherein the Major-Fault message is sent when the auxiliary edge node of the sub-ring identifies that a public link of the main ring and a non-public link of the main ring are simultaneously faulty;
[0087] The sending module is used to send the Major-Fault message to the primary ring after the delay time expires, so that the master node of the primary ring opens the blocked service secondary port after receiving the Major-Fault message.
[0088] Based on the above method embodiments, an embodiment of the present disclosure further provides a network device, which is placed at a master node of a primary ring and includes:
[0089] A receiving module, configured to receive a Major-Fault message sent by an auxiliary edge node, wherein the Major-Fault message is sent by the auxiliary edge node through each valid output port when the auxiliary edge node identifies that the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty;
[0090] The processing module is used to open the blocked service secondary port according to the Major-Fault message.
[0091] 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.
[0092] 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.
[0093] 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.
[0094] 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.
[0095] 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 multi-ring failures, characterized in that: The method is applied to an auxiliary edge node of a sub-ring, and the method includes: When it is identified that both the public link and the non-public link of the primary ring are faulty at the same time, a Major-Fault message is sent through each valid output port; The primary ring master node that receives the Major-Fault message opens the blocked service secondary port.
2. The method according to claim 1, characterized in that The method for identifying simultaneous failures of the public links and non-public links of the primary ring includes: When the auxiliary edge node does not receive the Edge-Hello message sent by the edge node within a preset time, it is determined that both the public link of the primary ring and the non-public link of the primary ring are faulty.
3. The method according to claim 1, characterized in that Methods for determining auxiliary edge nodes include: An edge node of a sub-ring is determined, and another sub-ring node connected to the edge node via a public link is designated as an auxiliary edge node.
4. A method for handling RRPP multi-ring failures, characterized in that: The method is applied to a master edge node of a sub-ring, and includes: Receive a Major-Fault message sent by an auxiliary edge node of a sub-ring, wherein the Major-Fault message is sent by the auxiliary edge node of the sub-ring when the auxiliary edge node of the sub-ring identifies that a public link of the main ring and a non-public link of the main ring are simultaneously faulty; After the waiting delay time expires, the Major-Fault message is sent to the primary ring, so that the master node of the primary ring opens the blocked service secondary port after receiving the Major-Fault message.
5. A method for handling RRPP multi-ring failures, characterized in that: The method is applied to the master node of the primary ring, and the method includes: Receiving a Major-Fault message sent by the auxiliary edge node, wherein the Major-Fault message is sent through each valid output port when the auxiliary edge node identifies that the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty; Open the blocked secondary service port based on the Major-Fault message.
6. A network device, characterized in that: The network device is placed in an auxiliary edge node of a sub-ring in an RRPP multi-ring, and the network device includes: An identification module, configured to identify whether the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty; The sending module is used to send a Major-Fault message through each valid output port when it is identified that the public link and the non-public link of the primary ring fail at the same time, so that the primary ring master node that receives the Major-Fault message opens the blocked service secondary port.
7. The network device according to claim 6, wherein: The identification module is specifically configured to determine that both the public link of the primary ring and the non-public link of the primary ring are faulty when the auxiliary edge node does not receive the Edge-Hello message sent by the edge node within a preset time.
8. The network device according to claim 6, wherein: The network device further includes: The determination module is used to determine the auxiliary edge node.
9. A network device, characterized in that: The network device is placed at the primary edge node of the sub-ring, and the network device includes: A receiving module, configured to receive a Major-Fault message sent by an auxiliary edge node of a sub-ring, wherein the Major-Fault message is sent when the auxiliary edge node of the sub-ring identifies that a public link of the main ring and a non-public link of the main ring are simultaneously faulty; The sending module is used to send the Major-Fault message to the primary ring after the delay time expires, so that the master node of the primary ring opens the blocked service secondary port after receiving the Major-Fault message.
10. A network device, characterized in that: The network device is placed at the master node of the primary ring, and the network device includes: A receiving module, configured to receive a Major-Fault message sent by an auxiliary edge node, wherein the Major-Fault message is sent by the auxiliary edge node through each valid output port when the auxiliary edge node identifies that the public link of the primary ring and the non-public link of the primary ring are simultaneously faulty; The processing module is used to open the blocked service secondary port according to the Major-Fault message.