CN111800338B - Cross-AS EVPN route interaction method and device - Google Patents
Cross-AS EVPN route interaction method and device Download PDFInfo
- Publication number
- CN111800338B CN111800338B CN202010483445.5A CN202010483445A CN111800338B CN 111800338 B CN111800338 B CN 111800338B CN 202010483445 A CN202010483445 A CN 202010483445A CN 111800338 B CN111800338 B CN 111800338B
- Authority
- CN
- China
- Prior art keywords
- evi
- edge device
- ebgp
- current
- issued
- 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/58—Association of routers
- H04L45/586—Association of routers of virtual routers
-
- 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/52—Multiprotocol routers
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a cross-AS EVPN route interaction method and a device, wherein the method comprises the following steps: acquiring an EVPN route to be issued; searching a first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a destination edge device of the EVPN route to be issued in a first corresponding relation table of the EVI and the IP address of the EBGP neighbor carrying the automatically generated RT identifier and the derived RT; if the first entry is found in the first correspondence table, issuing the EVPN route to be issued carrying the export RT included in the first entry to the destination edge device, so that the destination edge device imports the export RT included in the first entry into the EVI corresponding to the export RT included in the first entry after finding the export RT included in the first entry in the second correspondence table of import RT and EVI. The scheme can realize EVPN route interaction between devices across AS.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to an Ethernet Virtual Private Network (EVPN) interaction method and apparatus across Autonomous Systems (AS).
Background
The EVPN is a Virtual Private Network (VPN), the control plane interacts with EVPN routing through a Multi-Protocol Border Gateway Protocol (MP-BGP), and the data plane may use a Multi-Protocol Label switching (MPLS) or a Virtual eXtensible Local Area Network (VXLAN).
When EVPN routes are interacted among EVPN devices, different tenants are isolated from each other through a Route Distinguisher (RD), and an EVPN Route is correctly led into a corresponding EVPN Instance (EVI) through a Route Target (RT). Each EVI is configured with an import RT and an export RT, and when an EVPN route is issued, the export RT is in attribute information of the issued EVPN route; when receiving the EVPN route, searching an EVI corresponding to an import RT which is the same as the RT carried in the attribute information of the EVPN route, if the EVI is searched, importing the received EVPN route into the searched EVI, and if the EVI is not searched, discarding the EVPN route.
In order to ensure that different devices in the same EVI can learn the EVPN route and isolate different devices in different EVIs, it is necessary to ensure that the import RT and the export RT between different devices in the same EVI are the same and the import RT and the export RT between different devices in different EVIs are different. Currently, the import RT and export RT generated by devices in the same AS are "local AS number: for example, the AS number of the local device is 65535, the EVI is 100, and the generated import RT and export RT are 65535:100, which can only implement EVPN route interaction between devices in the same AS and cannot implement EVPN interaction between devices across ases.
Disclosure of Invention
The embodiment of the invention provides a cross-AS EVPN route interaction method and device, which are used for realizing cross-AS EVPN route interaction between devices.
According to the embodiment of the invention, an EVPN route interaction method crossing AS is provided, which is applied to each edge device of the EVPN, and comprises the following steps:
acquiring an EVPN route to be issued; searching a first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a target edge device of the EVPN route to be issued in a first corresponding relation table of EVIs carrying automatically generated RT identifications, IP addresses of EBGP neighbors and derived RTs, wherein each derived RT in the first corresponding relation table comprises an AS identification of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; if the first entry is found in the first correspondence table, issuing the EVPN route to be issued carrying the export RT included in the first entry to the destination edge device, so that the destination edge device imports the evipn route to be issued into the EVI corresponding to the export RT included in the first entry after finding the export RT included in the first entry in a second correspondence table of import RTs and EVIs, where each import RT in the second correspondence table includes the AS identifier of the AS where the destination edge device is located and the EVI to which the import RT belongs; and/or the presence of a gas in the gas,
receiving EVPN routes to be introduced, which are issued by other edge devices and carry RTs, wherein the RTs comprise AS identifications of ASs where the other edge devices are located and second EVIs to which the other edge devices belong; searching a second table entry corresponding to the RT and second IP addresses of other edge devices in a third corresponding relation table of EVIs carrying automatically generated RT identifications, IP addresses of EBGP neighbors and import RTs, wherein each import RT in the third corresponding relation table comprises an AS identification of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; and if the second entry is found in the third corresponding relationship table, importing the EVPN route to be imported into the EVI included in the second entry.
Optionally, the method further includes:
determining whether each EVI to which the edge device belongs carries the automatic generation RT identifier;
and aiming at each EBGP neighbor and each EVI carrying the automatic generation RT identifier, executing:
generating a current export RT, wherein the current export RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
adding an entry comprising the current derived RT, the IP address of the current EBGP neighbor and the current EVI in the first correspondence table.
Optionally, after obtaining the EVPN route to be issued, the method further includes:
determining whether the destination edge device is an EBGP neighbor;
if the target edge device is determined to be an EBGP (Ethernet broadcast protocol) neighbor, determining whether a first EVI to which the EVPN route to be issued belongs carries an automatic generation RT (reverse transcription) identifier or not;
and if the first EVI to which the EVPN route to be issued belongs is determined to carry the automatic generation RT identifier, searching the first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to the first IP address of the destination edge device of the EVPN route to be issued in a first corresponding relation table of the EVI carrying the automatic generation RT identifier, the IP address of the EBGP neighbor and the derived RT.
Optionally, the method further includes:
determining whether each EVI to which the edge device belongs carries the automatic generation RT identifier;
and aiming at each EBGP neighbor and each EVI carrying the automatic generation RT identifier, executing:
generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
and adding a table entry comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
Optionally, after receiving the EVPN route to be imported, which carries the RT and is issued by another edge device, the method further includes:
determining whether the other edge device is an EBGP neighbor;
and if the other edge devices are determined to be EBGP neighbors, the step of searching a second table entry corresponding to the RT and second IP addresses of the other edge devices in a third corresponding relation table of the EVI carrying the automatically generated RT identifier, the IP addresses of the EBGP neighbors and the imported RT is executed.
According to an embodiment of the present invention, there is also provided an EVPN routing interaction apparatus across an AS, applied to each edge device of an EVPN, including:
the obtaining module is used for obtaining an EVPN route to be issued; the first lookup module is used for looking up a first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a target edge device of the EVPN route to be issued in a first corresponding relation table carrying EVIs with automatically generated RT identifiers, IP addresses of EBGP neighbors and derived RTs, wherein each derived RT in the first corresponding relation table comprises an AS identifier of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; a publishing module, configured to publish, to the destination edge device, the EVPN route to be published, where the EVPN route to be published carries a derived RT included in the first entry, if the first entry is found in the first correspondence table, so that the destination edge device imports, after finding, in a second correspondence table between an import RT and an EVI, an export RT included in the first entry, the EVPN route to be published into an EVI corresponding to the export RT included in the first entry, where each import RT in the second correspondence table includes an AS identifier of an AS where the destination edge device is located and an EVI to which the destination edge device belongs; and/or the presence of a gas in the gas,
the receiving module is used for receiving EVPN routes to be introduced, which are issued by other edge devices and carry RTs, wherein the RTs comprise AS identifications of ASs where the other edge devices are located and second EVIs to which the other edge devices belong; a second searching module, configured to search a third correspondence table carrying the EVIs of the automatically generated RT identifiers, the IP addresses of the EBGP neighbors, and the import RTs for second entries corresponding to the RT and the second IP addresses of the other edge devices, where each import RT included in the third correspondence table includes the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; and an importing module, configured to import the to-be-imported EVPN route to the EVI included in the second entry if the second entry is found in the third correspondence table.
Optionally, the method further includes:
a first determining module, configured to determine whether each EVI to which the edge device belongs carries the automatically generated RT identifier;
a first execution module, configured to execute, for each EBGP neighbor and each EVI carrying the automatically generated RT identifier:
generating a current export RT, wherein the current export RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
adding an entry comprising the current derived RT, the IP address of the current EBGP neighbor and the current EVI in the first correspondence table.
Optionally, the obtaining module is further configured to:
after obtaining an EVPN route to be issued, determining whether the destination edge device is an EBGP (Ethernet broadcast packet gateway) neighbor or not;
if the target edge device is determined to be an EBGP (Ethernet broadcast protocol) neighbor, determining whether a first EVI to which the EVPN route to be issued belongs carries an automatic generation RT (reverse transcription) identifier or not;
and if the first EVI to which the EVPN route to be issued belongs is determined to carry the automatically generated RT identifier, turning to the first search module.
Optionally, the method further includes:
a second determining module, configured to determine whether each EVI to which the edge device belongs carries the automatically generated RT identifier;
a second execution module, configured to execute, for each EBGP neighbor and each EVI carrying the automatically generated RT identifier:
generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
and adding a table entry comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
Optionally, the receiving module is further configured to:
after receiving EVPN routes to be led in and carrying RT issued by other edge devices, determining whether the other edge devices are EBGP neighbors or not;
and if the other edge devices are determined to be EBGP neighbors, turning to the second searching module.
According to the embodiment of the invention, the electronic equipment comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus;
a memory for storing a computer program;
a processor for implementing the above method steps when executing the program stored in the memory.
According to an embodiment of the present invention, there is also provided a computer-readable storage medium having stored therein a computer program, which when executed by a processor, performs the above-mentioned method steps.
The invention has the following beneficial effects:
the embodiment of the invention provides an interaction method and device for an EVPN route across AS, which are used for acquiring the EVPN route to be issued; searching a first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a target edge device of the EVPN route to be issued in a first corresponding relation table carrying an EVPN instance EVI of an automatically generated route target RT mark, an Internet protocol IP address of an External Border Gateway Protocol (EBGP) neighbor and a derived RT, wherein each derived RT in the first corresponding relation table comprises an AS mark of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; if the first entry is found in the first correspondence table, issuing the EVPN route to be issued carrying the export RT included in the first entry to the destination edge device, so that the destination edge device imports the evipn route to be issued into the EVI corresponding to the export RT included in the first entry after finding the export RT included in the first entry in a second correspondence table of import RTs and EVIs, where each import RT in the second correspondence table includes the AS identifier of the AS where the destination edge device is located and the EVI to which the import RT belongs; and/or receiving EVPN routes to be introduced, which are issued by other edge devices and carry RTs, wherein the RTs comprise AS identifications of ASs where the other edge devices are located and second EVIs to which the other edge devices belong; searching a second table entry corresponding to the RT and second IP addresses of other edge devices in a third corresponding relation table of EVIs carrying automatically generated RT identifications, IP addresses of EBGP neighbors and import RTs, wherein each import RT in the third corresponding relation table comprises an AS identification of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; and if the second entry is found in the third corresponding relationship table, importing the EVPN route to be imported into the EVI included in the second entry. In the scheme, when each edge device of the EVPN is used as the issuing device of the EVPN route, a derived RT may be generated based on each EBGP neighbor that includes the AS identification of the AS in which the corresponding EBGP neighbor is located and the EVI to which the edge device belongs, and stores it in the first corresponding relation table of EVI, EBGP neighbor IP address carrying the automatic generation RT mark and the derived RT, then, based on the first corresponding relation table, looking up a first EVI to which the EVPN route to be issued belongs and a derived RT corresponding to the first IP address of the destination edge device of the EVPN route to be issued, because the export RT is generated according to the target edge device serving AS the RBGP neighbor, the target edge device can still generate the import RT according to the AS identification of the AS where the target edge device is located and the EVI to which the target edge device belongs without changing the generation mode of the import RT, and can also ensure that the EVPN route issued by the edge device serving AS the EBGP neighbor is correctly imported; when each edge device of the EVPN is used AS a receiving device of the EVPN route, it may generate an import RT including the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs based on each EBGP neighbor, and store it in a third correspondence table carrying the EVI of the automatically generated RT identifier, the IP address of the EBGP neighbor, and the import RT, and then look up the EVI carried by the route to be imported and corresponding to the second IP address of other edge devices based on the third correspondence table.
Drawings
Fig. 1 is a flowchart of an AS-spanning EVPN route interaction method using EVPN edge devices AS EVPN route issuing devices AS execution agents in an embodiment of the present invention;
fig. 2 is a flowchart of another cross-AS EVPN route interaction method that uses an edge device of an EVPN AS a receiving device of an EVPN route AS an execution subject in the embodiment of the present invention;
fig. 3 is a schematic structural diagram of an EVPN routing interaction apparatus across ases corresponding to fig. 1 according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of an EVPN routing interaction apparatus across ases corresponding to fig. 2 according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device shown in the present application.
Detailed Description
In order to implement EVPN route interaction between devices across ases, an embodiment of the present invention provides a method for EVPN route interaction across ases, and the method is introduced below with an EVPN edge device AS an issuing device and a receiving device of an EVPN route AS an execution subject, respectively.
Firstly, an EVPN route interaction method across ASs is introduced, in which an EVPN edge device is used AS an EVPN route issuing device AS an execution subject, and the flow of the method is shown in fig. 1, and the execution steps are AS follows:
s11: and acquiring an EVPN route to be issued.
S12: searching a first EVI to which an EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a destination edge device of the EVPN route to be issued in a first corresponding relation table of EVI and EBGP neighbors carrying an automatically generated RT identifier and a derived RT.
A first corresponding relation table of the EVI carrying the identification of the automatically generated RT, the IP addresses of the EBGP neighbors and the derived RT can be established in advance, and the EBGP neighbors are the EBGP neighbors, namely, the EBGP neighbors are not in the same AS, namely, the cross AS; each derived RT in the first mapping table includes the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs, which is different from a manner in the prior art that the derived RT is generated according to the AS identifier of the AS where the device is located and the EVI to which the device belongs.
S13: if the first entry is found in the first correspondence table, issuing an EVPN route to be issued carrying a derived RT included in the first entry to the destination edge device, so that after the destination edge device finds the derived RT included in the first entry in a second correspondence table of the derived RTs and EVIs, the EVPN route to be issued is led into the EVI corresponding to the derived RT included in the first entry, and each derived RT in the second correspondence table includes an AS identifier of an AS where the destination edge device is located and the EVI to which the destination edge device belongs.
If the first table entry is found in the first corresponding relation table, the derived RT included in the first table entry is taken as the attribute information of the routing equipment to be issued and issued to the target edge equipment; the destination edge device may pre-establish a second correspondence table between the import RTs and the EVIs, where each import RT in the second correspondence table includes the AS identifier of the AS where the destination edge device is located and the EVI to which the destination edge device belongs, and then after finding the export RT included in the first entry in the second correspondence table, that is, finding the import RT that is the same AS the export RT included in the first entry, at this time, the route of the EVPN to be issued may be imported into the EVI corresponding to the export RT included in the first entry.
In the scheme, when each edge device of the EVPN is used as the issuing device of the EVPN route, a derived RT may be generated based on each EBGP neighbor that includes the AS identification of the AS in which the corresponding EBGP neighbor is located and the EVI to which the edge device belongs, and stores it in the first corresponding relation table of EVI, EBGP neighbor IP address carrying the automatic generation RT mark and the derived RT, then, based on the first corresponding relation table, looking up a first EVI to which the EVPN route to be issued belongs and a derived RT corresponding to the first IP address of the destination edge device of the EVPN route to be issued, because the export RT is generated according to the target edge device AS the RBGP neighbor, the target edge device can still generate the import RT according to the AS identification of the AS where the target edge device is located and the EVI to which the target edge device belongs without changing the generation mode of the import RT, and can also ensure that the EVPN route issued by the edge device AS the EBGP neighbor is correctly imported.
Optionally, the method further includes:
determining whether each EVI to which the edge equipment belongs carries an automatic generation RT identifier;
aiming at each EBGP neighbor and each EVI carrying the automatic generation RT identifier, executing:
generating a current export RT, wherein the current export RT comprises the AS identification of the AS where the current EBGP neighbor is located and the current EVI;
and adding an item comprising the current derived RT, the IP address of the current EBGP neighbor and the current EVI in the first corresponding relation table.
There may be multiple belonged EVIs in the edge device, an automatic RT generation function may be set for one or more of the EVIs, an automatic RT generation identifier may be added to the EVIs set with the automatic RT generation function, and generally, each edge device of the EVPN may have multiple other edge devices as EBGP neighbors, so as to generate corresponding entries in the first correspondence table, for each EBGP neighbor and each EVI carrying the automatic RT generation identifier, the following steps may be performed: generating a current export RT (RT) which comprises the AS identification of the AS where the current EBGP neighbor is located and the current EVI; and adding an item comprising the current derived RT, the IP address of the current EBGP neighbor and the current EVI in the first corresponding relation table.
Optionally, after obtaining the EVPN route to be issued in S11, the method further includes:
determining whether the destination edge device is an EBGP neighbor;
if the target edge device is determined to be an EBGP (Ethernet broadcast protocol) neighbor, determining whether a first EVI to which an EVPN route to be issued belongs carries an automatic generation RT (reverse transcription) identifier or not;
and if the first EVI to which the EVPN route to be issued belongs is determined to carry the automatically generated RT identifier, executing S12.
Sometimes, the first mapping table may be relatively large, and if the first mapping table is queried for each EVPN route to be issued, a large amount of resources of the edge device may be occupied, because the first corresponding relation table stores the entries carrying the EVI and the IP addresses of the EBGP neighbors and the derived RT which automatically generate the RT identifications, whether the destination edge device is the EBGP neighbor or not can be judged firstly, if not, the processing can be performed according to the flow of the prior art, if yes, it can be further determined whether the first EVI to which the EVPN route to be issued belongs carries the auto-generated RT identifier, if not, the processing can be performed according to the original flow, if the processing is carried out, S12 is executed, a part of EVPN routes to be issued can be filtered through the process, and the first corresponding relation table is searched only for the EVPN routes to be issued meeting the conditions, so that the resources of the edge device can be greatly saved.
The cross-AS EVPN route interaction method using the EVPN edge device AS the issuing device of the EVPN route AS the executing agent is introduced above, and the cross-AS EVPN route interaction method using the EVPN edge device AS the receiving device of the EVPN route AS the executing agent is introduced below, where the flow of the method is shown in fig. 2, and the execution steps are AS follows:
s21: and receiving EVPN routes to be led in, which carry RTs and are issued by other edge devices.
The RT includes the AS identification of the AS where the other edge device is located and the second EVI to which the other edge device belongs, that is, the other edge device generates the RT in the manner in the prior art.
S22: and searching a second table item corresponding to the RT and second IP addresses of other edge devices in a third corresponding relation table of the EVI and EBGP neighbors carrying the automatically generated RT identifications and the imported RT.
A third corresponding relation table of the EVI carrying the automatically generated RT mark, the IP addresses of the EBGP neighbors and the imported RT can be pre-established, and the EBGP neighbors are the EBGP neighbors, namely, the EBGP neighbors are not in the same AS, namely, the AS is crossed; each import RT included in the third mapping table includes an AS identifier of an AS where the corresponding EBGP neighbor is located and an EVI to which the edge device belongs, which is different from a manner in the prior art in which an import RT is generated according to the AS identifier of the AS where the device is located and the EVI to which the edge device belongs.
S23: and if the second table entry is found in the third corresponding relation table, importing the EVPN route to be imported into the EVI included in the second table entry.
In the scheme, when each edge device of the EVPN serves AS a receiving device of the EVPN route, an import RT including an AS identifier of an AS where a corresponding EBGP neighbor is located and an EVI to which the edge device belongs may be generated based on each EBGP neighbor, and stored in a third correspondence table carrying the EVI automatically generating the RT identifier, the IP address of the EBGP neighbor, and the import RT, and then the EVI carried by the EVPN route to be imported and the EVI corresponding to the second IP address of the other edge device are searched based on the third correspondence table.
Optionally, the method further includes:
determining whether each EVI to which the edge device belongs carries an automatic generation RT identifier;
aiming at each EBGP neighbor and each EVI carrying the automatic generation RT identifier, executing:
generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
and adding a table item comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
There may be multiple belonged EVIs in the edge device, an automatic RT generation function may be set for one or more of the EVIs, an automatic RT generation identifier may be added to the EVIs set with the automatic RT generation function, and generally, multiple edge devices of the EVPN may be used as EBGP neighbors, so as to generate corresponding entries in the third correspondence table, for each EBGP neighbor and each EVI carrying the automatic RT generation identifier, the following steps may be performed: generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI; and adding a table item comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
Optionally, after receiving the to-be-imported EVPN route carrying the RT and issued by another edge device in S21, the method further includes:
determining whether the other edge devices are EBGP neighbors;
if it is determined that the other edge devices are EBGP neighbors, S22 is performed.
Sometimes, the third mapping table may be relatively large, if the third mapping table is queried for each EVPN route to be imported, a large amount of resources of the edge device may be occupied, because the third mapping table stores the IP addresses of the EVI and EBGP neighbors carrying the automatically generated RT identifier and the table entry of the import RT, it may be determined whether other edge devices are EBGP neighbors, if not, the process according to the prior art may be performed, if yes, S12 is executed, a part of EVPN routes to be imported may be filtered through the process, and only the EVPN routes to be imported meeting the condition may be searched for the third mapping table, thereby greatly saving resources of the edge device.
It should be noted that the EVPN edge device may also simultaneously perform the methods shown in fig. 1 and fig. 2, that is, the issuing device and the receiving device, which are EVPN routes, may simultaneously issue and receive EVPN routes.
The following specific example illustrates the above process. Suppose that EBGP neighbors are established between the edge device a, the edge device B and the edge device C, IP addresses are 1.1.1.1, 2.2.2.2, and 3.3.3, respectively, the AS identifier of the AS where the edge device a is located is 100, the AS identifier of the AS where the edge device B is located is 200, the AS identifier of the AS where the edge device C is located is 300, EVPN routes of the EVI 100 need to be interacted between the edge devices, and the EVI 100 carries an automatic RT generation identifier. According to the prior art, the RT generated by the edge device A for the belonged EVI 100 is 100:100, the RT generated by the edge device B for the belonged EVI 100 is 200:100, and the RT generated by the edge device C for the belonged EVI 100 instance is 300: 100.
If the export RT generated by the edge device A for the edge device B is 200:100, storing 2.2.2, 100, 200:100 into the first corresponding relation; the export RT generated by edge device a for edge device C is 300:100, storing 3.3.3.3, 100, 300:10 in the first correspondence. When the edge device A needs to issue the EVPN route of the EVI 100 to the edge device B, firstly determining that the edge device B is an EBGP neighbor and determining that the EVI 100 carries an automatic generation RT identifier, then searching the IP address 2.2.2.2.2 address of the edge device B and the EVI 100 in the first corresponding relation, and finding out the derivation RT of 200: 100; finally, 200:100 is added to attributes of the EVPN route and issued to the edge device B2.2.2.2. The edge device B receives the EVPN route, and according to the EVPN route imported in the prior art, searches for a second correspondence relationship established in advance, that is, finds the EVI 100 according to a ratio of 200:100, and imports the EVPN route into the EVI 100. The method for the edge device a to issue the route to the edge device C and the method for the edge device C to import the EVPN route are the same as those of the edge device B, and are not described herein again.
If the import RT generated by the edge device A for the edge device B is 200:100, storing 2.2.2.2, 200:100 and EVI 100 into a third corresponding relation; the import RT generated by edge device a for edge device C is 300:100, and 3.3.3.3, 300:100, EVI 100 are stored in the third correspondence. After receiving the EVPN route which carries R of 200:100 and is issued by the edge device B, the edge device A determines that the edge device B is an EBGP neighbor, searches the EVI corresponding to 2.2.2.2 and 200:100 in the third corresponding relation, finds the EVI 100, and finally leads the EVPN route into the EVI 100. If the edge device a receives the EVPN route issued by the edge device C, the importing method is the same as that of the edge device B, which is not described in detail here.
Based on the same inventive concept, an embodiment of the present invention provides an EVPN routing interaction apparatus across AS, corresponding to the method shown in fig. 1, and applied to each edge device of EVPN, where the structure of the apparatus is shown in fig. 3, and the apparatus includes:
the obtaining module 31 is configured to obtain an EVPN route to be issued.
The first lookup module 32 is configured to lookup a first EVI to which the EVPN route to be issued belongs and a first entry corresponding to a first IP address of a destination edge device of the EVPN route to be issued in a first correspondence table carrying the EVI and the EBGP neighbor IP address of the automatically generated RT identifier, where each derived RT in the first correspondence table includes an AS identifier of an AS where the corresponding EBGP neighbor is located and an EVI to which the edge device belongs.
The issuing module 33 is configured to issue, to the destination edge device, an EVPN route to be issued that carries the export RT included in the first entry if the first entry is found in the first correspondence table, so that the destination edge device, after finding the export RT included in the first entry in the second correspondence table between the import RT and the EVI, imports the EVPN route to be issued into the EVI corresponding to the export RT included in the first entry, where each import RT in the second correspondence table includes an AS identifier of an AS where the destination edge device is located and an EVI to which the import RT belongs.
In the scheme, when each edge device of the EVPN is used as the issuing device of the EVPN route, a derived RT may be generated based on each EBGP neighbor that includes the AS identification of the AS in which the corresponding EBGP neighbor is located and the EVI to which the edge device belongs, and stores it in the first corresponding relation table of EVI, EBGP neighbor IP address carrying the automatic generation RT mark and the derived RT, then, based on the first corresponding relation table, looking up a first EVI to which the EVPN route to be issued belongs and a derived RT corresponding to the first IP address of the destination edge device of the EVPN route to be issued, because the export RT is generated according to the target edge device AS the RBGP neighbor, the target edge device can still generate the import RT according to the AS identification of the AS where the target edge device is located and the EVI to which the target edge device belongs without changing the generation mode of the import RT, and can also ensure that the EVPN route issued by the edge device AS the EBGP neighbor is correctly imported.
Optionally, the method further includes:
the first determining module is used for determining whether each EVI to which the edge device belongs carries an automatic generation RT identifier;
a first execution module, configured to execute, for each EBGP neighbor and each EVI carrying an auto-generated RT identity:
generating a current export RT, wherein the current export RT comprises the AS identification of the AS where the current EBGP neighbor is located and the current EVI;
and adding an item comprising the current derived RT, the IP address of the current EBGP neighbor and the current EVI in the first corresponding relation table.
Optionally, the obtaining module is further configured to:
after obtaining an EVPN route to be issued, determining whether a target edge device is an EBGP neighbor or not;
if the target edge device is determined to be an EBGP (Ethernet broadcast protocol) neighbor, determining whether a first EVI to which an EVPN route to be issued belongs carries an automatic generation RT (reverse transcription) identifier or not;
and if the first EVI to which the EVPN route to be issued belongs is determined to carry the automatically generated RT identifier, turning to a first searching module.
Based on the same inventive concept, an embodiment of the present invention provides an EVPN routing interaction apparatus across AS, corresponding to the method shown in fig. 2, and applied to each edge device of EVPN, where the structure of the apparatus is shown in fig. 4, and the apparatus includes:
a receiving module 41, configured to receive an EVPN route to be imported, which carries an RT and is issued by another edge device, where the RT includes an AS identifier of an AS where the other edge device is located and a second EVI to which the other edge device belongs.
The second lookup module 42 is configured to lookup a second table entry corresponding to the RT and second IP addresses of other edge devices in a third correspondence table carrying the EVIs and the EBGP neighbors with the automatically generated RT identifiers, where each imported RT included in the third correspondence table includes the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs.
And an importing module 43, configured to import the to-be-imported EVPN route into the EVI included in the second entry if the second entry is found in the third correspondence table.
In the scheme, when each edge device of the EVPN serves AS a receiving device of the EVPN route, an import RT including an AS identifier of an AS where a corresponding EBGP neighbor is located and an EVI to which the edge device belongs may be generated based on each EBGP neighbor, and stored in a third correspondence table carrying the EVI automatically generating the RT identifier, the IP address of the EBGP neighbor, and the import RT, and then the EVI carried by the EVPN route to be imported and the EVI corresponding to the second IP address of the other edge device are searched based on the third correspondence table.
Optionally, the method further includes:
the second determining module is used for determining whether each EVI to which the edge device belongs carries an automatic generation RT identifier;
a second execution module, configured to execute, for each EBGP neighbor and each EVI carrying an automatically generated RT identifier:
generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
and adding a table item comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
Optionally, the receiving module is further configured to:
after receiving EVPN routes to be led in, which carry RT and are issued by other edge devices, determining whether the other edge devices are EBGP neighbors or not;
and if the other edge devices are determined to be EBGP neighbors, turning to a second searching module.
It should be noted that the edge device of EVPN may further include the apparatus shown in fig. 3 and fig. 4, that is, the issuing device and the receiving device that can be simultaneously used as EVPN route may issue and receive EVPN route.
An electronic device is further provided in the embodiment of the present application, please refer to fig. 5, which includes a processor 510, a communication interface 520, a memory 530 and a communication bus 540, wherein the processor 510, the communication interface 520 and the memory 530 complete communication with each other through the communication bus 540.
A memory 530 for storing a computer program;
the processor 510 is configured to implement the EVPN routing interaction method across ases described in any of the above embodiments when executing the program stored in the memory 530.
The communication interface 520 is used for communication between the electronic apparatus and other apparatuses.
The Memory may include a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.
In the scheme, when each edge device of the EVPN is used as the issuing device of the EVPN route, a derived RT may be generated based on each EBGP neighbor that includes the AS identification of the AS in which the corresponding EBGP neighbor is located and the EVI to which the edge device belongs, and stores it in the first corresponding relation table of EVI, EBGP neighbor IP address carrying the automatic generation RT mark and the derived RT, then, based on the first corresponding relation table, looking up a first EVI to which the EVPN route to be issued belongs and a derived RT corresponding to the first IP address of the destination edge device of the EVPN route to be issued, because the export RT is generated according to the target edge device serving AS the RBGP neighbor, the target edge device can still generate the import RT according to the AS identification of the AS where the target edge device is located and the EVI to which the target edge device belongs without changing the generation mode of the import RT, and can also ensure that the EVPN route issued by the edge device serving AS the EBGP neighbor is correctly imported; when each edge device of the EVPN is used AS a receiving device of the EVPN route, the import RT including the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs may be generated based on each EBGP neighbor, and stored in a third correspondence table carrying the EVI that automatically generates the RT identifier, the IP address of the EBGP neighbor, and the import RT, and then the EVI carried by the route to be imported and the EVI corresponding to the second IP address of the other edge device are searched based on the third correspondence table.
Accordingly, an embodiment of the present application further provides a computer-readable storage medium, which stores instructions that, when executed on a computer, cause the computer to perform the EVPN route interaction method across ases described in any of the above embodiments.
In the scheme, when each edge device of the EVPN is used as the issuing device of the EVPN route, a derived RT may be generated based on each EBGP neighbor that includes the AS identification of the AS in which the corresponding EBGP neighbor is located and the EVI to which the edge device belongs, and stores it in the first corresponding relation table of EVI, EBGP neighbor IP address carrying the automatic generation RT mark and the derived RT, then, based on the first corresponding relation table, looking up a first EVI to which the EVPN route to be issued belongs and a derived RT corresponding to the first IP address of the destination edge device of the EVPN route to be issued, because the export RT is generated according to the target edge device serving AS the RBGP neighbor, the target edge device can still generate the import RT according to the AS identification of the AS where the target edge device is located and the EVI to which the target edge device belongs without changing the generation mode of the import RT, and can also ensure that the EVPN route issued by the edge device serving AS the EBGP neighbor is correctly imported; when each edge device of the EVPN is used AS a receiving device of the EVPN route, the import RT including the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs may be generated based on each EBGP neighbor, and stored in a third correspondence table carrying the EVI that automatically generates the RT identifier, the IP address of the EBGP neighbor, and the import RT, and then the EVI carried by the route to be imported and the EVI corresponding to the second IP address of the other edge device are searched based on the third correspondence table.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While alternative embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following appended claims be interpreted as including alternative embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass these modifications and variations.
Claims (12)
1. An Ethernet virtual private network EVPN route interaction method crossing an Autonomous System (AS) is applied to each edge device of the EVPN, and is characterized by comprising the following steps:
acquiring an EVPN route to be issued; searching a first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a target edge device of the EVPN route to be issued in a first corresponding relation table carrying an EVPN instance EVI of an automatically generated route target RT mark, an Internet protocol IP address of an External Border Gateway Protocol (EBGP) neighbor and a derived RT, wherein each derived RT in the first corresponding relation table comprises an AS mark of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; if the first entry is found in the first correspondence table, issuing the EVPN route to be issued carrying the export RT included in the first entry to the destination edge device, so that the destination edge device imports the evipn route to be issued into the EVI corresponding to the export RT included in the first entry after finding the export RT included in the first entry in a second correspondence table of import RTs and EVIs, where each import RT in the second correspondence table includes the AS identifier of the AS where the destination edge device is located and the EVI to which the import RT belongs; and/or the presence of a gas in the atmosphere,
receiving EVPN routes to be introduced, which are issued by other edge devices and carry RTs, wherein the RTs comprise AS identifications of ASs where the other edge devices are located and second EVIs to which the other edge devices belong; searching a second table entry corresponding to the RT and second IP addresses of other edge devices in a third corresponding relation table of EVIs carrying automatically generated RT identifications, IP addresses of EBGP neighbors and import RTs, wherein each import RT in the third corresponding relation table comprises an AS identification of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; and if the second table entry is found in the third corresponding relation table, importing the EVPN route to be imported into the EVI included in the second table entry.
2. The method of claim 1, further comprising:
determining whether each EVI to which the edge device belongs carries the automatic generation RT identifier;
and aiming at each EBGP neighbor and each EVI carrying the automatic generation RT identifier, executing:
generating a current export RT (RT) which comprises an AS (identity) of an AS where a current EBGP (E-Back group GP) neighbor is located and a current EVI (error rate indicator);
adding an entry comprising the current derived RT, the IP address of the current EBGP neighbor and the current EVI in the first correspondence table.
3. The method of claim 1 or 2, wherein after acquiring the EVPN route to be issued, further comprising:
determining whether the destination edge device is an EBGP neighbor;
if the target edge device is determined to be an EBGP (Ethernet broadcast protocol) neighbor, determining whether a first EVI to which the EVPN route to be issued belongs carries an automatic generation RT (reverse transcription) identifier or not;
and if the first EVI to which the EVPN route to be issued belongs is determined to carry the automatic generation RT identifier, searching the first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to the first IP address of the destination edge device of the EVPN route to be issued in a first corresponding relation table of the EVI carrying the automatic generation RT identifier, the IP address of the EBGP neighbor and the derived RT.
4. The method of claim 1, further comprising:
determining whether each EVI to which the edge device belongs carries the automatic generation RT identifier;
and aiming at each EBGP neighbor and each EVI carrying the automatic generation RT identifier, executing:
generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
and adding a table entry comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
5. The method of claim 1 or 4, wherein after receiving the EVPN route to be imported carrying the RT and issued by the other edge device, the method further comprises:
determining whether the other edge device is an EBGP neighbor;
and if the other edge devices are determined to be EBGP neighbors, the step of searching a second table entry corresponding to the RT and second IP addresses of the other edge devices in a third corresponding relation table of the EVI carrying the automatically generated RT identifier, the IP addresses of the EBGP neighbors and the imported RT is executed.
6. An EVPN route interaction device across AS, which is applied to each edge device of EVPN, is characterized by comprising:
the obtaining module is used for obtaining an EVPN route to be issued; the first lookup module is used for looking up a first EVI to which the EVPN route to be issued belongs and a first table entry corresponding to a first IP address of a target edge device of the EVPN route to be issued in a first corresponding relation table carrying EVIs with automatically generated RT identifiers, IP addresses of EBGP neighbors and derived RTs, wherein each derived RT in the first corresponding relation table comprises an AS identifier of an AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; a publishing module, configured to publish, to the destination edge device, the EVPN route to be published, where the EVPN route to be published carries a derived RT included in the first entry, if the first entry is found in the first correspondence table, so that the destination edge device imports, after finding, in a second correspondence table between an import RT and an EVI, an export RT included in the first entry, the EVPN route to be published into an EVI corresponding to the export RT included in the first entry, where each import RT in the second correspondence table includes an AS identifier of an AS where the destination edge device is located and an EVI to which the destination edge device belongs; and/or the presence of a gas in the gas,
the receiving module is used for receiving EVPN routes to be introduced, which are issued by other edge devices and carry RTs, wherein the RTs comprise AS identifications of ASs where the other edge devices are located and second EVIs to which the other edge devices belong; a second searching module, configured to search a third correspondence table carrying the EVIs of the automatically generated RT identifiers, the IP addresses of the EBGP neighbors, and the import RTs for second entries corresponding to the RT and the second IP addresses of the other edge devices, where each import RT included in the third correspondence table includes the AS identifier of the AS where the corresponding EBGP neighbor is located and the EVI to which the edge device belongs; and an importing module, configured to import the to-be-imported EVPN route to the EVI included in the second entry if the second entry is found in the third correspondence table.
7. The apparatus of claim 6, further comprising:
a first determining module, configured to determine whether each EVI to which the edge device belongs carries the automatically generated RT identifier;
a first execution module, configured to execute, for each EBGP neighbor and each EVI carrying the automatically generated RT identifier:
generating a current export RT, wherein the current export RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
adding an entry in the first correspondence table that includes the current derived RT, the IP address of the current EBGP neighbor, and the current EVI.
8. The apparatus of claim 6 or 7, wherein the obtaining module is further configured to:
after obtaining an EVPN route to be issued, determining whether the target edge equipment is an EBGP neighbor or not;
if the target edge device is determined to be an EBGP (Ethernet broadcast protocol) neighbor, determining whether a first EVI to which the EVPN route to be issued belongs carries an automatic generation RT (reverse transcription) identifier or not;
and if the first EVI to which the EVPN route to be issued belongs is determined to carry the automatically generated RT identifier, turning to the first search module.
9. The apparatus of claim 6, further comprising:
a second determining module, configured to determine whether each EVI to which the edge device belongs carries the automatically generated RT identifier;
a second execution module, configured to execute, for each EBGP neighbor and each EVI carrying the automatically generated RT identifier:
generating a current import RT, wherein the current import RT comprises an AS identifier of an AS where a current EBGP neighbor is located and a current EVI;
and adding a table entry comprising the current import RT, the IP address of the current EBGP neighbor and the current EVI in the third corresponding relation table.
10. The apparatus of claim 6 or 9, wherein the receiving module is further configured to:
after receiving EVPN routes to be led in, which carry RT and are issued by other edge devices, determining whether the other edge devices are EBGP neighbors or not;
and if the other edge devices are determined to be EBGP neighbors, turning to the second searching module.
11. An electronic device, characterized in that the electronic device comprises a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory are communicated with each other through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1 to 5 when executing a program stored on a memory.
12. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method steps of any one of the claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010483445.5A CN111800338B (en) | 2020-06-01 | 2020-06-01 | Cross-AS EVPN route interaction method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010483445.5A CN111800338B (en) | 2020-06-01 | 2020-06-01 | Cross-AS EVPN route interaction method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111800338A CN111800338A (en) | 2020-10-20 |
| CN111800338B true CN111800338B (en) | 2022-09-16 |
Family
ID=72806612
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010483445.5A Active CN111800338B (en) | 2020-06-01 | 2020-06-01 | Cross-AS EVPN route interaction method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111800338B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113765803B (en) * | 2021-08-05 | 2023-10-24 | 新华三大数据技术有限公司 | Route release method and device and network equipment |
| WO2023039831A1 (en) * | 2021-09-17 | 2023-03-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for selective importing ip route |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011029241A1 (en) * | 2009-09-14 | 2011-03-17 | 华为技术有限公司 | Method, system and router for route processing |
| CN103095578A (en) * | 2013-01-29 | 2013-05-08 | 杭州华三通信技术有限公司 | Routing information control method and processing element (PE) device in multiple protocol label switching framework for layer 3 virtual private network (MPLS L3VPN) |
| CN104660502A (en) * | 2015-03-16 | 2015-05-27 | 杭州华三通信技术有限公司 | Method and device for announcing route to EBGP (external border gateway protocol) neighbor |
| CN106789629A (en) * | 2016-12-23 | 2017-05-31 | 锐捷网络股份有限公司 | Business fast convergent method and device |
| CN108322376A (en) * | 2017-06-26 | 2018-07-24 | 新华三技术有限公司 | Route synchronization method, apparatus and machine readable storage medium |
| CN109218178A (en) * | 2017-07-05 | 2019-01-15 | 华为技术有限公司 | A kind of message processing method and the network equipment |
| CN111200549A (en) * | 2018-11-16 | 2020-05-26 | 华为技术有限公司 | Method and device for acquiring routing information |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1323522C (en) * | 2003-01-22 | 2007-06-27 | 华为技术有限公司 | Method for determining relation between routers at fringe of client site and virtual private network |
| CN104219147B (en) * | 2013-06-05 | 2018-10-16 | 中兴通讯股份有限公司 | The VPN of edge device realizes processing method and processing device |
| CN104243260B (en) * | 2013-06-21 | 2018-06-15 | 新华三技术有限公司 | Ethernet virtualization internet network interconnecting method and edge device |
| US10250552B1 (en) * | 2016-04-27 | 2019-04-02 | Cisco Technology, Inc. | L3VPN service with single IGP/BGP session from a multi-homed CE with fast convergence using EVPN |
| US10305794B2 (en) * | 2017-03-27 | 2019-05-28 | At&T Intellectual Property I, L.P. | System for indirect border gateway protocol routing |
| US10630509B2 (en) * | 2018-03-30 | 2020-04-21 | Juniper Networks, Inc. | Aliasing behavior for traffic to multihomed sites in ethernet virtual private network (EVPN) networks |
-
2020
- 2020-06-01 CN CN202010483445.5A patent/CN111800338B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011029241A1 (en) * | 2009-09-14 | 2011-03-17 | 华为技术有限公司 | Method, system and router for route processing |
| CN103095578A (en) * | 2013-01-29 | 2013-05-08 | 杭州华三通信技术有限公司 | Routing information control method and processing element (PE) device in multiple protocol label switching framework for layer 3 virtual private network (MPLS L3VPN) |
| CN104660502A (en) * | 2015-03-16 | 2015-05-27 | 杭州华三通信技术有限公司 | Method and device for announcing route to EBGP (external border gateway protocol) neighbor |
| CN106789629A (en) * | 2016-12-23 | 2017-05-31 | 锐捷网络股份有限公司 | Business fast convergent method and device |
| CN108322376A (en) * | 2017-06-26 | 2018-07-24 | 新华三技术有限公司 | Route synchronization method, apparatus and machine readable storage medium |
| CN109218178A (en) * | 2017-07-05 | 2019-01-15 | 华为技术有限公司 | A kind of message processing method and the network equipment |
| CN111200549A (en) * | 2018-11-16 | 2020-05-26 | 华为技术有限公司 | Method and device for acquiring routing information |
Non-Patent Citations (2)
| Title |
|---|
| EVPN Interworking with IPVPN draft-ietf-bess-evpn-ipvpn-interworking-03;J. Rabadan等;《IETF 》;20200525;全文 * |
| L3 Aliasing and Mass Withdrawal Support for EVPN draft-sajassi-bess-evpn-ip-aliasing-01;A. Sajassi等;《IETF 》;20200309;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111800338A (en) | 2020-10-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9001644B2 (en) | Ethernet virtual private network system for providing fast protection for access rings | |
| US20160134528A1 (en) | Signaling aliasing capability in data centers | |
| CN104184664B (en) | Route forwarding table items generation method and device | |
| US10511518B2 (en) | Mechanism and framework for finding optimal multicast tree roots without the knowledge of traffic sources and receivers for Fabricpath and TRILL | |
| CN111800338B (en) | Cross-AS EVPN route interaction method and device | |
| CN111010329B (en) | Message transmission method and device | |
| WO2020088465A1 (en) | Port configuration method and device, storage medium, and electronic device | |
| CN109951371B (en) | Data forwarding method and device | |
| CN105827495A (en) | Message forwarding method and device for VXLAN gateway | |
| CN111934969B (en) | Maintenance method and device of MAC forwarding table | |
| EP3018866A1 (en) | Signaling aliasing capability in data centers | |
| CN107896188A (en) | Data forwarding method and device | |
| CN112866114B (en) | Multicast message processing method and device | |
| CN113923162B (en) | Message forwarding method, device, equipment and storage medium | |
| CN111865803B (en) | Route processing method and device based on EVPN | |
| CN105337863A (en) | Label assigning method and device | |
| CN102355410B (en) | Pseudo-wire labeling method for MPLS (Multiple Protocol Label Switching) network virtual exchange embodiment | |
| CN110971526B (en) | Flow table expansion method and device for FDB (fully drawn bus) resources of hybrid switch | |
| CN112637053B (en) | Method and device for determining backup forwarding path of route | |
| CN105207904A (en) | Message processing method, device and router | |
| CN101222408B (en) | VLAN topological generating method and device | |
| CN109327462B (en) | MAC address authentication method based on L2VPN network | |
| CN107707480B (en) | Message forwarding method and device | |
| CN112367251A (en) | Forwarding information base table item detection method, detection equipment and network equipment | |
| CN113746739B (en) | Routing table creating method, PE (provider edge) equipment, electronic equipment and storage medium |
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 |