Hi Art,
Thanks for your reply and the shared command, I tried to use couple of MX240 to reproduce the lab, observed that on MX routers also do not have this :vxlan.inet.0 table generated. However, MAC address learning and EVPN routing forwarding are working fine, hosts can ping to each other.
This is quite confuse, do not so clear if the route protocol next hop address is not in this :vxlan.inet.0 table, how EVPN route forwarding is working. Do not find the example CLI output related to this table from Internet when use EX or MX to run EVPN VXLAN.
Also tried the the hidden command you shared, unfortunately not changes on vEX after rebooting. Anyway, it does not prevent the future lab practice.
Regards
Marco
-------------------------------------------
Original Message:
Sent: 08-13-2025 18:23
From: Art Stine
Subject: :vxlan.inet.0 routing table on vswitch
See if adding this config makes it work:
set chassis evpn-vxlan-default-switch-support
The EX9000 series isn't a QFX so it may not have all the switching capabilities that vQFX had.
Art
------------------------------
Art Stine
Virtualization/Kernel team
Original Message:
Sent: 08-11-2025 15:55
From: marco.xu
Subject: :vxlan.inet.0 routing table on vswitch
Hi Community,
I am planning to use the vswitch/vEX (version 24.4R1.9) to practice the EVPN MAC-VRF lab due to the vQFX version is lower than the requiremened version to support this function. It is strange there is no :vxlan.inet.0 table generated on any leaf, however, vxlan vtep interfaces are created and can see vxlan tunnels to remote vteps.
Is there special command required on vEX/juniper-vswitch to make it working?
Regards
Marco
-------------------------------------------