A data center engineer is troubleshooting intermittent connectivity between two servers in different VLANs. The servers are connected to different leaf switches in a VXLAN EVPN fabric. When checking the fabric, the engineer notices that the NVE interface on one leaf is up/up but the VNI for the server VLAN is not listed in 'show nve vni'. What is the most likely cause?
Trap 1: MTU mismatch on the underlay network
MTU mismatch would cause packet drops but not the absence of VNI from 'show nve vni'.
Trap 2: Anycast gateway is not configured on the leaf
Anycast gateway is used for first-hop redundancy; its absence does not affect VNI visibility on the NVE.
Trap 3: BGP EVPN peers are not established
BGP EVPN peers not established would affect route exchange, but the VNI would still appear in 'show nve vni' if configured.
- A
MTU mismatch on the underlay network
Why wrong: MTU mismatch would cause packet drops but not the absence of VNI from 'show nve vni'.
- B
Anycast gateway is not configured on the leaf
Why wrong: Anycast gateway is used for first-hop redundancy; its absence does not affect VNI visibility on the NVE.
- C
BGP EVPN peers are not established
Why wrong: BGP EVPN peers not established would affect route exchange, but the VNI would still appear in 'show nve vni' if configured.
- D
The VLAN-to-VNI mapping is missing under the VLAN configuration
The VNI must be mapped to a VLAN using 'vn-segment vlan-id' under the VLAN configuration; without it, the VNI does not appear in the NVE interface.