Information processing method and apparatus

Abstract

Disclosed in the embodiments of the present application is an information processing method, which is applied to a first network device. The 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, wherein the first message comprises a route prefix of the first detail route, next-hop information, and a route prefix of an aggregation route, the aggregation route corresponds to the first detail route and a second detail route, the second detail route is available, and the next-hop information indicates a port on the first network device that is used for communicating with a third network device; and after generating the first message, the first network device can send the first message to the third network device, such that the third network device determines that the first detail route corresponding to the aggregation route is unavailable, and the third network device can correspondingly execute corresponding processing measures, so as to prevent traffic, which matches the first detail route, from being forwarded to the first network device, thereby avoiding traffic interruption.

Description

Information processing method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on August 17, 2023, with application number 202311044698.2 and invention name “A Method and Device for Information Processing”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0003] Network devices can transfer routes between each other, for example, using the Border Gateway Protocol (BGP). BGP is an external gateway protocol used to select optimal routes and control route propagation between network domains, such as autonomous systems (ASs). When BGP operates within the same network domain, it is called the Internal Border Gateway Protocol (IBGP). When BGP operates between different network domains, it is called the External Border Gateway Protocol (EBGP).

[0004] To reduce the number of routes maintained by network devices, you can aggregate specific routes to create aggregated routes. Consequently, when advertising routes, network devices can only advertise the aggregated routes, eliminating the specific routes. However, this approach can cause traffic interruptions when traffic is forwarded based on the aggregated routes.

[0005] Therefore, a solution is urgently needed to solve the above problems.

[0006] Summary of the Invention

[0007] 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.

[0008] In a first aspect, embodiments of the present application provide an information processing method that can be applied to a first network device. In one example, the first network device can determine that a first specific route sent by a second network device to the first network device is unavailable. After determining that the first specific route is unavailable, the first network device can generate a first message. The first message includes the route prefix of the first specific route, next hop information, and the route prefix of an aggregate route. The aggregate route corresponds to the first specific route and the second specific route. In other words, the network segment corresponding to the aggregate route includes the network segment corresponding to the first specific route and the network segment corresponding to the second specific route. The second specific 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 used for communication with a third network device. After generating the first message, the first network device can send the first message to the third network device, causing the third network device to determine that the first specific route corresponding to the aggregate route is unavailable. In response, the third network device can perform corresponding processing to prevent traffic matching the first specific route from being forwarded to the first network device, thereby avoiding traffic interruption. This shows that, by using this solution, traffic interruption can be avoided in a scenario where network devices only publish aggregate routes and no longer publish detailed routes.

[0009] 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.

[0010] In one possible implementation, the first network device may determine that the first detailed route is unavailable if the second network device fails, or if the link between the second network device and the first network device fails. The unavailability of the first detailed route can be understood as meaning that 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 if the second network device fails, or if the link between the second network device and the first network device fails. Furthermore, the first network device may send a first message to a third network device to avoid traffic interruption.

[0011] 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 as the first detailed route cannot guide the forwarding of traffic from the first network device to the routing prefix of the first detailed route. In this scenario, if traffic whose destination address matches the routing 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.

[0012] In one possible implementation, the first message may be a route advertisement message. In this case, the first network device may send the route prefix, next hop information, and route prefix of the aggregate route of the first specific route to the third network device via the route advertisement message, so that the third network device determines that the first specific route corresponding to the aggregate route is unavailable. Accordingly, the third network device may perform appropriate processing to prevent traffic matching the first specific route from being forwarded to the first network device, thereby avoiding traffic interruption.

[0013] In one possible implementation, the route advertisement message includes an extended community attribute, which includes the route prefix and the next hop information of the aggregated route. The third network device may parse the extended community attribute to obtain the route prefix and the next hop information of the aggregated route. In another 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 and the next hop information of the aggregated route.

[0014] In one 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, based on the type code field of the BGP path attribute, that the content carried by the BGP path attribute is the route prefix and the next hop information of the aggregated route, and thus parse the BGP path attribute field to obtain the route prefix and the next hop information of the aggregated route.

[0015] In one possible implementation, the first network device is the network device that generates the aggregated route. That is, upon detecting that the first specific route is unavailable, the device that generates the aggregated route sends a first message to a third network device, so that the third network device can determine that the first specific route corresponding to the aggregated route is unavailable. Accordingly, the third network device can execute appropriate processing measures to prevent traffic matching the first specific route from being forwarded to the first network device, thereby avoiding traffic interruption.

[0016] In one possible implementation, the first network device is a device in the aggregation layer facing the core layer, the second network device is a device in the aggregation 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 aggregation layer publishes an aggregate route to the core layer devices but no longer publishes the first and second detailed routes corresponding to the aggregate route, even if the first detailed route sent by the aggregation layer to the access layer devices or the access layer devices is unavailable, traffic will not be interrupted.

[0017] In a second aspect, embodiments of the present application provide an information processing method that can be applied to a third network device. In one example, the third network device may receive a first message sent by a first network device. The first message includes a route prefix, next hop information, and a route prefix of an aggregate route. The aggregate route corresponds to the first and second specific routes. In other words, the network segment corresponding to the aggregate route includes the network segment corresponding to the first and second specific routes. The second specific 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 used for communication with the third network device. After receiving the first message, the third network device may locally search for a route table entry corresponding to the route prefix of the aggregate route. If the next hop information included in the first route table entry indicates the first and second ports, and the second port is a port on a fourth network device used for communication with the third network device, the third network device may generate a second route table entry corresponding to the route prefix of the first specific route, wherein the next hop information included in the second route table entry indicates the second port. In this way, when the third network device receives traffic that matches the first specific 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. Thus, using this solution, it is possible to avoid traffic interruption in scenarios where network devices only publish aggregate routes and no longer publish specific routes.

[0018] In one 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. This means that when the third network device forwards traffic matching the routing prefix corresponding to the first specific route, it can only forward it through the first network device. In this case, once the third network device receives traffic matching the routing prefix corresponding to the first specific route, traffic will inevitably be interrupted. In this case, the third network device may generate a second message based on the first message. The second message includes the routing prefix of the first specific route, next hop information indicating the third port, and the routing prefix of the aggregate route. The third port is the port on the third network device used for communication with the fifth network device. The second message is then sent to the fifth network device. Accordingly, after receiving the second message, the fifth network device may locally search for a routing table entry corresponding to the routing prefix of the aggregate route. If the next hop information included in the third routing table entry found indicates the third port and the fourth port, the fourth port is the port on the sixth network device used for communication 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 either 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.

[0019] In a possible implementation, the first specific 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.

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

[0021] In a possible implementation, 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.

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

[0023] 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 aggregate route.

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

[0025] 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.

[0026] 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 generates 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.

[0027] In a possible implementation, 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.

[0028] In a possible implementation, 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.

[0029] In a possible implementation, the first specific 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.

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

[0031] In a possible implementation, 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.

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

[0033] 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 aggregate route.

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

[0035] 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.

[0036] 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 aggregate route of a first detailed route, the aggregate 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, the next hop information indicates a first port, and the first port 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 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 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.

[0037] In one possible implementation, the processing unit is further 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.

[0038] In a possible implementation, the first specific 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.

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

[0040] In a possible implementation, 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.

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

[0042] 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 aggregate route.

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

[0044] 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.

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

[0046] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, comprising 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 to execute any of the methods described in the second aspect above.

[0047] 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 one of the methods described in the first aspect above, or to execute any one of the methods described in the second aspect above.

[0048] 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

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

[0050] FIG1 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0051] FIG2a is a schematic diagram of routing table entries of various network devices provided in an embodiment of the present application;

[0052] FIG2b is a schematic diagram of another routing table entry of each network device provided in an embodiment of the present application;

[0053] FIG3 is a schematic diagram of signaling interaction of an information processing method provided in an embodiment of the present application;

[0054] FIG4 is a schematic diagram of the structure of a routing advertisement message provided in an embodiment of the present application;

[0055] FIG5a is a schematic diagram of a fault scenario provided in an embodiment of the present application;

[0056] FIG5 b is a schematic diagram of another fault scenario provided in an embodiment of the present application;

[0057] FIG6 is a schematic diagram of the structure of an information processing device provided in an embodiment of the present application;

[0058] FIG7 is a schematic structural diagram of another information processing device provided in an embodiment of the present application;

[0059] FIG8 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0060] 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.

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

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

[0063] The network structure shown in Figure 1 can be, but is not limited to, a data center network architecture. The network architecture shown in Figure 1 includes an access layer, an aggregation layer, and a core layer. The access layer includes network devices 1-1, 1-2, 1-3, and 1-4. The aggregation 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.

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

[0065] 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 has two host routes with prefixes 10.1.1.1 / 32 and 10.1.1.2 / 32, respectively. S2 has two host routes with prefixes 10.1.2.1 / 32 and 10.1.2.2 / 32, respectively.

[0066] Network devices 1-1 and 1-2 both have corresponding network segment routes. The host route corresponding to S1 is within the network segment of the network segment routes corresponding to both network devices 1-1 and 1-2. In one example, the route prefix for the network segment routes corresponding to both network devices 1-1 and 1-2 is 10.1.1.0 / 24. The route prefix for 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.

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

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

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

[0070] 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 explained in detail here.

[0071] Through route advertisements between the aggregation layers, the devices facing the core layer can learn the routing prefixes for S1's host routes (10.1.1.1 / 32 and 10.1.1.2 / 32), the routing prefixes for S2's host routes (10.1.2.1 / 32 and 10.1.2.2 / 32), the routing prefixes for the segment routes of network devices 1-1 and 1-2 (10.1.1.0 / 24), and the routing prefixes for the segment routes of network devices 1-3 and 1-4 (10.1.2.0 / 24). The devices facing the core layer are the network devices used by the aggregation layer to communicate with the core layer. In Figure 1, network devices 2-5, 2-6, 2-7, and 2-8 are the devices facing the core layer.

[0072] Devices at the aggregation layer facing the core layer can advertise routes to core layer devices. To reduce the scale of routes, devices at the aggregation layer facing the core layer can aggregate detailed routes to obtain aggregated routes when advertising routes to network devices at the core layer, and advertise the aggregated routes to the core layer devices without publishing the detailed routes within the aggregated route segment. For example, in the scenario shown in Figure 1, 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 aggregated route with a route prefix of 10.1.0.0 / 16, and advertise the aggregated route obtained by itself to core layer devices 3-1 and 3-3. Similarly, network device 2-6 can aggregate the 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 prefix of 10.1.0.0 / 16, and advertise the aggregated route to core devices 3-2 and 3-4. Network device 2-7 can aggregate the 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 prefix of 10.1.0.0 / 16, and advertise the aggregated route to core devices 3-1 and 3-3. Network device 2-8 may aggregate the 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 the prefix 10.1.0.0 / 16, and notify the core layer devices 3-2 and 3-4 of the aggregated route.

[0073] Core devices can also advertise routes between each other. For example, core device 3-1 can advertise the routing prefix 10.1.0.0 / 16 received from the aggregation device to core devices 3-6 and 3-5. Core device 3-2 can advertise the routing prefix 10.1.0.0 / 16 received from the aggregation device to core devices 3-6 and 3-5. Core device 3-3 can advertise the routing prefix 10.1.0.0 / 16 received from the aggregation device to core devices 3-7 and 3-8. Core device 3-4 can advertise the routing prefix 10.1.0.0 / 16 received from the aggregation device to core devices 3-7 and 3-8.

[0074] At this point, the routing table entries stored by each network device can be shown in Figure 2a, which is a schematic diagram of the routing table entries of each network device provided in an embodiment of the present application. In Figure 2a, 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 entry. For example, in the entry 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. In Figure 2a, for network device a, the next hop information in the routing table entry it stores is network device b, which can be understood as the next hop information being the port used by network device b to communicate with network device a. For example, in the table entry corresponding to network device 1-1, the next hop corresponding to the routing prefix 10.1.1.1 / 32 is S1, which can be understood as the next hop corresponding to the routing prefix 10.1.1.1 / 32 being the port S1 uses to communicate with 1-1. The ports mentioned in the embodiments of the present application can be physical ports or logical ports, and the embodiments of the present application do not specifically limit this.

[0075] In one example, if a failure occurs at the aggregation layer, traffic will be interrupted when the core layer devices direct traffic forwarding based on the routing prefix of the aggregation route. Next, let's take the failure of aggregation layer device 2-1 as an example.

[0076] When network device 2-5 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 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.

[0077] Accordingly, 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 makes network device 2-2 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-5.

[0078] 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.

[0079] Accordingly, 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, causes network device 2-2 to 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-6.

[0080] At this point, the BGP routing table entries of each network device are shown in Figure 2b, which is a schematic diagram of another routing table entry for each network device provided in an embodiment of the present application. As can be seen from Figures 2a and 2b, 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 remain unchanged. In Figure 2b, the strikethrough in the routing table entry can indicate that the routing table entry has been deleted, or it can indicate that the routing table entry has been invalidated (i.e., is in an invalid state).

[0081] As can be seen from the preceding description, when network device 2-1 fails, the BGP routing entries stored in core devices 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7, and 3-8 remain unchanged. Therefore, when core devices 3-1, 3-2, 3-3, and 3-4, facing the aggregation layer, receive traffic matching the route prefixes 10.1.1.0 / 24, 10.1.1.1 / 32, or 10.1.1.2 / 32, they continue to forward the traffic based on the corresponding entries in the aggregation route. This results in traffic being forwarded along an unavailable path, causing 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 entry corresponding to the traffic, and therefore discards the traffic, resulting in service interruption.

[0082] 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.

[0083] Referring to Figure 3, which is a schematic diagram of signaling interaction of an information processing method provided by an embodiment of the present application, the method shown in Figure 3 may include the following steps S101-S106.

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

[0085] When the method shown in FIG3 is applied to the network scenario shown in FIG1, in one example, the second network device may be a device at the access layer, the first network device may be a device at the convergence layer facing the core layer, and the third network device may be a device at the core layer, for example, a device at the core layer facing the convergence layer. The device at the access layer may announce routes to the device at the convergence layer facing the core layer via the device at the convergence layer facing the access layer. For example, if 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, 1-1 may announce routes to 2-5 via 2-1. For another example, if 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, 1-1 may announce routes to 2-6 via 2-1.

[0086] When the method shown in Figure 3 is applied to the network scenario shown in Figure 1, in another example, the second network device can be a device at the aggregation layer facing the access layer, the first network device can be a device at the aggregation layer facing the core layer, and the third network device can 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.

[0087] In one example, the first network device may be a device that generates an aggregated route. When the method shown in FIG3 is applied to the network scenario shown in FIG1 , 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.

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

[0089] Because 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 may determine that the first detailed route is unavailable if the second network device fails, or if the link between the second network device and the first network device fails. The unavailability of the first detailed route can be understood as the inability of the first detailed route to guide traffic forwarding. Specifically, this can be understood as the inability of the first detailed route to guide traffic forwarding from the first network device to the route prefix of the first detailed route.

[0090] 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 used for communicating with the second network device in the first network device is faulty.

[0091] In this embodiment of the present application, a 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 prefixes of the first detailed route include: 10.1.1.0 / 24, 10.1.1.1 / 32, and 10.1.1.2 / 32.

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

[0093] In the embodiments of the present application, an aggregated route corresponds to a first detailed route and a second detailed route. This can be understood as the network segment corresponding to the route prefix of the aggregated 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 aggregated route can be obtained by aggregating the first detailed route and the second detailed route.

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

[0095] 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. 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 used to communicate with the third network device. The next hop information can be, for example, the port address of the first port.

[0096] In one example, the first message may be a first Ethernet message including the routing prefix of the first detailed route, next hop information, and routing prefix of the aggregated route. In another example, the first message may be a routing advertisement message, i.e., a BGP update message.

[0097] 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.

[0098] The embodiments of the present application do not specifically limit the extended group attribute, which can be any 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 route announcement message is used to carry the routing prefix of an unavailable detailed route (i.e., the routing prefix of the first detailed route).

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

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

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

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

[0103] 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 route field 412 carries the routing prefix of the aggregate route, 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 route.

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

[0105] It should be noted that FIG4 is for understanding some fields of the routing advertisement message shown in this solution. The routing advertisement message may also include other fields, which are not specifically limited in the embodiment of the present application.

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

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

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

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

[0110] 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 receiving the first message, the third network device 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 a routing 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 a locally stored routing table entry.

[0111] 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.

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

[0113] 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. The second port is a port on the fourth network device used to communicate with the third network device. This means that when the third network device forwards traffic that matches the routing prefix corresponding to the aforementioned first detailed route, it can forward it through the first network device or the fourth network device. In this case, to avoid traffic interruption caused by the third network device forwarding the traffic to the first network device, 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 traffic that matches 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.

[0114] 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, and the fourth network device is 2-7. 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. The second routing table entry is shown in Table 1 below:

[0115] Table 1

[0116] 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. This means that when the third network device forwards traffic that matches the routing prefix corresponding to the aforementioned first detailed route, it can only forward it through the first network device. In this case, once the third network device receives traffic that matches 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 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 used to communicate with the fifth network device, and send the second message 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.

[0117] 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.

[0118] Accordingly, after receiving the second message, the fifth network device can locally search for a 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 indicates the third port and the fourth port, and 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 forward it through either the third network device or the sixth network device. In this case, 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.

[0119] 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:

[0120] Table 2

[0121] In one example, considering that when a network failure occurs, operations and maintenance personnel will troubleshoot the failure and implement appropriate treatment measures to recover from the failure. Therefore, in order to reduce the number of routing table entries maintained by the network device, the third network device may further set a certain lifecycle for the second routing table entry, and delete the second routing table entry at the end of the lifecycle. The embodiments of the present application do not specifically limit the specific value of the lifecycle; the lifecycle may be determined, for example, based on the time it takes to recover from the failure.

[0122] In one example, before executing S101, the first network device may further 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 introduces the information processing method provided in the embodiment of the present application. Next, in combination with the network architecture shown in Figure 1, the specific application of the information processing method provided in the present application under different fault scenarios is introduced.

[0125] Refer to Figure 5a, which is a schematic diagram of a fault scenario provided in an embodiment of the present application. As shown in Figure 5a, 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] Referring to FIG5b, FIG5b is another schematic diagram of a fault scenario provided by an embodiment of the present application. As shown in FIG5b, network device 2-1 fails, which causes the link between network device 2-5 and network device 2-1, and the link between network device 2-6 and network device 2-1 to fail. Then, 2-5 can generate a routing announcement message 1 and send it to network devices 3-1 and 3-3. Accordingly, 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 network devices 3-2 and 3-4. Accordingly, 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] Regarding Figures 5a and 5b, the specific structure of the routing announcement messages involved (such as routing announcement message 1 and routing announcement message 2) can be understood in conjunction with Figure 4. Figures 5a and 5b are only simple examples and do not constitute a limitation on the embodiments of the present application.

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

[0129] 6 , which is a schematic diagram of the structure of an information processing device provided in an embodiment of the present application. The information processing device 600 shown in FIG6 can be applied to a first network device to execute the steps performed by the first network device provided in the above method embodiment, for example, executing S101-S103 above.

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

[0131] 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, the first message including a route prefix and next hop information of the first specific route, and a route prefix of an aggregated route, the aggregated route corresponding to the first specific route and the second specific route, the second specific route being available, and the next hop information indicating a first port, where the first port is a port on the first network device used for communication 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, 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, the first specific 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.

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

[0137] In a possible implementation, 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.

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

[0139] 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 aggregate route.

[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] Referring to Figure 7, which is a schematic diagram of the structure of another information processing device provided in an embodiment of the present application, the information processing device 700 shown in Figure 7 can be applied to a third network device to execute the steps provided by the third network device in the above method embodiment, for example, executing S104-S106 above.

[0143] The information processing device 700 shown in FIG7 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 specific route, and a route prefix of an aggregated route, where the aggregated route corresponds to the first specific route and a second specific route, where the first specific route is unavailable, the first specific route is a route sent by a second network device to the first network device, and 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 for communicating 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 the fourth network device used to communicate 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 one possible implementation, the processing unit 702 is further 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, the first specific 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.

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

[0149] In a possible implementation, 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.

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

[0151] 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 aggregate route.

[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 aforementioned information processing devices 600 and 700 may be the structure shown in FIG8 , which is a schematic diagram of the structure of a device provided in an embodiment of the present application.

[0155] As shown in Figure 8 , device 800 includes a processor 810, a communication interface 820, and a memory 830. The number of processors 810 in device 800 may be one or more, and Figure 8 illustrates a single processor as an example. In the embodiment of the present application, processor 810, communication interface 820, and memory 830 may be connected via a bus system or other means, and Figure 8 illustrates a connection via bus system 840 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 an 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] Memory 830 may include volatile memory, such as random-access memory (RAM); non-volatile memory, such as flash memory, a hard disk drive (HDD), or a solid-state drive (SSD); or a combination of the aforementioned types of memory. Memory 830 may, for example, store routing table entries corresponding to route prefixes of route aggregation.

[0158] Optionally, the memory 830 stores an operating system and programs, executable modules or data structures, or subsets thereof, or extended sets thereof, wherein the programs 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 can read the programs in the memory 830 to implement the information processing method provided in the embodiment of the present application.

[0159] The bus system 840 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus system 840 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in Figure 8, but this 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 run on a computer, enable the computer to execute the information processing method provided in the above embodiment.

[0160] An embodiment of the present application further provides a computer program product comprising instructions or a computer program, which, when executed on a computer, enables the computer to execute the information processing method provided in the above embodiment.

[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," and the like (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequential sequence. It should be understood that the terms used in this manner are 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, e.g., a process, method, system, product, or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0163] Those skilled in the art will 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 this 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 merely illustrative. For example, the division of units is only a logical business division. In actual implementation, there may be other division methods, such as 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 interface, device or unit, which can be electrical, mechanical or other forms.

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

[0166] In addition, each business unit in each embodiment of the present application can be integrated into a processing unit, each unit can exist physically separately, or two or more units can be integrated into a single unit. The above-mentioned integrated units can be implemented in the form of hardware or 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, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0168] Those skilled in the art will appreciate that, in one or more of the above examples, the services described herein can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these services can be stored on 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, including any medium that facilitates the transmission of computer programs from one location to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0169] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods 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, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. 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.

25. A computer program product, characterized in that The invention comprises a computer program which, when executed on a processor, executes the method according to any one of claims 1 to 19.

Images