Troubleshooting methods, electronic equipment, media and products

Abstract

This application proposes a fault handling method, electronic device, medium, and product. The fault handling method includes: in response to a silent fault occurring on a port of a network device in a packet to be transmitted, generating a silent fault notification message based on the routing address information of the packet to be transmitted; the silent fault notification message includes a first source IP address and a first destination IP address, wherein the first source IP address is the destination IP address of the packet to be transmitted, and the first destination IP address is the source IP address of the packet to be transmitted; sending the silent fault notification message to the upstream device of the current network device on the current routing forwarding path of the packet to be transmitted; the silent fault notification message is used to notify the target upstream device with routing protection capability for the packet to be transmitted to perform corresponding routing protection operations on the packet to be transmitted.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a fault handling method, electronic device, medium, and product. Background Technology

[0002] In related technologies, the detection of IP (Internet Protocol) network faults is generally triggered by abnormal port activity of network devices. Fault response processing and routing protection can only be triggered if the faulty network device has routing protection capabilities.

[0003] However, in some fault scenarios, a device may experience an abnormal malfunction, but this will not trigger an anomaly in the device port or initiate fault response processing for routing protection. Furthermore, if the faulty network device lacks routing protection capabilities, it cannot promptly trigger fault response processing for routing protection. This can result in the fault remaining undetected and unaddressed for an extended period, potentially leading to network service disruptions. Summary of the Invention

[0004] This application provides a fault handling method, electronic device, medium, and product.

[0005] This application provides a fault handling method, which includes:

[0006] In response to a silent failure occurring on the port of the network device in a packet to be transmitted, a silent failure notification message is generated based on the routing address information of the packet to be transmitted; the silent failure notification message includes a first source IP address and a first destination IP address, wherein the first source IP address is the destination IP address of the packet to be transmitted and the first destination IP address is the source IP address of the packet to be transmitted.

[0007] The silent fault notification message is sent to the upstream device of the current routing forwarding path of the packet to be transmitted by the current network device; the silent fault notification message is used to notify the target upstream device with routing protection capability for the packet to be transmitted to perform corresponding routing protection operation on the packet to be transmitted.

[0008] This application embodiment also provides a fault handling method, which includes:

[0009] The first silent fault notification message is sent by the next-hop device of the current routing forwarding path of the message to be transmitted. The first silent fault notification message includes a first source IP address and a first destination IP address. The first source IP address is the destination IP address of the message to be transmitted, and the first destination IP address is the source IP address of the message to be transmitted. The message to be transmitted is a message indicating that a silent fault has occurred at the port of the target downstream device in the routing forwarding path.

[0010] Determine whether the current network device has the routing protection capability for the packet to be transmitted based on the first source IP address;

[0011] In response to the fact that the current network device has the routing protection capability, the corresponding routing protection operation is performed on the message to be transmitted.

[0012] This application also provides an electronic device, including: one or more processors; and a memory storing one or more computer programs thereon, wherein when the one or more computer programs are executed by the one or more processors, the one or more processors implement any of the fault handling methods in this application.

[0013] This application also provides a computer-readable medium, wherein the computer-readable medium stores a computer program, which, when executed by a processor, implements any of the fault handling methods in this application.

[0014] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements any of the fault handling methods in this application.

[0015] According to the fault handling method, electronic device, medium, and product provided in the embodiments of this application, network devices can quickly respond to silent faults that occur at ports, and notify the target upstream device with routing protection capability for the packets to be transmitted to perform routing protection operations for the packets to be transmitted by constructing a silent fault notification message. This can effectively improve the reliability, stability, and maintainability of the network, improve the response efficiency and processing efficiency of network faults, improve network service anomalies, and enhance the user's experience with the network.

[0016] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0017] In the accompanying drawings of the embodiments of this application:

[0018] Figure 1 This diagram illustrates a fault handling method provided in an embodiment of this application.

[0019] Figure 2 The flowchart illustrates a specific implementation of step S12 in an embodiment of this application.

[0020] Figure 3 This is a flowchart illustrating a specific implementation of step S11 in an embodiment of this application.

[0021] Figure 4 This diagram illustrates an application scenario of a fault handling method provided in an embodiment of this application.

[0022] Figure 5 This diagram illustrates a flowchart of another fault handling method provided in an embodiment of this application.

[0023] Figure 6 This diagram illustrates an application scenario of another fault handling method provided in an embodiment of this application.

[0024] Figure 7 This diagram illustrates an application scenario of another fault handling method provided in an embodiment of this application.

[0025] Figure 8 This illustration shows a network scenario diagram of a network device provided in an embodiment of this application.

[0026] Figure 9 This is a block diagram illustrating the composition of an electronic device provided in an embodiment of this application. Detailed Implementation

[0027] To enable those skilled in the art to better understand the technical solutions of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0028] The present application will be described more fully below with reference to the accompanying drawings; however, the embodiments shown may be embodied in different forms, and the present application should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that this application will be thorough and complete, and will enable those skilled in the art to fully understand the scope of the application.

[0029] The accompanying drawings of the embodiments of this application are used to provide a further understanding of the embodiments of this application and constitute a part of the specification. They are used together with the detailed embodiments to explain this application and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the description of the detailed embodiments with reference to the accompanying drawings.

[0030] This application can be described with reference to plan views and / or cross-sectional views using the ideal schematic diagram of this application. Therefore, the example illustrations can be modified according to manufacturing techniques and / or tolerances.

[0031] Where there is no conflict, the various embodiments of this application and the features thereof may be combined with each other.

[0032] The terminology used in this application is for describing specific embodiments only and is not intended to limit the application. The term "and / or" as used herein includes any and all combinations of one or more of the associated enumerated entries. The singular forms "a" and "the" as used herein are also intended to include the plural forms unless the context clearly indicates otherwise. The terms "comprising," "made of," etc., as used herein, specify the presence of the stated feature, integral, step, operation, element, and / or component, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0033] Unless otherwise specified, all terms used in this application (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this application, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in this application.

[0034] In related technologies, IP network fault detection is generally triggered by port anomalies on network devices. This triggering can directly initiate fault protection scenarios such as changes to the outgoing (egress) port of a route (FRR) or ECMP (Equal-Cost Multipath Routing). A common effect of these faults is a relatively obvious fault response, and fault response processing and route protection can only be triggered if the faulty network device has routing protection capabilities (such as FRR, ECMP, or routing convergence triggered by routing protocols). However, in some fault scenarios, a device may experience an abnormal fault, but this will not trigger port anomalies, nor will it trigger fault response processing and route protection (such as FRR or ECMP), nor will it trigger route convergence. Furthermore, if the faulty network device lacks routing protection capabilities (such as FRR or ECMP), it cannot promptly trigger fault response processing and route protection. This can result in the fault remaining undetected and unprocessed for an extended period, potentially leading to network service anomalies.

[0035] This application provides a fault handling method, electronic device, medium, and product, which aim to effectively improve the technical problems existing in the above-mentioned related technologies.

[0036] Please see Figure 1 , Figure 1This illustration shows a flowchart of a fault handling method provided in an embodiment of this application. This embodiment provides a fault handling method that can be applied to network devices, such as routers or switches. Figure 1 As shown, the fault handling method in the embodiments of this application includes, but is not limited to, steps S11 and S12.

[0037] Step S11: In response to a silent fault occurring on the port of the network device in the message to be transmitted, a silent fault notification message is generated based on the routing address information of the message to be transmitted. The silent fault notification message includes a first source IP address and a first destination IP address, where the first source IP address is the destination IP address of the message to be transmitted and the first destination IP address is the source IP address of the message to be transmitted.

[0038] In some embodiments, the current network device refers to the network device to which the packet to be transmitted is currently being transmitted on the current routing path of the packet to be transmitted. The port of the current network device can be a first port of the current network device used to receive the packet to be transmitted from the previous hop network device on the current routing path, i.e., the ingress port or the receive port of the packet to be transmitted on the current network device; the port of the current network device can also be a second port of the current network device used to forward the packet to be transmitted to the next hop network device on the current routing path, i.e., the egress port or the send port of the packet to be transmitted on the current network device.

[0039] In this application embodiment, a silent fault refers to a fault that the port fails to detect and respond to, including but not limited to packet loss or hardware failure, which cannot be detected by the port or immediately detected by the router. Packet loss includes, for example, ACL (Access Control List) packet loss, QoS (Quality of Service) packet loss, bandwidth packet loss, forwarding anomaly packet loss, and network congestion packet loss. Hardware failures include, for example, unstable hardware voltage, unstable hardware current, and abnormal processor (CPU) operation. This application embodiment does not impose special limitations on the type of silent fault; any fault that the port fails to detect and respond to falls within the protection scope of this application embodiment.

[0040] In this embodiment, different silent fault identification configurations can be pre-configured for network devices based on the different types of silent faults, enabling the network devices to identify silent faults occurring at ports or within the device itself during operation. For example, for packet loss, a packet loss queue can be pre-configured on the network device's port to detect and identify packet loss of packets to be transmitted; for hardware faults, corresponding hardware sensors can be pre-configured in the network device to detect and identify hardware faults such as voltage instability and current instability. This embodiment does not impose special limitations on the silent fault identification method; other suitable technical means can also be used for silent fault detection and identification.

[0041] In this embodiment of the application, in step S11, in response to the detection that a silent fault (e.g., packet loss) has occurred on the port of the current network device in the packet to be transmitted, the routing address information of the packet to be transmitted is obtained from the packet to be transmitted. The routing address information includes the source IP (Session Initiation Protocol, SIP) address and the destination IP (Destination Internet Protocol, DIP) address of the packet to be transmitted. A silent fault notification message is constructed based on the source IP address and destination IP address of the packet to be transmitted in the routing address information. The silent fault notification message includes a first source IP address and a first destination IP address. The first source IP address is the destination IP address of the packet to be transmitted, and the first destination IP address is the source IP address of the packet to be transmitted. That is, the source IP address of the silent fault notification message is the destination IP address of the packet to be transmitted, and the destination IP address of the silent fault notification message is the source IP address of the packet to be transmitted. For example, if the source IP address of the message to be transmitted is 10.10.10.1 and the destination IP address of the message to be transmitted is 20.20.20.1, then the first source IP address of the constructed silent fault notification message is 20.20.20.1 and the first destination IP address is 10.10.10.1.

[0042] In some embodiments, if the port of the current network device is the first port mentioned above, or if the current network device does not have the routing protection capability for the message to be transmitted, then in step S11 above, in response to the silent fault occurring in the first port of the current network device, a silent fault notification message is generated based on the routing address information of the message to be transmitted.

[0043] In some embodiments, if the port of the current network device is the second port mentioned above, then in step S11 above, in response to the silent fault occurring on the second port of the current network device and the second port not having the routing protection capability for the message to be transmitted, a silent fault notification message is generated based on the routing address information of the message to be transmitted.

[0044] Step S12: Send a silent fault notification message to the upstream device of the current routing forwarding path of the packet to be transmitted by the current network device; the silent fault notification message is used to notify the target upstream device with routing protection capability for the packet to be transmitted to perform the corresponding routing protection operation for the packet to be transmitted.

[0045] In this embodiment of the application, the upstream device of the current network device in the current routing forwarding path of the message to be transmitted refers to the network device upstream of the current network device in the current routing forwarding path of the message to be transmitted, that is, the network device that forwards the message to be transmitted to the current network device in the current routing forwarding path of the message to be transmitted.

[0046] In this embodiment, a silent fault notification message is constructed, and the first source IP address of the silent fault notification message is set as the destination IP address of the message to be transmitted, and the first destination IP address is set as the source IP address of the message to be transmitted. The silent fault notification message is then propagated hop-by-hop to the upstream devices on the current routing forwarding path of the message to be transmitted by the current network device until it reaches the target upstream device with routing protection capability for the message to be transmitted, so that the target upstream device with routing protection capability can perform the corresponding routing protection operation on the message to be transmitted.

[0047] For each upstream network device of the current network device, after receiving the silent fault notification message, each upstream network device determines whether it has the routing protection capability for the message to be transmitted. If it determines that it has the routing protection capability for the message to be transmitted, the network device becomes the target upstream device. If it determines that it does not have the routing protection capability for the message to be transmitted, the network device continues to send silent fault notification messages to the previous hop device of the current routing forwarding path until it reaches the target upstream device with the routing protection capability for the message to be transmitted.

[0048] In this embodiment, the target upstream device refers to a network device located upstream of the current network device on the current routing forwarding path of the packet to be transmitted and possessing routing protection capabilities for the packet to be transmitted. After receiving a silent fault notification message, the target upstream device performs corresponding routing protection operations on the packet to be transmitted based on the silent fault notification message. Different routing protection capabilities correspond to different routing protection operations; this embodiment does not impose any special restrictions on the type of routing protection capability.

[0049] According to the fault handling method provided in this application embodiment, in response to recognizing a silent fault in the port of the packet to be transmitted, the network device constructs a silent fault notification message, setting the first source IP address of the silent fault notification message to the destination IP address of the packet to be transmitted and the first destination IP address to the source IP address of the packet to be transmitted. This silent fault notification message is then propagated hop-by-hop to upstream devices along the current routing path of the packet to be transmitted, until it reaches a target upstream device with routing protection capabilities for the packet to be transmitted. The target upstream device then performs corresponding routing protection operations on the packet to be transmitted. This allows the network device to quickly respond to silent faults in its port and, by constructing a silent fault notification message, notify the target upstream device with routing protection capabilities for the packet to be transmitted to perform routing protection operations. This effectively improves network reliability, stability, and maintainability, enhances network fault response and processing efficiency, mitigates network service anomalies, and improves the user experience.

[0050] Figure 2 This diagram illustrates a specific implementation of step S12 in an embodiment of this application. In some embodiments, such as... Figure 2 As shown, in step S12 above, sending a silent fault notification message to the upstream device of the current network device on the current routing forwarding path of the packet to be transmitted may further include:

[0051] Step S21: Based on the source IP address of the message to be transmitted, find the forwarding port information of the message to be transmitted in the previous hop device from the routing table of the current network device.

[0052] In some embodiments, the routing table of the current network device is searched by the source IP address of the message to be transmitted, the routing prefix of the corresponding route is found in the routing table according to the longest prefix matching principle, and the forwarding port information of the message to be transmitted in the previous hop device is found based on the corresponding routing prefix, that is, the outgoing port information of the message to be transmitted in the previous hop device.

[0053] For example, if the source IP (SIP) address of the message to be transmitted is 10.10.10.1, the routing table of the current network device is looked up using the source IP address of the message to be transmitted. The corresponding route and route prefix are found to be 10.10.10.0 / 24. The forwarding port information of the message to be transmitted on the previous hop device is found to be port A1.

[0054] Step S22: Based on the forwarding port information, send a silent fault notification message to the upstream device.

[0055] In some embodiments, after determining the forwarding port information of the message to be transmitted in the previous hop device, the constructed silent fault notification message is sent from the port corresponding to the forwarding port information of the current network device to the port corresponding to the forwarding port information of the previous hop device, so as to send the silent fault notification message to the previous hop device.

[0056] For example, if the port corresponding to the forwarding port information of the message to be transmitted in the previous hop device is port A1, then the constructed silent fault notification message will be sent from port A1 of the current network device to port A1 of the previous hop device.

[0057] Figure 3 This diagram illustrates a specific implementation of step S11 in an embodiment of this application. In some embodiments, such as... Figure 3 As shown, in step S11 above, generating a silent fault notification message based on the routing address information of the message to be transmitted may further include:

[0058] Step S31: Obtain the routing address information of the message to be transmitted from the message header information. The routing address information includes the source IP address and destination IP address of the message to be transmitted.

[0059] Step S32: Construct a silent fault notification message based on the source IP address, destination IP address, and silent fault identification information of the message to be transmitted; the silent fault identification information is used to identify the occurrence of a silent fault.

[0060] In some embodiments, the source IP address of the message to be transmitted (e.g., 10.10.10.1) is set as the first destination IP address of the silent fault notification message, and the destination IP address of the message to be transmitted (e.g., 20.20.20.1) is set as the first source IP address of the silent fault notification message. The silent fault notification message is constructed by encapsulating the first source IP address, the first destination IP address and the silent fault identification information. The silent fault notification message includes the first source IP address, the first destination IP address and the silent fault identification information.

[0061] In some embodiments, a preset field is used as silent fault identification information in the silent fault notification message to indicate that a port of the current network device has experienced a silent fault. For example, the preset field is the TCP (Transmission Control Protocol) / UDP (User Datagram Protocol) port field in the message. In some embodiments, a silent fault can also be identified by message coloring, with the message coloring information serving as the silent fault identification information. This application does not impose special limitations on the specific implementation of the silent fault identification information in the silent fault notification message; other suitable methods can also be used to carry information identifying silent faults in the message.

[0062] It should be noted that the identification and recognition methods of silent fault identification information can be pre-configured in each network device. This allows each network device to configure silent fault identification information using the pre-configured identification method when constructing a silent fault notification message, and to identify the silent fault identified by the silent fault identification information using the pre-configured recognition method when receiving a silent fault notification message and needing to identify the silent fault identification information.

[0063] In some embodiments, before generating a silent fault notification message based on the routing address information of the message to be transmitted in response to a silent fault occurring at the port of the current network device, i.e. before step S11 above, the fault handling method further includes: determining whether the message to be transmitted has been lost through the packet loss queue of the port of the current network device; and determining that a silent fault has occurred at the port of the current network device in response to determining that the message to be transmitted has been lost.

[0064] In some embodiments, after determining that a silent failure has occurred on the port of the current network device, the header information of the packet to be transmitted in the packet loss queue is identified by a preset identification method. The header information of the packet to be transmitted includes, but is not limited to, the source MAC (Media Access Control Address), destination MAC address, source IP address, and destination IP address. The preset identification method includes, but is not limited to, ACL packet capture, packet loss queue sampling, and packet loss queue mirroring.

[0065] In some embodiments, if the port of the current network device that experiences a silent failure is the first port mentioned above, then in step S11, in response to the silent failure of the message to be transmitted on the first port of the current network device, a silent failure notification message is generated based on the routing address information of the message to be transmitted.

[0066] In some embodiments, the port where the current network device experiences a silent fault is the second port mentioned above. In step S11, before generating a silent fault notification message based on the routing address information of the message to be transmitted, the routing fault handling method further includes: determining whether the current network device has routing protection capability for the message to be transmitted based on the destination IP address of the message to be transmitted; and performing corresponding routing protection operations on the message to be transmitted in response to determining that the current network device has routing protection capability for the message to be transmitted.

[0067] In some embodiments, the routing protection capability includes Fast Rerouting (FRR) and / or Equal Cost Route (ECMP) routing protection capabilities. In response to determining that the current network device has the routing protection capability for the packet to be transmitted, the corresponding routing protection operation is performed on the packet to be transmitted, including: in response to determining that the current network device has the routing protection capability of Fast Rerouting (FRR), performing a routing protection operation of switching the routing forwarding path of the packet to be transmitted through Fast Rerouting (FRR); or, in response to determining that the current network device has the routing protection capability of Equal Cost Route (ECMP), performing a routing protection operation of invalidating the next-hop route of the packet to be transmitted in the current network device through Equal Cost Route (ECMP).

[0068] In some embodiments, the step of determining whether the current network device has the routing protection capability for the packet to be transmitted based on the destination IP address of the packet to be transmitted may further include: looking up the routing table of the current network device based on the destination IP address of the packet to be transmitted; and determining whether the current network device has the routing protection capability for the packet to be transmitted based on the route corresponding to the destination IP address of the packet to be transmitted found.

[0069] For example, based on the route (e.g., 20.20.20.0 / 24) corresponding to the destination IP address (e.g., 20.20.20.1) of the message to be transmitted, if the forwarding port (outgoing port) of the route is determined to be an FRR group, pointing to forwarding port A1 and forwarding port A2, then it is determined that the current network device has the route protection capability of Fast Rerouting (FRR). In this case, forwarding port A1 is the second port that has experienced a silent fault.

[0070] In some embodiments, in response to determining that the current network device has the routing protection capability of Fast Rerouting (FRR), the step of performing a routing protection operation to switch the routing forwarding path of the packet to be transmitted through Fast Rerouting (FRR) may further include: switching the forwarding port of the packet to be transmitted in the current network device from the second port (such as forwarding port A1) to another forwarding port (such as forwarding port A2) pointed to by FRR through Fast Rerouting (FRR), thereby realizing the routing forwarding path switching.

[0071] For example, if the route (e.g., 20.20.20.0 / 24) corresponding to the destination IP address (e.g., 20.20.20.1) of the message to be transmitted is determined to be an ECMP group, then the current network device is determined to have the route protection capability of Equal Cost Route (ECMP).

[0072] In some embodiments, in response to determining that the current network device has the routing protection capability of Equal Cost Route (ECMP), the step of performing a routing protection operation to disable the next-hop route of the packet to be transmitted in the current network device through Equal Cost Route (ECMP) may further include: cutting off the forwarding port in the ECMP group that has a silent failure, or deleting the forwarding port in the ECMP group that has a silent failure, so as to disable the next-hop route of the current network device.

[0073] In some embodiments, in step S11 above, in response to a silent fault occurring on the second port of the current network device and it being determined that the current network device does not have the routing protection capability for the message to be transmitted, the step of generating a silent fault notification message based on the routing address information of the message to be transmitted is performed.

[0074] In this embodiment, the above-described fault handling method can be applied to a current network device that experiences a silent fault. The current network device can be a switch or a router, and can be used to perform routing protection when the current network device experiences a silent fault in an IP network or other tunnel network.

[0075] Figure 4 This illustration shows an application scenario diagram of a fault handling method provided in an embodiment of this application, such as... Figure 4As shown, in some application scenarios, a silent failure occurs on the port of the current network device. In response to recognizing this silent failure on the port of the packet to be transmitted, the current network device analyzes the packet header information to obtain the source IP (SIP) address (10.10.10.1) and destination IP (DIP) address (20.20.20.1). Then, the current network device searches its local routing table using the source IP (SIP) address (10.10.10.1) to find the corresponding subnet route (10.10.10.0 / 24) and determines the destination IP address. The forwarding port (egress port) of the transmission message on the previous hop device is forwarding port A1. A silent fault notification message is constructed based on the source IP (SIP) address of the message to be transmitted: 10.10.10.1 and the destination IP (DIP) address: 20.20.20.1. The source IP (SIP) address of the silent fault notification message is configured to be the destination IP address of the message to be transmitted: 20.20.20.1, and the destination IP (DIP) address of the silent fault notification message is configured to be the source IP address of the message to be transmitted: 10.10.10.1. The message is then sent to the previous hop device through the found forwarding port A1.

[0076] Please see Figure 5 , Figure 5 This illustration shows a flowchart of another fault handling method provided in an embodiment of this application. This application provides a fault handling method that can be applied to network devices, such as routers or switches. Figure 5 As shown, the fault handling method in the embodiments of this application includes, but is not limited to, steps S51 to S53.

[0077] Step S51: Receive a first silent fault notification message sent by the current network device to the next-hop device in the current routing forwarding path of the packet to be transmitted. The first silent fault notification message includes a first source IP address and a first destination IP address. The first source IP address is the destination IP address of the packet to be transmitted, and the first destination IP address is the source IP address of the packet to be transmitted. The packet to be transmitted is a message indicating that a silent fault has occurred on the port of the target downstream device in the routing forwarding path.

[0078] In some embodiments, the current network device refers to the network device that currently receives the silent fault notification message. The next-hop device of the current network device in the current routing forwarding path of the message to be transmitted is the next network device downstream of the current network device in the current routing forwarding path of the message to be transmitted. In other words, it is the network device that receives the message to be transmitted forwarded by the current network device in the current routing forwarding path of the message to be transmitted.

[0079] It is understandable that, for the current network device, the next-hop device is the downstream device of the current network device; and for the next-hop device, the current network device is the upstream device of the next-hop device.

[0080] In this embodiment, the target downstream device refers to a network device located downstream of the current network device on the current routing path of the packet to be transmitted and whose port has a silent fault. Based on the fault handling method of the aforementioned embodiment, in response to recognizing that the packet to be transmitted has a silent fault on the port of the target downstream device, the target downstream device constructs a silent fault notification message, sets the first source IP address of the silent fault notification message to the destination IP address of the packet to be transmitted, sets the first destination IP address to the source IP address of the packet to be transmitted, and propagates the silent fault notification message hop-by-hop to the upstream device of the target downstream device on the current routing path of the packet to be transmitted.

[0081] It is understandable that the current network device can be any upstream network device on the current routing path of the target downstream device whose port has a silent failure, and the next-hop device of the current network device can be the target downstream device, or it can be a network device on the current routing path that is between the current network device and the target downstream device and is the next hop of the current network device.

[0082] In some embodiments, after receiving a first silent fault notification message sent by the next-hop device of the current network device, the first source IP address and the first destination IP address are obtained from the header information of the first silent fault notification message.

[0083] Step S52: Determine whether the current network device has the routing protection capability for the packet to be transmitted based on the first source IP address.

[0084] In some embodiments, the first silent fault notification message may further include silent fault identification information, which is used to identify that a port of the target downstream device has a silent fault. Based on the silent fault identification information, it can be identified that a port of the target downstream device has a silent fault on the current routing forwarding path of the message to be transmitted.

[0085] In some embodiments, after receiving a first silent fault notification message sent by the next-hop device of the current network device, in response to identifying a silent fault on the current routing path of the packet to be transmitted based on the silent fault identification information, the current network device determines whether it has the routing protection capability for the packet to be transmitted based on the first source IP address, which is also the destination IP address of the packet to be transmitted.

[0086] Step S53: In response to the fact that the current network device has routing protection capabilities, perform the corresponding routing protection operation on the packet to be transmitted.

[0087] In the embodiments of this application, different routing protection capabilities correspond to different routing protection operations. The embodiments of this application do not impose special restrictions on the type of routing protection capability.

[0088] In some embodiments, the routing protection capability includes the routing protection capability of Fast Rerouting (FRR) and / or Equal Cost Route (ECMP). The routing protection operation corresponding to the routing protection capability of Fast Rerouting (FRR) includes the operation of switching the route forwarding path, and the routing protection operation corresponding to the routing protection capability of Equal Cost Route (ECMP) includes the operation of failing the next-hop route.

[0089] According to the fault handling method provided in the embodiments of this application, after receiving a first silent fault notification message sent by a downstream device, the network device determines whether it has the routing protection capability for the message to be transmitted. In response to the network device having the routing protection capability, it performs the corresponding routing protection operation on the message to be transmitted. In this way, the network device can quickly respond to silent faults that occur on the routing forwarding path and perform routing protection operation on the message to be transmitted when the network device has the routing protection capability. This can effectively improve the reliability, stability and maintainability of the network, improve the response efficiency and processing efficiency of network faults, improve network service anomaly issues, and enhance the user's experience with the network.

[0090] In some embodiments, after determining whether the current network device has the routing protection capability for the packet to be transmitted based on the first source IP address, the fault handling method further includes: in response to the current network device not having the routing protection capability, regenerating a second silent fault notification message based on the first source IP address, the first destination IP address, and silent fault identification information, wherein the silent fault identification information is used to identify the occurrence of a silent fault; and sending the second silent fault notification message to the hop device above the current routing forwarding path of the packet to be transmitted by the current network device.

[0091] In some embodiments, the upstream device of the current network device in the current routing forwarding path of the packet to be transmitted refers to the preceding network device that is upstream of the current network device in the current routing forwarding path of the packet to be transmitted, that is, the network device that forwards the packet to be transmitted to the current network device in the current routing forwarding path of the packet to be transmitted.

[0092] In some embodiments, the source IP address and destination IP address of the first silent fault notification message are reused as the source IP address and destination IP address of the second silent fault notification message, and silent fault identification information is marked by preset fields or message coloring. For a description of the generation method of the second silent fault notification message, please refer to the description of the silent fault notification message in the foregoing embodiments, which will not be repeated here.

[0093] Understandably, since the message also needs to carry the MAC address of the network device, and different network devices have different MAC addresses, the current network device needs to reconstruct the second silent fault notification message and send it to the upstream network device if it determines that it does not have routing protection capabilities.

[0094] In some embodiments, the network device, through the aforementioned response and processing methods for silent fault notification messages, enables the downstream device to transmit silent fault notification messages hop-by-hop to upstream network devices when a silent fault occurs at any port of the target downstream device. Upon receiving a silent fault notification message, any upstream network device of the target downstream device determines whether it possesses routing protection capabilities. If the silent fault is detected in the routing path of the packet to be transmitted and the device possesses routing protection capabilities, it triggers the execution of corresponding routing protection operations on the packet to be transmitted. If the silent fault is detected in the routing path of the packet to be transmitted but the device lacks routing protection capabilities, it continues to transmit silent fault notification messages to upstream network devices. This allows silent faults that are not perceptible to ports on the routing path to be transmitted to be quickly transmitted into the network, and routing protection operations are rapidly triggered on network devices with routing protection capabilities. This effectively shortens the impact time of silent faults on network services, improves network fault response and processing efficiency, and mitigates network service anomalies.

[0095] In some embodiments, sending a second silent fault notification message to the upstream device of the current network device on the current routing forwarding path of the packet to be transmitted includes: finding the forwarding port information of the packet to be transmitted on the upstream device from the routing table of the current network device based on the first destination IP address; and sending the second silent fault notification message to the upstream device according to the forwarding port information.

[0096] In some embodiments, the routing table of the current network device is searched using the first destination IP address, which is the source IP address of the message to be transmitted. The routing prefix of the corresponding route is found in the routing table according to the longest prefix matching principle. Based on the corresponding routing prefix, the forwarding port information of the message to be transmitted in the previous hop device is found, that is, the outgoing port information of the message to be transmitted in the previous hop device.

[0097] For example, if the first destination IP address, which is the source IP (SIP) address of the packet to be transmitted, is 10.10.10.1, the routing table of the current network device is searched using the first destination IP address. The corresponding route and route prefix are found to be 10.10.10.0 / 24. The forwarding port information of the packet to be transmitted on the previous hop device is found to be port A3.

[0098] In some embodiments, after determining the forwarding port information of the message to be transmitted in the previous hop device, the constructed second silent fault notification message is sent from the port corresponding to the forwarding port information of the current network device to the port corresponding to the forwarding port information of the previous hop device, so as to send the second silent fault notification message to the previous hop device.

[0099] For example, if the port corresponding to the forwarding port information of the message to be transmitted in the previous hop device is port A3, then the constructed second silent fault notification message will be sent from port A3 of the current network device to port A3 of the previous hop device.

[0100] In some embodiments, determining whether the current network device has the capability to protect the packet to be transmitted based on the first source IP address includes: looking up the routing table of the current network device based on the first source IP address; and determining whether the current network device has the capability to protect the packet to be transmitted based on the route corresponding to the first source IP address found.

[0101] For example, if the first source IP address, i.e. the destination IP address of the packet to be transmitted, is 20.20.20.1, by looking up the routing table of the current network device, the route corresponding to the first source IP address is found to be 20.20.20.0 / 24. Based on this route, the forwarding port (outgoing port) of this route is determined to be the FRR group, pointing to forwarding port A1 and forwarding port A2. Then it is determined that the current network device has the routing protection capability of Fast Rerouting (FRR). Here, forwarding port A1 is the port on the current route forwarding path where the current network device sends the packet to be transmitted to the next hop device.

[0102] For example, if the first source IP address, i.e. the destination IP address of the packet to be transmitted, is 20.20.20.1, by looking up the routing table of the current network device, the route corresponding to the first source IP address is found to be 20.20.20.0 / 24. Based on this route, it is determined that the forwarding port (outgoing port) of this route is an ECMP group, thus confirming that the current network device has the route protection capability of Equal Cost Route (ECMP).

[0103] For example, if the first source IP address, i.e. the destination IP address of the packet to be transmitted, is 20.20.20.1, by looking up the routing table of the current network device, the route corresponding to the first source IP address is found to be 20.20.20.0 / 24. Based on this route, the forwarding port (outgoing port) of this route is determined to be forwarding port A1. Forwarding port A1 is the port on the current route forwarding path where the current network device sends the packet to be transmitted to the next hop device. This indicates that the current network device does not have any other route forwarding path as a protection path for the packet to be transmitted. In this case, it is considered that the current network device does not have the route protection capability for the packet to be transmitted.

[0104] In some embodiments, the routing protection capability includes fast rerouting (FRR) routing protection capability and / or equal-cost routing (ECMP) routing protection capability; in response to the current network device having routing protection capability, the corresponding routing protection operation is performed on the packet to be transmitted, including: in response to the current network device having fast rerouting (FRR) routing protection capability, switching the routing forwarding path of the packet to be transmitted; or, in response to the current network device having equal-cost routing (ECMP) routing protection capability, invalidating the next-hop route of the packet to be transmitted in the current network device.

[0105] In some embodiments, in response to the current network device having the routing protection capability of Fast Rerouting (FRR), the step of performing a routing protection operation to switch the routing forwarding path of the packet to be transmitted may further include: switching the forwarding port of the packet to be transmitted in the current network device from the current forwarding port of the packet to be transmitted (such as forwarding port A1) to another forwarding port (such as forwarding port A2) pointed to by FRR through Fast Rerouting (FRR).

[0106] In some embodiments, in response to the current network device having the routing protection capability of Equal Cost Route (ECMP), the step of performing a routing protection operation to switch the routing forwarding path of the packet to be transmitted may further include: cutting off the current forwarding port of the packet to be transmitted in the ECMP group, or deleting the current forwarding port of the packet to be transmitted in the ECMP group, so as to invalidate the next-hop route of the current network device.

[0107] In this embodiment of the application, the above-described fault handling method can be applied to any network device upstream of the target downstream device that has a silent fault on the current routing forwarding path. The network device can be a switch or a router, etc., and can be used to perform routing protection when a silent fault occurs in an IP network or other tunnel network.

[0108] Figure 6 This illustration shows an application scenario diagram of another fault handling method provided in an embodiment of this application, such as... Figure 6 As shown, in some application scenarios, the current network device receives the first silent fault notification message sent by the downstream network device, and the current network device has the routing protection capability for the message to be transmitted. In this scenario, the current network device's forwarding port A1 receives the first silent fault notification message from the downstream network device. Analyzing the message header information, the first destination IP (DIP) address is found to be 10.10.10.1, and the first source IP (SIP) address is 20.20.20.1. The current network device then searches its local routing table using the first source IP (SIP) address 20.20.20.1 and finds the corresponding subnet route 20.20.20.0 / 24. The corresponding forwarding port is an FRR group, pointing to the current network device's forwarding ports A1 and A2. Therefore, it is determined that the current network device has FRR route protection capability. In response to the current network device's FRR route protection capability, a route forwarding path switching operation is triggered for the packet to be transmitted, switching the FRR group of route 20.20.20.0 / 24 from forwarding port A1 to forwarding port A2.

[0109] It should be noted that if the forwarding port corresponding to the found subnet route 20.20.20.0 / 24 is an ECMP group, it is determined that the current network device has ECMP route protection capability. In response to the current network device having FRR route protection capability, the next-hop route of the packet to be transmitted is invalidated, either by cutting off the forwarding port A1 pointed to by the ECMP group or deleting the forwarding port A1 pointed to by the ECMP group.

[0110] Figure 7 This illustration shows an application scenario diagram of another fault handling method provided in an embodiment of this application, such as... Figure 7As shown, in some application scenarios, the current network device receives a first silent fault notification message from a downstream network device, and the current network device does not have the routing protection capability for the message to be transmitted. In this case, the forwarding port A1 of the current network device receives the first silent fault notification message from the downstream network device. Analyzing the message header information, the first destination IP (DIP) address of the message is found to be 10.10.10.1, and the first source IP (SIP) address is 20.20.20.1. The current network device looks up the local routing table using the first source IP (SIP) address: 20.20.20.1, and finds the corresponding subnet route: 20.20.20.0 / 24, whose corresponding forwarding port is forwarding port A1. This indicates that there is no other route transmission path as a route protection path. Therefore, in this case, it is considered that the current network device does not have the routing protection capability for the message to be transmitted. The system provides routing protection for transmitted packets. In response to the current network device lacking routing protection for the packet to be transmitted, it searches the local routing table on the current network device using the first destination IP (DIP) address: 10.10.10.1. The corresponding subnet route is found to be 10.10.10.0 / 24, and its corresponding forwarding port is forwarding port A3, which is also the forwarding port of the packet to be transmitted on the previous hop device. Based on the first destination IP (DIP) address: 10.10.10.1 and the first source IP (SIP) address: 20.20.20.1, a second silent fault notification message is constructed and sent to the previous hop device through forwarding port A3.

[0111] Figure 8 This illustration shows a network scenario diagram of a network device provided in an embodiment of this application, such as... Figure 8 As shown, in some network topology scenarios, the network includes network device 1, network device 2, network device 3, and network device 4. The current routing and forwarding path of the packet to be transmitted is as follows: Figure 8As shown, the current routing forwarding path is network device 1-network device 2-network device 4. Based on the fault handling method provided in this application embodiment, network device 2 detects a silent fault in forwarding port A1, and network device 2 itself does not have the routing protection capability for the packet to be transmitted. Network device 2 constructs a silent fault notification message and, following the silent fault notification message transmission path that is passed hop-by-hop to upstream network devices, first transmits the silent fault notification message to network device 1, which is upstream of network device 2 on the current routing forwarding path. Network device 1 determines that it has the routing protection capability of FRR based on the silent fault notification message, where FRR points to... Forwarding ports include forwarding ports A2 and A3. Forwarding port A2 is the forwarding port of network device 1 on the current route forwarding path of the packet to be transmitted. Since a silent fault occurs on the current route forwarding path of the packet to be transmitted, and network device 1 has FRR route protection capability, network device 1, in response to its own FRR route protection capability, switches the current forwarding port of the packet to be transmitted from A2 to A3 through FRR, thereby switching the route forwarding path of the packet to be transmitted so that the packet to be transmitted is transmitted according to the switched route forwarding path. The switched route forwarding path is network device 1-network device 3-network device 4.

[0112] It should be noted that, Figure 8 This application merely illustrates one networking scenario of its embodiment and does not limit the network networking scenarios of this application. The networking of network devices in this application includes, but is not limited to, the following: Figure 8 The network scenario shown.

[0113] In the embodiments of this application, the above-mentioned fault handling method can be deployed in the underlay (basic network) layer of IP network or other tunnel network to improve the network's protection against silent faults and the switching response speed.

[0114] It should be clarified that this application is not limited to the specific configurations and processes described in the above embodiments and shown in the figures. For the sake of convenience and brevity, detailed descriptions of known methods are omitted here and will not be repeated.

[0115] Figure 9 This is a block diagram illustrating the composition of an electronic device provided in an embodiment of this application.

[0116] like Figure 9 As shown, the electronic device includes: one or more processors 901 and a memory 902; the memory 902 stores one or more computer programs, which, when executed by one or more processors 901, enable one or more processors 901 to implement any of the fault handling methods described in the above embodiments.

[0117] In some embodiments, the electronic device further includes an I / O interface (read / write interface) 903, which is connected between the processor 901 and the memory 902 and enables information interaction between the memory 902 and the processor 901. The I / O interface 903 includes, but is not limited to, a data bus.

[0118] Among them, the processor is a device with data processing capabilities, including but not limited to the central processing unit (CPU); the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically such as SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH).

[0119] This application also provides a computer-readable medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements any of the fault handling methods described in the above embodiments.

[0120] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements any of the fault handling methods described in the above embodiments.

[0121] Those skilled in the art will understand that all or some of the steps, systems, and devices disclosed above, as functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0122] In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be executed by several physical components working together.

[0123] Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit (CPU), digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technique for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage; read-only optical disc (CD-ROM), digital versatile disc (DVD) or other optical disc storage; magnetic cartridges, magnetic tapes, disk storage or other magnetic storage; and any other media that can be used to store desired information and can be accessed by a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0124] This application has disclosed exemplary embodiments, and although specific terminology has been used, it is used and should be interpreted only in a general illustrative sense and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this application as set forth by the appended claims.

Claims

1. A fault handling method, comprising: In response to a silent failure occurring on the port of the network device for a message to be transmitted, a silent failure notification message is generated based on the routing address information of the message to be transmitted. The silent fault notification message includes a first source IP address and a first destination IP address, wherein the first source IP address is the destination IP address of the message to be transmitted, and the first destination IP address is the source IP address of the message to be transmitted. The silent fault notification message is sent to the upstream device of the current routing forwarding path of the packet to be transmitted by the current network device. The silent fault notification message is used to notify the target upstream device that has the routing protection capability for the message to be transmitted, and to perform the corresponding routing protection operation on the message to be transmitted.

2. The failure handling method according to claim 1, wherein Sending the silent fault notification message to the upstream device of the current routing forwarding path of the packet to be transmitted by the current network device includes: Based on the source IP address of the message to be transmitted, the forwarding port information of the message to be transmitted in the previous hop device is found in the routing table of the current network device. Based on the forwarding port information, the silent fault notification message is sent to the previous hop device.

3. The fault handling method according to claim 1, wherein, The step of generating a silent fault notification message based on the routing address information of the message to be transmitted includes: Obtain the routing address information of the message to be transmitted from the message header information of the message to be transmitted. The routing address information includes the source IP address and destination IP address of the message to be transmitted. Based on the source IP address, destination IP address, and silent fault identifier information of the message to be transmitted, the silent fault notification message is constructed; the silent fault identifier information is used to identify the occurrence of a silent fault.

4. The fault handling method according to claim 1, wherein, The silent fault is a fault in which the port fails to detect and respond.

5. The fault handling method according to claim 1, wherein, The fault handling method further includes: Whether the message to be transmitted has been lost is determined by the packet loss queue of the port of the current network device; In response to determining that the message to be transmitted has been lost, it is determined that the silent fault has occurred on the port of the current network device.

6. A fault handling method, comprising: Receive a first silent fault notification message sent by the current network device to the next-hop device in the current routing forwarding path of the packet to be transmitted. The first silent fault notification message includes a first source IP address and a first destination IP address. The first source IP address is the destination IP address of the packet to be transmitted, and the first destination IP address is the source IP address of the packet to be transmitted. The packet to be transmitted is a message indicating that a silent fault has occurred at the port of the target downstream device in the routing forwarding path. Determine whether the current network device has the routing protection capability for the packet to be transmitted based on the first source IP address; In response to the fact that the current network device has the routing protection capability, the corresponding routing protection operation is performed on the message to be transmitted.

7. The fault handling method according to claim 6, wherein, After determining whether the current network device has the routing protection capability for the packet to be transmitted based on the first source IP address, the fault handling method further includes: In response to the fact that the current network device does not have the routing protection capability, a second silent fault notification message is regenerated based on the first source IP address, the first destination IP address and silent fault identification information, wherein the silent fault identification information is used to identify the occurrence of silent fault; The second silent fault notification message is sent to the upstream device of the current routing forwarding path of the message to be transmitted by the current network device.

8. The fault handling method according to claim 7, wherein, Sending the second silent fault notification message to the upstream device of the current routing forwarding path of the packet to be transmitted by the current network device includes: Based on the first destination IP address, the forwarding port information of the packet to be transmitted in the previous hop device is found from the routing table of the current network device. Based on the forwarding port information, the second silent fault notification message is sent to the upstream device.

9. The fault handling method according to claim 6, wherein, The step of determining whether the current network device has the routing protection capability for the packet to be transmitted based on the first source IP address includes: The routing table of the current network device is searched based on the first source IP address; Based on the route corresponding to the first source IP address found, determine whether the current network device has the route protection capability for the packet to be transmitted.

10. The fault handling method according to any one of claims 6-9, wherein, The routing protection capability includes fast rerouting and / or equal-cost routing protection. In response to the current network device possessing the routing protection capability, the corresponding routing protection operation is performed on the packet to be transmitted, including: In response to the current network device possessing the routing protection capability of fast rerouting, a switching operation is performed on the routing forwarding path of the packet to be transmitted; or, In response to the fact that the current network device has the routing protection capability of the equivalent route, the next-hop route of the message to be transmitted is invalidated in the current network device.

11. An electronic device, wherein, include: One or more processors; A memory having stored one or more computer programs thereon, which, when executed by the one or more processors, cause the one or more processors to implement the fault handling method as described in any one of claims 1 to 10.

12. A computer-readable medium, wherein, The computer-readable medium stores a computer program that, when executed by a processor, implements the fault handling method as described in any one of claims 1 to 10.

13. A computer program product comprising a computer program that, when executed by a processor, implements the fault handling method as described in any one of claims 1 to 10.

Images