Step 1: create the following topology

Step 2: set the hostnames on spine, vtep-a and vtep-b. Also check nxos is
set to boot file on next reload
Step 3: configure interfaces on spine
Step 4: configure interfaces on vtep-a
Step 5: configure interfaces on vtep-b
Step 6: configure pc1 and pc2 with their
respective names, ip and verify the config
Step 7: on vteps, check cam table. You will
see that it is empty.

On next step, we will initiate traffic from downstream pc to

populate mac table on vteps
Step 8: ping from pcs

There is no reachability between pcs

Check the cam table on the vteps.

You should be able to find the pc mac
Step 9: time for troubleshooting

Why is the entry not appearing on the vtep

cam table?

Was the Vlan 10 created on the vteps?

Create Vlan 10 and check the cam table
Step 10:check vlan

Thus we know the L2 interface of the vtep is functioning

and

that vtep is able to build its cam table from the local hosts attached to the vtep
Step 11: To build reachability between Vteps, there should be reachability with IGP

We will make use of OSPF to announce reachability between Vteps

Configure ospf on spine

Step 12: configure ospf on vteps – A and B
Step 13: check reachability between Lo0 of vtep-a and Lo0 of Vtep-b

NVE will be configured with the loopback 0 interface only.

Since there is reachability,

the underlay is ready with
ospf.

Next step is to configure

Vxlan
Step 14: enable vxlan on vtep-a and vtep-b

Step 15: create nve interface on vtep-a and vtep-b

We intend to make use of

mb-bgp for the control plane

Therefore, we need to
config BGP between vtep
for control plane
Step 16: configure bgp on vtep-a and vtep-b

Enabled BGP on vteps

Note:
to make use of EVPN family with BGP, following commands
have to be executed on Vtep
Step 17: configure bgp on vtep-a and vtep-b
Step 18: check bgp neighborship between peers

We can see that messages are sent and received across peers
Step 19: we can learn the BGP status between vteps as follows

Therefore, there is BGP reachability between the Vtep Peers so as to allow control plane
communication.
Step 20: To allow vlans over the vxlan overlay, we need to map vlan to VNI.
Enable mapping feature in both vteps

Step 21: create mapping

Step 22: this mapping has to be informed to the EVPN family under BGP

At this point, all configurations have been made. Mp-Bgp

control plane will work if it is a hardware deployment..

Here we cannot accomplish ingress replication, therefore

Mp_Bgp control plane will not work in Eve. You can only
check neighborship

Arp packets from Pc1 cannot reach Pc2 at this point since NLRI
is not advertised yet
Step 23: for Arp to reach from Pc1 to Pc2, we are making use of multicast here

Enable multicast on spine and vteps interfaces

Step 24: enable pim on interfaces
Step 25: prepare Loopback 0 of Spine as RP
And config RP on all vteps
Step 26: add VNI under NVE interfaces

Step 27: verify NVE interfaces

Step 28: ping 10.0.0.2 from pc1 and 10.0.0.1 from pc2. note that there is connectivity

Step 29: check the nve vni. Notice that mode is set to control plane
Step 30: check nve peers. Check the learning type
Step 31: finally, check the evpn updates

Thus, we see that the route-type 2 updates

are used to propagate NLRI information