Question 80
A tenant VLAN is stretched across racks, yet remote VTEPs do not learn which peers participate in its broadcast domain, breaking intended flooding of unknown traffic. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Check BUM membership whenever adding VNIs or extending a bridge domain to a new rack. Tenant flood membership is a separate control-plane requirement from individual host MAC advertisement.
Incorrect Answers
A shared Ethernet segment identity is important for supported EVPN multihoming coordination of the same access segment. For the current prevention question, the evidence instead states: A tenant VLAN is stretched across racks, yet remote VTEPs do not learn which peers participate in its broadcast domain, breaking intended flooding of unknown traffic. Here, eVPN Type 3 IMET signaling can advertise VTEP membership information used for broadcast, unknown-unicast and multicast replication in a VXLAN domain.
Maintain automated checks for VNI service identity during VLAN renumbering and rack expansion. That concerns VXLAN VNI-to-VLAN mapping, while the issue here is EVPN Type 3 inclusive membership for BUM. Inspect the tenant's EVPN Type 3 reachability and import scope, and repair the supported BUM replication membership for its VNI.
VXLAN adds outer transport headers, making the required underlay packet size greater than the original tenant Ethernet payload. However, the present prevention decision is grounded in: A tenant VLAN is stretched across racks, yet remote VTEPs do not learn which peers participate in its broadcast domain, breaking intended flooding of unknown traffic. For this issue, inspect the tenant's EVPN Type 3 reachability and import scope, and repair the supported BUM replication membership for its VNI.