CN101931590A - A routing integration method and device - Google Patents

Abstract

The invention discloses a routing integration method and device, both of which can issue the routing table to obtain part of the forwarding information and export index; search the platform software table according to the export index to obtain export and packaging information; and can obtain the export and encapsulation information according to the routing table and The information in the platform software table is integrated to form complete forwarding information. The method and device of the present invention no longer need to check the hardware table twice or the second routing, and the forwarding efficiency is significantly improved; and it can ensure that two-level forwarding can also be realized on devices that do not support multiple table lookups, providing the same function Under the premise, the equipment cost is reduced.

Description

A routing integration method and device

technical field

The invention relates to the communication field, in particular to a routing integration method and device.

Background technique

With the continuous development of the Internet and corporate intranets, three-tier vpn (Visual-Private-Network, virtual private network), ECMP (Equal-Cost Multi-Path, equal-cost multi-path), FRR (Fast ReRoute, fast rerouting) And other technologies are more and more widely used. The demand for two-level ecmp/frr networking is becoming more and more common. As shown in Figure 1: a three-layer VPN network, the remote destination CE (Custom Edge Router, user edge router) performs dual-homing, and two remote PE (Provider Edge Router, operator edge router) devices perform backup and reach the primary The public network of the PE device is load-balanced, so the local PE needs to support multi-level ecmp/frr routing and forwarding. Existing technology mainly relies on searching the hardware forwarding table multiple times. First, the routing table is checked according to the destination ip address. If the exit is found to be ecmp or frr, the first-level exit index is obtained, and the hardware table is searched according to this index; if an entry is found If the specified export is still ecmp or frr, it means that it is multi-level nesting, obtain the second-level index, check the ecmp/frr hardware table again, and obtain the real export information for encapsulation and forwarding.

There is following defect in above-mentioned technical content:

1. Devices whose hardware does not support secondary table lookup or secondary routing cannot realize the routing and forwarding of the above-mentioned nested networking;

2. Devices that support multiple table lookups or routings have high hardware costs and need to look up the hardware table multiple times, obviously the forwarding efficiency is low.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a routing integration method and device, which can ensure two-level forwarding on devices that do not support multiple table lookups, and improve forwarding efficiency.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A routing integration method, the method comprising:

Issue the routing table to obtain part of the forwarding information and export index; search the platform software table according to the export index to obtain export and encapsulation information;

The complete forwarding information is integrated according to the information in the routing table and the platform software table.

The search for the platform software table is realized based on the routing table for circular search, including:

According to the index relationship from the first-level index to the second-level index, all the second-level indexes under the first-level index are searched circularly, and the platform software table is obtained accordingly.

The integrated forwarding information includes:

The egress and encapsulation information is obtained from the platform software table obtained in each cycle, combined with the partial forwarding information obtained from the routing table, and finally the complete forwarding information is integrated.

The export index is implemented based on the established index relationship, and the index relationship includes:

Index relationship from address resolution protocol arp to fast rerouting/equivalent multipath frr/ecmp/routing; index relationship from frr to routing; index relationship from ecmp to routing; index relationship from public network frr to virtual private network vpnecmp/vpn frr ; Index relationship from public network ecmp to vpn ecmp/vpn frr.

The method further includes routing update processing, providing routing update information that can be used for reference for integrating complete forwarding information;

The routing update is caused by the change of the next hop arp, or by the change of the frr group, or by the change of the ecmp group.

A routing integration device, which includes a routing table processing unit, a platform software table processing unit, and an integration unit; wherein,

The routing table processing unit is configured to deliver the routing table and obtain part of the forwarding information and egress index;

The platform software table processing unit is used to obtain the export index obtained by the routing table processing unit, and search the platform software table accordingly to obtain export and packaging information;

The integration unit is used to obtain the forwarding information obtained by the routing table processing unit and the platform software table found by the platform software table processing unit, and integrate the complete forwarding information according to the information in the obtained routing table and platform software table .

The platform software table processing unit searches for the platform software table based on a routing table for circular search; the platform software table processing unit searches for the platform software table for:

According to the index relationship from the first-level index to the second-level index, all the second-level indexes under the first-level index are searched circularly, and the platform software table is obtained accordingly.

When the integration unit integrates the complete forwarding information, it is used for:

The egress and encapsulation information is obtained from the platform software table obtained in each cycle, combined with the partial forwarding information obtained from the routing table, and finally the complete forwarding information is integrated.

The export index is implemented based on the established index relationship, and the index relationship includes:

Index relationship from arp to frr/ecmp/routing; index relationship from frr to routing; index relationship from ecmp to routing; index relationship from public network frr to vpn ecmp/vpn frr; index relationship from public network ecmp to vpn ecmp/vpn frr .

The device further includes a routing updating unit, configured to: perform routing updating and provide the integrating unit with routing updating information that can be used for reference;

The routing update is caused by the change of the next hop arp, or by the change of the frr group, or by the change of the ecmp group.

The method and device of the present invention no longer need to check the hardware table twice or the second routing, and the forwarding efficiency is significantly improved; and it can ensure that two-level forwarding can also be realized on devices that do not support multiple table lookups, providing the same function Under the premise, the equipment cost is reduced.

Description of drawings

Figure 1 is a schematic diagram of a two-level ecmp/frr networking application scenario;

Fig. 2 is the two-stage ecmp/frr routing integration flowchart of an embodiment of the present invention;

Fig. 3 is a schematic diagram of the reference relationship between address resolution protocol (arp) and frr/ecmp routing according to an embodiment of the present invention;

Fig. 4 is the flow chart of routing update caused by the change of next hop arp according to an embodiment of the present invention;

Fig. 5 is a flow chart of routing update caused by frr group changes according to an embodiment of the present invention;

Fig. 6 is a flow chart of routing update caused by ecmp group changes according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a routing integration process according to an embodiment of the present invention;

FIG. 8 is a diagram of a routing integration device according to an embodiment of the present invention.

Detailed ways

Generally speaking, the routing table can be issued through the platform software, and the platform software table can also be queried, and the complete export information can be integrated according to the routing table and platform software table, and then the integrated export information can be issued to the driver at one time to write the hardware. Table, in subsequent applications, the hardware only needs to perform a table lookup process for the hardware table to complete the two-level ecmp/frr forwarding.

The above operation idea may include the following steps:

1) The routing table is issued to obtain part of the forwarding information and egress index.

2) Search the platform software table according to the export index to obtain export and packaging information.

3) Integrating the complete forwarding information according to the information in the routing table and the platform software table.

It should be noted that the egress index includes an ecmp index or a frr index. And, if the exit index cannot be found in the platform software table, then end directly. The complete forwarding information usually includes: destination ip, mask, vpn id, physical outbound port, outbound interface index, next hop ip address, destination media access control mac, outbound label, etc.

In actual application, the specific routing integration process is shown in Figure 2, which includes the following steps:

Step 201: The upper layer protocol issues routing table addition or triggers routing update.

Step 202: Determine whether the route egress type is a common next hop, if yes, go to step 203; otherwise, go to step 204.

Step 203: Search the platform software table according to the next hop ip and the three-layer interface index, and obtain the destination mac and physical outbound port.

Step 204: Search the platform software table according to the export frr index or ecmp index, judge whether the search is successful, if successful, enter step 205; otherwise, return failure and end the process.

Step 205: Set the value of i to zero.

Step 206: Determine whether i is smaller than m, if smaller, go to step 208; otherwise, go to step 207.

Step 207: Add complete forwarding information such as routing prefix information and egress information to the driver.

Specifically, routing prefix information includes destination ip, mask, vpn id, etc., and egress information includes next-hop ip, physical outbound port, destination mac, outbound interface index, next-hop vpn id, etc.

Step 208: Determine whether there is a secondary index at the exit of the i-th next hop, if so, go to step 210; otherwise, go to step 209.

Step 209: Search the platform software table according to the ip address of the i-th next hop and the three-layer interface index, and obtain the destination mac and physical egress port.

Step 210: Search the platform software table according to the export frr index or ecmp index, and judge whether the search is successful; if the search is successful, enter step 211; otherwise, return failure and end the process.

Step 211: Set the value of j to zero.

Step 212: Judging whether j is smaller than n, if smaller, go to step 213; otherwise, go to step 215.

Step 213: Search the platform software table according to the ip address of the jth next hop and the three-layer interface index, and obtain the destination mac and physical egress port.

Step 214: Accumulate j, return to step 212.

Step 215: Accumulate i, return to step 206.

It can be seen from the above process that the lookup for the platform software table is realized based on the routing table. This gets the platform software table. Based on the above-mentioned cyclic search method, when the complete forwarding information is integrated later, the export and encapsulation information can be obtained from the platform software table obtained in each previous cycle, combined with the partial forwarding information obtained from the routing table, Finally, the complete forwarding information is integrated.

There is an index relationship between the indexes in the above process, and the above index relationship can be described by using Figure 3 in combination with the reference relationship among arp, frr/ecmp, and routing. See Figure 3. The common next-hop arp change will change the route that references it or the ecmp/frr that references it. The change of arp needs to trigger the update of related frr/ecmp and routes; If vpn frr, vpn ecmp or routing changes, related vpn frr, vpn ecmp and routing updates need to be triggered. Changes in vpn frr or vpnecmp will cause changes to the routing exits that refer to it, and related routing updates need to be triggered. Therefore, it is necessary to establish an index relationship opposite to the direction of the reference relationship: that is, the index relationship from arp to frr/ecmp/routing; the index relationship from frr to routing; the index relationship from ecmp to routing; the index relationship from public network frr to vpn ecmp/vpn frr ; Index relationship from public network ecmp to vpn ecmp/vpn frr.

The above indexes can be combined to illustrate the update relationship among routing, next-hop arp, and ecmp/frr groups.

Specifically, the protocol cannot perceive all next-hop arp changes, and the current routing integration module needs to respond to arp changes and trigger related routing update drivers. The routing update process caused by common next-hop changes is shown in Figure 4. The process shown in Figure 4 includes the following steps:

Step 401: The protocol issues an arp add, delete, or update operation.

Step 402: Determine whether the subnet route referencing the arp can be found according to the index relationship, if found, go to step 403; otherwise, go to step 404.

Step 403: Specific processing according to the operation type. For example: if it is an arp addition or update operation, integrate the complete export information and the found routing prefix information and write the driver. If it is an arp deletion operation, you can set the subnet routing exit to be sent to the CPU, and wait for the arp information to be complete before reintegrating the subnet routing exit.

Step 404: Determine whether the ecmp group referencing the arp can be found according to the index relationship, if found, go to step 405; otherwise, go to step 406.

Step 405: Perform a routing update process according to the ecmp index.

Step 406: Determine whether the frr group referencing the arp can be found according to the index relationship, if found, go to step 407; otherwise, end the process.

Step 407: Perform a routing update process according to the frr index.

The routing update process caused by the frr group change is shown in Figure 5, and the process shown in Figure 5 includes the following steps:

Step 501: Determine whether it is an frr group update operation, if yes, go to step 502; otherwise, go to step 510.

Step 502: Judging whether the platform frr software entry can be found according to the frr index, if found, go to step 503; otherwise, end the process.

Step 503: Judging whether the vpn frr or vpnecmp referring to the frr group can be found according to the index relationship, if it can be found, enter step 504; otherwise, enter step 507.

Step 504: Judging whether the platform software entry can be found according to the vpn frr/vpn ecmp index, if found, enter step 505; otherwise, enter step 507.

Step 505: Judging whether the route a referencing vpn frr or vpn ecmp can be found according to the index relationship, if it can be found, enter step 506; otherwise, enter step 507.

Step 506: integrate the complete forwarding information, and update the driver by referencing the route a of vpn frr/vpn ecmp.

Step 507: Determine whether the route b referencing the frr group can be found according to the index relationship, and enter step 508 if found.

Step 508: If it is an frr update or add operation, then integrate the complete route b information and update the driver; if it is an frr delete operation, temporarily set the exit of route b to send to the cpu, and update the driver. End this process.

Step 510: Judging whether to add operation for frr group, if yes, go to step 503; otherwise, go to step 520.

Step 520: Determine whether it is an frr group deletion operation, if yes, go to step 507; otherwise, end this process.

The routing update process caused by the ecmp group change is shown in Figure 6, and the process shown in Figure 6 includes the following steps:

Step 601: Determine whether it is an Ecmp group update operation, if yes, go to step 602; otherwise, go to step 610.

Step 602: Determine whether the platform Ecmp software entry can be found according to the Ecmp index, and if it can be found, go to step 603; otherwise, end the process.

Step 603: Judging whether the vpn frr or vpnecmp referring to the Ecmp group can be found according to the index relationship, if it can be found, enter step 604; otherwise, enter step 607.

Step 604: Judging whether the platform software entry can be found according to the vpn frr/vpn ecmp index, if found, enter step 605; otherwise, enter step 607.

Step 605: Judging whether the route a referencing vpn frr or vpn ecmp can be found according to the index relationship, if it can be found, enter step 606; otherwise, enter step 607.

Step 606: Integrate the complete route a information and update the driver.

Step 607: Determine whether the route b referencing the Ecmp group can be found according to the index relationship, and go to step 608 if it can be found.

Step 608: If it is an Ecmp update or add operation, integrate the complete information of route b and update the driver; if it is an Ecmp delete operation, temporarily set the exit of route b to be sent to the cpu, and update the driver. End this process.

Step 610: Determine whether to add an operation for the Ecmp group, if yes, go to step 603; otherwise, go to step 620.

Step 620: Determine whether it is an Ecmp group deletion operation, if yes, go to step 607; otherwise, end this process.

In combination with the above process description, it can be seen that the operation idea of routing integration in the present invention can be represented as shown in FIG. 7 . Referring to FIG. 7, FIG. 7 is a schematic diagram of a routing integration process according to an embodiment of the present invention, and the process includes the following steps:

Step 710: Deliver the routing table, and obtain part of the forwarding information and egress index in it.

Step 720: Search the platform software table according to the export index to obtain export and package information.

Step 730: Integrate into complete forwarding information according to the information in the routing table and the platform software table.

In order to ensure that the above-mentioned process and operation idea can be realized smoothly, the settings shown in Figure 8 can be performed. Referring to FIG. 8 , FIG. 8 is a diagram of a route integration device according to an embodiment of the present invention. The device includes a connected routing table processing unit, a platform software table processing unit, an integration unit, and may also include a routing update unit connected to the integration unit.

In a specific application, the routing table processing unit can issue the routing table and obtain part of the forwarding information and export index; the platform software table processing unit can obtain the export index obtained by the routing table processing unit, and search for the platform based on it. Software table, for export and packaging information. The integration unit can obtain the forwarding information obtained by the routing table processing unit and the platform software table found by the platform software table processing unit, and integrate the complete forwarding information according to the information in the obtained routing table and platform software table.

In addition, the routing updating unit can perform routing updating processing as shown in FIGS. 4 to 6 , and notify the integration unit of the processing result, so as to provide the routing updating information that can be used for reference when the integration unit integrates the complete forwarding information.

It should be noted that, for any unit in the units shown in FIG. 8 , as long as the unit needs to use the reference relationship between the arp and frr/ecmp routes to perform related operations, the reference relationship can be maintained. The specific operations that can be realized by each unit shown in FIG. 8 have been described in detail in the foregoing process, and will not be repeated here. In addition, for the traditional first-level ecmp/frr networking or common networking, the preceding process is also applicable.

In summary, no matter the method or the device, the two-level ecmp/frr routing integration technology of the present invention has the following beneficial effects compared with the prior art:

1. It is no longer necessary to check the hardware table or route twice, and the forwarding efficiency is significantly improved.

2. It is guaranteed that two-level forwarding can also be realized on devices that do not support multiple table lookups, and the device cost is reduced under the premise of providing the same function.

The above description is only a preferred embodiment of the present invention, and is not used to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included in the within the protection scope of the present invention.

Claims (10)

1. A method for route aggregation, the method comprising:

issuing a routing table to obtain part of forwarding information and an exit index in the routing table; searching a platform software table according to the export index to obtain export and packaging information;

and integrating complete forwarding information according to the information in the routing table and the platform software table.

2. The method of claim 1, wherein the lookup for the platform software table is implemented by performing a round-robin lookup based on a routing table, and comprises:

and circularly searching all the secondary indexes under the primary index according to the index relationship from the primary index to the secondary index, thereby obtaining the platform software table.

3. The method of claim 2, wherein the integrating the complete forwarding information comprises:

and acquiring export and encapsulation information from the platform software table acquired during each circulation, and finally integrating complete forwarding information by combining the partial forwarding information acquired from the routing table.

4. The method of any of claims 1 to 3, wherein the exit index is implemented based on an established indexing relationship comprising:

the index relationship from the address resolution protocol arp to the fast reroute/equal cost multipath frr/ecmp/route; frr index relationship to route; ecmp index relationship to route; the index relationship from the public network frr to the virtual private network vpnecmp/vpn frr; the index relationship of the public network ecmp to vpn ecmp/vpn frr.

5. The method of claim 4, further comprising a route update process for providing route update information for the integrated complete forwarding information to be used as a reference;

the route update is caused by a next hop arp change, or by a frr group change, or by an ecmp group change.

6. A route integration device is characterized by comprising a route table processing unit, a platform software table processing unit and an integration unit; wherein,

the routing table processing unit is used for issuing a routing table and acquiring part of forwarding information and exit indexes in the routing table;

the platform software table processing unit is used for obtaining the outlet index obtained by the routing table processing unit and searching the platform software table according to the outlet index to obtain outlet and packaging information;

the integration unit is used for obtaining the forwarding information acquired by the routing table processing unit and the platform software table searched by the platform software table processing unit, and integrating complete forwarding information according to the acquired routing table and the information in the platform software table.

7. The apparatus according to claim 6, wherein the lookup of the platform software table by the platform software table processing unit is implemented by performing a loop lookup based on a routing table; when the platform software table processing unit searches the platform software table, the platform software table processing unit is used for:

and circularly searching all the secondary indexes under the primary index according to the index relationship from the primary index to the secondary index, thereby obtaining the platform software table.

8. The apparatus of claim 7, wherein the integration unit, when integrating the complete forwarding information, is configured to:

and acquiring export and encapsulation information from the platform software table acquired during each circulation, and finally integrating complete forwarding information by combining the partial forwarding information acquired from the routing table.

9. The apparatus of any of claims 6 to 8, wherein the exit index is implemented based on an established indexing relationship comprising:

the index relationship of arp to frr/ecmp/route; frr index relationship to route; ecmp index relationship to route; the index relation from the public network frr to the vpn ecmp/vpn frr; the index relationship of the public network ecmp to vpn ecmp/vpn frr.

10. The apparatus of claim 9, further comprising a route update unit configured to: performing route updating and providing route updating information which can be used for reference for the integration unit;

the route update is caused by a next hop arp change, or by a frr group change, or by an ecmp group change.

Images