Layer 3 convergence for evpn link failure

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.

1 - 20 . (canceled) 
     
     
         21 . A method comprising:
 receiving, by a first provider edge (PE) device of a layer 3 (L3) network, configuration data configuring the first PE device to provide, with a second PE device of the L3 network using an Ethernet Virtual Private Network (EVPN) instance and via an Ethernet segment, active-active multi-homing layer 2 (L2) connectivity to a customer network;   receiving, by the first PE device from the second PE device, an EVPN route comprising an L2-L3 binding of address information for a customer device of the customer network; and   forwarding, by the first PE device via the Ethernet segment and based at least on the L2-L3 binding, an L3 packet to the customer device.   
     
     
         22 . The method of  claim 21 , wherein the configuration data configures the first PE device with an integrated routing and bridging (IRB) interface that is an L3 routing interface assigned to the EVPN instance, the method further comprising:
 receiving, by the first PE device, the L3 packet via the IRB interface; and   forwarding, by the first PE device, the L3 packet via a bridge domain for the IRB interface.   
     
     
         23 . The method of  claim 21 ,
 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.   
     
     
         24 . The method of  claim 23 , wherein the address resolution entry comprises one of an Address Resolution Protocol (ARP) entry or 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.   
     
     
         25 . The method of  claim 23 , 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.   
     
     
         26 . The method of  claim 23 , 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. 
     
     
         27 . The method of  claim 21 , 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.   
     
     
         28 . The method of  claim 27 , 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, the EVPN MAC/IP advertisement message comprising the L2-L3 binding received from the second PE device.   
     
     
         29 . The method of  claim 21 , wherein the EVPN route comprises an EVPN MAC/IP Advertisement route. 
     
     
         30 . The method of  claim 21 , 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. 
     
     
         31 . The method of  claim 21 , 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. 
     
     
         32 . A network device operable as a provider edge (PE) device of a layer 3 (L3) network, comprising:
 one or more processors operably coupled to a memory,   wherein the one or more processors are configured to receive configuration data configuring the PE device to provide, with a peer PE device of the L3 network using an Ethernet Virtual Private Network (EVPN) instance and via an Ethernet segment, active-active multi-homing layer 2 (L2) connectivity to a customer network,   wherein the one or more processors are configured to receive, from the peer PE device, an EVPN route comprising an L2-L3 binding of address information for a customer device of the customer network,   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 
 send, via a routing protocol, the L2-L3 binding received from the peer PE device to a PE device of the EVPN instance. 
   
     
     
         33 . The network device of  claim 32 ,
 wherein the configuration data configures the PE device with an integrated routing and bridging (IRB) interface that is an L3 routing interface assigned to the EVPN instance, and   wherein the one or more processors are configured to receive an L3 packet via the IRB interface, and   wherein the or more processors are configured to forward, based at least on the L2-L3 binding, the L3 packet via a bridge domain for the IRB interface.   
     
     
         34 . The network device of  claim 32 ,
 wherein the or more processors are configured to 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, and   wherein the one or more processors are configured to forward, based on the address resolution entry, an L3 packet to the customer device.   
     
     
         35 . The network device of  claim 34 ,
 wherein the address resolution entry comprises one of an Address Resolution Protocol (ARP) entry or a Neighbor Discovery Protocol (NDP) entry, and   wherein the one or more processors are further configured to install the address resolution entry to one of an ARP table or NDP table.   
     
     
         36 . The network device of  claim 34 , 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. 
     
     
         37 . The network device of  claim 32 , wherein 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. 
     
     
         38 . The network device of  claim 37 , wherein, to send the L2-L3 binding to the 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. 
     
     
         39 . The network device of  claim 32 , wherein the EVPN route includes an identifier for the Ethernet segment. 
     
     
         40 . A non-transitory computer-readable medium comprising instructions for causing one or more programmable processors of a first provider edge (PE) device of a layer 3 network to:
 receive configuration data configuring the first PE device to provide, with a second PE device of the L3 network using an Ethernet Virtual Private Network (EVPN) instance and via an Ethernet segment, active-active multi-homing layer 2 (L2) connectivity to a customer network;   receive, from the second PE device, an EVPN route comprising an L2-L3 binding of address information for a customer device of the customer network; and   forward, via the Ethernet segment and based at least on the L2-L3 binding, an L3 packet to the customer device.