A method, network device and system for MRP redundant domain link fault processing

Abstract

The embodiment of the application provides a kind of MRP redundancy domain link failure processing method, network device and system, it is related to network technical field, it is applied to first network device, above-mentioned method includes: after determining that first port fails, it is judged whether first message is received within first preset time length, first message is broadcasted in first MRP redundancy domain after second network device determines that second port is in failure state;In the case where first network device is MIM device in MRP interconnection domain, the state of first interconnection port is switched to the forwarding state of allowing forwarding message;In the case where first network device is not MIM device in MRP interconnection domain, second message is sent to MIM device, to make MIM device switch the state of second interconnection port of itself to forwarding state.The scheme provided in the embodiment of the application can make data message normal forwarding as far as possible when multiple links in MRP redundancy domain fail.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a method, network device and system for handling MRP redundant domain link failures. Background Technology

[0002] MRP (Media Redundancy Protocol) interconnection domains are loops formed by connecting different MRP redundancy domains through links. An MRP redundancy domain is a ring link formed by interconnecting MRP-enabled network devices. See also Figure 1 This diagram illustrates an MRP redundancy domain. It includes network devices A through I. The solid lines representing the interconnected ring links formed by network devices A, B, C, D, E, and F, and the dashed lines representing the interconnected ring links, represent MRP redundancy domain 1, and MRP redundancy domain 2, respectively. In other words, the same group of network devices can form different ring links through different ports, thus achieving different MRP redundancy domains. For example, ports 1 and 2 on network device A belong to MRP redundancy domain 1, while ports 3 and 4 belong to MRP redundancy domain 2. Furthermore, the ring link formed by network devices A, G, H, and I represents MRP redundancy domain 3.

[0003] See Figure 2 This diagram illustrates an MRP interconnection domain. Network devices A through H form MRP redundancy domain 1, network devices I through P form redundancy domain 2, network devices B and J are connected, and network devices C and K are connected. Network devices B, C, J, and K together form an MRP interconnection domain. As shown, an MRP interconnection domain can connect different MRP redundancy domains. Ports on network devices within an MRP interconnection domain that connect to another MRP redundancy domain are called interconnection ports. For example, a port on network device B connected to network device J is an interconnection port, and a port on network device J connected to network device B is an interconnection port.

[0004] In an MRP interconnect domain, one network device acts as the Media Redundancy Interconnection Manager (MIM) for monitoring loops and controlling links. When no link failure occurs in the MRP interconnect domain, the MIM's interconnect ports are in a blocked state, and these ports do not transmit data packets. Other network devices in the MRP interconnect domain (i.e., Media Redundancy Interconnection Clients) are in a forwarding state, capable of forwarding data packets. This prevents data packets from continuously looping and being forwarded within the MRP interconnect domain, thus preventing broadcast storms. For example, Figure 2 In this example, network device B is a MIM (Multi-Instrument Machine). When no fault occurs in the MRP interconnection domain, the interconnection port on network device B (i.e., the port on network device B connected to network device J) is in a blocked state, preventing data packets from being sent in a loop within the MRP interconnection domain. If the interconnection port on any network device in the MRP interconnection domain fails, the interconnection port on network device B enters a forwarding state, enabling data packet forwarding. This ensures that data packets can still be forwarded normally even in the event of a fault. For example, if the interconnection port of network device C fails, the interconnection port on network device B switches to the forwarding state. Thus, although network device C cannot directly send data packets to network device K through the failed interconnection port, it can still send data packets to network device K via the path: network device C - network device B - network device J - network device K. This achieves fault handling.

[0005] However, if Figure 2 If a link failure occurs between network devices B and C, the interconnect port status of the MIM will not change because the interconnect port itself is not faulty. However, since network devices B and C are in MRP redundancy domain 1, MRP redundancy domain 1 can function normally. Network devices B and C can communicate normally via the path: network device B-network device A-network device H-network device G-network device F-network device E-network device D-network device C. However, if MRP redundancy domain 1 contains multiple link failures or multiple port failures, such as a link failure between network devices B and C, or a link failure between network devices A and H, then network devices in MRP redundancy domain 1 may not be able to communicate normally; for example, network devices H and B may not be able to communicate. Therefore, it is necessary to address the problem of data packet forwarding failure when multiple links in the MRP redundancy domain fail. Summary of the Invention

[0006] The purpose of this application is to provide a method, network device, and system for handling link failures in an MRP redundancy domain, so as to ensure that data packets can be forwarded normally as much as possible when multiple links in an MRP redundancy domain fail. The specific technical solution is as follows:

[0007] In a first aspect, embodiments of this application provide an MRP interconnection domain fault handling method, applied to a first network device in a first Media Redundancy Protocol (MRP) redundancy domain. A first interconnection port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are ring links formed by sequentially connecting different network devices. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnection domain, a first port of the first network device is connected to a second port of the second network device. The method includes:

[0008] After determining that the first port is faulty, it is determined whether a first message is received within a first preset time period, wherein the first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state;

[0009] If the first message is not received within the first preset time period, and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain, the state of the first interconnect port is switched to the forwarding state that allows message forwarding.

[0010] If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

[0011] In one embodiment of this application, after switching the state of the first interconnect port to a forwarding state that allows message forwarding, or after sending the second message to the MIM device through the MRP interconnect domain, the method further includes:

[0012] If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets.

[0013] If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

[0014] In one embodiment of this application, the method further includes:

[0015] If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

[0016] In one embodiment of this application, the method further includes:

[0017] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets.

[0018] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

[0019] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0020] Secondly, embodiments of this application provide a network device, which serves as a first network device in a first Media Redundancy Protocol (MRP) redundancy domain. A first interconnect port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are ring links formed by sequentially connecting different network devices. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnect domain, a first port of the first network device is connected to a second port of the second network device. The first network device includes:

[0021] A processor; a transceiver; a machine-readable storage medium storing machine-executable instructions that can be executed by the processor, the machine-executable instructions causing the processor to perform the following steps:

[0022] After determining that the first port is faulty, it is determined whether a first message is received within a first preset time period, wherein the first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state;

[0023] If the first message is not received within the first preset time period, and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain, the state of the first interconnect port is switched to the forwarding state that allows message forwarding.

[0024] If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

[0025] In one embodiment of this application, after switching the state of the first interconnect port to a forwarding state that allows message forwarding, or after sending the second message to the MIM device through the MRP interconnect domain, the machine-executable instructions further cause the processor to perform the following steps:

[0026] If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets.

[0027] If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

[0028] In one embodiment of this application, the machine-executable instructions further cause the processor to perform the following steps:

[0029] If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

[0030] In one embodiment of this application, the machine-executable instructions further cause the processor to perform the following steps:

[0031] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets.

[0032] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

[0033] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0034] Thirdly, embodiments of this application provide an MRP interconnection domain fault handling system, the system including a first network device and a second network device in a first Media Redundancy Protocol (MRP) redundancy domain;

[0035] The first interconnection port of the first network device is directly connected to the network device in the second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are respectively ring links composed of different network devices connected in sequence. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form a ring link. As an MRP interconnection domain, the first port of the first network device is connected to the second port of the second network device.

[0036] The second network device is configured to broadcast a first message in the first MRP redundancy domain after determining that the second port is faulty;

[0037] The first network device is configured to, after determining that the first port is faulty, determine whether a first packet has been received within a first preset time period; if the first packet is not received within the first preset time period, and if the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP Interconnect Domain, switch the state of the first interconnect port to a forwarding state that allows packet forwarding; if the first packet is not received within the first preset time period, and if the first network device is not a MIM device in the MRP Interconnect Domain, send a second packet to the MIM device through the MRP Interconnect Domain, so that the MIM device switches the state of its second interconnect port to a forwarding state.

[0038] In one embodiment of this application, after switching the state of the first interconnect port to a forwarding state that allows message forwarding, or after sending a second message to the MIM device through the MRP interconnect domain, the first network device is further configured to:

[0039] If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets.

[0040] If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

[0041] In one embodiment of this application, the first network device is further configured to:

[0042] If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

[0043] In one embodiment of this application, the first network device is further configured to:

[0044] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets.

[0045] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

[0046] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0047] Fourthly, this application provides an MRP interconnection domain fault handling device, applied to a first network device in a first Media Redundancy Protocol (MRP) redundancy domain. A first interconnection port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are ring links formed by sequentially connecting different network devices. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnection domain, a first port of the first network device is connected to a second port of the second network device. The device includes:

[0048] The message receiving judgment module is used to determine whether a first message has been received within a first preset time period after determining that the first port is faulty. The first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state.

[0049] The port switching module is used to switch the state of the first interconnect port to a forwarding state that allows forwarding packets if the first packet is not received within the first preset time period and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain.

[0050] The second message sending module is used to send a second message to the MIM device through the MRP interconnection domain if the first message is not received within the first preset time period and the first network device is not a MIM device in the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

[0051] In one embodiment of this application, the apparatus further includes:

[0052] The port recovery module is used to switch the state of the first interconnect port to a blocked state that does not allow forwarding data packets if the first packet is received and the first network device is a MIM device in the MRP interconnect domain.

[0053] The third message sending module is configured to, if the first message is received and the first network device is not a MIM device in the MRP interconnection domain, send a third message to the MIM device in the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to a blocked state.

[0054] In one embodiment of this application, the apparatus further includes:

[0055] The first port holding module is configured to, if the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, keep the port that has returned to normal in a blocked state for a second preset time period, and then switch the port that has returned to normal to a forwarding state.

[0056] In one embodiment of this application, the apparatus further includes:

[0057] The second port holding module is used to maintain the state of the first interconnect port as a blocked state that does not allow forwarding data packets if the first packet is received within the first preset time period after the first port is determined to be faulty, and the first network device is a MIM device in the MRP interconnect domain.

[0058] The third port holding module is used to send a third message to the MIM device if, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, so that the MIM device keeps its second interconnection port in a blocked state.

[0059] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0060] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the methods described in the first aspect.

[0061] In a sixth aspect, embodiments of this application also provide a computer program product containing instructions that, when run on a computer, cause the computer to perform any of the steps described in the first aspect above.

[0062] Beneficial effects of the embodiments in this application:

[0063] In the MRP redundancy domain link failure handling method provided in this application embodiment, the first network device and the second network device are located in the first MRP redundancy domain and are both directly connected to network devices in the second MRP redundancy domain. It can be seen that in the scenario of this application embodiment, there is an MRP interconnection domain between the first MRP redundancy domain and the second MRP redundancy domain, and the first network device and the second network device are located in the MRP interconnection domain. The first port of the first network device and the second port of the second network device are connected. Therefore, if the link between the first network device and the second network device fails, both the first port and the second port will fail. In this case, the second network device broadcasts a first message, and the first network device waits to receive it. Since both the first network device and the second network device are located in the first MRP redundancy domain, if only the link between the first network device and the second network device fails in the first MRP redundancy domain, then based on the characteristics of the first MRP redundancy domain, the first message can still be sent to the first network device along the ring link. However, if the first network device does not receive the first message within a first preset time period, it indicates that there is more than one link failure in the first MRP redundancy domain. In this scenario, if the first network device is a MIM device within the MRP interconnection domain, the first interconnection port is directly switched to forwarding mode. If the first network device is not a MIM device within the MRP interconnection domain, a first message is sent to the MIM device through the MRP interconnection domain, causing the MIM device to switch its second interconnection port to forwarding mode. This opens a path for data packet transmission between the first and second MRP redundancy domains. Therefore, when multiple link failures in the first MRP redundancy domain affect the normal transmission of data packets, the ring link provided by the MRP interconnection domain and the second MRP redundancy domain can be used for packet forwarding. This ensures that data packets can be forwarded normally as much as possible when multiple links fail in the first MRP redundancy domain. Attached Figure Description

[0064] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other embodiments can be obtained based on these drawings.

[0065] Figure 1 This is a schematic diagram of an MRP redundancy domain;

[0066] Figure 2 This is a schematic diagram of an MRP interconnection domain;

[0067] Figure 3 A schematic diagram illustrating the first type of MRP_InTopologyChange message transmission provided in this application embodiment;

[0068] Figure 4 This is a schematic diagram illustrating the second type of MRP_InTopologyChange message transmission provided in an embodiment of this application.

[0069] Figure 5 This application provides a schematic diagram of a packet forwarding path in an MRP interconnection domain under normal link conditions, as illustrated in an embodiment of the present application.

[0070] Figure 6 This application provides a schematic diagram of a packet forwarding path in an MRP interconnection domain under link failure conditions, as illustrated in an embodiment of the present application.

[0071] Figure 7 This is a schematic diagram illustrating a method for a MIC device to forward MRP protocol messages, provided in an embodiment of this application.

[0072] Figure 8 This is a schematic diagram illustrating the first application scenario provided in the embodiments of this application;

[0073] Figure 9 A flowchart illustrating the first MRP redundant domain link failure handling method provided in this application embodiment;

[0074] Figure 10 This is a schematic diagram illustrating a second application scenario provided in the embodiments of this application;

[0075] Figure 11 This is a schematic diagram illustrating a third application scenario provided in the embodiments of this application;

[0076] Figure 12 A flowchart illustrating the second MRP redundant domain link failure handling method provided in this application embodiment;

[0077] Figure 13 This is a schematic diagram illustrating the fourth application scenario provided in the embodiments of this application;

[0078] Figure 14 A flowchart illustrating the third MRP redundant domain link failure handling method provided in this application embodiment;

[0079] Figure 15 This is a schematic diagram illustrating the fifth application scenario provided in the embodiments of this application;

[0080] Figure 16 This application provides a schematic diagram of the structure of a network device.

[0081] Figure 17 This is a schematic diagram of the structure of an MRP interconnection domain fault handling device provided in an embodiment of this application. Detailed Implementation

[0082] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art based on this application are within the scope of protection of this application.

[0083] To better illustrate the application scenarios of this application, the MRP redundancy domain and MRP interconnection domain in related technologies are first described.

[0084] First, the network structure of the MRP redundancy domain can be found in [reference needed]. Figure 1 , Figure 1 The diagram illustrates redundant domains 1 and 2, each containing six network devices, and redundant domain 3, containing four network devices. It should be noted that these redundant domains are merely examples; any network devices that can form a ring link can constitute a redundant domain. Different VLANs (Virtual Local Area Networks) are used in different MRP redundant domains to carry MRP protocol messages. The identification of an MRP redundant domain includes three types: Redundant Domain ID, Redundant Domain Name, and Redundant Domain UUID (Universally Unique Identifier). The Redundant Domain ID and Redundant Domain Name are only used locally on the network device to distinguish different MRP redundant domains, while the UUID is a unique identifier for the MRP redundant domain throughout the entire network. The same network device can belong to different MRP redundant domains, for example... Figure 1 The network device A shown is located in MRP redundancy domain 1, MRP redundancy domain 2 and MRP redundancy domain 3.

[0085] An MRP redundancy domain includes MRM (Media Redundancy Manager) devices, MRC (Media Redundancy Client) devices, and MRA (Media Redundancy Automanager) devices. The same network device can function as different devices and perform different functions in different MRP redundancy domains. For example, Figure 1 Network device A is an MRM device in MRP redundancy domain 1 and an MRC device in MRP redundancy domain 2.

[0086] In the MRP redundancy domain, the MRM device plays a role in monitoring and controlling links. Only one MRM device exists in an MRP redundancy domain at a time. The MRM device reacts to link failures within the MRP redundancy domain. When there is no fault in the MRP redundancy domain, one ring port on the MRM device is in a blocked state; this ring port is the port on the MRM device that connects to other network devices in the MRP redundancy domain. This prevents all ports in the MRP redundancy domain from forwarding data packets, thus avoiding a broadcast storm caused by continuous packet looping. However, once a link failure is detected in the MRP redundancy domain, the ring port is switched to a forwarding state to handle the link failure.

[0087] For example, if Figure 1 In MRP Redundancy Domain 1, network device A is an MRM device. When no link failure occurs in MRP Redundancy Domain 1, port 2 of network device A is in the Block state. This allows data packets sent by network device A to be sent along the path of network device A-network device B-network device C-network device D-network device E-network device F, but they will not be sent back to network device A, preventing a circular forwarding. However, if the link between network devices C and D fails, port 2 of network device A switches back to the Forwarding state, enabling data packet forwarding. The path from network device C-network device B-network device A-network device F-network device E remains connected, allowing normal packet forwarding. Furthermore, due to the link failure between network devices C and D, a data packet forwarding loop is not formed, preventing the continuous circular forwarding of data packets.

[0088] MRC devices are network devices other than MRM devices in the MRP redundancy domain. MRC devices monitor the status of their own ring network ports to determine whether they are functioning correctly or faulty. If the status changes, they notify the MRM device, enabling the MRM device to identify link failures within the MRP redundancy domain. It's important to note that when an MRM device's ring network port is in a Blocked state, it will not forward data packets, but it will forward MRP protocol messages. MRC devices communicate the status of their ring network ports to the MRM device via MRP protocol messages.

[0089] When the MRM device is running normally, the MRA device performs tasks as the MRC device. In the event of a failure of the current MRM device, an election is held, and the only device elected from the MRA devices becomes the new MRM device, thereby improving the stability of the MRP redundancy domain.

[0090] The MRP interconnect domain includes MIM devices and MIC devices.

[0091] The MIM device plays a role in monitoring and controlling links within the MRP interconnect domain. The MIM device responds to link failures within the MRP interconnect domain. When there is no fault in the MRP interconnect domain, the interconnect ports on the MIM device are in a blocked state. These interconnect ports are the ports on the MIM device that connect to network devices in another MRP redundancy domain. This prevents all ports in the entire MRP interconnect domain from forwarding data packets, thus avoiding a broadcast storm caused by continuous packet looping within the MRP interconnect domain. However, upon determining that a link failure has occurred in the MRP interconnect domain, the interconnect ports are switched to a forwarding state to address the link failure.

[0092] For example, if Figure 2 In MRP Redundancy Domain 1, network device B is a MIM device. When no link failure occurs in MRP Interconnection Domain 1, the interconnection port of network device B is in the Block state. This allows data packets sent by network device B to be sent along the path of network device B-network device C-network device K-network device J, but they will not be sent back to network device B, preventing a circular forwarding. However, if the link between network devices C and K fails, the interconnection port of network device B switches back to the Forwarding state, enabling data packet forwarding. The path from network device C-network device B-network device J-network device K remains connected, allowing normal packet forwarding. Furthermore, due to the link failure between network devices C and K, a data packet forwarding loop is not formed, preventing the continuous circular forwarding of data packets.

[0093] The MIC (Micro-Interface) device is any network device in the MRP interconnection domain other than the MIM (Membership Instrumentation) device. The MIC monitors the status of its own interconnection ports, checking for normal operation or failure. If the status changes, it notifies the MIM device, enabling the MIM device to determine the fault status of the interconnection ports within the MRP interconnection domain. It's important to note that when the MIM device's interconnection port is in a Blocked state, it will not forward data packets, but it will forward MRP protocol messages. The MIC device communicates the status of its interconnection ports to the MIM device via MRP protocol messages.

[0094] In this embodiment, the MIM device and MIC device operate in the MRP interconnect domain based on the LC (LinkCheck) mode. In this mode, the MIC device in the MRP interconnect domain collects the status of its directly connected interconnect links (links connecting different MRP redundancy domains) and feeds the detection results back to the MIM device for aggregation. The MIM device then adjusts the status of its own interconnect ports based on the aggregated results.

[0095] The specific process is as follows: After the MIM device determines that its interconnect port is in a normal UP state, it sets the interconnect port to the Blocked state and sends an MRP_InLinkStatusPoll (MRP InLink Status Polling) message from its own ring network port. The MRP_InLinkStatusPoll message is used to notify the MIC device to send its own detection results on whether the interconnect port is faulty, so as to facilitate the MIM device to collect the MRP interconnect domain link status.

[0096] After receiving the MRP_InLinkStatusPoll message, the MIC device sends an MRP_InLinkChange (MRP Inbound Link Change) message from its own ring network port according to the status of its own interconnection port. There are two types of MRP_InLinkChange messages: one is the MRP_InLinkUp (MRP Inbound Link Normal) message sent by the MIC device when it determines that its own interconnection port is in a normal UP state, and the other is the MRP_InLinkDown (MRP Inbound Link Fault) message sent by the MIC device when it determines that its own interconnection port is in a fault Down state.

[0097] The MIM device manages the MRP interconnection domain based on the received MRP_InLinkChange messages. Specifically: if the MIM device does not receive an MRP_InLinkDown message, it determines that the link status of the MRP interconnection domain is good, sets its own interconnection port to the Blocked state, and sends an MRP_InTopologyChange (MRP topology change) message through its own ring network port and interconnection port. If the MIM device receives an MRP_InLinkDown message, it determines that there is a link failure in the MRP interconnection domain. It sets its own interconnection port to the Forwarding state and sends an MRP_InTopologyChange message through its own ring network port and interconnection port.

[0098] See Figure 3 This is a schematic diagram of the first type of MRP_InTopologyChange message transmission provided in the embodiments of this application.

[0099] Figure 3 This includes the MIM and MIC1-MIC3. Under normal link conditions, the MIM sends MRP_InTopologyChange messages in the direction shown by the arrows. The circles on the interconnect ports of the MIM in the diagram indicate that they are in the Blocked state.

[0100] See Figure 4This is a schematic diagram of the second type of MRP_InTopologyChange message transmission provided in the embodiments of this application.

[0101] Figure 4 Network structure and Figure 3 The diagram shows the same pattern. The difference is a link failure between MIC1 and MIC2. The MIM sends MRP_InTopologyChange messages in the direction indicated by the arrows. The squares on the interconnect ports of the MIM in the diagram indicate that they are in the Forwarding state.

[0102] Upon receiving the MRP_InTopologyChange message, network devices in the MRP interconnection domain and devices in the MRP redundancy domain where the MIM device resides clear their own FDB (Forwarding Database) to relearn the MAC (Media Access Control) addresses after the MRP interconnection topology change. When a MIC device receives the MRP_InTopologyChange message, if its interconnection port is in a normal Up state, it sets that interconnection port to the Forwarding state.

[0103] When the MIC device detects a change in the link status of its own interconnect port, it will still send the corresponding MRP_InLinkChange message to notify the MIM device.

[0104] The MRP_InLinkStatusPoll, MRP_InLinkChange, and MRP_InTopologyChange messages mentioned above are all MRP protocol messages.

[0105] See Figure 5 This is a schematic diagram of a message forwarding path in an MRP interconnection domain under normal link conditions, provided by an embodiment of this application.

[0106] Figure 5 This includes the MIM and MIC1-MIC3. Under normal link conditions, the solid black arrows indicate the path through which MIC2 sends MRP_InLinkUp messages to the MIM. The dashed arrows indicate the path through which MIC3 sends MRP_InLinkUp messages to the MIM. The white arrows indicate the path through which MIC1 sends MRP_InLinkUp messages to the MIM.

[0107] See Figure 6 This is a schematic diagram of a message forwarding path in an MRP interconnection domain under a link failure situation, provided by an embodiment of this application.

[0108] Figure 6Network structure and Figure 5 The difference lies in the link failure between MIC1 and MIC2, which causes a failure in the interconnection port between MIC1 and MIC2. Therefore, MIC1 and MIC2 need to send MRP_InLinkDown messages to the MIM. The white arrow in the diagram indicates the path through which MIC1 sends MRP_InLinkDown messages to the MIM. The arrow in the diagram indicates the path through which MIC2 sends MRP_InLinkDown messages to the MIM.

[0109] MIC devices can forward various MRP protocol messages. The specific forwarding methods are as follows:

[0110] For MRP_InLinkStatusPoll messages, the MIC device will forward MRP_InLinkStatusPoll messages received from the ring network port to the interconnect port, but will not forward MRP_InLinkStatusPoll messages received from the interconnect port.

[0111] For MRP_InLinkChange messages, the MIC device will forward MRP_InLinkChange messages received from the ring network port to the interconnect port, but will not forward MRP_InLinkChange messages received from the interconnect port.

[0112] For MRP_InTopologyChange messages, the MIC device will forward MRP_InTopologyChange messages received from the interconnect port to the ring network port, but will not forward MRP_InTopologyChange messages received from the ring network port to the interconnect port.

[0113] See Figure 7 This is a schematic diagram illustrating a method for a MIC device to forward MRP protocol messages, as provided in an embodiment of this application.

[0114] Figure 7 The network structure is the same as the aforementioned Figure 3 Similarly, the solid black arrows indicate the forwarding path of the MRP_InLinkStatusPoll message, the dashed black arrows indicate the forwarding path of the MRP_InLinkChange message, and the white arrows indicate the forwarding path of the MRP_InTopologyChange message. It should be noted that the arrows in the diagram only represent a portion of the forwarding paths for these messages, not all of them. The MIC device shown in the diagram forwards MRP protocol messages in the same way as described above.

[0115] To more clearly describe the problems to be solved by the embodiments of this application, see [link to relevant documentation]. Figure 8This is a schematic diagram of the first application scenario provided in the embodiments of this application.

[0116] Figure 8 A1, B1, C1, and D1 in the MRP redundancy domain 1 form an MRP redundancy domain 1. Among them, A1 is the MRM in this MRP redundancy domain 1.

[0117] Figure 8 A2, B2, C2, and D2 in the MRP redundancy domain 2 form an MRP redundancy domain 2. D2 is the MRM in this MRP redundancy domain 2.

[0118] The ports marked with circles in the diagram are in the Blocked state.

[0119] Port P3 of A2 is connected to port P3 of A1, and port P3 of B2 is connected to port P3 of B1. A1, A2, B1, and B2 form an MRP interconnection domain, where B1 is the MIM. The P3 interfaces on A1, A2, B1, and B2 are their respective interconnection ports.

[0120] The link between A2 and B2 in the diagram is faulty, and the link between A2 and D2 is also faulty. Since none of these faults will cause the interconnect ports on A2, B2, A1, and B1 to fail, the interconnect port on B1, which is the MIM, remains in a blocked state.

[0121] Due to a link failure in MRP redundancy domain 2, D2, acting as the MRM, will switch its ring port P2, which was originally set to Blocked, to Forwarding. This allows D2 to communicate with C2 and B2 through port P2. However, due to multiple link failures in MRP redundancy domain 2, A2 and other network devices in MRP redundancy domain 2 still cannot communicate.

[0122] To address the aforementioned issues, this application provides an MRP redundant domain link failure handling method, network device, and system.

[0123] See Figure 9 This is a flowchart illustrating a first MRP redundancy domain link failure handling method provided in this application embodiment. A first network device is applied in a first MRP redundancy domain. The first interconnect port of the first network device is directly connected to a network device in a second MRP redundancy domain. The first and second MRP redundancy domains are ring links formed by sequentially connecting different network devices. The first and second network devices in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links, serving as MRP interconnection domains. The first port of the first network device is connected to the second port of the second network device.

[0124] The above method includes steps S901-S903.

[0125] S901: After determining that the first port is faulty, determine whether the first message has been received within the first preset time period.

[0126] The first message mentioned above is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state.

[0127] The first network device and the second network device are network devices in the first MRP redundancy domain that are connected to the second MRP redundancy domain; that is, both the first and second network devices are located in the MRP interconnection domain. Furthermore, the first port of the first network device in the first MRP redundancy domain is connected to the second port of the second network device, which is also located in the first MRP redundancy domain. This indicates that both the first and second ports are ring network ports, not interconnection ports. Moreover, a failure of the first port on the first network device indicates a link failure in the first MRP redundancy domain.

[0128] In this application, the link between the first network device and the second network device can be referred to as the common link between the first MRP redundancy domain and the MRP interconnection domain.

[0129] In one embodiment of this application, if the network devices at both ends of the public link determine that the port connecting them to the public link has failed, both can broadcast a first message in the first MRP redundancy domain. To distinguish between the first messages sent by the two devices, the first messages sent by the two devices can carry different preset identifiers. For example, using... Figure 8 Taking the network structure shown as an example, the first network device and the second network device can be respectively Figure 8 In B2 and A2, the first MRP redundancy domain is Figure 8 In MRP redundancy domain 2, the link between B2 and A2 is a common link. If the common link fails, both B2 and A2 can broadcast the first message. Correspondingly, when B2, as the first network device, waits to receive the first message, A2, as the second network device, sends the first message; when B2, as the second network device, sends the first message, A2, as the first network device, waits to receive the first message.

[0130] In another embodiment of this application, to save message transmission resources, it is possible to pre-set which network device at both ends of the common link broadcasts the first message and which waits to receive the first message. Then, the first network device will not broadcast the first message in the first MRP redundancy domain. The pre-set network device waiting to receive the first message is the first network device, and the pre-set network device sending the first message is the second device. For example, using... Figure 8Taking the illustrated embodiment as an example, it can be preset that B2 waits to receive the first message and A2 sends the first message. In this case, B2 is a fixed first network device and A2 is a fixed second network device.

[0131] After the first network device determines that the first port of its connection to the public link has failed, it starts the first timeout timer. The timeout duration of the first timeout timer is the first preset duration. If the first message is still not received after the first timeout timer expires, step S902 or step S903 is executed.

[0132] The aforementioned first message can be referred to as an Inter-Hello message, which carries a field with a fixed value at a fixed location, enabling the network device receiving the first message to determine that the received message is the first message based on this fixed value field. This application embodiment does not limit the specific location or value of the fixed value field.

[0133] As mentioned above, if a link in the first MRP redundancy domain fails, the MRM device in the first MRP redundancy domain will switch its ring network port, which is set to the Blocked state, to the Forwarding state to handle the link failure. However, if the first network device still cannot receive the first packet under these circumstances, it means that even if the MRM device performs the above processing, it still cannot resolve the link failure that occurred in the first MRP redundancy domain. Therefore, if the first packet is not received within the first preset time period, step S902 or step S903 needs to be executed, and the fault handling solution provided in the embodiment of this application is adopted.

[0134] S902: If the first message is not received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to the forwarding state that allows message forwarding.

[0135] In addition, when the first network device is a MIM device, after switching the first interconnect port to forwarding state, it is also necessary to send an MRP_InTopologyChange message through its own ring network port and the first interconnect port so that the network device that receives the MRP_InTopologyChange message can relearn the route. The specific process can be found in the previous description and will not be repeated here.

[0136] See Figure 10 This is a schematic diagram of a second application scenario provided in the embodiments of this application.

[0137] Figure 10 The application scenarios shown are Figure 8The only difference in the application scenarios shown is that the MIM in the MRP interconnect domain changes from B1 to B2, and the P3 port of B1 is no longer a blocked port.

[0138] In this application scenario, B2, as the first network device and a MIM (Multi-Instrument), experiences two link failures in MRP Redundancy Domain 2. B2 cannot receive the first packet sent by A2, therefore step S902 is executed. B2 sets its first interconnect port (P3) to forwarding mode. Under these conditions, the link between B2 and B1 is connected, enabling data packet forwarding. It is evident that before executing step S902, A2 could not transmit data packets to other network devices in MRP Redundancy Domain 2. After executing step S902, A2 and B2 can transmit data packets via the path A2-A1-B1-B2, A2 and C2 via the path A2-A1-B1-B2-C2, and A2 and D2 via the path A2-A1-B1-B2-D2. This resolves the problem of multiple link failures in MRP Redundancy Domain 2. Furthermore, no loops are formed in the network, preventing the continuous circular forwarding of data packets.

[0139] S903: If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

[0140] The second message mentioned above can be the aforementioned MRP_InLinkDown message. That is, even if the first interconnect port of the first network device does not fail, the first network device still sends an MRP_InLinkDown message to the MIM device indicating a failure of the first interconnect port, thereby triggering the MIM device to perform subsequent switching of the state of the second interconnect port and sending an MRP_InTopologyChange message. The specific processing flow of the MIM device after receiving the MRP_InLinkDown message can be found in the preceding description and will not be repeated here.

[0141] exist Figure 8 In the application scenario shown, if B2, as the first network device, cannot receive the first message sent by A2, it sends a second message to B1, which is the MIM device, so that B1 switches the state of the second interconnection port to the forwarding state.

[0142] Before executing step S903, A2 cannot transmit data packets to other network devices in MRP redundancy domain 2. After executing step S903, A2 and B2 can transmit data packets via the path A2-A1-B1-B2, A2 and C2 can transmit data packets via the path A2-A1-B1-B2-C2, and A2 and D2 can transmit data packets via the path A2-A1-B1-B2-D2. This solves the problem of multiple link failures in MRP redundancy domain 2. Moreover, no loops are formed in the network, and the problem of data packets being continuously forwarded in a loop is avoided.

[0143] In addition, if both network devices at both ends of the common link in this application embodiment are first network devices, for example, B2 and A2 are both first network devices, then both send a second message to the MIM device. Regardless of which network device sends the second message, the MIM device will switch the state of its second interconnection port to the forwarding state.

[0144] As can be seen from the above, the first network device and the second network device are located in the first MRP redundancy domain, and both are directly connected to network devices in the second MRP redundancy domain. It is evident that in the scenario of this application embodiment, an MRP interconnection domain exists between the first and second MRP redundancy domains, and the first and second network devices are located within the MRP interconnection domain. The first port of the first network device is connected to the second port of the second network device. Therefore, if the link between the first and second network devices fails, both the first and second ports will fail. In this case, the second network device broadcasts a first message, and the first network device waits to receive it. Since both the first and second network devices are located within the first MRP redundancy domain, if only the link between the first and second network devices fails within the first MRP redundancy domain, the first message can still be sent to the first network device along the ring link based on the characteristics of the first MRP redundancy domain. However, if the first network device does not receive the first message within a first preset time period, it indicates that there is more than one link failure in the first MRP redundancy domain. In this scenario, if the first network device is a MIM device within the MRP interconnection domain, the first interconnection port is directly switched to forwarding mode. If the first network device is not a MIM device within the MRP interconnection domain, a first message is sent to the MIM device through the MRP interconnection domain, causing the MIM device to switch its second interconnection port to forwarding mode. This opens a path for data packet transmission between the first and second MRP redundancy domains. Therefore, when multiple link failures in the first MRP redundancy domain affect the normal transmission of data packets, the ring link provided by the MRP interconnection domain and the second MRP redundancy domain can be used for packet forwarding. This ensures that data packets can be forwarded normally as much as possible when multiple links fail in the first MRP redundancy domain.

[0145] See Figure 11 This is a schematic diagram of a third application scenario provided in the embodiments of this application, which is consistent with the aforementioned Figure 8 Compared to the embodiment shown, the checkmark in the figure indicates fault recovery of the link between A2 and D2 mentioned above.

[0146] In this case, see Figure 12 This is a flowchart illustrating the second MRP redundant domain link failure handling method provided in this application embodiment, which is consistent with the aforementioned... Figure 9 Compared to the illustrated embodiment, step S902 is followed by step S904, and step S903 is followed by step S905. It should be noted that the second network device continuously sends the second message after determining that the second port has failed. Therefore, if the previously faulty link recovers, the first network device will be able to receive the first message.

[0147] S904: If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets.

[0148] As mentioned above Figure 10 As shown, if the link between A2 and D2 recovers from the failure, a loop will form between A1, A2, D2, C2, B2, and B1. Maintaining this loop will cause data packets to be continuously forwarded in a loop. To solve this problem, B2, acting as a MIM device, switches the state of its first interconnect port to a blocked state, thereby breaking the loop.

[0149] In addition to the above Figure 10 In addition to the link fault recovery between A2 and D2, if the link between A2 and B2 is restored to normal, or if the links between A2 and B2 and before A2 and D2 are all restored to normal, B2 can receive the first message sent by A2. In this case, B2 can determine that the link fault has been recovered, and a loop will also occur. In order to avoid the problem of data packet circular forwarding caused by the loop, B2, as a MIM device, switches the state of the first interconnection port to the blocked state.

[0150] After the first network device switches the state of the first interconnection port, it will send an MRP_InTopologyChange message as described above. The specific process will not be repeated here.

[0151] S905: If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

[0152] As mentioned above Figure 11 As shown, if the link between A2 and D2 recovers, a loop will form between A1, A2, D2, C2, B2, and B1. Maintaining this loop will cause data packets to be continuously forwarded in a loop. To solve this problem, the first network device (in...) Figure 11 In the illustrated embodiment, B2) sends a third message to the MIM device, causing the MIM device to switch the state of the second interconnect port to a blocked state. This third message can be the aforementioned MRP_InLinkUp message.

[0153] In addition to the above Figure 11 In addition to the link fault recovery between A2 and D2, if the link between A2 and B2 is restored to normal, or if the links between A2 and B2 and before A2 and D2 are all restored to normal, B2 will be able to receive the first message sent by A2. In this case, B2 can determine that the link fault has been recovered, and a loop will also occur. In order to avoid the problem of data packet circular forwarding caused by the loop, B2, as the first network device, needs to send a third message to the MIM device.

[0154] After the second network device switches the status of the second interconnection port, it will send an MRP_InTopologyChange message as described above. The specific process will not be repeated here.

[0155] In another embodiment of this application, since the process of the first network device switching the state of the first interconnect port as a MIM device and subsequently sending the MRP_InTopologyChange message takes time, or the first network device sending a third message to the MIM device as a non-MIM device also takes time for the MIM device to respond, a loop in the network can lead to the problem of data packets being continuously forwarded in a loop.

[0156] To avoid such problems, the first network device also performs the following step A.

[0157] Step A: If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

[0158] Specifically, after the first network device determines that its port has returned to normal, it can start a second timeout timer. The duration of the second timeout timer is a second preset duration. Before the second timeout timer expires, the port remains in a blocked state. After the second timeout timer expires, the port is switched to a forwarding state. This extends the time for the port to return to the forwarding state, allowing time for the MIM device to switch the state of the second interconnect port, and minimizing the risk of loop formation.

[0159] It should be noted that other network devices in the first MRP redundancy domain can also keep the restored ports in a blocked state for a second preset time period after confirming that their ports have returned to normal, and then switch the restored ports to a forwarding state.

[0160] If the first network device is a MIM device, it can determine that its own port has returned to normal and, after receiving the first packet, can directly switch its own first interconnection port to a blocking state, and then set the port that has returned to normal to a forwarding state.

[0161] As can be seen from the above, after the fault is recovered in the first MRP redundancy domain in this application, in order to avoid the formation of a loop in the network that causes data packets to be forwarded continuously, the MIM device will switch the state of its own interconnection port to a blocked state, thereby cutting off the loop and preventing data packet forwarding failure.

[0162] See Figure 13 This is a schematic diagram of the fourth application scenario provided in the embodiments of this application, and... Figure 8 Compared to the application scenarios shown, Figure 13 In the application scenario shown, a fault occurs only between A2 and B2. In this case, B2, as the first network device, can receive the first message sent by A2, and since there is only one link failure in MRP redundancy domain 2, the MRM device can handle the fault by adjusting the ring network port to forwarding state. Furthermore, if the MIM device (B1) switches the state of its interconnect port to forwarding state according to the scheme provided in this application embodiment, a loop of A1, B1, B2, C2, D2, and A2 will also be formed. Therefore, the handling method in this case is described below. Figure 14 .

[0163] See Figure 14 This is a flowchart illustrating the third MRP redundant domain link failure handling method provided in this application embodiment, which is consistent with the aforementioned... Figure 9 Compared to the embodiments shown, the above method further includes steps S906-S907, which are performed when the first network device receives the first message within a first preset time period.

[0164] S906: If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets.

[0165] S907: If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

[0166] As can be seen from the above, if the first network device can receive the first message, it means that the network device in the first MRP redundancy domain can still forward the message normally. Therefore, it does not need to rely on the network device in the second MRP redundancy domain for forwarding. The interconnection port of the MIM device can continue to remain blocked to prevent loop formation.

[0167] See Figure 15 This is a schematic diagram of the fifth application scenario provided in the embodiments of this application. Figure 15 Network structure and Figure 8 The network structures shown are the same, the difference is that Figure 15 The links that failed are the link between D2 and C2, and the link between A2 and D2. That is, the common link between A2 and B2 did not fail. In this case, the solution provided in this application embodiment is not executed. This is because if the solution provided in this application embodiment were executed, the interconnect port of B1 would switch to forwarding mode, forming a loop between A1, A2, B2, and B1, causing data packets to be continuously forwarded in a loop. Therefore, the solution provided in this application embodiment is not executed when the common link does not fail. The above is merely an example of a common link not failing; in this application, as long as the common link does not fail, the solution provided in this application embodiment does not need to be executed.

[0168] Corresponding to the aforementioned MRP redundant domain link failure handling method, this application embodiment also provides a network device.

[0169] See Figure 16This application provides a schematic diagram of a network device structure. The network device serves as a first network device in a first Media Redundancy Protocol (MRP) redundancy domain. A first interconnect port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first and second MRP redundancy domains are ring links formed by sequentially connecting different network devices. The first and second network devices in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnect domain, a first port of the first network device is connected to a second port of the second network device. The first network device includes:

[0170] Processor 1601;

[0171] Transceiver 1604;

[0172] A machine-readable storage medium 1602 stores machine-executable instructions that can be executed by the processor 1601, the machine-executable instructions causing the processor 1601 to perform the following steps:

[0173] After determining that the first port is faulty, it is determined whether a first message is received within a first preset time period, wherein the first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state;

[0174] If the first message is not received within the first preset time period, and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain, the state of the first interconnect port is switched to the forwarding state that allows message forwarding.

[0175] If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

[0176] like Figure 16As shown, the network device may also include a communication bus 1603. The processor 1601, machine-readable storage medium 1602, and transceiver 1604 communicate with each other via the communication bus 1603. The communication bus 1603 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus 1603 can be divided into an address bus, a data bus, a control bus, etc.

[0177] Transceiver 1604 can be a wireless communication module. Under the control of processor 1601, transceiver 1604 interacts with other devices for data exchange.

[0178] Machine-readable storage medium 1602 may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Alternatively, machine-readable storage medium 1602 may also be at least one storage device located remotely from the aforementioned processor.

[0179] Processor 1601 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0180] As can be seen from the above, the first network device and the second network device are located in the first MRP redundancy domain, and both are directly connected to network devices in the second MRP redundancy domain. It is evident that in the scenario of this application embodiment, an MRP interconnection domain exists between the first and second MRP redundancy domains, and the first and second network devices are located within the MRP interconnection domain. The first port of the first network device is connected to the second port of the second network device. Therefore, if the link between the first and second network devices fails, both the first and second ports will fail. In this case, the second network device broadcasts a first message, and the first network device waits to receive it. Since both the first and second network devices are located within the first MRP redundancy domain, if only the link between the first and second network devices fails within the first MRP redundancy domain, the first message can still be sent to the first network device along the ring link based on the characteristics of the first MRP redundancy domain. However, if the first network device does not receive the first message within a first preset time period, it indicates that there is more than one link failure in the first MRP redundancy domain. In this scenario, if the first network device is a MIM device within the MRP interconnection domain, the first interconnection port is directly switched to forwarding mode. If the first network device is not a MIM device within the MRP interconnection domain, a first message is sent to the MIM device through the MRP interconnection domain, causing the MIM device to switch its second interconnection port to forwarding mode. This opens a path for data packet transmission between the first and second MRP redundancy domains. Therefore, when multiple link failures in the first MRP redundancy domain affect the normal transmission of data packets, the ring link provided by the MRP interconnection domain and the second MRP redundancy domain can be used for packet forwarding. This ensures that data packets can be forwarded normally as much as possible when multiple links fail in the first MRP redundancy domain.

[0181] In one embodiment of this application, after the state of the first interconnect port is switched to a forwarding state that allows message forwarding, or after the second message is sent to the MIM device through the MRP interconnect domain, the machine-executable instructions further cause the processor 1601 to perform the following steps:

[0182] If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets.

[0183] If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

[0184] As can be seen from the above, after the fault is recovered in the first MRP redundancy domain in this application, in order to avoid the formation of a loop in the network that causes data packets to be forwarded continuously, the MIM device will switch the state of its own interconnection port to a blocked state, thereby cutting off the loop and preventing data packet forwarding failure.

[0185] In one embodiment of this application, the machine-executable instructions further cause the processor 1601 to perform the following steps:

[0186] If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

[0187] In one embodiment of this application, the machine-executable instructions further cause the processor 1601 to perform the following steps:

[0188] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets.

[0189] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

[0190] As can be seen from the above, if the first network device can receive the first message, it means that the network device in the first MRP redundancy domain can still forward the message normally. Therefore, it does not need to rely on the network device in the second MRP redundancy domain for forwarding. The interconnection port of the MIM device can continue to remain blocked to prevent loop formation.

[0191] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0192] Corresponding to the aforementioned MRP interconnect domain fault handling method, this application embodiment also provides an MRP interconnect domain fault handling system.

[0193] The aforementioned system includes a first network device and a second network device in the first Media Redundancy Protocol (MRP) redundancy domain;

[0194] The first interconnection port of the first network device is directly connected to the network device in the second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are respectively ring links composed of different network devices connected in sequence. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form a ring link. As an MRP interconnection domain, the first port of the first network device is connected to the second port of the second network device.

[0195] The second network device is configured to broadcast a first message in the first MRP redundancy domain after determining that the second port is faulty;

[0196] The first network device is configured to, after determining that the first port is faulty, determine whether a first packet has been received within a first preset time period; if the first packet is not received within the first preset time period, and if the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP Interconnect Domain, switch the state of the first interconnect port to a forwarding state that allows packet forwarding; if the first packet is not received within the first preset time period, and if the first network device is not a MIM device in the MRP Interconnect Domain, send a second packet to the MIM device through the MRP Interconnect Domain, so that the MIM device switches the state of its second interconnect port to a forwarding state.

[0197] As can be seen from the above, the first network device and the second network device are located in the first MRP redundancy domain, and both are directly connected to network devices in the second MRP redundancy domain. It is evident that in the scenario of this application embodiment, an MRP interconnection domain exists between the first and second MRP redundancy domains, and the first and second network devices are located within the MRP interconnection domain. The first port of the first network device is connected to the second port of the second network device. Therefore, if the link between the first and second network devices fails, both the first and second ports will fail. In this case, the second network device broadcasts a first message, and the first network device waits to receive it. Since both the first and second network devices are located within the first MRP redundancy domain, if only the link between the first and second network devices fails within the first MRP redundancy domain, the first message can still be sent to the first network device along the ring link based on the characteristics of the first MRP redundancy domain. However, if the first network device does not receive the first message within a first preset time period, it indicates that there is more than one link failure in the first MRP redundancy domain. In this scenario, if the first network device is a MIM device within the MRP interconnection domain, the first interconnection port is directly switched to forwarding mode. If the first network device is not a MIM device within the MRP interconnection domain, a first message is sent to the MIM device through the MRP interconnection domain, causing the MIM device to switch its second interconnection port to forwarding mode. This opens a path for data packet transmission between the first and second MRP redundancy domains. Therefore, when multiple link failures in the first MRP redundancy domain affect the normal transmission of data packets, the ring link provided by the MRP interconnection domain and the second MRP redundancy domain can be used for packet forwarding. This ensures that data packets can be forwarded normally as much as possible when multiple links fail in the first MRP redundancy domain.

[0198] In one embodiment of this application, after switching the state of the first interconnect port to a forwarding state that allows message forwarding, or after sending a second message to the MIM device through the MRP interconnect domain, the first network device is further configured to:

[0199] If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets.

[0200] If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

[0201] As can be seen from the above, after the fault is recovered in the first MRP redundancy domain in this application, in order to avoid the formation of a loop in the network that causes data packets to be forwarded continuously, the MIM device will switch the state of its own interconnection port to a blocked state, thereby cutting off the loop and preventing data packet forwarding failure.

[0202] In one embodiment of this application, the first network device is further configured to:

[0203] If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

[0204] In one embodiment of this application, the first network device is further configured to:

[0205] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets.

[0206] If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

[0207] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0208] As can be seen from the above, if the first network device can receive the first message, it means that the network device in the first MRP redundancy domain can still forward the message normally. Therefore, it does not need to rely on the network device in the second MRP redundancy domain for forwarding. The interconnection port of the MIM device can continue to remain blocked to prevent loop formation.

[0209] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0210] Corresponding to the aforementioned MRP interconnect domain fault handling method, this application embodiment also provides an MRP interconnect domain fault handling device.

[0211] See Figure 17This is a schematic diagram of an MRP interconnection domain fault handling device provided in an embodiment of this application. It is applied to a first network device in a first Media Redundancy Protocol (MRP) redundancy domain. The first interconnection port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first and second MRP redundancy domains are ring links formed by sequentially connecting different network devices. The first and second network devices in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnection domain, the first port of the first network device is connected to the second port of the second network device. The device includes:

[0212] The message receiving judgment module 1701 is used to determine whether a first message has been received within a first preset time period after determining that the first port is faulty. The first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state.

[0213] The port switching module 1702 is used to switch the state of the first interconnect port to a forwarding state that allows forwarding packets if the first packet is not received within the first preset time period and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain.

[0214] The second message sending module 1703 is used to send a second message to the MIM device through the MRP interconnection domain if the first message is not received within the first preset time period and the first network device is not a MIM device in the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

[0215] As can be seen from the above, the first network device and the second network device are located in the first MRP redundancy domain, and both are directly connected to network devices in the second MRP redundancy domain. It is evident that in the scenario of this application embodiment, an MRP interconnection domain exists between the first and second MRP redundancy domains, and the first and second network devices are located within the MRP interconnection domain. The first port of the first network device is connected to the second port of the second network device. Therefore, if the link between the first and second network devices fails, both the first and second ports will fail. In this case, the second network device broadcasts a first message, and the first network device waits to receive it. Since both the first and second network devices are located within the first MRP redundancy domain, if only the link between the first and second network devices fails within the first MRP redundancy domain, the first message can still be sent to the first network device along the ring link based on the characteristics of the first MRP redundancy domain. However, if the first network device does not receive the first message within a first preset time period, it indicates that there is more than one link failure in the first MRP redundancy domain. In this scenario, if the first network device is a MIM device within the MRP interconnection domain, the first interconnection port is directly switched to forwarding mode. If the first network device is not a MIM device within the MRP interconnection domain, a first message is sent to the MIM device through the MRP interconnection domain, causing the MIM device to switch its second interconnection port to forwarding mode. This opens a path for data packet transmission between the first and second MRP redundancy domains. Therefore, when multiple link failures in the first MRP redundancy domain affect the normal transmission of data packets, the ring link provided by the MRP interconnection domain and the second MRP redundancy domain can be used for packet forwarding. This ensures that data packets can be forwarded normally as much as possible when multiple links fail in the first MRP redundancy domain.

[0216] In one embodiment of this application, the apparatus further includes:

[0217] The port recovery module is used to switch the state of the first interconnect port to a blocked state that does not allow forwarding data packets if the first packet is received and the first network device is a MIM device in the MRP interconnect domain.

[0218] The third message sending module is configured to, if the first message is received and the first network device is not a MIM device in the MRP interconnection domain, send a third message to the MIM device in the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to a blocked state.

[0219] As can be seen from the above, after the fault is recovered in the first MRP redundancy domain in this application, in order to avoid the formation of a loop in the network that causes data packets to be forwarded continuously, the MIM device will switch the state of its own interconnection port to a blocked state, thereby cutting off the loop and preventing data packet forwarding failure.

[0220] In one embodiment of this application, the apparatus further includes:

[0221] The first port holding module is configured to, if the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, keep the port that has returned to normal in a blocked state for a second preset time period, and then switch the port that has returned to normal to a forwarding state.

[0222] In one embodiment of this application, the apparatus further includes:

[0223] The second port holding module is used to maintain the state of the first interconnect port as a blocked state that does not allow forwarding data packets if the first packet is received within the first preset time period after the first port is determined to be faulty, and the first network device is a MIM device in the MRP interconnect domain.

[0224] The third port holding module is used to send a third message to the MIM device if, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, so that the MIM device keeps its second interconnection port in a blocked state.

[0225] As can be seen from the above, if the first network device can receive the first message, it means that the network device in the first MRP redundancy domain can still forward the message normally. Therefore, it does not need to rely on the network device in the second MRP redundancy domain for forwarding. The interconnection port of the MIM device can continue to remain blocked to prevent loop formation.

[0226] In one embodiment of this application, the first network device does not broadcast the first message in the first MRP redundancy domain.

[0227] In another embodiment provided in this application, a computer-readable storage medium is also provided, which stores a computer program that, when executed by a processor, implements the steps of any of the MRP redundant domain link failure handling methods described above.

[0228] In another embodiment provided in this application, a computer program product containing instructions is also provided, which, when run on a computer, causes the computer to execute any of the MRP redundant domain link failure handling methods in the above embodiments.

[0229] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0230] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0231] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments for network devices, systems, apparatuses, computer-readable storage media, and computer program products are basically similar to the method embodiments, and therefore the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0232] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application are included within the scope of protection of this application.

Claims

1. A method for handling MRP interconnection domain faults, characterized in that, A first network device is applied in a first Media Redundancy Protocol (MRP) redundancy domain. A first interconnect port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first and second MRP redundancy domains are ring links formed by sequentially connecting different network devices. The first and second network devices in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnect domain, the first port of the first network device is connected to the second port of the second network device. The method includes: After determining that the first port is faulty, it is determined whether a first message is received within a first preset time period, wherein the first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state; If the first message is not received within the first preset time period, and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain, the state of the first interconnect port is switched to the forwarding state that allows message forwarding. If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

2. The method according to claim 1, characterized in that, After switching the state of the first interconnect port to a forwarding state that allows message forwarding, or after sending the second message to the MIM device through the MRP interconnect domain, the method further includes: If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets. If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

3. The method according to claim 2, characterized in that, The method further includes: If the first network device is not a MIM device in the MRP interconnection domain, and receives the first message after determining that its own port has returned to normal, then the port that has returned to normal will remain in a blocked state for a second preset time period, and then the port that has returned to normal will be switched to a forwarding state.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is kept in a blocked state that does not allow forwarding of data packets. If, after determining that the first port is faulty, the first message is received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device so that the MIM device keeps its second interconnection port in a blocked state.

5. The method according to any one of claims 1-3, characterized in that, The first network device does not broadcast the first message in the first MRP redundancy domain.

6. A network device, characterized in that, The network device serves as the first network device in a first Media Redundancy Protocol (MRP) redundancy domain. The first interconnect port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first and second MRP redundancy domains are ring links formed by sequentially connecting different network devices. The first and second network devices in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnect domain, the first port of the first network device is connected to the second port of the second network device. The first network device includes: processor; transceiver; A machine-readable storage medium storing machine-executable instructions that can be executed by the processor, the machine-executable instructions causing the processor to perform the following steps: After determining that the first port is faulty, it is determined whether a first message is received within a first preset time period, wherein the first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state; If the first message is not received within the first preset time period, and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain, the state of the first interconnect port is switched to the forwarding state that allows message forwarding. If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

7. The network device according to claim 6, characterized in that, After switching the state of the first interconnect port to a forwarding state that allows message forwarding, or after sending the second message to the MIM device through the MRP interconnect domain, the machine-executable instructions further cause the processor to perform the following steps: If the first message is received, and the first network device is a MIM device in the MRP interconnection domain, the state of the first interconnection port is switched to a blocking state that does not allow forwarding of data packets. If the first message is received, and the first network device is not a MIM device in the MRP interconnection domain, a third message is sent to the MIM device in the MRP interconnection domain so that the MIM device switches the state of its second interconnection port to a blocked state.

8. An MRP interconnection domain fault handling system, characterized in that, The system includes a first network device and a second network device in the first Media Redundancy Protocol (MRP) redundancy domain. The first interconnection port of the first network device is directly connected to the network device in the second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are respectively ring links composed of different network devices connected in sequence. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form a ring link. As an MRP interconnection domain, the first port of the first network device is connected to the second port of the second network device. The second network device is configured to broadcast a first message in the first MRP redundancy domain after determining that the second port is faulty; The first network device is configured to determine whether a first packet has been received within a first preset time period after determining that the first port is faulty. If the first message is not received within the first preset time period, and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain, the state of the first interconnect port is switched to the forwarding state that allows message forwarding. If the first message is not received within the first preset time period, and the first network device is not a MIM device in the MRP interconnection domain, a second message is sent to the MIM device through the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

9. An MRP interconnection domain fault handling device, characterized in that, A first network device is applied in a first Media Redundancy Protocol (MRP) redundancy domain. A first interconnect port on the first network device is directly connected to a network device in a second MRP redundancy domain. The first MRP redundancy domain and the second MRP redundancy domain are ring links formed by sequentially connecting different network devices. The first network device and the second network device in the first MRP redundancy domain are directly connected to different network devices in the second MRP redundancy domain to form ring links. As an MRP interconnection domain, the first port of the first network device is connected to the second port of the second network device. The device includes: The message receiving judgment module is used to determine whether a first message has been received within a first preset time period after determining that the first port is faulty. The first message is broadcast in the first MRP redundancy domain by the second network device after determining that the second port is in a faulty state. The port switching module is used to switch the state of the first interconnect port to a forwarding state that allows forwarding packets if the first packet is not received within the first preset time period and the first network device is a Media Redundancy Interconnect Manager (MIM) device in the MRP interconnect domain. The second message sending module is used to send a second message to the MIM device through the MRP interconnection domain if the first message is not received within the first preset time period and the first network device is not a MIM device in the MRP interconnection domain, so that the MIM device switches the state of its second interconnection port to the forwarding state.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method described in any one of claims 1-5.

Images