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.

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.

Abstract: In general, techniques are provided for described herein that extend existing Ethernet Virtual Private Network (EVPN) protocol signaling mechanisms so that local, multi-homing PEs couple to an Ethernet segment can definitively convey their primary/backup designated forwarder (DF) status to any remote PE of the EVPN. In one example, this is accomplished by utilizing a new extended community attribute to each Ethernet A-D per EVI route advertised by each of the multi-homing PEs to specifically carry the advertising PE's primary or backup status. As such, any receiving remote PE need not rely on the arrival of individual MAC routes from a new primary PE and withdrawal of MAC routes from a former primary PE to update its forwarding information.

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.

Abstract: Techniques are described for providing fast convergence in the event of a link failure in an all-active multi-homed Ethernet virtual private network. A provide edge (PE) network device may pre-configure an interface next hop and secondary next hops. The secondary next hops may be logical links to other PE network devices in the same Ethernet segment. In the event of a link failure in the interface next hop between the PE network device and a customer edge (CE) network device, the PE network device may be configured to forward data traffic to the CE network device using the secondary next hops. In the event of a link failure between the PE network device and a core network, the PE network device may be configured to send an out-of-service message to the CE network device that instructs the CE network device to stop sending traffic to the PE network device.

Abstract: In general, techniques are provided for described herein that extend existing Ethernet Virtual Private Network (EVPN) protocol signaling mechanisms so that local, multi-homing PEs couple to an Ethernet segment can definitively convey their primary/backup designated forwarder (DF) status to any remote PE of the EVPN. In one example, this is accomplished by utilizing a new extended community attribute to each Ethernet A-D per EVI route advertised by each of the multi-homing PEs to specifically carry the advertising PE's primary or backup status. As such, any receiving remote PE need not rely on the arrival of individual MAC routes from a new primary PE and withdrawal of MAC routes from a former primary PE to update its forwarding information.

Abstract: Techniques are described for providing fast convergence in the event of a link failure in an all-active multi-homed Ethernet virtual private network. A provide edge (PE) network device may pre-configure an interface next hop and secondary next hops. The secondary next hops may be logical links to other PE network devices in the same Ethernet segment. In the event of a link failure in the interface next hop between the PE network device and a customer edge (CE) network device, the PE network device may be configured to forward data traffic to the CE network device using the secondary next hops. In the event of a link failure between the PE network device and a core network, the PE network device may be configured to send an out-of-service message to the CE network device that instructs the CE network device to stop sending traffic to the PE network device.