If the point here is that the EVPN-VxLAN "L2" information (flooding information, MACs and neighbors) is only installed into the kernel (specifically, via the netlink interface) and does not have an interface into FPM, that is correct. Whoever has an immediate use case (need) for it can take it up. I would definitely recommend not to try to merge data structures etc. as part of the effort to add an FPM interface for the L2 information; that should be taken up separately, if warranted.As far as routes go, irrespective of whether they originated in BGP from an EVPN (type-2 or type-5) route or otherwise, the zebra installation towards the kernel and FPM should be the same. There is some special "sideband" handling for an EVPN-sourced route currently, but it is not for the route itself, and this code will be reduced/eliminated soon.On Tue, Feb 12, 2019 at 8:05 AM Jia Chen <jchen1@paloaltonetworks.com> wrote:_______________________________________________When considering to add VxLAN to Zfpm, I suggest to review the Zfpm design to avoid sending routes information to Zfpm from many different places in the Zebra update code. Is it possible to send/queue a copy to Zfpm right where a route or routes are “send” to kernel via netlink?
Jay
From: dev <dev-bounces@lists.frrouting.org> on behalf of Donald Sharp <sharpd@cumulusnetworks.com>
Date: Monday, February 11, 2019 at 5:26 PM
To: Srinivasulu P <srinivas.pichika@gmail.com>
Cc: FRRouting-Dev <dev@lists.frrouting.org>
Subject: Re: [dev] Vxlan route updates not going zfpm
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.
donald
On Wed, Feb 6, 2019 at 12:34 AM Srinivasulu P <srinivas.pichika@gmail.com> wrote:
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_vtepCould 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
_______________________________________________
dev mailing list
dev@lists.frrouting.org
https://lists.frrouting.org/listinfo/dev
dev mailing list
dev@lists.frrouting.org
https://lists.frrouting.org/listinfo/dev