Question 460
At Lakeshore Municipal Networks, while checking a remote VTEP path, the data center fabric team observes: BGP EVPN peers come up over the underlay but a remote VTEP remains unable to carry data traffic. What ongoing operational safeguard directly addresses this root issue?
Explanation
Correct Answer
At Lakeshore Municipal Networks, while checking a remote VTEP path, for Lakeshore Municipal Networks, include the safeguard: Include separate control-plane and VXLAN data-plane checks for every overlay. It reduces repeat risk from the original mechanism and complements a validation of: A tenant test packet reaches its remote leaf using the intended VXLAN path.
Incorrect Answers
At Lakeshore Municipal Networks, while checking a remote VTEP path, this option proposes: Review tenant service boundaries before accepting EVPN provisioning changes. This option assumes the other problem (An EVPN change accidentally exposes one tenant's broadcast traffic to another) is present. The case instead describes BGP EVPN peers come up over the underlay but a remote VTEP remains unable to carry data traffic, for which the causal issue is Control-plane EVPN session health was mistaken for working VXLAN data-plane transport.
At Lakeshore Municipal Networks, while checking a remote VTEP path, this option proposes: Include endpoint mobility and convergence tests for workload migrations. It tests a different symptom: A relocated virtual machine is reachable from one leaf but stale on another. For the observed case, the relevant distinction is Control-plane EVPN session health was mistaken for working VXLAN data-plane transport, with verification: A tenant test packet reaches its remote leaf using the intended VXLAN path.
At Lakeshore Municipal Networks, while checking a remote VTEP path, this option proposes: Alert on conflicting remote MAC locations and review multi-attachment changes. That choice would be more relevant when this different symptom occurs: A remote server's MAC is learned through two unexpected VTEPs. The present scenario instead points to: Control-plane EVPN session health was mistaken for working VXLAN data-plane transport. The correct resolution has its own verification outcome: A tenant test packet reaches its remote leaf using the intended VXLAN path.