[dev] Vxlan route updates not going zfpm

[Jia Chen]

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 at lists.frrouting.org> on behalf of Donald Sharp <sharpd at cumulusnetworks.com>
Date: Monday, February 11, 2019 at 5:26 PM
To: Srinivasulu P <srinivas.pichika at gmail.com>
Cc: FRRouting-Dev <dev at 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 at gmail.com<mailto:srinivas.pichika at 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_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




_______________________________________________
dev mailing list
dev at lists.frrouting.org<mailto:dev at lists.frrouting.org>
https://lists.frrouting.org/listinfo/dev<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.frrouting.org_listinfo_dev&d=DwMFaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=yetdj-aXQpuqTCJGs-93hOpK3740MIRXowfUNLByeos&m=WFEc2yCNjgymSPtaWgHv93-39sLEXnE2zh-1IwycCl8&s=W2TAHxF32GfX-ingXKk1Tq4wW_IU1HseMDRP7DXbjTo&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20190212/615ad50b/attachment-0001.html>