}
fail_mode = cfg_get_string(0, "%s.fail-mode", pfx);
+ if (!fail_mode) {
+ fail_mode = cfg_get_string(0, "mgmt.fail-mode");
+ }
ofproto_set_failure(br->ofproto,
fail_mode && (!strcmp(fail_mode, "standalone") ||
!strcmp(fail_mode, "open")));
Changing the inactivity probe interval also changes the interval
before entering standalone mode (see below).
.IP "\fBbridge.\fIname\fB.controller.fail-mode = \fBstandalone\fR|\fBsecure\fR"
+.IQ "\fBmgmt.fail-mode = standalone\fR|\fBsecure\fR"
When a controller is configured, it is, ordinarily, responsible for
setting up all flows on virtual switch. Thus, if the connection to
the controller fails, no new network connections can be set up. If
the connection to the controller stays down long enough, no packets
can pass through the switch at all.
.IP
-If this option is unset, or if it is set to \fBstandalone\fR (the
-default), \fBvswitchd\fR will take over responsibility for setting up
+The first of these that is set takes effect.
+If the value is \fBstandalone\fR, or if neither of these settings is
+set, \fBvswitchd\fR will take over responsibility for setting up
flows when no message has been received from the controller for three
times the inactivity probe interval (see above). In this mode,
\fBvswitchd\fR causes the datapath to act like an ordinary