Layer 3 convergence for EVPN link failure

Patent metadata

Field	Value
Publication number	US-9992154-B2
Application number	US-201615198948-A
Country	US
Kind code	B2
Filing date	Jun 30, 2016
Priority date	Jun 30, 2016
Publication date	Jun 5, 2018
Grant date	Jun 5, 2018

Abstract

A network device is configured to provide, via an Ethernet segment with a customer network, active-active multi-homing L2 virtual bridge connectivity to the customer network using an EVPN instance (EVI) and L3 routing using an IRB interface that is a L3 routing interface assigned to the EVI; to receive, from a peer PE device of the EVPN instance, an EVPN route comprising an L2-L3 binding for a customer device of the customer network and associating the L2-L3 binding with the Ethernet segment, the L2-L3 binding comprising an L2 and an L3 address assigned to the customer device, wherein the peer PE device provides, with the network device and via the Ethernet segment, active-active multi-homing L2 virtual bridge connectivity to the customer network; and to forward, via the Ethernet segment and based at least on the L2-L3 binding received from the peer PE device, an L3 packet to the customer device.

First claim

What is claimed is:

1. A method comprising:
receiving, by a first provider edge (PE) device of a layer 3 network, configuration data configuring the first PE device to provide, via an Ethernet segment with a customer network, active-active multi-homing layer 2 (L2) virtual bridge connectivity to the customer network using an Ethernet Virtual Private Network (EVPN) instance and layer 3 (L3) routing using an integrated routing and bridging (IRB) interface that is a L3 routing interface assigned to the EVPN instance;
receiving, by the first PE device from a second PE device of the EVPN instance, an EVPN route comprising an L2-L3 binding for a customer device of the customer network and associating the L2-L3 binding with the Ethernet segment, the L2-L3 binding comprising an L2 address and an L3 address that are assigned to the customer device,
wherein the second PE device provides, with the first PE device and via the Ethernet segment, active-active multi-homing L2 virtual bridge connectivity to the customer network; and
forwarding, by the first PE device via the Ethernet segment and based at least on the L2-L3 binding received from the second PE device, an L3 packet to the customer device.

2. The method of claim 1 , further comprising:
by the first PE device in response to receiving, from the second PE device, an indication to withdraw an Ethernet Auto-Discovery (A-D) route associated with the Ethernet segment:
determining the L2-L3 binding received from the second PE device is associated with the Ethernet segment; and
generating an address resolution entry based on the L2-L3 binding received from the second PE device, wherein the address resolution entry associates the L2 address and the L3 address that are assigned to the customer device,

wherein forwarding the L3 packet to the customer device comprises forwarding, by the first PE device based on the address resolution entry, the L3 packet to the customer device.

3. The method of claim 2 , wherein the address resolution entry comprises one of an Address Request Protocol (ARP) entry and a Neighbor Discovery Protocol (NDP) entry, the method further comprising:
installing, by the first PE device, the address resolution entry to one of an ARP table or NDP table.

4. The method of claim 2 , further comprising:
sending, by the first PE device in response to generating the address resolution entry and via a routing protocol, the L2-L3 binding received from the second PE device to a PE device of the EVPN instance.

5. The method of claim 2 , wherein generating the address resolution entry based on the L2-L3 binding comprises generating, by the first PE device, the address resolution entry based on the L2-L3 binding only if the L2-L3 binding is not already locally learned by the first PE device on a local attachment circuit for the EVPN instance.

6. The method of claim 1 , further comprising:
sending, by the first PE device via a routing protocol, the L2-L3 binding received from the second PE device to a PE device of the EVPN instance.

7. The method of claim 6 , wherein sending the L2-L3 binding to the PE device of the EVPN instance comprises:
outputting, by the first PE device, an EVPN MAC/IP advertisement message for the EVPN instance and comprising the L2-L3 binding received from the second PE device.

8. The method of claim 1 , wherein the EVPN route comprising the L2-L3 binding comprises an EVPN MAC/IP Advertisement route.

9. The method of claim 1 , wherein forwarding the L3 packet to the customer device comprises forwarding, by the first PE device, the L3 packet without the first PE device storing an address resolution entry for the L2-L3 binding for the customer device locally learned on a local attachment circuit for the EVPN instance.

10. The method of claim 1 , wherein forwarding the L3 packet to the customer device comprises generating, based on the L2-L3 binding, an L2 packet comprising the L3 packet and an L2 header having a destination L2 address that is the L2 address of the L2-L3 binding.

11. A network device configured as a provider edge (PE) device of a layer 3 network, comprising:
one or more processors coupled to a memory,
wherein the one or more processors are configured to receive configuration data that configures the network device to provide, via an Ethernet segment with a customer network, active-active multi-homing layer 2 (L2) virtual bridge connectivity to the customer network using an Ethernet Virtual Private Network (EVPN) instance and layer 3 (L3) routing using an integrated routing and bridging (IRB) interface that is a L3 routing interface assigned to the EVPN instance,
wherein the one or more processors are configured to receive, from a peer PE device of the EVPN instance, an EVPN route comprising an L2-L3 binding for a customer device of the customer network and associating the L2-L3 binding with the Ethernet segment, the L2-L3 binding comprising an L2 address and an L3 address that are assigned to the customer device, wherein the peer PE device provides, with the network device and via the Ethernet segment, active-active multi-homing L2 virtual bridge connectivity to the customer network; and
wherein the one or more processors are configured to forward, via the Ethernet segment and based at least on the L2-L3 binding received from the peer PE device, an L3 packet to the customer device.

12. The network device of claim 11 ,
wherein the one or more processors are further configured to, in response to receiving, from the peer PE device, an indication to withdraw an Ethernet Auto-Discovery (A-D) route associated with the Ethernet segment:
determine the L2-L3 binding received from the peer PE device is associated with the Ethernet segment; and
generate an address resolution entry based on the L2-L3 binding received from the peer PE device, wherein the address resolution entry associates the L2 address and the L3 address that are assigned to the customer device,

wherein the one or more processors configured to forward the L3 packet to the customer device is further configured to forward, based on the address resolution entry, the L3 packet to the customer device.

13. The network device of claim 12 ,
wherein the address resolution entry comprises one of an Address Request Protocol (ARP) entry and a Neighbor Discovery Protocol (NDP) entry,
wherein the one or more processors are further configured to install the address resolution entry to one of an ARP table or NDP table.

14. The network device of claim 12 , the one or more processors are further configured to send, in response to generating the address resolution entry and via a routing protocol, the L2-L3 binding received from the peer PE device to a PE device of the EVPN instance.

15. The network device of claim 12 , wherein the one or more processors are further configured to generate the address resolution entry based on the L2-L3 binding only if the L2-L3 binding is not already locally learned by the network device on a local attachment circuit for the EVPN instance.

16. The network device of claim 11 , the one or more processors are further configured to send, via a routing protocol, the L2-L3 binding received from the peer PE device to a PE device of the EVPN instance.

17. The network device of claim 16 , wherein, to send the L2-L3 binding to the peer PE device of the EVPN instance, the one or more processors are further configured to output an EVPN MAC/IP advertisement message for the EVPN instance and comprising the L2-L3 binding received from the peer PE device.

18. The network device of claim 11 , wherei

Assignees

• Juniper Networks Inc

Inventors

• Bickhart Ryan
• Singh Nitin
• Lin Wen
• Hosseini Hassan C

Classifications

• H04L45/50

  using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title

• H04L12/66

  Arrangements for connecting between networks having differing types of switching systems, e.g. gateways · CPC title

• H04L12/462

  LAN interconnection over a bridge based backbone · CPC title

• H04L12/4641 Primary

  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 title

• H04L45/66

  Layer 2 routing, e.g. in Ethernet based MAN's · CPC title