WO2010072110A1 - Routing aging method, apparatus and router based on border gateway protocol - Google Patents

Abstract

A routing aging method, an apparatus and a router based on border gateway protocol (BGP) are provided. Wherein the routing aging method based on BGP includes that: after a BGP distribution point restarts, the routing request messages are transmitted to the BGP neighbors, the BGP neighbors are the BGP neighbors which have the capabilities of aging routes in the case that the neighbors do not disconnect; the BGP distribution point receives the routes that are transmitted by the BGP neighbors according to the routing request messages, and performs routing processing on the received routes; the BGP distribution point transmits the processed routes to the BGP neighbors, so that the BGP neighbors perform routing aging according to the received routes. The above scheme can realize the update of the routes stored in the BGP neighbors in the case that the neighbors do not disconnect.

Description

 Instruction manual

Title of Invention: Route aging method, device and router based on border gateway protocol

 [1] This application claims priority to Chinese Patent Application No. 200810241079.1, entitled "Route Aging Method, Device and Router Based on Border Gateway Protocol", filed on December 25, 2008, all of which is filed on December 25, 2008. The content is incorporated herein by reference.

[2] Technical field

 [3] The present invention relates to the field of network communication technologies, and specifically relates to a BGP-based route aging method, a BGP-based route aging device, and a router.

 [4] Background of the invention

 [5] Border Gateway

Protocol (Border Gateway Protocol, BGP) The distributed technology solution sets multiple BGP distribution points. For example, _BG P processes, BGP threads, etc. are set on multiple boards. All routes (such as VPN routes or IP routes) are configured. Assigned to multiple BGP distribution points for processing. The BGP distributed technology solution can reduce the routing processing pressure of a single BGP process or a thread in a BGP centralized technology solution, and avoid the performance bottleneck of BGP route processing, thereby improving the routing processing capability and routing capacity of BGP.

 [6] In the process of implementing the present invention, the inventor found that: In the BGP distributed technical solution, a plurality of different reasons may cause the BGP distribution point to restart; during the BGP distribution point restart process, the route may occur. The BGP distribution point cannot be notified to the BGP neighbors. Update the changed route. In order to ensure that the BGP neighbors store the correct routes, you can use the BGP centralized technology solution. That is, the BGP distribution point is disconnected from all BGP neighbors after the startup is complete, and the connection is re-established. After the connection is successfully re-established, The BGP neighbor re-collects the route. Although this processing method enables BGP neighbors to store correct routes, any BGP distribution point restart will affect all BGP neighbors.

 [7] Summary of the invention

[8] The embodiment of the present invention provides a BGP-based route aging method, device, and router, which may When the BGP neighbor is disconnected, the route stored in the BGP neighbor is updated.

 A route aging method provided by the embodiment of the present invention, after the BGP distribution point is restarted, the method includes:

 Sending a routing request message to the BGP neighbor, where the BGP neighbor is: a BGP neighbor having an aging routing capability when the neighbor is continuously connected;

 Receiving a route sent by the BGP neighbor according to the route request message, and performing routing processing on the received route;

 The route processed by the route is sent to the BGP neighbor, so that the BGP neighbor performs route aging according to the received route.

 The BGP-based route aging device provided by the embodiment of the present invention includes:

 The route requesting module is configured to send a route request message to the BGP neighbor after the BGP distribution point is restarted, where the BGP neighbor is a BGP neighbor having the ability to aging the route when the neighbor is continuously connected; the route processing module is configured to distribute the BGP The route received by the point is routed, and the received route is a route sent by the BGP neighbor according to the route request message;

 The route sending module is configured to: after the route processing module completes the route processing, send the route processed by the route to the BGP neighbor, so that the BGP neighbor performs route aging according to the received route.

 The router provided by the embodiment of the present invention is configured with multiple BGP distribution points, and the router includes: a route requesting module, configured to send a route request message to the BGP neighbor after the BGP distribution point is restarted, where the BGP neighbor has the neighbor a BGP neighbor that continuously aging the routing capability; and a receiving module, configured to receive a route that the BGP neighbor sends according to the routing request message;

 a routing processing module, configured to perform routing processing on a route received by the receiving module;

 The route sending module is configured to: after the route processing module completes the route processing, send the route processed by the route to the BGP neighbor, so that the BGP neighbor performs route aging according to the received route.

According to the description of the foregoing technical solution, after the BGP distribution point is restarted, the BGP distribution point can receive the route sent by the BGP neighbor and implement the route processing by sending a route request message to the BGP neighbor. The BGP distribution point sends the route to the BGP neighbor. The BGP neighbors can aging the routes that are stored on the BGP neighbors based on the received routes. Therefore, the BGP neighbors can store the correct routes and avoid the BGP neighbors. a BGP distribution point re- Startup affects all BGP neighbors.

[23] BRIEF DESCRIPTION OF THE DRAWINGS

 1 is a flowchart of a BGP-based route aging method according to Embodiment 1 of the present invention;

 2 is a schematic structural diagram of an RD-based distributed routing process according to Embodiment 2 of the present invention;

 FIG. 3 is a flowchart of a BGP-based route aging method according to Embodiment 3 of the present invention; FIG.

 4 is a schematic diagram of a BGP-based route aging apparatus according to Embodiment 4 of the present invention;

 FIG. 5 is a schematic diagram of a routing processing module according to Embodiment 4 of the present invention; FIG.

 6 is a schematic diagram of a route sending module according to Embodiment 4 of the present invention.

 [30] Mode for carrying out the invention

 [31] The specific implementation process of the BGP-based route aging method will be described below with reference to the accompanying drawings.

[32] Embodiment 1 The flow of the BGP-based route aging method is as shown in FIG. 1.

 [33] In Figure 1, step 100, at least one of the plurality of BGP distribution points is restarted. The reason for the restart of the B GP distribution point is that the resource is exhausted and the board of the BGP distribution point is abnormal. This embodiment does not limit the cause of restarting the BGP distribution point. There are various types of BGP distribution points, for example, BGP-based BGP distribution points. This embodiment does not limit the specific representation of BGP distribution points.

 [34] Step 110: After the restart of the BGP distribution point is completed, the BGP distribution point sends a route request message to the BGP neighbor when the connection between the BGP distribution point and the B GP neighbor is continuously connected. The BGP neighbors here can be: BGP neighbors with the ability to aging routes when the neighbors are continuously connected.

 [35] In a network, if all nodes are sure to have the ability to aging routes when the neighbors are constantly connected, the BGP distribution point can send routing request messages directly to all BGP neighbors after restarting. If not all the nodes are sure to have the ability to aging routes when the neighbors are continuously connected, the BGP distribution point can be selected to have the B GP neighbors with the aging route capability in the case of continuous neighbor connection. Then, The selected BGP neighbor sends a route request message.

[36] The BGP distribution point can determine, according to the pre-stored information, a BGP neighbor with the aging route capability in the case of continuous neighbor connection. The pre-stored information can be statically configured or dynamically configured. A specific example of the static configuration is as follows: The NMS sends a command to configure the BGP neighbors with the aging neighboring capability in the BGP distribution point. A specific example of dynamic configuration is: Regardless of the support of each node in the network for the above capabilities, between the BGP neighbor and the BGP distribution point It is possible to notify each other whether there is information about the aging routing capability in the case where the neighbors are constantly connected, and the BGP distribution point stores the notified information. In this way, the BGP distribution point can learn, according to the notified information, which BGP neighbors have the ability to aging the route when the neighbors are continuously connected.

[37] The process of whether the above notification has the information of aging routing capability in the case of continuous neighbor connection can be implemented in the BGP capability negotiation process. That is, the ability to aging routes while neighbors are constantly connected can be used as part of BGP capabilities. A specific example of whether the BGP neighbors have the information about the aging capability of the neighbors in the case of the neighbors are: The information about whether the BGP neighbors have the aging capability in the case of the neighbors are continuously carried in the OPEN message, and sent to the peer node. The OPEN message. The OPEN message can be extended to carry the above information in the OPEN message. The extension of the OPEN message may be to add a new field, and use the newly added field to carry the above information; or to use the existing field of the OPEN message to carry the above information, for example, by using a reserved field in the OPEN message to carry the above information. Information, etc.

[38] For BGP neighbors in the network that do not have the ability to aging routes in the case of neighbors, you can use existing methods to ensure that BGP neighbors store the correct routes, for example, between BGP distribution points and BGP neighbors. Connect, and then re-establish the connection between BGP neighbors.

 [39] In step 110, the routing request message may be implemented by using a message in the existing protocol, such as a Route-Refresh message as a routing request message; the routing request message may also be implemented by other messages, for example, by a new definition. The message is used to implement the routing request message. This embodiment does not limit the specific representation of the routing request message.

 [40] Step 120: The BGP neighbor receives the route request message, and sends a route to the BGP distribution point according to the route request message. BGP neighbors should follow BGP's route loopback prevention rules when sending routes to BGP distribution points. The message used by the BGP neighbor to send the route can be the message specified in the existing BGP. Of course, other messages can also be used, for example, the newly added message is added.

[41] After the BGP neighbor sends the route to be sent to the BGP distribution point, the BGP neighbor can send a message to the BGP distribution point. The message indicates that the BGP neighbor route is sent. The message can be called the first route sending end message. A specific example of the first route transmission end message is: End-Of-RIB message. Of course, the first route sending end message may also be other messages, for example, a message that may be added for a new definition or the like. [42] It should be noted that the BGP neighbor may also carry the first route sending end flag information in the message sending the route, and the flag information indicates that the BGP neighbor route is sent. When the route sending end message carries the route sending end flag information, the BGP neighbor may no longer send the first route sending end message.

 [43] Step 130: The BGP distribution point receives the route sent by the BGP neighbor, and performs routing processing on the received route.

 [44] After the BGP neighbor sends a route to the BGP distribution point and sends the first route transmission end message to the BGP distribution point, the BGP distribution point needs to determine whether to receive each route after receiving the route sent by each BGP neighbor. The first route sent by the BGP neighbor sends a message. After the route that is sent by each BGP neighbor and the first route is sent, the BGP distribution point processes the received route. BGP distribution points can be routed according to existing mechanisms, such as routing routes and updating routing forwarding tables. In the case that the route sent by the BGP neighbor to the BGP distribution point carries the first route sending end flag information, the BGP distribution point can also perform routing processing in a similar manner.

 [45] Step 140: After the route processing is completed, the BGP distribution point sends the route processed route to the BGP neighbor. For example, a BGP distribution point sends a route processed route to each BGP neighbor according to an egress policy.

 [46] The BGP distribution point sends a route to the BGP neighbor. The BGP neighbor sends a message to the BGP neighbor. The message indicates that the route received by the BGP neighbor is sent by the BGP distribution point and used by the BGP neighbor. Route aging processed route. This message can be referred to as a route to send start message. After a BGP neighbor has multiple ports, the BGP distribution point should send a route sending start message to multiple BGP neighbors.

 [47] The BGP distribution point can consider the address family and sub-address family information supported by the BGP neighbors in the process of sending the route to the BGP neighbor. That is, the route sent by the BGP distribution point to the BGP neighbor should belong to the BGP neighbor. Address family and sub address family. The address family and sub-address family information supported by BGP neighbors can be statically configured or dynamically configured. A specific example of static configuration is as follows: The network management device configures the address family and sub-address family information supported by BGP neighbors in the BGP distribution point by sending commands. A specific example of dynamic configuration is as follows: A BGP neighbor informs a BGP distribution point of its supported address family and sub-address family information, and a BGP distribution point stores the notified information. In this way, the BGP distribution point can learn the address family and sub-address family information supported by the BGP neighbor according to the notified information. The address family and sub-address families here are IP v6 unicast/multicast, IPv4 unicast/multicast, VPNv6 unicast/multicast, and VPNv4 unicast/multicast.

[48] BGP distribution points can be considered in the process of sending route processing to BGP neighbors. If the BGP neighbors support the routing range, the BGP distribution point can send the route range information of the aging route to the BGP neighbor and the route within the route range. Otherwise, the BGP distribution point needs to send all the routes to the BGP neighbor. Routing. Whether the BGP neighbor supports the routing range information can be statically configured or dynamically configured. A specific example of static configuration is as follows: The NMS configures BGP neighbors to support routing range information in BGP distribution points by sending commands. A specific example of dynamic configuration is as follows: A BGP neighbor notifies a BGP distribution point of its supported route range information, and a BGP distribution point stores the notified information. In this way, the BGP distribution point can learn the supported routing range of the BGP neighbor according to the notified information.

Ι π Λ∑! ,.

 [49] After the BGP neighbor supports the route range, the BGP distribution point can carry the route range information in the route start message. The route range information is used to indicate that the BGP neighbor performs route aging processing in the route range. VPN routing range information such as RD information. The above route sending start message may be a newly defined added message.

 [50] After sending the route sending start message, the BGP distribution point sends the route processed route to the BGP neighbor.

 BGP distribution points should follow BGP's route loopback prevention rules when sending routes to BGP neighbors. The message used by the BGP distribution point to send routing information may be a message specified in the existing BGP, such as a routing update message; of course, other messages may also be used, such as using a newly defined added message.

 [51] For a BGP neighbor, after the BGP distribution point sends the route to be sent to the BGP neighbor, the BGP distribution point sends a message to the BGP neighbor. The message indicates that the BGP distribution point route is sent. The message can be It is called the second route sending end message. A specific example of the second route transmission end message is: End-Of-RIB message. Of course, the second route sending end message may also be other messages, for example, a message that may be added for a new definition or the like. The second route sending end message may be the same as the first route sending end message, such as an End-Of-RIB message, or a message that is newly added.

[52] In step 140, the BGP distribution point may also carry the route sending start flag information and the route range information in the message sending the route, where the flag information indicates that the BGP distribution point starts to send the route used for route aging. When the route sending message carries the route sending start flag information and the route range information, the BGP distribution point may no longer send the route sending start message. In addition, the BGP distribution point may also carry a route to send a second end flag information in the message sending the route, and the flag information indicates BGP. The distribution point route is sent. When the message carrying the route carries the second route sending end flag information, the BGP distribution point may no longer send the second route sending end message. Here, the second route transmission end flag may be the same as the above-described first route transmission end flag.

[53] Step 150: The BGP neighbor performs route aging processing according to the received route. The route aging process includes deleting a route stored in a BGP neighbor, modifying a route stored in a BGP neighbor, and adding a new route to the BGP neighbor.

 [54] In the case that the BGP distribution point sends the second route sending end message, the BGP neighbor may perform route aging processing on the stored route according to the received route after receiving the second route sending end message. If the BGP neighbor does not receive the second route sending end message within the scheduled interval, the BGP neighbor can also perform route aging processing on the stored route based on the received route. The predetermined time interval is the maximum waiting time for the aging process of the BGP neighbors.

 [55] The BGP neighbor can start counting the maximum waiting time after receiving the route sending start message. When the accounting value does not exceed the maximum waiting time and the BGP neighbor receives the route sending end message, the BGP neighbor receives the message according to the Routes are routed to the stored routes. In the case where the calculated value exceeds the maximum waiting time and the B GP neighbor has not received the second route transmission end message sent by the BGP distribution point, the BGP neighbor is received according to the received route. A route aging the routes it stores. That is to say, in this embodiment, the condition for triggering the BGP neighbor to perform the route aging process may be the second route sending end message, or may be the maximum waiting time. If the above calculation value does not exceed the maximum waiting time, the calculation value may not reach the maximum waiting time. Therefore, the calculation value exceeds the maximum waiting time, and the calculation value should reach the maximum waiting time. In addition, the BGP neighbors can also start the maximum waiting time after receiving the route sent by the BGP distribution point.

 [56] It should be noted that, in the case that the route sent by the BGP distribution point to the BGP neighbor carries the route sending start flag information and/or the second route sending end flag information, the BGP neighbor may also use the similar manner described above. To perform route aging processing. In addition, the above maximum waiting time may be statically configured or dynamically configured. A specific example of static configuration is as follows: The NMS configures the maximum waiting time in the BGP neighbor by sending commands. A specific example of dynamic configuration is: Negotiate to determine the maximum wait time during the BGP capability negotiation process.

[57] It can be seen from the description of the first embodiment that the BGP distribution point is sent to the BGP neighbor after being restarted. Route request message, the BGP neighbor sends a route to the BGP distribution point according to the received route request message, so that the BGP distribution point can collect the route sent by the BGP neighbor after the restart, without disconnecting the BGP neighbor. Route processing: The BGP distribution point sends the route-processed route to the BGP neighbor, so that the BGP neighbor can aging the stored route based on the received route, so that the BGP neighbor does not need to be disconnected and re-established. It also enables BGP neighbors to store the correct routes, thus avoiding the problem that a BGP distribution point is restarted and affects all BGP neighbors. After the BGP neighbor sends a route to the BGP distribution point, the BGP distribution point can clearly know whether the complete route is successfully collected from the BGP neighbor. The aging process of the BGP neighbor is triggered by using the maximum waiting time and the second route to send the end message. This prevents the aging of the route due to the abnormal transmission of the second route. The BGP distribution point can easily learn which BGP neighbors have the ability to aging routes when the neighbors are continuously connected. In the BGP capability negotiation process, the aging of the routes is the same as that of the neighbors. , so that BGP neighbors can get a reasonable maximum waiting time. By carrying the routing range information in the routing start message, the BGP neighbor can perform aging processing on the route within the routing range that is responsible for the BGP distribution point.

[58] Embodiment 2: A method for implementing route aging in the case that the BGP distribution point is an RD-based BGP distribution point.

 [59] The RD-based distributed routing processing structure is shown in Figure 2.

 [60] Figure 2 includes: a route receiving and distribution module and three route storage and processing modules. A route storage and processing module is an RD-based BGP distribution point, that is, an RD-based BGP operation unit. The RD-based BGP operation unit can be called an RD-BGP operation unit, and the RD-BGP operation unit can be a process or a thread. Other ways to achieve.

 [61] The route receiving and distribution module receives VPN routes from BGP neighbors. The route receiving and distributing module shown in FIG. 2 can receive the VPN route sent by the BGP neighbor 1 and the BGP neighbor 2, and the VPN route sent by the BGP neighbor 1 can include the VPN route with the RD of 100: 1 and the RD is 200: 1 VPN route; The VPN route sent by BGP neighbor 2 can include a VPN route with an RD of 300:1.

[62] After receiving the VPN route from the BGP neighbor, the route receiving and distributing module acquires the route storage and processing module corresponding to the RD of the VPN route from the BGP neighbor. The route receiving and distribution module will receive The VPN route is sent to the acquired route storage and processing module, that is, a VPN route is sent to one of the three route storage and processing modules. The route storage and processing module receives the VPN route sent by the route receiving and distribution module, and processes the received VPN route.

In the three RD-BGP running units shown in Figure 2 above, set one of the RD-BGP running units to restart, and the restarted RD-BGP running unit should be continuously connected to all neighbors after restarting. In this case, the BGP neighbor that aging the routing capability sends a route request message. The restarted RD-BGP running unit can use the _BGP capability negotiation mechanism to learn which _BGP neighbors have the ability to aging routes when the neighbors are continuously connected, and which BGP neighbors do not have the ability to aging routes when the neighbors are continuously connected. If there are five BGP neighbors with the ability to aging the neighbors in the case of continuous neighboring, the five BGP neighbors send routes to the restarted RD-BGP running unit according to their storage routes after receiving the routing request message. Each of the five BGP neighbors needs to send an End-Of-RIB message to the restarted RD-BGP running unit after the route is sent to indicate that the BGP neighbor route is sent. The restarted RD-BGP running unit receives the routes respectively sent by the five BGP neighbors, and the restarted RD-BGP running unit determines the End-Of-RIB message sent by the five BGP neighbors respectively. Successfully collected routes from the above five BGP neighbors. The restarted RD-BGP running unit performs routing processing on all received routes, such as routing routing, updating routing forwarding tables, and the like. After the route processing is completed, the restarted RD-BGP running unit sends a route sending start message to the five BGP neighbors respectively, so that the restarted RD-BGP running unit starts to send routes to the BGP neighbors, and the BGP neighbors should be re-based. Routes sent by the RD-BGP running unit to perform route aging processing. In the case that the five BGP neighbors support the routing range, the route sending start message may carry the address family and sub-address family information supported by the BGP neighbor and the routing range information of the RD-BGP running unit. After that, the restarted RD-BGP running unit sends a routing update message to the five BGP neighbors, and the route update message carries the route processed by the route, and the route carried in the message is the restarted RD-BGP running unit. Responsible routing. After the restarted RD-BGP running unit sends a route to each BGP neighbor, it needs to send an End-Of-RIB message to indicate that the restarted RD-BGP running unit route is sent. After receiving the route sending start message, the BGP neighbor starts to calculate the maximum waiting time. If the BGP neighbor receives the E nd-Of-RIB message after the calculated value does not reach the maximum waiting time, the BGP neighbor stores the route according to the route in the received routing update message. Route aging processing is performed. If the BGP neighbor does not receive the End-Of-RIB message after the aging timer reaches the maximum waiting time, the BGP neighbor performs route aging processing on the route that is stored according to the route in the received routing update message. The route that performs the route aging process is: the address family and sub-address family supported by the BGP neighbor, and the route within the route range.

 In the third embodiment, the specific implementation process of the route aging method is shown in FIG. 3 when the BGP distribution point is an RD-based BGP distribution point.

 In Figure 3, the BGP restarter (that is, the restarted RD-based BGP distribution point) and the BGP peer (PBGP neighbor) negotiate the aging capability of the route in the case of continuous neighbor connection in the BGP capability negotiation process. Negotiate "the ability of neighbors to continuously connect to aging routes" and establish a session.

 [66] For example, a TLV field defined in the extension field of the BGP OPEN message, BGP

 The restarter and the BGP peer carry the foregoing capability negotiation information in the TLV field of the OPEN message. The capability negotiation information carried in the TLV field is used to describe whether the local end can support the foregoing capability, the address family and the sub-address family information of the aging route supported by the local end. Route range information and the maximum wait time required for BGP neighbor aging routes.

 [67] Step 2: After the BGP restarter is restarted, the BGP restarter sends a Route-Refresh message to all BGP peers with the ability of the neighbor to continuously connect to the aging route to request to update the route.

[68] Step 3: After receiving the Route-Refresh message, the BGP peer sends an update route message to the BGP restarter. After the BGP peer sends the update route message, the BGP peer sends the BGP peer to the BGP peer.

 The restarter sends an End-Of-RIB message ' to indicate that the route has been sent.

[69] Step 4: After receiving the End-Of-RIB message sent by all BGP peers, the BGP restarter starts routing the received route and updates the routing and forwarding table.

[70] Step 5. The BGP restarter sends a "route sending start message" to the BGP peer.

[71] The message format of the "route sending start message" may be extended in the message format of the Route-Refresh message specified by BGP, for example, extending a TLV field based on the Route-Refresh message.

The extended TLV field carries the RD information, and the RD information can instruct the BGP peer to perform route aging processing on the route of the specific RD. The RD information is the routing range information.

[72] Step 6, BGP

After receiving the "route sending start message", the peer records the aging flag and starts the aging process for the BGP neighbor. The aging timer set by the maximum waiting time required. A specific example of recording the aging flag is: Recording the time when the route sending start message is received, and the time is the aging flag, so that the route within the route range received before the time is required to perform route aging. Another specific example of the aging flag is: The route within the route range is marked before the route is sent, so that the marked route is a route that needs to be routed.

[73] The BGP peer can obtain the RD information from the TLV field of the "Route to send start message" and store the RD

 Ι π Λ∑! ,.

 [74] Step 7. The BGP restarter sends an update routing message to the BGP peer. After the update routing message is sent, the BGP restarter sends an End-Of-RIB message to the BGP peer. The BGP restarter should consider the address family and sub-address family information supported by the BGP peer and whether the BGP peer supports the routing range. In the case that the BGP peer supports the route range, the route carried in the update route message should belong to the address family and sub-address family supported by the BGP peer, and the route within the predetermined route range (such as the RD range supported by the BGP restarter).

 [75] Step 8. In the case that the aging timer does not reach the maximum waiting time, the BGP peer receives the End-Of-RIB message, and the BGP peer performs route aging according to the aging flag to update its route. Forwarding table. For example, a BGP peer performs route aging processing on routes that belong to the RD information before the aging flag.

 [76] From the description of the third embodiment, after the BGP restarter is restarted, the BGP peer sends a route to the BGP restarter according to the received Route-Refresh message, so that the BGP restarter can After the BGP peer is restarted, the route sent by the BGP peer is collected and the route is processed. The BGP restarter sends the route to the BGP peer to ensure that the BGP peer can receive the route according to the received route. The stored routes are aged, so that the B GP peer can store the correct route without BGP neighbors disconnecting and re-establishing the connection, thereby avoiding a BGP.

 The restarter restarts and affects all BGP neighbors.

 [77] Embodiment 4: A BGP-based route aging device is shown in FIG. 4.

[78] The route aging device in FIG. 4 includes: a route request module 400, a route processing module 410, and a route sending module 420. Optionally, the device may further include a capability negotiation module 430. [79] After the BGP distribution point is restarted, the routing request module 400, after continuously connecting the connection between the BGP distribution point and the BGP neighbor, to the B GP neighbor having the aging routing capability in the case of continuous connection of the neighbors Send a route request message. There are many types of BGP distribution points, such as BGP-based BGP distribution points.

 [80] In a network, if all nodes are sure to have the ability to aging routes when the neighbors are continuously connected, the route requesting module 400 can directly send routing requests to all BGP neighbors after the BGP distribution point is restarted. Message. If not all the nodes are sure to have the ability to aging the route when the neighbors are continuously connected, the route requesting module 400 may select the BGP with the aging route capability in the case of continuous neighbor connection after the BGP distribution point is restarted. The neighbor then sends a route request message to the selected B GP neighbor.

 [81] The route requesting module 400 may determine, according to the pre-stored information, a BGP neighbor having an aging routing capability in the case of a persistent neighbor connection. Pre-stored information can be statically configured or dynamically configured. A specific example of static configuration is as follows: The NMS sends information to BGP neighbors with aging routes in the BGP distribution point. A specific example of the dynamic configuration is as follows: The capability negotiation module 430 acquires and stores, in the BGP capability negotiation process, whether the BGP neighbor has the capability of aging the route when the neighbors are continuously connected. That is to say, the ability to aging routes in the case of neighbors can be used as part of BGP capabilities. For example, the capability negotiation module 430 obtains, from the received OPE N message, whether the BGP neighbor has the capability of aging the routing capability when the neighbor is continuously connected.

 [82] The routing request message sent by the routing request module 400 is a Route-Refresh message.

 [83] After receiving the route request message, the BGP neighbor sends a route to the BGP distribution point according to the route request message. BGP neighbors should follow the BGP route loopback prevention rules when sending routes to BGP distribution points. The message that the B GP neighbor sends the route can be the message specified in the existing BGP. Of course, other messages can also be used, for example, the newly added message is added.

[84] After the BGP neighbor sends the route to be sent to the BGP distribution point, the BGP neighbor can send a message to the BGP distribution point. The message indicates that the BGP neighbor route is sent. The message can be called the first route sending end message. A specific example of the first route transmission end message is: End-Of-RIB message. The BGP neighbor may also carry the route to send the first end flag information in the message that sends the route, as described in the foregoing embodiment. [85] The routing processing module 410 performs routing processing on the route that is sent by the BGP distribution point and is sent by the BGP neighbor according to the routing request message. In the case that the BGP neighbor sends the End-Of-RIB message, the route processing module 410 may start the routing process after receiving the End-Of-RIB message sent by each BGP neighbor at the BGP distribution point.

 After the route processing module 420 completes the routing process, the route sending module 420 sends the routed route to the BGP neighbor, so that the BGP neighbor performs route aging according to the received route.

 After the route sending module 420 needs to send a route to the BGP neighbor, the BGP neighbor may send a message to the BGP neighbor. The message indicates that the route received by the BGP neighbor is sent by the BGP distribution point. Routing. This message can be referred to as a route to send start message. After the BGP neighbors are multiple ports, the route sending module 420 should send a route sending start message to multiple BGP neighbors.

 The route sending module 420 can consider the address family and the sub-address family information supported by the BGP neighbors in the process of sending the route to the BGP neighbor. That is, the route sent by the route sending module 420 to the BGP neighbor should belong to the address supported by the BGP neighbor. Family and subaddress families. The address family and sub-address family information supported by BGP neighbors can be statically configured or dynamically configured. The dynamic configuration, such as the capability negotiation module 430, is negotiated during the BGP capability negotiation process. The capability negotiation module 430 can use the existing capability negotiation process to carry the address family and the sub-address family information supported by the BGP neighbors in the existing message to obtain the address family and the sub-address family supported by the BGP peer, as described in the foregoing embodiment. .

 [89] The route sending module 420 may consider whether the BGP neighbor supports the routing range in the process of sending the route to the BGP neighbor. If the BGP neighbor supports the routing range, the route sending module 420 may send the route that needs to perform route aging to the BGP neighbor. Range information, and routes within the routing range; otherwise, route sending module 420 sends all routes to the BGP neighbors.

 [90] Whether the BGP neighbor supports the routing range information can be statically configured or dynamically configured. A specific example of static configuration is as follows: The NMS configures BGP neighbors to support routing range information in the BGP distribution point by sending commands. The dynamic configuration, such as the capability negotiation module 430, is negotiated during the BGP capability negotiation process. The capability negotiation module 430 can use the existing capability negotiation process to carry out whether the BGP neighbor supports the routing range information in the existing message to negotiate whether the BGP neighbor supports the routing range information, as described in the foregoing embodiment.

[91] After the BGP neighbor supports the routing range, the route sending module 420 can carry in the route sending start message. The route range information is used to indicate that the BGP neighbor performs route aging processing in the route range. VPN routing range information such as RD information.

[92] The route sending module 420 sends a route to the BGP neighbor after sending the route start message. The route sending module 420 should follow the BGP route loopback prevention rules when sending routes to the BGP neighbors. The message sent by the route sending module 420 to the route may be a route update message.

[93] For a BGP neighbor, after the route to be sent is sent to the BGP neighbor, the route sending module 420 may send a message to the BGP neighbor, where the message indicates that the BGP distribution point route is complete, the message is sent. It can be called a second route transmission end message. A specific example of the second route transmission end message is: End-Of-RIB message. The route sending module 420 may also carry the route sending start flag information, the route range information, and the second route sending end flag, etc., in the message sending the route, as described in the foregoing embodiment.

[94] The BGP neighbor performs route aging processing according to the received route. Route aging processing, such as deleting a route stored in a BGP neighbor, modifying a route stored in a BGP neighbor, and adding a new route to a BGP neighbor.

 [95] The capability negotiation module 430 can also implement the negotiation of the maximum waiting time in the BGP capability negotiation process. The maximum waiting time can trigger the aging process of the BGP neighbors, as described in the foregoing embodiment.

 [96] The structure of the routing processing module 410 in the above fourth embodiment is as shown in FIG.

 [97] The routing processing module 410 of FIG. 5 includes: a determining sub-module 411 and a routing processing sub-module 412.

 [98] The determining sub-module 411 determines whether the BGP distribution point receives the first route sending end message sent by each BGP neighbor.

 [99] The routing processing sub-module 412 performs routing processing on the route received by the BGP distribution point after the judgment result of the sub-module 411 is that the BGP distribution point receives the first route sending end message sent by each BGP neighbor. The routing process performed by the routing processing sub-module 412 is as described in the above embodiment.

[100] The structure of the route sending module 420 in the above fourth embodiment is as shown in FIG. 6.

The routing module 420 of FIG. 6 includes: a message construction sub-module 421 and a transmission sub-module 422.

[102] The message construction sub-module 421 constructs a route transmission start message sent to the BGP neighbor, a message carrying the route processed route, and a second route transmission end message. The message construction sub-module 421 can be constructed first The routing start message is generated, and after the sending sub-module 422 successfully sends the route sending start message, the message carrying the route is constructed, and after the sending sub-module 422 successfully sends the message carrying the route, the second route is sent. Message. The message construction sub-module 421 may also not construct the above message in the above order. Although the message construction sub-module 421 may not construct the message in the above order, the transmission sub-module 422 shall send a start message according to the route after transmitting the message. - The message carrying the route processed route is sent in the order of the second route transmission end message. The information in the foregoing embodiment is described in the foregoing embodiment, and the information carried in the routing start message, the message carrying the routed route, and the information in the second route sending end message are not described here.

[103] Embodiment 5: A router with multiple BGP distribution points is set.

 [104] The router includes: a route request module, a receiving module, a route processing module, and a route sending module. The optional router may also include a capability negotiation module.

[105] After the routing request module detects that the BGP distribution point restarts, it continuously connects the BGP distribution point with B.

In the case of a connection between GP neighbors, a route request message is sent to a BGP neighbor having an aging route capability in the case of a neighbor continuous connection. There are various types of BGP distribution points, such as BGP-based BGP distribution points.

 [106] The routing requesting module can learn, according to the BGP capability negotiation result of the capability negotiation module, the BGP neighbor that has the aging routing capability in the case that the neighbor is continuously connected. Specifically, the description of the above embodiment.

 [107] After receiving the route request message, the BGP neighbor sends a route to the BGP distribution point according to the route request message. The receiving module receives the route sent by the BGP neighbor, and the first route sending end message.

 [108] The routing processing module performs routing processing on the route that is received by the receiving module and sent by the BGP neighbor according to the routing request message. In the case that the BGP neighbor sends an End-Of-RIB message, the routing processing module may start routing processing after the receiving module receives the End-Of-RIB message sent by each BGP neighbor.

 [109] After the route processing module completes the route processing, the route sending module sends the route processed route to the BGP neighbor, so that the BGP neighbor performs route aging according to the received route.

[110] After the route sending module needs to send a route to the BGP neighbor, it can send a message to the BGP neighbor. The message indicates that the route received by the subsequent BGP neighbor is sent by the BGP distribution point and is used for aging processing of the BGP neighbor. routing. This message can be referred to as a route to send start message. After a BGP neighbor has multiple ports, the route sending module should send a route sending start message to multiple BGP neighbors. [111] In the process of sending a route to a BGP neighbor, the route sending module can consider the address family and sub-address family information supported by the BGP neighbor. That is, the route sent by the route sending module to the BGP neighbor should belong to the address family and sub-supports supported by the BGP neighbor. Address family. The address family and sub-address family information supported by BGP neighbors can be statically configured or dynamically configured. The dynamic configuration, such as the capability negotiation module, is configured during the BGP capability negotiation process. The capability negotiation module can use the existing capability negotiation process to carry the address family and the sub-address family information supported by the BGP neighbors in the existing message to obtain the address family and the sub-address family supported by the BGP peer. The description is as follows.

 [112] In the process of sending a route to a BGP neighbor, the route sending module can consider whether the BGP neighbor supports the route range. If the BGP neighbor supports the route range, the route sending module can send the route range information of the route aging to the BGP neighbor, and Routing within the routing range; otherwise, the routing module sends all routes to the B GP neighbor.

 [113] Whether the BGP neighbor supports the routing range information can be statically configured or dynamically configured. The dynamic configuration, such as the capability negotiation module, is set during the BGP capability negotiation process. The capability negotiation module can use the existing capability negotiation process to carry the BGP neighbors to support the routing range information in the existing message to negotiate whether the BGP neighbor supports the routing range information, as described in the foregoing embodiment.

 [114] After the BGP neighbors support the route range, the route sending module may carry the route range information in the route sending start message, where the route range information is used to indicate that the BGP neighbor performs route aging processing in the route range. VPN routing range information such as RD information.

 [115] The route sending module sends a route to the BGP neighbor after sending the route start message. The routing module sends routings to BGP neighbors, which should comply with BGP's route loopback prevention rules. The message sent by the route sending module to send the route may be a route update message.

 [116] For a BGP neighbor, the route sending module sends a message to the BGP neighbor after the route to be sent is sent to the BGP neighbor. The message indicates that the BGP distribution point route is sent. The message can be sent. It is called the second route sending end message. A specific example of the second route transmission end message is: End-Of-RIB message. The route sending module may also carry the route to send the second start flag information, the route range information, and the second route sending end flag in the message sending the route, as described in the foregoing embodiment.

[117] A BGP neighbor performs route aging processing based on the received route. Route aging processing, such as deleting BGP neighbors A route stored in the BGP neighbor, a new route stored in the BGP neighbor, and a new route added to the BGP neighbor.

 [118] The foregoing capability negotiation module may also implement negotiation of the maximum waiting time in the BGP capability negotiation process.

 The maximum waiting time can trigger the aging process of the BGP neighbors, as described in the above embodiment.

The sub-modules and the like included in the routing processing module and the routing module respectively are as described in the above embodiments, and will not be described in detail herein.

 Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, all can be implemented by hardware, but in many cases, the former It is a better implementation. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

 While the invention has been described by the embodiments of the invention, it is understood that

Claims

Claim  [Claim 1] A route aging method based on the Border Gateway Protocol BGP, characterized in that BGP  After the distribution point is restarted, the method includes:  Sending a route request message to the BGP neighbor, where the BGP neighbor is: a BGP neighbor having the ability to aging the route if the neighbor is not disconnected;  Receiving a route sent by the BGP neighbor according to the route request message, and performing routing processing on the received route;  Sending the route-processed route to the BGP neighbor, so that the BGP neighbor performs route aging according to the received route. [Claim 2] The method according to claim 1, wherein before the sending the route request message to the BGP neighbor, the method further includes:  The BGP distribution point performs the BGP capability negotiation with the BGP neighbor, and in the BGP capability negotiation process, according to whether the BGP neighbors mutually notify each other whether the aging route capability is continuously connected to the neighbor, A BGP neighbor with the aging capability of the neighboring continually connected, the information of the aging capability of the BGP capability negotiation process is carried in the message of the extended BGP capability negotiation process.  [Claim 3] The method according to claim 1, wherein the receiving the BGP neighbor according to the route sent by the routing request message, and performing routing processing on the received route, specifically:  Receiving, by the BGP distribution point, the route sent by the BGP neighbor according to the route request message, and after the BGP distribution point receives the first route sending end flag or the first route sending end message sent by the BGP neighbor, Route the received route.  [Claim 4] The method of claim 1, wherein before the sending the route processed to the BGP neighbor, the method further includes: The BGP distribution point sends a route sending start message to the BGP neighbor; the sending the route processed route to the BGP neighbor includes: The BGP distribution point sends the route processed by the route to the BGP neighbor according to the address family and sub-address family information supported by the BGP neighbor, and/or the route range supported by the BGP neighbor, and sends the route after the route is sent. After the route is processed, the second route sending end flag or the second route sending end message is sent to the BGP neighbor, where the BGP neighbor supports the address family and sub-address family information, and/or the BG P neighbor. The supported route range is negotiated and determined in the BGP capability negotiation process. [Claim 5] The method according to claim 4, wherein the aging of the BGP neighbors according to the received route includes:  When the BGP neighbor receives the second route sending end flag or the second route sending end message sent by the BGP distribution point, the BGP neighbor performs route aging on the stored route according to the received route; or  When the BGP neighbor receives the route sending start message sent by the BGP distribution point, starts counting; when the calculated value does not exceed the specified maximum waiting time, and the BGP distribution point receives the BGP neighbor sending The second route sending end flag or the second route sending end message, or the counting value exceeds a specified maximum waiting time, and the B GP distribution point has not received the second route sending end flag sent by the BGP neighbor or In the case that the second route sends the end message, the BGP neighbor performs route aging on the stored route according to the received route, and the maximum waiting time is negotiated and determined in the BGP capability negotiation process. [Claim 6] A BGP-based route aging device, the device includes: a route requesting module, configured to send a route request message to a BGP neighbor after the BGP distribution point is restarted, where the BGP neighbor has A BGP neighbor that aging the routing capability when the neighbors are continuously connected; The route processing module is configured to perform routing processing on the route received by the BGP distribution point, where the received route is a route route sending module sent by the BGP neighbor according to the route request message, and is used to complete the route processing after the route processing module completes the route processing. To BGP neighbors The route that is sent to the route is processed, so that the BGP neighbor performs route aging according to the received route.  [Claim 7] The device according to claim 6, wherein the device further comprises:  The capability negotiation module is configured to perform BGP capability negotiation, and determine, according to whether the BGP neighbors have the aging route capability information in the case of the neighbors continuously connected, determine the BGP neighbors that have the aging route capability in the case of the neighbors continuously connected, and store the neighbors continuously The BGP neighbor information of the aging routing capability in the case of the BGP neighboring information of the aging capability is carried in the message of the extended BGP capability negotiation process. [Claim S] The device according to claim 6, wherein the routing processing module comprises: a determining sub-module, configured to determine whether a first route sending end flag or a first route sending end message sent by the _BGP neighbor is received;  The routing processing sub-module is configured to perform routing processing on the route received by the BG P distribution point after the determining sub-module determines that the first route sending end flag or the first route sending end message sent by the BGP neighbor is received.  [Claim 9] The device according to claim 6, wherein the route sending module comprises: a message construction sub-module, configured to construct a route sending start message sent to the BGP neighbor, and carry the message to the BGP neighbor The routed route message and the second route sending end flag or the second route sending end message sent to the BG P neighbor; the sending submodule, configured to send a route sending start message to the BGP neighbor first, and then to the B GP The neighbor sends a message carrying the route processed by the route, and then sends a second route sending end flag or a second route sending end message to the BGP neighbor.  [Claim 10] A router with multiple BGP distribution points, including:  a routing requesting module, configured to send a routing request message to the BGP neighbor after the BGP distribution point is restarted, where the BGP neighbor is a BGP neighbor having the ability to age the router when the neighbor is continuously connected; a receiving module, configured to receive a route sent by a BGP neighbor according to the routing request message The route processing module is configured to perform routing processing on the route received by the receiving module, and the route sending module is configured to: after the route processing module completes the routing process, send the route processed by the route to the BGP neighbor, so that the BGP neighbor performs the route according to the received route. Route aging.  [Claim 11] The router according to claim 10, wherein the router further includes: a capability negotiation module, configured to perform BGP capability negotiation, and according to whether the BGP neighbor reports whether the aging route is continuously connected in the neighbor relationship The capability information determines the BGP neighbors that have the aging routing capability in the case of the neighbors continuously connected, and stores the BGP neighbor information with the aging routing capability in the case of the neighbors continuously connected. In the message of the extended BGP capability negotiation process.