Question 40
At a multihomed data center using redundant Ethernet segments, a Junos specialist investigates this scenario: Two VXLAN leaf switches have IP reachability but do not exchange learned remote MAC reachability. The design must avoid forwarding loops during failover. What risk must the implementation avoid?
Explanation
Correct Answer
For a multihomed data center using redundant Ethernet segments, the relevant safeguard is: Verify platform and release-specific EVPN support rather than enabling every address family indiscriminately. It matters while implementing: Enable a supported EVPN BGP signaling relationship with the intended route targets and instances. The fault involves: EVPN uses a BGP signaling address family to distribute Ethernet reachability and related control-plane information. The required acceptance result remains: show route table BGP.evpn.0 or equivalent EVPN table contains valid remote routes.
Incorrect Answers
EVPN MAC mobility information can signal updated reachability and help distinguish a newer MAC location. The appropriate correction for the reported case is: Verify platform and release-specific EVPN support rather than enabling every address family indiscriminately.
EVPN route type 5 conveys IP prefix reachability and can support routed overlay designs. Fixing that different mechanism would not address the current root cause: EVPN uses a BGP signaling address family to distribute Ethernet reachability and related control-plane information.
VXLAN uses a 24-bit VNI to identify a logical overlay segment associated with local bridging context. Its verification is distinct from the reported condition: Two VXLAN leaf switches have IP reachability but do not exchange learned remote MAC reachability. The design must avoid forwarding loops during failover.