Question 130
After replacing a leaf, a customer LAG is wired to the new pair but the second leaf advertises an unrelated Ethernet segment identifier, weakening the expected multihoming behavior. 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. Validate ESI and link-aggregation consistency whenever replacing a multihoming peer. That is important in this case because a shared Ethernet segment identity is important for supported EVPN multihoming coordination of the same access segment. The scenario was: After replacing a leaf, a customer LAG is wired to the new pair but the second leaf advertises an unrelated Ethernet segment identifier, weakening the expected multihoming behavior.
Incorrect Answers
The alternative applies to another Juniper security situation: An operator studies the two uplinks of a dual-attached rack and expects both leafs to forward every broadcast copy without considering designated-forwarder responsibilities. That situation concerns eVPN designated-forwarder selection controls eligible BUM forwarding toward a shared Ethernet segment and helps avoid duplicate delivery. Its key condition is a shared Ethernet segment identity is important for supported EVPN multihoming coordination of the same access segment.
Check anycast gateway consistency whenever a tenant virtual network is extended to another rack. That concerns anycast default gateway identity across leafs, while the issue here is ethernet segment identifier for multihomed access. Review the supported ESI and attachment configuration on both peers, align its identity and check the resulting EVPN multihoming routes. Specifically for the prevention question, the case to validate is: After replacing a leaf, a customer LAG is wired to the new pair but the second leaf advertises an unrelated Ethernet segment identifier, weakening the expected multihoming behavior.
A VXLAN VNI distinguishes the logical overlay segment, while local VLAN numbers and attachment mapping can be implementation-specific. For this issue, review the supported ESI and attachment configuration on both peers, align its identity and check the resulting EVPN multihoming routes.