Quick add-on to Justin's answer, in case it wasn't implied: ovs-vsctl *set-controller* <bridge> [ssl|tcp]:<flowvisor_ip>
-Reid 2011/1/18 Justin Pettit <jpet...@nicira.com> > If you have all the pieces installed, you can just configure it as you > would any OpenFlow controller in OVS: > > ovs-vsctl <bridge> ssl:<flowvisor_ip> > > or, if it's unencrypted: > > ovs-vsctl <bridge> tcp:<flowvisor_ip> > > The section "OpenFlow Controller Connectivity" in the ovs-vsctl man page > should have all the information you need. > > --Justin > > > On Jan 18, 2011, at 11:53 PM, Yue ZHANG wrote: > > > Dear staff, > > > > > > I plan to use flowvisor to manage more than one controller(NOX), working > together with some OVS instances. But I have difficulty in the > configuration, because there is few docs about it. > > > > So I just need your help to tell me how to connect a OVS to the > flowvisor? > > > > By my understanding, if the FV is listening port 6633, then the OVS > should connect to this port, someone use 'secchan' to do this, but I could > not find this command in my openvswitch-1.1.0pre2 deployment. > > > > Thanks. > > > > > > Yue ZHANG > > cassidy...@gmail.com > > 2011-01-19 > > _______________________________________________ > > discuss mailing list > > discuss@openvswitch.org > > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org > > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
