SDN

[Samanta]

Hello, please can someone help me.
I create an evpn controller and vnet network like tutorial, but I don't understand who is responsible to learn Mac address (evpn controller or vnet)

 

[spirit]

the mac address && ip address are learning from the controller (frr daemon) with listenting to vnet (linux bridge) mac bridge fdb table && arp table.

then the controller is exchancing this mac && ip through other controllers (peers) with bgp protocol

 

[Samanta]

Thank you for answering.
so if the learning of mac address is at the evpn controller, the vxlan are created between two frr routing and not between the VNET?
my last question is: do I have to create another zone to simulate learning between two controllers?

 

[spirit]

Thank you for answering.
so if the learning of mac address is at the evpn controller, the vxlan are created between two frr routing and not between the VNET?

the vxlan tunnel are created between each vnets in full mesh. (this is the forward plane)
the frr routing is exchanging the mac address/ip, and push them in each vnet locally. (this is the control plane)


this is the main difference with classic vxlan, where the mac learning (the control plane), is doing with flooding traffic to learn mac.
and this is why you can filter arp with evpn.

my last question is: do I have to create another zone to simulate learning between two controllers?

no, zone is to separate traffic between vnets (with evpn, it's a different vrf between each zone)
as the are routable, you can't communicate between 2 vnets in 2 differents zones
another usage, is if you want to use same private subnet && ips, in 2 differents zones for example.

so, you need 1 zone. and in the controller config, you add all ips of all controllers (all the servers where vnets are located).

 

[Samanta]

the vxlan tunnel are created between each vnets in full mesh. (this is the forward plane)
the frr routing is exchanging the mac address/ip, and push them in each vnet locally. (this is the control plane)


this is the main difference with classic vxlan, where the mac learning (the control plane), is doing with flooding traffic to learn mac.
and this is why you can filter arp with evpn.



no, zone is to separate traffic between vnets (with evpn, it's a different vrf between each zone)
as the are routable, you can't communicate between 2 vnets in 2 differents zones
another usage, is if you want to use same private subnet && ips, in 2 differents zones for example.

so, you need 1 zone. and in the controller config, you add all ips of all controllers (all the servers where vnets are located).

Thank your, it was so helpful.