Abstract: Techniques are described to provide layer 2 (L2) circuit failover in the event connectivity to an Ethernet Virtual Private Network (EVPN) instance is lost. For example, if one of multi-homed provider edge (PE) devices loses connectivity to the EVPN instance, the PE device may mark its customer-facing interface as down and propagate the interface status to the access node such that the access node may update its routing information to switch L2 circuits to another one of the multi-homed PE devices having reachability to the EVPN instance. In some examples, the plurality of PE devices may further implement Connectivity Fault Management (CFM) techniques to propagate the interface status to the access node such that the access node may update its forwarding information to send traffic on a different L2 circuit to another one of the multi-homed PE devices having reachability to the EVPN instance.

Abstract: Techniques are described to provide layer 2 (L2) circuit failover in the event connectivity to an Ethernet Virtual Private Network (EVPN) instance is lost. For example, if one of multi-homed provider edge (PE) devices loses connectivity to the EVPN instance, the PE device may mark its customer-facing interface as down and propagate the interface status to the access node such that the access node may update its routing information to switch L2 circuits to another one of the multi-homed PE devices having reachability to the EVPN instance. In some examples, the plurality of PE devices may further implement Connectivity Fault Management (CFM) techniques to propagate the interface status to the access node such that the access node may update its forwarding information to send traffic on a different L2 circuit to another one of the multi-homed PE devices having reachability to the EVPN instance.

Abstract: Techniques are described to provide layer 2 (L2) circuit failover in the event connectivity to an Ethernet Virtual Private Network (EVPN) instance is lost. For example, if one of multi-homed provider edge (PE) devices loses connectivity to the EVPN instance, the PE device may mark its customer-facing interface as down and propagate the interface status to the access node such that the access node may update its routing information to switch L2 circuits to another one of the multi-homed PE devices having reachability to the EVPN instance. In some examples, the plurality of PE devices may further implement Connectivity Fault Management (CFM) techniques to propagate the interface status to the access node such that the access node may update its forwarding information to send traffic on a different L2 circuit to another one of the multi-homed PE devices having reachability to the EVPN instance.

Abstract: The problem of looping at the egress of a transport network with a CE multihomed to a protected egress PE and a backup/protector egress PE can be avoided by (a) enabling the protector egress PE to distinguish between fast reroute (FRR) traffic coming from the protected egress PE and normal known unicast (KU) traffic coming from a PE of the transport network that is not attached to the same multihomed segment; (b) receiving, by the protector egress PE, known unicast data, to be forwarded to the CE; (c) determining, by the protector egress PE, that a link between it and the CE is unavailable; and (d) responsive to determining that the link between the protector egress PE and the CE is unavailable, (1) determining whether the known unicast traffic received was sent from the protected egress PE or from another PE of the transport network that is not attached to the same multihomed segment, and (2) responsive to a determination that the known unicast traffic received was sent from the protected egress PE, discardi

Abstract: The problem of looping at the egress of a transport network with a CE multihomed to a protected egress PE and a backup/protector egress PE can be avoided by (a) enabling the protector egress PE to distinguish between fast reroute (FRR) traffic coming from the protected egress PE and normal known unicast (KU) traffic coming from a PE of the transport network that is not attached to the same multihomed segment; (b) receiving, by the protector egress PE, known unicast data, to be forwarded to the CE; (c) determining, by the protector egress PE, that a link between it and the CE is unavailable; and (d) responsive to determining that the link between the protector egress PE and the CE is unavailable, (1) determining whether the known unicast traffic received was sent from the protected egress PE or from another PE of the transport network that is not attached to the same multihomed segment, and (2) responsive to a determination that the known unicast traffic received was sent from the protected egress PE, discardi

Abstract: Techniques are described to provide layer 2 (L2) circuit failover in the event connectivity to an Ethernet Virtual Private Network (EVPN) instance is lost. For example, if one of multi-homed provider edge (PE) devices loses connectivity to the EVPN instance, the PE device may mark its customer-facing interface as down and propagate the interface status to the access node such that the access node may update its routing information to switch L2 circuits to another one of the multi-homed PE devices having reachability to the EVPN instance. In some examples, the plurality of PE devices may further implement Connectivity Fault Management (CFM) techniques to propagate the interface status to the access node such that the access node may update its forwarding information to send traffic on a different L2 circuit to another one of the multi-homed PE devices having reachability to the EVPN instance.

Abstract: In one example, a network device includes an interface card comprising a physical network interface; a forwarding component associated with the interface card; a control unit comprising one or more processors, wherein the control unit is configured to program the forwarding component to configure sets of one or more valid media access control (MAC) addresses in association with respective logical interfaces of a plurality of logical interfaces configured for the physical interface, wherein the forwarding component is configured to identify a logical interface of the plurality of logical interfaces with which to process a packet received by the network device at the physical interface, and wherein the forwarding component is configured to, in response to a determination that the set of valid MAC addresses associated with the identified logical interface does not include a valid MAC address that matches a destination MAC address of the packet, drop the packet.