Srinivas -Vxlan updates are typically a mac address and a ip address, which are placed into the linux neighbor table. This is l2 information. At this point in time the zebra rib is meant for l3 routes. At this point in time zebra is used for pass through to the data plane. If you need this information stored in the zebra rib, it would be a different table and more work to consolidate all this information.donaldOn Wed, Feb 6, 2019 at 12:34 AM Srinivasulu P <srinivas.pichika@gmail.com> wrote:_______________________________________________
dev mailing list
dev@lists.frrouting.org
https://lists.frrouting.org/listinfo/dev
Hi,
When I checked latest FRR code all Vxlan updates[type2, type5] are going to Linux kernel. It means VTEP information is not giving to Zfpm from zebra-rib, like zebra_vxlan_remote_vtep_add, zebra_vxlan_remote_vtep_del, zebra_vxlan_remote_macip_add, zebra_vxlan_remote_macip_del.
The code flow
zebra_vxlan_remote_vtep_add
|zvni_vtep_install
|kernel_add_vtep
Could you please let me know whether my understanding is correct.
For this to work whether I can add "route_node" to rib_queue. Will it solve the issue. Could you please provide your inputs.
Thanks,
Srinivas