Network fault notification method and device, network equipment and readable storage medium

Abstract

The invention relates to the technical field of communication, and provides a network fault notification method and device, network equipment and a readable storage medium, which are applied to the network equipment, the network equipment is directly connected with at least one direct connection network equipment, and the network equipment is provided with a link type of a direct connection link between the network equipment and each direct connection network equipment. The link type comprises an uplink link and a downlink link. The method comprises the following steps: acquiring a fault notification message; determining a forwarding link from all the direct links, wherein the forwarding link comprises at most one uplink link; and sending the fault notification message through each link in the forwarding links. According to the invention, rapid sensing of link faults can be realized.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a network fault notification method, device, network equipment and readable storage medium. Background Art

[0002] With the rapid development of AI (Artificial Intelligence) technology, intelligent computing center networks have gradually become a hot research topic in the industry. AI training is extremely sensitive to network failures due to its characteristics of distributed computing, long-term operation, and real-time response. Since intelligent computing networks usually use a large number of vulnerable components such as optical modules, network failures are inevitable during AI training. At present, the industry attaches great importance to improving the fault convergence speed in the intelligent computing center network and reducing the impact of network failures on AI training tasks.

[0003] Fault recovery in traditional technologies mainly relies on the control plane of network devices. When a network device senses a link or node failure, it sends a protocol message to its neighbors through routing protocols (BGP (Border Gateway Protocol) / OSPF (Open Shortest Path First) / ISIS (Intermediate System to Intermediate System)) to notify the withdrawal of the route; the service can only be restored after the neighboring device receives the protocol message and updates the local routing table. The convergence time in a typical scenario is in seconds, and the service packet loss time is too long.

[0004] In order to solve the problem of long service packet loss caused by slow convergence of routing protocols, the industry has begun to propose fault recovery technology based on the forwarding plane. The main idea is to combine fault notification with remote fault switching. Regarding fault notification, an existing solution is to use the whole network flooding method to perform fault notification. Its disadvantages are: fault notification message forwarding loop, many repeated notifications, low efficiency, and fault notification message wastes network bandwidth. Summary of the invention

[0005] The object of the present invention is to provide a network fault notification method, device, network equipment and readable storage medium, which can enable all network devices affected by the fault to quickly perceive the fault without changing the hardware.

[0006] The embodiments of the present invention can be implemented as follows:

[0007] In a first aspect, the present invention provides a network fault notification method, which is applied to a network device, wherein the network device is directly connected to at least one directly connected network device, and the network device is provided with a link type of a direct link between the network device and each directly connected network device, wherein the link type includes an uplink link and a downlink link, and the method includes:

[0008] Obtain fault notification message;

[0009] Determine a forwarding link from all the directly connected links, wherein the forwarding link includes at most one uplink;

[0010] The fault notification message is sent through each link in the forwarding link.

[0011] In an optional implementation manner, the step of determining a forwarding link from all the directly connected links includes:

[0012] If there is at least one downlink link among all the directly connected links, each of the downlink links is used as a link in the forwarding link;

[0013] If there is at least one uplink link among all the directly connected links, the forwarding link is determined according to the fault notification message.

[0014] In an optional implementation manner, the step of determining the forwarding link according to the fault notification message includes:

[0015] If the fault notification message is generated by the network device when detecting a fault in the link between the network device and any of the directly connected network devices or the fault notification message is received by the network device through at least one of the downlink links, an uplink link is determined from the at least one uplink as a link in the forwarding link.

[0016] In an optional implementation manner, the step of obtaining the fault notification message includes:

[0017] When a traffic message is received, the next-hop link used to forward the traffic message is determined, and the status of the next-hop link is obtained. If the status of the next-hop link is a faulty state, a notification message is generated, and the preset field in the notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain the fault notification message.

[0018] In an optional implementation manner, the step of obtaining the fault notification message includes:

[0019] When a fault is detected in a link between any of the directly connected network devices, a notification message is generated, a preset field in the generated notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain the fault notification message.

[0020] In an optional implementation manner, when a failure in a link between any of the directly connected network devices is detected, before the step of generating a notification message, the step includes:

[0021] For any of the directly connected network devices, if it is detected that the optical module status of the directly connected network device is abnormal, or the device port status of the directly connected network device is disconnected, or the bidirectional forwarding detection BFD session between the directly connected network device is disconnected, it is determined that the link between the network device and the directly connected network device is faulty.

[0022] In an optional implementation manner, the step of obtaining the fault notification message includes:

[0023] Receive notification messages sent by other network devices;

[0024] If the notification message contains a preset field and the preset field is a preset value, the notification message is used as the fault notification message.

[0025] In a second aspect, the present invention provides a network fault notification device, which is applied to a network device, wherein the network device is directly connected to at least one directly connected network device, and the network device is provided with a link type of a direct link between the network device and each directly connected network device, wherein the link type includes an uplink link and a downlink link, and the device includes:

[0026] An acquisition module is used to acquire fault notification messages;

[0027] A determination module, configured to determine a forwarding link from all the directly connected links, wherein the forwarding link includes at most one uplink;

[0028] A sending module is used to send the fault notification message through each link in the forwarding link.

[0029] In a third aspect, the present invention provides a network device, including a processor and a memory, wherein the memory is used to store a program, and the processor is used to implement the network fault notification method described in any one of the aforementioned implementation modes when executing the program.

[0030] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the network fault notification method described in any one of the aforementioned embodiments is implemented.

[0031] Compared with the prior art, the present invention has the following beneficial effects: when forwarding a fault notification message, the fault notification message is forwarded on the forwarding plane through at most one uplink, thereby avoiding the use of protocol notification routing update to perform fault notification on the control plane, thereby improving the efficiency of fault notification, allowing all devices affected by the fault to quickly perceive the fault, and effectively avoiding the waste of network bandwidth caused by loop forwarding or multiple repeated forwarding of the fault notification message in the network, and at the same time does not involve hardware improvements, reducing the difficulty of implementation. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0033] Figure 1 This is an example diagram of the Fat-Tree network provided in this embodiment.

[0034] Figure 2 The embodiment provided Figure 1 An example diagram of a traffic forwarding path affected by a link failure in the prior art.

[0035] Figure 3 This is a block diagram of an example network device provided in this embodiment.

[0036] Figure 4 This is an example flowchart of the network fault notification method provided in this embodiment.

[0037] Figure 5 The embodiment provided Figure 1 An example diagram of fault notification using the network fault notification method of this embodiment.

[0038] Figure 6 This is a block diagram of an example of a network fault notification device provided in this embodiment.

[0039] Icons: 10 - network device; 11 - processor; 12 - memory; 13 - bus; 100 - network fault notification device; 110 - acquisition module; 120 - determination module; 130 - sending module. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0041] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0042] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0043] In the description of the present invention, it should be noted that if the terms "upper", "lower", "inside", "outside", etc. appear to indicate an orientation or position relationship, they are based on the orientation or position relationship shown in the accompanying drawings, or are the orientation or position relationship in which the product of the invention is usually placed when used. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0044] In addition, the terms “first”, “second”, etc., if used, are merely used to distinguish between the descriptions and should not be understood as indicating or implying relative importance.

[0045] It should be noted that, in the absence of conflict, the features in the embodiments of the present invention may be combined with each other.

[0046] For the sake of convenience, this embodiment takes the network device in the Fat-Tree network as an example. Figure 1 , Figure 1 This is an example diagram of a Fat-Tree network provided in this embodiment. The Fat-Tree network can be a two-level Fat-Tree network or a three-level Fat-Tree network. Figure 1 This is an example diagram of a three-level Fat-Tree network. Figure 1The network devices in the Fat-Tree include the Spine device at the top layer, the Leaf device at the middle layer, and the Tor (Top of Rack) device at the bottom layer. The Tor device communicates directly with the computing nodes responsible for intelligent computing. Since the main component of each node responsible for intelligent computing is the GPU (Graphics Processing Unit), Figure 1 It is simplified to GPU representation in . Figure 1 In the network, there is at least one direct link between the device of each layer and the devices of other layers. The two devices connected by a direct link are called directly connected devices. The directly connected devices learn routing table entries through BGP / OSPF / ISIS routing protocols.

[0047] Spine devices are connected to Leaf devices, and Spine devices can also be interconnected to form a flat network structure. Therefore, any two Leaf devices can achieve fast data exchange through the Spine switch.

[0048] Leaf devices are directly connected to Tor devices in the three-level Fat-Tree network and directly connected to computing nodes including GPUs in the second-level Fat-Tree network. They are the edge layer or access layer in the network and are responsible for receiving data and forwarding it to Spine devices.

[0049] The Tor device is an important device in the network architecture of the intelligent computing center. The main function of the Tor device is to provide a network access point for the computing center, so that the computing center can be directly connected to the Tor device through a shorter jumper.

[0050] It should be noted that Figure 1 This is just an example of a three-level Fat-Tree network. In actual application scenarios, the three-level Fat-Tree network can include more Tor devices, more Leaf devices, more Spine devices, more computing nodes including GPUs, and the number of direct links between each device is also greater.

[0051] It should also be noted that the secondary Fat-Tree network is similar to it, except that it includes Spine devices and Leaf devices, among which the Leaf devices communicate directly with the nodes responsible for intelligent computing. The network fault notification method provided in this embodiment is applicable to both the secondary Fat-Tree network and the tertiary Fat-Tree network.

[0052] based on Figure 1 In order to more vividly illustrate the situation in which the control plane route is affected by the link failure by using the routing protocol traffic forwarding in the prior art, please refer to Figure 2 , Figure 2 The embodiment provided Figure 1 An example diagram of a traffic forwarding path affected by a link failure in the prior art is shown in FIG. Figure 2 In the example of the failure of the link between Leaf1 and Tor1, for the traffic from Tor5 to Tor1, both paths passing through Leaf5 will pass through the failed link, so Tor5 needs to respond to the link failure and switch the traffic to the path of other Leafs. The traditional fault convergence method based on routing protocols is: after Leaf1 senses the failure of the link connected to Tor1, it sends a protocol message to Spine1 and Spine2 through the routing protocol (BGP / OSPF / ISIS) to notify the route withdrawal, the routing protocol of Spine1 and Spine2 notifies the directly connected Leaf3 and Leaf5, and the routing protocol of Leaf5 notifies Tor. The service can be restored only when Tor5 receives the protocol message and updates the local routing table. The whole process requires the participation of the control planes of multiple devices, and the convergence time is long.

[0053] In view of this, the present embodiment provides a network fault notification method, apparatus, network equipment and readable storage medium, which forward fault notification messages on the forwarding plane, avoiding the use of protocol notification routing update method for fault notification on the control plane, thereby improving the efficiency of fault notification. At the same time, the fault notification message is forwarded through at most one uplink, effectively avoiding the waste of network bandwidth caused by loop forwarding or multiple repeated forwarding of the fault notification message in the network. At the same time, it does not involve hardware improvements, reducing the difficulty of implementation. It will be described in detail below.

[0054] Please refer to Figure 3 , Figure 3 The network device 10 is a block diagram of an example of a network device provided in this embodiment. The network device 10 implements the network fault notification method of this embodiment. For a three-level Fat-Tree network, the network device 10 may be Figure 1 Spine device in the Figure 1 The Leaf device in Figure 1 For a Tor device in a secondary Fat-Tree network, the network device 10 may be a Spine device or a Leaf device. The network device 10 includes a processor 11, a memory 12, and a bus 13, and the processor 11 and the memory 12 are connected via the bus 13.

[0055] The processor 11 may be an integrated circuit chip having the ability to process signals. In the implementation process, each step of the network fault notification method of the above embodiment may be completed by an integrated logic circuit of hardware in the processor 11 or by instructions in the form of software. The above processor 11 may be a general-purpose processor, including a CPU (Central Processing Unit), a NP (Network Processor), etc.; it may also be a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Logic Gate Array) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0056] The memory 12 is used to store a program for implementing the network fault notification method. The program can be a software function module stored in the memory 12 in the form of software or firmware or solidified in the OS (Operating System) of the network device 10.

[0057] After receiving the execution instruction, the processor 11 executes the program to implement the network fault notification method of the above embodiment.

[0058] Based on the above Figure 1 and Figure 2 This embodiment provides a method that can be applied to Figure 1 Spine device, Leaf device, Tor device or Figure 2 For the convenience of description, this embodiment takes any network device in the Fat-Tree network as the execution subject (in this embodiment, it is called this network device, and the devices other than this network device in the Fat-Tree network are called other network devices) for introduction. Figure 4 , Figure 4 This is a flowchart of a network fault notification method provided in this embodiment. The method includes the following steps:

[0059] Step S101, obtaining a fault notification message.

[0060] In this embodiment, the fault notification message is generated by a network device that detects a link failure and sent to other network devices. Therefore, for this network device, the acquired fault notification message may be generated by this network device, or may be generated by other network devices and then forwarded to this network device.

[0061] In this embodiment, the fault notification message usually uses a specific identifier to distinguish it from other messages. When any network device receives a message carrying the specific identifier, it can determine that the message is a fault notification message. In addition, the fault notification message can also carry the link identifier of the faulty link, so that the network device that receives the fault notification message can perform fault processing according to the link identifier.

[0062] Step S102: determining a forwarding link from all directly connected links, where the forwarding link includes at most one uplink.

[0063] In this embodiment, the network device is directly connected to at least one directly connected network device, and the network device is set with a link type of a direct link between each directly connected network device, and the link type includes an uplink link and a downlink link. One way to determine the link type may be to pre-set a level for each network device in the Fat-Tree network, and the level of the network device is set according to its hierarchy in the Fat-Tree network, for example, Figure 1 In the example, if all Spine devices are at the same level, then all Spine devices are at the same level; if all Leaf devices are at the same level, then all Leaf devices are at the same level; if all Tor devices are at the same level, then all Tor devices are at the same level. The level of Spine devices is higher than that of Leaf devices, and the level of Leaf devices is higher than that of Tor devices. An uplink is a direct link between a network device and a directly connected network device of a higher level, and a downlink is a direct link between a network device and a directly connected network device of a lower level. For example, this network device is Figure 1 Taking Leaf1 device in as an example, its directly connected network devices include Spine1 device, Spine2 device, Tor1 device, Tor2 device, Tor3 device and Tor4 device. The direct links between Leaf1 device and Spine1 device and between Leaf1 device and Spine2 device are uplinks, and the direct links between Leaf1 device and Tor1 device, Tor2 device, Tor3 device and Tor4 device are downlinks.

[0064] In this embodiment, the forwarding link includes at most one uplink, that is, the forwarding link may include one uplink but no downlink, one uplink and at least one downlink, or multiple downlinks but no uplink.

[0065] Step S103: Send a fault notification message through each link in the forwarding link.

[0066] In this embodiment, the fault notification message is sent on the forwarding plane rather than the control plane. When the fault notification message is generated by the network device, the network device sends it to the corresponding directly connected network device through each link in the forwarding link. When the fault notification message is received by the network device from other directly connected network devices, the network device forwards the received fault notification message to the corresponding directly connected network device through each link in the forwarding link.

[0067] The above method provided in this embodiment avoids the use of protocol notification route update to perform fault notification on the control plane, thereby improving the efficiency of fault notification. It can not only enable all devices affected by the fault to quickly perceive the fault, but also effectively avoid the waste of network bandwidth caused by loop forwarding or repeated forwarding of fault notification messages in the network. At the same time, it does not involve hardware improvements, reducing the difficulty of implementation.

[0068] It should be noted that, for application scenarios with high requirements on the delay of the fault notification process, the sending and forwarding of the fault notification message can also be implemented in a hardware manner through a switching chip.

[0069] In this embodiment, the fault notification message may be sent through an uplink or a downlink. This embodiment provides an implementation method for determining a forwarding link:

[0070] If there is at least one downlink link among all the directly connected links, each downlink link is used as a link in the forwarding link;

[0071] In this embodiment, when there are downlink links in the direct link, the fault link message needs to be sent to each downlink link, which is called the "downward flooding" principle in this embodiment.

[0072] In this embodiment, when the fault notification message is forwarded by a directly connected network device, there are two situations: (1) the fault notification message is forwarded via an uplink; (2) the fault notification message is forwarded via a downlink. For (2), the fault notification message can be sent via all downlinks, because the downlink that forwards the fault notification message will not send it again even if it receives the forwarded fault notification message again; the fault notification message can also be sent via the remaining downlinks except the downlink that sent the fault notification message.

[0073] If there is at least one uplink link among all the directly connected links, the forwarding link is determined according to the fault notification message.

[0074] In this embodiment, in order to minimize repeated transmission of fault notification messages and avoid a fault notification message forwarding loop, when there is at least one uplink link among all directly connected links, whether the fault notification message needs to be forwarded through the uplink link depends on the specific situation. This embodiment provides an implementation method for determining a forwarding link according to the fault notification message:

[0075] If the fault notification message is generated by the network device when detecting a fault in a link between the network device and any directly connected network device or the fault notification message is received by the network device through at least one downlink, an uplink is determined from at least one uplink as a link in the forwarding link.

[0076] In this embodiment, the fault notification message generated by the network device or the fault notification message from the downlink needs to be sent through the uplink, but it does not need to be sent through each uplink. It only needs to select one from all uplinks for sending. The selection method can be random selection, or it can be to select a link with the most stable network from all uplinks for sending, or it can be to select a link with the smallest network bandwidth load from all uplinks for sending. This embodiment calls it the principle of "single sending upward". For the fault notification message from the uplink, it does not need to be sent through the uplink again, but only needs to be sent through each downlink. This is the principle of "single sending upward and flooding downward" proposed in this embodiment.

[0077] In this embodiment, the fault notification message may be generated by the network device itself, or may be sent to the network device by other network devices. When the network device itself generates the fault notification message, there are two ways of generating the fault notification message according to different timings of generating the fault notification message:

[0078] Method 1: Generate a fault notification message when receiving a traffic message

[0079] When a traffic message is received, the next-hop link used to forward the traffic message is determined, and the status of the next-hop link is obtained. If the status of the next-hop link is a faulty state, a notification message is generated, and the preset field in the notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain a fault notification message.

[0080] In this embodiment, the above method of obtaining notification messages can minimize the unnecessary impact of fault notification messages on network bandwidth.

[0081] Method 2: Generated when a link failure is detected

[0082] When a fault is detected in a link between any directly connected network device, a notification message is generated, a preset field in the generated notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain a fault notification message.

[0083] In this embodiment, a link failure will generate a corresponding event in the network device, and the event will trigger the generation of a fault notification message.

[0084] In this embodiment, the link failure between the present network device and the directly connected network device may be a failure of the directly connected network device or an abnormal session between the present network device and the directly connected network device. This embodiment provides a method for determining a link failure:

[0085] For any directly connected network device, if it is detected that the optical module status of the directly connected network device is abnormal, or the device port status of the directly connected network device is disconnected, or the bidirectional forwarding detection BFD session between the directly connected network device is disconnected, it is determined that the link between the network device and the directly connected network device is faulty.

[0086] In this embodiment, the device port status includes two states: UP (connected) and DOWN (disconnected). When the device port status is DOWN, it can be determined that the device port status is disconnected.

[0087] BFD sessions are used to quickly detect connectivity failures in network connections. A BFD session is a BFD connection established between two network devices. Through this connection, network devices can quickly find out whether the other party is reachable and whether the network path is normal. BFD sessions include two states: UP and DOWN. When the BFD session state is DOWN, it can be determined that the BFD session is disconnected.

[0088] In this embodiment, in order to distinguish the fault notification message from other messages, a specific identifier in the message is usually used to distinguish it from other messages. The specific identifier can be identified by using a preset field such as a special source MAC address or destination MAC address, or a special source IP address or destination IP address, or a special Ethernet header protocol type. A specific method can be to assign specific values ​​to these specific fields to identify them. In addition to using preset fields to represent the fault notification message, in order to achieve fault convergence more quickly, the information of the faulty link can also be carried in the fault notification message. For example, the link identifier that represents the faulty link is added to the fault notification message, so that the network device that receives the fault notification message can promptly know the information of the faulty link, so as to perform timely processing to avoid the faulty link. In this embodiment, when the fault notification message is received from other network devices, the method of obtaining the fault notification message is:

[0089] Receive notification messages sent by other network devices;

[0090] If the notification message contains a preset field and the preset field is a preset value, the notification message is used as a fault notification message.

[0091] To more vividly illustrate the process of fault notification by the network notification method provided in this embodiment, please refer to Figure 5 , Figure 5 The embodiment provided Figure 1 An example diagram of a fault notification using the network fault notification method of this embodiment is shown in FIG. Figure 5 When Leaf1 detects that the link between Leaf1 and Tor1 fails, it generates a fault notification message, sets the Ethernet type of the fault notification message to 0x88FF to identify the message as a fault notification message, and sets the source MAC address of the fault notification message to the link identifier link_leaf1_tor1 so that the fault notification message carries the link identifier of the faulty link. According to the principle of "single upward transmission and flooding downward", Leaf1 selects the uplink link between Leaf1 and Spine1 to send the generated fault notification message, and sends the fault notification message to Tor2, Tor3 and Tor4 through the downlink link. When Spine1 receives the fault notification message, according to the principle of "single upward transmission and flooding downward", since Spine1 does not have an uplink link, Spine1 forwards the fault notification message to Leaf3, Leaf5 and Leaf7 through the downlink link. Leaf3, Leaf5 and Leaf7 send the fault notification message to Tor1 to Tor8 through their respective downlink links according to the principle of "single upward transmission and flooding downward". It can be seen that the network fault notification method of this embodiment not only reduces the amount of fault messages sent, but also sends the fault notification message to all network devices affected by the faulty link, without affecting the fault convergence effect.

[0092] In order to execute the corresponding steps in the above embodiment and each possible implementation method, a method for implementing the network fault notification device 100 is given below. Figure 6 , Figure 6 This is a block diagram of the network fault notification device provided in this embodiment. It should be noted that the basic principle and technical effect of the network fault notification device 100 provided by the present invention are the same as those of the corresponding above-mentioned embodiments, and are not mentioned in this embodiment for the sake of brief description.

[0093] The network fault notification device 100 includes an acquisition module 110 , a determination module 120 , and a sending module 130 .

[0094] An acquisition module 110 is used to acquire a fault notification message;

[0095] A determination module 120, configured to determine a forwarding link from all directly connected links, wherein the forwarding link includes at most one uplink;

[0096] The sending module 130 is configured to send a fault notification message through each link in the forwarding link.

[0097] In an optional implementation manner, the determination module 120 is specifically configured to:

[0098] If there is at least one downlink link among all the directly connected links, each downlink link is used as a link in the forwarding link;

[0099] If there is at least one uplink link among all the directly connected links, the forwarding link is determined according to the fault notification message.

[0100] In an optional implementation manner, when the determination module 120 is used to determine the forwarding link according to the fault notification message, it is specifically used to:

[0101] If the fault notification message is generated by the network device when detecting a fault in a link between the network device and any directly connected network device or the fault notification message is received by the network device through at least one downlink, an uplink is determined from at least one uplink as a link in the forwarding link.

[0102] In an optional implementation manner, the acquisition module 110 is specifically used to:

[0103] When a traffic message is received, the next-hop link used to forward the traffic message is determined, and the status of the next-hop link is obtained. If the status of the next-hop link is a faulty state, a notification message is generated, and the preset field in the notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain a fault notification message.

[0104] In an optional implementation manner, the acquisition module 110 is further specifically configured to:

[0105] When a fault is detected in a link between any directly connected network device, a notification message is generated, a preset field in the generated notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain a fault notification message.

[0106] In an optional implementation manner, when detecting that a link between any of the directly connected network devices fails, the acquisition module 110 is further configured to:

[0107] For any directly connected network device, if it is detected that the optical module status of the directly connected network device is abnormal, or the device port status of the directly connected network device is disconnected, or the bidirectional forwarding detection BFD session between the directly connected network device is disconnected, it is determined that the link between the network device and the directly connected network device is faulty.

[0108] In an optional implementation manner, the acquisition module 110 is further configured to:

[0109] Receive notification messages sent by other network devices;

[0110] If the notification message contains a preset field and the preset field is a preset value, the notification message is used as a fault notification message.

[0111] An embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the network fault notification method described in any one of the aforementioned implementations is implemented.

[0112] In summary, the embodiments of the present invention provide a network fault notification method, apparatus, network equipment and readable storage medium, the method comprising: being applied to a network device, the network device being directly connected to at least one directly connected network device, the network device being provided with a link type of a direct link between each directly connected network device, the method comprising: obtaining a fault notification message; determining a forwarding link from all directly connected links, the forwarding link comprising at most one uplink link; and sending a fault notification message through each link in the forwarding link. Compared with the prior art, this embodiment has at least the following advantages: (1) performing fault notification according to the "single upward transmission and flooding downward" rule, so that all devices affected by the fault can quickly perceive the fault, and effectively avoiding the waste of network bandwidth caused by loop forwarding or repeated forwarding of the fault notification message in the network; (2) performing fault notification based on the device forwarding plane, without the participation of the control plane, and having a fast fault notification speed; (3) fault notification is independent of the number of service flows and has good scalability.

[0113] The above are only various embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A network fault notification method, characterized in that: Applied to a network device, the network device is directly connected to at least one directly connected network device, the network device is provided with a link type of a direct link between the network device and each of the directly connected network devices, the link type includes an uplink link and a downlink link, the method includes: Obtain fault notification message; Determine a forwarding link from all directly connected links, wherein the forwarding link includes at most one uplink; The fault notification message is sent through each link in the forwarding link.

2. The network fault notification method according to claim 1, characterized in that: The step of determining a forwarding link from all directly connected links comprises: If there is at least one downlink link among all the directly connected links, each of the downlink links is used as a link in the forwarding link; If there is at least one uplink link among all the directly connected links, the forwarding link is determined according to the fault notification message.

3. The network fault notification method according to claim 2, characterized in that: The step of determining the forwarding link according to the fault notification message comprises: If the fault notification message is generated by the network device when detecting a fault in the link between the network device and any of the directly connected network devices or the fault notification message is received by the network device through at least one of the downlink links, an uplink link is determined from the at least one uplink as a link in the forwarding link.

4. The network fault notification method according to claim 1, characterized in that: The step of obtaining the fault notification message includes: When a traffic message is received, the next-hop link used to forward the traffic message is determined, and the status of the next-hop link is obtained. If the status of the next-hop link is a faulty state, a notification message is generated, and the preset field in the notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain the fault notification message.

5. The network fault notification method according to claim 1, characterized in that: The step of obtaining the fault notification message includes: When a fault is detected in a link between any of the directly connected network devices, a notification message is generated, a preset field in the notification message is set to a preset value, and a link identifier representing the faulty link is added to the notification message to obtain the fault notification message.

6. The network fault notification method according to claim 5, characterized in that: When a failure is detected in a link between any of the directly connected network devices, the step of generating a notification message includes: For any of the directly connected network devices, if it is detected that the optical module status of the directly connected network device is abnormal, or the device port status of the directly connected network device is disconnected, or the bidirectional forwarding detection BFD session between the directly connected network device is disconnected, it is determined that the link between the network device and the directly connected network device is faulty.

7. The network fault notification method according to claim 1, characterized in that: The step of obtaining the fault notification message includes: Receive notification messages sent by other network devices; If the notification message contains a preset field and the preset field is a preset value, the notification message is used as the fault notification message.

8. A network fault notification device, characterized in that: Applied to a network device, the network device is directly connected to at least one directly connected network device, the network device is provided with a link type of a direct link between the network device and each directly connected network device, the link type includes an uplink link and a downlink link, and the device includes: An acquisition module is used to acquire fault notification messages; A determination module, configured to determine a forwarding link from all the directly connected links, wherein the forwarding link includes at most one uplink; A sending module is used to send the fault notification message through each link in the forwarding link.

9. A network device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store a program, and the processor is used to implement the network fault notification method according to any one of claims 1 to 7 when executing the program.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the computer program is executed by a processor, the network fault notification method according to any one of claims 1 to 7 is implemented.

Images