On 2019-03-27 12:12 p.m., Colton Powell wrote:
By default, having a looped topology causes issues with broadcast
packets (such as ARP packets) being looped. I have read the Common
Configuration Problems page, which says to use bonds or STP to solve
this issue.
A looped infrastructure is generally frowned upon. Layer 2 underlay
networks are generally frowned upon.
Could you explain what you are trying to do? There might be alternate
better solutions.
Using a VxLAN or Geneve underlay between OVS instances might be better
(which uses a more robust Layer 3 redundant, load balancing routing
mechanism).
The OVN portion of OVS handles much of the mechanics for you.
However, bonds do not satisfy the requirements I wish to meet, and STP
causes problems with OpenDaylight. When STP is enabled on the
switches, OpenDaylight fails to detect all links in the topology. In
particular, only the links along the spanning tree are detected, and
any links that would otherwise cause a cycle are not detected. This
makes it impossible to gather a complete view of the topology from the
controller, meaning I cannot consider all paths throughout the network
before installing flows onto the switches.
I have found some hacky workarounds for this, but they are definitely
not ideal. Would anyone here have any insight as to how I can
correctly configure my OpenVSwitches in a looped topology without
using bonds or STP? Or is there perhaps another solution that I am not
seeing?
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
