Layer2 provider services, pseudowires and EVPN
Define the attachment and service topology
A customer attachment connects an access circuit to the intended provider service context. Point-to-point Ethernet service connects two relevant ends, while multipoint arrangements connect more than two participants under their supported forwarding model. E-Line, E-LAN and rooted-multipoint terminology describe service intent rather than a universal single implementation. The customer-facing encapsulation, VLAN handling and effective MTU must match the actual contract and configured path.
Distinguish signaling and forwarding
A pseudowire represents a supported emulated link across the provider network. Its service signaling and forwarding labels differ from the underlay path used to reach the remote provider edge. LDP-signaled and BGP/EVPN-related arrangements have different control-plane behavior; neither protocol name alone proves every service is configured correctly. A virtual-circuit identifier or service label mismatch can break the service even while core reachability and unrelated customer traffic remain healthy. Examine the actual local and remote attachment states together.
Learn where reachability information comes from
Traditional multipoint Ethernet forwarding can involve MAC learning and flooding under its model, while EVPN uses BGP-based advertisement of relevant reachability and service information. Different EVPN route types serve different purposes. A control-plane MAC advertisement is not proof that every data path, VLAN mapping or remote attachment is operational. Split-horizon and multihoming mechanisms address loops and redundancy under their actual procedures; they do not make every failure invisible to every application.
Preserve frame and failure assumptions
Check customer and provider MTU accounting, encapsulation overhead and supported control-word behavior rather than assume a successful small ping proves large frames fit. Forwarding tests need the correct source, destination and service context. Ethernet service separation is not payload encryption. If a design includes integrated routing/bridging, identify that extra routing role rather than claiming a provider edge never processes an IP route. Before any proposed change, document the intended attachment, signaling, labels, forwarding and verification, with an authorized recovery path. These exercises make no pseudowire, EVPN, VLAN or interface change and do not claim complete current official practical coverage or command compatibility across router platforms.