[SOLVED] SDN with EVPN controller: Routing loop when using multiple exit nodes

[bitposs]

yeah inserting rules is quite difficult. What I do is to remove the default route-map and replace it with a fully custom one

router bgp 65000

 address-family l2vpn evpn

  no neighbor VTEP route-map MAP_VTEP_IN in

  neighbor VTEP route-map MAP_VTEP_IN_CUSTOM in

 exit-address-family

exit

keep in mind, that you have to fully manually manage that one then.

Good stuff Hedius, I didn't even think of this!

For now, we were in need of another piece of hardware anyways, so built it and are just using it for VM's on one of the networks, hence can use it safely as the exit gateway.

The problem with static changes, we're a company of 30 ppl, so trying to keep everyone on the same page without things getting jumbled is a bit challenging.

 

[ns33]

Hi,

are you trying to ping from 192.168.0.1 (in evpn network) to 192.168.0.10 (in the real network ?)

If, yes, it's cannot work currently.
The only way could be to bridge the exit-node at layer2, but currently, it's possible to do it with multiple nodes, this need a solution to do mlag across proxmox nodes, and they are no opensource solution to do this.

You need different subnets between your evpn networks and your real networks.

@spirit Sorry for bring up an old post but if I did seek to have the same subnets in both evpn network and a real network; is that even possible? Would the physical side switch need to have it's own evpn controller and that would be a peer to the sdn?

 

[shanreich]

Would the physical side switch need to have it's own evpn controller and that would be a peer to the sdn?

Yes, it'd also have to act as a VTEP and encapsulate the traffic accordingly.