Engineers debate why ingress replication lists on municipal leaves grow as more VTEPs join each VNI. What scaling relationship should they cite?
Select an answer to reveal the explanation.
Short Explanation
Ingress replication is like the mayor’s office printing one flyer per branch—more branches, more copies. As VTEPs join a VNI, that replication list and the BUM fan-out work grow with them. It is not an STP sideshow and it does not magically stay at one remote leaf forever.
Full Explanation
Ingress replication requires the ingress VTEP to send a unicast VXLAN copy to each remote VTEP in the VNI’s replication set. Therefore list size and BUM encapsulation cost scale with VTEP membership, which is a key reason large fabrics evaluate multicast underlays, optimized EVPN multicast features, or careful VNI scoping. EVPN does not limit a VNI to a single remote leaf, and STP underlay changes are not the driver of EVPN replication-list growth. Capacity planning should include BUM replication scale alongside unicast overlay traffic.