Information processing method and device

Abstract

The embodiment of the invention discloses an information processing method, which is applied to first network equipment. A first network device can determine that a first detail route sent by a second network device to the first network device is unavailable and generate a first message, the first message comprises a route prefix of the first detail route, next hop information and a route prefix of an aggregation route, and the aggregation route corresponds to the first detail route and a second detail route. The second detail route is available. The next hop information indicates a port on the first network device for communicating with the third network device. After the first network device generates the first message, the first message can be sent to the third network device, so that the third network device determines that the first detail route corresponding to the aggregation route is unavailable, and correspondingly, the third network device can execute corresponding processing measures. Therefore, the traffic matched with the first detail route is prevented from being forwarded to the first network equipment, and traffic interruption is avoided.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to an information processing method and device. Background Art

[0002] Routes can be transferred between network devices. For example, routes can be transferred between network devices through the Border Gateway Protocol (BGP). BGP is an external gateway protocol that can be used to select the best route and control the propagation of routes between network domains such as autonomous systems (AS). When BGP runs within the same network domain, it is called the Internal Border Gateway Protocol (IBGP). When BGP runs between different network domains, it is called the External Border Gateway Protocol (EBGP).

[0003] In order to reduce the number of routes maintained by network devices, detailed routes can be aggregated to obtain aggregated routes. Accordingly, when publishing routes, network devices can only publish aggregated routes and no longer publish detailed routes. However, when using this method to guide traffic forwarding based on aggregated routes, there will be traffic interruption.

[0004] Therefore, a solution is urgently needed to solve the above problems. Summary of the invention

[0005] The embodiments of the present application provide an information processing method and apparatus, which can avoid traffic interruption in a scenario where a network device only publishes aggregate routes and no longer publishes detailed routes.

[0006] In a first aspect, an embodiment of the present application provides an information processing method, which can be applied to a first network device. In an example, the first network device can determine that a first detailed route sent by a second network device to the first network device is unavailable. After the first network device determines that the first detailed route is unavailable, it can generate a first message, the first message including a route prefix of the first detailed route, next hop information, and a route prefix of an aggregate route, the aggregate route corresponds to the first detailed route and the second detailed route, in other words, the network segment corresponding to the aggregate route includes the network segment corresponding to the first detailed route and the network segment corresponding to the second detailed route. The second detailed route is available. The next hop information indicates the first network device, specifically, the next hop information indicates a port on the first network device for communicating with a third network device. After the first network device generates the first message, it can send the first message to the third network device, so that the third network device determines that the first detailed route corresponding to the aggregate route is unavailable, and accordingly, the third network device can perform corresponding processing measures to prevent the traffic matching the first detailed route from being forwarded to the first network device, thereby avoiding traffic interruption. It can be seen that by using this solution, traffic interruption can be avoided in a scenario where the network device only publishes aggregate routes and no longer publishes detailed routes.

[0007] In one possible implementation, before determining that the first detailed route is unavailable, the first network device may also send the aggregate route to the third network device, and not send the first detailed route and the second detailed route to the third network device, so as to reduce the number of routing table entries maintained by the third network device.

[0008] In a possible implementation, the first network device may determine that the first detailed route is unavailable when the second network device fails or the link between the second network device and the first network device fails. The first detailed route is unavailable, which can be understood as the first detailed route cannot be used to guide traffic forwarding. That is, the first network device may determine that the first detailed route cannot be used to guide traffic forwarding when the second network device fails or the link between the second network device and the first network device fails. Further, the first network device may send a first message to the third network device to avoid traffic interruption.

[0009] In one possible implementation, the first detailed route is unavailable, which can be understood as the first detailed route cannot be used to guide traffic forwarding. Specifically, it can be understood that the first detailed route cannot guide the forwarding of traffic from the first network device to the route prefix of the first detailed route. In this scenario, if traffic whose destination address matches the route prefix of the first detailed route is sent to the first network device, the traffic will be interrupted at the first network device. Therefore, the first network device sends the first message to the third network device, so that the third network device determines that the first detailed route corresponding to the aggregate route is unavailable. Accordingly, the third network device can perform corresponding processing measures to avoid the traffic matching the first detailed route from being forwarded to the first network device, thereby avoiding traffic interruption.

[0010] In a possible implementation, the first message may be a route announcement message. In this case, the first network device may send the route prefix, next hop information, and route prefix of the aforementioned first detailed route to the third network device through the route announcement message, so that the third network device determines that the first detailed route corresponding to the aggregated route is unavailable. Accordingly, the third network device may perform corresponding processing measures to prevent the traffic matching the first detailed route from being forwarded to the first network device, thereby avoiding traffic interruption.

[0011] In a possible implementation, the route advertisement message includes an extended community attribute, and the extended community attribute includes a route prefix of the aggregate route and the next hop information. The third network device may parse the extended community attribute to obtain the route prefix of the aggregate route and the next hop information. In a possible implementation, the extended community attribute is a BGP path attribute. The third network device may parse the BGP path attribute to obtain the route prefix of the aggregate route and the next hop information.

[0012] In a possible implementation, the type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix and the next hop information of the aggregated route. In this way, the third network device can determine that the content carried by the BGP path attribute is the route prefix and the next hop information of the aggregated route based on the type code field of the BGP path attribute, and thus parse the BGP path attribute field to obtain the route prefix and the next hop information of the aggregated route.

[0013] In a possible implementation, the first network device is a network device that generates the aggregate route. That is, when the device that generates the aggregate route senses that the first detailed route is unavailable, it sends a first message to the third network device, so that the third network device determines that the first detailed route corresponding to the aggregate route is unavailable. Accordingly, the third network device can perform corresponding processing measures to prevent traffic matching the first detailed route from being forwarded to the first network device, thereby avoiding traffic interruption.

[0014] In a possible implementation, the first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer. With this solution, in a scenario where the convergence layer facing the core layer device publishes an aggregate route to the core layer device, but no longer publishes the first detailed route and the second detailed route corresponding to the aggregate route, even if the first detailed route sent by the convergence layer to the access layer device or the access layer device is unavailable, it will not cause traffic interruption.

[0015] In a second aspect, an embodiment of the present application provides an information processing method, which can be applied to a third network device. In an example, the third network device can receive a first message sent by the first network device, wherein the first message includes a route prefix of a first detailed route, next hop information, and a route prefix of an aggregate route. The aggregate route corresponds to the first detailed route and the second detailed route. In other words, the network segment corresponding to the aggregate route includes the network segment corresponding to the first detailed route and the network segment corresponding to the second detailed route. The second detailed route is available. The next hop information indicates the first network device, and specifically, the next hop information indicates a port on the first network device for communicating with the third network device. After receiving the first message, the third network device can locally search for a route table item corresponding to the route prefix of the aggregate route. If the next hop information included in the first route table item obtained indicates the first port and the second port, and the second port is a port on a fourth network device for communicating with the third network device, then a second route table item corresponding to the route prefix of the first detailed route is generated, wherein the next hop information included in the second route table item indicates the second port. In this way, when the third network device receives traffic matching the first detailed route, it can forward the traffic to the fourth network device based on the second routing table entry, rather than forwarding the traffic to the first network device based on the aggregate route, thereby avoiding traffic interruption. It can be seen that, using this solution, traffic interruption can be avoided in a scenario where the network device only publishes aggregate routes and no longer publishes detailed routes.

[0016] In a possible implementation, if the next hop information included in the first routing table entry only indicates the first port. For example, the next hop information in the first routing table entry only includes the port address of the first port. It means that when the third network device forwards the traffic matching the routing prefix corresponding to the aforementioned first detailed route, it can only be forwarded through the first network device. In this case, once the third network device receives the traffic matching the routing prefix corresponding to the first detailed route, it will inevitably cause traffic interruption. In this case, the third network device can generate a second message based on the first message, the second message includes the routing prefix of the first detailed route, the next hop information indicating the third port, and the routing prefix of the aggregate route, the third port is the port in the third network device used to communicate with the fifth network device, and send the second message to the fifth network device. Correspondingly, after receiving the second message, the fifth network device can locally search for the routing table entry corresponding to the routing prefix of the aggregate route. If the next hop information included in the third routing table entry obtained by searching indicates the third port and the fourth port, the fourth port is the port on the sixth network device used to communicate with the fifth network device. This means that when the fifth network device forwards traffic that matches the routing prefix corresponding to the aforementioned first detailed route, it can be forwarded through the third network device or the sixth network device. In this case, in order to avoid traffic interruption caused by the fifth network device forwarding the traffic to the third network device, the fifth network device can generate a fourth routing table entry corresponding to the routing prefix of the first detailed route, wherein the next hop information included in the fourth routing table entry indicates the fourth port. In this way, when the fifth network device receives traffic that matches the routing prefix corresponding to the aforementioned first detailed route, it can forward the traffic to the sixth network device based on the fourth routing table entry, thereby avoiding traffic interruption.

[0017] In a possible implementation manner, the first specific route is unavailable, including: the first specific route cannot guide the forwarding of traffic from the first network device to the route prefix of the first specific route.

[0018] In a possible implementation manner, the first message includes a routing advertisement message.

[0019] In a possible implementation manner, the route advertisement message includes an extended community attribute, and the extended community attribute includes a route prefix of the aggregate route and the next hop information.

[0020] In a possible implementation manner, the extended community attribute is a Border Gateway Protocol (BGP) path attribute.

[0021] In a possible implementation manner, the type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix of the aggregate route and the next hop information.

[0022] In a possible implementation manner, the first network device is a network device that generates the aggregate route.

[0023] In a possible implementation, the first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

[0024] In a third aspect, an embodiment of the present application provides an information processing device, which is applied to a first network device, and the device includes: a processing unit, which is used to determine that a first detailed route sent by a second network device to the first network device is unavailable, and generate a first message, the first message including a routing prefix, next hop information, and a routing prefix of an aggregate route of the first detailed route, the aggregate route corresponding to the first detailed route and the second detailed route, the second detailed route is available, and the next hop information indicates a first port, which is a port on the first network device for communicating with a third network device; a sending unit, which is used to send the first message to the third network device.

[0025] In a possible implementation manner, the sending unit is further configured to: before determining that the first specific route is unavailable, send the aggregate route to the third network device, and not send the first specific route and the second specific route to the third network device.

[0026] In a possible implementation manner, determining that the first detailed route sent by the second network device to the first network device is unavailable includes: determining that the second network device fails, or determining that a link between the second network device and the first network device fails.

[0027] In a possible implementation manner, the first specific route is unavailable, including: the first specific route cannot guide the forwarding of traffic from the first network device to the route prefix of the first specific route.

[0028] In a possible implementation manner, the first message includes a routing advertisement message.

[0029] In a possible implementation manner, the route advertisement message includes an extended community attribute, and the extended community attribute includes a route prefix of the aggregate route and the next hop information.

[0030] In a possible implementation manner, the extended community attribute is a Border Gateway Protocol (BGP) path attribute.

[0031] In a possible implementation manner, the type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix of the aggregate route and the next hop information.

[0032] In a possible implementation manner, the first network device is a network device that generates the aggregate route.

[0033] In a possible implementation, the first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

[0034] In a fourth aspect, an embodiment of the present application provides an information processing device, which is applied to a third network device, and the device includes: a receiving unit, which is used to receive a first message sent by a first network device, the first message including a routing prefix, next hop information, and a routing prefix of an aggregated route of a first detailed route, the aggregated route corresponding to the first detailed route and the second detailed route, the first detailed route is unavailable, the first detailed route is a route sent by the second network device to the first network device, the second detailed route is available, and the next hop information indicates a first port, which is a port on the first network device for communicating with the third network device; a processing unit, which is used to locally search for a routing table entry corresponding to the routing prefix of the aggregated route, and if the next hop information included in the first routing table entry obtained indicates the first port and the second port, and the second port is a port on the fourth network device for communicating with the third network device, then generate a second routing table entry corresponding to the routing prefix of the first detailed route, wherein the next hop information included in the second routing table entry indicates the second port.

[0035] In a possible implementation, the processing unit is also used to: if the next hop information included in the first routing table entry only indicates the first port, generate a second message based on the first message, the second message including the routing prefix of the first detailed route, the next hop information indicating the third port, and the routing prefix of the aggregate route, the third port being the port in the third network device for communicating with the fifth network device; the device also includes a sending unit for notifying the fifth network device of the second message.

[0036] In a possible implementation manner, the first specific route is unavailable, including: the first specific route cannot guide the forwarding of traffic from the first network device to the route prefix of the first specific route.

[0037] In a possible implementation manner, the first message includes a routing advertisement message.

[0038] In a possible implementation manner, the route advertisement message includes an extended community attribute, and the extended community attribute includes a route prefix of the aggregate route and the next hop information.

[0039] In a possible implementation manner, the extended community attribute is a Border Gateway Protocol (BGP) path attribute.

[0040] In a possible implementation manner, the type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix of the aggregate route and the next hop information.

[0041] In a possible implementation manner, the first network device is a network device that generates the aggregate route.

[0042] In a possible implementation, the first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

[0043] In a fifth aspect, an embodiment of the present application provides a device. The device includes a processor and a memory. The memory is used to store instructions or computer programs. The processor is used to execute the instructions or computer programs in the memory, execute any one of the methods described in the first aspect above, or execute any one of the methods described in the second aspect above.

[0044] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, which, when executed on a computer, enables the computer to execute any of the methods described in the first aspect above, or execute any of the methods described in the second aspect above.

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

[0046] In an eighth aspect, an embodiment of the present application provides a communication system, which includes a first network device that executes the method described in any one of the first aspects above, and a third network device that executes the method described in any one of the second aspects above. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0048] Figure 1 A schematic diagram of a network architecture provided for an embodiment of the present application;

[0049] Figure 2a A schematic diagram of a routing table entry of each network device provided in an embodiment of the present application;

[0050] Figure 2b A schematic diagram of another routing table entry of each network device provided in an embodiment of the present application;

[0051] Figure 3 A signaling interaction diagram of an information processing method provided in an embodiment of the present application;

[0052] Figure 4 A schematic diagram of the structure of a routing advertisement message provided in an embodiment of the present application;

[0053] Figure 5a A schematic diagram of a fault scenario provided in an embodiment of the present application;

[0054] Figure 5b A schematic diagram of another fault scenario provided in an embodiment of the present application;

[0055] Figure 6 A schematic diagram of the structure of an information processing device provided in an embodiment of the present application;

[0056] Figure 7 A schematic diagram of the structure of another information processing device provided in an embodiment of the present application;

[0057] Figure 8 A schematic diagram of the structure of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The embodiments of the present application provide an information notification method, an information processing method and an apparatus, which can avoid traffic interruption in a scenario where a network device only publishes aggregate routes and no longer publishes detailed routes.

[0059] For ease of understanding, possible application scenarios of the embodiments of the present application are first introduced.

[0060] See also Figure 1 , which is a schematic diagram of a network architecture provided in an embodiment of the present application.

[0061] Figure 1 The network structure shown may be, but is not limited to, a data center network architecture. Figure 1 The network architecture shown includes an access layer, a convergence layer, and a core layer. The access layer includes network devices 1-1, 1-2, 1-3, and 1-4. The convergence layer includes network devices 2-1, 2-2, 2-3, 2-4, 2-5, 2-6, 2-7, and 2-8. The core layer includes network devices 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7, and 3-8.

[0062] For the connection relationship between various network devices, please refer to Figure 1 , which will not be described in detail here.

[0063] Server S1 is dual-homed to network devices 1-1 and 1-2, and server S2 is dual-homed to network devices 1-3 and 1-4. S1 corresponds to two host routes, and the route prefixes of these two host routes are 10.1.1.1 / 32 and 10.1.1.2 / 32 respectively. S2 corresponds to two host routes, and the route prefixes of these two host routes are 10.1.2.1 / 32 and 10.1.2.2 / 32 respectively.

[0064] Network device 1-1 and network device 1-2 both have corresponding network segment routes, and the host route corresponding to S1 is within the network segment of the network segment routes corresponding to network device 1-1 and network device 1-2. In an example, the route prefixes of the network segment routes corresponding to network device 1-1 and network device 1-2 are both 10.1.1.0 / 24. The route prefix of the host route within the network segment corresponding to 10.1.1.0 / 24 can be: 10.1.1.* / 32, where the value of "*" can be between 1 and 254.

[0065] Network devices 1-3 and 1-4 both have corresponding network segment routes, and the host route corresponding to S2 is within the network segment of the network segment routes corresponding to network devices 1-3 and 1-4. In an example, the route prefixes of the network segment routes corresponding to network devices 1-3 and 1-4 are both 10.1.2.0 / 24. The route prefix of the host route within the network segment corresponding to 10.1.2.0 / 24 can be: 10.1.2.X / 32, where the value of "X" can be between 1 and 254.

[0066] S1 may advertise its host route to network devices 1-1 and 1-2, and S2 may advertise its host route to network devices 1-3 and 1-4.

[0067] Correspondingly, the access layer device 1-1 can announce its own network segment routing and the routing prefix of the host routing of S1 to the aggregation layer devices 2-1 and 2-3; the access layer device 1-2 can announce its own network segment routing and the routing prefix of the host routing of S1 to the aggregation layer devices 2-1 and 2-3; the access layer device 1-3 can announce its own network segment routing and the routing prefix of the host routing of S1 to the aggregation layer devices 2-2 and 2-4; the access layer device 1-4 can announce its own network segment routing and the routing prefix of the host routing of S1 to the aggregation layer devices 2-2 and 2-4.

[0068] Routing announcements can also be made between aggregation layer devices. For example, aggregation layer device 2-1 can announce the routing prefix it receives from the access layer device to aggregation layer device 2-6, aggregation layer device 2-2 can announce the routing prefix it receives from the access layer device to aggregation layer device 2-6, aggregation layer device 2-6 can announce the routing prefix it receives from aggregation layer device 2-2 to aggregation layer device 2-1, and so on. These are not described in detail here.

[0069] Through the routing announcements between the aggregation layers, the devices on the aggregation layer facing the core layer can learn the routing prefixes of S1's host routes (10.1.1.1 / 32 and 10.1.1.2 / 32), S2's host routes (10.1.2.1 / 32 and 10.1.2.2 / 32), the routing prefixes of network device 1-1 and network device 1-2's segment routes (10.1.1.0 / 24), and the routing prefixes of network device 1-3 and network device 1-4's ​​segment routes (10.1.2.0 / 24). The devices on the aggregation layer facing the core layer refer to the network devices on the aggregation layer that are used to communicate with the core layer. Figure 1 In the figure, network devices 2-5, 2-6, 2-7 and 2-8 are devices at the aggregation layer facing the core layer.

[0070] The devices at the aggregation layer facing the core layer can advertise routes to the core layer devices. In order to reduce the routing scale, when the devices at the aggregation layer facing the core layer advertise routes to the network devices at the core layer, they can aggregate the detailed routes to obtain the aggregated routes, and then advertise the aggregated routes to the core layer devices instead of publishing the detailed routes within the aggregated route segment. For example, Figure 1In the scenario shown, network device 2-5 can aggregate the prefix routes 10.1.1.1 / 32, 10.1.1.2 / 32, 10.1.2.1 / 32, 10.1.2.2 / 32, 10.1.1.0 / 24 and 10.1.2.0 / 24 to obtain an aggregate route whose routing prefix is ​​10.1.0.0 / 16, and notify the core layer devices 3-1 and 3-3 of the aggregate route obtained by its own aggregation. Similarly, network device 2-6 can aggregate the prefix routing prefixes 10.1.1.1 / 32, 10.1.1.2 / 32, 10.1.2.1 / 32, 10.1.2.2 / 32, 10.1.1.0 / 24 and 10.1.2.0 / 24 to obtain an aggregated route with a routing prefix of 10.1.0.0 / 16, and notify the core layer devices 3-2 and 3-4 of the aggregated route obtained by itself. Network device 2-7 can aggregate the prefix routing prefixes 10.1.1.1 / 32, 10.1.1.2 / 32, 10.1.2.1 / 32, 10.1.2.2 / 32, 10.1.1.0 / 24 and 10.1.2.0 / 24 to obtain an aggregated route with a routing prefix of 10.1.0.0 / 16, and notify the core layer devices 3-1 and 3-3 of the aggregated route obtained by itself. The network device 2-8 may aggregate the prefix routing prefixes 10.1.1.1 / 32, 10.1.1.2 / 32, 10.1.2.1 / 32, 10.1.2.2 / 32, 10.1.1.0 / 24 and 10.1.2.0 / 24 to obtain an aggregated route with a routing prefix of 10.1.0.0 / 16, and notify the core layer devices 3-2 and 3-4 of the aggregated route obtained by itself.

[0071] Core devices can also make route announcements between each other. For example, core layer device 3-1 can announce the route prefix 10.1.0.0 / 16 received from the aggregation layer device to core layer devices 3-6 and 3-5, core layer device 3-2 can announce the route prefix 10.1.0.0 / 16 received from the aggregation layer device to core layer devices 3-6 and 3-5, core layer device 3-3 can announce the route prefix 10.1.0.0 / 16 received from the aggregation layer device to core layer devices 3-7 and 3-8, and core layer device 3-4 can announce the route prefix 10.1.0.0 / 16 received from the aggregation layer device to core layer devices 3-7 and 3-8.

[0072] At this point, the routing table entries stored in each network device can be Figure 2a As shown, Figure 2a A schematic diagram of a routing table entry of each network device provided in an embodiment of the present application. Figure 2aIn the table corresponding to network device 1-1, the next hop corresponding to the routing prefix is ​​127.0.0.1, indicating that the routing prefix is ​​a routing prefix generated by the network device that stores the table entry. For example, in the table corresponding to network device 1-1, the next hop corresponding to the routing prefix 10.1.1.0 / 24 is 127.0.0.1, indicating that the routing prefix 10.1.1.0 / 24 is a routing prefix generated by network device 1-1. Figure 2a For network device a, the next hop information in the route table entry it stores is network device b, which can be understood as the next hop information being the port that network device b uses to communicate with network device a. For example, in the table entry corresponding to network device 1-1, the next hop corresponding to the route prefix 10.1.1.1 / 32 is S1, which can be understood as the next hop corresponding to the route prefix 10.1.1.1 / 32 is the port that S1 uses to communicate with 1-1. The ports mentioned in the embodiments of the present application may be physical ports or logical ports, which are not specifically limited in the embodiments of the present application.

[0073] In one example, if the aggregation layer fails, when the core layer device guides traffic forwarding based on the routing prefix of the aggregation route, traffic interruption may occur. Next, the failure of the aggregation layer device 2-1 is used as an example for explanation.

[0074] When network device 2-5 senses that the link between itself and network device 2-1 fails, it can delete the routing prefix 10.1.1.0 / 24 of the segment route and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route received from network device 2-1, or network device 2-5 can invalidate the routing prefix 10.1.1.0 / 24 of the segment route and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route received from network device 2-1.

[0075] Correspondingly, network device 2-5 can send a routing update message or a routing withdrawal message to network device 2-2, so that network device 2-2 deletes the routing prefix 10.1.1.0 / 24 of the segment route and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route received from network device 2-5, or, network device 2-2 invalidates the routing prefix 10.1.1.0 / 24 of the segment route and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route received from network device 2-5.

[0076] Similarly, when network device 2-6 senses that the link between itself and network device 2-1 has failed, it can delete the routing prefix 10.1.1.0 / 24 of the segment route received from network device 2-1 and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route, or network device 2-6 can invalidate the routing prefix 10.1.1.0 / 24 of the segment route received from network device 2-1 and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route.

[0077] Correspondingly, network device 2-6 can send a routing update message or a routing withdrawal message to network device 2-2, so that network device 2-2 deletes the routing prefix 10.1.1.0 / 24 of the segment route and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route received from network device 2-6, or, network device 2-2 invalidates the routing prefix 10.1.1.0 / 24 of the segment route and the routing prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32 of the host route received from network device 2-6.

[0078] At this point, the BGP routing table entries of each network device are as follows Figure 2b As shown, Figure 2b A schematic diagram of another routing table entry of each network device provided in an embodiment of the present application. Figure 2a and Figure 2b It can be seen that network device 2-1 fails, and the BGP routing table entries corresponding to network devices 2-1, 2-2, 2-5, and 2-6 have changed, while the BGP routing table entries of other network devices have not changed. Figure 2b In the example, a deleted line in a routing table entry may indicate that the routing table entry has been deleted, or may indicate that the routing table entry has been invalidated (ie, is in an invalid state).

[0079] From the above description, it can be seen that when the network device 2-1 fails, the BGP routing table entries saved by the core layer devices 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7 and 3-8 do not change. Therefore, when the core layer devices 3-1, 3-2, 3-3 and 3-4 facing the aggregation layer receive traffic matching the routing prefix 10.1.1.0 / 24, 10.1.1.1 / 32 or 10.1.1.2 / 32, they will still guide the traffic forwarding according to the table entries corresponding to the aggregated route, so that the traffic will be forwarded from the actually unavailable path, resulting in service interruption. Taking network device 3-1 as an example, when network device 3-1 receives traffic that matches the routing prefix 10.1.1.0 / 24, 10.1.1.1 / 32 or 10.1.1.2 / 32, it may forward the traffic to network device 2-5 based on its own BGP routing table entries. After the traffic is forwarded to network device 2-5, network device 2-5 cannot match the routing table entries corresponding to the traffic, and therefore discards the traffic, resulting in service interruption.

[0080] In order to solve the above problems, an embodiment of the present application provides an information processing method and device. Next, the information processing method and device provided by the embodiment of the present application are introduced in conjunction with the accompanying drawings.

[0081] See also Figure 3 , which is a schematic diagram of signaling interaction of an information processing method provided in an embodiment of the present application. Figure 3 The method shown may include the following S101-S106.

[0082] Before introducing S101-S106, the first network device, the second network device, and the third network device involved in S101-S106 are described. The embodiment of the present application does not specifically limit the first network device, the second network device, and the third network device. In the process of route transmission, the path of route transmission can be: second network device→first network device→third network device. That is, the second network device can transmit the route to the first network device, and the first network device can further transmit the route to the third network device.

[0083] when Figure 3 The method shown is applied to Figure 1In the network scenario shown, in one example, the second network device may be a device at the access layer, the first network device is a device at the aggregation layer facing the core layer, and the third network device is a device at the core layer, for example, a device at the core layer facing the aggregation layer. Among them, the device at the access layer can announce the route to the device at the aggregation layer facing the core layer through the device at the aggregation layer facing the access layer. For example, the second network device is 1-1, the first network device is 2-5, and the third network device is 3-1 or 3-3, and 1-1 can announce the route to 2-5 through 2-1. For another example, the second network device is 1-1, the first network device is 2-6, and the third network device is 3-2 or 3-4, and 1-1 can announce the route to 2-6 through 2-1.

[0084] when Figure 3 The method shown is applied to Figure 1 In the network scenario shown, in another example, the second network device may be a device at the aggregation layer facing the access layer, the first network device may be a device at the aggregation layer facing the core layer, and the third network device may be a device at the core layer, such as a device at the core layer facing the aggregation layer. For example, the second network device is 2-1, the first network device is 2-5, and the third network device is 3-1 or 3-3. For another example, the second network device is 2-1, the first network device is 2-6, and the third network device is 3-2 or 3-4.

[0085] In one example, the first network device may be a device that generates an aggregate route. Figure 3 The method shown is applied to Figure 1 In the network scenario shown, the first network device is a device that aggregates the routing prefix of the network device segment routing at the access layer and the routing prefix of the host routing of the server.

[0086] S101: A first network device determines that a first detailed route sent by a second network device to the first network device is unavailable.

[0087] Since the first detailed route is the route sent by the second network device to the first network device, in one example, the first network device can determine that the first detailed route is unavailable when the second network device fails or the link between the second network device and the first network device fails. The first detailed route is unavailable, which can be understood as the first detailed route cannot be used to guide traffic forwarding. Specifically, it can be understood that the first detailed route cannot guide the forwarding of traffic from the first network device to the route prefix of the first detailed route.

[0088] In one example, the first network device may determine that the second network device is faulty when a keepalive message between the first network device and the second network device is interrupted. In another example, the first network device may determine that a link between the first network device and the second network device is faulty when a port in the first network device used to communicate with the second network device is faulty.

[0089] In the embodiment of the present application, the first detailed route may include multiple routes, and accordingly, the route prefix of the first detailed route may include multiple route prefixes. For example, when the first network device is 2-5 and the second network device is 2-1, the route prefix of the first detailed route includes: 10.1.1.0 / 24, 10.1.1.1 / 32 and 10.1.1.2 / 32.

[0090] S102: The first network device generates a first message, which includes a routing prefix of the first detailed route, next hop information, and a routing prefix of an aggregated route, wherein the aggregated route corresponds to the first detailed route and the second detailed route, the second detailed route is available, and the next hop information indicates a first port, which is a port on the first network device for communicating with a third network device.

[0091] In the embodiment of the present application, the aggregate route corresponds to the first detailed route and the second detailed route, which can be understood as the network segment corresponding to the route prefix of the aggregate route, including the network segment corresponding to the route prefix of the first detailed route and the network segment corresponding to the route prefix of the second detailed route. Alternatively, the aggregate route can be obtained by aggregating the first detailed route and the second detailed route.

[0092] Similar to the first detailed route, the second detailed route may also include multiple routes, and accordingly, the route prefix of the second detailed route may include multiple route prefixes. For example, when the first network device is 2-5 and the second network device is 2-1, the route prefix of the second detailed route includes: 10.1.2.0 / 24, 10.1.2.1 / 32 and 10.1.2.2 / 32.

[0093] In an embodiment of the present application, if the first detailed route corresponding to the aggregate route is unavailable and the second detailed route is available, the table entry of the aggregate route stored in the third network device will not change due to the unavailability of the first detailed route. Therefore, when the third network device guides traffic forwarding based on the table entry corresponding to the aggregate route, there will be a phenomenon of traffic interruption. In order to solve this problem, in an embodiment of the present application, the first network device can generate a first message. The first message includes the route prefix of the first detailed route, the next hop information, and the route prefix of the aggregate route. The next hop information indicates the first network device. Specifically, the next hop information indicates the first port on the first network device for communicating with the third network device. The next hop information can be, for example, the port address of the first port.

[0094] In one example, the first message may be a first Ethernet message, which includes the routing prefix of the first detailed route, the next hop information, and the routing prefix of the aggregated route. In another example, the first message may be a routing advertisement message, namely, a BGP update message.

[0095] In one example, the route advertisement message may include an extended community attribute, wherein the extended community attribute includes the route prefix and next hop information of the aggregate route. In addition, the route advertisement message also includes network layer reachability information (NLRI), wherein the NLRI includes the route prefix of the first detailed route.

[0096] The embodiments of the present application do not specifically limit the extended group attribute, and the extended group attribute can be any type of BGP extended group attribute. As an example, the extended group attribute can be a BGP path attribute. That is, the BGP path attribute can be used to carry the routing prefix and next hop information of the aforementioned aggregate route. For this case, in one example, the type code of the BGP path attribute indicates that the BGP path attribute is used to carry the routing prefix and the next hop information of the aggregate route. In this way, the network device that receives the first message can determine that the content carried by the BGP path attribute is the routing prefix and the next hop information of the aggregate route based on the type code field of the BGP path attribute. In another example, the type code is also used to indicate that the NLRI in the routing announcement message is used to carry the routing prefix of an unavailable detailed route (i.e., the routing prefix of the first detailed route).

[0097] Regarding the routing advertisement message, it may include Figure 4 The structure shown. Figure 4A schematic diagram of the structure of a routing advertisement message provided in an embodiment of the present application. Figure 4 As shown, the routing advertisement message includes a BGP path attribute 410 and an NLRI 420, wherein the BGP path attribute 410 includes a type code field 411, an aggregate route field 412, and an unreachable next hop field 413, wherein:

[0098] The aggregate route field 412 and the unreachable next hop field 413 belong to the value field of the BGP path attribute 410;

[0099] The aggregate route field 412 is used to carry the route prefix of the aggregate route;

[0100] The unreachable next hop field 413 is used to carry the aforementioned next hop information;

[0101] The type code field 411 indicates a routing attribute, the attribute type of which is an unavailable routing prefix. As a specific example, the type code field 411 indicates that the aggregate routing field 412 carries the routing prefix of the aggregate routing, the unreachable next hop field 413 carries the aforementioned next hop information, and the NLRI field 420 carries the routing prefix of the unavailable detailed routing;

[0102] The NLRI 420 carries the routing prefix of the first specific route.

[0103] It should be noted that Figure 4 This is for the purpose of understanding some fields of the routing announcement message shown in this solution. The routing announcement message may also include other fields, which are not specifically limited in the embodiments of the present application.

[0104] In another example, the routing prefix, next hop information, and routing prefix of the aggregated route of the aforementioned first detailed route can all be carried through the NLRI in the routing announcement message. For example, the NLRI includes a first subtype length value (sub type length value, sub-TLV) and a second sub-TLV, the first sub-TLV is used to carry the routing prefix of the aggregated route, and the second sub-TLV is used to carry the aforementioned next hop information.

[0105] S103: The first network device sends the first message to the third network device.

[0106] S104: The third network device receives the first message sent by the first network device.

[0107] S105: The third network device locally searches for a routing table entry corresponding to the routing prefix of the aggregate route.

[0108] After the first network device generates the first message, it can send the first message to the third network device. Accordingly, the third network device can receive the first message announced by the first network device. After the third network device receives the first message, it can determine, based on the first message, that the first detailed route is unavailable, that is, it can determine that the first detailed route cannot guide the forwarding of traffic from the first network device to the route prefix of the first detailed route. Furthermore, the third network device can locally search for the route table entry corresponding to the route prefix of the aggregate route. In one example, the third network device can use the route prefix of the aggregate route as an index to search for the locally stored route table entry.

[0109] S106: If the next hop information included in the first routing table entry found by the third network device indicates the first port and the second port, and the second port is a port on the fourth network device used to communicate with the third network device, then a second routing table entry corresponding to the routing prefix of the first detailed route is generated, wherein the next hop information included in the second routing table entry indicates the second port.

[0110] After the third network device searches for and obtains the first routing table entry corresponding to the routing prefix of the aggregate route, it can determine a corresponding processing measure according to the next hop information in the first routing table entry.

[0111] In one example, if the next hop information included in the first routing table entry indicates the first port and the second port. For example, the next hop information in the first routing table entry includes the port address of the first port and the port address of the second port. Among them, the second port is a port on the fourth network device for communicating with the third network device. It means that when the third network device forwards the traffic matching the routing prefix corresponding to the aforementioned first detailed route, it can be forwarded through the first network device or through the fourth network device. In this case, in order to avoid the third network device forwarding the traffic to the first network device and causing traffic interruption, the third network device can generate a second routing table entry corresponding to the routing prefix of the first detailed route, wherein the next hop information included in the second routing table entry indicates the second port. In this way, when the third network device receives the traffic matching the routing prefix corresponding to the aforementioned first detailed route, it can forward the traffic to the fourth network device based on the second routing table entry, thereby avoiding traffic interruption.

[0112] For example: the first network device is 2-5, the second network device is 2-1, the third network device is 3-1, the routing prefixes of the first detailed route include: 10.1.1.0 / 24, 10.1.1.1 / 32 and 10.1.1.2 / 32, the fourth network device is 2-7, then the next hop information in the second routing table entry indicates the port in network device 2-7 used to communicate with network device 3-1. Then the second routing table entry is shown in Table 1 below:

[0113] Table 1

[0114] Route Prefix Next hop 10.1.1.0 / 24 2-7 10.1.1.1 / 32 2-7 10.1.1.2 / 32 2-7

[0115] In another example, if the next hop information included in the first routing table entry only indicates the first port. For example, the next hop information in the first routing table entry only includes the port address of the first port. It means that when the third network device forwards the traffic matching the routing prefix corresponding to the aforementioned first detailed route, it can only be forwarded through the first network device. In this case, once the third network device receives the traffic matching the routing prefix corresponding to the first detailed route, it will inevitably cause traffic interruption. In this case, the third network device can generate a second message based on the first message, the second message includes the routing prefix of the first detailed route, the next hop information indicating the third port, and the routing prefix of the aggregate route, the third port is the port in the third network device for communicating with the fifth network device, and the second message is sent to the fifth network device. For example, the first network device is 2-5, the second network device is 2-1, the third network device is 3-1, and the fifth network device is 3-5 or 3-6.

[0116] Regarding the second message, its message structure is the same as that of the first message. For related content, please refer to the description of the first message above, and no repeated description will be made here.

[0117] Correspondingly, after receiving the second message, the fifth network device can search for the routing table item corresponding to the routing prefix of the aggregate route locally. If the next hop information included in the third routing table item obtained by searching indicates the third port and the fourth port, the fourth port is the port on the sixth network device used to communicate with the fifth network device. It means that when the fifth network device forwards the traffic matching the routing prefix corresponding to the aforementioned first detailed route, it can be forwarded through the third network device or the sixth network device. In this case, in order to avoid the fifth network device forwarding the traffic to the third network device and causing traffic interruption, the fifth network device can generate a fourth routing table item corresponding to the routing prefix of the first detailed route, wherein the next hop information included in the fourth routing table item indicates the fourth port. In this way, when the fifth network device receives the traffic matching the routing prefix corresponding to the aforementioned first detailed route, it can forward the traffic to the sixth network device based on the fourth routing table item, thereby avoiding traffic interruption.

[0118] For example: the first network device is 2-5, the second network device is 2-1, the third network device is 3-1, the fifth network device is 3-5, and the sixth network device is 3-2. The routing prefixes of the first detailed route include: 10.1.1.0 / 24, 10.1.1.1 / 32, and 10.1.1.2 / 3. The next hop information in the fourth routing table entry indicates the port in network device 3-2 used to communicate with network device 3-5. The second routing table entry is shown in Table 1 below:

[0119] Table 2

[0120] Route Prefix Next hop 10.1.1.0 / 24 3-2 10.1.1.1 / 32 3-2 10.1.1.2 / 32 3-2

[0121] In one example, considering that when a network failure occurs, the operation and maintenance personnel will troubleshoot the failure and perform corresponding processing measures to restore the failure. Therefore, in order to reduce the number of routing table items maintained by the network device, the third network device can also set a certain life cycle for the second routing table item, and delete the second routing table item at the end of the life cycle. The embodiment of the present application does not specifically limit the specific value of the life cycle, and the life cycle can be determined, for example, according to the time of fault recovery.

[0122] In an example, before executing S101, the first network device may also send the aggregate route to the third network device, and not send the first detailed route and the second detailed route to the third network device, so as to reduce the number of routing table entries maintained by the third network device.

[0123] From the above description, it can be seen that by using the solution of the embodiment of the present application, traffic interruption can be avoided in a scenario where the first network device only publishes the aggregate route to the third network device and no longer publishes the detailed route corresponding to the aggregate route.

[0124] The above is an introduction to the information processing method provided in the embodiment of the present application. Figure 1 The network architecture shown introduces the specific application of the information processing method provided by this application under different fault scenarios.

[0125] See also Figure 5a , Figure 5a A schematic diagram of a fault scenario provided in an embodiment of the present application is shown in FIG. Figure 5a As shown, if the link between network device 2-5 and network device 2-1 fails, 2-5 can generate a routing announcement message 1 and send it to network devices 3-1 and 3-3. Correspondingly, network devices 3-1 and 3-3 can generate a routing table entry 501 corresponding to the first detailed route based on the routing announcement message 1 while retaining the original routing table entry.

[0126] See also Figure 5b , Figure 5b A schematic diagram of another fault scenario provided in an embodiment of the present application is shown in FIG. Figure 5b As shown, the network device 2-1 fails, which causes the link between the network device 2-5 and the network device 2-1, and the link between the network device 2-6 and the network device 2-1 to fail. Then 2-5 can generate a routing announcement message 1 and send it to the network devices 3-1 and 3-3. Accordingly, the network devices 3-1 and 3-3 can generate routing table entry 501 based on the routing announcement message 1 while retaining the original routing table entry. Similarly, 2-6 can generate a routing announcement message 2 and send it to the network devices 3-2 and 3-4. Accordingly, the network devices 3-2 and 3-4 can generate routing table entry 502 based on the routing announcement message 2 while retaining the original routing table entry.

[0127] about Figure 5a and Figure 5b The specific structure of the routing advertisement message (eg, routing advertisement message 1 and routing advertisement message 2) involved can be combined with Figure 4 Understand, in Figure 5a and Figure 5b The examples are just simple examples and do not constitute a limitation of the embodiments of the present application.

[0128] Based on the information processing method provided by the above method embodiment, the present application embodiment also provides a corresponding device. Next, the information processing device provided by the present application embodiment is introduced in conjunction with the accompanying drawings.

[0129] See also Figure 6 , Figure 6 A schematic diagram of the structure of an information processing device provided in an embodiment of the present application. Figure 6 The information processing apparatus 600 shown can be applied to a first network device, and is used to execute the steps provided by the above method embodiment and performed by the first network device, for example, to execute S101 to S103 above.

[0130] Figure 6 The information processing device 600 shown includes a processing unit 601 and a sending unit 602 .

[0131] The processing unit 601 is configured to determine that a first specific route sent by the second network device to the first network device is unavailable, and generate a first message, where the first message includes a route prefix and next hop information of the first specific route, and a route prefix of an aggregate route, where the aggregate route corresponds to the first specific route and the second specific route, the second specific route is available, and the next hop information indicates a first port, where the first port is a port on the first network device used to communicate with a third network device;

[0132] The sending unit 602 is configured to send the first message to the third network device.

[0133] In a possible implementation, the sending unit 602 is further configured to: before determining that the first specific route is unavailable, send the aggregate route to the third network device, and not send the first specific route and the second specific route to the third network device.

[0134] In a possible implementation manner, determining that the first detailed route sent by the second network device to the first network device is unavailable includes: determining that the second network device fails, or determining that a link between the second network device and the first network device fails.

[0135] In a possible implementation manner, the first specific route is unavailable, including: the first specific route cannot guide the forwarding of traffic from the first network device to the route prefix of the first specific route.

[0136] In a possible implementation manner, the first message includes a routing advertisement message.

[0137] In a possible implementation manner, the route advertisement message includes an extended community attribute, and the extended community attribute includes a route prefix of the aggregate route and the next hop information.

[0138] In a possible implementation manner, the extended community attribute is a Border Gateway Protocol (BGP) path attribute.

[0139] In a possible implementation manner, the type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix of the aggregate route and the next hop information.

[0140] In a possible implementation manner, the first network device is a network device that generates the aggregate route.

[0141] In a possible implementation, the first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

[0142] See also Figure 7 , Figure 7 A schematic diagram of the structure of another information processing device provided in an embodiment of the present application. Figure 7 The information processing apparatus 700 shown may be applied to a third network device, and is used to execute the steps provided by the third network device in the above method embodiment, for example, to execute S104 to S106 above.

[0143] Figure 7 The information processing device 700 shown includes a receiving unit 701 and a processing unit 702 .

[0144] A receiving unit 701 is configured to receive a first message sent by a first network device, where the first message includes a route prefix and next hop information of a first detailed route, and a route prefix of an aggregated route, where the aggregated route corresponds to the first detailed route and the second detailed route, where the first detailed route is unavailable, where the first detailed route is a route sent by a second network device to the first network device, where the second detailed route is available, and where the next hop information indicates a first port, where the first port is a port on the first network device used to communicate with the third network device;

[0145] Processing unit 702 is used to locally search for a routing table entry corresponding to the routing prefix of the aggregate route, and if the next hop information included in the first routing table entry obtained indicates the first port and the second port, and the second port is a port on a fourth network device for communicating with the third network device, then generate a second routing table entry corresponding to the routing prefix of the first detailed route, wherein the next hop information included in the second routing table entry indicates the second port.

[0146] In a possible implementation, the processing unit 702 is also used to: if the next hop information included in the first routing table entry only indicates the first port, generate a second message based on the first message, the second message including the routing prefix of the first detailed route, the next hop information indicating the third port, and the routing prefix of the aggregate route, the third port being the port in the third network device for communicating with the fifth network device; the device also includes a sending unit for notifying the fifth network device of the second message.

[0147] In a possible implementation manner, the first specific route is unavailable, including: the first specific route cannot guide the forwarding of traffic from the first network device to the route prefix of the first specific route.

[0148] In a possible implementation manner, the first message includes a routing advertisement message.

[0149] In a possible implementation manner, the route advertisement message includes an extended community attribute, and the extended community attribute includes a route prefix of the aggregate route and the next hop information.

[0150] In a possible implementation manner, the extended community attribute is a Border Gateway Protocol (BGP) path attribute.

[0151] In a possible implementation manner, the type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix of the aggregate route and the next hop information.

[0152] In a possible implementation manner, the first network device is a network device that generates the aggregate route.

[0153] In a possible implementation, the first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

[0154] It should be noted that the hardware structure of the information processing devices 600 and 700 mentioned above can be as follows: Figure 8 The structure shown, Figure 8 A schematic diagram of the structure of a device provided in an embodiment of the present application.

[0155] See also Figure 8 As shown, the device 800 includes: a processor 810, a communication interface 820 and a memory 830. The number of the processor 810 in the device 800 can be one or more. Figure 8In the embodiment of the present application, the processor 810, the communication interface 820 and the memory 830 may be connected via a bus system or other means, wherein: Figure 8 The connection via bus system 840 is taken as an example.

[0156] The processor 810 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor 810 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0157] The memory 830 may include a volatile memory (English: volatile memory), such as a random-access memory (RAM); the memory 830 may also include a non-volatile memory (English: non-volatile memory), such as a flash memory (English: flash memory), a hard disk drive (HDD) or a solid-state drive (SSD); the memory 830 may also include a combination of the above-mentioned types of memory. The memory 830 may, for example, store routing table entries corresponding to routing prefixes of routing aggregation.

[0158] Optionally, the memory 830 stores an operating system and a program, an executable module or a data structure, or a subset thereof, or an extended set thereof, wherein the program may include various operating instructions for implementing various operations. The operating system may include various system programs for implementing various basic services and processing hardware-based tasks. The processor 810 may read the program in the memory 830 to implement the information processing method provided in the embodiment of the present application.

[0159] The bus system 840 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus system 840 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The embodiment of the present application also provides a computer-readable storage medium, including instructions or computer programs, which, when running on a computer, enable the computer to execute the information processing method provided in the above embodiment.

[0160] The embodiments of the present application also provide a computer program product including instructions or a computer program, which, when executed on a computer, enables the computer to execute the information processing method provided in the above embodiments.

[0161] An embodiment of the present application also provides a communication system, including the first network device and the third network device provided in the above method embodiment, which is used to execute the information processing method provided in the above method embodiment.

[0162] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0163] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0164] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical business division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0165] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0166] In addition, each business unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software business units.

[0167] If the integrated unit is implemented in the form of a software business unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0168] Those skilled in the art will appreciate that in one or more of the above examples, the services described in the present invention may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, the services may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media may be any available media that a general or special-purpose computer can access.

[0169] The above specific implementation modes further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation modes of the present invention.

[0170] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An information processing method, characterized in that: Applied to a first network device, the method comprises: Determining that a first detailed route sent by the second network device to the first network device is unavailable; Generate a first message, the first message including a route prefix of the first detailed route, next hop information, and a route prefix of an aggregate route, the aggregate route corresponds to the first detailed route and the second detailed route, the second detailed route is available, and the next hop information indicates a first port, the first port is a port on the first network device for communicating with a third network device; The first message is sent to the third network device.

2. The method according to claim 1, characterized in that Before determining that the first detailed route is unavailable, the method further includes: The aggregate route is sent to the third network device, and the first specific route and the second specific route are not sent to the third network device.

3. The method according to claim 1 or 2, characterized in that: The determining that the first detailed route sent by the second network device to the first network device is unavailable includes: Determine that the second network device fails, or, A link failure between the second network device and the first network device is determined.

4. The method according to claim 3, characterized in that The first detailed route is unavailable, including: The first specific route cannot guide the forwarding of traffic from the first network device to the routing prefix of the first specific route.

5. The method according to any one of claims 1 to 4, characterized in that: The first message includes a routing advertisement message.

6. The method according to claim 5, characterized in that The route advertisement message includes an extended community attribute, and the extended community attribute includes the route prefix of the aggregate route and the next hop information.

7. The method according to claim 6, characterized in that The extended community attribute is a Border Gateway Protocol BGP path attribute.

8. The method according to claim 7, characterized in that The type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix and the next hop information of the aggregate route.

9. The method according to any one of claims 1 to 8, characterized in that: The first network device is a network device that generates the aggregate route.

10. The method according to any one of claims 1 to 9, characterized in that: The first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

11. An information processing method, characterized in that: Applied to a third network device, the method includes: receiving a first message sent by a first network device, the first message including a route prefix and next hop information of a first specific route, and a route prefix of an aggregate route, the aggregate route corresponding to the first specific route and the second specific route, the first specific route being unavailable, the first specific route being a route sent by a second network device to the first network device, the second specific route being available, the next hop information indicating a first port, the first port being a port on the first network device used for communicating with the third network device; Searching for a routing table entry corresponding to the routing prefix of the aggregated route locally; If the next hop information included in the first routing table entry obtained by retrieval indicates the first port and the second port, and the second port is a port on the fourth network device used to communicate with the third network device, then a second routing table entry corresponding to the routing prefix of the first detailed route is generated, wherein the next hop information included in the second routing table entry indicates the second port.

12. The method according to claim 11, characterized in that The method further comprises: If the next hop information included in the first routing table entry only indicates the first port, a second message is generated according to the first message, the second message including a routing prefix of the first detailed route, next hop information indicating a third port, and a routing prefix of the aggregate route, the third port being a port in the third network device for communicating with a fifth network device; The second message is notified to the fifth network device.

13. The method according to claim 11 or 12, characterized in that: The first detailed route is unavailable, including: The first specific route cannot guide the forwarding of traffic from the first network device to the routing prefix of the first specific route.

14. The method according to any one of claims 11 to 13, characterized in that: The first message includes a routing advertisement message.

15. The method according to claim 14, characterized in that The route advertisement message includes an extended community attribute, and the extended community attribute includes the route prefix of the aggregate route and the next hop information.

16. The method according to claim 15, characterized in that The extended community attribute is a Border Gateway Protocol BGP path attribute.

17. The method according to claim 16, characterized in that The type code type code of the BGP path attribute indicates that the BGP path attribute is used to carry the route prefix and the next hop information of the aggregate route.

18. The method according to any one of claims 11 to 17, characterized in that: The first network device is a network device that generates the aggregate route.

19. The method according to any one of claims 11 to 18, characterized in that: The first network device is a device in the convergence layer facing the core layer, the second network device is a device in the convergence layer facing the access layer or a device in the access layer, and the third network device is a device in the core layer.

20. An information processing device, characterized in that: Applied to a first network device, the apparatus comprises: a processing unit, configured to determine that a first specific route sent by a second network device to the first network device is unavailable, and generate a first message, wherein the first message includes a route prefix and next hop information of the first specific route, and a route prefix of an aggregate route, wherein the aggregate route corresponds to the first specific route and the second specific route, the second specific route is available, and the next hop information indicates a first port, wherein the first port is a port on the first network device used for communicating with a third network device; A sending unit, configured to send the first message to the third network device.

21. An information processing device, characterized in that: Applied to a third network device, the apparatus comprises: a receiving unit, configured to receive a first message sent by a first network device, wherein the first message includes a route prefix and next hop information of a first detailed route, and a route prefix of an aggregated route, wherein the aggregated route corresponds to the first detailed route and the second detailed route, wherein the first detailed route is unavailable, the first detailed route is a route sent by the second network device to the first network device, the second detailed route is available, and the next hop information indicates a first port, wherein the first port is a port on the first network device used for communicating with the third network device; A processing unit is used to locally search for a routing table entry corresponding to the routing prefix of the aggregate route, and if the next hop information included in the first routing table entry obtained indicates the first port and the second port, and the second port is a port on a fourth network device for communicating with the third network device, then generate a second routing table entry corresponding to the routing prefix of the first detailed route, wherein the next hop information included in the second routing table entry indicates the second port.

22. A device, characterized in that include: Processor and memory; The memory is used to store instructions or computer programs; The processor is used to execute the instructions or computer programs to perform the method according to any one of claims 1 to 19.

23. A computer-readable storage medium, characterized in that: The method comprises instructions or computer programs, which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 19.

24. A communication system, characterized in that: The system comprises: A first network device for executing the method described in any one of claims 1 to 10, and a third network device for executing the method described in any one of claims 11 to 19.

Images