Question 300
At a Junos EVPN-VXLAN leaf-spine fabric, a Junos specialist investigates this scenario: Two leaf switches dual-home one server but the remote fabric treats their attachments as unrelated segments. The tenant traffic must remain isolated across the overlay. When would the described mechanism be appropriate?
Explanation
Correct Answer
For a Junos EVPN-VXLAN leaf-spine fabric, this mechanism fits the requirement: Use a shared ESI for EVPN multihomed links belonging to one Ethernet segment. The design is appropriate because: A common Ethernet Segment Identifier identifies the shared multihomed Ethernet segment for EVPN coordination. In this scenario, the observed issue is: Two leaf switches dual-home one server but the remote fabric treats their attachments as unrelated segments. The corresponding implementation is: Configure a consistent nonconflicting ESI on the intended dual-homed attachment.
Incorrect Answers
EVPN Ethernet Segment route type 4 supports discovery of PEs connected to the same Ethernet segment. The appropriate correction for the reported case is: Configure a consistent nonconflicting ESI on the intended dual-homed attachment.
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: a common Ethernet Segment Identifier identifies the shared multihomed Ethernet segment for EVPN coordination.
EVPN Ethernet Auto-Discovery route type 1 participates in multihoming reachability and mass-withdraw behavior. Its verification is distinct from the reported condition: Two leaf switches dual-home one server but the remote fabric treats their attachments as unrelated segments. The tenant traffic must remain isolated across the overlay. When would the described mechanism be appropriate.