aboutsummaryrefslogtreecommitdiff
path: root/utilities
diff options
context:
space:
mode:
authorJustin Pettit <jpettit@nicira.com>2011-10-12 11:09:47 -0700
committerJustin Pettit <jpettit@nicira.com>2011-10-12 14:58:52 -0700
commitc0de82d9fc7b8b80b806577650c1bb09f051c605 (patch)
tree75ab9cc26e780624ae8af1676697e11d386c4ef1 /utilities
parent070723f9fe70adf623acb519e249babfa7f40804 (diff)
ovs-vsctl: Update man page description of controller support.
ovs-vswitchd supports passive OpenFlow connections, but that was not indicated in the documentation. Add that information as well as a description of Primary (active) and Service (passive) control connections.
Diffstat (limited to 'utilities')
-rw-r--r--utilities/ovs-vsctl.8.in10
1 files changed, 8 insertions, 2 deletions
diff --git a/utilities/ovs-vsctl.8.in b/utilities/ovs-vsctl.8.in
index 3e9192c2..ef862df1 100644
--- a/utilities/ovs-vsctl.8.in
+++ b/utilities/ovs-vsctl.8.in
@@ -324,8 +324,13 @@ output.
.SS "OpenFlow Controller Connectivity"
.
\fBovs\-vswitchd\fR can perform all configured bridging and switching
-locally, or it can be configured to connect a given bridge to one or
-more external OpenFlow controllers, such as NOX.
+locally, or it can be configured to communicate with one or more
+external OpenFlow controllers. The switch is typically configured to
+connect to a primary controller that takes charge of the bridge's flow
+table to implement a network policy. In addition, the switch can be
+configured to listen to connections from service controllers. Service
+controllers are typically used for occasional support and maintenance,
+e.g. with \fBovs\-ofctl\fR.
.
.IP "\fBget\-controller\fR \fIbridge\fR"
Prints the configured controller target.
@@ -339,6 +344,7 @@ use any of the following forms:
.
.RS
.so lib/vconn-active.man
+.so lib/vconn-passive.man
.RE
.
.ST "Controller Failure Settings"