Op 07/03/2025 om 19:53 schreef Alex Dietrich:
Hi Julius,
When I deployed this, I did not have to do anything at the instance or
VM startup to produce the MAC+IP routes. I may have had a line or two in
the FRR configuration on the host to make sure it was advertising the
Mac-IP automatically. It may have been ‘advertise-svi-ip’.
Yes, that's it. No need to manually do anything.
advertise-all-vni
advertise-svi-ip
Also make sure you BGP neighbors are enabled under the EVPN family.
Wido
The bigger challenge I had in integrating this with an existing EVPN
VXLAN deployment was handling VNI mapping, which was not so fun 😊
I did end up with a “successful” deployment, so let me know if I can be
of further assistance.
Thanks,
Alex
*From: *Júlíus Þór Bess <jul...@1984.is>
*Date: *Friday, March 7, 2025 at 1:33 PM
*To: *users@cloudstack.apache.org <users@cloudstack.apache.org>
*Cc: *w...@denhollander.io <w...@denhollander.io>
*Subject: *EVPN-VXLAN to the host type-2 MAC+IP routes
EXTERNAL
Hi guys,
I see that some of you are using or have been experimenting with
EVPN-to-the-Host setup and I'd like to know how you are managing the
neighbor table entries to produce the Type-2 MAC+IP advertisements. Are
you using static entries added on VM startup (hook script, maybe?) or what?
Julius Thor
