ovs-controller: Document how to use with management protocol.

diff --git a/utilities/ovs-controller.8.in b/utilities/ovs-controller.8.in
index adef718219fd04ad0af6f81da52db3a17d5c12ec..0501062fc3e1ad091a07d4c729f9aee73d1f475b 100644 (file)
--- 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),