Ring network fault processing method and device

Abstract

The embodiment of the invention provides a looped network fault processing method and device. The method is applied to a first node and comprises the following steps: receiving a first message sent by a second node; according to the first destination IP address, a first FIB table item matched with the first destination IP address is obtained from an FIB, the first FIB table item comprises a first outbound interface identifier and a first forwarding attribute, and the first outbound interface identifier indicates a first interface; if the value of the first forwarding attribute is a first value and the first interface is in a DOWN state, a second message is forwarded to a third node in the ring network topology through a second interface, and a first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address. The first interface and the second interface belong to an interface group on the same ring. By applying the scheme provided by the embodiment of the invention, the resource quantity consumed by looped network fault processing can be reduced, and simple fault recovery is realized.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a method and device for handling ring network faults. Background Art

[0002] The network node ring network topology is simple and can improve the reliability of the network. It is a widely used network topology. Figure 1 , is a schematic diagram of the message forwarding path of the first ring network topology. The figure includes a ring network topology consisting of network nodes A and H. In this case, if a message is sent from network node Y to network node X, the message will be sent along the shortest path shown by the arrow in the figure. In the process of this message forwarding, network node G is the network node where the message enters the ring network topology, which can be called the upper ring node. Network node A is the network node where the message leaves the ring network topology, which can be called the lower ring node. Figure 1 Only one uplink node and one downlink node are shown in the figure. In actual situations, there may be multiple uplink nodes and multiple downlink nodes in a ring network topology.

[0003] If a network node or a link between network nodes in a ring network topology fails, the message forwarding path needs to be replanned. Figure 1 Based on the above, see Figure 2 , is a schematic diagram of the second ring network topology message forwarding path. If the link between network node H and network node A fails, then Figure 1 The path originally shown in the figure is unavailable. After network node H receives the message sent by node G, it needs to forward the message along the backup path. Since the link between network node H and network node G is not faulty, network node H will forward the message to network node G, and then network node G will forward the message to network node F in a clockwise direction, and so on. Finally, the message will be forwarded to network node A in a clockwise direction, and then network node A will forward the message to network node X.

[0004] In the related technology, after a ring network topology failure, in order to realize the process of forwarding messages according to the backup path described above, the topology-independent TI-LFA (Topology-Independent Loop-Free Alternate) FRR (Fast Reroute) technology can be used. The TI-LFA FRR technology is based on the SR (Segment Routing) technology. However, the premise of using the TI-LFA FRR technology to deal with network failures is that for each network node in the ring network topology, the network node needs to pre-calculate the backup path (Repair List) and backup outbound interface of each downlink node and underlay (physical infrastructure network) node in the ring network topology, so as to use the backup path and backup outbound interface to forward messages in the event of a failure.

[0005] It can be seen that the TI-LFA FRR technology based on SR technology is relatively complex. For a simple network topology such as a ring network topology, each network node needs to pre-calculate the backup path and backup outbound interface before a fault occurs. The network node needs to perform complex calculations and store a large amount of protection path information for dealing with network faults, that is, information such as backup paths and backup outbound interfaces, so that after a network fault, packets can be forwarded through the backup path and backup outbound interface based on the protection path information. As a result, the ring network fault handling process consumes a large amount of network node resources and the process is relatively complex. Summary of the invention

[0006] The purpose of the embodiments of the present application is to provide a ring network fault processing method and device to reduce the amount of resources consumed by ring network fault processing and achieve simple fault recovery. The specific technical solution is as follows: In a first aspect, an embodiment of the present application provides a ring network fault processing method, which is applied to a first node, where the first node is in a ring network topology, and the method includes: Receiving a first message sent by a second node, wherein the first message includes a first destination IP address; According to the first destination IP address, obtaining a first FIB table entry matching the first destination IP address from a forwarding information table FIB, wherein the first FIB table entry includes a first outbound interface identifier and a first forwarding attribute, wherein the first outbound interface identifier indicates a first interface; If the value of the first forwarding attribute is a first value and the first interface is in a disconnected DOWN state, forwarding a second message to a third node in the ring network topology through a second interface, wherein the first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address; The first interface and the second interface belong to the same ring interface group.

[0007] In a second aspect, an embodiment of the present application provides a ring network fault processing device, which is applied to a first node, where the first node is in a ring network topology, and the device includes: A first message receiving module, configured to receive a first message sent by a second node, wherein the first message includes a first destination IP address; A first table entry acquisition module, configured to acquire, according to the first destination IP address, from a forwarding information table FIB, a first FIB table entry matching the first destination IP address, wherein the first FIB table entry includes a first outbound interface identifier and a first forwarding attribute, and the first outbound interface identifier indicates a first interface; A first message forwarding module, configured to forward a second message to a third node in the ring network topology through a second interface if the value of the first forwarding attribute is a first value and the first interface is in a disconnected DOWN state, wherein the first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address; The first interface and the second interface belong to the same ring interface group.

[0008] In a third aspect, an embodiment of the present application provides a network node, the network node is located in a ring network topology, and the network node includes: processor; Transceiver; A machine-readable storage medium storing machine-executable instructions that can be executed by the processor; the machine-executable instructions prompt the processor to execute any one of the method steps in the first aspect.

[0009] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any method step described in the first aspect is implemented.

[0010] In a fifth aspect, an embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the method steps described in the first aspect above.

[0011] Beneficial effects of the embodiments of the present application: In the embodiment of the present application, if the first node in the ring network topology obtains the first FIB table item matching the first destination IP address of the first message from the FIB after receiving the first message, the first FIB table item contains the first forwarding attribute and the first output interface identifier. If the value of the first forwarding attribute is the first value, it means that the message needs to be forwarded on the ring, that is, the first node needs to forward the message to other nodes on the ring network topology. In this case, if the first interface indicated by the first output interface identifier is in the DOWN state, the first node can no longer send the message through the first interface. Since the first interface and the second interface both belong to the ring interface group, that is, they are both interfaces on the first node connected to the network node in the ring network topology. Changing the first interface for forwarding the first message to the second interface is equivalent to changing the forwarding direction of the message. Since the network nodes in the ring network topology are connected to form a ring, the message forwarding can be completed normally even if the forwarding direction is changed. In addition, by handling network failures in the manner of the embodiment of the present application, there is no need to calculate complex backup paths and backup output interfaces in the first node, and it is only necessary to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of network nodes, and ring network fault processing can be achieved in a simple way. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0013] Figure 1 This is a schematic diagram of the message forwarding path of the first ring network topology; Figure 2 This is a schematic diagram of the message forwarding path of the second ring network topology; Figure 3 A schematic diagram of a backup path provided in an embodiment of the present application; Figure 4 A flowchart of a first ring network fault handling method provided in an embodiment of the present application; Figure 5 A schematic diagram of the first type of message forwarding for a ring network failure provided in an embodiment of the present application; Figure 6 A schematic diagram of a second message forwarding for a ring network failure provided in an embodiment of the present application; Figure 7 A flowchart of a second ring network fault handling method provided in an embodiment of the present application; Figure 8 A third message forwarding schematic diagram of a ring network failure provided in an embodiment of the present application; Fig. 9 A flowchart of a third ring network fault handling method provided in an embodiment of the present application; Fig.10 A fourth message forwarding schematic diagram of a ring network failure provided in an embodiment of the present application; Fig.11 A schematic diagram of a path for normal message forwarding provided in an embodiment of the present application; Fig.12 is a schematic diagram of a first tangent micro-ring in the related art; Fig.13 is a schematic diagram of a second tangent micro-ring in the related art; Fig.14 A schematic diagram of a tangent micro-ring prevention process provided in an embodiment of the present application; Fig.15 A fifth message forwarding schematic diagram of a ring network failure provided in an embodiment of the present application; Fig.16 A schematic diagram of a back-cut micro-ring in the related art; Fig.17 A schematic diagram of a process of switching back to prevent micro-rings is provided for an embodiment of the present application; Fig.18 A schematic diagram of the structure of a ring network fault processing device provided in an embodiment of the present application; Fig.19 A schematic diagram of the structure of a network node provided in an embodiment of the present application. DETAILED DESCRIPTION

[0014] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field based on this application belong to the scope of protection of the present invention.

[0015] In order to reflect the difference between the embodiments of the present application and the related art, the related art is first described.

[0016] In related technologies, the FRR technology can be used to implement fault repair of IP network links or network nodes. The evolution of FRR technology has gone through FRR, LFA (Loop-Free Alternate) FRR, Remote LFA FRR, and TI-LFA FRR.

[0017] Among them, FRR is not available in IP (Internet Protocol) ring network topology. LFA FRR cannot calculate a loop-free backup path in most cases and is not available in IP ring network topology. Remote LFA FRR cannot calculate a backup path in some cases, and on the forwarding plane, it uses the more complex MPLS (Multi-Protocol Label Switching) forwarding method instead of the simple and widely used IP forwarding method, so it is not available in IP-based IP ring network topology.

[0018] That is, among the above fault recovery methods, only TI-LFA FRR is independent of the network topology and can be applied to the IP ring network topology. However, TI-LFA FRR is based on SR technology. SR is divided into MPLS SR based on MPLS and SRv6 (Segment Routing Internet Protocol Version 6) based on IPv6 (Internet Protocol Version 6). The forwarding plane of MPLS SR uses a more complex MPLS forwarding method, which is not applicable to the IP ring network topology. Only TI-LFA FRR based on SRv6 is applicable to the IP ring network topology.

[0019] But the previous Figure 2 Taking the scenario shown as an example, if SRv6-based TI-LFA FRR is used for fault handling, in order to avoid flow interruption caused by link failure between network node H and network node A, or to avoid flow interruption caused by failure of network node A, network node H needs to calculate the extended P space, Q space, backup path and backup outbound interface, and finally generate a backup forwarding table entry.

[0020] See also Figure 3 , is a schematic diagram of a backup path provided in an embodiment of the present application, in Figure 2 Based on the scenario shown, Figure 3 The clockwise direction indicated by the bold arrow is the message forwarding direction in the backup path generated by network node H. The backup path is network node H-network node G-network node F-network node E-network node D-network node C-network node B-network node A. That is, before the failure, the message is sent in the counterclockwise direction in the ring network topology. After the failure, the message is sent in the clockwise direction in the ring network topology.

[0021] In short, since the location of the fault in the ring network topology is random. Therefore, before the fault occurs, in order to be able to smoothly forward the message to the next ring node when its own interface is in the DOWN state, each network node in the ring network topology, except for the next ring node, needs to calculate the backup path to the next ring node to ensure that the message forwarding can continue after the fault occurs. That is, from the perspective of the next ring node, the other network nodes in the ring network topology need to calculate the backup path and backup output interface to the next ring node. For each next ring node, from the perspective of the network nodes in the ring network topology except the next ring node, each network node needs to calculate the backup path and backup output interface to the next ring node respectively. Only in this way can the network nodes in the ring network topology be able to smoothly forward the message after the ring network topology fails.

[0022] Therefore, for a simple ring network topology, each network node on the ring network topology needs to perform complex calculations and deployments and store more protection path information in order to cope with the problem of ring network topology failure, which makes the fault handling process complicated and consumes a lot of resources.

[0023] In order to solve the above problems, the embodiments of the present application provide a ring network fault handling method and device.

[0024] To facilitate subsequent description, the terms involved in the embodiments of the present application are first explained.

[0025] Ingress: A network node in a ring network topology that receives messages from network nodes outside the ring network topology and forwards messages to network nodes in the ring network topology.

[0026] Transit: A network node in a ring network topology that receives messages from network nodes within the ring network topology and forwards messages to network nodes in the ring network topology.

[0027] Egress: A network node in a ring network topology that receives messages from network nodes within the ring network topology and forwards messages to network nodes outside the ring network topology.

[0028] With the aforementioned Figure 1 Taking the scenario shown as an example, network node G is an entry node, network node H is a transit node, and network node A is an exit node.

[0029] Ring interface: The interface that connects network nodes in a ring network topology. For example, Figure 1 The interfaces of the network node G connecting the network node H and the network node F are all on-ring interfaces.

[0030] External ring interface: An interface on a network node in a ring network topology that connects to a network node outside the ring network topology. For example, Figure 1 The interface on network node G connected to network node Y.

[0031] Wrap MAC (Media Access Control): that is, the preset MAC address in the embodiment of the present application. If the destination MAC address of the message is a wrap MAC, it means that the message is protected from wrapping, that is, the message needs to be forwarded according to the ring network fault handling method provided in the present application.

[0032] In one embodiment of the present application, the preset MAC address (i.e., the wraparound MAC) may be different from the MAC address of the network node and the MAC address of the interface of the network node existing in the IP network, so as to be distinguished from the real MAC address existing in the network. In this case, the preset MAC address may be a fixed value, or the preset MAC address may also be a specified MAC address existing in the network. In the actual processing process, different preset MAC addresses need to be configured for unicast messages and multicast messages.

[0033] Wrapped message: A message whose destination MAC address in the Ethernet header is a wrapped MAC. The embodiment of the present application is applicable to IP messages, so a wrapped message refers to an IP message whose destination MAC address in the outer Ethernet header is a wrapped MAC, and is applicable to various IP protocols, including IPv4 (Internet Protocol Version 4) and IPv6.

[0034] On-ring forwarding: If the next-hop interface recorded in the FIB entry is an on-ring interface, the value of the first forwarding attribute in the FIB entry is the first value, indicating on-ring forwarding.

[0035] Down-ring forwarding: If the next-hop interface recorded in the FIB entry is an out-of-ring interface, the value of the first forwarding attribute in the FIB entry is the second value, indicating down-ring forwarding.

[0036] In-loop message: If the incoming interface of the message is connected to other network nodes in the ring network topology, the message is an in-loop message. For example, if network node H receives a message sent by network node G, then for network node H, the incoming interface of the message is connected to network node G in the ring network topology, so the message is an in-loop message.

[0037] Inbound message: If the incoming interface of the message is connected to other network nodes outside the ring network topology, the message is an inbound message. For example, if network node G receives a message sent by network node Y, then for network node G, the incoming interface of the message is connected to network node Y outside the ring network topology, so the message is an inbound message.

[0038] The following describes the method for handling ring network faults.

[0039] See also Figure 4 , which is a flow chart of a first ring network fault handling method provided in an embodiment of the present application, and is applied to a first node, the first node being in a ring network topology, and the method includes the following steps S401-S403.

[0040] S401: Receive a first message sent by a second node.

[0041] Wherein, the above-mentioned first message includes the first destination IP address.

[0042] The second node may be a node outside the ring network topology, the first node is an inbound node, and the first message is an inbound message. The second node may also be a node within the ring network topology, the first node may be a transit node or a drop node, and the first message is an inbound message.

[0043] S402: According to the first destination IP address, obtain a first FIB entry matching the first destination IP address from the FIB.

[0044] The first FIB (Forwarding Information Base) entry includes a first outbound interface identifier and a first forwarding attribute, and the first outbound interface identifier indicates a first interface.

[0045] S403: If the value of the above-mentioned first forwarding attribute is the first value, and the above-mentioned first interface is in the DOWN state, then the second message is forwarded to the third node in the above-mentioned ring network topology through the second interface, and the first destination MAC address included in the above-mentioned second message is a preset MAC address, so that the above-mentioned third node forwards the above-mentioned second message according to the above-mentioned preset MAC address.

[0046] The first interface and the second interface belong to the same on-ring interface group.

[0047] The fact that the value of the first forwarding attribute is the first value indicates that the first FIB entry is an on-ring forwarding entry, that is, the first interface indicated by the first outbound interface identifier is an on-ring interface.

[0048] If the first interface is in a faulty state, it may be that the link between the first node and the connected network node through the first interface is faulty, or it may be that the network node connected to the first interface is faulty. In this case, the first node can no longer forward messages through the first interface. In this case, ring network fault processing is required.

[0049] In this case, it is necessary to first decapsulate the Ethernet header of the first message, and then encapsulate the first message after the Ethernet header is decapsulated with an Ethernet header whose destination MAC address is the preset MAC address to obtain a second message. Since the destination MAC address of the second message is the preset MAC address, the second message is a wraparound message. After receiving the second message, the third node can determine that the second message is a wraparound message based on the preset MAC address. Then the third node can act as the first node and follow the following procedure: Figure 7 Steps S405 to S406 shown in the figure, or according to the following Fig. 9 Steps S408 to S409 are shown to forward the message. The specific forwarding method is described below and will not be described in detail here.

[0050] In one embodiment of the present application, after executing step S401, the following step A or step B may also be executed, and the second message is forwarded through step C.

[0051] Step A: If the input interface receiving the first message is connected to a node on the ring network topology, the first message is marked as an in-ring message.

[0052] The input interface of the first message is connected to the node on the ring network topology, which means that the first message is sent by the node on the ring network topology, and the first message is an in-ring message.

[0053] Step B: If the inbound interface receiving the first message is connected to a node outside the ring network topology, the first message is marked as a ring-inbound message.

[0054] The inbound interface of the first message is connected to the node outside the ring network topology, which means that the first message is sent by the node outside the ring network topology, and the first message is an inbound message.

[0055] Step C: If the value of the first forwarding attribute is the first value, the first interface is in the DOWN state, and the first message is marked as an in-loop message or an incoming-loop message, forward the second message to the third node in the ring network topology through the second interface.

[0056] In one embodiment of the present application, a first extended message header can be added to the first message, and the first extended message header can be added at any position before the data part of the first message. The first extended message header contains a first identifier. If the value of the first identifier is the first identifier value, it indicates that the first message is an in-loop message. If the value of the first identifier is the second identifier value, it indicates that the first message is an in-loop message. The first identifier in the first extended message header is used in the process of the first node processing the first message, and the first extended message header is not included in the second message sent out by the first node. Therefore, the above-mentioned first extended message header can be deleted at any time before forwarding the second message after using the first identifier. Since the first extended message header is added to the first message, even if the first node processes the first message on different internal data boards in the process of forwarding the first message, different data boards can quickly determine whether the first message is an in-loop message or an in-loop message through the first extended message header.

[0057] Specifically, as shown above, the first message may be an incoming message or an in-loop message. For the above two situations, the message can be forwarded through the following steps D to F.

[0058] Step D: decapsulate the Ethernet header of the first message, and encapsulate the first message after the decapsulation of the Ethernet header with an Ethernet header whose destination MAC address is a preset MAC address to obtain a second message.

[0059] Step E: If the first message is an in-loop message, the second message is forwarded through the inbound interface of the first message.

[0060] For example, see Figure 2 In the scenario shown, network node H receives a first message sent from network node G. In this case, network node H is a transit node and the first message is an in-ring message. In this case, the first interface is an interface connected to network node A. Due to a link failure between network node A and network node H, the first interface is in a DOWN state. In this case, the second message needs to be forwarded through the second interface.

[0061] The second interface that belongs to the interface group on the first ring together with the first interface is an interface on the network node H connected to the network node G, that is, an inbound interface of the first message.

[0062] Therefore, when the first message is an in-loop message, the first node forwards the second message through the inbound interface of the first message.

[0063] See also Figure 5 , which is a schematic diagram of the first type of message forwarding for a ring network failure provided in an embodiment of the present application.

[0064] Figure 5 The network structure shown in Figure 1The same, and Figure 5 and Figure 1 The scenarios are all scenarios where network node Y sends a message to network node X. Figure 5 In the example, the link between network node H and network node A fails.

[0065] Figure 5 The IP in it represents the destination IP address of the first message, MAC_G represents the MAC address of the network node G, MAC_H represents the MAC address of the network node H, and MAC_P represents the preset MAC address.

[0066] The solid arrows indicate the message forwarding path when the message is forwarded normally, and the dotted arrows indicate the message forwarding path after a fault occurs.

[0067] Depend on Figure 5 It can be seen that the destination MAC address in the Ethernet header of the message sent by network node Y to network node G is MAC_G, and the destination MAC address in the Ethernet header of the message sent by network node G to network node H is MAC_H. After receiving the message, network node H decapsulates the outer Ethernet header, determines the outgoing interface of the message, that is, the first interface DOWN, and therefore encapsulates the Ethernet header whose destination MAC address is the preset MAC address for the message after decapsulating the Ethernet header, and forwards the message to network node G. Therefore, the destination MAC address in the Ethernet header of the message sent by network node H to network node G is the preset MAC address.

[0068] Step F: If the first message is a ring-in message, forward the second message through the second interface.

[0069] In this case, the second interface is not the inbound interface of the first message.

[0070] For example, see Figure 1 In the scenario shown, network node G receives a first message sent from network node Y. In this case, network node G is an inbound node and the first message is an inbound message. In this case, the first interface is the interface on network node G that is connected to network node H. If the link between network node G and network node H fails, the first interface is DOWN. In this case, the second message needs to be forwarded through the second interface.

[0071] The second interface that belongs to the same on-ring interface group as the first interface is an interface on the network node G connected to the network node F.

[0072] See also Figure 6 , which is a schematic diagram of the second message forwarding of a ring network failure provided in an embodiment of the present application.

[0073] Figure 6 The network structure shown in Figure 1 The same, and Figure 6 and Figure 1 The scenarios are all scenarios where network node Y sends a message to network node X. Figure 6 In the example, the link between network node G and network node H fails.

[0074] Figure 6 The IP in it represents the destination IP address of the first message, MAC_G represents the MAC address of the network node G, and MAC_P represents the preset MAC address.

[0075] The solid arrows indicate the message forwarding path when the message is forwarded normally, and the dotted arrows indicate the message forwarding path after a fault occurs.

[0076] Depend on Figure 6 It can be seen that the destination MAC address in the Ethernet header of the message sent by network node Y to network node G is MAC_G. After receiving the message, network node G decapsulates the outer Ethernet header and determines the outgoing interface of the message, that is, the first interface DOWN, and thus encapsulates the Ethernet header whose destination MAC address is the preset MAC address for the message after decapsulating the Ethernet header, and forwards the message to network node F. Therefore, the destination MAC address in the Ethernet header of the message sent by network node G to network node F is the preset MAC address.

[0077] In one embodiment of the present application, the above-mentioned ring interface group can be created by the following step G before executing step S401.

[0078] Step G: Create an interface group on the ring.

[0079] The above-mentioned on-ring interface group includes interface identifiers of at least two interfaces, and the above-mentioned at least two interfaces both belong to the above-mentioned first node and are both connected to other nodes except the first node in the above-mentioned ring network topology.

[0080] Specifically, each network node in the ring network topology is connected to two other network nodes in the ring network topology. That is, each network node in the ring network topology has two interfaces connected to two other network nodes in the ring network topology, and these two interfaces form a ring interface group. Figure 1 Taking the ring network topology shown as an example, the network node H is the first node, and the two interfaces on the network node H respectively connected to the network node A and the network node G constitute the ring interface group of the first node.

[0081] In addition, in one embodiment of the present application, before forwarding the second message to the third node in the above ring network topology through the second interface, the following steps H-I are also included.

[0082] Step H: Determine the first on-ring interface group to which the first interface belongs.

[0083] Step I: Determine the interfaces in the interface group on the first ring other than the first interface as second interfaces.

[0084] In the embodiment of the present application, if the first node in the ring network topology obtains the first FIB table item matching the first destination IP address of the first message from the FIB after receiving the first message, the first FIB table item contains the first forwarding attribute and the first output interface identifier. If the value of the first forwarding attribute is the first value, it means that the message needs to be forwarded on the ring, that is, the first node needs to forward the message to other nodes on the ring network topology. In this case, if the first interface indicated by the first output interface identifier is in the DOWN state, the first node can no longer send the message through the first interface. Since the first interface and the second interface both belong to the ring interface group, that is, they are both interfaces on the first node connected to the network node in the ring network topology. Changing the first interface for forwarding the first message to the second interface is equivalent to changing the forwarding direction of the message. Since the network nodes in the ring network topology are connected to form a ring, the message forwarding can be completed normally even if the forwarding direction is changed. In addition, by handling network failures in the manner of the embodiment of the present application, there is no need to calculate complex backup paths and backup output interfaces in the first node, and it is only necessary to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of network nodes, and ring network fault processing can be achieved in a simple way.

[0085] In another embodiment of the present application, see Figure 7 , which is a flow chart of a second ring network fault handling method provided in an embodiment of the present application, including the following steps S404-S406.

[0086] S404: Receive a third message sent by the fourth node through the third interface.

[0087] The third message includes a second destination MAC address and a second destination IP address.

[0088] In one embodiment of the present application, the preset MAC address is a unicast preset MAC address or a multicast preset MAC address, and the unicast preset MAC address is different from the multicast preset MAC address.

[0089] S405: When the second destination MAC address is the preset MAC address, a second FIB entry matching the second destination IP address is obtained from the FIB.

[0090] The second FIB table entry includes a second forwarding attribute.

[0091] As shown above, the destination MAC address of the third message is a preset MAC address, indicating that the third message is a wraparound message and needs to be forwarded according to the ring network fault handling method provided in the embodiment of the present application.

[0092] S406: If the value of the above-mentioned second forwarding attribute is the above-mentioned first value, the fourth message is forwarded to the fifth node in the above-mentioned ring network topology through the fourth interface, and the third destination MAC address included in the above-mentioned fourth message is the above-mentioned preset MAC address, so that the above-mentioned fifth node forwards the above-mentioned fourth message according to the above-mentioned preset MAC address.

[0093] The third interface and the fourth interface belong to the same ring interface group.

[0094] If the value of the above-mentioned second forwarding attribute is the first value, it means that the second FIB table item is a forwarding table item on the ring, and the message needs to be forwarded in the ring network topology, rather than forwarded to the node outside the ring network topology. In this case, if the message is forwarded through the third message input interface, that is, the third interface, the message will be resent to the network node that last forwarded the third message, resulting in a forwarding loop failure. Therefore, in this case, it is necessary to forward the fourth message through a fourth interface that is different from the third interface and belongs to the same ring interface group as the third interface. In addition, the third destination MAC address of the fourth message is the above-mentioned preset MAC address, so that the fifth node that receives the fourth message can also determine that the fourth message is a wraparound message based on the preset MAC address, and needs to continue forwarding the message in accordance with the ring network fault handling method.

[0095] Specifically, the first node needs to decapsulate the Ethernet header on the outer layer of the third message, and encapsulate the third message after the decapsulation of the Ethernet header with an Ethernet header whose new destination MAC address is the preset MAC address, to obtain a fourth message.

[0096] In one embodiment of the present application, after step S404, the following step J is also included, and the fourth message is forwarded through step K.

[0097] Step J: When it is determined that the second destination MAC address is the preset MAC address, the third message is marked as a wraparound message.

[0098] Step K: If the value of the second forwarding attribute is the first value, and the third message is marked as a wraparound message, forwarding the fourth message to the fifth node in the ring network topology through the fourth interface.

[0099] In one embodiment of the present application, a second extended message header can be added to the third message, and the second extended message header can be added at any position before the data part of the third message. The second extended message header contains a second identifier, and the value of the second identifier is the third identifier value, which indicates that the third message is a wraparound message. The second identifier in the second extended message header is used in the process of the first node processing the third message, and the second extended message header is not included in the fourth message sent out by the first node. Therefore, after identifying that the third message is marked with the second identifier, the above-mentioned second extended message header can be deleted at any time before forwarding the fourth message. Since the second extended message header is added to the third message, even if the first node processes the third message on different internal data boards when forwarding the third message, the different data boards can quickly determine that the third message is a wraparound message through the second extended message header.

[0100] In one embodiment of the present application, before forwarding the fourth message to the fifth node in the above ring network topology through the fourth interface, the following steps L-M are also included.

[0101] Step L: Determine the interface group on the second ring to which the third interface belongs.

[0102] Step M: Determine the interfaces in the interface group on the second ring except the third interface as fourth interfaces.

[0103] See also Figure 8 , which is a third message forwarding diagram for a ring network failure provided in an embodiment of the present application.

[0104] exist Figure 5 On the basis of the embodiment shown, the newly added dotted arrow indicates the forwarding path after the message is forwarded to the network node G. After receiving the message, the network node G needs to continue forwarding. In this case, the network node G receives the message from the network node H, the network node G is not a downlink node, and the network node G as the first node receives the message through the interface connected to the network node H, and then forwards the message through the interface connected to the network node F.

[0105] At this time, network node F is also not a downlink node. After receiving the message through the interface connected to network node G as the first node, network node F forwards the message through the interface connected to network node E.

[0106] By analogy, the message is forwarded from network node G to network node F, network node E, network node D, network node C, network node B, and network node A in sequence.

[0107] In this process, the destination MAC address in the Ethernet header of the forwarded message is a preset MAC address, namely MAC_P.

[0108] In addition, in one embodiment of the present application, each network node will first decapsulate the Ethernet header after receiving the message, and then re-capsulate the Ethernet header. After receiving the message with the destination MAC address as the preset MAC address, the transit node first decapsulates the Ethernet header, and then the destination MAC address in the re-capsulated Ethernet header is still the preset MAC address, and the source MAC address in the re-capsulated Ethernet header is the MAC address of the transit node.

[0109] As can be seen from the above, in the embodiment of the present application, after the first node receives the third message whose destination MAC address is the preset MAC address, it can determine that the third message is a message forwarded in the event of a fault. And the value of the second forwarding attribute is the first value, indicating that the message needs to be forwarded in the ring network topology, then the first node forwards the message to the fourth interface that belongs to the same ring interface group as the input interface. Therefore, even if the backup path and the backup output interface are not recorded in the first node, the message can be forwarded when the third message is received. The first node still does not need to calculate the complex backup path and backup output interface, and only needs to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of the network nodes, and ring network fault handling can be achieved in a simple way.

[0110] In another embodiment of the present application, see Fig. 9 , which is a flow chart of a third ring network fault handling method provided in an embodiment of the present application, including the following steps S407-S409.

[0111] S407: Receive a fifth message sent by the sixth node through the fifth interface.

[0112] The fifth message includes the third destination IP address and the fourth destination MAC address.

[0113] S408: When the fourth destination MAC address is the preset MAC address, a third FIB entry matching the third destination IP address is obtained from the FIB.

[0114] The third FIB table entry includes a third forwarding attribute and a second outbound interface identifier, and the second outbound interface identifier indicates a sixth interface.

[0115] S409: If the value of the third forwarding attribute is the second value, forwarding the sixth message to a seventh node outside the ring network topology through the sixth interface.

[0116] The fifth destination MAC address included in the sixth message is the MAC address of the seventh node.

[0117] If the value of the third forwarding attribute is the second value, it means that the third FIB table entry indicates down-ring forwarding, that is, the fifth message needs to be sent to a node outside the ring network topology.

[0118] This indicates that the node connected to the sixth interface is a network node outside the ring network topology. In this case, the message needs to be sent outside the ring network topology and cannot be forwarded further within the ring network topology. Therefore, in this case, the message is forwarded normally through the sixth interface to the network node outside the ring network topology.

[0119] Specifically, the first node needs to decapsulate the Ethernet header of the fifth message, and encapsulate the Ethernet header whose destination MAC address is the next hop MAC address to obtain the sixth message. After the first node decapsulates the outer Ethernet header of the fifth message, it obtains the first destination IP address in the inner IP header. According to the first destination IP address, obtain the first FIB table entry that matches the first destination IP address from the FIB, and the first FIB table entry includes the next hop IP address. According to the next hop IP address, search the ARP table entry that matches the next hop IP address from the ARP (Address Resolution Protocol) table, and use the MAC address recorded in the matched ARP table entry as the destination MAC address in the newly encapsulated Ethernet header.

[0120] In one embodiment of the present application, the above step S407 further includes the following step N, and the sixth message is forwarded through step O.

[0121] Step N: When it is determined that the fourth destination MAC address is the preset MAC address, the fifth message is marked as a wraparound message.

[0122] Step O: If the value of the third forwarding attribute is the second value, and the fifth message is marked as a wraparound message, forwarding the sixth message to a seventh node outside the ring network topology through the sixth interface.

[0123] In one embodiment of the present application, a third extended message header can be added to the fifth message, and the third extended message header can be added at any position before the data part of the fifth message. The third extended message header contains a second identifier, and the value of the second identifier is the third identifier value, which indicates that the fifth message is a wraparound message. The second identifier in the third extended message header is used in the process of the first node processing the fifth message, and the third extended message header is not included in the sixth message sent out by the first node. Therefore, after identifying that the fifth message is marked with the second identifier, the above-mentioned third extended message header can be deleted at any time before forwarding the sixth message. Since the third extended message header is added to the fifth message, even if the first node processes the sixth message on different internal data boards during the process of forwarding the sixth message, the different data boards can quickly determine that the fifth message is a wraparound message through the third extended message header.

[0124] See also Fig.10, which is a fourth message forwarding diagram of a ring network failure provided in an embodiment of the present application.

[0125] exist Figure 8 On the basis of the embodiment shown, an arrow is added between network node A and network node X, indicating that the message is forwarded from network node A to network node X. After the message is forwarded to network node A, since the destination node of the message is network node X, network node A is the downlink node in this case. Therefore, network node A, as the first node, forwards the message according to the sixth interface, that is, the interface connected to network node X.

[0126] It can be seen that when network node Y sends a message to network node X, if there is no fault in the ring network topology, the message is sent to network node X through network node Y, network node G, network node H, and network node A. If a fault occurs in the ring network topology, the message can also be sent to network node X through network node Y, network node G, network node F, network node E, network node D, network node C, network node B, and network node A. Therefore, the solution provided by the embodiment of the present application can realize ring network fault processing.

[0127] As can be seen from the above, if the value of the third forwarding attribute is the second value, it means that the first node is a down-ring node, then the first node needs to forward the message to the network node indicated by the destination address of the message outside the ring network topology. In this case, the sixth interface recorded in the FIB table item is the interface connected to the network node outside the ring network topology. In this case, the message needs to be forwarded through the next-hop interface. The first node still does not need to calculate the complex backup path and backup output interface, and can also implement ring network fault handling in a simple way. The simple fault handling method provided by the embodiment of the present application can achieve rapid fault handling from sub-millisecond to hundreds of microseconds.

[0128] The process described above is the process of message forwarding when a fault occurs. The following describes the process of message forwarding in a normal state.

[0129] See also Fig.11 , is a schematic diagram of a path for normal message forwarding provided in an embodiment of the present application.

[0130] Fig.11 The network nodes A to H in the network form a ring network topology.

[0131] Fig.11 The service flow 1 is represented by an arrow from network node Y to network node X, and the service flow is specifically an underlay flow. Fig.11The diagram also includes a service flow 2 represented by an arrow from network node Z to network node W, which is specifically an overlay (logical overlay network) flow. Overlay is a logical network or virtual network built on the basis of underlay, such as VPN (Virtual Private Network).

[0132] For service flow 1, the service packets that constitute service flow 1 all contain an IP header (in Fig.11 The destination IP addresses in the IP headers of the service packets constituting service flow 1 are all the IP addresses of network node X, which will not be described in detail below.

[0133] In one example, when the link is normal, network node Y sends service message 1 to network node G. Service message 1 includes an Ethernet header, an IP header, and a data part from the outer layer to the inner layer, and the destination MAC address included in the Ethernet header is the MAC address (MAC_G) of network node G. Network node Y can forward service message 1 to network node G according to MAC_G.

[0134] After receiving service message 1, network node G decapsulates the outer Ethernet header and determines the destination IP address in the IP header. Network node G searches the FIB table entry that matches the destination IP address, obtains the next-hop IP address included in the FIB table entry, and then searches the ARP table for the MAC address corresponding to the next-hop IP address, that is, the MAC address of network node H (MAC_H). Then network node G encapsulates the Ethernet header in the outer layer of service message 1 after decapsulating the Ethernet header. The destination MAC address in the encapsulated Ethernet header is MAC_H, and service message 2 is obtained. Network node G forwards service message 2 to network node H according to MAC_H.

[0135] After receiving service message 2, network node H decapsulates the outer Ethernet header of service message 2 in the same way, and recapsulates the Ethernet header. The destination MAC address of the encapsulated Ethernet header is the MAC address of network node A (MAC_A), and service message 3 is obtained. Network node H forwards service message 3 to network node A according to MAC_A.

[0136] After receiving service message 3, network node A decapsulates the outer Ethernet header of service message 3 in the same way, and recapsulates the Ethernet header. The destination MAC address of the encapsulated Ethernet header is the MAC address of network node X (MAC_X), and service message 4 is obtained. Network node A forwards service message 4 to network node X according to MAC_X.

[0137] At this point, the forwarding of the service message from network node Y to network node X is completed.

[0138] exist Fig.11 In the ring network topology shown, if the link between network node H and network node A fails, for service flow 1, the process of network node Y forwarding service message 1 to network node G is the same as above and will not be repeated here.

[0139] After the subsequent service message 1 enters the ring network topology, the solution provided by the embodiment of the present application is adopted to forward the service message, that is, after receiving the service message 1, the network node G marks the service message 1 as an incoming ring message because the incoming interface of the service message 1 is connected to the network node Y outside the ring network topology. The Ethernet header of the outer layer of the service message 1 is decapsulated, and the FIB table entry is searched according to the destination IP address in the IP header, and the next hop IP address, the outgoing interface identifier and the forwarding attribute value are obtained from the found FIB table entry. The outgoing interface identifier indicates the outgoing interface (referred to as outgoing interface 1) connected to the network node H on the network node G. The network node G determines that the outgoing interface 1 is in the UP state, and the obtained forwarding attribute value is the first value, and the service message 1 is marked as an incoming ring message, which means that the service message needs to be forwarded through the outgoing interface 1 in the ring network topology. Then, the network node G searches the ARP table for the MAC address corresponding to the next hop IP address, that is, the MAC address (MAC_H) of the network node H. The outer layer of the service message 1 after the Ethernet header is decapsulated is encapsulated with an Ethernet header to obtain the service message 2. The destination MAC address of the encapsulated Ethernet header is MAC_H. Network node G forwards service message 2 to network node H through outbound interface 1.

[0140] After receiving service message 2, network node H connects to network node G in the ring network topology according to the input interface of service message 2, and marks service message 2 as an in-ring message. Network node H decapsulates the Ethernet header of the outer layer of service message 2, searches the FIB table entry according to the destination IP address in the IP header, and obtains the value of the outgoing interface identifier and the forwarding attribute from the found FIB table entry. The outgoing interface identifier indicates the outgoing interface (referred to as outgoing interface 2) on network node H that is connected to network node A. Network node H determines that outgoing interface 2 is in the DOWN state, and the obtained forwarding attribute value is the first value, and service message 2 is marked as an in-ring message, which means that it is necessary to use other outgoing interfaces in the ring interface group to which outgoing interface 2 belongs in the ring network topology to forward service messages. Furthermore, network node H determines the interface that belongs to the same ring interface group as outgoing interface 2, that is, the outgoing interface (referred to as outgoing interface 3) on network node H that is connected to network node G. The network node H encapsulates the Ethernet header in the outer layer of the service message 2 after decapsulating the Ethernet header, and the destination MAC address of the encapsulated Ethernet header is the preset MAC address, thereby obtaining the service message 5. Since there are service messages 3 and 4 in the previous example, in order to distinguish them from the service messages in the previous example, this service message is called service message 5. The network node H forwards the service message 5 to the network node G through the outbound interface 3.

[0141] After receiving service message 5 through the inbound interface connected to network node H, network node G determines that the destination MAC address of service message 5 is the preset MAC address, and therefore marks service message 5 as a wraparound message. Network node G decapsulates the outer Ethernet header of service message 5. Network node G searches for the FIB table entry according to the destination IP address in the IP header, and obtains the value of the forwarding attribute from the found FIB table entry. If the obtained value of the forwarding attribute is the first value, and service message 5 is marked as a wraparound message, it means that it is necessary to use other interfaces in the ring interface group to which the inbound interface belongs in the ring network topology to forward the message. Further, network node G determines the interface that belongs to the same ring interface group as the inbound interface, that is, the outbound interface (referred to as outbound interface 4) connected to network node F on network node G. Network node G encapsulates the outer layer of service message 5 after decapsulating the Ethernet header with an Ethernet header, and the destination MAC address of the encapsulated Ethernet header is the preset MAC address, and obtains service message 6. Network node G forwards service message 6 to network node F through outbound interface 4.

[0142] Subsequent network nodes F, E, D, C, and B complete the forwarding of service messages along network nodes F, E, D, C, and B to network node A in a similar forwarding manner as network node G.

[0143] After network node A receives service message n forwarded by network node B, it determines that the destination MAC address of service message n is the preset MAC address. Therefore, service message n is marked as a wraparound message. Network node A decapsulates the outer Ethernet header of service message n. Network node A searches the FIB table entry according to the destination IP address in the IP header, and obtains the forwarding attribute, the outgoing interface identifier, and the next-hop IP address from the found FIB table entry. The value of the obtained forwarding attribute is the second value, and service message n is marked as a wraparound message, indicating that down-loop forwarding is required. Therefore, network node A searches the ARP table for the MAC address corresponding to the next-hop IP address obtained from the FIB table entry, that is, the MAC address of network node X (MAC_X). The outer layer of service message n after decapsulating the Ethernet header is encapsulated with an Ethernet header, and the destination MAC address in the encapsulated Ethernet header is MAC_X, and service message n+1 is obtained. Network node A forwards service packet n+1 through the outbound interface (the interface connected to network node X) indicated by the outbound interface identifier obtained from the FIB table entry, thereby forwarding service packet n+1 to network node X.

[0144] So far, the service message forwarding from network node Y to network node X in the case of link failure is completed through the above method.

[0145] For service flow 2, the service packets that constitute service flow 2 all contain an inner IP header (in Fig.11 The destination IP addresses in the inner IP headers of the service packets constituting service flow 2 are all the IP addresses of network node W, which will not be described in detail below.

[0146] In another example, when the link is normal, network node Z sends service message 7 to network node E. Among them, service message 7 includes an Ethernet header, an inner IP header and a data part from the outer layer to the inner layer, and the destination MAC address included in the Ethernet header is the MAC address (MAC_E) of network node E. Network node Z can forward service message 7 to network node E according to MAC_E.

[0147] Network node E is a network node in the ring network topology, and a tunnel exists in the ring network topology. Service messages entering the ring network topology will be encapsulated in the tunnel header to achieve tunnel forwarding. For example, the VXLAN (Virtual Extensible Local Area Network) tunnel header includes a VXLAN header, an outer UDP (User Datagram Protocol) header, and an outer IP header. The tunnel header is located between the Ethernet header and the inner IP header.

[0148] Specifically, there is a pre-set tunnel between network node E and network node C. After receiving service message 7, network node E decapsulates the outer Ethernet header and obtains the destination IP address (IP address of network node W) in the inner IP header. Network node E searches for the FIB table entry that matches the destination IP address in the FIB and obtains the next hop information contained in the FIB table entry, which indicates the tunnel forwarding table entry. The tunnel forwarding table entry contains the IP address (IP_C) of network node C at the other end of the tunnel, the IP address and MAC address (MAC_D) of the next hop node (network node D), and the outbound interface identifier (the identifier of the interface on network node E connected to network node D). Network node E encapsulates the outer layer of service message 7 after decapsulating the Ethernet header with a tunnel header, and the destination IP address in the tunnel header is IP_C. Then, the Ethernet header is encapsulated in the outer layer of the tunnel header to obtain service message 8, and the destination MAC address of the encapsulated Ethernet header is MAC_D. Network node E forwards service message 8 to network node D according to MAC_D through the outbound interface indicated by the outbound interface identifier in the tunnel forwarding table entry. It should be noted that Fig.11 Only the destination IP address (IP_C) in the tunnel header is shown, and other information included in the tunnel header is omitted.

[0149] After receiving service message 8, network node D decapsulates the outermost Ethernet header of service message 8. After that, network node D searches the FIB table entry that matches the destination IP address in the tunnel header, obtains the next-hop IP address included in the FIB table entry, and then searches the ARP table for the MAC address corresponding to the next-hop IP address, that is, the MAC address of network node C (MAC_C). Network node D encapsulates the outermost Ethernet header of service message 8 after decapsulating the Ethernet header to obtain service message 9. The destination MAC address of the encapsulated Ethernet header is MAC_C. Network node D forwards service message 9 to network node C according to MAC_C.

[0150] After receiving the service message 9, the network node C decapsulates the outermost Ethernet header of the service message 9. After that, the network node C determines that the destination IP address (IP_C) in the tunnel header is its own IP address, so the network node C decapsulates the tunnel header of the service message 9. After that, the network node C obtains the destination IP address in the inner IP header (the IP address of the network node W). The network node C searches the FIB table entry that matches the IP address of the network node W. The next hop IP address included in the FIB table entry is obtained. Then the MAC address corresponding to the next hop IP address is searched from the ARP table, that is, the MAC address (MAC_W) of the network node W. The network node C encapsulates the Ethernet header in the outer layer of the service message 9 that decapsulates the Ethernet header and the tunnel header to obtain the service message 10. The destination MAC address of the encapsulated Ethernet header is MAC_W. The network node C forwards the service message 10 to the network node W according to MAC_W.

[0151] At this point, the forwarding of the service message from network node Z to network node W is completed.

[0152] exist Fig.11 In the ring network topology shown, if the link between network node D and network node C fails, for service flow 2, the process of network node Z forwarding service message 7 to network node E is the same as above and will not be repeated here.

[0153] After the subsequent service message enters the ring network topology, the solution provided by the embodiment of the present application is used to forward the service message. There is a pre-set tunnel between network node E and network node C. After network node E receives service message 7, since the input interface of service message 7 is connected to network node Y outside the ring network topology, service message 7 is marked as an incoming ring message. Decapsulate the outer Ethernet header and obtain the destination IP address (IP address of network node W) in the inner IP header. Network node E searches the FIB for the FIB entry that matches the destination IP address, obtains the next hop information and forwarding attribute value contained in the FIB entry, and the next hop information indicates the tunnel forwarding table entry. The tunnel forwarding table entry contains the IP address (IP_C) of network node C at the other end of the tunnel, the IP address and MAC address (MAC_D) of the next hop node (network node D), and the outbound interface identifier. The outbound interface identifier indicates the outbound interface (outbound interface 5 for short) on network node E that is connected to network node D. Network node E determines that outbound interface 5 is in the UP state, and the value of the forwarding attribute obtained is the first value, and service message 7 is marked as an incoming ring message, which means that the service message needs to be forwarded through outbound interface 5 in the ring network topology. Then, network node E encapsulates the outer layer of service message 7 after decapsulating the Ethernet header with a tunnel header, and the destination IP address in the tunnel header is IP_C. Then, the Ethernet header is encapsulated in the outer layer of the tunnel header to obtain service message 8, and the destination MAC address of the encapsulated Ethernet header is MAC_D. Network node E forwards service message 8 to network node D through outbound interface 5 according to MAC_D.

[0154] After receiving the service message 8, the network node D is connected to the network node E in the ring network topology according to the input interface of the service message 8, and the service message 8 is marked as an in-ring message. In addition, the network node D decapsulates the outermost Ethernet header of the service message 8, searches the FIB table entry according to the IP_C in the tunnel header, and obtains the value of the output interface identifier and the forwarding attribute from the found FIB table entry. The output interface identifier indicates the output interface (referred to as output interface 6) connected to the network node C on the network node D. The network node D determines that the output interface 6 is in the DOWN state, and the value of the forwarding attribute obtained is the first value, and the service message 8 is marked as an in-ring message, which means that it is necessary to use other output interfaces in the ring interface group to which the output interface 6 belongs in the ring network topology to forward the service message. Furthermore, the network node D determines the interface that belongs to the same ring interface group as the output interface 6, that is, the output interface (referred to as output interface 7) connected to the network node E on the network node D. The network node D encapsulates the Ethernet header in the outer layer of the service message 8 after decapsulating the Ethernet header, and the destination MAC address of the encapsulated Ethernet header is the preset MAC address, thereby obtaining the service message 11. Since there are service messages 9 and 10 in the previous example, in order to distinguish the service messages in the previous example, this service message is referred to as service message 11. The network node D forwards the service message 11 to the network node E through the outbound interface 7.

[0155] After receiving the service message 11 through the inbound interface connected to the network node D, the network node E determines that the destination MAC address of the service message 11 is the preset MAC address. Therefore, the service message 11 is marked as a wraparound message. The network node E decapsulates the outermost Ethernet header of the service message 11. The network node E searches for the FIB table entry according to the destination IP address (IP_C) in the tunnel header, and obtains the value of the forwarding attribute from the found FIB table entry. The obtained forwarding attribute value is the first value, and the service message 11 is marked as a wraparound message, which means that it is necessary to use other interfaces in the ring interface group to which the inbound interface belongs in the ring network topology to forward the message. Then the network node E determines the interface that belongs to the same ring interface group as the inbound interface, that is, the outbound interface (referred to as outbound interface 8) connected to the network node F on the network node E. The network node E encapsulates the Ethernet header in the outermost layer of the service message 11 after decapsulating the Ethernet header, and the destination MAC address of the encapsulated Ethernet header is the preset MAC address, and obtains the service message 12. Network node E forwards service message 12 to network node F through outbound interface 8 .

[0156] Subsequent network nodes F, network node G, network node H, network node A, and network node B complete the forwarding of service messages along network nodes F, network node G, network node H, network node A, and network node B to network node C in a similar forwarding manner as network node E.

[0157] After network node C receives the service message m forwarded by network node B, it determines that the destination MAC address of service message m is the preset MAC address. Therefore, service message m is marked as a wraparound message. Network node C decapsulates the outermost Ethernet header of service message m. Network node C determines that the destination IP address in the tunnel header is its own IP address (IP_C), so it decapsulates the tunnel header in service message m and obtains the destination IP address in the inner IP header (IP address of network node W). Network node C searches the FIB table entry according to the destination IP address in the inner IP header, and obtains the value of the forwarding attribute, the outgoing interface identifier, and the next-hop IP address from the found FIB table entry. The obtained forwarding attribute value is the second value, and service message m is marked as a wraparound message, which means that down-loop forwarding is required. Therefore, network node C searches the ARP table for the MAC address corresponding to the next-hop IP address, that is, the MAC address MAC_W of network node W, based on the next-hop IP address obtained from the FIB table entry. After decapsulating the Ethernet header and the tunnel header, the outer layer of the service message m is encapsulated with an Ethernet header, and the destination MAC address of the encapsulated Ethernet header is MAC_W, obtaining the service message m+1. Network node C forwards the service message m+1 to network node W according to MAC_W through the outbound interface (the interface connected to network node W) indicated by the outbound interface identifier obtained from the FIB table entry.

[0158] So far, the service message forwarding from the network node Z to the network node W in the case of a link failure is completed in the above manner.

[0159] That is, the ring network topology can realize the forwarding of underlay flow and overlay flow when the link is normal or abnormal.

[0160] In another embodiment of the present application, the first node further performs the following steps P-R to configure the value of the forwarding attribute in the FIB table entry.

[0161] Step P: If the interface indicated by the outgoing interface identifier contained in any FIB table entry is connected to other nodes in the ring network topology except the first node, the value of the forwarding attribute in any FIB table entry is configured as the first value.

[0162] If the interface indicated by the outgoing interface identifier contained in the FIB table entry is connected to other nodes in the ring network topology except the above-mentioned first node, it means that the message forwarded from the outgoing interface is still in the ring network topology, that is, the ring forwarding of the message can be achieved through the interface. Therefore, the value of the forwarding attribute in the FIB table entry is configured as the first value, and the first value is used to indicate the forwarding on the ring.

[0163] Step Q: If the interface indicated by the outgoing interface identifier contained in any FIB table entry is connected to a node outside the ring network topology, the value of the forwarding attribute in any of the above FIB table entries is configured as the second value.

[0164] If the interface indicated by the outgoing interface identifier contained in the FIB table entry is connected to a node outside the ring network topology, it means that the message forwarded from the interface is not in the ring network topology, that is, the message can be forwarded in the lower ring through the interface. Therefore, the value of the forwarding attribute in the FIB table entry is configured as the second value, and the second value is used to indicate the lower ring forwarding.

[0165] Step R: When updating the FIB table items in the above FIB, obtain the cost COST values ​​of the routing table items corresponding to the FIB table items before and after the update. If the COST value corresponding to the updated FIB table item is not less than the COST value corresponding to the FIB table item before the update, configure the value of the forwarding attribute in the updated FIB table item to the third value.

[0166] The first node will perform real-time routing calculations based on the current network status, so that the calculated routes match the actual network status. After a fault occurs in the ring network topology, the first node will recalculate a new forwarding path that avoids the faulty part, so that the routing table entries in the routing table are updated, and further the FIB table entries in the FIB table are updated.

[0167] The first node follows the shortest path principle when performing route calculation. After a fault occurs in the ring network topology, the shortest path that the first node originally used to reach the destination address in the ring network topology is unavailable. The first node will recalculate a new shortest path that can reach the destination address and update the FIB table entry to avoid the faulty part of the ring network topology during subsequent message forwarding.

[0168] The COST value corresponding to the updated FIB table entry is greater than or equal to the COST value of the FIB table entry before the update. In this case, the first node configures the value of the forwarding attribute in the updated FIB table entry to a third value, and the third value indicates a wraparound protection state. In this way, after a failure occurs in the ring network topology, the first node can forward the message according to the third value, avoiding the problem of tangent micro-rings in the process of forwarding messages in the new shortest path.

[0169] The following introduces the causes of the tangent micro-ring problem and the method for solving the tangent micro-ring problem in the embodiments of the present application.

[0170] When the TI-LFA FRR technology is used in the related art to handle the fault of the ring network topology, there is a problem of tangent micro-ring. Specifically, the following Fig.12 and Fig.13 Describe the specific meaning of tangent microring.

[0171] See also Fig.12 , which is a schematic diagram of the first tangent micro-ring in the related art.

[0172] Fig.12 The structure of the network Figure 1 The solid arrows indicate the forwarding path of packets during normal forwarding, and the dotted arrows indicate the forwarding path of packets during fault handling.

[0173] Depend on Fig.12 It can be seen that when network node Y sends a message to network node X, the message is first forwarded from network node Y to network node G, and then forwarded from network node G to network node H. Due to the link failure between network node H and network node A. Therefore, after the FIB table entry of network node H is updated, the message is forwarded according to the updated FIB table entry. That is, network node H will forward the message to network node G clockwise along dotted arrow 1. However, if the FIB table entry of network node G has not been updated at this time, network node G will still forward the message according to the original FIB table entry, that is, it will send the message to network node H along dotted arrow 2 again. Thus, a loop is formed between network node G and network node H. The message will be forwarded uselessly, and there is a problem of tangent micro-loop.

[0174] See also Fig.13 , which is a schematic diagram of the second type of tangent micro-ring in the related art.

[0175] Fig.13 The structure of the network Figure 1 The solid arrows indicate the forwarding path of packets during normal forwarding, and the dotted arrows indicate the forwarding path of packets during fault handling.

[0176] Depend on Fig.13 It can be seen that when network node Y sends a message to network node X, the message is initially forwarded from network node Y to network node G. Due to the link failure between network node G and network node H. Therefore, after the FIB table entry of network node G is updated, the message is forwarded according to the updated FIB table entry. That is, network node G will forward the message to network node F clockwise along dotted arrow 1. However, if the FIB table entry of network node F has not been updated at this time, network node F will still forward the message to network node X according to the original FIB table entry and the shortest path, that is, it will send the message to network node G along dotted arrow 2. Thus, a loop is formed between network node G and network node F. That is, due to the asynchronous update of FIB table entries between network nodes, the message will be forwarded uselessly, and there is a problem of tangent micro-ring.

[0177] In order to deal with the above-mentioned tangent micro-ring problem, the TI-LFA FRR technology needs to additionally configure a tangent anti-micro-ring mechanism, which further increases the complexity of the TI-LFA FRR technology.

[0178] In the embodiment of the present application, in order to solve the problem of tangent micro-ring, see Fig.14 , is a schematic diagram of a tangent anti-microring process provided in an embodiment of the present application, including the following steps S1401-S1403.

[0179] S1401: Receive the seventh message sent by the eighth node.

[0180] Among them, the seventh message includes the fourth destination IP address.

[0181] S1402: According to the fourth destination IP address, obtain from the FIB a fourth FIB entry matching the fourth destination IP address.

[0182] The fourth FIB table entry includes a third outbound interface identifier and a fourth forwarding attribute, and the third outbound interface identifier indicates the seventh interface.

[0183] S1403: If the value of the fourth forwarding attribute is the third value, forward the eighth message to the ninth node through the seventh interface.

[0184] The sixth destination MAC address included in the eighth message is the preset MAC address, so that the ninth node forwards the eighth message according to the preset MAC address.

[0185] If the value of the fourth forwarding attribute is the third value, it means that the fourth FIB table entry is an entry in the wrap-around protection state. In this case, the first node receives the seventh message, decapsulates the Ethernet header of the seventh message, and then encapsulates the Ethernet header whose destination MAC address is the preset MAC address for the seventh message after the decapsulation of the Ethernet header to obtain the eighth message, to indicate that the eighth message is a wrap-around message, and forwards the eighth message to the ninth node through the seventh interface.

[0186] If the network node receiving the eighth message is a transit node, then if the FIB entry in the transit node is not updated, after receiving the eighth message, it can be determined that the eighth message is a wraparound message based on the preset MAC address in the Ethernet header, and then according to the above Figure 7 The illustrated embodiment performs message forwarding on the wrapped message. Figure 7 In the embodiment shown, when forwarding the wrapped message, the message will not be forwarded according to the outgoing interface indicated by the outgoing interface identifier recorded in the FIB entry. Therefore, the message can be forwarded even if the FIB entry is not updated. If the FIB entry in the forwarding node has been updated, the forwarding node will forward the message according to the outgoing interface identifier recorded in the FIB entry. Fig.14In addition, if the network node receiving the eighth message is a downlink node, after the downlink node receives the eighth message and determines that the eighth message is a wraparound message based on the preset MAC address in the Ethernet header, if the FIB table entry of the downlink node is not updated, the above method can be used. Figure 8 In the embodiment shown, the outbound interface indicated by the outbound interface identifier recorded in the FIB table entry is forwarded to the network node outside the ring network topology. Fig.14 The illustrated embodiment can also implement message forwarding.

[0187] It can be seen that the problem of tangent micro-loops caused by asynchronous FIB updates of different network nodes can be avoided through the embodiments of the present application.

[0188] For example, in the aforementioned Fig.12 In the embodiment shown, the FIB entry of network node H has been updated, and the FIB entry of network node G has not been updated. In order to avoid the faulty link between network node H and network node A, the interface indicated by the outgoing interface identifier in the updated FIB entry of network node H should be the interface with network node G. Then network node H based on the above Fig.14 In the embodiment shown in the figure, based on the updated FIB table entry, a message is sent to the network node G, and the destination MAC address of the message is the preset MAC address. After receiving the message, the network node G follows the above Figure 8 The illustrated embodiment continues to forward the message to the network node F, thereby avoiding the problem of a loop being formed between the network node H and the network node G.

[0189] See also Fig.15 , which is a fifth message forwarding diagram for a ring network failure provided in an embodiment of the present application.

[0190] Fig.15 The network structure shown in Figure 1 The same, and Fig.15 and Figure 1 The scenarios are all scenarios where a message is sent from network node Y to network node X. Fig.15 In the example, there is a fault in the link between network node H and network node A. Assume Fig.15The FIB entry of network node G as the ingress node has been updated. In this case, in order to avoid the faulty link between network node H and network node A, the interface indicated by the outgoing interface identifier in the updated FIB entry should be the interface between network node G and network node F. Then, as the first node, network node G first decapsulates the Ethernet header of the seventh message after receiving the seventh message, and then encapsulates the Ethernet header with the destination MAC address as the preset MAC address (i.e., MAC_P in the figure) to obtain the eighth message, and forwards the eighth message to network node F. After receiving the eighth message, network node F will subsequently forward the message to network node E according to the aforementioned steps S404-S406, instead of Fig.13 As shown, the message is forwarded to the network node G. Thus, the problem of a loop being formed between the network node F and the network node G can be avoided.

[0191] From the above, it can be seen that through the solution provided by the embodiment of the present application, when a fault occurs in the ring network topology, the first node forwards the message according to the FIB table entry in the wrap-around protection state, and other network nodes forward the message in the aforementioned manner. In this way, positive switching to prevent micro-loops can be achieved.

[0192] Furthermore, after the fault is restored, the message forwarding path will be restored to the path before the fault. The routing convergence speeds of different network nodes are different. Therefore, the forwarding path indicated by the FIB table entries recorded in some network nodes is the forwarding path after the fault, while the forwarding path indicated by the FIB table entries recorded in other network nodes is the forwarding path before the fault. As a result, the message forms a forwarding loop before the network node, causing the problem of micro-loop switching back.

[0193] See also Fig.16 , which is a schematic diagram of a back-cut micro-ring in the related art.

[0194] Fig.16 The network structure shown in Figure 1 Same. And Fig.16 The link between network node H and network node A fails, causing the routes of each network node in the network to reconverge, and the generated forwarding path avoids the link between network node H and network node A.

[0195] Therefore, for the message sent to network node X, after the route reconverges, the interface indicated by the outgoing interface identifier recorded in the FIB table entry in network node H should be the interface connected to network node G. The interface indicated by the outgoing interface identifier recorded in the FIB table entry in network node G should be the interface connected to network node F.

[0196] On this basis, the "√" symbol in the figure indicates that the link between network node H and network node A has returned to normal. Then the routes of each network node need to be reconverged. For the message sent to network node X, if the route of network node G converges first, the interface indicated by the outgoing interface identifier recorded in network node G is the interface connected to network node H. However, if the route of network node H has not been reconverged at this time, the interface indicated by the outgoing interface identifier recorded in network node H is still the interface connected to network node G.

[0197] Therefore, the destination MAC address of the message sent by the network node G to the network node H is MAC_H, and the destination MAC address of the message sent by the network node H to the network node G is MAC_G. A loop is formed in the network, and there is a problem of switching back micro-loops.

[0198] To solve the above problems, see Fig.17 , a schematic diagram of a process of switching back to prevent micro-loop is provided for an embodiment of the present application, including the following steps S1701-S1702.

[0199] S1701: If it is determined that the eighth interface is restored from the DOWN state to the connection UP state, or the first routing protocol message is received through the eighth interface, routing recovery is performed and the FIB table entry in the FIB is updated.

[0200] The eighth interface is the interface of the first node, and the recovery of the eighth interface means the recovery of the interface of the first node itself, and the first node needs to perform routing recovery and update the FIB table items.

[0201] In addition, receiving the first routing protocol message through the eighth interface means that the other nodes instruct the first node to perform routing recovery and update the FIB table entry.

[0202] The first routing protocol message may be a BGP (Border Gateway Protocol, Border Gateway Protocol) message or an IGP (Interior Gateway Protocol, Interior Gateway Protocol) message.

[0203] S1702: Send a second routing protocol message to a tenth node on the ring network topology through a ninth interface, so that the tenth node performs routing recovery and updates a FIB table entry in a local FIB after receiving the second routing protocol message.

[0204] The eighth interface and the ninth interface belong to the same on-ring interface group, and the second routing protocol message is generated according to the updated FIB entry of the first node.

[0205] After the first node completes the FIB table entry update, it sends a second routing protocol message to the tenth node, so that the tenth node updates the FIB table entry, thereby controlling the tenth node's FIB table entry update to be later than the first node.

[0206] by Fig.16 Taking the scenario shown as an example, the fault of the ring interface of network node H (i.e., the interface on network node H connected to network node A) is restored. In this case, network node H first determines that the eighth interface is restored from the DOWN state to the connection UP state, so network node H first executes step S1701 to perform routing recovery and update the FIB table entry. For the message sent to network node X, the interface indicated by the outgoing interface identifier in the updated FIB table entry is changed to the interface on network node H connected to network node A. Then network node H executes step S1702 to send a routing protocol message through the ninth interface (i.e., the interface other than the restored ring interface in the ring interface group). Since the restored ring interface is the interface on network node H connected to network node A, the corresponding ninth interface is the interface on network node H connected to network node G. That is, network node H sends a routing protocol message to network node G.

[0207] At this time, Fig.16 In the scenario shown, only the route of network node H is restored, and the FIB entry of network node B-network node G is still the FIB entry calculated after the link between network node H and network node A fails. Fig.15 As described in the description, after the link between network node H and network node A fails, the interface indicated by the outgoing interface identifier in the updated FIB table entry in network node G is the interface between network node G and network node F. Therefore, when network node G needs to send a message to network node X, network node G will still forward the message to network node F, and network node F will forward the message to network node E, and so on. The message can still be forwarded clockwise to network node A, and then forwarded to network node X. It can be seen that there will be no problem of switching back micro-rings in this process.

[0208] Afterwards, network node G receives the routing protocol message sent by network node H, and as the first node, performs step S1701 to perform routing recovery and update the FIB table entry. For the message sent to network node X, the outgoing interface indicated by the updated FIB table entry is changed to the interface on network node G connected to network node H. Afterwards, network node G performs step S1702 to send the routing protocol message through the ninth interface (i.e., an interface other than the interface receiving the routing protocol message in the ring interface group). Since the interface on network node G that receives the routing protocol message is the interface on network node G connected to network node H, the corresponding ninth interface is the interface on network node G connected to network node F. That is, network node G sends the routing protocol message to network node F.

[0209] In this case, since the routes of network node G and network node H are restored, in this case, for the message sent to network node X, network node G forwards the message to network node H, network node H then forwards the message to network node A, and finally network node A sends the message to network node X. Message forwarding can also be achieved, and the problem of switching back micro-rings will not occur.

[0210] Afterwards, after the route of network node G is restored, it sends a routing protocol message to network node F. After the route of network node F is restored, it sends a routing protocol message to network node E, and so on. The route is restored in sequence from downstream to upstream according to the message forwarding direction before the failure (i.e., counterclockwise direction), thereby avoiding the problem of micro-loop switching back.

[0211] It can be seen from the above that, in the solution provided by the embodiment of the present application, each network node can perform routing recovery in sequence from downstream to upstream in the order of message forwarding direction before the failure, thereby avoiding the problem of switching back micro-rings.

[0212] Corresponding to the aforementioned ring network fault handling method, the embodiment of the present application also provides a ring network fault handling device.

[0213] See also Fig.18 , a ring network fault processing device provided in an embodiment of the present application, applied to a first node, the first node is in a ring network topology, the device comprising: A first message receiving module 1801 is configured to receive a first message sent by a second node, where the first message includes a first destination IP address; A first entry acquisition module 1802 is configured to acquire, according to the first destination IP address, a first FIB entry matching the first destination IP address from a forwarding information table FIB, wherein the first FIB entry includes a first outbound interface identifier and a first forwarding attribute, wherein the first outbound interface identifier indicates a first interface; A first message forwarding module 1803 is configured to forward a second message to a third node in the ring network topology through a second interface if the value of the first forwarding attribute is a first value and the first interface is in a disconnected DOWN state, wherein the first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address; The first interface and the second interface belong to the same ring interface group.

[0214] In the embodiment of the present application, if the first node in the ring network topology obtains the first FIB table item matching the first destination IP address of the first message from the FIB after receiving the first message, the first FIB table item contains the first forwarding attribute and the first output interface identifier. If the value of the first forwarding attribute is the first value, it means that the message needs to be forwarded on the ring, that is, the first node needs to forward the message to other nodes on the ring network topology. In this case, if the first interface indicated by the first output interface identifier is in the DOWN state, the first node can no longer send the message through the first interface. Since the first interface and the second interface both belong to the ring interface group, that is, they are both interfaces on the first node connected to the network node in the ring network topology. Changing the first interface for forwarding the first message to the second interface is equivalent to changing the forwarding direction of the message. Since the network nodes in the ring network topology are connected to form a ring, the message forwarding can be completed normally even if the forwarding direction is changed. In addition, by handling network failures in the manner of the embodiment of the present application, there is no need to calculate complex backup paths and backup output interfaces in the first node, and it is only necessary to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of network nodes, and ring network fault processing can be achieved in a simple way.

[0215] In one embodiment of the present application, the device further includes: A second message receiving module, used to receive a third message sent by the fourth node through a third interface, wherein the third message includes a second destination MAC address and a second destination IP address; A second entry acquisition module, configured to acquire, from the FIB, a second FIB entry matching the second destination IP address when the second destination MAC address is the preset MAC address, wherein the second FIB entry includes a second forwarding attribute; A second message forwarding module, configured to forward a fourth message to a fifth node in the ring network topology through a fourth interface if the value of the second forwarding attribute is the first value, wherein the third destination MAC address included in the fourth message is the preset MAC address, so that the fifth node forwards the fourth message according to the preset MAC address; The third interface and the fourth interface belong to the same ring interface group.

[0216] As can be seen from the above, in the embodiment of the present application, after the first node receives the third message whose destination MAC address is the preset MAC address, it can determine that the third message is a message forwarded in the event of a fault. And the value of the second forwarding attribute is the first value, indicating that the message needs to be forwarded in the ring network topology, then the first node forwards the message to the fourth interface that belongs to the same ring interface group as the input interface. Therefore, even if the backup path and the backup output interface are not recorded in the first node, the message can be forwarded when the third message is received. The first node still does not need to calculate the complex backup path and backup output interface, and only needs to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of the network nodes, and ring network fault handling can be achieved in a simple way.

[0217] In one embodiment of the present application, the device further includes: A third message receiving module, used to receive a fifth message sent by a sixth node through a fifth interface, wherein the fifth message includes a third destination IP address and a fourth destination MAC address; A third table entry acquisition module, configured to, when the fourth destination MAC address is the preset MAC address, acquire, from the FIB, a third FIB table entry matching the third destination IP address, the third FIB table entry including a third forwarding attribute and a second outbound interface identifier, wherein the second outbound interface identifier indicates a sixth interface; The third message forwarding module is used to forward the sixth message to the seventh node outside the ring network topology through the sixth interface if the value of the third forwarding attribute is the second value, and the fifth destination MAC address included in the sixth message is the MAC address of the seventh node.

[0218] As can be seen from the above, in the embodiment of the present application, after the first node receives the third message whose destination MAC address is the preset MAC address, it can determine that the third message is a message forwarded in the event of a fault. And the value of the second forwarding attribute is the first value, indicating that the message needs to be forwarded in the ring network topology, then the first node forwards the message to the fourth interface that belongs to the same ring interface group as the input interface. Therefore, even if the backup path and the backup output interface are not recorded in the first node, the message can be forwarded when the third message is received. The first node still does not need to calculate the complex backup path and backup output interface, and only needs to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of the network nodes, and ring network fault handling can be achieved in a simple way.

[0219] In one embodiment of the present application, the device further includes: A first interface group determining module, used to determine the first on-ring interface group to which the first interface belongs; The first interface determination module is used to determine the interfaces in the first on-ring interface group except the first interface as second interfaces.

[0220] In one embodiment of the present application, the device further includes: A second interface group determination module, used to determine the interface group on the second ring to which the third interface belongs; The second interface determination module is used to determine the interfaces in the second ring interface group except the third interface as the fourth interface.

[0221] In one embodiment of the present application, the device further includes: A first message marking module, configured to mark the first message as an in-ring message if an inbound interface receiving the first message is connected to a node on the ring network topology; A second message marking module, configured to mark the first message as a ring-in message if the inbound interface receiving the first message is connected to a node outside the ring network topology; The first message forwarding module 1803 is specifically used to forward the second message to the third node in the ring network topology through the second interface if the value of the first forwarding attribute is a first value, and the first interface is in a DOWN state, and the first message is marked as an in-loop message or an in-loop message, and the first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address.

[0222] In one embodiment of the present application, the device further includes: A third message marking module, configured to mark the third message as a wrap message when determining that the second destination MAC address is the preset MAC address; The second message forwarding module is specifically used for: If the value of the second forwarding attribute is the first value and the third message is marked as a wraparound message, the fourth message is forwarded to the fifth node in the ring network topology through the fourth interface, and the third destination MAC address included in the fourth message is the preset MAC address, so that the fifth node forwards the fourth message according to the preset MAC address.

[0223] In one embodiment of the present application, the device further includes: A fourth message marking module, configured to mark the fifth message as a wrap message when determining that the fourth destination MAC address is the preset MAC address; The third message forwarding module is specifically used for: If the value of the third forwarding attribute is the second value, and the fifth message is marked as a wraparound message, the sixth message is forwarded to a seventh node outside the ring network topology through the sixth interface.

[0224] In one embodiment of the present application, the device further includes: The interface group creation module is used to create an interface group on the ring, wherein the interface group on the ring includes interface identifiers of at least two interfaces, and the at least two interfaces both belong to the first node and are connected to other nodes in the ring network topology except the first node.

[0225] In one embodiment of the present application, the device further includes: a fourth message receiving module, configured to receive a seventh message sent by the eighth node, wherein the seventh message includes a fourth destination IP address; a fourth entry acquisition module, configured to acquire, from the FIB, according to the fourth destination IP address, a fourth FIB entry matching the fourth destination IP address, wherein the fourth FIB entry includes a third outgoing interface identifier and a fourth forwarding attribute, and the third outgoing interface identifier indicates a seventh interface; The fourth message forwarding module is used to forward the eighth message to the ninth node through the seventh interface if the value of the fourth forwarding attribute is the third value, and the sixth destination MAC address included in the eighth message is the preset MAC address, so that the ninth node forwards the eighth message according to the preset MAC address.

[0226] From the above, it can be seen that through the solution provided by the embodiment of the present application, when a fault occurs in the ring network topology, the first node forwards the message according to the FIB table entry in the wrap-around protection state, and other network nodes forward the message in the aforementioned manner. In this way, positive switching to prevent micro-loops can be achieved.

[0227] In one embodiment of the present application, the device further includes: a first value configuration module, configured to configure the value of the forwarding attribute in any FIB table entry to be a first value if the interface indicated by the outgoing interface identifier contained in any FIB table entry is connected to other nodes in the ring network topology except the first node; A second value configuration module, configured to configure the value of the forwarding attribute in any FIB table entry to a second value if the interface indicated by the outgoing interface identifier contained in any FIB table entry is connected to a node outside the ring network topology; The third value configuration module is used to obtain the cost COST values ​​of the routing table items corresponding to the FIB table items before and after the update when updating the FIB table items in the FIB. If the COST value corresponding to the updated FIB table item is not less than the COST value corresponding to the FIB table item before the update, the value of the forwarding attribute in the updated FIB table item is configured as the third value.

[0228] In one embodiment of the present application, the device further includes: A table entry updating module, configured to perform routing recovery and update the FIB table entry in the FIB if it is determined that the eighth interface is restored from a DOWN state to a connection UP state, or a first routing protocol message is received through the eighth interface; A protocol message sending module, used for sending a second routing protocol message to a tenth node on the ring network topology through a ninth interface, so that the tenth node performs routing recovery and updates a FIB table entry in a local FIB after receiving the second routing protocol message; The eighth interface and the ninth interface belong to the same on-ring interface group, and the second routing protocol message is generated according to the FIB table entry updated by the first node.

[0229] It can be seen from the above that, in the solution provided by the embodiment of the present application, each network node can perform routing recovery in sequence from downstream to upstream in the order of message forwarding direction before the failure, thereby avoiding the problem of switching back micro-rings.

[0230] In one embodiment of the present application, the preset MAC address is a unicast preset MAC address or a multicast preset MAC address, and the unicast preset MAC address is different from the multicast preset MAC address.

[0231] Corresponding to the aforementioned ring network fault handling method, the embodiment of the present application also provides a network node.

[0232] See also Fig.19 , is a schematic diagram of the structure of a network node provided in an embodiment of the present application, the network node is located in a ring network topology as a first node, and the network node includes: Processor 1901; Transceiver 1904; The machine-readable storage medium 1902 stores machine-executable instructions that can be executed by the processor; the machine-executable instructions prompt the processor to execute any one of the method steps in the ring network fault processing method.

[0233] like Fig.19As shown, the network device may further include a communication bus 1903. The processor 1901, the machine-readable storage medium 1902, and the transceiver 1904 communicate with each other through the communication bus 1903. The communication bus 1903 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 1903 may be divided into an address bus, a data bus, a control bus, and the like.

[0234] The transceiver 1904 may be a wireless communication module, and under the control of the processor 1901 , the transceiver 1904 performs data exchange with other devices.

[0235] The machine-readable storage medium 1902 may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk storage. In addition, the machine-readable storage medium 1902 may also be at least one storage device located away from the aforementioned processor.

[0236] Processor 1901 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, and discrete hardware components.

[0237] In the embodiment of the present application, if the first node in the ring network topology obtains the first FIB table item matching the first destination IP address of the first message from the FIB after receiving the first message, the first FIB table item contains the first forwarding attribute and the first output interface identifier. If the value of the first forwarding attribute is the first value, it means that the message needs to be forwarded on the ring, that is, the first node needs to forward the message to other nodes on the ring network topology. In this case, if the first interface indicated by the first output interface identifier is in the DOWN state, the first node can no longer send the message through the first interface. Since the first interface and the second interface both belong to the ring interface group, that is, they are both interfaces on the first node connected to the network node in the ring network topology. Changing the first interface for forwarding the first message to the second interface is equivalent to changing the forwarding direction of the message. Since the network nodes in the ring network topology are connected to form a ring, the message forwarding can be completed normally even if the forwarding direction is changed. In addition, by handling network failures in the manner of the embodiment of the present application, there is no need to calculate complex backup paths and backup output interfaces in the first node, and it is only necessary to forward the message according to the ring interface group during the message forwarding process. There is no need to consume a large amount of resources of network nodes, and ring network fault processing can be achieved in a simple way.

[0238] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned ring network fault handling methods are implemented.

[0239] In another embodiment provided in the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute any ring network fault handling method in the above embodiments.

[0240] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part 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, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive Solid State Disk (SSD)), etc.

[0241] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0242] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, network node, computer-readable storage medium, and computer program product embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0243] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A ring network fault processing method, characterized in that: Applied to a first node, where the first node is in a ring network topology, the method includes: Receiving a first message sent by a second node, wherein the first message includes a first destination IP address; According to the first destination IP address, obtaining a first FIB table entry matching the first destination IP address from a forwarding information table FIB, wherein the first FIB table entry includes a first outbound interface identifier and a first forwarding attribute, wherein the first outbound interface identifier indicates a first interface; If the value of the first forwarding attribute is a first value and the first interface is in a disconnected DOWN state, forwarding a second message to a third node in the ring network topology through a second interface, wherein the first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address; The first interface and the second interface belong to the same ring interface group.

2. The method according to claim 1, characterized in that The method further comprises: Receiving, through the third interface, a third message sent by the fourth node, wherein the third message includes a second destination MAC address and a second destination IP address; When the second destination MAC address is the preset MAC address, obtaining a second FIB table entry matching the second destination IP address from the FIB, wherein the second FIB table entry includes a second forwarding attribute; If the value of the second forwarding attribute is the first value, forwarding a fourth message to a fifth node in the ring network topology through a fourth interface, wherein the third destination MAC address included in the fourth message is the preset MAC address, so that the fifth node forwards the fourth message according to the preset MAC address; The third interface and the fourth interface belong to the same ring interface group.

3. The method according to claim 1, characterized in that The method further comprises: Receiving, through the fifth interface, a fifth message sent by the sixth node, wherein the fifth message includes a third destination IP address and a fourth destination MAC address; When the fourth destination MAC address is the preset MAC address, obtaining, from the FIB, a third FIB table entry matching the third destination IP address, the third FIB table entry including a third forwarding attribute and a second outbound interface identifier, wherein the second outbound interface identifier indicates a sixth interface; If the value of the third forwarding attribute is the second value, the sixth message is forwarded to the seventh node outside the ring network topology through the sixth interface, and the fifth destination MAC address included in the sixth message is the MAC address of the seventh node.

4. The method according to claim 1, characterized in that: Before forwarding the second message to the third node in the ring network topology through the second interface, the method further includes: Determine a first interface group on the ring to which the first interface belongs; Interfaces in the first ring interface group except the first interface are determined as second interfaces.

5. The method according to claim 2, characterized in that: Before forwarding the fourth message to the fifth node in the ring network topology through the fourth interface, the method further includes: Determine the interface group on the second ring to which the third interface belongs; The interfaces in the interface group on the second ring except the third interface are determined as fourth interfaces.

6. The method according to claim 1, characterized in that After receiving the first message sent by the second node, the method further includes: If the inbound interface receiving the first message is connected to a node on the ring network topology, marking the first message as an in-ring message; If the inbound interface receiving the first message is connected to a node outside the ring network topology, marking the first message as an inbound message; If the value of the first forwarding attribute is a first value and the first interface is in a DOWN state, forwarding the second message to the third node in the ring network topology through the second interface includes: If the value of the first forwarding attribute is a first value, the first interface is in a DOWN state, and the first message is marked as an in-ring message or an incoming-ring message, forward the second message to a third node in the ring network topology through a second interface.

7. The method according to claim 2, characterized in that After receiving the third message sent by the fourth node through the third interface, the method further includes: When determining that the second destination MAC address is the preset MAC address, marking the third message as a wraparound message; If the value of the second forwarding attribute is the first value, forwarding the fourth message to the fifth node in the ring network topology through the fourth interface includes: If the value of the second forwarding attribute is the first value, and the third message is marked as a wraparound message, forwarding the fourth message to a fifth node in the ring network topology through a fourth interface.

8. The method according to claim 3, characterized in that After receiving the fifth message sent by the sixth node through the fifth interface, the method further includes: When determining that the fourth destination MAC address is the preset MAC address, marking the fifth message as a wraparound message; If the value of the third forwarding attribute is the second value, forwarding the sixth message to the seventh node outside the ring network topology through the sixth interface includes: If the value of the third forwarding attribute is the second value, and the fifth message is marked as a wraparound message, the sixth message is forwarded to a seventh node outside the ring network topology through the sixth interface.

9. The method according to any one of claims 1 to 8, characterized in that Before receiving the first message sent by the second node, the method further includes: An on-ring interface group is created, wherein the on-ring interface group includes interface identifiers of at least two interfaces, wherein the at least two interfaces both belong to the first node and are both connected to other nodes on the ring network topology except the first node.

10. The method according to any one of claims 1 to 8, characterized in that The method further comprises: receiving a seventh message sent by the eighth node, wherein the seventh message includes a fourth destination IP address; According to the fourth destination IP address, obtaining, from the FIB, a fourth FIB table entry matching the fourth destination IP address, wherein the fourth FIB table entry includes a third outbound interface identifier and a fourth forwarding attribute, and the third outbound interface identifier indicates a seventh interface; If the value of the fourth forwarding attribute is the third value, the eighth message is forwarded to the ninth node through the seventh interface, and the sixth destination MAC address included in the eighth message is the preset MAC address, so that the ninth node forwards the eighth message according to the preset MAC address.

11. The method according to any one of claims 1 to 8, characterized in that The method further comprises: If the interface indicated by the outgoing interface identifier contained in any FIB table entry is connected to other nodes in the ring network topology except the first node, the value of the forwarding attribute in any FIB table entry is configured as the first value; If the interface indicated by the outgoing interface identifier contained in any FIB table entry is connected to a node outside the ring network topology, configuring the value of the forwarding attribute in any FIB table entry to be the second value; When updating the FIB table items in the FIB, the cost COST values ​​of the routing table items corresponding to the FIB table items before and after the update are obtained. If the COST value corresponding to the updated FIB table item is not less than the COST value corresponding to the FIB table item before the update, the value of the forwarding attribute in the updated FIB table item is configured as a third value.

12. The method according to any one of claims 1 to 8, characterized in that The method further comprises: If it is determined that the eighth interface is restored from the DOWN state to the connection UP state, or the first routing protocol message is received through the eighth interface, routing recovery is performed and the FIB table entry in the FIB is updated; Sending a second routing protocol message to a tenth node on the ring network topology through a ninth interface, so that the tenth node performs routing recovery and updates a FIB table entry in a local FIB after receiving the second routing protocol message; The eighth interface and the ninth interface belong to the same on-ring interface group, and the second routing protocol message is generated according to the updated FIB table entry of the first node.

13. The method according to any one of claims 1 to 8, characterized in that The preset MAC address is a unicast preset MAC address or a multicast preset MAC address, and the unicast preset MAC address is different from the multicast preset MAC address.

14. A ring network fault processing device, characterized in that: Applied to a first node, the first node is in a ring network topology, the device includes: A first message receiving module, configured to receive a first message sent by a second node, wherein the first message includes a first destination IP address; A first table entry acquisition module, configured to acquire, according to the first destination IP address, from a forwarding information table FIB, a first FIB table entry matching the first destination IP address, wherein the first FIB table entry includes a first outbound interface identifier and a first forwarding attribute, and the first outbound interface identifier indicates a first interface; A first message forwarding module, configured to forward a second message to a third node in the ring network topology through a second interface if the value of the first forwarding attribute is a first value and the first interface is in a disconnected DOWN state, wherein the first destination MAC address included in the second message is a preset MAC address, so that the third node forwards the second message according to the preset MAC address; The first interface and the second interface belong to the same ring interface group.

Images