Per RFC 7432 (BGP MPLS-Based EVPN), split-horizon filtering for all-active multihoming is enforced at the PE level, not at the CE. When the non-DF PE (PE3) floods BUM traffic received from the multihomed CE1 into the core, it must push the ESI split-horizon label — advertised by PE1 for that Ethernet segment — onto the copy sent to PE1, since PE1 is attached to the same ES as PE3. Upon receiving that packet, PE1 performs a label lookup and, because the label matches its local ESI, it is required to NOT forward the packet onto that Ethernet segment at all — the filtering decision and action occur entirely within PE1's forwarding plane. CE1 is a Layer 2 customer device with no awareness of ESI or MPLS labels, so it cannot 'discard' anything based on such a label; it simply never receives the looped copy in the first place. This makes the statement describing PE1 forwarding the packet to CE1, and CE1 discarding it based on the ESI label, factually incorrect — the real mechanism has PE1, not CE1, dropping the traffic before it reaches the customer edge.
Community Discussion