L2 stretch across the city’s DCI works, but unknown unicast and broadcast traffic is saturating the WAN links. What troubleshooting focus is appropriate?
Select an answer to reveal the explanation.
Short Explanation
L2 stretch turns the WAN into another flood domain for BUM if you are not careful—like leaving every firehose pointed at the metro pipe. Hunt DF behavior, replication design, and whether that segment truly needs L2 across sites. Sometimes Type-5 L3 DCI is the calmer fix.
Full Explanation
Excessive BUM is a common L2 DCI failure mode. Operators should inspect designated-forwarder behavior for multi-homed segments, BUM replication method (ingress replication versus multicast), ARP/ND rate, and whether applications can move to L3 DCI instead. Blaming Type-5 alone, relying only on STP timers, or shutting VTEP loopbacks are incorrect mitigations.