WO2018028676A1 - 以太网虚拟私有网络evpn与公网互通 - Google Patents

以太网虚拟私有网络evpn与公网互通 Download PDF

Info

Publication number
WO2018028676A1
WO2018028676A1 PCT/CN2017/097113 CN2017097113W WO2018028676A1 WO 2018028676 A1 WO2018028676 A1 WO 2018028676A1 CN 2017097113 W CN2017097113 W CN 2017097113W WO 2018028676 A1 WO2018028676 A1 WO 2018028676A1
Authority
WO
WIPO (PCT)
Prior art keywords
public network
evpn
route
network
network device
Prior art date
Application number
PCT/CN2017/097113
Other languages
English (en)
French (fr)
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 WO2018028676A1 publication Critical patent/WO2018028676A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • 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/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/08—Learning-based routing, e.g. using neural networks or artificial intelligence

Definitions

  • EVPN Ethernet Virtual Private Network
  • the control plane advertises EVPN routing information using the Multi-Protocol Border Gateway Protocol (MP-BGP).
  • MP-BGP Multi-Protocol Border Gateway Protocol
  • the data plane is virtualized.
  • the VXLAN (Virtual Extensible Local Area Network) encapsulation method forwards packets.
  • EVPN can provide Layer 2 interconnection for the same subnet of the same tenant based on the existing service provider or enterprise IP network, and provide Layer 3 interconnection for different subnets of the same tenant through the EVPN gateway, and provide it with the external network. Three layers of interconnection.
  • FIG. 1 is a flowchart of a method provided by an embodiment of the present application
  • Figure 2 is a schematic view of an embodiment of the present application.
  • Figure 3 is a schematic view of an embodiment of the present application.
  • Figure 4 is a schematic view of an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of hardware of a network device according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic structural diagram of an interworking logic between an EVPN and a public network according to some embodiments of the present disclosure.
  • EVPN typically uses a core (Spine)-leaf hierarchy.
  • the device in the leaf layer serves as the VXLAN tunnel end point (VTEP: VXLAN Tunnel End Point), and performs EVPN-related processing on the packet.
  • the device in the Spine layer is the core device and forwards the packet according to the destination IP address of the packet.
  • AS Autonomous System
  • IBGP intra-BGP
  • RR Route Reflector
  • the EVPN networking will be superimposed on the basis of the original network model. This will cause the EVPN networking to communicate with the original network.
  • the original network is a public network, and the EVPN must be in the virtual routing forwarding (VRF) instance.
  • VRF virtual routing forwarding
  • the EVPN can communicate with the public network, and the user can flexibly deploy the EVPN service on the public network.
  • FIG. 1 is a flowchart of a method provided by the present application.
  • the EVPN service When the EVPN service is deployed on the network device in the public network, the EVPN can communicate with the public network on the network device. As shown in Figure 1, the network device can perform the following steps:
  • step 201 the EVPN route is learned.
  • network devices can advertise routes based on BGP.
  • learning the EVPN route means that in the EVPN, the network device learns the route advertised by the BGP peer.
  • Step 202 Determine whether the route identifier (RT: Route-Target) corresponding to the learned EVPN route is the same as the input (Import) RT of the public network instance configured by the network device, and if yes, add the learned EVPN route. Local local network routing table to the network device.
  • RT Route-Target
  • the network device can advertise the EVPN route through a routing message (such as an Update message).
  • the message can carry the RT attribute.
  • the network device can learn the RT and the message carried in the message when learning the EVPN route through the routing message.
  • the Import RT of the public network instance configured on the network device is compared. If they are the same, the EVPN route is added to the local public network routing table.
  • the EVPN route added to the local public network routing table is a route learned from the EVPN.
  • the public network is configured as a public network instance in a network device.
  • the public network instance can be used as a special VRF instance. You can configure the Import RT and Export RT for the public network instance.
  • the public network instance configured on the network device is configured with multiple pairs of Import RT and Export RT. A pair of Import RT and Export RT correspond to one EVPN. Based on this, in step 202, it is determined whether the RT corresponding to the learned EVPN route is the same as the Import RT of the public network instance configured by the network device.
  • the method is as follows: In the Import RT of the public network instance that is configured on the network device, the Import RT that matches the RT corresponding to the EVPN route is searched. If the RT is determined, the RT corresponding to the EVPN route and the configured network device are determined. The Import RT of the network instance is the same.
  • step 202 the public network route and the EVPN route are all in the same public network routing table, and then, when the public network accesses the EVPN packet or the EVPN accesses the public network packet, the public network can be based on the public network.
  • the routing table forwards the packets, and implements EVPN and public network interworking based on the same public network routing table.
  • step 202 when it is determined that the learned RT of the EVPN route is different from the imported RT of the public network instance configured by the network device, the learned EVPN route may also be learned according to the RT matching principle. Join the local private network routing table of the network device.
  • Step 203 Receive a packet, the packet being the EVPN packet accessed by the public network, or the EVPN accessing the public network packet.
  • Step 204 Match the route used for forwarding the packet in the local public network routing table, and forward the packet according to the matched route.
  • the network device stores the public network route and the EVPN route to the local public network routing table. Therefore, whether the public network accesses the EVPN packet or the EVPN accesses the public network packet, the network device will receive the local public.
  • the routing table of the network matches the route used to forward the packet. This implements the interworking between the EVPN and the public network.
  • FIG. 1 Based on the above description, the flow shown in FIG. 1 is described by way of a plurality of specific embodiments:
  • FIG. 2 is a schematic diagram of an embodiment of the present application.
  • both the device 1 and the device 4 are configured with a public network service and an EVPN service.
  • the device 1 and the device 2 belong to the leaf device of the Leaf layer, and the device 3 and the device 4 belong to the Spine device of the Spine layer.
  • the public network instance is configured on the device 1 and the device 2, and the route distinguishing identifier (RD: Route Distinguisher), Import RT, and Export RT are configured.
  • RD Route Distinguisher
  • Import RT Import RT
  • Export RT Export RT
  • the RD of the public network instance is equal to the RD of the VRF instance to which the EVPN service belongs.
  • the Export RT of the public network instance is equal to the Import RT of the VRF instance to which the EVPN service belongs.
  • the Import RT of the public network instance is equal to the Export of the VRF instance to which the EVPN service belongs. RT. Therefore, in this embodiment, even if the EVPN service is deployed on the device 1 and the device 2, the public network instance can be deployed.
  • the host 1 of the access device 1 (the IP address is 192.168.1.10) runs the EVPN service
  • the host 2 of the access device 1 (the IP address is 192.168.2.20) runs the public network service.
  • Run the EVPN service on the host 3 of the access device 2 (the IP address is 192.168.3.30), and run the host 4 on the access device 2 (the IP address is 192.168.4.40).
  • Network business the IP address is 192.168.1.10) runs the EVPN service
  • the host 2 of the access device 1 (the IP address is 192.168.2.20) runs the public network service.
  • Run the EVPN service on the host 3 of the access device 2 (the IP address is 192.168.3.30)
  • run the host 4 on the access device 2 (the IP address is 192.168.4.40).
  • the device learns the routes of the two hosts. To distinguish the routes of the two hosts, in all the examples in this disclosure, The route of the host where the EVPN service is deployed is called the EVPN route of the host. The route of the host where the public network service is deployed is called the public network route of the host. For example, in this example, device 1 can learn the EVPN route of host 1 and the public network route of host 2; device 2 can learn the EVPN route of host 3 and the public network route of host 4.
  • the device 1 checks the configuration of the virtual switch interface (VSI: Virtual Switch Interface) used for accessing the host 1;
  • VSI Virtual Switch Interface
  • the device 1 finds that the configuration of the VSI indicates public network access, that is, in fact, despite the fact that the VSI accesses the host 1 (equivalent to EVPN access) running the EVPN service, in this embodiment, in order to implement the EVPN. Interworking with the public network, configuring the VSI, indicating that the VSI is a public network access, rather than a de facto EVPN access. In this case, the device 1 directly routes the EVPN of the host 1 (recorded as EVPN route 1_1). ) Add to the local public network routing table of device 1.
  • the device 1 advertises the EVPN route 1_1 through the routing message, where the RD and the RT are respectively the RD and the Export RT of the VRF instance to which the EVPN service (corresponding to the host 1) belongs.
  • device 1 adds the public network route of host 2 (referred to as public network route 1_2) to the local public network routing table of device 1.
  • Device 1 advertises public network route 1_2 and does not carry RD or RT information.
  • Device 3 and device 4 learn EVPN route 1_1 and public network route 1_2.
  • the device 2 learns the EVPN route 1_1, and determines whether the RT corresponding to the EVPN route 1_1 is the same as the Import RT of the public network instance configured by the network device.
  • the device 2 finds that the RT carried by the EVPN route 1_1 is the same as the import RT of the public network instance configured by the network device 2, and the device 2 adds the EVPN route 1_1 (hereinafter referred to as the EVPN route 1_1_2) to the local public network routing table of the device 2.
  • the device 2 learns the public network route 1_2, and the device 2 adds the learned public network route 1_2 (hereinafter referred to as the public network route 1_2_2) to the local public network routing table of the device 2.
  • the process of the route advertised by the device 1 is described above.
  • the process of advertised by the device 2 is similar to that of the device 1 and will not be repeated.
  • the host 1 in the EVPN accesses the host 2 in the public network
  • the host 1 first sends an access message (recorded as message 1) to the device 1.
  • the device 1 When receiving the packet 1, the device 1 matches the route for forwarding the packet 1 in the local public network routing table of the device 1.
  • the device 1 forwards the packet 1 through the public network route 1_2 matched in the local public network routing table of the device 1. Finally, the host 2 receives the packet 1. It can be seen that the packets from the EVPN host can be forwarded to the public network host. The host 1 of the EVPN and the host 2 of the public network can communicate with each other through the commonly accessed device 1.
  • the host 4 in the public network accesses the host 1 in the EVPN, the host 4 first sends an access message (recorded as message 2) to the device 2.
  • an access message (recorded as message 2)
  • the device 2 When receiving the packet 2, the device 2 matches the route for forwarding the packet 2 in the local public network routing table of the device 2.
  • the device 2 forwards the packet 2 through the route of the host 1 that is matched in the local public network routing table of the device 2, that is, the EVPN route 1_1_1, and finally the host 1 receives the packet 2. It can be seen that the public network host and the EVPN host across devices can also communicate.
  • FIG. 3 is a schematic diagram of an embodiment of the present application.
  • the public network service and the EVPN service are deployed on the device 1, the device 3, and the device 4.
  • the device 2 does not deploy the EVPN service and only the public network service is deployed.
  • the device 1 and the device 2 belong to the leaf device of the Leaf layer, and the device 3 and the device 4 belong to the Spine device of the Spine layer.
  • only the public network instance can be configured on the device 1, the device 3, and the device 4.
  • the host 1 of the access device 1 (the IP address is 192.168.1.10) runs the EVPN service
  • the host 2 of the access device 1 (the IP address is 192.168.2.20) runs the public network service.
  • the public network service is run on the host 4 of the access device 2 (the IP address is 192.168.4.40).
  • the device 1 checks the configuration of the virtual switch interface (VSI) that is used for the access of the host 1;
  • VSI virtual switch interface
  • the device 1 finds that the configuration of the VSI indicates public network access, that is, in fact, despite the fact that the VSI accesses the host 1 (equivalent to EVPN access) running the EVPN service, in this embodiment, in order to implement the EVPN. Interworking with the public network, configuring the VSI, indicating that the VSI is a public network access, rather than a de facto EVPN access. In this case, the device 1 directly routes the EVPN of the host 1 (recorded as EVPN route 1_1). ) Add to the local public network routing table of device 1.
  • the device 1 advertises the EVPN route 1_1 through the routing message, where the RD and the RT are respectively the RD and the Export RT of the VRF instance (corresponding to the host 1) to which the EVPN service belongs.
  • device 1 adds the public network route of host 2 (referred to as public network route 1_2) to the local public network forwarding table of device 1.
  • the device 1 advertises the public network route 1_2 according to the public network route advertisement mode. It does not carry RD or RT information.
  • the device 4 receives the route advertised by device 1 as an example.
  • the principle of device 4 is similar.
  • the device 3 learns the EVPN route 1_1 issued by the device 1.
  • the device 3 determines whether the RT corresponding to the learned EVPN route 1_1 is the same as the Import RT of the public network instance configured by the network device 3;
  • the device 3 finds that the learned EVPN route 1_1 carries the same RT as the public network instance configured on the network device 3, and the device 3 adds the learned EVPN route 1_1 (hereinafter referred to as EVPN route 1_1_3) to the device 3. Local public network forwarding table.
  • Device 3 continues to publish the learned EVPN route 1_1.
  • the device 3 advertises the learned EVPN route 1_1 to the device 2, the device 3 deploys the public network service but does not deploy the EVPN service. If the device 3 and the device 2 establish only the public network IPv4 BGP neighbor relationship, the device 3
  • the learned EVPN route 1_1 is advertised to the public network BGP peer, that is, device 2, and the routing message does not carry RD and RT information.
  • the route advertised to device 2 is recorded as public network route 1_1.
  • the device 3 learns the public network route 1_2 issued by the device 1, and directly adds the learned public network route 1_2 (hereinafter referred to as the public network route 1_2_3) to the local public network routing table of the device 3.
  • Device 3 continues to publish the learned public network route 1_2.
  • the device 2 learns the public network route 1_1 issued by the device 3, and directly adds the learned public network route 1_1 (hereinafter referred to as the public network route 1_1_2) to the local public network routing table of the device 2.
  • the device 2 learns the public network route 1_2 issued by the device 3, and directly adds the learned public network route 1_2 (hereinafter referred to as the public network route 1_2_2) to the local public network routing table of the device 2.
  • the host 4 in the public network accesses the host 1 in the EVPN, the host 4 first sends an access message (recorded as message 21) to the device 2.
  • the device 2 When the device 2 receives the packet 21, the device 2 matches the route for forwarding the packet 21 in the local public network routing table of the device 2.
  • the device 2 forwards the packet 21 to the device 3 through the public network route 1_1_2 matched in the local public network routing table of the device 2.
  • the device 3 receives the packet 21 and matches the route for forwarding the packet 21 in the local public network routing table of the device 3.
  • the device 3 forwards the packet 21 to the device 1 through the route for forwarding the packet 21, that is, the EVPN route 1_1_3, which is matched in the local public network routing table of the device 3.
  • the packet 21 of the public network accessing the EVPN is accessed by the device 3 to enter the EVPN.
  • Eventually host 1 will receive message 21.
  • host 1 in the EVPN accesses host 4 in the public network, host 1 first sends an access message (recorded as message 22) to device 1.
  • the device 1 When receiving the packet 22, the device 1 matches the route for forwarding the packet 22 in the local public network routing table of the device 1.
  • the device 1 forwards the message 22 by the route (referred to as the public network route 2_4) that is matched in the local public network routing table of the device 1 for forwarding the packet 22.
  • the packet 22 of the EVPN accessing the public network is accessed by the device 1 in the public network.
  • Eventually host 4 will receive message 22.
  • the host 1 of the EVPN and the host 4 of the public network can communicate with each other across devices.
  • FIG. 4 is a schematic diagram of an embodiment of the present application.
  • This embodiment is an application scenario in which a network device is newly added on the basis of the embodiment shown in FIG. 3.
  • the newly added network device is referred to as device 5 and device 6.
  • the device 5 and the device 6 are deployed with the EVPN service but the public network service is not deployed.
  • the device 5 and the device 6 are leaf devices.
  • the host 5 of the access device 5 (the IP address is 192.168.5.50) and the host 6 of the access device 6 (the IP address is 192.168.6.60) run the EVPN service.
  • the processing of the device 1 and the device 2 is similar to the description of the embodiment shown in FIG. 3, and details are not described herein again.
  • the device 5 and the device 6 are newly added, when the device 3 (the device 4 is similar in principle) learns the EVPN route 1_1, the device 5 and the device 6 continue to issue the EVPN route 1_1.
  • the device 3 When the device 3 learns the public network route 1_2, the device 3 further forwards the public network route 1_2 to the device 5 and the device 6.
  • the device 3 sends the learned public network route 1_2 to the device 5 as an example.
  • the device 5 deploys the EVPN service and does not deploy the public network service. Therefore, when the device 3 advertises the public network route 1_2 to the device 5, the device 3 needs to follow the route in the EVPN.
  • the advertised route is advertised as the EVPN route 5_2.
  • the routing message carries the RD and the RT.
  • the RD is the RD of the public network instance and the RT is the export RT of the public network instance. It should be noted that if the public network is configured with multiple pairs of export RTs, the RT carried in the routing message is the export RT of all public network instances.
  • the principle that the device 3 advertises the public network route 1_2 to the device 6 is the same as the device 3 that advertises the public network route 1_2 to the device 5.
  • the device 5 When the device 5 receives the EVPN route 1_1, the device 5 learns the EVPN route 1_1 and records the EVPN route 1_1 to the local private network routing table of the device 5 according to the RT matching principle.
  • the host 5 of the EVPN accesses the host 2 in the public network
  • the host 5 first sends an access message (recorded as message 3) to the device 5.
  • the device 5 matches the route for forwarding the packet 3 in the local public network routing table of the device 5.
  • the device 5 forwards the packet 3 to the device 3 through the EVPN route 5_2 matched in the local private network routing table of the device 5.
  • the device 3 receives the packet 3 and matches the route for forwarding the packet 3 in the local public network routing table of the device 3.
  • the device 3 forwards the packet 3 to the device 1 through the public network route 1_2_3 matched in the local public network routing table of the device 3.
  • the packets accessed by the EVPN are accessed by the device 3 on the public network.
  • Eventually host 2 will receive message 3. It can be seen that the host 5 of the EVPN and the host 2 of the public network can communicate with each other across devices.
  • the BGP multi-instance technology can be used to deploy the EVPN and the public network in different BGP instances.
  • the EVPN is deployed in the BGP EVPN instance
  • the public network is deployed in the public network BGP instance. It is equivalent to running two BGP control planes on the user network.
  • the two BGP control planes are isolated from each other.
  • the data planes of the two BGP control planes can be interconnected or isolated. This can be well controlled and extended.
  • the policy of not releasing the route to the same device according to the route is as follows.
  • the route is advertised.
  • the public network route in the public network does not need to be advertised through the EVPN extension.
  • the EVPN private network route can be configured to filter the public network route.
  • FIG. 5 is a hardware structural diagram of a network device according to some embodiments of the present disclosure.
  • the network device 50 can include a processor 51 and a machine readable storage medium 52.
  • the processor 51 and the machine readable storage medium 52 can communicate via the system bus 53.
  • the processor 51 can perform the method of interworking between the EVPN and the public network described above.
  • the machine-readable storage medium 52 referred to herein can be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like.
  • the machine readable storage medium 92 may be a RAM (Random Access Memory), a volatile memory, a nonvolatile memory, a flash memory, a storage drive (such as a hard disk drive), a solid state drive, or any type of A storage disk (such as a compact disc, a DVD, etc.), or a similar storage medium, or a combination thereof.
  • the EVPN and public network interworking logic 60 may be:
  • the learning unit 601 is configured to learn an EVPN route.
  • the routing unit 602 is configured to determine whether the route identifier Export RT corresponding to the EVPN route learned by the learning unit 601 is the same as the input Import RT of the public network instance configured by the network device of the network device, and if yes, The EVPN route learned by the learning unit is added to the local public network routing table;
  • the storage unit 603 is configured to store a local public network routing table.
  • the receiving unit 604 is configured to receive a packet, where the packet is a packet that is accessed by the public network to access the EVPN, or is a packet that the EVPN accesses the public network.
  • the forwarding unit 605 is configured to match the route used for forwarding the packet in the local public network routing table, and forward the packet according to the matched route.
  • the routing unit 602 is configured to:
  • Import RT In the Import RT of the public network instance that is configured on the network device, find the Import RT that matches the RT corresponding to the EVPN route. If found, determine the RT corresponding to the EVPN route and the public network instance configured on the network device. Import RT is the same.
  • the routing unit 602 when the network device is a branch Leaf device, the routing unit 602 further checks a configuration of a virtual switching interface VSI that is locally used for host access; if the configuration indicates public network access, The learned EVPN route of the host is added to the local public network routing table, and the EVPN route of the host is advertised.
  • VSI virtual switching interface
  • the routing unit 602 when the network device is a core Spine device, and the Spine device deploys a public network service and an EVPN service, the routing unit 602 further advertises the learned EVPN route to the deployed public. A leaf device that does not deploy EVPN services.
  • the network device when the network device is a core Spine device, and the Spine device deploys a public network service and an EVPN service,
  • the learning unit 601 further learns a public network route
  • the routing unit 602 further adds the learned public network route to the local public network routing table, and advertises the public network route to the leaf device that deploys the EVPN service but does not deploy the public network service.
  • a machine readable storage medium comprising machine executable instructions, such as a map A machine readable storage medium 52 in the computer executable instructions executable by the processor 51 in the network device to implement the EVPN and public network interworking methods described above.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Artificial Intelligence (AREA)
  • Evolutionary Computation (AREA)
  • Medical Informatics (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供了以太网虚拟私有网络EVPN与公网互通方法及网络设备。本实施例中，网络设备学习EVPN路由；判断所述EVPN路由对应的路由标识符RT是否与本网络设备已配置的公网实例的输入Import RT相同，如果是，将所述EVPN路由添加至本地公网路由表；接收报文，所述报文为公网访问EVPN的报文，或者为EVPN访问公网的报文；在本地公网路由表中匹配用于转发报文的路由，依据匹配到的路由转发报文。

Description

以太网虚拟私有网络EVPN与公网互通
相关申请的交叉引用
本专利申请要求于2016年8月12日提交的、申请号为201610664322.5、发明名称为“以太网虚拟私有网络EVPN与公网互通方法及其装置”的中国专利申请的优先权，该申请的全文以引用的方式并入本文中。
背景技术
以太网虚拟私有网络(EVPN：Ethernet Virtual Private Network)是一种二层VPN技术，控制平面采用多协议边界网关协议(MP-BGP：Multi-Protocol Border Gateway Protocol)通告EVPN路由信息，数据平面采用虚拟可扩展局域网(VXLAN：Virtual Extensible Local Area Network)封装方式转发报文。EVPN可以基于已有的服务提供商或企业IP网络，为同一租户的相同子网提供二层互联，以及通过EVPN网关为同一租户的不同子网提供三层互联，并为其提供与外部网络的三层互联。
附图说明
图1为本申请实施例提供的方法流程图；
图2为本申请实施例的示意图；
图3为本申请实施例的示意图；
图4为本申请实施例的示意图；
图5为本申请实施例提供的网络设备的硬件结构示意图；
图6为本申请一些实施例提供的EVPN与公网互通逻辑的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
EVPN通常采用核心(Spine)-分支(Leaf)的分层结构。其中，Leaf层的设备作为VXLAN隧道终结点(VTEP：VXLAN Tunnel End Point)，对报文进行EVPN相关处理；Spine层的设备为核心设备，根据报文的目的IP地址转发报文。当EVPN中的所有设备属于同一个自治系统(AS：Autonomous System)时，为了避免在所有VTEP之间建立域内BGP(IBGP：Internal Border Gateway Protocol)对等体，可以将核心设备配置为路由反射器(RR：Route Reflector)。
在实际应用中，会在不改变原有网络模型的基础上叠加EVPN组网，这就会存在EVPN组网与原有网络互通的问题。比如，原有网络为公网，而EVPN必须运行在虚拟路由转发(VRF：Virtual Routing Forwarding)实例下，公网与EVPN无法互通。
在本申请提供的方法中能够实现EVPN与公网互通，方便用户在公网中灵活部署EVPN业务。
下面通过图1对本申请提供的方法进行描述。
参见图1，图1为本申请提供的方法流程图。当公网中的网络设备部署了EVPN业务，为在该网络设备上实现EVPN与公网互通，则如图1所示，该网络设备可执行以下步骤：
步骤201，学习EVPN路由。
在EVPN中，网络设备可以基于BGP发布路由。这里，学习EVPN路由指：在EVPN中，网络设备学习BGP对等体发布的路由。
步骤202，判断学习到的EVPN路由对应的路由标识符(RT：Route-Target)是否与本网络设备已配置的公网实例的输入(Import)RT相同，如果是，将学习到的EVPN路由添加至网络设备的本地公网路由表。
EVPN中，网络设备可以通过路由消息(例如Update消息)发布EVPN路由，该消息中可以携带RT属性，相应的，网络设备学习通过路由消息学习到EVPN路由时，可以将消息中携带的RT与本网络设备已配置的公网实例的Import RT进行比较，如果相同，则将该EVPN路由添加至本地公网路由表。其中，添加到该本地公网路由表中的EVPN路由为从EVPN学习到的路由。
在本申请中，将公网看作一个公网实例配置在网络设备中，该公网实例可以作为一个特殊VRF实例。其中，可以为该公网实例配置Import RT、输出(Export)RT。需要说明的是，在本申请中，为了实现公网和多个EVPN互通，则网络设备上配置的公网实例会配置多对Import RT、Export RT。一对Import RT、Export RT对应一个EVPN。基于此，在步骤202中，判断学习到的EVPN路由对应的RT是否与本网络设备已配置的公网实例的Import RT相同具 体为：在本网络设备已配置的公网实例的Import RT中查找与所述EVPN路由对应的RT相匹配的Import RT，如果查找到，确定EVPN路由对应的RT与本网络设备已配置的公网实例的Import RT相同。
通过步骤202，能够实现公网路由和EVPN路由都处于同一张公网路由表中，之后，后续当收到公网访问EVPN的报文或者EVPN访问公网的报文时，可基于该公网路由表进行报文转发，实现了基于同一张公网路由表进行EVPN与公网互通。
需要说明的是，在步骤202中，当判断出学习到的EVPN路由携带的RT与本网络设备已配置的公网实例的Import RT均不同时，还可根据RT匹配原则将学习到的EVPN路由加入到网络设备的本地私网路由表中。
步骤203，接收报文，报文为公网访问EVPN的报文，或者为EVPN访问公网的报文。
步骤204，在本地公网路由表中匹配用于转发报文的路由，依据匹配到的路由转发报文。
如上描述，网络设备将公网路由和EVPN路由存放至本地同一张公网路由表中，因此，不管是公网访问EVPN的报文，还是EVPN访问公网的报文，网络设备都会从本地公网路由表中匹配到用于转发该报文的路由，这实现了EVPN与公网互通。
至此，完成图1所示的流程。
基于上面描述下面通过多个具体实施例对图1所示的流程进行举例描述：
在一实施例中，参见图2，图2为本申请实施例的示意图。在本实施例中，设备1至设备4均部署了公网业务和EVPN业务，其中，设备1、设备2属于Leaf层的Leaf设备，设备3、设备4属于Spine层的Spine设备。
在本实施例中，设备1、设备2上配置了公网实例，公网实例被配置了路由区分标识(RD：Route Distinguisher)、Import RT、Export RT。
在本实施例中，公网实例的RD等于EVPN业务所属VRF实例的RD，公网实例的Export RT等于EVPN业务所属VRF实例的Import RT，公网实例的Import RT等于EVPN业务所属VRF实例的Export RT。因此，在本实施例中，即使设备1、设备2部署了EVPN业务，可部署公网实例即可，没有必要再重复配置EVPN业务所属VRF实例。
在本实施例中，接入设备1的主机1(IP地址为192.168.1.10)上运行EVPN业务，接入设备1的主机2(IP地址为192.168.2.20)上运行公网业务。接入设备2的主机3(IP地址为192.168.3.30)上运行EVPN业务，接入设备2的主机4(IP地址为192.168.4.40)上运行公 网业务。
设备上即可以接入部署EVPN业务的主机，也可以接入部署公网业务的主机，设备会学习到两种主机的路由，为了区分这两种主机的路由，在本公开所有的示例中，将部署EVPN业务的主机的路由称为主机的EVPN路由，将部署了公网业务的主机的路由称为主机的公网路由。例如，在本示例中，设备1可以学习到主机1的EVPN路由以及主机2的公网路由；设备2可以学习到主机3的EVPN路由以及主机4的公网路由。
以设备1发布路由为例，则，
设备1检查用于主机1接入的虚拟交换接口(VSI：Virtual Switch Interface)的配置；
设备1发现VSI的配置指示公网接入，也就是说，尽管事实上VSI接入的是运行了EVPN业务的主机1(相当于EVPN接入)，但是，在本实施例中，为了实现EVPN与公网互通，对VSI进行配置，通过该配置指示VSI是公网接入，而非事实上的EVPN接入，此种情况下，设备1直接将主机1的EVPN路由(记为EVPN路由1_1)添加至设备1的本地公网路由表。
设备1通过路由消息发布EVPN路由1_1，其中携带RD、RT分别为EVPN业务(对应于主机1)所属VRF实例的RD、Export RT。
因为主机2运行在公网中，设备1将主机2的公网路由(记为公网路由1_2)添加至设备1的本地公网路由表。
设备1发布公网路由1_2，不携带RD、RT信息。
设备3、设备4学习EVPN路由1_1、公网路由1_2。
设备2学习EVPN路由1_1，判断EVPN路由1_1对应的RT是否和本网络设备配置的公网实例的Import RT相同；
设备2发现EVPN路由1_1携带的RT和本网络设备2配置的公网实例的Import RT相同，设备2将EVPN路由1_1(此时记为EVPN路由1_1_2)添加至设备2的本地公网路由表。
设备2学习公网路由1_2，设备2将学习到的公网路由1_2(此时记为公网路由1_2_2)添加至设备2的本地公网路由表。
以上对设备1发布路由的流程进行了描述，设备2发布路由的流程类似设备1，不再重复赘述。
基于上述路由的发布，则当EVPN内的主机1访问公网内的主机2时，主机1先把访问报文(记为报文1)发送给设备1。
设备1收到报文1时，在设备1的本地公网路由表中匹配用于转发报文1的路由。
设备1通过在设备1的本地公网路由表中匹配到的公网路由1_2转发报文1，最终，主机2会收到报文1。可以看出，来自EVPN主机的报文在设备1就可转发给公网主机，EVPN的主机1和公网的主机2通过共同接入的设备1即可实现互通。
当公网内的主机4访问EVPN内的主机1时，主机4先把访问报文(记为报文2)发送给设备2。
设备2收到报文2时，在设备2的本地公网路由表中匹配用于转发报文2的路由。
设备2通过在设备2的本地公网路由表中匹配到的主机1的路由，即EVPN路由1_1_1，转发报文2，最终主机1会收到报文2。可以看出，跨设备的公网主机和EVPN主机也可实现互通。
至此，完成本实施例的描述。
在一个实施例中，参见图3，图3为本申请一个实施例的示意图。在本实施例中，设备1、设备3、设备4均部署了公网业务和EVPN业务，设备2未部署EVPN业务仅部署公网业务。其中，设备1、设备2属于Leaf层的Leaf设备，设备3、设备4属于Spine层的Spine设备。
在本实施例2中，设备1、设备3、设备4上可仅配置公网实例。
在本实施例中，接入设备1的主机1(IP地址为192.168.1.10)上运行EVPN业务，接入设备1的主机2(IP地址为192.168.2.20)上运行公网业务。接入设备2的主机4(IP地址为192.168.4.40)上运行公网业务。
以设备1发布路由为例，则，
设备1检查本地用于主机1接入的虚拟交换接口(VSI：Virtual Switch Interface)的配置；
设备1发现VSI的配置指示公网接入，也就是说，尽管事实上VSI接入的是运行了EVPN业务的主机1(相当于EVPN接入)，但是，在本实施例中，为了实现EVPN与公网互通，对VSI进行配置，通过该配置指示VSI是公网接入，而非事实上的EVPN接入，此种情况下，设备1直接将主机1的EVPN路由(记为EVPN路由1_1)添加至设备1的本地公网路由表。
设备1通过路由消息发布EVPN路由1_1，其中携带的RD、RT分别为EVPN业务所属VRF实例(对应于主机1)的RD、Export RT。
因为主机2运行在公网中，设备1将主机2的公网路由(记为公网路由1_2)添加至设备1的本地公网转发表。
设备1按照公网路由发布方式发布公网路由1_2，不携带RD、RT信息。
以设备3收到设备1发布的路由为例，设备4原理类似。
设备3学习设备1发布的EVPN路由1_1。
设备3判断学习到的EVPN路由1_1对应的RT是否和本网络设备3配置的公网实例的Import RT相同；
设备3发现学习到的EVPN路由1_1携带的RT和本网络设备3配置的公网实例的Import RT相同，设备3将学习到的EVPN路由1_1(此时记为EVPN路由1_1_3)添加至设备3的本地公网转发表。设备3继续发布学习到的EVPN路由1_1。其中，设备3在向设备2发布学习到的EVPN路由1_1时，由于设备2部署了公网业务但未部署EVPN业务，设备3和设备2建立的仅是公网IPv4BGP邻居关系，则设备3将学习到的EVPN路由1_1向公网BGP对等体、即设备2发布，路由消息中不携带RD和RT信息，此处，将向设备2发布的路由记为公网路由1_1。
设备3学习设备1发布的公网路由1_2，则直接将学习到的公网路由1_2(此时记为公网路由1_2_3)添加至设备3的本地公网路由表。
设备3继续发布学习到的公网路由1_2。
设备2学习设备3发布的公网路由1_1，直接将学习到的公网路由1_1(此时记为公网路由1_1_2)添加至设备2的本地公网路由表。
设备2学习设备3发布的公网路由1_2，直接将学习到的公网路由1_2(此时记为公网路由1_2_2)添加至设备2的本地公网路由表。
基于上面描述，当公网内的主机4访问EVPN内的主机1时，主机4先把访问报文(记为报文21)发送给设备2。
设备2收到报文21时，在设备2的本地公网路由表中匹配用于转发报文21的路由。
设备2通过在设备2本地公网路由表中匹配到的公网路由1_1_2转发报文21给设备3。
设备3接收到报文21，在设备3的本地公网路由表中匹配用于转发报文21的路由。
设备3通过在设备3的本地公网路由表中匹配到的用于转发报文21的路由，即EVPN路由1_1_3，转发报文21给设备1。公网访问EVPN的报文21在设备3进入EVPN内访问。最终主机1会收到报文21。
当EVPN内的主机1访问公网内的主机4时，主机1先把访问报文(记为报文22)发送给设备1。
设备1收到报文22时，在设备1的本地公网路由表中匹配用于转发报文22的路由。
设备1通过在设备1的本地公网路由表中匹配到的用于转发报文22的路由(记为公网路由2_4)转发报文22。EVPN访问公网的报文22在设备1进入公网内访问。最终主机4会收到报文22。
可以看出，EVPN的主机1和公网内的主机4可以跨设备实现互通。
至此，完成本实施例的描述。
在一个实施例中，参见图4，图4为本申请一个实施例的示意图。本实施例是在如图3所示实施例的基础上新增加了网络设备的应用场景。该新增加的网络设备记为设备5、设备6。设备5、设备6部署了EVPN业务但未部署公网业务，设备5、设备6为leaf设备。接入设备5的主机5(IP地址为192.168.5.50)、接入设备6的主机6(IP地址为192.168.6.60)运行EVPN业务。
在本实施例中，设备1、设备2的处理类似如图3所示实施例的描述，这里不再赘述。
在本实施例中，因为新增加了设备5、设备6，当设备3(设备4原理类似)学习到EVPN路由1_1时，还会进一步向设备5、设备6继续发布EVPN路由1_1。
当设备3学习到公网路由1_2时，还会进一步向设备5、设备6继续发布公网路由1_2。以设备3向设备5发布学习到的公网路由1_2为例，因为设备5部署了EVPN业务未部署公网业务，所以设备3在向设备5发布公网路由1_2时，需要按照EVPN中的路由发布方式发布该路由，此处，将向设备5发布的路由记为EVPN路由5_2，路由消息中携带RD、RT，其中，RD为公网实例的RD、RT为公网实例的Export RT。需要说明的是，如果公网实例配置了多对Export RT，则此时路由消息中携带的RT为所有公网实例的Export RT。
设备3向设备6发布公网路由1_2的原理与上述的设备3向设备5发布公网路由1_2相同。
当设备5收到设备3发布EVPN路由1_1时，学习EVPN路由1_1，根据RT匹配原则将EVPN路由1_1记录至设备5的本地私网路由表。
基于上面描述，则当EVPN下的主机5访问公网内的主机2时，主机5先把访问报文(记为报文3)发送给设备5。
设备5收到报文3时，在设备5的本地公网路由表中匹配用于转发报文3的路由。
设备5通过在设备5的本地私网路由表中匹配到的EVPN路由5_2转发报文3给设备3。
设备3接收到报文3，在设备3的本地公网路由表中匹配用于转发报文3的路由。
设备3通过在设备3的本地公网路由表中匹配到的公网路由1_2_3转发报文3给设备1。EVPN访问的报文在设备3进入公网内访问。最终主机2会收到报文3。可以看出，EVPN的主机5和公网内的主机2可以跨设备实现互通。
至此，完成本实施例的描述。
以上通过多个实施例对本发明提供的EVPN和公网互通进行了描述。
需要说明的是，在本申请中，结合BGP多实例技术，可以将EVPN和公网部署在不同BGP多实例中，比如EVPN部署在BGP EVPN实例中，公网部署在公网BGP实例中，这相当于在用户网络上可以运行两个BGP控制平面，两个BGP控制平面互相隔离；而，两个BGP控制平面的数据平面既可以互通，也可以隔离，这可以很好地进行控制和扩展。
需要说明的是，为避免路由重复发布，在本申请中，不管是Leaf层的设备，还是Spine层的设备，其在发布路由时，都是尽可能按照路由不重复发布给同一个设备的策略来发布路由，具体地，在公网中的公网路由不需要通过EVPN扩展发布，而EVPN私网路由在发布时可配置策略过滤掉公网路由。
以上对本申请提供的方法进行了描述。下面对本申请提供的装置进行描述：
参见图5，图5为本申请一些实施例提供的网络设备的硬件结构图。该网络设备50可包括处理器51以及机器可读存储介质52。其中，处理器51和机器可读存储介质52可经由系统总线53通信。并且，通过读取并执行机器可读存储介质52中存储的与EVPN与公网互通逻辑60对应的机器可执行指令，处理器51可执行上文所述的EVPN与公网互通的方法。
本文提到的机器可读存储介质52可以是任何电子、磁性、光学或其他物理存储装置，可以包含或存储信息，如可执行指令、数据，等等。例如，所述机器可读存储介质92可以是RAM(Random Access Memory，随机存取存储器)、易失存储器、非易失性存储器、闪存、存储驱动器(如硬盘驱动器)、固态硬盘、任何类型的存储盘(如光盘、DVD等)，或者类似的存储介质，或者它们的组合。
如图6所示，从功能上划分，所述EVPN与公网互通逻辑60可包括：
学习单元601，用于学习EVPN路由；
路由单元602，用于判断所述学习单元601学习到的EVPN路由对应的路由标识符Export RT是否与所述网络设备的本网络设备已配置的公网实例的输入Import RT相同，如果是，将所述学习单元学习到的EVPN路由添加至本地公网路由表；
存储单元603，用于存储本地公网路由表；
接收单元604，用于接收报文，所述报文为公网访问EVPN的报文，或者为EVPN访问公网的报文；
转发单元605，用于在本地公网路由表中匹配用于转发报文的路由，依据匹配到的路由转发报文。
在一实施例中，当本网络设备已配置的公网实例具有两个以上Import RT时，所述路由单元602用于：
在本网络设备已配置的公网实例的Import RT中查找与所述EVPN路由对应的RT相匹配的Import RT，如果查找到，确定EVPN路由对应的RT与本网络设备已配置的公网实例的Import RT相同。
在一实施例中，当所述网络设备为分支Leaf设备时，所述路由单元602进一步检查本地用于主机接入的虚拟交换接口VSI的配置；若所述配置指示公网接入，则将学习到的所述主机的EVPN路由添加至本地公网路由表，并发布所述主机的EVPN路由。
在一实施例中，当所述网络设备为核心Spine设备、且所述Spine设备部署了公网业务和EVPN业务时，所述路由单元602进一步将学习到的所述EVPN路由发布给部署了公网业务但未部署EVPN业务的Leaf设备。
在一实施例中，当所述网络设备为核心Spine设备、且所述Spine设备部署了公网业务和EVPN业务时，
所述学习单元601进一步学习公网路由；
所述路由单元602进一步将学习到的公网路由添加至本地公网路由表；将所述公网路由发布给部署EVPN业务但未部署公网业务的Leaf设备。
在一实施例中，将所述公网路由发布给部署EVPN业务但未部署公网业务的Leaf设备时，携带本网络设备已配置的公网实例的所有Export RT。
至此，完成图6所示网络设备的结构描述。
根据本申请的示例，还提供了一种包括机器可执行指令的机器可读存储介质，例如图 6中的机器可读存储介质52，所述机器可执行指令可由网络设备中的处理器51执行以实现以上描述的EVPN与公网互通的方法。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
以上对本发明实施例所提供的方法和装置进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (15)

  1. 一种以太网虚拟私有网络EVPN与公网互通方法，包括：
    网络设备学习EVPN路由；
    所述网络设备判断所述EVPN路由对应的路由标识符RT是否与本网络设备已配置的公网实例的输入Import RT相同，如果是，将所述EVPN路由添加至所述网络设备的本地公网路由表；
    所述网络设备接收报文，所述报文为公网访问EVPN的报文，或者为EVPN访问公网的报文；
    所述网络设备在本地公网路由表中匹配用于转发报文的路由，依据匹配到的路由转发报文。
  2. 根据权利要求1所述的方法，其特征在于，当本网络设备已配置的公网实例具有两个以上Import RT时，判断EVPN路由对应的路由标识符RT是否与本网络设备已配置的公网实例的Import RT相同包括：
    所述网络设备在本网络设备已配置的公网实例的Import RT中查找与所述EVPN路由对应的RT相匹配的Import RT，如果查找到，确定EVPN路由对应的RT与本网络设备已配置的公网实例的Import RT相同。
  3. 根据权利要求1所述的方法，其中，当所述网络设备为分支Leaf设备时，该方法还包括：
    所述网络设备检查本地用于主机接入的虚拟交换接口VSI的配置；
    若所述配置指示公网接入，则所述网络设备将学习到的所述主机的EVPN路由添加至本地公网路由表，并发布所述主机的EVPN路由。
  4. 根据权利要求1所述的方法，其中，当所述网络设备为核心Spine设备、且所述Spine设备部署了公网业务和EVPN业务时，该方法还包括：
    所述网络设备将学习到的所述EVPN路由发布给部署了公网业务但未部署EVPN业务的Leaf设备。
  5. 根据权利要求1所述的方法，其特征在于，当所述网络设备为核心Spine设备、且所述Spine设备部署了公网业务和EVPN业务时，该方法还包括：
    所述网络设备学习公网路由，将学习到的公网路由添加至本地公网路由表；
    所述网络设备将所述公网路由发布给部署EVPN业务但未部署公网业务的Leaf设备。
  6. 根据权利要求5所述的方法，其中，
    将所述公网路由发布给部署EVPN业务但未部署公网业务的Leaf设备时，路由消息携带本网络设备已配置的公网实例的所有Export RT。
  7. 一种网络设备，包括：
    处理器和机器可读存储介质，
    所述机器可读存储介质存储有能够被所述处理器执行的机器可执行指令，所述处理器被所述机器可执行指令促使：
    学习EVPN路由；
    判断所述EVPN路由对应的路由标识符RT是否与本网络设备已配置的公网实例的输入Import RT相同，如果是，将所述EVPN路由添加至所述网络设备的本地公网路由表；
    接收报文，所述报文为公网访问EVPN的报文，或者为EVPN访问公网的报文；
    在本地公网路由表中匹配用于转发报文的路由，依据匹配到的路由转发报文。
  8. 根据权利要求7所述的网络设备，其中，当本网络设备已配置的公网实例具有两个以上Import RT时，所述处理器进一步被所述机器可执行指令促使：
    在本网络设备已配置的公网实例的Import RT中查找与所述EVPN路由对应的RT相匹配的Import RT，如果查找到，确定EVPN路由对应的RT与本网络设备已配置的公网实例的Import RT相同。
  9. 根据权利要求7所述的网络设备，其中，当所述网络设备为分支Leaf设备时，所述处理器进一步被所述机器可执行指令促使：
    检查本地用于主机接入的虚拟交换接口VSI的配置；
    若所述配置指示公网接入，则将学习到的所述主机的EVPN路由添加至本地公网路由表，并发布所述主机的EVPN路由。
  10. 根据权利要求7所述的网络设备，其中，当所述网络设备为核心Spine设备、且所述Spine设备部署了公网业务和EVPN业务时，所述处理器进一步被所述机器可执行指令促使：
    将学习到的所述EVPN路由发布给部署了公网业务但未部署EVPN业务的Leaf设备。
  11. 根据权利要求7所述的网络设备，其中，当所述网络设备为核心Spine设备、且所述Spine设备部署了公网业务和EVPN业务时，所述处理器进一步被所述机器可执行指令促使：
    学习公网路由，将学习到的公网路由添加至本地公网路由表；
    将所述公网路由发布给部署EVPN业务但未部署公网业务的Leaf设备。
  12. 根据权利要求11所述的网络设备，其中，
    将所述公网路由发布给部署EVPN业务但未部署公网业务的Leaf设备时，路由消息携带本网络设备已配置的公网实例的所有Export RT。
  13. 一种机器可读存储介质，存储有机器可执行指令，在被网络设备的处理器调用和执行时，所述机器可执行指令促使所述处理器执行：
    学习EVPN路由；
    判断所述EVPN路由对应的路由标识符RT是否与本网络设备已配置的公网实例的输入Import RT相同，如果是，将所述EVPN路由添加至所述网络设备的本地公网路由表；
    接收报文，所述报文为公网访问EVPN的报文，或者为EVPN访问公网的报文；
    在本地公网路由表中匹配用于转发报文的路由，依据匹配到的路由转发报文。
  14. 根据权利要求13所述的机器可读存储介质，其中，当本网络设备已配置的公网实例具有两个以上Import RT时，所述机器可执行指令进一步促使所述处理器执行：
    在本网络设备已配置的公网实例的Import RT中查找与所述EVPN路由对应的RT相匹配的Import RT，如果查找到，确定EVPN路由对应的RT与本网络设备已配置的公网实例的Import RT相同。
  15. 根据权利要求13所述的机器可读存储介质，其中，当所述网络设备为分支Leaf设备时，所述机器可执行指令进一步促使所述处理器执行：
    检查本地用于主机接入的虚拟交换接口VSI的配置；
    若所述配置指示公网接入，则将学习到的所述主机的EVPN路由添加至本地公网路由表，并发布所述主机的EVPN路由。
PCT/CN2017/097113 2016-08-12 2017-08-11 以太网虚拟私有网络evpn与公网互通 WO2018028676A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610664322.5 2016-08-12
CN201610664322.5A CN107733795B (zh) 2016-08-12 2016-08-12 以太网虚拟私有网络evpn与公网互通方法及其装置

Publications (1)

Publication Number Publication Date
WO2018028676A1 true WO2018028676A1 (zh) 2018-02-15

Family

ID=61161671

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/097113 WO2018028676A1 (zh) 2016-08-12 2017-08-11 以太网虚拟私有网络evpn与公网互通

Country Status (2)

Country Link
CN (1) CN107733795B (zh)
WO (1) WO2018028676A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110430076A (zh) * 2019-07-31 2019-11-08 新华三技术有限公司合肥分公司 一种路由管理方法及装置
CN111083034A (zh) * 2019-12-24 2020-04-28 浪潮思科网络科技有限公司 一种在evpn下管理vxlan隧道的方法及设备、介质
CN111464511A (zh) * 2020-03-18 2020-07-28 紫光云技术有限公司 一种用于实现云计算网络中支持多vpc隔离的方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153757B (zh) * 2019-06-29 2023-03-10 华为技术有限公司 通信方法、装置和系统
CN110505152B (zh) * 2019-09-11 2022-02-22 迈普通信技术股份有限公司 路由过滤方法、装置及电子设备
CN110505140B (zh) * 2019-10-09 2021-07-20 中国联合网络通信集团有限公司 基于VxLAN的报文转发方法和网络
CN112887188B (zh) * 2021-02-23 2022-04-01 新华三信息安全技术有限公司 一种报文转发方法及设备
CN114124780B (zh) * 2021-11-15 2023-07-21 迈普通信技术股份有限公司 路由发布方法、装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1708031A (zh) * 2004-06-11 2005-12-14 华为技术有限公司 虚拟专用网的实现方法
CN101083598A (zh) * 2007-06-22 2007-12-05 杭州华三通信技术有限公司 一种虚拟私有网的路由引入方法、系统和运营商边缘设备
US7468956B1 (en) * 2002-08-16 2008-12-23 Juniper Networks, Inc. Managing routing information in a hub-and-spokes network
US7486659B1 (en) * 2003-02-24 2009-02-03 Nortel Networks Limited Method and apparatus for exchanging routing information between virtual private network sites
CN102664811A (zh) * 2012-05-04 2012-09-12 杭州华三通信技术有限公司 报文转发方法和装置
CN103401752A (zh) * 2013-07-23 2013-11-20 迈普通信技术股份有限公司 访问虚拟专用网的方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100571197C (zh) * 2005-11-03 2009-12-16 中兴通讯股份有限公司 一种结合网络地址转换的提供商边缘设备及其使用方法
CN100466589C (zh) * 2006-04-12 2009-03-04 华为技术有限公司 一种实现虚拟专用网访问的方法
CN100550841C (zh) * 2006-07-12 2009-10-14 华为技术有限公司 自治系统边界路由器路由发布方法及自治系统边界路由器

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7468956B1 (en) * 2002-08-16 2008-12-23 Juniper Networks, Inc. Managing routing information in a hub-and-spokes network
US7486659B1 (en) * 2003-02-24 2009-02-03 Nortel Networks Limited Method and apparatus for exchanging routing information between virtual private network sites
CN1708031A (zh) * 2004-06-11 2005-12-14 华为技术有限公司 虚拟专用网的实现方法
CN101083598A (zh) * 2007-06-22 2007-12-05 杭州华三通信技术有限公司 一种虚拟私有网的路由引入方法、系统和运营商边缘设备
CN102664811A (zh) * 2012-05-04 2012-09-12 杭州华三通信技术有限公司 报文转发方法和装置
CN103401752A (zh) * 2013-07-23 2013-11-20 迈普通信技术股份有限公司 访问虚拟专用网的方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ROSEN ET AL.: "NETWORK WORKING GROUP. rfc2547bis , BGP/MPLS IP VPNs", DRAFT-IETF-13VPN-RFC2547BIS-03, 31 October 2004 (2004-10-31), XP055542481 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110430076A (zh) * 2019-07-31 2019-11-08 新华三技术有限公司合肥分公司 一种路由管理方法及装置
CN110430076B (zh) * 2019-07-31 2022-05-31 新华三技术有限公司合肥分公司 一种路由管理方法及装置
CN111083034A (zh) * 2019-12-24 2020-04-28 浪潮思科网络科技有限公司 一种在evpn下管理vxlan隧道的方法及设备、介质
CN111464511A (zh) * 2020-03-18 2020-07-28 紫光云技术有限公司 一种用于实现云计算网络中支持多vpc隔离的方法

Also Published As

Publication number Publication date
CN107733795A (zh) 2018-02-23
CN107733795B (zh) 2020-05-12

Similar Documents

Publication Publication Date Title
WO2018028676A1 (zh) 以太网虚拟私有网络evpn与公网互通
US10333836B2 (en) Convergence for EVPN multi-homed networks
US11032183B2 (en) Routing information validation in SDN environments
US8948055B2 (en) Resilient interworking of shortest path bridging and Ethernet virtual private networks
US9838309B1 (en) Distributed network subnet
WO2018090872A1 (zh) 数据处理
JP2024084781A (ja) 決定的ホスト学習及びローカライズされた統合ルーティング及びブリッジングを有するホストルーテッドオーバーレイ
WO2018040530A1 (zh) 一种确定虚拟机迁移的方法和装置
US9019814B1 (en) Fast failover in multi-homed ethernet virtual private networks
US9100213B1 (en) Synchronizing VPLS gateway MAC addresses
US20160134528A1 (en) Signaling aliasing capability in data centers
US11652791B2 (en) Consolidated routing table for extranet virtual networks
US11159341B2 (en) Forwarding packet
CN113302898A (zh) 将客户机-设备对等互联的虚拟路由控制器
US11516184B2 (en) Firewall service insertion across secure fabric preserving security group tags end to end with dual homed firewall
CN113132235B (zh) 基于虚电路的数据报文处理方法、转发表项的构建方法
US11811613B2 (en) Method and apparatus for automated spanning-tree loop detection in networks
US11743232B2 (en) Software defined branch single internet protocol orchestration
US11177979B2 (en) Synchronizing route
US20240137305A1 (en) Multiple network interfacing
US11159342B2 (en) MAC address synchronization
WO2021146052A1 (en) Live network sandboxing on a centralized management system
US10554549B1 (en) DCI stitching for data center overlays
US10432544B2 (en) Enhanced sequence number updating of routes associated with migrating virtual machines
US20230032240A1 (en) Filtering advertising of route advertisements based on virtual network identifiers

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: 17838806

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: 17838806

Country of ref document: EP

Kind code of ref document: A1