[dev] Vxlan route updates not going zfpm

[Srinivasulu P]

Hi Donald,

Thanks for the response. In EVPN case for Type-2, locally learned mac
address and ip address will be send to other VTEP device. In this case,
Zebra needs to update BGP to prepare Type-2 routes and send it to remote
device.

Could you please suggest, how zebra can receive  these locally learned
mac/ip address from the ASIC. It is via rt_netlink socket or any other
mechanism to achieve this.

Thanks and regards
Srinivas


On Tue, Feb 12, 2019 at 6:55 AM Donald Sharp <sharpd at cumulusnetworks.com>
wrote:

> 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>
> 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
>> https://lists.frrouting.org/listinfo/dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20190223/4d4b8d11/attachment.html>