The ADCampus Spine device cannot learn Leaf's arp entries

Topology：

The EVPN neighbor relationship is established between the spine and the leaf, but the addresses of vsi4094 on the spine and the leaf cannot access each other.

First check that the BGP EVPN neighbor relationship has been established normally.

The vxlan tunnels on Spine and Leaf are also established normally

However, the Spine cannot learn the arp entries of the VSI4094 interface 130.1.0.3 on the Leaf.

Looking at the routing table, Also can't find the detailed route to Leaf VSI4094 interface.

Check the EVPN routing messages on Spine and Leaf, and find that there is no detailed route advertised for 130.1.0.3

It can be shown that Leaf itself has not released the arp entry of 130.1.0.3.

Check the vsi4094 interface and the configuration under vsi vxlan4094 and find that arp-advertising disable is configured under vsi vxlan4094.

try removing this command，”arp-advertising disable“.Recheck BGP EVPN routing messages on Leaf.

We can see that Leaf has published this type 2 host route,Check the BGP EVPN message on the spine, and the result has also received this type 2 host route.

Looking at the routing table, detailed routes to 130.1.0.3 have been generated.

Ping test passed on spine.

Removing this command，"arp-advertising disable".