I think Vmware NSX implementation is far from perfect. The 1:1 bridge restriction is unclear. Vmware talk about loops and there fore dont allow this. Its not serious explanation - software itselt must prevent loops, vmware itself must develop harder. Example. I have 2 ESXi. In ESXi-1 I have NSX manager, edge and controller. In ESXi-2 I have edge and controller. VM-1 in ESXi-1 and VM-2 in ESXi-2. Both VMs in the same logical switch. Vmware says I cant implement 2 edge bridges to connect the same VXLAN to VLAN. In first place yes, it shows VMs in common logical switch can have 2 points to connect to outside world. Instead traffic must flow from VM-2 to ESXi-1 and out through its edge. Or VM-1 through ESXi-2 edge. Why traffic must go through this long way? Why VM-1 cant be go out through ESXi-1 bridge and VM-2 through ESXi-2 bridge? But this is only vmware software developing implementation. There is no any loop when vmware implement priority rules how L2 traffic must flow. Example when NSX software detects VM-1 is local (to ESXi-1 bridge), then ARP broadcast must be blocked in ESXi-2 bridge. And traffic flows out through ESXi-1 bridge. For VM-2 it must block ESXi-1 broadcast and traffic flows out through ESXi-2 bridge. No any loop and no any double outputs. ....So, I still hope in next version Vmware implement this.
↧