You can use ovs-vsctl to control the port on which each OVS bridge listens, or to find out the port on which each OVS bridge listens.
On Wed, Mar 27, 2013 at 09:47:35AM +0800, can. wrote: > I may not make my question clear. > > My problem is that the controller does not support some features of ovs, so > as a circumvent, I tried to get the port number and remotely control the > switch using ovs-ofctl. This trick must parallel the common scenario, say, > the controller doesn't know which switch will connect to it. So the > switch's port number could not be pre-configured and might not be the > default one. In this scenario, is there a way to fetch the port number? > > > 2013/3/27 Ben Pfaff <[email protected]> > > > It's common practice to have all the switches connect outward to the > > controller, in which case there is no problem. > > > > On Wed, Mar 27, 2013 at 09:08:48AM +0800, can. wrote: > > > So what if I can't use the default port number? For example, when more > > than > > > one switches are created, their port numbers are 6634, 6635, etc. How > > could > > > I know that from the controller side? > > > > > > > > > 2013/3/26 Ben Pfaff <[email protected]> > > > > > > > On Tue, Mar 26, 2013 at 03:08:15PM +0800, Can Zhang wrote: > > > > > The command ovs-ofctl could connect to a switch using syntax > > > > > tcp:1.2.3.4:1234, but if I don't know this port number, is there any > > > > > way to fetch it? I mean like when a switch connects to the > > controller, > > > > > the controller knows the switch's dpid. > > > > > > > > If you use the default port number, then there is no need to fetch it. > > > > > > > > > > > > > > > > -- > > > Best regards, > > > Can Zhang > > > > > > -- > Best regards, > Can Zhang _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
