WO2012024948A1 - Procédé et appareil d'intégration de routage - Google Patents

Procédé et appareil d'intégration de routage Download PDF

Info

Publication number
WO2012024948A1
WO2012024948A1 PCT/CN2011/074318 CN2011074318W WO2012024948A1 WO 2012024948 A1 WO2012024948 A1 WO 2012024948A1 CN 2011074318 W CN2011074318 W CN 2011074318W WO 2012024948 A1 WO2012024948 A1 WO 2012024948A1
Authority
WO
WIPO (PCT)
Prior art keywords
index
routing
ecmp
platform software
frr
Prior art date
Application number
PCT/CN2011/074318
Other languages
English (en)
Chinese (zh)
Inventor
史亮
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012024948A1 publication Critical patent/WO2012024948A1/fr

Links

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

Definitions

  • the present invention relates to the field of communications, and in particular, to a route integration method and apparatus. Background technique
  • Layer 3 VPN Voice-Private-Network, Virtual Private Network
  • ECMP Equal-Cost Multi-Path
  • FRR Fast ReRoute
  • the Layer 3 VPN network the remote destination CE (Custom Edge Router) performs dual-homing
  • the remote PE Provider Edge Router
  • the public network of the PE device is load balanced.
  • the local PE needs to support multi-level ecmp/frr route forwarding.
  • the existing technology mainly relies on searching the hardware forwarding table multiple times.
  • the routing table is checked according to the destination IP address. If the egress is ecmp or frr, the first-level egress index is obtained, and the hardware table is checked according to the index; The indicated exit is still ecmp or frr, which means that it is multi-level nested, obtain the second-level index, and then check the ecmp/frr hardware table to obtain the real export information for encapsulation and forwarding.
  • the device that does not support the secondary lookup table or the secondary route cannot implement the routing and forwarding of the above nested networking.
  • the main object of the present invention is to provide a route integration method and apparatus, which can ensure two-level forwarding on a device that does not support multiple table lookups, and improve forwarding efficiency.
  • a route integration method comprising:
  • the complete forwarding information is integrated according to the information in the routing table and the platform software table.
  • the searching for the platform software table is implemented by a loop search based on a routing table, and the process of the loop search includes:
  • the index of each level under the primary index is searched step by step, and the platform software table is obtained accordingly.
  • the integration of complete forwarding information includes:
  • the egress and encapsulation information is obtained from the platform software table obtained in each loop search, and the partial forwarding information obtained from the routing table is combined, and finally the complete forwarding information is integrated.
  • the egress index is implemented based on an established index relationship, and the index relationship includes at least one of the following:
  • Address resolution protocol arp to fast reroute / equivalent multipath frr / ecmp / routing index relationship; frr to routing index relationship; ecmp to routing index relationship; public network frr to virtual private network vpn ecmp / vpn fir ⁇ index Relationship; index relationship of public network ecmp to vpn ecmp/vpn frr.
  • the method further includes routing update processing for providing routing update information that can be referenced for integrating the complete forwarding information;
  • the routing update is caused by a change in the next hop arp, or caused by a change in the frr group, or caused by a change in the ecmp group.
  • a route integration device the device includes a routing table processing unit, and a platform software table processing list Yuan, integrated unit; among them,
  • the routing table processing unit is configured to obtain partial forwarding information and an egress index in the routing table.
  • the platform software table processing unit is configured to obtain an egress index obtained by the routing table processing unit, and search for platform software according to the routing software Table, obtaining export and package information;
  • the integration unit is configured to obtain forwarding information acquired by the routing table processing unit and a platform software table found by the platform software table processing unit, and integrate the information according to the obtained routing table and the platform software table. Complete forwarding information.
  • the searching of the platform software table processing unit for the platform software table is implemented by performing a loop search based on the routing table; and the platform software table processing unit is used to: when searching the platform software table in a loop:
  • the index of each level under the primary index is searched step by step, and the platform software table is obtained accordingly.
  • 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 loop search, and the partial forwarding information obtained from the routing table is combined, and finally the complete forwarding information is integrated.
  • the egress index is implemented based on an established index relationship, and the index relationship includes at least one of the following:
  • Index relationship of arp to frr/ecmp/route index relationship of frr to route; index relationship of ecmp to route; index relationship of public network frr to vpn ecmp/vpn frr; index relationship of public network ecmp to vpn ecmp/vpn frr .
  • the apparatus further includes a routing update unit, configured to: provide the integration unit with routing update information that can be used for reference;
  • the routing update is caused by a change in the next hop arp, or caused by a change in the fa group, or caused by a change in the ecmp group.
  • the method and device of the invention no longer need to check the hardware table or the secondary route twice, and the forwarding efficiency Significantly improved; and can ensure that two-level forwarding can be implemented on devices that do not support multiple look-up tables, reducing equipment costs while providing the same functionality.
  • Figure 1 is a schematic diagram of a two-stage ecmp/frr networking application scenario
  • FIG. 2 is a flowchart of two-stage ecmp/frr routing integration according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a reference relationship between an address resolution protocol (arp) and a frr/ecmp route according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a route update caused by a change of a next hop ar according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a route update caused by a variation of a frr group according to an embodiment of the present invention
  • FIG. 6 is an ecmp according to an embodiment of the present invention
  • FIG. 1 is a schematic diagram of a route integration process according to an embodiment of the present invention
  • FIG. 8 is a diagram of a route integration apparatus according to an embodiment of the present invention. detailed description
  • the platform software can be used to deliver the routing table, and the platform software table can be queried, and the complete export information can be integrated according to the routing table and the platform software table, and the integrated export information is sent to the driver once to write the hardware.
  • the hardware only needs to perform a table lookup process for the hardware table to complete the two-stage ecmp/frr forwarding.
  • the routing table is delivered, and part of the forwarding information and the exit index are obtained.
  • the egress index includes an ecmp index or an frr index. Also, if the exit index is not found in the platform software table, it ends directly.
  • the complete forwarding information usually includes: destination ip, mask, vpn id, physical outbound interface, outbound interface index, next hop ip address, The destination media access controls mac, out tags, and so on.
  • Step 201 The upper layer protocol sends a routing table to add or trigger a route update.
  • Step 202 Determine whether the route exit type is a normal next hop, and if yes, enter the step
  • Step 203 Check the platform software table according to the next hop ip and the layer 3 interface index to obtain the destination mac and the physical outgoing port.
  • Step 204 Find the platform software table according to the export frr index or the ecmp index, and determine whether the search is successful. If successful, go to step 205; otherwise, return the failure and end the process.
  • Step 205 Set the value of i to zero.
  • Step 206 Determine whether i is less than m, if not, proceed to step 208; otherwise, proceed to step 207.
  • Step 207 Add complete forwarding information such as route prefix information and exit information to the driver.
  • the route prefix information includes the destination ip, the mask, the vpn id, and the like.
  • the egress information includes the next hop ip, the physical egress port, the destination mac, the outbound interface index, and the next hop vpn id.
  • Step 208 Determine whether there is a secondary index for the exit of the i th next hop. If yes, go to step 210; otherwise, go to step 209.
  • Step 209 Check the platform software table according to the ip address of the i-th next hop and the layer 3 interface index to obtain the destination mac and the physical egress port.
  • Step 210 Find the platform software table according to the export frr index or the ecmp index, and determine whether the search is successful. If the search is successful, go to step 211; otherwise, return the failure and end the process.
  • Step 211 Set the value of j to zero.
  • Step 212 Determine whether j is less than n, if not, proceed to step 213; otherwise, proceed to step 215.
  • Step 213 Check the platform software table according to the ip address of the jth next hop and the layer 3 interface index to obtain the destination mac and the physical outgoing port.
  • Step 214 Accumulate j, return to step 212.
  • Step 215 Accumulate i, return to step 206.
  • the search for the platform software table is implemented by a cyclic lookup based on the routing table, such as: according to the index relationship from the primary index to the multi-level index (such as the secondary index), the hierarchical search is performed under the primary index.
  • the index of each level (such as all secondary indexes), in order to obtain the platform software table.
  • the egress and encapsulation information can be obtained from the platform software table obtained in each previous loop, and combined with the partial forwarding information obtained from the routing table. The final integration of the complete forwarding information.
  • FIG. 3 illustrates the index relationship.
  • the normal next hop arp change will change the route that references it or the ecmp/frr that references it.
  • the arp change needs to trigger the relevant frr/ecmp and route update.
  • the frr/ecmp change will refer to it. If the vpn frr, vpn ecm, or route changes, the related vpn frr, vpn ecm, and route update must be triggered.
  • the vpn frr or vpn ecmp change will change the route exit that references it, and the related route update needs to be triggered.
  • index relationship of arp to frr/ecmp/route index relationship of frr to route
  • index relationship of ecmp to route index relationship of public network fir to vpn ecmp/vpn frr ; public network ecm to vpn ecmp / vpn frr index relationship.
  • the update relationship between the route, the next hop arp, and the ecmp/frr group can be described in combination with the above index.
  • the protocol can not perceive all the next-hop ar p changes required by the current routing module integrated response arp change, and triggers associated routing update the driver.
  • the route update process caused by the normal next hop change is shown in Figure 4.
  • the process shown in Figure 4 includes the following steps: Step 401: The protocol sends an arp add, delete, or update operation.
  • Step 402 Determine whether the subnet route referring to the arp can be found according to the index relationship. If yes, go to step 403; otherwise, go to step 404.
  • Step 403 Specifically processing according to the operation type. For example: If it is an arp add or update operation, the complete exit information and the found route prefix information are integrated and written. If the arp delete operation is performed, you can set the subnet route exit to the CPU and wait for the arp information to complete before re-integrating the subnet route exit.
  • Step 404 Determine whether the ecmp group referring to the aip can be found according to the index relationship. If yes, go to step 405; otherwise, go to step 406.
  • Step 405 Perform a route update process according to ecmp cable.
  • Step 406 Determine whether the frr group referring to the arp can be found according to the index relationship. If it can be found, go to step 407; otherwise, end the process.
  • Step 407 Perform a route update process according to the frr index.
  • the routing update process caused by the change of the frr group is shown in Figure 5.
  • the process shown in Figure 5 includes the following steps:
  • Step 501 Determine whether it is a frr group update operation, and if yes, go to step 502; otherwise, go to step 510.
  • Step 502 Determine whether the platform frr software entry can be found according to the frr index. If it can be found, go to step 503; otherwise, end the process.
  • Step 503 Determine whether vpn frr or vpn ecmp that references the frr group can be found according to the index relationship. If it can be found, go to step 504; otherwise, go to step 507.
  • Step 504 Determine whether the platform software entry can be found according to the vpn frr/vpn ecmp index. If it can be found, go to step 505; otherwise, go to step 507.
  • Step 505 Determine whether the route a referring to the vpn fir or the vpn ecmp can be found according to the index relationship. If it can be found, go to step 506; otherwise, go to step 507.
  • Step 506 Integrate the complete forwarding information, and update the route a reference vpn frr/vpn ecmp.
  • Step 507 Determine whether the route b referring to the frr group can be found according to the index relationship, and proceed to step 508 when it can be found.
  • Step 508 If it is a frr update or add operation, integrate the complete route b information and update the driver; if it is a frr delete operation, temporarily set the exit of the route b to the send cpu, and update the driver. End this process.
  • Step 510 Determine whether to add an operation to the frr group, if yes, go to step 503; otherwise, go to step 520.
  • Step 520 Determine whether the frr group delete operation, if yes, proceed to step 507; otherwise, end the process.
  • the route update process caused by the change of the ecmp group is shown in Figure 6.
  • the process shown in Figure 6 includes the following steps:
  • Step 601 Determine whether the Ecmp group update operation is performed. 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. If it can be found, go to step 603; otherwise, end the process.
  • Step 603 Determine whether vpn fir or vpn ecmp that references the Ecmp group can be found according to the index relationship. If it can be found, go to step 604; otherwise, go to step 607.
  • Step 604 Determine whether the platform software entry can be found according to the vpn frr/vpn ecm index. If it can be found, go to step 605; otherwise, go to step 607.
  • Step 605 Determine whether the route a referring to vpn frr or vpn ecmp can be found according to the index relationship. If it can be found, go to step 606; otherwise, go to step 607.
  • Step 606 Integrate the complete route a information and update the driver.
  • Step 607 Determine whether the route b that references the Ecmp group can be found according to the index relationship. And when it can be found, it proceeds to step 608.
  • Step 608 If it is an Ecmp update or add operation, integrate the information of the complete route b and update the driver; if it is an Ecmp delete operation, temporarily set the exit of the route b to the send cpu, and update the driver. End this process.
  • Step 610 Determine whether to add an operation to the Ecmp group. If yes, go to step 603; otherwise, go to step 620.
  • Step 620 Determine whether the Ecmp group delete operation is performed. If yes, go to step 607; otherwise, end the process.
  • FIG. 7 is a schematic diagram of a route integration process according to an embodiment of the present invention, where the process includes the following steps:
  • Step 710 The routing table is delivered, and part of the forwarding information and the egress index are obtained.
  • Step 720 Find the platform software table according to the egress index, and obtain the export and encapsulation information.
  • Step 730 Integrate the complete forwarding information according to the information in the routing table and the platform software table.
  • FIG. 8 is a diagram of a route integration apparatus according to an embodiment of the present invention.
  • the apparatus includes an associated routing table processing unit, a platform software table processing unit, and an integration unit, and may further include a route update unit connected to the integration unit.
  • the routing table processing unit can issue a routing table and obtain part of the forwarding information and the egress index; the platform software table processing unit can obtain the egress index obtained by the routing table processing unit, and search the platform accordingly.
  • the merging 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 obtained routing table and the information in the platform software table.
  • the route update unit is capable of performing route update processing as shown in FIGS. 4 to 6, and The processing result is notified to the integration unit, and the integration unit provides routing update information that can be used for reference when integrating the complete forwarding information.
  • the two-stage ecmp/frr routing integration technique of the present invention has the following beneficial effects as compared with the prior art, whether it is a method or a device:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention porte sur un procédé et un appareil d'intégration de routage, dans lesquels des informations d'acheminement partielles et un indice de sortie dans la table de routage peuvent être acquis ; une table logicielle de plateforme est consultée conformément à l'indice de sortie de façon à acquérir les informations de sortie et d'encapsulation, et les informations obtenues dans la table de routage sont intégrées aux informations obtenues dans la table logicielle de plateforme afin d'acquérir les informations d'acheminement complètes. Le procédé et l'appareil peuvent clairement améliorer l'efficacité d'acheminement sans consultation de table matérielle secondaire ni routage secondaire, assurer qu'un acheminement à deux niveaux peut être réalisé sur le dispositif qui ne prend pas en charge une consultation de table répétée, et réduire le coût du dispositif en partant de la prémisse que la même fonction soit fournie.
PCT/CN2011/074318 2010-08-27 2011-05-19 Procédé et appareil d'intégration de routage WO2012024948A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2010102673741A CN101931590A (zh) 2010-08-27 2010-08-27 一种路由整合方法和装置
CN201010267374.1 2010-08-27

Publications (1)

Publication Number Publication Date
WO2012024948A1 true WO2012024948A1 (fr) 2012-03-01

Family

ID=43370521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/074318 WO2012024948A1 (fr) 2010-08-27 2011-05-19 Procédé et appareil d'intégration de routage

Country Status (2)

Country Link
CN (1) CN101931590A (fr)
WO (1) WO2012024948A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931590A (zh) * 2010-08-27 2010-12-29 中兴通讯股份有限公司 一种路由整合方法和装置
CN102984062B (zh) * 2012-11-29 2016-06-15 中兴通讯股份有限公司 一种子网路由的处理方法及报文转发设备
CN104158718B (zh) * 2014-08-25 2017-06-13 新华三技术有限公司 一种报文处理方法和装置
CN110635988B (zh) * 2019-10-24 2020-10-27 北京大学 一种用于多路径传输的数据转发方法及设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1885820A (zh) * 2005-06-21 2006-12-27 中兴通讯股份有限公司 一种路由转发表地址查找引擎装置
CN101043428A (zh) * 2006-05-30 2007-09-26 华为技术有限公司 一种路由转发的方法和系统
CN101442494A (zh) * 2008-12-16 2009-05-27 中兴通讯股份有限公司 一种实现快速重路由的方法
CN101931590A (zh) * 2010-08-27 2010-12-29 中兴通讯股份有限公司 一种路由整合方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100586108C (zh) * 2007-09-26 2010-01-27 杭州华三通信技术有限公司 一种更新地址解析协议表中端口地址的方法和设备
CN101562575B (zh) * 2009-06-04 2012-01-04 杭州华三通信技术有限公司 Mpls te frr快速切换的方法和装置
CN101695047B (zh) * 2009-10-26 2015-01-28 中兴通讯股份有限公司 一种实现动态隧道报文转发的方法及交换机

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1885820A (zh) * 2005-06-21 2006-12-27 中兴通讯股份有限公司 一种路由转发表地址查找引擎装置
CN101043428A (zh) * 2006-05-30 2007-09-26 华为技术有限公司 一种路由转发的方法和系统
CN101442494A (zh) * 2008-12-16 2009-05-27 中兴通讯股份有限公司 一种实现快速重路由的方法
CN101931590A (zh) * 2010-08-27 2010-12-29 中兴通讯股份有限公司 一种路由整合方法和装置

Also Published As

Publication number Publication date
CN101931590A (zh) 2010-12-29

Similar Documents

Publication Publication Date Title
US10050877B2 (en) Packet forwarding method and apparatus
JP5996643B2 (ja) 強化された転送方法及びシステムと共にエッジルータ間で２つの疑似ワイヤを用いるｅツリー
US9973469B2 (en) MAC (L2) level authentication, security and policy control
US7944854B2 (en) IP security within multi-topology routing
EP2997702B1 (fr) Compression de listes à lien unique partageant des noeuds communs pour l'expansion de groupes multidestinations
EP3054634B1 (fr) Schéma pour effectuer une fonction de transfert tunnel monopasse sur une structure de réseau à deux couches
US7583674B2 (en) Switch and method for supporting internet protocol (IP) network tunnels
WO2013123847A1 (fr) Procédé de transmission de paquets et dispositif réseau
WO2011113340A1 (fr) Procédé et appareil d'accès destinés à un réseau privé virtuel de couche 2 à commutation multiprotocole par étiquette
WO2015024408A1 (fr) Procédé de commutation de tunnels, dispositif et commutateur
US10313154B2 (en) Packet forwarding
WO2013139159A1 (fr) Procédé de transmission de paquet dans un réseau et dispositif côté fournisseur
US20110242988A1 (en) System and method for providing pseudowire group labels in a network environment
WO2012024948A1 (fr) Procédé et appareil d'intégration de routage
WO2007082405A1 (fr) Procédé d'exécution pour détecter la légitimité d'un chemin de message à étiquette
JP2018537045A (ja) 顧客宅内ｌａｎの拡大
WO2011127849A2 (fr) Procédé et dispositif de réseau pour la transmission de flux de données
Sajassi et al. Requirements for ethernet vpn (evpn)
WO2016150093A1 (fr) Procédé, dispositif et appareil de pe de réacheminement de paquet
WO2007031006A1 (fr) Procede de commutation virtuelle qui peut etre acheminee
EP1927222B1 (fr) Vpls fonctionnant avec un temps de latence faible
JP5840211B2 (ja) オフセットを用いてインバンド制御チャネルを提供する疑似ワイヤ
WO2014105551A1 (fr) Adressage multidomaine dans un système de routage de messages
WO2015081684A1 (fr) Procédé de mise en œuvre d'une protection par tunnel, appareil et dispositif de réseau
WO2016074529A1 (fr) Procédé et appareil de commutation de liaison de réacheminement de contrôle d'accès au support

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11819323

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11819323

Country of ref document: EP

Kind code of ref document: A1