WO2022033341A1 - Path restoring method and device - Google Patents

Abstract

Disclosed are a path restoring method and a device. The method comprises: a first routing device obtains first aggregated information, and sends the obtained first aggregated information to a management device, the first aggregated information comprising an identifier of a second routing device and an identifier of at least one outbound interface of the first routing device, and the at least one outbound interface of the first routing device being used for the first routing device to send a packet to the second routing device, and thus the management device can determine a restoration path from the first routing device to the second routing device on the basis of the first aggregated information and adjacency information in a first LSDB. In this way, each routing device aggregates routing information from the routing device to other routing devices in a network domain to obtain aggregated information, and reports the obtained aggregated information to the management device as the data basis for the management device to restore the path, which can ensure that the restoration path obtained by the management device is completely consistent with the real forwarding path, and provides a reliable basis for fast and accurate troubleshooting in the network domain.

Description

A method and device for path restoration

This application claims the priority of the Chinese patent application with the application number 202010820620.5 and the application title "A method and apparatus for path restoration", which was submitted to the State Intellectual Property Office of China on August 14, 2020, the entire contents of which are incorporated by reference in in this application.

technical field

The present application relates to the field of communication technologies, and in particular, to a method and device for path restoration.

Background technique

In the network, packets are forwarded between routing devices to provide users with corresponding business services. When a service or a certain performance of a service is abnormal, in order to troubleshoot the fault, the actual forwarding path of the packet is usually restored, and troubleshooting is performed based on the restored path. In this way, the fault location can be quickly and effectively determined.

At present, the management device usually implements path restoration based on the Link State Data Base (English: Link State Data Base, abbreviated as: LSDB). The specific process includes: after the management device obtains the LSDB, it first determines the network topology based on the adjacency information included in the LSDB. , and then based on the metric value (English: metric) of each link in the LSDB and the determined network topology, the restoration path is calculated according to the Shortest Path First (English: Shortest Path First, SPF for short) algorithm. The adjacency relationship information included in the LSDB is used to indicate the connection relationship between the outgoing interface of the routing device and the incoming interface of the neighbor of the routing device. This path restoration method does not consider the configuration on each routing device, for example, does not consider the maximum number of load-balancing paths (English: maximum load-balancing) set on the routing device, resulting in the calculated restoration path and the actual forwarding in the network. The paths are inconsistent, which affects the efficiency and accuracy of troubleshooting.

Based on this, there is an urgent need to provide a path restoration method, which can accurately obtain a restoration path consistent with the real forwarding path.

SUMMARY OF THE INVENTION

Based on this, the embodiments of the present application provide a method and device for path restoration, in which the management device restores a restoration path consistent with the real forwarding path based on the aggregation information reported by each routing device and in combination with the adjacency information in the LSDB, so that Troubleshooting in the network can be faster and more accurate.

In a first aspect, an embodiment of the present application provides a method for path restoration. The path restoration process may include: a first routing device obtains first aggregation information, where the first aggregation information includes an identifier of a second routing device and a first route At least one outgoing interface identifier of the device, the at least one outgoing interface of the first routing device is used for the first routing device to send packets to the second routing device; then, the first routing device sends the first aggregation information to the management device, and manages the The device can determine the restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency information in the first LSDB, where the first LSDB is where the first routing device and the second routing device are located. The LSDB corresponding to the first network domain. In this way, each routing device aggregates the routing information from the routing device to other routing devices in the network domain to obtain aggregation information, and reports the aggregation information to the management device as the data basis for the management device to restore the path. The configuration of each routing device has been considered in the process of the restoration process. Therefore, the routing information based on the path restoration process conforms to the configuration of each routing device, so that the aggregation information obtained by aggregation also conforms to the configuration of each routing device, so that the obtained restoration path is consistent with the actual configuration of each routing device. Completely consistent forwarding paths are possible, providing a reliable basis for fast and accurate troubleshooting in the network domain.

The adjacency relationship information in the first LSDB is used to describe the topology of the first network domain. The LSDBs in the same network domain are the same, and different network domains correspond to different LSDBs.

As an example, the obtaining of the first aggregation information by the first routing device may specifically include: the first routing device obtains the first aggregation information based on the forwarding table. During specific implementation, obtaining the first aggregation information based on the forwarding table by the first routing device may include, for example: the first routing device determines in the forwarding table the outgoing address corresponding to the Internet Protocol (English: Internet Protocol, IP for short) prefix of the second routing device in the forwarding table. The interface identifier; thus, the outgoing interface identifier corresponding to the IP prefix of the second routing device is determined as at least one outgoing interface identifier of the first routing device in the first aggregation information. In this way, the first aggregation information is obtained by aggregating the next hop information of the forwarding table entries of the IP prefixes belonging to the destination routing device in the forwarding table, which provides a reliable data basis for path restoration.

As another example, the obtaining of the first aggregation information by the first routing device may specifically include: the first routing device obtains the first aggregation information from a locally saved shortest path tree (English: Shortest Path Tree, SPT for short) calculation result. It should be understood that the process of determining the real forwarding path by the first routing device may include: the first step: taking other routing devices in the first network domain except the first routing device as the destination routing device, and calculating the route from the first routing device to each route. The shortest path of the device; in the second step, based on the shortest path and the IP prefix corresponding to the destination routing device, the routing table on the first routing device is obtained; in the third step, the routing table is sent to the routing management (English: Router Management, referred to as: RM) module, the RM module determines the forwarding table based on the routing table; in the fourth step, the first routing device forwards the message to each routing device according to the forwarding table. The applicable scenario of this implementation method is: in the second step, based on the configuration such as maximum load-balancing, the shortest path that matches the configuration is selected from the shortest path, and then the routing table is generated according to the selected shortest path. Then, in the third step, the routing table is generated based on The forwarding table may not consider the configuration of the routing device, and the first routing device saves the intermediate result in the process of generating the forwarding table, that is, the routing table calculated based on the SPT algorithm and combined with the configuration of the routing device. In this way, the first aggregation information can be obtained by directly reading the saved intermediate result without additional processing by the first routing device, which can effectively improve the efficiency of the first routing device in obtaining the first aggregation information.

In a possible implementation manner, if the second routing device and the third routing device belong to the second network domain, that is, the second routing device is a border routing device of the first network domain and the second network domain, the method may also Including: the first routing device obtains second aggregation information, where the second aggregation information includes the identifier of the second routing device and the identifier of the third routing device; the first routing device sends the second aggregation information to the management device, and the management device is based on the first routing device. The first aggregation information, the second aggregation information, the adjacency relationship information in the first LSDB corresponding to the first network domain, and the adjacency relationship information in the second LSDB corresponding to the second network domain, determine that the first routing device arrives via the second routing device The restoration path of the third routing device. Wherein, since the first routing device and the third routing device belong to different network domains, in order for the first routing device to accurately restore the path to the third routing device, before the first routing device obtains the second aggregation information , the third routing device also needs to configure the identification of the third routing device (for example, the group identification (English: group id) of the third routing device), and carry the identification of the third routing device in the routing message and send it to the first routing device equipment. As an example, the routing message used to carry the identifier of the third routing device may be a Link-State Advertisement (English: Link-State Advertisement, LSA for short) packet, and the LSA packet can be extended to display the information in the LSA packet. The text carries the identifier of the third routing device. For example, the identifier of the third routing device can be carried through the extended length type value (English: Type Length Value, TLV for short) field in the LSA message. In this way, each routing device aggregates the aggregation information from the routing device to other routing devices, and reports the aggregation information to the management device. Since the configuration of each routing device has been considered in the process of actually forwarding the packet, the path restoration process The aggregation information based on the network has also been in line with the configuration of each routing device. Based on the aggregation information, the path restoration across the network domain can make the obtained restoration path and the real forwarding path exactly the same, which is fast and accurate in the network domain and in the cross-network domain scenario. Troubleshooting provides a reliable basis.

In some possible implementation manners, the first routing device sends the first aggregation information to the management device, which may periodically send the first aggregation information to the management device, or may send the first aggregation information to the management device based on a trigger instruction . The trigger instruction may be generated by the routing device based on its own events, for example, the trigger instruction is generated when the route on the routing device changes; or the trigger instruction may also be sent by the management device or other routing devices to the routing device. In this embodiment of the present application, the manner in which the first routing device sends the first aggregation information to the management device is specifically limited.

In a second aspect, an embodiment of the present application further provides a method for route restoration. The process of route restoration may include: a management device receives first aggregation information from a first routing device, where the first aggregation information includes an identifier of the second routing device and at least one outbound interface identifier of the first routing device, at least one outbound interface of the first routing device is used for the first routing device to send packets to the second routing device; then, the management device is based on the first aggregation information and The adjacency relationship information in the first LSDB determines the first restoration path from the first routing device to the second routing device, where the first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.

In a possible implementation manner, in the case where a fourth routing device is included between the first routing device and the second routing device, and the fourth routing device also belongs to the first network domain, the method may further include: a fourth routing device Obtain and send third aggregation information to the management device, where the third aggregation information includes an identifier of the second routing device and at least one outbound interface identifier of the fourth routing device, and at least one outbound interface of the fourth routing device is used for the fourth routing device Send a message to the second routing device; then, the management device determines the first restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency information in the first LSDB, which may specifically include: the management device is based on The first aggregation information, the third aggregation information, and the adjacency relationship information in the first LSDB determine a first restoration path, and the first restoration path passes through the fourth routing device.

As an example, the process for the management device to determine the first restoration path based on the first aggregation information, the third aggregation information, and the adjacency relationship information in the first LSDB may include, for example: the management device determines the first restoration path based on the first aggregation information and the first LSDB Adjacency relationship information, determining the first path from the first routing device to the fourth routing device, and the adjacency relationship information in the first LSDB is used to indicate that at least one outbound interface of the first routing device is connected to the inbound interface of the fourth routing device; Next, the management device determines a second path from the fourth routing device to the second routing device based on the third aggregation information and the adjacency relationship information in the first LSDB, and the adjacency relationship information in the first LSDB is further used to indicate the fourth routing device At least one outgoing interface of the routing device is connected to the incoming interface of the second routing device; thus, the management device determines the first restoration path based on the first path and the second path. In this way, the real forwarding path in the network domain can be restored in an orderly and efficient manner, which provides a reliable data basis for troubleshooting.

In some other possible implementation manners, if the second routing device and the third routing device belong to the second network domain, the method may further include: the management device determines a second restoration path from the first routing device to the third routing device, the The second restoration path is a path from the first routing device to the third routing device via the second routing device.

As an example, if both the first network domain and the second network domain are standard network domains, before determining the second restoration path, the method may further include: the management device receiving the second aggregation information sent by the first routing device, The second aggregation information includes the identifier of the second routing device and the identifier of the third routing device; then, the management device determines the relationship between the first routing device and the second routing device based on the first aggregation information and the adjacency information in the first LSDB. For the first restoration path, the process may include: the management device determines the first restoration path based on the first aggregation information, the second aggregation information and the adjacency relationship information in the first LSDB. The management device determines the first restoration path based on the first aggregation information, the second aggregation information, and the adjacency information in the first LSDB. Specifically, the management device may first determine the border routing device through which the second restoration path passes based on the second aggregation information. is the second routing device, so that the management device determines the first restoration path based on the first aggregation information and the adjacency relationship information in the first LSDB. Wherein, in order for the management device to know the correspondence between the third routing device and the identifier of the third routing device, the third routing device also needs to send the identifier of the third routing device to the management device.

In this example, the method provided by the embodiment of the present application may further include: the management device receives fourth aggregation information sent by the second routing device, where the fourth aggregation information includes an identifier of the third routing device and at least one output of the second routing device. The interface identifier, at least one outgoing interface of the second routing device is used for the second routing device to send packets to the third routing device; then, the process of the management device determining the second restoration path from the first routing device to the third routing device may include: : The management device determines the third restoration path from the second routing device to the third routing device according to the fourth aggregation information and the adjacency information in the second LSDB corresponding to the second network domain; The restoration path is determined, and the second restoration path is determined.

As another example, if the first network domain is a standard network domain and the second network domain is a non-standard network domain, then the management device determines the second restoration path, which may specifically be provided in the standard network domain according to the embodiment of the present application The method determines the path between the source routing device and the border routing device, and determines the path between the border routing device and the destination routing device based on the characteristics of the non-standard network domain in the non-standard network domain, so as to splicing the two paths. to get the second restoration path. Taking the second network domain as the Stub domain as an example, before determining the second restoration path, the method may further include: the management device receives a default route sent by the third routing device; then, the process of the management device determining the second restoration path may include: : The management device determines a third restoration path from the second routing device to the third routing device according to the default route; then, the management device determines the second restoration path based on the first restoration path and the third restoration path.

It should be noted that, for the specific implementation manner of the method provided in the second aspect and the effect achieved, reference may be made to the relevant description of the above-mentioned first aspect, and details are not repeated here.

In a third aspect, an embodiment of the present application further provides a method for route restoration. The process of route restoration may include: a third routing device sends a routing message to a first routing device, where the first routing device belongs to a first network domain, and a third routing device sends a routing message to a first routing device. The three-routing device belongs to the second network domain, and the routing message carries the identifier of the third routing device, so that the first routing device obtains and sends the second aggregation information to the management device based on the identifier of the third routing device. The information includes an identifier of a third routing device and an identifier of a second routing device, where the second routing device is a border device of the first network domain and the second network domain. In this way, the management device can determine the restoration path from the first routing device to the third routing device via the second routing device based on the second aggregation information.

The routing message sent by the third routing device to the first routing device may specifically be: an LSA packet sent by the third routing device to the first routing device, where the LSA packet carries the identifier of the third routing device through the extended TLV field .

As an example, the method may further include: the third routing device sends the identification of the third routing device to the management device.

It should be noted that, for the specific implementation manner of the method provided in the third aspect and the effect achieved, reference may be made to the relevant description of the above-mentioned first aspect, which will not be repeated here.

In a fourth aspect, an embodiment of the present application further provides a routing device, where the routing device is applied to the first routing device, and the routing device includes: a processing unit and a sending unit. The processing unit is configured to obtain first aggregation information, where the first aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the first routing device, and at least one outgoing interface of the first routing device is used for the first routing The device sends a packet to the second routing device; the sending unit is configured to send the first aggregation information to the management device, so that the management device determines the first route based on the first aggregation information and the adjacency information in the first link state database LSDB The restoration path from the device to the second routing device. The first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.

In some possible implementations, the processing unit is specifically configured to: obtain the first aggregation information based on the forwarding table. For example, the processing unit is specifically configured to: determine the outbound interface identifier corresponding to the IP prefix of the second routing device in the forwarding table, and determine the outbound interface identifier corresponding to the IP prefix of the second routing device as the first aggregation information At least one outbound interface identifier of a routing device.

In some other possible implementation manners, the processing unit is specifically configured to: obtain the first aggregation information from the locally saved shortest path tree SPT calculation result.

In some other possible implementations, the second routing device and the third routing device belong to the second network domain, and the processing unit of the routing device is further configured to obtain second aggregation information, where the second aggregation information includes the data of the second routing device. The identifier and the identifier of the third routing device; the sending unit is further configured to send the second aggregation information to the management device, so that the management device is based on the first aggregation information, the second aggregation information, and the adjacency in the first LSDB corresponding to the first network domain The relationship information and the adjacency relationship information in the second LSDB corresponding to the second network domain determine the restoration path from the first routing device to the third routing device via the second routing device.

The routing device further includes a receiving unit, which is configured to receive a routing message advertised by the third routing device before obtaining the second aggregation information, where the routing message carries the identifier of the third routing device. As an example, the receiving unit may be specifically configured to: receive an LSA packet sent by a third routing device, where the LSA packet carries an identifier of the third routing device through an extended TLV field.

In some possible implementation manners, the sending unit is specifically configured to: periodically send the first aggregation information to the management device.

In some other possible implementation manners, the sending unit is specifically configured to: send the first aggregation information to the management device based on the trigger instruction.

It should be noted that, the routing device provided in the fourth aspect is used to perform the relevant operations mentioned in the first aspect. For the specific implementation manner and the effect achieved, reference can be made to the relevant description of the first aspect, which is not repeated here. Repeat.

In a fifth aspect, an embodiment of the present application further provides a management device, where the management device may include: a receiving unit and a processing unit. The receiving unit is configured to receive first aggregation information from the first routing device, where the first aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the first routing device, and at least one outgoing interface of the first routing device for the first routing device to send a packet to the second routing device; the processing unit is configured to determine the relationship between the first routing device and the second routing device based on the first aggregation information and the adjacency information in the first link state database LSDB. For the first restoration path, the first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.

In some possible implementations, the receiving unit is further configured to receive third aggregation information from the fourth routing device, where the third aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the fourth routing device, and the fourth routing device At least one outgoing interface of the routing device is used for the fourth routing device to send a packet to the second routing device; then, the processing unit may be specifically configured to: based on the first aggregation information, the third aggregation information and the adjacency information in the first LSDB , determine the first restoration path, and the first restoration path passes through the fourth routing device.

In this implementation manner, as an example, the processing unit is specifically configured to: determine the first path from the first routing device to the fourth routing device based on the first aggregation information and the adjacency information in the first LSDB, and the first path in the first LSDB The adjacency relationship information is used to indicate that at least one outbound interface of the first routing device is connected to the inbound interface of the fourth routing device; based on the third aggregation information and the adjacency relationship information in the first LSDB, determine the connection between the fourth routing device and the second routing device The adjacency information in the first LSDB is also used to indicate that at least one outgoing interface of the fourth routing device is connected to the incoming interface of the second routing device; thus, based on the first path and the second path, determine the first restore path.

In some other possible implementation manners, the second routing device and the third routing device belong to the second network domain, and the processing unit is further configured to determine a second restoration path from the first routing device to the third routing device, where the second restoration path is A path from the first routing device to the third routing device via the second routing device.

As an example, the receiving unit is further configured to receive second aggregation information sent by the first routing device, where the second aggregation information includes an identifier of the second routing device and an identifier of the third routing device; then, the processing unit can be specifically used for: The first restoration path is determined based on the first aggregation information, the second aggregation information, and the adjacency relationship information in the first LSDB.

In this example, the receiving unit is further configured to receive fourth aggregation information sent by the second routing device, where the fourth aggregation information includes an identifier of the third routing device and at least one outbound interface identifier of the second routing device, and at least one One outgoing interface is used by the second routing device to send packets to the third routing device; then, the processing unit may be specifically configured to: determine the first aggregation information according to the fourth aggregation information and the adjacency information in the second LSDB corresponding to the second network domain. A third restoration path from the second routing device to the third routing device; thus, a second restoration path is determined based on the first restoration path and the third restoration path.

The receiving unit is further configured to receive the identifier of the third routing device sent by the third routing device.

As another example, the processing unit may be specifically configured to: determine a third restoration path from the second routing device to the third routing device according to the default route; thus, determine the second restoration path based on the first restoration path and the third restoration path path.

Wherein, the receiving unit is further configured to receive the default route sent by the third routing device.

It should be noted that the management device provided in the fifth aspect is used to perform the related operations mentioned in the second aspect. For the specific implementation manner and the effect achieved, reference can be made to the relevant description of the second aspect, which is not repeated here. Repeat.

In a sixth aspect, an embodiment of the present application further provides a routing device, the routing device is applied to a third routing device, the routing device includes: a sending unit, the sending unit is configured to send a routing message to the first routing device, the first routing device The routing device belongs to the first network domain, the third routing device belongs to the second network domain, and the routing message carries the identifier of the third routing device, so that the first routing device obtains based on the identifier of the third routing device and sends the second aggregation device to the management device information, the second aggregation information includes the identifier of the third routing device and the identifier of the second routing device, and the second routing device is a border device of the first network domain and the second network domain.

As an example, the sending unit is specifically configured to send an LSA packet to the first routing device, where the LSA packet carries the identifier of the third routing device through an extended TLV field.

Wherein, the sending unit is further configured to send the identifier of the third routing device to the management device.

It should be noted that the routing device provided in the sixth aspect is used to perform the related operations mentioned in the third aspect. For the specific implementation manner and the effect achieved, reference can be made to the relevant description of the third aspect, which is not repeated here. Repeat.

In a seventh aspect, an embodiment of the present application further provides a routing device, including: a memory and a processor. Wherein, the memory is used for storing program codes or instructions; the processor is used for running the program codes or instructions, so that the routing device executes the method provided in the first aspect above.

In an eighth aspect, an embodiment of the present application further provides a management device, including: a memory and a processor. The memory is used for storing program codes or instructions; the processor is used for running the program codes or instructions, so that the management device executes the method provided in the second aspect above.

In a ninth aspect, an embodiment of the present application further provides a routing device, including: a memory and a processor. The memory is used for storing program codes or instructions; the processor is used for running the program codes or instructions, so that the routing device executes the method provided in the third aspect.

In a tenth aspect, an embodiment of the present application further provides a network system, where the network system includes the routing device provided in the fourth aspect, the management device provided in the fifth aspect, and the routing device provided in the sixth aspect; or, the network system may also It may include the routing device provided in the seventh aspect, the management device provided in the eighth aspect, and the routing device provided in the ninth aspect.

In an eleventh aspect, the embodiments of the present application also provide a computer-readable storage medium, where program codes or instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer can execute the first aspect and the first The method provided in any one of the possible implementation manners provided in the second aspect or the third aspect.

In a twelfth aspect, an embodiment of the present application further provides a computer program product, which, when the computer program product runs on a network device, enables the network device to perform any one of the first aspect, the second aspect, or the third aspect. methods provided in the implementation of .

Description of drawings

FIG. 1 is a schematic structural diagram of a network domain 100 involved in an application scenario in an embodiment of the present application;

FIG. 2 is a signaling flowchart of a method 100 for path restoration in an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a network 10 in an embodiment of the application;

FIG. 4 is a signaling flowchart of a method 200 for path restoration in an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a network 20 in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a first routing device 600 in an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a management device 700 in an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a third routing device 800 in an embodiment of the present application;

FIG. 9 is a schematic structural diagram of another first routing device 900 in an embodiment of the present application;

FIG. 10 is a schematic structural diagram of another management device 1000 in an embodiment of the present application;

FIG. 11 is a schematic structural diagram of another third routing device 1100 in an embodiment of the present application;

FIG. 12 is a schematic structural diagram of a network system 1200 in an embodiment of the present application.

detailed description

Path restoration is an effective method for troubleshooting. When an abnormality occurs in the network, the restoration path that is consistent with the actual forwarding path of the packet is restored to quickly and effectively implement troubleshooting and positioning. At present, the LSDB is usually used to calculate the restoration path. The specific process may include: after the management device obtains the LSDB in the network domain, firstly determines the network topology based on the adjacency information included in the LSDB, and then determines the network topology based on the metric and the determined value of each link in the LSDB. Network topology, calculate the restoration path according to the SPF algorithm. Because the configuration of each routing device is also considered in the real forwarding path, and the configuration of each routing device is not considered in the restoration path calculated in this path restoration method, the obtained restoration path is likely to be inconsistent with the real forwarding path, which affects troubleshooting. and positioning effects.

For example, for the network domain 100 shown in Figure 1, there are 3 equal-cost paths from the routing device 10 to the routing device 15 calculated according to the SPF algorithm, which are: Path 1: routing device 10-routing device 11-routing device 12 - routing device 15, path 2: routing device 10 - routing device 11 - routing device 13 - routing device 15, and path 3: routing device 10 - routing device 11 - routing device 14 - routing device 15. Assuming that the maximum load-balancing=2 configured on the routing device 11, select 2 out of 3 equal-cost paths according to certain rules, and use the selected path as the real forwarding path for forwarding packets. For example, the real forwarding path is path 1 and path 3. Then, the forwarding table for guiding forwarding also includes only the relevant forwarding table entries of path 1 and path 3.

Each routing device in the network domain 100 has the same LSDB, and the LSDB includes adjacency information and the metric of each link, wherein the adjacency information is used to indicate the connection relationship between adjacent routing devices, for example: routing device 10 The A interface is connected to the A interface of the routing device 11. The metric of each link is used to reflect the parameters of the link. For example, the metric of the link 1 from the routing device 10 to the routing device 11 is the link cost x1 of the link 1. For example, the LSDB corresponding to the network domain 100 can be referred to as shown in Table 1 below:

Table 1 LSDB

Wherein, for example, x2+x5=x3+x6=x4+x7, that is, the sum of link costs of path 1, path 2 and path 3 are equal.

During the path restoration process, any one or more routing devices in the network domain 100 send the LSDB shown in Table 1 to the management device 50, and the management device 50 determines, based on the adjacency information in the LSDB, as shown in FIG. 1 . Network topology; then, based on the network topology and the metric in the LSDB, the management device 50 calculates an equivalent path through the SPF algorithm, and the obtained restoration path includes path 1 , path 2 and path 3 . It can be seen that the restoration path obtained by the path restoration method is inconsistent with the real forwarding path, which affects the efficiency and accuracy of troubleshooting in the network domain 100 .

Based on this, in the embodiment of the present application, a method for restoring a path is provided, which can accurately restore a restoring path that is consistent with the real forwarding path. For the first routing device and the second routing device belonging to the same network domain, the process of restoring the restoration path from the first routing device to the second routing device may include: the first routing device obtains and sends aggregation information to the management device, the aggregation information It includes the identifier of the second routing device and at least one outgoing interface identifier of the first routing device, and at least one outgoing interface of the first routing device is used for the first routing device to send packets to the second routing device; in this way, the management device can be based on The aggregation information and the adjacency information in the LSDB corresponding to the network domain determine the restoration path from the first routing device to the second routing device. In this way, each routing device aggregates the routing information from the routing device to other routing devices in the network domain to obtain aggregation information, and reports the aggregation information to the management device as the data basis for the management device to restore the path. The configuration of each routing device has been considered in the process of routing, so the routing information based on the path restoration process conforms to the configuration of each routing device, so that the aggregated aggregated information also conforms to the configuration of each routing device, so that the restored path obtained is consistent with the actual configuration of each routing device. Completely consistent forwarding paths are possible, providing a reliable basis for fast and accurate troubleshooting in the network domain.

For example, still taking the scenario shown in FIG. 1 as an example, it is assumed that the real restoration paths are path 1 and path 3. Each routing device obtains the aggregation information from the routing device to other routing devices. The aggregation information 1 of the routing device 10 can be shown in Table 2 below:

Table 2 Aggregated Information 1

The ID of the destination routing device	Outbound interface ID
11	A
12	A
13	A
14	A
15	A

Wherein, each row in the aggregation information 1 is used to indicate the outbound interface of the routing device 10 when the packet is sent from the routing device 10 to the identified routing device; for example, the aggregation information in the third row is used to indicate that the slave routing device 10 When the packet is sent to the routing device 12, it passes through the outgoing interface A of the routing device 10.

The aggregation information 2 of the routing device 11 may be shown in Table 3 below:

Table 3 Aggregated Information 2

The aggregation information 3 of the routing device 12 may be shown in Table 4 below:

Table 4 Aggregated Information 3

The ID of the destination routing device

Outbound interface ID

10	A
11	A
13	A
14	A
15	B

The aggregation information 4 of the routing device 13 may be shown in Table 5 below:

Table 5 Aggregated Information 4

The ID of the destination routing device	Outbound interface ID
10	A
11	A
12	A
14	A
15	B

The aggregation information 5 of the routing device 14 may be shown in Table 6 below:

Table 6 Aggregation Information 5

The ID of the destination routing device	Outbound interface ID
10	A
11	A
12	A
13	A
15	B

The aggregation information 6 of the routing device 15 can be shown in Table 7 below:

Table 7 Aggregated Information 6

It should be noted that, in order to provide a more reliable data basis for path restoration, the aggregation information can also carry the Internet protocol of the incoming interface of the routing device identified when the local routing device sends the packet to the identified destination routing device to receive the packet. (English: Internet Protocol, IP for short) address, take the aggregation information 1 of the routing device 10 as an example, the aggregation information can also be shown in Table 8 below, and the aggregation information of other routing devices is also similar.

Table 8 Aggregation Information 1

The ID of the destination routing device	Outbound interface ID	IP address of the inbound interface of the destination routing device
11	A	IP address 1
12	A	IP address 1
13	A	IP address 1
14	A	IP address 1
15	A	IP address 1

Based on the aggregation information in Tables 2 to 7 and the LSDB shown in Table 1, the management device 50 can obtain a restoration path between each routing device, wherein the obtained restoration path includes the path from the routing device 10 to the routing device 15. There are two restoration paths, namely path 1 and path 3. The process of restoring the path 1 and the path 2 by the management device 50 may include, for example:

S11, the management device 50 determines, based on Table 2, that the destination routing device 15 corresponds to the outbound interface A of the routing device 10, and determines that the interface A of the routing device 10 and the interface A of the routing device 11 are connected based on Table 1, so as to determine that the restoration path includes "routing device 10". 10-routing device 11";

S12, the management device 50 determines, based on Table 3, that the destination routing device 15 corresponds to the outbound interfaces B and D of the routing device 11, and determines, based on Table 1, that the interface B of the routing device 11 is connected to the interface A of the routing device 12, and the interface D of the routing device 11 is connected to the interface A of the routing device 12. Interface A of the routing device 14 is connected, thereby determining that the restoration path includes "routing device 10-routing device 11-routing device 12" and "routing device 10-routing device 11-routing device 14";

S13, the management device 50 determines, based on Table 4, that the destination routing device 15 corresponds to the outbound interface B of the routing device 12, and determines that the interface B of the routing device 12 is connected to the interface A of the routing device 15 based on Table 1, thereby determining that the restoration path includes "routing device 15". 10-routing device 11-routing device 12-routing device 15";

S14, the management device 50 determines, based on Table 6, that the destination routing device 15 corresponds to the outbound interface B of the routing device 14, and determines that the interface B of the routing device 14 and the interface C of the routing device 15 are connected based on Table 1, so as to determine that the restoration path includes "routing device 14". 10-routing device 11-routing device 14-routing device 15".

It can be seen that the management device 50 restores the path 1 and the path 3 shown in FIG. 1 , which are consistent with the actual forwarding path of the packet.

It should be noted that the above-mentioned routing device refers to a network device with a packet forwarding function, such as a router or a switch. A management device refers to a device with a path restoration function, such as a controller, server, or routing device.

The specific implementation of a method for path restoration in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

FIG. 2 is a signaling flowchart of a path restoration method 100 in an embodiment of the present application. Referring to FIG. 2 , the method 100 is applied in the first network domain, and the embodiment of the present application is introduced by the interaction between the source node of the restoration path and the management device. For example, the method 100 may be applied in the network domain 100 shown in FIG. 1 . In an example, the method 100 may be to restore the path between the routing device 10 and the routing device 15 , where the routing device 10 may correspond to the method 100 The first routing device in , the routing device 15 corresponds to the second routing device in the method 100 , and the management device 50 corresponds to the management device in the method 100 . It should be noted that the method 100 only involves the restoration of paths within a network domain. For restoration paths involving multiple network domains, please refer to the related description of the method 200 below.

During specific implementation, the method 100 may, for example, include the following S101 to S104:

S101. A first routing device obtains first aggregation information, where the first aggregation information includes an identifier of the second routing device and at least one outbound interface identifier of the first routing device, where the at least one outbound interface of the first routing device is used for the first routing device. The routing device sends the packet to the second routing device.

Before S101, the process of determining the real forwarding path by the first routing device may include: S21, using other routing devices in the first network domain except the first routing device as destination routing devices, calculating the distance between the first routing device and each routing device S22, obtain the routing table on the first routing device based on the shortest path and the IP prefix corresponding to the destination routing device; S23, send the routing table to the routing management (English: Router Management, referred to as: RM) module, RM The module determines a forwarding table based on the routing table; S24, the first routing device forwards the packet to each routing device according to the forwarding table.

As an example, in S22, the shortest path that conforms to the configuration can be selected from the shortest paths based on the configuration such as maximum load-balancing, and then the routing table can be generated according to the selected shortest path. Then, the routing table can be generated based on the routing table in S23 without considering the routing. Device configuration. Taking the network domain 100 shown in FIG. 1 as an example, the generating process of the forwarding table entry corresponding to the routing device 15 in the forwarding table on the routing device 10 may include: the routing device 10 is based on the shortest path tree (English: Shortest Path Tree, referred to as shortest path tree). : SPT) algorithm calculates the shortest path from routing device 10 to routing device 15, obtains path 1, path 2 and path 3, and then based on the maximum load-balancing of each routing device passing through path 1 to path 3, from the three shortest paths Select the shortest path in line with maximum load-balancing: path 1 and path 3 (due to maximum load-balancing=2 of routing device 11), based on IP prefix 1 corresponding to path 1 and routing device 15, path 3 and routing device 15 correspond to IP prefix 3, obtain the routing table 1 on the routing device 10; send the routing table 1 to the RM module 101, and the RM module 101 directly determines the forwarding table 1 based on the routing table 1, and the forwarding table 1 corresponds to the routing device 15. The published entry is the same as the routing entry corresponding to the routing device 15 in the routing table 1 generated above.

In this example, if the first routing device saves the intermediate result (that is, the routing table calculated based on the SPT algorithm and combined with the configuration of the routing device) in the process of generating the forwarding table, then the first aggregation result is obtained in S101, which may be specifically It means: the first routing device obtains the first aggregation information from the SPT calculation result stored locally. In this way, there is no need for the first routing device to perform additional processing, which can effectively improve the efficiency with which the first routing device obtains the first aggregation information.

As another example, in S22, a routing table can be generated directly based on the calculated shortest path, regardless of the configuration of the routing device. However, in S23, the shortest path that matches the configuration is selected from the routing table based on the configuration such as maximum load-balancing, and then The forwarding table is generated according to the shortest path selected in the routing table. Taking the network domain 100 shown in FIG. 1 as an example, the process of generating a forwarding table entry corresponding to the routing device 15 in the forwarding table on the routing device 10 may include: Shortest path, path 1, path 2 and path 3 are obtained, based on IP prefix 1 corresponding to path 1 and routing device 15, IP prefix 2 corresponding to path 2 and routing device 15, and IP prefix 3 corresponding to path 3 and routing device 15 , obtain the routing table 2 on the routing device 10; send the routing table 2 to the RM module 101, and the RM module 101 is based on the routing table 2, combined with the maximum load-balancing of each routing device on path 1 to path 3, from 3 In the shortest path, select the shortest path that conforms to maximum load-balancing: path 1 and path 3, so as to filter the routing table entries corresponding to path 1 and path 3 from routing table 2, and determine the routing based on the routing table entries corresponding to path 1 and path 3. Publication 1, the number of forwarding table entries corresponding to the routing device 15 in the forwarding table 1 may be different from the number of routing table entries corresponding to the routing device 15 in the above-generated routing table.

In this example, S101 may specifically be that the first routing device obtains the first aggregation information based on the forwarding table. For example, the first routing device determines the outbound interface identifier corresponding to the Internet Protocol IP prefix of the second routing device in the forwarding table, and determines the determined outbound interface identifier corresponding to the IP prefix of the second routing device as the first aggregation At least one outgoing interface identifier of the first routing device in the information, so that the first aggregation information including at least the identifier of the second routing device and the at least one outgoing interface identifier on the first routing device is obtained. In this way, the first aggregation information is obtained by aggregating the next hop information of the forwarding table entries of the IP prefixes belonging to the destination routing device in the forwarding table, which provides a reliable data basis for path restoration.

It should be noted that the first routing device and the second routing device may be any two different routing devices in the same network domain. Forwarding paths for accurate restoration.

In this embodiment, restoring the real forwarding path between the first routing device and the second routing device is used as an example for description. The second routing device is the destination routing device of the path to be restored, and the first routing device may be the same as the second routing device. Any routing device directly or indirectly connected to the device. In one case, if the first routing device and the second routing device are directly connected, the management device only needs to restore the restoration path from the first routing device to the second routing device based on the first aggregation information and the first aggregation information reported by the first routing device. The LSDB corresponding to this network domain. In another case, if the first routing device and the second routing device are not directly connected, the management device needs to restore the restoration path from the first routing device to the second routing device based on the first aggregation information reported by the first routing device , the LSDB corresponding to the network domain and the aggregation information reported by other routing devices in the network domain. For details, refer to the relevant description of S104 below.

For example, assuming that the first routing device is the routing device 10 in the network domain 100, the first aggregation information may be the aggregation information 1 shown in Table 2; the first aggregation information may also be the aggregation information 1 shown in Table 2. The row corresponding to the second routing device, for example, the second routing device is routing device 11, then the first aggregation information may be the second row in aggregation information 1, and the first aggregation information is used to indicate the routing device 10 to the routing device 11. When the routing device 11 sends the packet, it goes through the outbound interface A of the routing device 10; for another example, if the second routing device is the routing device 15, the first aggregation information may be the sixth line in the aggregation information 1, and the first aggregation information The information is used to indicate that a packet is sent from the routing device 10 to the routing device 15 through the outbound interface A of the routing device 10 .

S102, the first routing device sends the first aggregation information to the management device.

S103, the management device receives the first aggregation information from the first routing device.

As an example, each routing device may periodically send the obtained aggregation information to the management device, and the period for sending the aggregation information may be pre-configured by the routing device, or may be uniformly configured by the management device for all routing devices. In this example, S102 and S103 may be, for example: the first routing device periodically sends the first aggregation information to the management device; the management device receives the first aggregation information sent by the first routing device.

As another example, each routing device may send the obtained aggregation information to the management device based on a trigger instruction, and the trigger instruction may be generated by the routing device based on its own event, for example, the route on the routing device changes; The instruction may also be sent by the management device or other routing device to the routing device. In this example, S102 and S103 may be, for example: the first routing device sends the first aggregation information to the management device based on the trigger instruction; the management device receives the first aggregation information sent by the first routing device.

It should be noted that, after receiving the aggregation information sent by each routing device, the management device may execute the following S104 to restore the real forwarding path in the network domain. The specific path that needs to be restored can be determined based on the actual network conditions. For example, if the management device determines that the network domain is abnormal, but cannot determine the smaller scope that causes the abnormality, the management device can restore all real forwarding paths in the network domain. Another example: the management device determines that the network domain is abnormal and determines that the service performance provided by the border routing device 15 in the network domain is abnormal, then the management device can use the routing device 15 as the destination routing device to restore all routing devices from the network domain The path to the routing device 15 is sufficient. In this way, this embodiment can restore the required path in a targeted and accurate manner, which provides convenience for troubleshooting and locating faults.

S104, the management device determines a first restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency information in the first LSDB, where the first LSDB is where the first routing device and the second routing device are located The LSDB corresponding to the first network domain.

As an example, if the first routing device and the second routing device are directly connected, S104 may include: the management device obtains, from the first aggregation information, the data of the second routing device that matches the destination routing device (ie, the second routing device). identifier, determine the outgoing interface identifier of the first routing device corresponding to the identifier of the second routing device, thereby determining the outgoing interface corresponding to the outgoing interface identifier of the first routing device; then, the management device obtains the information from the adjacency relationship information of the first LSDB. , to learn that the determined outbound interface of the first routing device is connected to the inbound interface of the second routing device, so that the first restoration path from the first routing device to the second routing device is determined. For example: assuming that the first routing device, the second routing device and the management device are respectively the routing device 10, the routing device 11 and the management device 50 in the network domain 100, then S104 may include: the management device 50 converges from the aggregation shown in Table 2 In the second row of information 1, it is determined that the packet is forwarded from the outbound interface A of the routing device 10 to the routing device 11; then, the management device 50 determines the interface A of the routing device 10 and the routing device 11 from the second row of the LSDB in Table 1. Therefore, the restoration path 1 from the A interface of the routing device 10 to the A interface of the routing device 11 is obtained.

As another example, if the first routing device and the second routing device are not directly connected, for example, at least one routing device is included between the first routing device and the second routing device, then, before S104, the method 100 may further include : The management device receives the aggregation information sent by each routing device included between the first routing device and the second routing device. Then, the data base for determining the restoration path in S104 also needs to include aggregation information sent by other routing devices.

Taking a fourth routing device between the first routing device and the second routing device as an example, before S104, the method 100 may further include: S31, the fourth routing device obtains third aggregation information, where the third aggregation information includes the second The identifier of the routing device and the identifier of at least one outgoing interface of the fourth routing device, the at least one outgoing interface of the fourth routing device is used for the fourth routing device to send the packet to the second routing device; S32, the fourth routing device sends the message to the management device third aggregation information; S33, the management device receives the third aggregation information sent by the fourth routing device. It should be noted that, for the specific implementation manners of S31 to S33 and the effects achieved, reference may be made to the relevant descriptions of S101 to S103 above.

In this example, S104 may, for example, include: the management device determines the first restoration path based on the first aggregation information, the third aggregation information and the adjacency relationship information in the first LSDB, and the first restoration path passes through the fourth routing device. Specifically, S104 may include: S41, the management device may determine the first path from the first routing device to the fourth routing device based on the first aggregation information and the adjacency information in the first LSDB, and the adjacency in the first LSDB The relationship information is used to indicate that at least one outbound interface of the first routing device is connected to the inbound interface of the fourth routing device; S42, the management device determines, based on the third aggregation information and the adjacency relationship information in the first LSDB, the connection between the fourth routing device and the fourth routing device. The second path of the second routing device, the adjacency relationship information in the first LSDB is further used to indicate that at least one outgoing interface of the fourth routing device is connected to the incoming interface of the second routing device; S43, the management device is based on the first A path and a second path determine the first restoration path. For example: Assuming that the first routing device, the second routing device, the fourth routing device and the management device are respectively the routing device 11, the routing device 15, the routing device 12 and the management device 50 in the network domain 100, then S104 may include: management From the sixth row of the aggregation information 2 shown in Table 3, the device 50 determines that the packet is forwarded from the outbound interface B of the routing device 11 to the routing device 15. Next, the management device 50 determines the route from the third row of the LSDB in Table 1. The interface B of the device 11 is connected to the interface A of the routing device 12, so the path b from the B interface of the routing device 11 to the A interface of the routing device 12 is obtained; , determine that the packet is forwarded from the outbound interface B of the routing device 12 to the routing device 15, and then, the management device 50 determines the connection between the interface B of the routing device 12 and the interface A of the routing device 15 from the sixth row of the LSDB in Table 1, so , to obtain the path d from the B interface of the routing device 12 to the A interface of the routing device 15; thus, the management device 50 can obtain the restoration path 1 from the routing device 11 to the routing device 15 through the routing device 12 according to the path b and the path d.

It should be noted that, in the case where the first routing device and the second routing device are not directly connected, there may be multiple fourth routing devices, and the generated first restoration path may be multiple equal-cost paths. For a method of restoring a path, reference may be made to the relevant description in the foregoing implementation manner.

For example: assuming that the first routing device, the second routing device and the management device are respectively the routing device 10, the routing device 15 and the management device 50 in the network domain 100, then S104 may include: the management device 50 is shown in Table 2 In the sixth row of the aggregation information 1, it is determined that the packet is forwarded from the outbound interface A of the routing device 10 to the routing device 15. Next, the management device 50 determines the interface A of the routing device 10 and the route from the first row of the LSDB in Table 1. The interface A of the device 11 is connected, so the path a from the A interface of the routing device 10 to the A interface of the routing device 11 is obtained; the management device 50 determines from the sixth row of the aggregation information 2 shown in Table 3 that the packet is sent from the routing device The outgoing interfaces B and D of 11 are forwarded to the routing device 15. Next, the management device 50 determines the connection between the interface B of the routing device 11 and the interface A of the routing device 12 from the third and fifth rows of the LSDB in Table 1, and the routing device. The interface D of 11 is connected with the interface A of the routing device 14, so the path b from the B interface of the routing device 11 to the A interface of the routing device 12 and the path c from the D interface of the routing device 11 to the A interface of the routing device 14 are obtained; From the sixth row of the aggregation information 3 shown in Table 4, the management device 50 determines that the packet is forwarded from the outbound interface B of the routing device 12 to the routing device 15. Next, the management device 50 determines from the sixth row of the LSDB in Table 1. The interface B of the routing device 12 is connected to the interface A of the routing device 15, so the path d from the B interface of the routing device 12 to the A interface of the routing device 15 is obtained; OK, confirm that the packet is forwarded from the outbound interface B of the routing device 14 to the routing device 15, then, the management device 50 determines the connection between the interface B of the routing device 14 and the interface C of the routing device 15 from the eighth row of the LSDB in Table 1, Therefore, the path e from the B interface of the routing device 14 to the C interface of the routing device 15 is obtained; in this way, the management device 50 can obtain the restoration path 1 according to the path a, the path b and the path d, and obtain the restoration path 1 according to the path a, the path c and the path e. The restoration path 2, both of which are restoration paths from the routing device 10 to the routing device 15, are consistent with the real forwarding path between the routing device 10 and the routing device 15.

In this way, with the method 100 provided in this embodiment of the present application, for the first routing device and the second routing device belonging to the same network domain, the first routing device obtains and sends the first aggregation information to the management device, where the first aggregation information includes the first aggregation information. The identifier of the second routing device and the identifier of at least one outgoing interface of the first routing device, and at least one outgoing interface of the first routing device is used for the first routing device to send packets to the second routing device; in this way, the management device can be based on the first routing device. The aggregation information and the adjacency information in the first LSDB corresponding to the network domain determine the restoration path from the first routing device to the second routing device. In this way, each routing device aggregates the aggregation information of the routing device to other routing devices in the network domain, and reports the aggregation information to the management device. Since the configuration of each routing device has been considered in the process of actually forwarding the packet, therefore, The aggregation information based on the path restoration process has also conformed to the configuration of each routing device. The path restoration based on the aggregation information can make the obtained restoration path and the real forwarding path exactly the same, which provides a reliable solution for fast and accurate troubleshooting in the network domain. in accordance with.

In some possible implementations, considering that there is also a need to restore the real forwarding path across network domains in an actual scenario, the embodiment of the present application also provides a method 200 for restoring a path. The method 200 The embodiments of the present application are introduced by applying to the first network domain and the second network domain to restore the interaction between the source node of the path and the management device. The method 200 can be applied to, for example, the network 10 shown in FIG. 3 , and the network 10 includes the network domain 200 in addition to the network domain 100 shown in FIG. 1 .

As shown in FIG. 3 , in the network 100 , the routing device 15 is a border routing device of the network domain 100 and the network domain 200 . Network domain 200 includes routing device 17 and routing device 18 . The network domain 100 and the network domain 200 are both responsible for the path restoration by the management device 50 .

In an example, the method 200 may be to restore the path between the routing device 10 and the routing device 18, wherein the routing device 10 may correspond to the first routing device in the method 200, and the routing device 15 may correspond to the first routing device in the method 200. Two routing devices, the routing device 18 corresponds to the third routing device in the method 200 , and the management device 50 corresponds to the management device in the method 200 . It should be noted that, for the specific implementation of path restoration in the network domain involved in the method 200, reference may be made to the relevant description of the above-mentioned method 100.

During specific implementation, the method 200 may, for example, include the following S201 to S210:

S201, a third routing device sends a routing message to the first routing device, where the routing message carries an identifier of the third routing device.

It can be understood that, in the above method 100, the first routing device performs aggregation based on the IP prefix of the destination routing device to obtain the first aggregation information. However, since the destination routing device (ie, the third routing device) and the first routing device do not belong to Therefore, the first routing device cannot obtain aggregation information based on the IP prefix of the destination routing device. Based on this, the third routing device can configure the identifier of the third routing device, and flood the identifier of the third routing device to other network domains through routing messages. The identifier of the third routing device is used to uniquely identify the third routing device, for example, it may be a group identifier (English: group id) of the third routing device.

As an example, the routing message sent by the third routing device to the first routing device may specifically be a Link-State Advertisement (English: Link-State Advertisement, LSA for short) packet, and the LSA packet can be extended to The LSA packet carries the identifier of the third routing device. For example, the identifier of the third routing device may be carried through the extended length type value (English: Type Length Value, TLV for short) field in the LSA message.

It should be noted that, in order to allow the management device to accurately restore the path across network domains, after the third routing device is configured with the identifier of the third routing device, the third routing device can also send the identifier of the third routing device to the management device, so as to facilitate management. The device knows that the third routing device corresponds to the identifier of the third routing device, and the identifier of the third routing device is used to uniquely identify the third routing device.

S202, the first routing device acquires first aggregation information and second aggregation information, where the first aggregation information includes an identifier of the second routing device and at least one outbound interface identifier of the first routing device, and at least one of the first routing device's identifiers One outgoing interface is used for the first routing device to send a packet to the second routing device, and the second aggregation information includes the identifier of the second routing device and the identifier of the third routing device.

The manner in which the first routing device obtains the first aggregation information and the content of the first aggregation information can be referred to the relevant description of S101 in the foregoing method 100, and details are not repeated here.

For the first routing device, in order to subsequently restore the restoration path across the network domain from the first routing device to the third routing device, the boundary routing device whose destination routing device is the third routing device may also be aggregated to obtain the second aggregation information. Specifically, the first routing device may determine a border routing device corresponding to the identifier of the third routing device, and use the determined identifier of the border routing device and the identifier of the third routing device as the second aggregation information. It should be noted that, in the method 200, a border routing device (ie, a second routing device) is used as an example for description, and the processing method for determining a plurality of border routing devices to the destination routing device, and the implementation of one border routing device The method is the same and will not be repeated here.

Taking the network 10 shown in FIG. 3 as an example, if the first routing device is the routing device 10, the second routing device is the routing device 15, and the third routing device is the routing device 18, the first aggregation information can refer to the above Table 2 , the second aggregated information can participate in the third row of aggregated information 10 shown in Table 10 below:

Table 10 Aggregated Information 10

The ID of the destination routing device	ID of the border routing device
17	15
18	15

Taking the third row of Table 10 as an example, the aggregation information 10 is used to indicate that the border routing device to be passed from the routing device 10 to the routing device 17 is the routing device 15 .

S203, the first routing device sends the first aggregation information and the second aggregation information to the management device.

S204, the management device receives the first aggregation information and the second aggregation information sent by the first routing device.

Specifically, in reality, the first routing device may periodically send the first aggregation information and the second aggregation information to the management device, and may also send the first aggregation information and the second aggregation information to the management device based on a trigger instruction, which is not specified in this embodiment. limited.

It should be noted that the first routing device may carry the first aggregation information and the second aggregation information in two different messages and send them to the management device, or may carry the first aggregation information and the second aggregation information in one message. is sent to the management device, which is not specifically limited in this embodiment.

S205: The second routing device acquires fourth aggregation information, where the fourth aggregation information includes an identifier of the third routing device and at least one outbound interface identifier of the second routing device, and the at least one outbound interface of the second routing device is used for The second routing device sends the packet to the third routing device.

For the manner in which the second routing device obtains the fourth aggregation information and the content of the fourth aggregation information, reference may be made to the relevant description of S101 in the foregoing method 100, and details are not repeated here.

Taking the network 10 shown in FIG. 3 as an example, if the second routing device is the routing device 15 and the third routing device is the routing device 18, the interface D of the routing device 15 is connected to the interface A of the routing device 17, and the interface B of the routing device 17 is connected. Connect the interface A of the routing device 18, then, the fourth aggregation information can participate in the aggregation information 11 shown in the following table 11:

Table 11 Aggregated Information 11

The ID of the destination routing device	Outbound interface ID
17	D
18	D

S206, the second routing device sends fourth aggregation information to the management device.

S207, the management device receives the fourth aggregation information sent by the second routing device.

Specifically, in reality, the second routing device may periodically send the fourth aggregation information to the management device, or may send the fourth aggregation information to the management device based on a trigger instruction, which is not specifically limited in this embodiment.

It should be noted that the above-mentioned executions of S202 to S204 and S205 to S207 are not limited in order. S202 to S204 can be executed first and then S205 to S207, or S205 to S207 can be executed first and then S202 to S204, or they can be executed at the same time. S202 to S204 and S205 to S207.

S208, the management device determines the first restoration path based on the first aggregation information, the second aggregation information, and the adjacency relationship information in the first LSDB.

When specifically implemented, S208 may specifically include: S2081, the management device determines, based on the second aggregation information, the border routing device that the path from the first routing device to the third routing device passes through as the second routing device; S2082, the management device is based on the first routing device. The information and the adjacency relationship information in the first LSDB are aggregated to determine the first restoration path.

Taking the network 10 shown in FIG. 3 as an example, if the first routing device is routing device 10, the second routing device is routing device 15, the third routing device is routing device 18, and the second aggregation information is shown in Table 10, then Based on the third row in Table 10 , it is determined that the border routing device through which the restoration path from routing device 10 to routing device 18 passes is routing device 15 .

It should be noted that, for the specific implementation manner and effect of S2082, reference may be made to the relevant description of S104 in the foregoing method 100, and details are not repeated here.

S209, the management device determines a third restoration path from the second routing device to the third routing device based on the fourth aggregation information and the adjacency relationship information in the second LSDB corresponding to the second network domain.

The LSDBs in one network domain are the same, but the LSDBs in different network domains are different, and the adjacency relationship information in the LSDB is used to describe the topology of the routing device in the network domain corresponding to the LSDB.

It should be noted that, for the specific implementation manner and effect of determining the third restoration path by the management device, reference may be made to the relevant description of S104 in the above method 100.

S210, the management device determines a second restoration path based on the first restoration path and the third restoration path, where the second restoration path is a path from the first routing device to the third routing device via the second routing device.

During specific implementation, the management device determines the first restoration path from the first routing device to the second routing device in the first network domain, and the third restoration path from the second routing device to the third routing device in the second network domain Afterwards, the management device may splicing the first restoration path and the third restoration path to obtain a second restoration path from the first routing device to the third routing device.

As an example, if the border routing device includes only one second routing device, the second restoration path can be obtained by simply splicing the first restoration path and the third restoration path determined respectively by the two network domains. For example: taking the network 10 shown in FIG. 3 as an example, the management device 50 determines that the first restoration path includes path 1 and path 3, and the third restoration path is path 4: routing device 15-routing device 17-routing device 18, then, The second restoration path includes path 14 and path 34, wherein path 14 is: routing device 10-routing device 11-routing device 12-routing device 15-routing device 17-routing device 18, and path 34 is: routing device 10-routing device Device 11 - Routing Device 14 - Routing Device 15 - Routing Device 17 - Routing Device 18.

As another example, if the border routing device includes multiple routing devices, the first restoration path and the third restoration path determined respectively in the two network domains can be spliced according to the preset splicing rule to obtain the second restoration path . Taking the border routing device as the second routing device and the fifth routing device as an example, the splicing rule may be, for example: splicing the intra-domain restoration paths obtained respectively in the two network domains to obtain a plurality of candidate restoration paths, according to each routing device. The configuration determines at least one shortest second restoration path from multiple candidate restoration paths, and the number of the second restoration paths is related to the configuration of each routing device, such as maximum load-balancing. For example: taking the network 20 shown in FIG. 5 as an example, suppose that the border routing devices of the network domain 300 and the network domain 400 include the routing device 21 and the routing device 22, restore the path 1 from the routing device 20 to the routing device 21, and from the routing device 20 to the routing device 21. Path 2 from device 20 to routing device 22, path 3 from routing device 21 to routing device 24, and path 4 from routing device 22 to routing device 24, then two candidate restoration paths can be spliced: path 13 and path 24 , wherein the path 13 is a candidate restoration path passing through the boundary routing device 21 , and the path 24 is a candidate restoration path passing through the boundary routing device 22 . In one case, if the maximum load-balancing=1 of the routing device 20, then the second restoration path finally determined by the management device is the path with the shortest distance between the path 13 and the path 24, if the path 13 and the path 24 are equal cost paths , then, the management device may randomly select one of the paths 13 and 24 as the second restoration path. In another case, if the maximum load-balancing of the routing device 20 is greater than or equal to 2, the second restoration paths finally determined by the management device are the path 13 and the path 24.

It can be seen that with the method 200 provided in this embodiment of the present application, for the first routing device and the third routing device belonging to different network domains, the first routing device obtains and sends the first aggregation information and the second aggregation information to the management device, and the second routing device obtains and sends the first aggregation information and the second aggregation information to the management device. The routing device obtains and sends fourth aggregation information to the management device, where the first aggregation information includes an identification of the second routing device and at least one outbound interface identification of the first routing device, and the second aggregation information includes an identification of the second routing device and the first routing device. The identifier of the third routing device, and the fourth aggregation information includes the identifier of the third routing device and at least one outbound interface identifier of the second routing device; in this way, the management device can be based on the first aggregation information, the second aggregation information, the fourth aggregation information information and the adjacency relationship information in the two LSDBs corresponding to the two network domains, determine the restoration path from the first routing device to the third routing device via the second routing device. In this way, each routing device aggregates the aggregation information from the routing device to other routing devices, and reports the aggregation information to the management device. Since the configuration of each routing device has been considered in the process of actually forwarding the packet, the path restoration process The aggregation information based on the network has also been in line with the configuration of each routing device. Based on the aggregation information, the path restoration across the network domain can make the obtained restoration path and the real forwarding path exactly the same, which is fast and accurate in the network domain and in the cross-network domain scenario. Troubleshooting provides a reliable basis.

It should be noted that the above-mentioned first network domain and second network domain are both standard network domains, that is, the method 200 exemplarily describes a method for restoring a path across standard network domains.

For a network scenario spanning from a standard network domain to a non-standard network domain or from a non-standard network domain to a standard network domain, the management device may also perform path restoration according to the method provided in this embodiment of the present application, which may specifically include: S51, for standard network domains In the network domain, the first restoration path is determined according to the above method 100; S52, for the non-standard network domain, the fourth restoration path is determined according to the path restoration method applicable to the non-standard network domain; S53, according to the preset splicing rule, the first restoration path is determined. The first restoration path and the fourth restoration path are spliced to obtain a fifth restoration path spanning from the standard network domain to the non-standard network domain or from the non-standard network domain to the standard network domain.

Take the non-standard network domain as the stub domain as an example, the first routing device and the second routing device belong to the standard network domain, the second routing device and the third routing device belong to the stub domain, and the restoration from the first routing device to the third routing device is restored. In the process of the path, S52 may specifically include: the management device determines a third restoration path from the second routing device to the third routing device according to a default route, where the default route is sent by the third routing device to the management device. Taking the network 100 shown in FIG. 3 as an example, assuming that the network domain 200 is a stub domain and the network domain 100 is a standard domain, the first restoration path determined by the management device 50 in the network domain 100 includes: path 1 and path 1 3. In the network domain 200, based on the default route sent by the routing device 18 and the default route sent by the routing device 17, the determined third restoration path is: path 4, thereby simply splicing path 3 and path 4 to obtain the second restoration path, ie, path 34 .

It should be noted that, in the above embodiment, the aggregation information sent by the routing device to the management device can be carried in any message that can be identified by the management device. Specific restrictions.

Correspondingly, an embodiment of the present application further provides a first routing device 600, as shown in FIG. 6 . The first routing device 600 includes: a processing unit 601 and a sending unit 602 .

The processing unit 601 is configured to obtain first aggregation information, where the first aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the first routing device, and at least one outgoing interface of the first routing device is used for the first routing device. The routing device sends the packet to the second routing device.

The sending unit 602 is configured to send the first aggregation information to the management device, so that the management device determines the restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency information in the first link state database LSDB , the first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.

In some implementations, the processing unit 601 is specifically configured to: obtain the first aggregation information based on the forwarding table. For example, the processing unit 601 is specifically configured to: determine the outbound interface identifier corresponding to the IP prefix of the second routing device in the forwarding table, and determine the outbound interface identifier corresponding to the IP prefix of the second routing device as the outgoing interface identifier in the first aggregation information At least one outbound interface identifier of the first routing device.

In some other implementations, the processing unit 601 is specifically configured to: obtain the first aggregation information from the locally saved shortest path tree SPT calculation result.

In still other implementations, the second routing device and the third routing device belong to the second network domain, and the processing unit 601 of the first routing device 600 is further configured to obtain second aggregation information, where the second aggregation information includes the second routing The identifier of the device and the identifier of the third routing device; the sending unit 602 is further configured to send the second aggregation information to the management device, so that the management device is based on the first aggregation information, the second aggregation information, and the first LSDB corresponding to the first network domain The adjacency information in the LSDB and the adjacency information in the second LSDB corresponding to the second network domain determine the restoration path from the first routing device to the third routing device via the second routing device.

The first routing device 600 further includes a receiving unit, which is configured to receive a routing message advertised by a third routing device before obtaining the second aggregation information, where the routing message carries the identifier of the third routing device. As an example, the receiving unit may be specifically configured to: receive an LSA packet sent by a third routing device, where the LSA packet carries the identifier of the third routing device through an extended TLV field.

In some implementation manners, the sending unit 602 is specifically configured to: periodically send the first aggregation information to the management device.

In other implementations, the sending unit 602 is specifically configured to: send the first aggregation information to the management device based on the trigger instruction.

It should be noted that the first routing device 600 shown in FIG. 6 may be the first routing device in the example shown in FIG. 2 or FIG. 4 . Therefore, for various specific embodiments of the first routing device 600, please refer to The related introduction of the method 100 corresponding to FIG. 2 and the method 200 corresponding to FIG. 4 is not repeated in this embodiment.

Correspondingly, an embodiment of the present application further provides a management device 700, as shown in FIG. 7 . The management device 700 includes: a receiving unit 701 and a processing unit 702 .

The receiving unit 701 is configured to receive first aggregation information from a first routing device, where the first aggregation information includes an identifier of the second routing device and at least one outbound interface identifier of the first routing device, and at least one outgoing interface identifier of the first routing device The interface is used by the first routing device to send packets to the second routing device.

The processing unit 702 is configured to determine the first restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency information in the first link state database LSDB, where the first LSDB is the first routing device and the second routing device. The LSDB corresponding to the first network domain where the second routing device is located.

In some implementation manners, the receiving unit 701 is further configured to receive third aggregation information from the fourth routing device, where the third aggregation information includes an identifier of the second routing device and at least one outbound interface identifier of the fourth routing device, and the fourth routing device At least one outgoing interface of the device is used by the fourth routing device to send packets to the second routing device; then, the processing unit 702 may be specifically configured to: based on the first aggregation information, the third aggregation information and the adjacency relationship information in the first LSDB , determine the first restoration path, and the first restoration path passes through the fourth routing device.

In this implementation, as an example, the processing unit 702 is specifically configured to: determine the first path from the first routing device to the fourth routing device based on the first aggregation information and the adjacency information in the first LSDB, and the first path in the first LSDB The adjacency relationship information is used to indicate that at least one outgoing interface of the first routing device is connected to the incoming interface of the fourth routing device; based on the third aggregation information and the adjacency relationship information in the first LSDB, determine the route from the fourth routing device to the second routing device. For the second path of the device, the adjacency information in the first LSDB is also used to indicate that at least one outgoing interface of the fourth routing device is connected to the incoming interface of the second routing device; thus, based on the first path and the second path, determine the first path. A restore path.

In some other implementations, the second routing device and the third routing device belong to the second network domain, and the processing unit 702 is further configured to determine a second restoration path from the first routing device to the third routing device, where the second restoration path is the first restoration path. A path from a routing device to a third routing device via the second routing device.

As an example, the receiving unit 701 is further configured to receive the second aggregation information sent by the first routing device, where the second aggregation information includes the identifier of the second routing device and the identifier of the third routing device; then, the processing unit 702 can specifically use In: determining a first restoration path based on the first aggregation information, the second aggregation information and the adjacency relationship information in the first LSDB.

In this example, the receiving unit 701 is further configured to receive fourth aggregation information sent by the second routing device, where the fourth aggregation information includes an identifier of the third routing device and at least one outbound interface identifier of the second routing device. At least one outgoing interface is used for the second routing device to send packets to the third routing device; then, the processing unit 702 may be specifically configured to: according to the fourth aggregation information and the adjacency information in the second LSDB corresponding to the second network domain, A third restoration path from the second routing device to the third routing device is determined; thus, based on the first restoration path and the third restoration path, a second restoration path is determined.

The receiving unit 701 is further configured to receive the identifier of the third routing device sent by the third routing device.

As another example, the processing unit 702 may be specifically configured to: determine the third restoration path from the second routing device to the third routing device according to the default route; thus, determine the second restoration path based on the first restoration path and the third restoration path restore path.

The receiving unit 701 is further configured to receive the default route sent by the third routing device.

It should be noted that the management device 700 shown in FIG. 7 may be the management device in the example shown in FIG. 2 or FIG. 4 . Therefore, for various specific embodiments of the management device 700, reference may be made to the method 100 corresponding to FIG. 2 . As well as the related introduction of the method 200 corresponding to FIG. 4 , details are not repeated in this embodiment.

Correspondingly, an embodiment of the present application further provides a third routing device 800, as shown in FIG. 8 . The third routing device 800 includes: a sending unit 801 .

The sending unit 801 is configured to send a routing message to the first routing device, the first routing device belongs to the first network domain, the third routing device belongs to the second network domain, and the routing message carries the identifier of the third routing device, so that the first routing device belongs to the first network domain, and the third routing device belongs to the second network domain. A routing device obtains and sends second aggregation information to the management device based on the identifier of the third routing device, where the second aggregation information includes the identifier of the third routing device and the identifier of the second routing device, and the second routing device is the first network domain and the second routing device. A border device of the second network domain.

As an example, the sending unit 801 is specifically configured to send an LSA packet to the first routing device, where the LSA packet carries the identifier of the third routing device through an extended TLV field.

The sending unit 801 is further configured to send the identifier of the third routing device to the management device.

It should be noted that the third routing device 800 shown in FIG. 8 may be the third routing device in the example shown in FIG. 4 . Therefore, various specific embodiments of the third routing device 800 can be referred to in FIG. 4 . The related introduction of the method 200 is not repeated in this embodiment.

Referring to FIG. 9 , an embodiment of the present application provides a first routing device 900 . The first routing device 900 may be any node other than the destination routing device in any of the foregoing embodiments, for example, may be the routing device 10, the routing device 11, etc. in the embodiment shown in FIG. 1, or may be the one in FIG. 2 The first routing device in the illustrated embodiment. The first routing device 900 includes at least one processor 901 , a bus system 902 , a memory 903 and at least one transceiver 904 .

The first routing device 900 is a device with a hardware structure, and can be used to implement the functional modules in the first routing device 600 shown in FIG. 6 . For example, those skilled in the art can think that the processing unit 601 in the first routing device 600 shown in FIG. 6 can be implemented by calling the code in the memory 903 by the at least one processor 901, and the first routing device 600 shown in FIG. The sending unit 602 in can be realized by the transceiver 904 .

Optionally, the first routing device 900 may also be used to implement the function of the first routing device in any of the foregoing embodiments.

Optionally, the above-mentioned processor 901 may be a general-purpose central processing unit (central processing unit, CPU), network processor (network processor, NP), microprocessor, application-specific integrated circuit (application-specific integrated circuit, ASIC) , or one or more integrated circuits used to control the execution of the program of this application.

The bus system 902 described above may include a path to transfer information between the above described components.

The above transceiver 904 is used to communicate with other devices or communication networks.

The above-mentioned memory 903 can be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or other types of storage devices that can store information and instructions. Types of dynamic storage devices, which can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical storage, CD-ROM storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by Any other medium accessed by the computer, but not limited to this. The memory can exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.

Wherein, the memory 903 is used for storing the application program code for executing the solution of the present application, and the execution is controlled by the processor 901 . The processor 901 is used to execute the application program code stored in the memory 903, so as to realize the functions in the method of this patent.

In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 9 .

In a specific implementation, as an embodiment, the first routing device 900 may include multiple processors, for example, the processor 901 and the processor 907 in FIG. 9 . Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

Referring to FIG. 10 , an embodiment of the present application provides a management device 1000 . The management device 1000 may be the management device in any of the foregoing embodiments, for example, may be the management device 50 in the embodiment shown in FIG. 1 or FIG. 3 , or may be the management device 50 in the embodiment shown in FIG. 2 or FIG. 4 . Manage devices. The management device 1000 includes at least one processor 1001 , a bus system 1002 , a memory 1003 and at least one transceiver 1004 .

The management device 1000 is a device with a hardware structure, and can be used to implement the functional modules in the management device 700 described in FIG. 7 . For example, those skilled in the art can think that the processing unit 702 in the management device 700 shown in FIG. 7 can be implemented by calling the code in the memory 1003 by the at least one processor 1001, and the receiving unit in the management device 700 shown in FIG. 7 can be implemented 701 can be implemented by the transceiver 1004 .

Optionally, the management device 1000 may also be used to implement the functions of the management device in any of the foregoing embodiments.

Optionally, the above-mentioned processor 1001 may be a general-purpose central processing unit (central processing unit, CPU), network processor (network processor, NP), microprocessor, application-specific integrated circuit (application-specific integrated circuit, ASIC) , or one or more integrated circuits used to control the execution of the program of this application.

The bus system 1002 described above may include a path to transfer information between the above described components.

The above transceiver 1004 is used to communicate with other devices or communication networks.

The above-mentioned memory 1003 can be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or other types of storage devices that can store information and instructions. Types of dynamic storage devices, which can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical storage, CD-ROM storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by Any other medium accessed by the computer, but not limited to this. The memory can exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.

Wherein, the memory 1003 is used for storing the application program code for executing the solution of the present application, and the execution is controlled by the processor 1001 . The processor 1001 is configured to execute the application program code stored in the memory 1003, thereby realizing the functions in the method of the present patent.

In a specific implementation, as an embodiment, the processor 1001 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 10 .

In a specific implementation, as an embodiment, the management device 1000 may include multiple processors, such as the processor 1001 and the processor 1007 in FIG. 10 . Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

Referring to FIG. 11 , an embodiment of the present application provides a third routing device 1100 . The third routing device 1100 may be any node in any of the foregoing embodiments, for example, may be the routing device 17, the routing device 18, etc. in the embodiment shown in FIG. 3, or may be the embodiment shown in FIG. 4 . the third routing device. The third routing device 1100 includes at least one processor 1101 , a bus system 1102 , a memory 1103 and at least one transceiver 1104 .

The third routing device 1100 is a device with a hardware structure, and can be used to implement the functional modules in the third routing device 800 shown in FIG. 8 . For example, those skilled in the art can think that the sending unit 801 in the third routing device 800 shown in FIG. 8 can be implemented by the transceiver 1104 .

Optionally, the third routing device 1100 may also be used to implement the functions of the third routing device in any of the foregoing embodiments.

Optionally, the above-mentioned processor 1101 may be a general-purpose central processing unit (central processing unit, CPU), network processor (network processor, NP), microprocessor, application-specific integrated circuit (application-specific integrated circuit, ASIC) , or one or more integrated circuits used to control the execution of the program of this application.

The bus system 1102 described above may include a path to transfer information between the above described components.

The above transceiver 1104 is used to communicate with other devices or communication networks.

The above-mentioned memory 1103 can be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (random access memory, RAM) or other types of storage devices that can store information and instructions. Types of dynamic storage devices, which can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical storage, CD-ROM storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being accessed by Any other medium accessed by the computer, but not limited to this. The memory can exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.

Wherein, the memory 1103 is used for storing the application program code for executing the solution of the present application, and the execution is controlled by the processor 1101 . The processor 1101 is used for executing the application program code stored in the memory 1103, so as to realize the functions in the method of the present patent.

In a specific implementation, as an embodiment, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 11 .

In a specific implementation, as an embodiment, the third routing device 1100 may include multiple processors, for example, the processor 1101 and the processor 1107 in FIG. 11 . Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

Referring to FIG. 12 , an embodiment of the present application provides a network system 1200 , where the network system 1200 includes: a first routing device 1201 , a management device 1202 , and a third routing device 1203 . The first routing device 1201 may specifically be the first routing device 600 shown in FIG. 6 or the first routing device 900 shown in FIG. 9 ; the management device 1202 may specifically be the management device 700 shown in FIG. 7 or the first routing device 900 shown in FIG. 10 . The third routing device 1203 may specifically be the third device 800 shown in FIG. 8 or the third routing device 1100 shown in FIG. 11 .

Optionally, the first routing device 1201 may be the first routing device in the embodiment shown in FIG. 4 , the third routing device 1202 may be the third routing device in the embodiment shown in FIG. 4 , and the management device may be FIG. 4 Management device in the illustrated embodiment.

In addition, an embodiment of the present application also provides a computer-readable storage medium, where program codes or instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer can execute the implementation shown in FIG. 2 or FIG. 4 above. The method in any of the implementations in the example.

In addition, the embodiments of the present application also provide a computer program product, which, when running on a computer, causes the computer to execute any one of the implementation manners of the foregoing method 100 , or causes the computer to execute any one of the foregoing methods 200 . method of implementation.

The "first" in the names such as "first restoration path" and "first aggregation information" mentioned in the embodiments of the present application are only used for name identification, and do not represent the first in order. The same rule applies to "second" etc.

It should be understood that "determining B based on A" mentioned in the embodiments of the present application does not mean that B is only determined according to A, and B can also be determined according to A and/or other information.

From the description of the above embodiments, those skilled in the art can clearly understand that all or part of the steps in the methods of the above embodiments can be implemented by means of software plus a general hardware platform. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product, and the computer software product can be stored in a storage medium, such as read-only memory (English: read-only memory, ROM)/RAM, magnetic disk, An optical disc, etc., includes several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the methods described in various embodiments or some parts of the embodiments of the present application.

Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiments and device embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and reference may be made to some descriptions of the method embodiments for related parts. The device and system embodiments described above are only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in One place, or it can be distributed over multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment. Those of ordinary skill in the art can understand and implement it without creative effort.

The above descriptions are only preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the present application, several improvements and modifications can also be made, and these improvements and modifications should also be regarded as the protection scope of the present application.

Claims (44)

1. A method for path restoration, comprising:

   The first routing device obtains first aggregation information, where the first aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the first routing device, and the at least one outgoing interface of the first routing device is used for sending, by the first routing device, a packet to the second routing device;

   The first routing device sends the first aggregation information to a management device, so that the management device determines the first routing device based on the first aggregation information and the adjacency information in the first link state database LSDB The restoration path to the second routing device, where the first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.
2. The method according to claim 1, wherein obtaining the first aggregation information by the first routing device comprises:

   The first routing device obtains the first aggregation information based on the forwarding table.
3. The method according to claim 2, wherein the first routing device obtains the first aggregation information based on a forwarding table, comprising:

   The first routing device determines, in the forwarding table, an outbound interface identifier corresponding to the Internet Protocol IP prefix of the second routing device;

   The first routing device determines an outgoing interface identifier corresponding to the IP prefix of the second routing device as at least one outgoing interface identifier of the first routing device in the first aggregation information.
4. The method according to claim 1, wherein obtaining the first aggregation information by the first routing device comprises:

   The first routing device obtains the first aggregation information from the locally stored shortest path tree SPT calculation result.
5. The method according to any one of claims 1-4, wherein the second routing device and the third routing device belong to a second network domain, and the method further comprises:

   obtaining, by the first routing device, second aggregation information, where the second aggregation information includes an identifier of the second routing device and an identifier of the third routing device;

   The first routing device sends the second aggregation information to the management device, so that the management device based on the first aggregation information, the second aggregation information, the first network domain corresponding to the first network domain. The adjacency relationship information in an LSDB and the adjacency relationship information in the second LSDB corresponding to the second network domain determine a restoration path from the first routing device to the third routing device via the second routing device.
6. The method according to claim 5, wherein before the first routing device obtains the second aggregation information, the method further comprises:

   The first routing device receives a routing message advertised by the third routing device, where the routing message carries the identifier of the third routing device.
7. The method according to claim 6, wherein the receiving, by the first routing device, the routing message advertised by the third routing device comprises:

   The first routing device receives the link state advertisement LSA packet sent by the third routing device, and the LSA packet carries the identifier of the third routing device through an extended length type value TLV field.
8. The method according to any one of claims 1-7, wherein the sending, by the first routing device, the first aggregation information to the management device comprises:

   The first routing device periodically sends the first aggregation information to the management device.
9. The method according to any one of claims 1-7, wherein the sending, by the first routing device, the first aggregation information to the management device comprises:

   The first routing device sends the first aggregation information to the management device based on the trigger instruction.
10. A method for route restoration, comprising:

    The management device receives the first aggregation information from the first routing device, where the first aggregation information includes the identifier of the second routing device and the identifier of at least one outgoing interface of the first routing device, and the at least one outgoing interface of the first routing device the interface is used by the first routing device to send a packet to the second routing device;

    The management device determines the first restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency information in the first link state database LSDB, and the first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.
11. The method of claim 10, wherein the method further comprises:

    The management device receives third aggregation information from the fourth routing device, where the third aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the fourth routing device, and at least one outgoing interface identifier of the fourth routing device. the interface is used for the fourth routing device to send a packet to the second routing device;

    The management device determines, based on the first aggregation information and the adjacency information in the first LSDB, the first restoration path from the first routing device to the second routing device, including:

    The management device determines the first restoration path based on the first aggregation information, the third aggregation information, and the adjacency relationship information in the first LSDB, and the first restoration path passes through the fourth route equipment.
12. The method according to claim 11, wherein the management device determines the first restoration path based on the first aggregation information, the third aggregation information and the adjacency relationship information in the first LSDB ,include:

    The management device determines the first path from the first routing device to the fourth routing device based on the first aggregation information and the adjacency relationship information in the first LSDB, and the adjacency in the first LSDB The relationship information is used to indicate that at least one outgoing interface of the first routing device is connected to the incoming interface of the fourth routing device;

    The management device determines the second path from the fourth routing device to the second routing device based on the third aggregation information and the adjacency relationship information in the first LSDB, and the adjacency in the first LSDB The relationship information is further used to indicate that at least one outgoing interface of the fourth routing device is connected to the incoming interface of the second routing device;

    The management device determines the first restoration path based on the first path and the second path.
13. The method according to any one of claims 10-12, wherein the second routing device and the third routing device belong to a second network domain, and the method further comprises:

    The management device determines a second restoration path from the first routing device to the third routing device, where the second restoration path is for the first routing device to reach the third route through the second routing device The path to the device.
14. The method of claim 13, wherein the method further comprises:

    receiving, by the management device, second aggregation information sent by the first routing device, where the second aggregation information includes an identifier of the second routing device and an identifier of the third routing device;

    The management device determines, based on the first aggregation information and the adjacency information in the first link state database LSDB, the first restoration path from the first routing device to the second routing device, including:

    The management device determines the first restoration path based on the first aggregation information, the second aggregation information and the adjacency relationship information in the first LSDB.
15. The method according to claim 13 or 14, wherein the method further comprises:

    The management device receives fourth aggregation information sent by the second routing device, where the fourth aggregation information includes an identifier of the third routing device and at least one outbound interface identifier of the second routing device, and the first At least one outgoing interface of the second routing device is used for the second routing device to send packets to the third routing device;

    The management device determines the second restoration path from the first routing device to the third routing device, including:

    The management device determines a third restoration path from the second routing device to the third routing device according to the fourth aggregation information and the adjacency information in the second LSDB corresponding to the second network domain;

    The management device determines the second restoration path based on the first restoration path and the third restoration path.
16. The method according to any one of claims 13-15, wherein the method further comprises:

    The management device receives the identifier of the third routing device sent by the third routing device.
17. The method according to claim 13, wherein the management device determines the second restoration path from the first routing device to the third routing device, comprising:

    The management device determines, according to the default route, a third restoration path from the second routing device to the third routing device;

    The management device determines the second restoration path based on the first restoration path and the third restoration path.
18. The method of claim 17, wherein the method further comprises:

    The management device receives the default route sent by the third routing device.
19. A method for route restoration, comprising:

    The third routing device sends a routing message to the first routing device, the first routing device belongs to the first network domain, the third routing device belongs to the second network domain, and the routing message carries the information of the third routing device. identification, so that the first routing device obtains and sends second aggregation information to the management device based on the identification of the third routing device, where the second aggregation information includes the identification of the third routing device and the identification of the second routing device. identification, the second routing device is a border device of the first network domain and the second network domain.
20. The method according to claim 19, wherein the third routing device sends a routing message to the first routing device, comprising:

    The third routing device sends a link state advertisement LSA packet to the first routing device, where the LSA packet carries the identifier of the third routing device through an extended length type value TLV field.
21. The method according to claim 19 or 20, wherein the method further comprises:

    The third routing device sends the identification of the third routing device to the management device.
22. A routing device, characterized in that it includes:

    The processing unit is configured to obtain first aggregation information, where the first aggregation information includes the identifier of the second routing device and the identifier of at least one outgoing interface of the first routing device, and the at least one outgoing interface of the first routing device is used for sending a packet from the first routing device to the second routing device;

    A sending unit, configured to send the first aggregation information to a management device, so that the management device determines, based on the first aggregation information and the adjacency information in the first link state database LSDB, that the first routing device to The restoration path of the second routing device, and the first LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.
23. The routing device according to claim 22, wherein the processing unit is specifically configured to:

    The first aggregation information is obtained based on the forwarding table.
24. The routing device according to claim 23, wherein the processing unit is specifically configured to:

    determining, in the forwarding table, an outgoing interface identifier corresponding to the Internet Protocol IP prefix of the second routing device;

    The outgoing interface identifier corresponding to the IP prefix of the second routing device is determined as at least one outgoing interface identifier of the first routing device in the first aggregation information.
25. The routing device according to claim 22, wherein the processing unit is specifically configured to:

    The first aggregation information is obtained from the locally stored shortest path tree SPT calculation result.
26. The routing device according to any one of claims 22-25, wherein the second routing device and the third routing device belong to a second network domain, and the processing unit is further configured to:

    obtaining second aggregation information, where the second aggregation information includes an identifier of the second routing device and an identifier of the third routing device;

    The sending unit is also used for:

    Send the second aggregation information to the management device, so that the management device is based on the first aggregation information, the second aggregation information, and the adjacency relationship in the first LSDB corresponding to the first network domain information and the adjacency relationship information in the second LSDB corresponding to the second network domain to determine the restoration path from the first routing device to the third routing device via the second routing device.
27. The routing device according to claim 26, wherein the routing device further comprises:

    A receiving unit, configured to receive, before obtaining the second aggregation information, a routing message advertised by the third routing device, where the routing message carries the identifier of the third routing device.
28. The routing device according to claim 27, wherein the receiving unit is specifically configured to:

    Receive a link state advertisement LSA packet sent by the third routing device, where the LSA packet carries the identifier of the third routing device through an extended length type value TLV field.
29. The routing device according to any one of claims 22-28, wherein the sending unit is specifically configured to:

    The first aggregation information is periodically sent to the management device.
30. The routing device according to any one of claims 22-28, wherein the sending unit is specifically configured to:

    Based on the trigger instruction, the first aggregation information is sent to the management device.
31. A management device, characterized in that it includes:

    A receiving unit, configured to receive first aggregation information from a first routing device, where the first aggregation information includes an identifier of the second routing device and at least one outgoing interface identifier of the first routing device, and the first routing device's identifier at least one outbound interface is used for the first routing device to send packets to the second routing device;

    a processing unit, configured to determine a first restoration path from the first routing device to the second routing device based on the first aggregation information and the adjacency relationship information in the first link state database LSDB, the first The LSDB is the LSDB corresponding to the first network domain where the first routing device and the second routing device are located.
32. The management device according to claim 31, wherein the receiving unit is further configured to:

    Receive third aggregation information from the fourth routing device, where the third aggregation information includes the identifier of the second routing device and the identifier of at least one outgoing interface of the fourth routing device, and the at least one outgoing interface of the fourth routing device is used for sending a packet from the fourth routing device to the second routing device;

    The processing unit is specifically used for:

    Based on the first aggregation information, the third aggregation information, and the adjacency relationship information in the first LSDB, the first restoration path is determined, and the first restoration path passes through the fourth routing device.
33. The management device according to claim 32, wherein the processing unit is specifically configured to:

    A first path from the first routing device to the fourth routing device is determined based on the first aggregation information and the adjacency information in the first LSDB, where the adjacency information in the first LSDB is used for Instructing at least one outgoing interface of the first routing device to be connected to the incoming interface of the fourth routing device;

    A second path from the fourth routing device to the second routing device is determined based on the third aggregation information and the adjacency relationship information in the first LSDB, and the adjacency relationship information in the first LSDB is also used instructing at least one outgoing interface of the fourth routing device to be connected to the incoming interface of the second routing device;

    The first restoration path is determined based on the first path and the second path.
34. The management device according to any one of claims 31-33, wherein the second routing device and the third routing device belong to the second network domain, and the square processing unit is further configured to:

    A second restoration path from the first routing device to the third routing device is determined, where the second restoration path is a path from the first routing device to the third routing device via the second routing device.
35. The management device according to claim 34, wherein the receiving unit is further configured to:

    receiving second aggregation information sent by the first routing device, where the second aggregation information includes an identifier of the second routing device and an identifier of the third routing device;

    The processing unit is specifically used for:

    The first restoration path is determined based on the first aggregation information, the second aggregation information, and the adjacency relationship information in the first LSDB.
36. The management device according to claim 34 or 35, wherein the receiving unit is further configured to:

    Receive fourth aggregation information sent by the second routing device, where the fourth aggregation information includes an identifier of the third routing device and at least one outbound interface identifier of the second routing device, and an identifier of the second routing device. at least one outgoing interface is used for the second routing device to send packets to the third routing device;

    The processing unit is specifically used for:

    The management device determines a third restoration path from the second routing device to the third routing device according to the fourth aggregation information and the adjacency information in the second LSDB corresponding to the second network domain;

    The management device determines the second restoration path based on the first restoration path and the third restoration path.
37. The management device according to any one of claims 34-36, wherein the receiving unit is further configured to:

    The identifier of the third routing device sent by the third routing device is received.
38. The management device according to claim 34, wherein the processing unit is specifically configured to:

    determining a third restoration path from the second routing device to the third routing device according to the default route;

    The second restoration path is determined based on the first restoration path and the third restoration path.
39. The management device according to claim 38, wherein the receiving unit is further configured to:

    The default route sent by the third routing device is received.
40. A routing device, characterized in that it includes:

    a sending unit, configured to send a routing message to a first routing device, where the first routing device belongs to the first network domain, the third routing device belongs to the second network domain, and the routing message carries the third routing device so that the first routing device obtains and sends the second aggregation information to the management device based on the identification of the third routing device, and the second aggregation information includes the identification of the third routing device and the second routing device. and the second routing device is a border device of the first network domain and the second network domain.
41. The routing device according to claim 40, wherein the sending unit is specifically configured to:

    Send a link state advertisement LSA packet to the first routing device, where the LSA packet carries the identifier of the third routing device through an extended length type value TLV field.
42. The routing device according to claim 40 or 41, wherein the sending unit is further configured to:

    Send the identification of the third routing device to the management device.
43. A network system, characterized in that, the network system includes the routing device described in claims 22 to 30, the management device described in claims 31 to 39, and the routing device described in claims 40 to 42.
44. A computer-readable storage medium, characterized in that, program codes or instructions are stored in the computer-readable storage medium, and when the program codes or instructions are run on a computer, the computer is made to execute the above claims 1- The method of any one of 21.

Images