Question 160
A team configures independent tenant gateway identities on each leaf and then expects seamless mobility across one EVPN virtual network. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Check anycast gateway consistency whenever a tenant virtual network is extended to another rack. That is important in this case because a distributed anycast gateway design requires a consistent logical gateway identity across participating VTEPs for the same tenant segment. The scenario was: A team configures independent tenant gateway identities on each leaf and then expects seamless mobility across one EVPN virtual network.
Incorrect Answers
Common ECMP forwarding implementations use stable flow hashing to select paths, so one flow need not balance packet-by-packet across every next hop. Here, a distributed anycast gateway design requires a consistent logical gateway identity across participating VTEPs for the same tenant segment.
Include encapsulation/decapsulation and VNI validation in packet-level overlay fault isolation. That concerns ingress VTEP encapsulation and egress decapsulation, while the issue here is anycast default gateway identity across leafs. Compare approved shared gateway address and MAC behavior on the relevant IRB interfaces, then test host mobility and local L3 forwarding. Specifically for the prevention question, the case to validate is: A team configures independent tenant gateway identities on each leaf and then expects seamless mobility across one EVPN virtual network.
Include route type and tenant VRF checks in intersubnet rollout procedures. Here, a distributed anycast gateway design requires a consistent logical gateway identity across participating VTEPs for the same tenant segment.