SYNCHRONIZING ROUTE

• US 20200136863A1
• Filed: 06/26/2018
• Published: 04/30/2020
• Est. Priority Date: 06/26/2017
• Status: Active Grant

• Current Assignee: New H3C Technologies Co., Ltd. (Tsinghua Holdings Co., Ltd.)
• Original Assignee: New H3C Technologies Co., Ltd. (Tsinghua Holdings Co., Ltd.)
• Inventors: HUANG, Liwei, WANG, Wei
• Granted Patent: US 11,177,979 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 45/08 Learning-based routing, e.g. using neural networks or artificial intelligence
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 45/66 Layer 2 routing, e.g. in Ethernet based MAN's
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 61/2592 using tunnelling or encapsulation

Abstract

In an example of a method of synchronizing a route, a first VTEP in a first EVPN learns an address of a first VM connected with the first VTEP; sends the learned address to a second VTEP connected with the first VTEP via a first EVPN route, where the second VTEP belongs to any of the first EVPN and a second EVPN of a different level from the first EVPN; receives a second EVPN route carrying an address of a second VM and a destination IP address for establishing a VXLAN tunnel; creates a route entry containing the address of the second VM, and nexthop information contained in the route entry is the destination IP address carried in the second EVPN route; and establishes a VXLAN tunnel between the first VTEP and a VTEP identified by the destination IP address carried in the second EVPN route.

Claims

1. A method of synchronizing a route, comprising:

learning, by a first VXLAN Tunnel End Point (VTEP) in a first Ethernet Virtual Private Network (EVPN), an address of a first Virtual Machine (VM) connected with the first VTEP;

sending, by the first VTEP, the learned address of the first VM to a second VTEP connected with the first VTEP via a first EVPN route,

wherein, the first EVPN route carries a destination IP address for establishing a VXLAN tunnel, and the destination IP address is an IP address of the first VTEP, and

wherein, the second VTEP belongs to any of the first EVPN and a second EVPN of a different level from the first EVPN;

receiving, by the first VTEP, a second EVPN route carrying an address of a second VM and a destination IP address for establishing a VXLAN tunnel;

creating, by the first VTEP, a route entry containing the address of the second VM, wherein next hop information contained in the route entry is the destination IP address carried in the second EVPN route; and

establishing, by the first VTEP, a VXLAN tunnel between the first VTEP and a VTEP identified by the destination IP address carried in the second EVPN route.

2. The method according to claim 1, wherein

an EVPN neighbor relationship is established between VTEPs in a same EVPN, and

a Multiprotocol Border Gateway Protocol (MP-BGP) neighbor relationship is established between VTEPs in EVPNs of different levels.

3. The method according to claim 2, wherein in the case that the second VTEP belongs to the second EVPN,

sending the learned address of the first VM to the second VTEP via the first EVPN route comprises:

carrying, by the first VTEP, the first EVPN route in an MP-BGP route, and sending the MP-BGP route to the second VTEP, wherein a private network identifier in the MP-BGP route is used to indicate that the MP-BGP route carries an EVPN route.

4. The method according to claim 1, wherein creating the route entry containing the address of the second VM comprises:

creating, by the first VTEP, the route entry containing the address of the second VM and corresponding to a first VPN when determining that the first VPN corresponding to a Route Target (RT) carried in the second EVPN route exists on the first VTEP.

5. The method according to claim 3, wherein the first VTEP receives the second EVPN route in any of the following manners:

receiving, by the first VTEP, the second EVPN route from a VTEP establishing an EVPN neighbor relationship with the first VTEP;

or

receiving, by the first VTEP, the MP-BGP route from a VTEP establishing an MP-BGP neighbor relationship with the first VTEP, and

acquiring, by the first VTEP, the second EVPN route from the received MP-BGP route in the case of determining that an EVPN route is carried in the MP-BGP route according to the private network identifier carried in the received MP-BGP route.

6. The method according to claim 2, further comprising:

in the case that the second VTEP belongs to the first EVPN,

forwarding, by the first VTEP, the second EVPN route to the second VTEP; and

in the case that the second VTEP belongs to the second EVPN,

carrying, by the first VTEP, the second EVPN route in an MP-BGP route, and sending the MP-BGP route to the second VTEP, wherein the sent MP-BGP route carries a private network identifier used to indicate that the MP-BGP route carries an EVPN route.

7. The method according to claim 2, wherein in the case that the second VTEP belongs to the second EVPN, the method further comprises:

receiving, by the second VTEP, a third EVPN route;

forwarding, by the second VTEP, the third EVPN route to a VTEP in the second EVPN, comprising;

replacing, by the second VTEP, a Route Distinguisher (RD) carried in the third EVPN route with an RD corresponding to a second VPN to which an ingress port of the third EVPN route belongs, adding a Route Target (RT) corresponding to the second VPN to the third EVPN route, and forwarding the third EVPN route to a VTEP establishing an EVPN neighbor relationship with the second VTEP; and

forwarding, by the second VTEP, the third EVPN route to a VTEP in an EVPN of a different level from the second EVPN, comprising;

carrying, by the second VTEP, the third EVPN route in an MP-BGP route and forwarding the MP-BGP route to a VTEP that is in a third VPN and establishes an MP-BGP neighbor relationship with the second VTEP when the second VTEP determines that the third VPN corresponding to the RT carried in the third EVPN route exists on the second VTEP.

8-13. -13. (canceled)

14. An apparatus for synchronizing a route, comprising:

a processor, and

a non-transitory machine-readable storage medium storing machine-executable instructions executable by the processor,

wherein the processor is caused by the machine-executable instructions to;

learn an address of a first Virtual Machine (VM) connected with the first VTEP;

send the learned address of the first VM to a second VTEP connected with the first VTEP via a first EVPN route,

wherein, the first EVPN route carries a destination IP address for establishing a VXLAN tunnel, and the destination IP address is an IP address of the first VTEP, and

wherein, the second VTEP belongs to any of the first EVPN and a second EVPN of a different level from the first EVPN;

receive a second EVPN route carrying an address of a second VM and a destination IP address for establishing a VXLAN tunnel;

create a route entry containing the address of the second VM, wherein next hop information contained in the route entry is the destination IP address carried in the second EVPN route; and

establish a VXLAN tunnel between the first VTEP and a VTEP identified by the destination IP address carried in the second EVPN route.

16. The apparatus for synchronizing a route according to claim 14, wherein

an EVPN neighbor relationship is established between VTEPs in a same EVPN, and

a Multiprotocol Border Gateway Protocol (MP-BGP) neighbor relationship is established between VTEPs in EVPNs of different levels.

17. The apparatus for synchronizing a route according to claim 16, wherein in the case that the second VTEP belongs to the second EVPN, when sending the learned address of the first VM to the second VTEP via the first EVPN route, the processor is caused to:

carry the first EVPN route in an MP-BGP route and send the MP-BGP route to the second VTEP, wherein a private network identifier in the MP-BGP route is used to indicate that the MP-BGP route carries an EVPN route.

18. The apparatus for synchronizing a route according to claim 14, wherein when creating the route entry containing the address of the second VM, the processor is caused to:

create the route entry containing the address of the second VM and corresponding to a first VPN when determining that the first VPN corresponding to a Route Target (RT) carried in the second EVPN route exists on the first VTEP.

19. The apparatus for synchronizing a route according to claim 17, wherein when receiving the second EVPN route, the processor is caused to:

receive the second EVPN route from a VTEP establishing an EVPN neighbor relationship with the first VTEP;

or

receive the MP-BGP route from a VTEP establishing an MP-BGP neighbor relationship with the first VTEP, and

acquire the second EVPN route from the received MP-BGP route in the case of determining that an EVPN route is carried in the MP-BGP route according to the private network identifier carried in the received MP-BGP route.

20. The apparatus for synchronizing a route according to claim 16, wherein the processor is further caused to:

in the case that the second VTEP belongs to the first EVPN,

forward the second EVPN route to the second VTEP; and

in the case that the second VTEP belongs to the second EVPN,

carry the second EVPN route in an MP-BGP route, and send the MP-BGP route to the second VTEP, wherein the sent MP-BGP route carries a private network identifier used to indicate that the MP-BGP route carries an EVPN route.

21. The apparatus for synchronizing a route according to claim 16, wherein in the case that the second VTEP belongs to the second EVPN, the processor is further caused to:

receive a third EVPN route;

forward the third EVPN route to a VTEP in the second EVPN, comprising;

replace a Route Distinguisher (RD) carried in the third EVPN route with an RD corresponding to a second VPN to which an ingress port of the third EVPN route belongs, add a Route Target (RT) corresponding to the second VPN to the third EVPN route, and forward the third EVPN route to a VTEP establishing an EVPN neighbor relationship with the second VTEP; and

forward the third EVPN route to a VTEP in an EVPN of a different level from the second EVPN, comprising;

carry the third EVPN route in an MP-BGP route and forward the MP-BGP route to a VTEP that is in a third VPN and establishes an MP-BGP neighbor relationship with the second VTEP when it is determined that the third VPN corresponding to the RT carried in the third EVPN route exists on the second VTEP.

15. A machine-readable storage medium storing machine-executable instructions, wherein the machine-executable instructions are invoked an executed by a processor to:

learn an address of a first Virtual Machine (VM) connected with the first VTEP;

send the learned address of the first VM to a second VTEP connected with the first VTEP via a first EVPN route,

wherein, the first EVPN route carries a destination IP address for establishing a VXLAN tunnel, and the destination IP address is an IP address of the first VTEP, and

wherein, the second VTEP belongs to any of the first EVPN and a second EVPN of a different level from the first EVPN;

receive a second EVPN route carrying an address of a second VM and a destination IP address for establishing a VXLAN tunnel;

create a route entry containing the address of the second VM, wherein next hop information contained in the route entry is the destination IP address carried in the second EVPN route; and

establish a VXLAN tunnel between the first VTEP and a VTEP identified by the destination IP address carried in the second EVPN route.

22. The machine-readable storage medium according to claim 15, wherein in the case that the second VTEP belongs to the second EVPN, when sending the learned address of the first VM to the second VTEP via the first EVPN route, the processor is caused to:

carry the first EVPN route in an MP-BGP route and send the MP-BGP route to the second VTEP, wherein a private network identifier in the MP-BGP route is used to indicate that the MP-BGP route carries an EVPN route.

23. The machine-readable storage medium according to claim 15, wherein when creating the route entry containing the address of the second VM, the processor is caused to:

create the route entry containing the address of the second VM and corresponding to a first VPN when determining that the first VPN corresponding to a Route Target (RT) carried in the second EVPN route exists on the first VTEP.

24. The machine-readable storage medium according to claim 22, wherein when receiving the second EVPN route, the processor is caused to:

receive the second EVPN route from a VTEP establishing an EVPN neighbor relationship with the first VTEP;

or

receive the MP-BGP route from a VTEP establishing an MP-BGP neighbor relationship with the first VTEP, and

acquire the second EVPN route from the received MP-BGP route in the case of determining that an EVPN route is carried in the MP-BGP route according to the private network identifier carried in the received MP-BGP route.

25. The machine-readable storage medium according to claim 15, wherein the processor is further caused to:

in the case that the second VTEP belongs to the first EVPN,

forward the second EVPN route to the second VTEP; and

in the case that the second VTEP belongs to the second EVPN,

carry the second EVPN route in an MP-BGP route, and send the MP-BGP route to the second VTEP, wherein the sent MP-BGP route carries a private network identifier used to indicate that the MP-BGP route carries an EVPN route.

26. The machine-readable storage medium according to claim 15, wherein in the case that the second VTEP belongs to the second EVPN, the processor is further caused to:

receive a third EVPN route;

forward the third EVPN route to a VTEP in the second EVPN, comprising;

replace a Route Distinguisher (RD) carried in the third EVPN route with an RD corresponding to a second VPN to which an ingress port of the third EVPN route belongs, add a Route Target (RT) corresponding to the second VPN to the third EVPN route, and forward the third EVPN route to a VTEP establishing an EVPN neighbor relationship with the second VTEP; and

forward the third EVPN route to a VTEP in an EVPN of a different level from the second EVPN, comprising;

carry the third EVPN route in an MP-BGP route and forward the MP-BGP route to a VTEP that is in a third VPN and establishes an MP-BGP neighbor relationship with the second VTEP when it is determined that the third VPN corresponding to the RT carried in the third EVPN route exists on the second VTEP.