Symptom/Cause | Solution |
---|---|
“map access port” for a physical port is not successful | Ensure that the access port that you are trying to map to a vxlan vnid is part of a bridge. |
“map access port-vlan” for an interface is not successful | Ensure that the access port that you are trying to map to a vxlan vnid is part of a bridge. Ensure that the vlan which you are trying to map is configured on the access port. |
“map network tunnel” is not successful for unicast tunnel | Verify that the physical interface used for tunnel is up and running. Ensure that the ip route is present on VTEP. |
Can we have tunnel source ip as loopback interface ip? | Yes, you can use loopback IP as tunnel source IP. |
Known unicast traffic not flowing from one end to another end after configuring static entries | Ensure that all the interfaces are up and running. Ensure that source mac address is learnt on source VTEP on each VTEP using "show bridge". Ensure that you can ping tunnel destination IP, ie. you have a route to reach the destination VTEP. Ensure that the mac address configured in static entry is that of correct destination host. |
BUM traffic is not flowing | Ensure that multicast tunnel is configured on the VTEPs. Unicast tunnel does not support BUM traffic, only known unicast traffic. |
Having different VLAN's on each access side isnt working. | For input VTEP, traffic is allowed based on the vlan configured on the access port but on destination VTEP after decapsulation, vlan check is not happening. |
Multicast tunnel installation is unsuccessful. | Verify that the physical interface used for tunnel is up and running. Ensure that “tunnel add interface <if-name>” is configured in the multicast tunnel. |
Multicast traffic not flowing from one end to another end after configuring VTEPs successfully. | Ensure that all the interfaces are up and running. Ensure that the intermediate routers are supporting multicast. Ensure that the VTEPs have joined the multicast group correctly, ie the tunnel destination ip(multicast ip) is correct on the participating VTEPs. Ensure that source mac address is learnt on source VTEP on each VTEP using "show bridge". |
Symptom/Cause | Solution |
---|---|
vxlan host-reachability-protocol evpn-bgp vrfblue is not successful | Make sure that the vrf which you are trying to map is configured. |
Can we have vtep-ip-global as loopback ip | Yes.This ip is the source ip of the tunnel. |
sh bgp l2vpn evpn does not show the multicast entries | Make sure that your route is reachable using any static/dynamic (isis/ospf...) protocol. Also make sure that bgp neighborship is established. |
Ping is not working for a particular vnid | Ensure that all the interfaces are up and running Ensure that source mac address is learnt on source VTEP on each VTEP using show bridge. Ensure that you can ping tunnel destination IP, ie. you have a route to reach the destination VTEP. Ensure that bgp neighborship is established, have proper router-id's configured Ensure that you have imported/exported the route correctly using route-target.Ensure unique RD in all VRFs Also ensure that on all the VTEPs, access port is mapped to respective/relevant VNID |