Objectives
The simulator ticks each one as soon as the network meets it.
Find what is wrong (show l2vpn bridge-domain detail on each PE).
Fix PE2’s customer port: it is not interface … l2transport.
Fix the pw-id: PE3 uses 300 toward PE1, where the VPN uses 100.
Fix the mesh: PE2 has no neighbor toward PE3.
All three PEs have two pseudowires up, and PC1, PC2 and PC3 reach each other.
Before you start
A port in a bridge-domain must be l2transport, or its attachment circuit stays down. A PW ID must match on both ends. And VPLS needs a full mesh, because a frame from one pseudowire never leaves on another: with no PE2–PE3 pseudowire, those two sites cannot talk even through PE1.
Concept
VPLS: a virtual switch across an MPLS core
VPLS joins many sites into one Layer 2 segment. Each PE runs a virtual switch (a VFI on Cisco, a VSI on Huawei) with a pseudowire to every other PE, and learns MAC addresses behind its ports and pseudowires. Unknown frames are flooded out of all of them.
Concept
Pseudowires: Ethernet through an MPLS core
A pseudowire makes an MPLS core look like one long cable between two customer ports, called attachment circuits. The ingress PE pushes two labels on each frame: an inner VC label that names the far attachment circuit, and an outer transport label that carries it across the core. LDP signals the VC label between the two PEs, directly, through a session that may cross many routers.
