This is related to the EVPN-VXLAN setup in the SPINE/LEAF architecture. If we have the IRB/L3 gateway for the VLANs on the spines, we configure the Virtual Gateway Address for the IRB along with the Physical IP address for the IRB.
The issue is seen even with the parameter 'virtual-gateway-accept-data' configured:
'virtual-gateway-accept-data'
#set interfaces irb unit 100 virtual-gateway-accept-data
root@SPN01> ping 192.168.10.10 source 192.168.10.1 routing-instance TEST Apr 25 12:19:00 PING 192.168.10.10 (192.168.10.10): 56 data bytes ^C --- 192.168.10.10 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss
In an VXLAN-EVPN environment, it is mandatory to have the loopback interface configured for each routing-instance for the layer 3 connectivity to function as expected.
Note : When setting up a routing instance for EVPN-VXLAN, you must include a loopback interface. You must also specify an IP address for the interface using set interfaces lo0 unit logical-unit-number family inet address ip-address / prefix . If you inadvertently omit the loopback interface and associated IP address, EVPN control packets cannot be processed.
set interfaces lo0 unit logical-unit-number family inet address ip-address / prefix
On the spine, configure the loopback interface under the routing-instance as follows:
# set interfaces irb unit 100 virtual-gateway-accept-data # set interface lo0 unit 1 family inet # set routing-instance TEST interface lo0.1 # commit
For more information, refer to Example: Configuring IRB Interfaces in an EVPN-VXLAN Environment to Provide Layer 3 Connectivity for Hosts in a Data Center .