]> git.proxmox.com Git - mirror_ovs.git/blame_incremental - vswitchd/ovs-vswitchd.8.in
rconn: Suppress failed connection messages after the backoff maxes out.
[mirror_ovs.git] / vswitchd / ovs-vswitchd.8.in
... / ...
CommitLineData
1.\" -*- nroff -*-
2.de IQ
3. br
4. ns
5. IP "\\$1"
6..
7.TH ovs\-vswitchd 8 "June 2009" "Open vSwitch" "Open vSwitch Manual"
8.ds PN ovs\-vswitchd
9.
10.SH NAME
11ovs\-vswitchd \- Open vSwitch daemon
12.
13.SH SYNOPSIS
14.B ovs\-vswitchd
15\fIdatabase\fR
16.
17.SH DESCRIPTION
18A daemon that manages and controls any number of Open vSwitch switches
19on the local machine.
20.PP
21The mandatory \fIdatabase\fR argument normally takes the form
22\fBunix:\fIfile\fR, where \fIfile\fR is the name of a Unix domain
23socket on which \fBovsdb-server\fR is listening. However, all of the
24following forms are accepted:
25.so ovsdb/remote-active.man
26.so ovsdb/remote-passive.man
27.PP
28\fBovs\-vswitchd\fR retrieves its configuration from \fIdatabase\fR at
29startup. It sets up Open vSwitch datapaths and then operates
30switching across each bridge described in its configuration files. As
31the database changes, \fBovs\-vswitchd\fR automatically updates its
32configuration to match.
33.PP
34Upon receipt of a SIGHUP signal, \fBovs\-vswitchd\fR reopens its log
35file, if one was specified on the command line.
36.PP
37\fBovs\-vswitchd\fR switches may be configured with any of the following
38features:
39.
40.IP \(bu
41L2 switching with MAC learning.
42.
43.IP \(bu
44NIC bonding with automatic fail-over and source MAC-based TX load
45balancing ("SLB").
46.
47.IP \(bu
48802.1Q VLAN support.
49.
50.IP \(bu
51Port mirroring, with optional VLAN tagging.
52.
53.IP \(bu
54NetFlow v5 flow logging.
55.
56.IP \(bu
57sFlow(R) monitoring.
58.
59.IP \(bu
60Connectivity to an external OpenFlow controller, such as NOX.
61.
62.PP
63Only a single instance of \fBovs\-vswitchd\fR is intended to run at a time.
64A single \fBovs\-vswitchd\fR can manage any number of switch instances, up
65to the maximum number of supported Open vSwitch datapaths.
66.PP
67\fBovs\-vswitchd\fR does all the necessary management of Open vSwitch datapaths
68itself. Thus, external tools, such \fBovs\-dpctl\fR(8), are not needed for
69managing datapaths in conjunction with \fBovs\-vswitchd\fR, and their use
70to modify datapaths when \fBovs\-vswitchd\fR is running can interfere with
71its operation. (\fBovs\-dpctl\fR may still be useful for diagnostics.)
72.PP
73An Open vSwitch datapath kernel module must be loaded for \fBovs\-vswitchd\fR
74to be useful. Please refer to the \fBINSTALL.Linux\fR file included in the
75Open vSwitch distribution for instructions on how to build and load
76the Open vSwitch kernel module.
77.PP
78.SH OPTIONS
79.IP "\fB--mlockall\fR"
80Causes \fBovs\-vswitchd\fR to call the \fBmlockall()\fR function, to
81attempt to lock all of its process memory into physical RAM,
82preventing the kernel from paging any of its memory to disk. This
83helps to avoid networking interruptions due to system memory pressure.
84.IP
85Some systems do not support \fBmlockall()\fR at all, and other systems
86only allow privileged users, such as the superuser, to use it.
87\fBovs\-vswitchd\fR emits a log message if \fBmlockall()\fR is
88unavailable or unsuccessful.
89.
90.IP "\fB--fake-proc-net\fR"
91Causes \fBovs\-vswitchd\fR to simulate some files in \fB/proc/net/vlan\fR
92and \fB/proc/net/bonding\fR that some legacy software expects to
93exist. This option should only be used if such legacy software is
94actually in use. It requires the \fBbrcompat_mod.ko\fR kernel module
95to be loaded.
96.IP
97On non-Linux hosts, this option is accepted but has no effect.
98.
99.so lib/daemon.man
100.SS "Public Key Infrastructure Options"
101.so lib/ssl.man
102.so lib/ssl-bootstrap.man
103.so lib/vlog.man
104.so lib/common.man
105.so lib/leak-checker.man
106.
107.SH "RUNTIME MANAGEMENT COMMANDS"
108\fBovs\-appctl\fR(8) can send commands to a running
109\fBovs\-vswitchd\fR process. The currently supported commands are
110described below. The command descriptions assume an understanding of
111how to configure Open vSwitch.
112.SS "GENERAL COMMANDS"
113.IP "\fBexit\fR"
114Causes \fBovs\-vswitchd\fR to gracefully terminate.
115.SS "BRIDGE COMMANDS"
116These commands manage bridges.
117.IP "\fBfdb/show\fR \fIbridge\fR"
118Lists each MAC address/VLAN pair learned by the specified \fIbridge\fR,
119along with the port on which it was learned and the age of the entry,
120in seconds.
121.
122.IP "\fBbridge/dump-flows\fR \fIbridge\fR"
123Lists all flows in \fIbridge\fR, including those normally hidden to
124commands such as \fBovs-ofctl dump-flows\fR. Flows set up by mechanisms
125such as in-band control and fail-open are hidden from the controller
126since it is not allowed to modify or override them.
127.SS "BOND COMMANDS"
128These commands manage bonded ports on an Open vSwitch's bridges. To
129understand some of these commands, it is important to understand a
130detail of the bonding implementation called ``MAC hashing.'' Instead
131of directly assigning Ethernet source addresses to slaves, the bonding
132implementation computes a function that maps an 48-bit Ethernet source
133addresses into an 8-bit value (a ``MAC hash'' value). All of the
134Ethernet addresses that map to a single 8-bit value are then assigned
135to a single slave.
136.IP "\fBbond/list\fR"
137Lists all of the bonds, and their slaves, on each bridge.
138.
139.IP "\fBbond/show\fR \fIport\fR"
140Lists all of the bond-specific information about the given bonded
141\fIport\fR: updelay, downdelay, time until the next rebalance. Also
142lists information about each slave: whether it is enabled or disabled,
143the time to completion of an updelay or downdelay if one is in
144progress, whether it is the active slave, the MAC hashes assigned to
145the slave, and the MAC learning table entries that hash to each MAC.
146.IP "\fBbond/migrate\fR \fIport\fR \fIhash\fR \fIslave\fR"
147Assigns a given MAC hash to a new slave. \fIport\fR specifies the
148bond port, \fIhash\fR either the MAC hash to be migrated (as a decimal
149number between 0 and 255) or an Ethernet address to be hashed, and
150\fIslave\fR the new slave to be assigned.
151.IP
152The reassignment is not permanent: rebalancing or fail-over will
153cause the MAC hash to be shifted to a new slave in the usual
154manner.
155.IP
156A MAC hash cannot be migrated to a disabled slave.
157.IP "\fBbond/set-active-slave\fR \fIport\fR \fIslave\fR"
158Sets \fIslave\fR as the active slave on \fIport\fR. \fIslave\fR must
159currently be enabled.
160.IP
161The setting is not permanent: a new active slave will be selected
162if \fIslave\fR becomes disabled.
163.IP "\fBbond/enable-slave\fR \fIport\fR \fIslave\fR"
164.IQ "\fBbond/disable-slave\fR \fIport\fR \fIslave\fR"
165Enables (or disables) \fIslave\fR on the given bond \fIport\fR, skipping any
166updelay (or downdelay).
167.IP
168This setting is not permanent: it persists only until the carrier
169status of \fIslave\fR changes.
170.IP "\fBbond/hash\fR \fImac\fR"
171Returns the hash value which would be used for \fImac\fR.
172.
173.so lib/vlog-unixctl.man
174.SH "SEE ALSO"
175.BR ovs\-appctl (8),
176.BR ovs\-brcompatd (8),
177.BR ovsdb\-server (1),
178\fBINSTALL.Linux\fR in the Open vSwitch distribution.