On 2019-03-27 3:19 p.m., Colton Powell wrote:
Anyways, I was thinking the same thing as you: It seems I will have to disable
STP + the default forwarding rules, and then write flows to get ARP, etc.
working as intended. I just wanted to see if there was some other, simpler
solution that
Hi again Ray,
Thanks for the insight. I can definitely see the concern as far as the design
of the network goes, and I definitely plan into looking into
distributed/multiple controller solutions in the future! For now though, its
ok. We are using this network as part of a research project and
On 2019-03-27 1:48 p.m., Colton Powell wrote:
The difficult part for us, however, is actually finding the paths to redirect
on. Because we are currently using STP in our looped topology, OpenDaylight
cannot find all links/paths in the network. Only links on the Spanning Tree are
found
Hi Ray,
Thanks for your response.
We wish to write flows to OpenVSwitches in any given topology to redirect
traffic in the network. In our case, we wish to redirect some traffic between
machines if certain conditions are met (IE: there is sufficient bandwidth
available on the links leading
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
Hi all,
I know that this could be just as easily asked on an OpenDaylight mailing
list, but it specifically involves OpenVSwitch and was hoping someone here
might be able to provide some insight.
In short, I wish to have a OpenVSwitch topology which is looped, and want
to use OpenDaylight to
