I have seen config examples where 2 leaf switches are put into a mlag and then the vxlan vxrd effectively runs redundantly between them. Can this redundancy be achieved without having the leaf switches in mlag, as I would rather keep the L2 part of the network as simple as possible?
We will effectively have 2 racks (for now) with 2 leaf switches in each, L3 up to spines. Each rack will have a number of VMware ESX hosts in them connected to each leaf switch via standard port group balancing.
We also have a L2 external network/subnet for internet access, which we need to present to all ESX servers for virtual firewalls. My old school networking approach would have been to split the external range into smaller subnets and with extra vrrp's and VRF's route them across the L3 fabric. However with vxlan I'm seeing an opurtunity to do something more clever and allow more granular assinging of VM's to a rack.
I don't really have any need for mlag and would probably prefer to avoid it as "clever" L2 stuff tends to scare me. I would use just a simple L2 bonded link between leaf switches for the internal rack L2 vlan traffic. Is there anyway to run vxlan in this configuration so that if one leaf switch is unavailable, that vxlan will still be working and without causing loops?