Refer to the exhibit. An engineer is troubleshooting an issue with switch LEAF-SW-11. The engineer observes that several main servers on the VXLAN BGP EVPN Multi-Site network experience 50?0% packet…

Question

Exhibits

Options

• AOn the Nexus switch, run the inner ipv4 dst_ip 172.16.2.200 command against module-1.
• BOn LEAF-SW-11, run the inner ipv4 src_ip 172.16.2.200 command against module-1.
• COn LEAF-SW-11, run the evpn multisite dci-tracking command against interface Eth1/1.
• DOn LEAF-SW-11, enable the multisite ingress-replication command for the L2VNI of VLAN 11.
• EOn the Nexus switch, run the ip access-list permit ip address 172.16.2.200 command.

• A
  15% (7)
• B
  2% (1)
• C
  77% (36)
• E
  6% (3)

Explanation

In a VXLAN BGP EVPN Multi-Site environment: DCI tracking monitors the health of the DCI links. If all DCI-tracking interfaces go down, the leaf can incorrectly keep advertising or learning remote MAC/IP reachability, leading to packet loss and sub- optimal forwarding for servers in that VLAN/L2VNI. For proper operation, each DCI-facing interface must be enabled with evpn multisite dci-tracking so that the Multi-Site border leaf tracks reachability over that link. When using EVPN Multi-Site, BUM (broadcast, unknown unicast, multicast) traffic toward remote sites is typically handled via ingress replication, not multicast groups, for each L2VNI participating in Multi-Site. The configuration snippet shows an L2VNI (vn-segment 16535) still mapped to mcast-group 239.1.1.0, which is inconsistent with Multi-Site recommendations and contributes to packet loss.

No community discussion yet for this question.