Hi everyone,
I noticed on some platforms table :vxlan.inet.0 is not even created and on some it does:
Example: ( where vxlan.inet.0 gets created)
QFX 5110, running JUNOS 21.4R3
Model: vqfx-10000
Examples: ( where vxlan.inet.0 does not get created)
VRR JUNOS 21.3R1.9
But does not require explicit configuration to resolve bgp.evpn.0 's next hop in inet.0 when reflecting EVPN routes. It is doing it automatically.
Model: ex9214
Junos: 23.2R1.14
But does not require explicit configuration to resolve bgp.evpn.0 's next hop in inet.0 when reflecting EVPN routes. It is doing it automatically.
Is this some new JUNOS feature where EVPN next protocol hop is being resolved using inet.0 table?
Hopefully someone from Juniper can speak on it?
Much appreciated!!
------------------------------
Be kind!!
------------------------------