<div dir="ltr">Great! In reading about this feature (thanks to your response), it looks like the controller needs to present a connection id to OVS, which it will only do if it supports the "NXT_SET_CONTROLLER_ID Nicira extension". Anyone by chance know if this extension is something Opendaylight supports? If not, no worries, I can ping their mailing list about it.<br><div><div><div><br>Thanks for the quick reply Ben!<br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 4, 2017 at 11:18 AM, Ben Pfaff <span dir="ltr"><<a href="mailto:blp@ovn.org" target="_blank">blp@ovn.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Jan 04, 2017 at 11:05:07AM -0700, Sterdnot Shaken wrote:<br>
> Can you register one OVS bridge to 2 separate controllers and then, using<br>
> flow's, send some traffic to one controller and send some traffic to the<br>
> other one?<br>
><br>
> something like:<br>
><br>
> ovs-ofctl add-flow br0 priority=10,in_port=1,actions=<wbr>CONTROLLER1:65535<br>
> ovs-ofctl add-flow br0 priority=10,in_port=2,actions=<wbr>CONTROLLER2:65535<br>
<br>
</span>Yes. Use "id=controller-id" on the controller action. See ovs-ofctl(8)<br>
for more information.<br>
</blockquote></div><br></div>