vxlan 10.255.2.1:1 Vl10 Vl13 Vl99 VTEP-2# show ip vrf detail vxlan vxlan is the name of the VRF VRF vxlan (VRF Id = 2); default RD 10.255.2.1:1; default VPNID set> New CLI format, supports multiple address-families Flags: 0x180C Interfaces: Vl10 Vl13 Vl99 Address family ipv4 unicast (Table ID = 0x2): Table 2 maps to VRF vxlan, also found in BPG VPNv4 table Flags:
0x0 No Export VPN route-target communities No Import VPN route-target communities Export VPN route-target stitching communities import each other's targets (same as Layer 3 VPN) RT:10.255.2.1:1 Import VPN route-target stitching communities RT:10.255.1.1:1 No import route-map No global export route-map No export route-map VRF label distribution protocol: not configured VRF label allocation mode: per-prefix VRF is using stitching route-targets. VTEPs must Verify that Both Layer 2 and Layer 3 VNIs are provisioned in the VRF and are UP The following examples show how to verify that both Layer 2 and Layer 3 VNIs are provisioned in the VRF and are up:
VTEP-1# show run | section vlan config vlan configuration 99 VNI is a member of VRF vxlan, not of EVPN instance member vni99999 VTEP-1# show run interface vlan 99 interface Vlan99 description connected to L3_VNI_99999 vrf forwarding vxlan ip unnumbered Loopback999 VTEP-1# show run interface nve 1 no ip address source-interface Loopback999 host-reachability protocol bgp member vni 99999 vrf vxlan VNI tied to the VRF under NVE interface member vni 12012 mcast-group 239.12.12.12 VNI tied to the NVE VTEP-1# show run | section l2vpn l2vpn evpn instance 12 vlan-based encapsulation vxlan route-target export 12:1 Remote VTEP is NOT importing this route target, as it does not have the VLAN or VNI on its end route-target import 12:1 no auto-route-target VTEP-1# show run | section vlan config Troubleshooting BGP EVPN VXLAN Verifying the Provisioning of an EVPN VXLAN Layer 3 Overlay Network Troubleshooting BGP EVPN VXLAN 21