From c6278d208924bb04c41266ddca276712f95533bc Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Wed, 24 Mar 2010 10:42:17 -0700 Subject: [PATCH] ovs-controller: Document how to use with management protocol. --- utilities/ovs-controller.8.in | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/utilities/ovs-controller.8.in b/utilities/ovs-controller.8.in index adef7182..0501062f 100644 --- a/utilities/ovs-controller.8.in +++ b/utilities/ovs-controller.8.in @@ -90,12 +90,26 @@ This option is only for debugging the Open vSwitch implementation of .so lib/common.man . .SH EXAMPLES -. -.TP -To bind locally to port 6633 (the default) and wait for incoming connections from OpenFlow switches: .PP -.B % ovs\-controller ptcp: -. +To bind locally to port 6633 (the default) and wait for incoming +connections from OpenFlow switches: +.IP +\fB% ovs\-controller ptcp:\fR +.SH "BUGS" +.PP +Configuring a Citrix XenServer to connect to a particular controller +only points the remote OVSDB management connection to that controller. +It does not also configure OpenFlow connections, because the manager +is expected to do that over the management protocol. +\fBovs\-controller\fR is not an Open vSwitch manager and does not know +how to do that. +.PP +As a stopgap workaround, \fBovs\-vsctl\fR can wait for an OVSDB +connection and set the controller, e.g.: +.IP +\fB% ovs\-vsctl \-t0 \-\-db=pssl: \-\-certificate=cert.pem +\-\-ca\-cert=none \-\-private\-key=privkey.pem +\-\-peer\-ca\-cert=cacert.pem set\-controller ssl:\fIip\fR .SH "SEE ALSO" . .BR ovs\-openflowd (8), -- 2.30.2