Question 450
At Summitline Energy Services, while troubleshooting an EVPN MAC/IP route, the data center fabric team observes: A MAC is present in local learning but absent from another leaf's EVPN state. What test result proves the affected fabric function now works?
Explanation
Correct Answer
At Summitline Energy Services, while troubleshooting an EVPN MAC/IP route, the remote leaf receives the expected EVPN MAC/IP route and reaches the endpoint. This is linked directly to the observed symptom (A MAC is present in local learning but absent from another leaf's EVPN state) and cannot be replaced by an unrelated healthy dashboard.
Incorrect Answers
At Summitline Energy Services, while troubleshooting an EVPN MAC/IP route, this option proposes: Remote VTEP endpoints can be reached from the selected source loopbacks. This is a valid category of fabric maintenance for another scenario (A VXLAN VTEP cannot reach a remote tenant endpoint even though MAC-VRFs exist), not the targeted action for Summitline Energy Services. The distinction is the actual cause: The originating leaf is not exporting the relevant EVPN MAC/IP route.
At Summitline Energy Services, while troubleshooting an EVPN MAC/IP route, this option proposes: A controlled routed flow succeeds using the service model chosen for the fabric. Although related to EVPN, VXLAN, MAC-VRF and IP-VRF overlays, the proposed change fits another mechanism: The model expects direct destination bridge reachability that is not provisioned for that routing approach. The evidence in the current case requires a different result: The remote leaf receives the expected EVPN MAC/IP route and reaches the endpoint.
At Summitline Energy Services, while troubleshooting an EVPN MAC/IP route, this option proposes: The host sees the intended gateway and unrelated tenant gateways are unchanged. Using that approach would investigate A tenant interface uses the wrong virtual-router gateway address after a new subnet is created instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The originating leaf is not exporting the relevant EVPN MAC/IP route.