CN106789664B - Route aggregation method and device - Google Patents
Route aggregation method and device Download PDFInfo
- Publication number
- CN106789664B CN106789664B CN201610188077.5A CN201610188077A CN106789664B CN 106789664 B CN106789664 B CN 106789664B CN 201610188077 A CN201610188077 A CN 201610188077A CN 106789664 B CN106789664 B CN 106789664B
- Authority
- CN
- China
- Prior art keywords
- route
- reflector
- aggregated
- aggregation
- identification sequence
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
Abstract
The embodiment of the invention discloses a route aggregation method and a device, which are applied to routing equipment, and the method comprises the following steps: receiving a route aggregation request, wherein the route aggregation request comprises a destination address of an aggregation route required to be generated; generating the aggregated route; and determining a route to be aggregated from a route information table according to the destination address of the aggregated route, and determining a reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated. By applying the technical scheme provided by the embodiment of the invention, the problem of routing loops or routing black holes generated during routing aggregation is avoided.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method and an apparatus for route aggregation.
Background
In the internet, in order to prevent a route in an AS (Autonomous system) from forming a routing loop, a routing device cannot be further transferred to an IBGP (Internal Border Gateway Protocol) peer after receiving the route from the IBGP peer, that is, the route can only propagate one hop between the IBGP peers, and in order to ensure connectivity between the IBGP peers, a full connection relationship needs to be established between the IBGP peers. Assuming that there are n routing devices in an AS, the number of BGP (Border Gateway Protocol) neighbor connections that should be established is n (n-1)/2, AS shown in fig. 1, where there are 4 routing devices in the AS100, and 6 BGP neighbor connections need to be established.
With the increase of the AS, the number of the routing devices is too large, the more the number of the established BGP neighbor connections is, the more the routing information stored in the routing information table in the routing device is, at this time, one routing device is set AS a reflector, and the BGP neighbor connections are established between the reflector and other routing devices, so that the number of BPG neighbor connections that need to be established between other routing devices is reduced, AS shown in fig. 2, there are 4 routing devices in the AS100, and the RTB is a reflector, and only 3 BGP neighbor connections need to be established. However, AS the AS becomes more and more complex, the number of routing devices increases, the number of routes that each routing device needs to obtain is still large, and a large amount of network resources are also occupied in the process of transferring the routes.
In the prior art, a method for performing route aggregation on routes including destination addresses in a certain range is adopted to aggregate the routes, so that the routing equipment only needs to send the aggregated routes. However, when the route aggregation is performed in the routing device, the aggregated route is different from the original route attribute, and since the access priority of the aggregated route is higher than the priority of other routes, the aggregated route replaces other routes when accessing an external network or other routing devices, and thus, the lost route attribute causes a route loop or a route black hole in the AS.
Disclosure of Invention
The embodiment of the invention discloses a route aggregation method and a device, which are used for avoiding generating a route loop or a route black hole.
In order to achieve the above object, an embodiment of the present invention discloses a route aggregation method applied to a routing device, where the method includes:
receiving a route aggregation request, wherein the route aggregation request comprises a destination address of an aggregation route required to be generated;
generating the aggregated route;
and determining a route to be aggregated from a route information table according to the destination address, and determining a reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated.
In a specific implementation manner of the present invention, the determining a reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated includes:
determining a target reflector identifier, wherein the target reflector identifier is a reflector identifier which is contained in the reflector identifier sequence of the route to be aggregated and is not contained in the reflector identifier sequence of the aggregated route;
adding the target reflector identification to a sequence of reflector identifications for the aggregate route.
In a specific implementation manner of the present invention, the method further includes:
and generating a static route aiming at the aggregation route according to the destination address, and storing the static route, wherein a reflector identification sequence of the static route is empty.
In a specific implementation manner of the present invention, after determining the reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated, the method further includes:
and sending the aggregation route to a reflector in communication connection with the routing equipment, so that the reflector sends the aggregation route to other routing equipment under the condition that a preset sending condition is met.
In order to achieve the above object, an embodiment of the present invention further discloses a routing aggregation apparatus, which is applied to a routing device, and the apparatus includes:
a receiving module, configured to receive a route aggregation request, where the route aggregation request includes a destination address of an aggregation route that needs to be generated;
a first generating module, configured to generate the aggregated route;
and the determining module is used for determining the route to be aggregated from the route information table according to the destination address and determining the reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated.
In a specific implementation manner of the present invention, the determining module includes:
the first determining submodule determines a route to be aggregated from a route information table according to the destination address;
a second determining submodule, configured to determine a target reflector identifier, where the target reflector identifier is a reflector identifier that is included in the sequence of reflector identifiers of the routes to be aggregated and is not included in the sequence of reflector identifiers of the aggregated routes;
an adding submodule, configured to add the target reflector identification to a reflector identification sequence of the aggregate route.
In a specific implementation manner of the present invention, the apparatus further includes: a second generation module to:
and generating a static route aiming at the aggregation route according to the destination address, and storing the static route, wherein a reflector identification sequence of the static route is empty.
In a specific implementation manner of the present invention, the apparatus further includes: a sending module configured to:
and sending the aggregation route to a reflector in communication connection with the routing equipment, so that the reflector sends the aggregation route to other routing equipment under the condition that a preset sending condition is met.
As can be seen from the above, in the embodiment of the present invention, after receiving a route aggregation request, a routing device generates an aggregation route, determines a route to be aggregated from a route information table according to a destination address of the aggregation route that needs to be generated and is included in the route aggregation request, and determines a reflector identification sequence of the aggregation route according to the reflector identification sequence of the route to be aggregated, thereby avoiding problems of a route loop and a route black hole when generating the aggregation route.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of a fully connected architecture within an AS;
FIG. 2 is a schematic view of a connection structure including a reflector in an AS;
fig. 3 is a schematic flow chart of a route aggregation method according to an embodiment of the present invention;
FIG. 4 is a schematic view of another connection structure including a reflector in an AS;
fig. 5 is a schematic flow chart of another route aggregation method according to an embodiment of the present invention;
fig. 6 is a schematic flow chart of another route aggregation method according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a route aggregation apparatus according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another route aggregation apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of another route aggregation device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The present invention will be described in detail below with reference to specific examples.
Referring to fig. 3, fig. 3 is a flowchart of a route aggregation method, applied to a routing device, provided in an embodiment of the present invention, where the method includes the following steps:
s301: receiving a route aggregation request;
here, the route aggregation request includes a destination address of an aggregated route to be generated. The routing device is not limited to a router, and includes other devices having a routing function.
In a specific implementation manner of the present invention, a route aggregation command input by a user on a control device generates a corresponding route aggregation request (the route aggregation request includes information such as a destination address and a subnet mask of an aggregated route that needs to be generated), and issues the route aggregation request to a routing device, where the routing device performs route aggregation according to the destination address and the subnet mask.
Specifically, after a user inputs a route aggregation command "aggregate 1.1.1.0255.255.255.0 detail-reserved", a route aggregation request is generated, and the routing device receives the route aggregation request and learns that the destination address of the aggregation route to be generated is 1.1.1.0/24.
S302: generating an aggregation route;
s303: and determining a route to be aggregated from the route information table according to the destination address of the aggregated route, and determining a reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated.
The route information table is used to store a route, where the route includes a destination address and a route attribute, for example, the route attribute may include a reflector identification sequence used to record a reflector in the AS system, and the reflector is used to reflect the route.
In practical application, the routing device stores the received route sent by the reflector, the route sent to the reflector, or the route forwarded to other routing devices as the reflector in the routing information table of the routing device, and when the routing device sends or forwards the route to other routing devices or reflectors, the routing device can determine an access path according to the route stored in the routing information table, and send or forward the route according to the determined access path.
In addition, a route aggregation rule is set in the routing device, such as: all routes with destination addresses contained in a certain preset network segment are determined as to-be-aggregated routes, for example, 1.1.1.1/32, 1.1.1.2/32 and 1.1.1.0/24 are contained in the network segment of 1.1.1.0/24, and then the routes can be aggregated into an aggregated route with the destination address of 1.1.1.0/24.
Specifically, after receiving the route aggregation request, the routing device determines a route to be aggregated from the route information table according to a destination address of the aggregated route and a route aggregation rule set in the routing device. According to the assumption in step S301 that the destination address of the aggregated route is 1.1.1.0/24, the route aggregation rule is to determine all routes whose destination addresses are included in 1.1.1.0/24 segments as the routes to be aggregated, and if three routes whose destination addresses are 1.1.1.1.0/24, 1.1.1.1/32, and 1.1.1.2/32 are stored in the route information table of the routing device, and the destination addresses of the three routes are all included in 1.1.1.0/24 segments, it can be determined that the routes to be aggregated are 1.1.1.0/24, 1.1.1.1/32, and 1.1.1.2/32.
It should be noted that the destination address of one aggregated route may correspond to multiple routes.
In practical application, each reflected route includes a reflector identification sequence, and when a reflector (the reflector is identified as a) receives a route and sends the route to other routing devices, its own reflector identification a is added to the reflector identification sequence of the route, so that after the reflector receives a route a, if it is found that a included in the reflector identification sequence of the route a is the same as its own reflector identification, the route a is rejected from being sent to other routing devices, the route a is discarded, and the route a is rejected from being written into a routing information table of the reflector, so as to avoid the generation of routing loops and routing black holes in the network. In addition, in practical application, the reflector identification sequence of a route is used to record the identification of the reflector reflecting the route, and the reflector identification sequence may be set to include a plurality of reflector identifications, which may be grouped together to correspond to a route.
In a specific implementation manner of the present invention, the reflector identifier is an identifier capable of uniquely representing one reflector, such as: the IP address of the interface of the routing equipment and the like, so that the normal forwarding of the route cannot be influenced because the reflector identifications of the two reflectors are the same.
If the obtained reflector identification sequences of the three routes to be aggregated are: the reflector identification sequence of the route with the destination addresses of 1.1.1.0/24 and 1.1.1.1/32 is {10.1.1.2}, and the reflector identification sequence of the route with the destination address of 1.1.1.2/32 is {10.1.1.2, 10.1.1.3}, so that after the aggregation route with the destination address of 1.1.1.0/24 is generated, the reflector identification sequence of the aggregation route can be determined to be {10.1.1.2, 10.1.1.3 }. In this case, the reflector identification sequence of the aggregated route does not lose any reflector identification sequence of the route to be aggregated, so that the problem of generating routing loops or routing black holes in the network is avoided.
In a specific implementation manner of the present invention, the method for route aggregation may further include:
sending the aggregation route to a reflector in communication connection with the routing device, judging whether a reflector identification sequence of the aggregation route contains a reflector identification of the aggregation route after the reflector receives the aggregation route, if so, refusing to store the aggregation route in a route information table of the reflector and not forwarding the aggregation route, if not, reserving the aggregation route, storing the aggregation route in the route information table of the reflector, adding the reflector identification of the aggregation route in the reflector identification sequence of the aggregation route, and then sending the aggregation route to the routing device. Therefore, other routing equipment in the network can learn the aggregation route, and routing loops and routing black holes are avoided.
Specifically, AS shown in fig. 4, the AS100 includes a plurality of routing devices, wherein three routing devices RTA, RTB and RTC are shown by way of example only, where RTB is a reflector, the reflector of RTB is identified AS 10.1.1.2, and the routing information table on RTA, RTB and RTC is shown in table 1.
TABLE 1
At this time, after an aggregation route with a destination address of 1.1.1.0/24 is generated on the RTC, according to the reflector identification sequences of the three routes with the destination addresses of 1.1.1.0/24, 1.1.1.1/32 and 1.1.1.2/32, the reflector identification sequence of the aggregation route is determined to be {10.1.1.2, 10.1.1.3 }. When the RTC sends the aggregation route to the RTB, the RTB refuses to store and forward the aggregation route when finding that the reflector identification sequence of the aggregation route contains the reflector identification of the RTB, thereby avoiding the generation of a route loop. In addition, the aggregation route is not stored in the RTB, so that when the RTB accesses 1.1.1.0/24, the access message can be transmitted to the RTA according to the next hop address 10.1.1.1.1 of the route with the stored destination address of 1.1.1.0/24, and then the RTA transmits the access message out, so that the problem that the access message cannot be normally transmitted out due to the fact that the aggregation route loses the reflector identification sequence is avoided, and the problem of routing black holes is avoided.
By applying the embodiment shown in fig. 3, after receiving the route aggregation request, the routing device generates an aggregation route, determines a route to be aggregated from the route information table according to a destination address of the aggregation route to be generated, which is included in the route aggregation request, and determines a reflector identification sequence of the aggregation route according to the reflector identification sequence of the route to be aggregated, thereby avoiding problems of route loops and route black holes when generating the aggregation route.
Referring to fig. 5, fig. 5 is a flowchart illustrating another route aggregation method provided in the embodiment of the present invention, and is applied to a routing device, in the method, step S303 may include the following steps:
s3031: determining a route to be aggregated from a route information table according to a destination address of the aggregated route;
s3032: determining a target reflector identification;
here, the target reflector identification is a reflector identification that is included in the reflector identification sequence of the route to be aggregated and is not included in the reflector identification sequence of the aggregated route.
Assuming that the reflector identification sequence of the aggregation route is {10.1.1.2}, and the reflector identification sequence of the route to be aggregated is {10.1.1.2, 10.1.1.3}, at this time, the reflector identification 10.1.1.3 in the reflector identification sequence is not included in the reflector identification sequence of the aggregation route, so that it can be determined that {10.1.1.3} is the target reflector identification.
S3033: the target reflector identification is added to the reflector identification sequence of the aggregate route.
Specifically, when the aggregation route is just generated, the reflector identification sequence of the aggregation route is empty, at this time, the reflector identification sequence of the aggregation route is compared with the determined reflector identification sequence of the route to be aggregated, and when it is determined that a reflector identification in the reflector identification sequence of the route to be aggregated is not included in the reflector identification sequence of the aggregation route, the reflector identification is determined as a target reflector identification, and the target reflector identification is added to the reflector identification sequence of the aggregation route.
And then, when a route to be aggregated is determined again, the process is circularly carried out until all the routes in the route information table are traversed.
Each route comprises a reflector identification sequence, and if the reflector identification sequences of each route are the same, the reflector identification sequences of the aggregated routes are finally the same as the reflector identification sequence of any route to be aggregated.
As in the first two routes on the RTC in table 1, after the aggregation route with the destination address of 1.1.1.0/24 is generated, the reflector identification sequences of the route a to be aggregated with the destination address of 1.1.1.0/24 and the route B to be aggregated with the destination address of 1.1.1.1/32 are both {10.1.1.2}, so that it can be determined that the reflector identification sequence of the aggregation route with the destination address of 1.1.1.0/24 is {10.1.1.2 }.
However, if the reflector identification sequences of the routes to be aggregated are not identical, it is necessary to traverse the reflector identification in each of the reflector identification sequences of the routes to be aggregated to determine the reflector identification sequence of the aggregated route. As shown in the three routes of the RTC in table 1, if the route to be aggregated also includes the route C to be aggregated with the destination address of 1.1.1.2/32, and the reflector id sequence of the route C to be aggregated is {10.1.1.2, 10.1.1.3}, it can be determined that the reflector id sequence of the route to be aggregated is {10.1.1.2, 10.1.1.3 }.
In a specific implementation manner, the determining the target reflector identifier and adding the target reflector identifier to the reflector identifier sequence of the aggregation route may be:
s1, searching a routing information table according to the destination address of the aggregation route;
s2, determining a route to be aggregated, and comparing the reflector identification sequence of the route to be aggregated with the reflector identification sequence of the aggregated route;
s3, if the reflector identification sequence of the route to be aggregated has the reflector identification which is not contained in the reflector identification sequence of the aggregated route, the reflector identification is used as a target reflector identification, the target reflector identification is added into the reflector identification sequence of the aggregated route, and S5 is executed;
s4, if no reflector identifier not included in the reflector identifier sequence of the aggregation route exists in the reflector identifier sequence of the route to be aggregated, executing S5;
s5, judging whether the routing information table is traversed or not; if not, go to S1; if so, the polymerization is complete.
Specifically, as described above, after the aggregation route is generated, the route to be aggregated is searched for item by item in the route information table. And when the route X to be aggregated is matched, comparing the reflector identification sequences of the aggregated route and the route X to be aggregated. When it is determined that the reflector identification sequence of the aggregate route does not contain the reflector identification 10.1.1.2 in the reflector identification sequence of the route X to be aggregated, the reflector identification {10.1.1.2} of the route X to be aggregated is the target reflector identification, and the reflector identification 10.1.1.2 is added to the reflector identification sequence of the aggregate route. And continuously searching the routing information table, matching a route, and if the route is the route Y to be aggregated, comparing the reflector identification sequence {10.1.1.2} of the route Y to be aggregated with the reflector identification sequence {10.1.1.2} of the aggregation route, wherein the reflector identification sequence of the route Y to be aggregated is the same as the reflector identification sequence of the aggregation route, and not operating. Continuing to search the routing information table, matching a route, and comparing the reflector identification sequence {10.1.1.2, 10.1.1.3} of the route Z to be aggregated with the reflector identification sequence {10.1.1.2} of the aggregated route, wherein the reflector identification 10.1.1.3 in the reflector identification sequence of the route Z to be aggregated is not included in the reflector identification sequence of the aggregated route, but the reflector identification 10.1.1.2 in the reflector identification sequence of the route Z to be aggregated is included in the reflector identification sequence of the aggregated route, determining that {10.1.1.3} is a target reflector identification, adding the 10.1.1.3 reflector identification to the reflector identification sequence of the aggregated route, wherein the reflector identification sequence of the aggregated route is {10.1.1.2, 10.1.1.3}, no other route exists in the routing information table, and the route aggregation is completed, and the reflector identification sequence of the aggregated route is { 10.1.1.1.2, 10.1.3 }, and the reflector identification sequence of the aggregated route is 10.1.1.1.1.3 }, and the reflector identification sequence of the aggregated route is 10.1.1.1.1.
Referring to fig. 6, fig. 6 is a flowchart illustrating another route aggregation method provided in the embodiment of the present invention, and is applied to a routing device, where the method may further include the following steps:
s304: and generating a static route aiming at the aggregation route according to the destination address of the aggregation route, and storing the static route.
Wherein the reflector identification sequence of the static route is empty. Specifically, the destination address of the static route is the same as the destination address of the aggregated route.
In practical applications, after a routing device performs route aggregation, the routing device is likely to generate a black hole for the route, as in step S303, an aggregated route is generated on the RTC, the destination address of the aggregated route is 1.1.1.0/24, the next hop address is the local address 127.0.0.0 of the RTC, thus, if no static route is set on the RTC, then, when the RTC accesses 1.1.1.0/24, the next hop address is obtained as 127.0.0.0 from the aggregated route 1.1.1.0/24, according to the next hop address, the access message is directly discarded after being sent to the CPU of the local machine, so that the RTC cannot correctly access 1.1.1.0/24, and other routing equipment of the aggregation route is received and stored, when the access is 1.1.1.0/24, the access message is sent to the RTC, the RTC discards the access message, other routing devices A also do not have correct access to 1.1.1.0/24, thus creating a black hole on the RTC.
In order to avoid the black hole on the routing device, a static route which is the same as the destination address of the aggregated route can be set on the routing device, so that the routing device can access the destination address according to the static route. For example, a static route is generated on the RTC according to 1.1.1.0/24, a reflector identification sequence of the static route is null, a next hop address is an outgoing interface address 20.1.1.2 of the RTB communicatively connected to the RTC, when the RTC or other routing device a accesses 1.1.1.0/24, the RTB can be reached through the static route, the RTA can be reached through the next hop address 10.1.1.1, and finally the RTC flows to an external network through the RTA, thereby avoiding the generation of black holes on the RTC.
By applying the embodiment shown in fig. 6, the routing device generates a static route for the aggregated route according to the destination address of the aggregated route, and stores the static route, thereby avoiding the problem of black holes in the route due to the aggregated route in the routing device.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a route aggregation device according to an embodiment of the present invention, which is applied to a routing device, and the device includes:
a receiving module 701, configured to receive a route aggregation request, where the route aggregation request includes a destination address of an aggregation route that needs to be generated;
a first generating module 702, configured to generate the aggregated route;
a determining module 703, configured to determine, according to the destination address, a route to be aggregated from a route information table, and determine, according to the reflector identification sequence of the route to be aggregated, a reflector identification sequence of the aggregated route.
In a specific implementation manner of the present invention, the route aggregation apparatus may further include: a route transmission module (not shown in fig. 7);
and the sending module is used for sending the aggregation route to a reflector in communication connection with the routing equipment, so that the reflector sends the aggregation route to other routing equipment under the condition that a preset sending condition is met.
By applying the embodiment shown in fig. 7, after receiving the route aggregation request, the routing device generates an aggregation route, determines a route to be aggregated from the route information table according to a destination address of the aggregation route that needs to be generated and is included in the route aggregation request, and determines a reflector identification sequence of the aggregation route according to the reflector identification sequence of the route to be aggregated, thereby avoiding problems of route loops and route black holes when generating the aggregation route.
Referring to fig. 8, fig. 8 is a schematic structural diagram of another route aggregation apparatus according to an embodiment of the present invention, which is applied to a routing device, where the determining module 703 may include:
the first determining submodule 7031 determines a route to be aggregated from the route information table according to the destination address;
a second determining submodule 7032, configured to determine a target reflector identifier, where the target reflector identifier is a reflector identifier that is included in the reflector identifier sequence of the route to be aggregated and is not included in the reflector identifier sequence of the aggregated route;
an adding submodule 7033 is configured to add the target reflector identification to the sequence of reflector identifications of the aggregate route.
Referring to fig. 9, fig. 9 is a schematic structural diagram of another route aggregation apparatus according to an embodiment of the present invention, and is applied to a routing device, where the apparatus may further include: a second generation module 704;
the second generating module 704 is configured to generate a static route for the aggregated route according to the destination address of the aggregated route included in the route aggregation request, and store the static route, where a reflector identification sequence of the static route is empty.
By applying the embodiment shown in fig. 9, the routing device generates a static route for the aggregated route according to the destination address of the aggregated route, and stores the static route, thereby avoiding the problem of black holes in the route due to the aggregated route in the routing device.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those skilled in the art will appreciate that all or part of the steps in the above method embodiments may be implemented by a program to instruct relevant hardware to perform the steps, and the program may be stored in a computer-readable storage medium, which is referred to herein as a storage medium, such as: ROM/RAM, magnetic disk, optical disk, etc.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (6)
1. A route aggregation method is applied to a routing device, and is characterized by comprising the following steps:
receiving a route aggregation request, wherein the route aggregation request comprises a destination address of an aggregation route required to be generated;
generating the aggregated route;
determining a route to be aggregated from a route information table according to the destination address, and determining a reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated, wherein the route information table is used for storing the route, the route comprises the destination address and a route attribute, and the route attribute comprises the reflector identification sequence used for recording reflectors in an autonomous system AS to which the routing equipment belongs;
wherein, the determining the reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated includes:
determining a target reflector identifier, wherein the target reflector identifier is a reflector identifier which is contained in the reflector identifier sequence of the route to be aggregated and is not contained in the reflector identifier sequence of the aggregated route; adding the target reflector identification to a sequence of reflector identifications for the aggregate route.
2. The method of claim 1, further comprising:
and generating a static route aiming at the aggregation route according to the destination address, and storing the static route, wherein a reflector identification sequence of the static route is empty.
3. The method according to any of claims 1-2, wherein after determining the reflector identification sequence of the aggregated route according to the reflector identification sequence of the route to be aggregated, the method further comprises:
and sending the aggregation route to a reflector in communication connection with the routing equipment, so that the reflector sends the aggregation route to other routing equipment under the condition that a preset sending condition is met.
4. A route aggregation device applied to a routing device is characterized by comprising:
a receiving module, configured to receive a route aggregation request, where the route aggregation request includes a destination address of an aggregation route that needs to be generated;
a first generating module, configured to generate the aggregated route;
a determining module, configured to determine, according to the destination address, a route to be aggregated from a route information table, and determine, according to a reflector identification sequence of the route to be aggregated, a reflector identification sequence of the aggregated route, where the route information table is used to store a route, the route includes the destination address and a route attribute, and the route attribute includes a reflector identification sequence used for recording a reflector in an autonomous system AS to which the routing device belongs;
wherein the determining module comprises:
the first determining submodule determines a route to be aggregated from a route information table according to the destination address;
a second determining submodule, configured to determine a target reflector identifier, where the target reflector identifier is a reflector identifier that is included in the sequence of reflector identifiers of the routes to be aggregated and is not included in the sequence of reflector identifiers of the aggregated routes;
an adding submodule, configured to add the target reflector identification to a reflector identification sequence of the aggregate route.
5. The apparatus of claim 4, further comprising: a second generation module to:
and generating a static route aiming at the aggregation route according to the destination address, and storing the static route, wherein a reflector identification sequence of the static route is empty.
6. The apparatus of any of claims 4-5, further comprising: a sending module configured to:
and sending the aggregation route to a reflector in communication connection with the routing equipment, so that the reflector sends the aggregation route to other routing equipment under the condition that a preset sending condition is met.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610188077.5A CN106789664B (en) | 2016-03-29 | 2016-03-29 | Route aggregation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610188077.5A CN106789664B (en) | 2016-03-29 | 2016-03-29 | Route aggregation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106789664A CN106789664A (en) | 2017-05-31 |
| CN106789664B true CN106789664B (en) | 2021-05-28 |
Family
ID=58972244
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610188077.5A Active CN106789664B (en) | 2016-03-29 | 2016-03-29 | Route aggregation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106789664B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111327545B (en) * | 2018-12-14 | 2021-10-15 | 北京金山云网络技术有限公司 | Data sending method and device, network system and switch |
| CN111865803B (en) * | 2020-06-01 | 2022-08-16 | 锐捷网络股份有限公司 | Route processing method and device based on EVPN |
| CN113824633B (en) * | 2020-06-19 | 2022-12-13 | 华为技术有限公司 | Method for releasing route in campus network and network equipment |
| CN113595907A (en) * | 2021-07-27 | 2021-11-02 | 北京天融信网络安全技术有限公司 | Aggregation method and device for issuing routing strategy based on SSLVPN |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102387068A (en) * | 2011-09-29 | 2012-03-21 | 中国人民解放军国防科学技术大学 | Extensible routing method and router of identification network |
| CN102780617A (en) * | 2012-07-20 | 2012-11-14 | 中兴通讯股份有限公司 | Method and apparatus for dividing provider-defined network location identifier (PID), and application-layer traffic optimization (ALTO) server |
| CN105391636A (en) * | 2015-10-16 | 2016-03-09 | 东南大学 | Interconnection mechanism between software defined network (SDN) subnet and IP subnet in autonomous system |
-
2016
- 2016-03-29 CN CN201610188077.5A patent/CN106789664B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102387068A (en) * | 2011-09-29 | 2012-03-21 | 中国人民解放军国防科学技术大学 | Extensible routing method and router of identification network |
| CN102780617A (en) * | 2012-07-20 | 2012-11-14 | 中兴通讯股份有限公司 | Method and apparatus for dividing provider-defined network location identifier (PID), and application-layer traffic optimization (ALTO) server |
| CN105391636A (en) * | 2015-10-16 | 2016-03-09 | 东南大学 | Interconnection mechanism between software defined network (SDN) subnet and IP subnet in autonomous system |
Non-Patent Citations (1)
| Title |
|---|
| BGP专题;无;《网络大爬虫》;20101012(第3期);第2节 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106789664A (en) | 2017-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112840606B (en) | Asynchronous object manager in a network routing environment | |
| EP2974166B1 (en) | Method and apparatus for ip/mpls fast reroute | |
| CN106789664B (en) | Route aggregation method and device | |
| TWI584194B (en) | Finding services in a service-oriented architecture (soa) network | |
| CN105721311A (en) | System and method for efficient name-based content routing using link-state information in information-centric networks | |
| CN110798403B (en) | Communication method, communication device and communication system | |
| CN106559246B (en) | Cluster implementation method and server | |
| CN105634956A (en) | Message forwarding method, device and system | |
| JP2016001922A (en) | Communication system, controller, communication method, and program | |
| US10404598B1 (en) | Managing next hop groups in routers | |
| CN111010329B (en) | Message transmission method and device | |
| CN102957573A (en) | Path detection realizing method and node | |
| EP3806404A1 (en) | Communication method, device and system for avoiding loop | |
| CN107070790B (en) | Route learning method and routing equipment | |
| CN108243102B (en) | Method for realizing fast rerouting and PE equipment | |
| US20200036784A1 (en) | Peer-to-peer network for internet of things resource allocation operation | |
| US20200336385A1 (en) | BGP Logical Topology Generation Method, and Device | |
| US20190334814A1 (en) | Path establishment method and device, and network node | |
| JP7366283B2 (en) | Route update method and device | |
| US11329880B2 (en) | Automatic route reflector configuration system | |
| CN109218182B (en) | Method and device for synchronizing routing information | |
| CN104836734A (en) | Brand new instant messaging routing method and router | |
| CN112187635B (en) | Message forwarding method and device | |
| CN108632125B (en) | Multicast table item management method, device, equipment and machine readable storage medium | |
| CN109309619A (en) | The implementation method and device of two-dimentional Routing Protocol between a kind of domain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |