1 <?xml version="1.0" encoding="utf-8"?>
2 <database title="Open vSwitch Configuration Database">
4 A database with this schema holds the configuration for one Open
5 vSwitch daemon. The top-level configuration for the daemon is the
6 <ref table="Open_vSwitch"/> table, which must have exactly one
7 record. Records in other tables are significant only when they
8 can be reached directly or indirectly from the <ref
9 table="Open_vSwitch"/> table. Records that are not reachable from
10 the <ref table="Open_vSwitch"/> table are automatically deleted
11 from the database, except for records in a few distinguished
12 ``root set'' tables noted below.
15 <table name="Open_vSwitch" title="Open vSwitch configuration.">
16 Configuration for an Open vSwitch daemon. There must be exactly
17 one record in the <ref table="Open_vSwitch"/> table.
19 <group title="Configuration">
20 <column name="bridges">
21 Set of bridges managed by the daemon.
25 SSL used globally by the daemon.
28 <column name="external_ids">
29 Key-value pairs for use by external frameworks that integrate
30 with Open vSwitch, rather than by Open vSwitch itself. System
31 integrators should either use the Open vSwitch development
32 mailing list to coordinate on common key-value definitions, or
33 choose key names that are likely to be unique. The currently
34 defined common key-value pairs are:
36 <dt><code>system-id</code></dt>
37 <dd>A unique identifier for the Open vSwitch's physical host.
38 The form of the identifier depends on the type of the host.
39 On a Citrix XenServer, this will likely be the same as
40 <code>xs-system-uuid</code>.</dd>
41 <dt><code>xs-system-uuid</code></dt>
42 <dd>The Citrix XenServer universally unique identifier for the
43 physical host as displayed by <code>xe host-list</code>.</dd>
48 <group title="Status">
49 <column name="next_cfg">
50 Sequence number for client to increment. When a client modifies
51 any part of the database configuration and wishes to wait for
52 Open vSwitch to finish applying the changes, it may increment
56 <column name="cur_cfg">
57 Sequence number that Open vSwitch sets to the current value of
58 <ref column="next_cfg"/> after it finishes applying a set of
59 configuration changes.
62 <column name="capabilities">
63 Describes functionality supported by the hardware and software platform
64 on which this Open vSwitch is based. Clients should not modify this
65 column. See the <ref table="Capability"/> description for defined
66 capability categories and the meaning of associated
67 <ref table="Capability"/> records.
70 <column name="statistics">
72 Key-value pairs that report statistics about a system running an Open
73 vSwitch. These are updated periodically (currently, every 5
74 seconds). Key-value pairs that cannot be determined or that do not
75 apply to a platform are omitted.
79 <dt><code>cpu</code></dt>
82 Number of CPU processors, threads, or cores currently online and
83 available to the operating system on which Open vSwitch is
84 running, as an integer. This may be less than the number
85 installed, if some are not online or if they are not available to
89 Open vSwitch userspace processes are not multithreaded, but the
90 Linux kernel-based datapath is.
94 <dt><code>load_average</code></dt>
97 A comma-separated list of three floating-point numbers,
98 representing the system load average over the last 1, 5, and 15
99 minutes, respectively.
103 <dt><code>memory</code></dt>
106 A comma-separated list of integers, each of which represents a
107 quantity of memory in kilobytes that describes the operating
108 system on which Open vSwitch is running. In respective order,
113 <li>Total amount of RAM allocated to the OS.</li>
114 <li>RAM allocated to the OS that is in use.</li>
115 <li>RAM that can be flushed out to disk or otherwise discarded
116 if that space is needed for another purpose. This number is
117 necessarily less than or equal to the previous value.</li>
118 <li>Total disk space allocated for swap.</li>
119 <li>Swap space currently in use.</li>
123 On Linux, all five values can be determined and are included. On
124 other operating systems, only the first two values can be
125 determined, so the list will only have two values.
129 <dt><code>process_</code><var>name</var></dt>
132 One such key-value pair will exist for each running Open vSwitch
133 daemon process, with <var>name</var> replaced by the daemon's
134 name (e.g. <code>process_ovs-vswitchd</code>). The value is a
135 comma-separated list of integers. The integers represent the
136 following, with memory measured in kilobytes and durations in
141 <li>The process's virtual memory size.</li>
142 <li>The process's resident set size.</li>
143 <li>The amount of user and system CPU time consumed by the
145 <li>The number of times that the process has crashed and been
146 automatically restarted by the monitor.</li>
147 <li>The duration since the process was started.</li>
148 <li>The duration for which the process has been running.</li>
152 The interpretation of some of these values depends on whether the
153 process was started with the <option>--monitor</option>. If it
154 was not, then the crash count will always be 0 and the two
155 durations will always be the same. If <option>--monitor</option>
156 was given, then the crash count may be positive; if it is, the
157 latter duration is the amount of time since the most recent crash
162 There will be one key-value pair for each file in Open vSwitch's
163 ``run directory'' (usually <code>/var/run/openvswitch</code>)
164 whose name ends in <code>.pid</code>, whose contents are a
165 process ID, and which is locked by a running process. The
166 <var>name</var> is taken from the pidfile's name.
170 Currently Open vSwitch is only able to obtain all of the above
171 detail on Linux systems. On other systems, the same key-value
172 pairs will be present but the values will always be the empty
177 <dt><code>file_systems</code></dt>
180 A space-separated list of information on local, writable file
181 systems. Each item in the list describes one file system and
182 consists in turn of a comma-separated list of the following:
186 <li>Mount point, e.g. <code>/</code> or <code>/var/log</code>.
187 Any spaces or commas in the mount point are replaced by
189 <li>Total size, in kilobytes, as an integer.</li>
190 <li>Amount of storage in use, in kilobytes, as an integer.</li>
194 This key-value pair is omitted if there are no local, writable
195 file systems or if Open vSwitch cannot obtain the needed
203 <group title="Version Reporting">
205 These columns report the types and versions of the hardware and
206 software running Open vSwitch. We recommend in general that software
207 should test whether specific features are supported instead of relying
208 on version number checks. These values are primarily intended for
209 reporting to human administrators.
212 <column name="ovs_version">
213 The Open vSwitch version number, e.g. <code>1.1.0</code>.
214 If Open vSwitch was configured with a build number, then it is
215 also included, e.g. <code>1.1.0+build6579</code>.
218 <column name="db_version">
220 The database schema version number in the form
221 <code><var>major</var>.<var>minor</var>.<var>tweak</var></code>,
222 e.g. <code>1.2.3</code>. Whenever the database schema is changed in
223 a non-backward compatible way (e.g. deleting a column or a table),
224 <var>major</var> is incremented. When the database schema is changed
225 in a backward compatible way (e.g. adding a new column),
226 <var>minor</var> is incremented. When the database schema is changed
227 cosmetically (e.g. reindenting its syntax), <var>tweak</var> is
232 The schema version is part of the database schema, so it can also be
233 retrieved by fetching the schema using the Open vSwitch database
238 <column name="system_type">
240 An identifier for the type of system on top of which Open vSwitch
241 runs, e.g. <code>XenServer</code> or <code>KVM</code>.
244 System integrators are responsible for choosing and setting an
245 appropriate value for this column.
249 <column name="system_version">
251 The version of the system identified by <ref column="system_type"/>,
252 e.g. <code>5.6.100-39265p</code> on XenServer 5.6.100 build 39265.
255 System integrators are responsible for choosing and setting an
256 appropriate value for this column.
262 <group title="Database Configuration">
264 These columns primarily configure the Open vSwitch database
265 (<code>ovsdb-server</code>), not the Open vSwitch switch
266 (<code>ovs-vswitchd</code>). The OVSDB database also uses the <ref
267 column="ssl"/> settings.
271 The Open vSwitch switch does read the database configuration to
272 determine remote IP addresses to which in-band control should apply.
275 <column name="manager_options">
276 Database clients to which the Open vSwitch database server should
277 connect or to which it should listen, along with options for how these
278 connection should be configured. See the <ref table="Manager"/> table
279 for more information.
284 <table name="Bridge">
286 Configuration for a bridge within an
287 <ref table="Open_vSwitch"/>.
290 A <ref table="Bridge"/> record represents an Ethernet switch with one or
291 more ``ports,'' which are the <ref table="Port"/> records pointed to by
292 the <ref table="Bridge"/>'s <ref column="ports"/> column.
295 <group title="Core Features">
297 Bridge identifier. Should be alphanumeric and no more than about 8
298 bytes long. Must be unique among the names of ports, interfaces, and
302 <column name="ports">
303 Ports included in the bridge.
306 <column name="mirrors">
307 Port mirroring configuration.
310 <column name="netflow">
311 NetFlow configuration.
314 <column name="sflow">
318 <column name="flood_vlans">
319 VLAN IDs of VLANs on which MAC address learning should be disabled, so
320 that packets are flooded instead of being sent to specific ports that
321 are believed to contain packets' destination MACs. This should
322 ordinarily be used to disable MAC learning on VLANs used for mirroring
323 (RSPAN VLANs). It may also be useful for debugging.
327 <group title="OpenFlow Configuration">
328 <column name="controller">
329 OpenFlow controller set. If unset, then no OpenFlow controllers
333 <column name="fail_mode">
334 <p>When a controller is configured, it is, ordinarily, responsible
335 for setting up all flows on the switch. Thus, if the connection to
336 the controller fails, no new network connections can be set up.
337 If the connection to the controller stays down long enough,
338 no packets can pass through the switch at all. This setting
339 determines the switch's response to such a situation. It may be set
340 to one of the following:
342 <dt><code>standalone</code></dt>
343 <dd>If no message is received from the controller for three
344 times the inactivity probe interval
345 (see <ref column="inactivity_probe"/>), then Open vSwitch
346 will take over responsibility for setting up flows. In
347 this mode, Open vSwitch causes the bridge to act like an
348 ordinary MAC-learning switch. Open vSwitch will continue
349 to retry connecting to the controller in the background
350 and, when the connection succeeds, it will discontinue its
351 standalone behavior.</dd>
352 <dt><code>secure</code></dt>
353 <dd>Open vSwitch will not set up flows on its own when the
354 controller connection fails or when no controllers are
355 defined. The bridge will continue to retry connecting to
356 any defined controllers forever.</dd>
359 <p>If this value is unset, the default is implementation-specific.</p>
360 <p>When more than one controller is configured,
361 <ref column="fail_mode"/> is considered only when none of the
362 configured controllers can be contacted.</p>
365 <column name="datapath_id">
366 Reports the OpenFlow datapath ID in use. Exactly 16 hex
367 digits. (Setting this column will have no useful effect. Set
368 <ref column="other_config"/>:<code>other-config</code>
373 <group title="Other Features">
374 <column name="datapath_type">
375 Name of datapath provider. The kernel datapath has
376 type <code>system</code>. The userspace datapath has
377 type <code>netdev</code>.
380 <column name="external_ids">
381 Key-value pairs for use by external frameworks that integrate
382 with Open vSwitch, rather than by Open vSwitch itself. System
383 integrators should either use the Open vSwitch development
384 mailing list to coordinate on common key-value definitions, or
385 choose key names that are likely to be unique. The currently
386 defined key-value pairs are:
388 <dt><code>bridge-id</code></dt>
389 <dd>A unique identifier of the bridge. On Citrix XenServer this
390 will commonly be the same as <code>xs-network-uuids</code>.</dd>
391 <dt><code>xs-network-uuids</code></dt>
392 <dd>Semicolon-delimited set of universally unique identifier(s) for
393 the network with which this bridge is associated on a Citrix
394 XenServer host. The network identifiers are RFC 4122 UUIDs as
395 displayed by, e.g., <code>xe network-list</code>.</dd>
399 <column name="other_config">
400 Key-value pairs for configuring rarely used bridge
401 features. The currently defined key-value pairs are:
403 <dt><code>datapath-id</code></dt>
405 digits to set the OpenFlow datapath ID to a specific
406 value. May not be all-zero.</dd>
407 <dt><code>disable-in-band</code></dt>
408 <dd>If set to <code>true</code>, disable in-band control on
409 the bridge regardless of controller and manager settings.</dd>
410 <dt><code>hwaddr</code></dt>
411 <dd>An Ethernet address in the form
412 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>
413 to set the hardware address of the local port and influence the
415 <dt><code>in-band-queue</code></dt>
417 A queue ID as a nonnegative integer. This sets the OpenFlow queue
418 ID that will be used by flows set up by in-band control on this
419 bridge. If unset, or if the port used by an in-band control flow
420 does not have QoS configured, or if the port does not have a queue
421 with the specified ID, the default queue is used instead.
428 <table name="Port" table="Port or bond configuration.">
429 <p>A port within a <ref table="Bridge"/>.</p>
430 <p>Most commonly, a port has exactly one ``interface,'' pointed to by its
431 <ref column="interfaces"/> column. Such a port logically
432 corresponds to a port on a physical Ethernet switch. A port
433 with more than one interface is a ``bonded port'' (see
434 <ref group="Bonding Configuration"/>).</p>
435 <p>Some properties that one might think as belonging to a port are actually
436 part of the port's <ref table="Interface"/> members.</p>
439 Port name. Should be alphanumeric and no more than about 8
440 bytes long. May be the same as the interface name, for
441 non-bonded ports. Must otherwise be unique among the names of
442 ports, interfaces, and bridges on a host.
445 <column name="interfaces">
446 The port's interfaces. If there is more than one, this is a
450 <group title="VLAN Configuration">
451 <p>A bridge port must be configured for VLANs in one of two
452 mutually exclusive ways:
454 <li>A ``trunk port'' has an empty value for <ref
455 column="tag"/>. Its <ref column="trunks"/> value may be
456 empty or non-empty.</li>
457 <li>An ``implicitly tagged VLAN port'' or ``access port''
458 has an nonempty value for <ref column="tag"/>. Its
459 <ref column="trunks"/> value must be empty.</li>
461 If <ref column="trunks"/> and <ref column="tag"/> are both
462 nonempty, the configuration is ill-formed.
467 If this is an access port (see above), the port's implicitly
468 tagged VLAN. Must be empty if this is a trunk port.
471 Frames arriving on trunk ports will be forwarded to this
472 port only if they are tagged with the given VLAN (or, if
473 <ref column="tag"/> is 0, then if they lack a VLAN header).
474 Frames arriving on other access ports will be forwarded to
475 this port only if they have the same <ref column="tag"/>
476 value. Frames forwarded to this port will not have an
480 When a frame with a 802.1Q header that indicates a nonzero
481 VLAN is received on an access port, it is discarded.
485 <column name="trunks">
487 If this is a trunk port (see above), the 802.1Q VLAN(s) that
488 this port trunks; if it is empty, then the port trunks all
489 VLANs. Must be empty if this is an access port.
492 Frames arriving on trunk ports are dropped if they are not
493 in one of the specified VLANs. For this purpose, packets
494 that have no VLAN header are treated as part of VLAN 0.
499 <group title="Bonding Configuration">
500 <p>A port that has more than one interface is a ``bonded port.'' Bonding
501 allows for load balancing and fail-over. Some kinds of bonding will
502 work with any kind of upstream switch:</p>
505 <dt><code>balance-slb</code></dt>
507 Balances flows among slaves based on source MAC address and output
508 VLAN, with periodic rebalancing as traffic patterns change.
511 <dt><code>active-backup</code></dt>
513 Assigns all flows to one slave, failing over to a backup slave when
514 the active slave is disabled.
519 The following modes require the upstream switch to support 802.3ad with
520 successful LACP negotiation. If LACP negotiation fails then
521 <code>balance-slb</code> style flow hashing is used as a fallback:
525 <dt><code>balance-tcp</code></dt>
527 Balances flows among slaves based on L2, L3, and L4 protocol
528 information such as destination MAC address, IP address, and TCP
534 <dt><code>stable</code></dt>
536 <p>Attempts to always assign a given flow to the same slave
537 consistently. In an effort to maintain stability, no load
538 balancing is done. Uses a similar hashing strategy to
539 <code>balance-tcp</code>, falling back to <code>balance-slb</code>
540 style hashing when LACP negotiations are unsuccessful.</p>
541 <p>Slave selection decisions are made based on LACP port ID when LACP
542 negotiations are successful, falling back to openflow port number
543 when unsuccessful. Thus, decisions are consistent across all
544 ovs-vswitchd instances with equivalent port IDs.</p>
548 <p>These columns apply only to bonded ports. Their values are
549 otherwise ignored.</p>
551 <column name="bond_mode">
552 <p>The type of bonding used for a bonded port. Defaults to
553 <code>balance-slb</code> if unset.
557 <column name="bond_updelay">
558 <p>For a bonded port, the number of milliseconds for which carrier must
559 stay up on an interface before the interface is considered to be up.
560 Specify <code>0</code> to enable the interface immediately.</p>
561 <p>This setting is honored only when at least one bonded interface is
562 already enabled. When no interfaces are enabled, then the first bond
563 interface to come up is enabled immediately.</p>
566 <column name="bond_downdelay">
567 For a bonded port, the number of milliseconds for which carrier must
568 stay down on an interface before the interface is considered to be
569 down. Specify <code>0</code> to disable the interface immediately.
572 <column name="bond_fake_iface">
573 For a bonded port, whether to create a fake internal interface with the
574 name of the port. Use only for compatibility with legacy software that
579 <p>Configures LACP on this port. LACP allows directly connected
580 switches to negotiate which links may be bonded. LACP may be enabled
581 on non-bonded ports for the benefit of any switches they may be
582 connected to. <code>active</code> ports are allowed to initiate LACP
583 negotiations. <code>passive</code> ports are allowed to participate
584 in LACP negotiations initiated by a remote switch, but not allowed to
585 initiate such negotiations themselves. If unset Open vSwitch will
586 choose a reasonable default. </p>
591 <group title="Other Features">
593 Quality of Service configuration for this port.
597 The MAC address to use for this port for the purpose of choosing the
598 bridge's MAC address. This column does not necessarily reflect the
599 port's actual MAC address, nor will setting it change the port's actual
603 <column name="fake_bridge">
604 Does this port represent a sub-bridge for its tagged VLAN within the
605 Bridge? See ovs-vsctl(8) for more information.
608 <column name="external_ids">
610 Key-value pairs for use by external frameworks that integrate with
611 Open vSwitch, rather than by Open vSwitch itself. System integrators
612 should either use the Open vSwitch development mailing list to
613 coordinate on common key-value definitions, or choose key names that
614 are likely to be unique.
617 No key-value pairs native to <ref table="Port"/> are currently
618 defined. For fake bridges (see the <ref column="fake_bridge"/>
619 column), external IDs for the fake bridge are defined here by
620 prefixing a <ref table="Bridge"/> <ref table="Bridge"
621 column="external_ids"/> key with <code>fake-bridge-</code>,
622 e.g. <code>fake-bridge-xs-network-uuids</code>.
626 <column name="other_config">
627 Key-value pairs for configuring rarely used port features. The
628 currently defined key-value pairs are:
630 <dt><code>hwaddr</code></dt>
631 <dd>An Ethernet address in the form
632 <code><var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var></code>.</dd>
633 <dt><code>bond-rebalance-interval</code></dt>
634 <dd>For an SLB bonded port, the number of milliseconds between
635 successive attempts to rebalance the bond, that is, to
636 move source MACs and their flows from one interface on
637 the bond to another in an attempt to keep usage of each
638 interface roughly equal. The default is 10000 (10
639 seconds), and the minimum is 1000 (1 second).</dd>
640 <dt><code>bond-detect-mode</code></dt>
641 <dd> Sets the method used to detect link failures in a bonded port.
642 Options are <code>carrier</code> and <code>miimon</code>. Defaults
643 to <code>carrier</code> which uses each interface's carrier to detect
644 failures. When set to <code>miimon</code>, will check for failures
645 by polling each interface's MII. </dd>
646 <dt><code>bond-miimon-interval</code></dt>
647 <dd> The number of milliseconds between successive attempts to
648 poll each interface's MII. Only relevant on ports which use
649 <code>miimon</code> to detect failures. </dd>
650 <dt><code>bond-hash-basis</code></dt>
651 <dd> An integer hashed along with flows when choosing output slaves.
652 When changed, all flows will be assigned different hash values
653 possibly causing slave selection decisions to change.</dd>
654 <dt><code>lacp-system-id</code></dt>
655 <dd> The LACP system ID of this <ref table="Port"/>. The system ID
656 of a LACP bond is used to identify itself to its partners. Must
657 be a nonzero MAC address.</dd>
658 <dt><code>lacp-system-priority</code></dt>
659 <dd> The LACP system priority of this <ref table="Port"/>. In
660 LACP negotiations, link status decisions are made by the system
661 with the numerically lower priority. Must be a number between 1
663 <dt><code>lacp-time</code></dt>
665 <p>The LACP timing which should be used on this
666 <ref table="Port"/>. Possible values are <code>fast</code>,
667 <code>slow</code> and a positive number of milliseconds. By
668 default <code>slow</code> is used. When configured to be
669 <code>fast</code> LACP heartbeats are requested at a rate of once
670 per second causing connectivity problems to be detected more
671 quickly. In <code>slow</code> mode, heartbeats are requested at
672 a rate of once every 30 seconds.</p>
674 <p>Users may manually set a heartbeat transmission rate to increase
675 the fault detection speed further. When manually set, OVS
676 expects the partner switch to be configured with the same
677 transmission rate. Manually setting <code>lacp-time</code> to
678 something other than <code>fast</code> or <code>slow</code> is
679 not supported by the LACP specification.</p>
681 <dt><code>lacp-strict</code></dt>
682 <dd> When <code>true</code>, configures this <ref table="Port"/> to
683 require successful LACP negotiations to enable any slaves.
684 Defaults to <code>false</code> which safely allows LACP to be used
685 with switches that do not support the protocol.</dd>
686 <dt><code>lacp-force-aggregatable</code></dt>
687 <dd> When <code>true</code>, forces all slaves managed by this
688 <ref table="Port"/> to advertise themselves as aggregatable even if
689 they normally wouldn't. Defaults to <code>false</code>.</dd>
695 <table name="Interface" title="One physical network device in a Port.">
696 An interface within a <ref table="Port"/>.
698 <group title="Core Features">
700 Interface name. Should be alphanumeric and no more than about 8 bytes
701 long. May be the same as the port name, for non-bonded ports. Must
702 otherwise be unique among the names of ports, interfaces, and bridges
707 <p>Ethernet address to set for this interface. If unset then the
708 default MAC address is used:</p>
710 <li>For the local interface, the default is the lowest-numbered MAC
711 address among the other bridge ports, either the value of the
712 <ref table="Port" column="mac"/> in its <ref table="Port"/> record,
713 if set, or its actual MAC (for bonded ports, the MAC of its slave
714 whose name is first in alphabetical order). Internal ports and
715 bridge ports that are used as port mirroring destinations (see the
716 <ref table="Mirror"/> table) are ignored.</li>
717 <li>For other internal interfaces, the default MAC is randomly
719 <li>External interfaces typically have a MAC address associated with
722 <p>Some interfaces may not have a software-controllable MAC
726 <column name="ofport">
727 <p>OpenFlow port number for this interface. Unlike most columns, this
728 column's value should be set only by Open vSwitch itself. Other
729 clients should set this column to an empty set (the default) when
730 creating an <ref table="Interface"/>.</p>
731 <p>Open vSwitch populates this column when the port number becomes
732 known. If the interface is successfully added,
733 <ref column="ofport"/> will be set to a number between 1 and 65535
734 (generally either in the range 1 to 65279, inclusive, or 65534, the
735 port number for the OpenFlow ``local port''). If the interface
736 cannot be added then Open vSwitch sets this column
741 <group title="System-Specific Details">
743 The interface type, one of:
745 <dt><code>system</code></dt>
746 <dd>An ordinary network device, e.g. <code>eth0</code> on Linux.
747 Sometimes referred to as ``external interfaces'' since they are
748 generally connected to hardware external to that on which the Open
749 vSwitch is running. The empty string is a synonym for
750 <code>system</code>.</dd>
751 <dt><code>internal</code></dt>
752 <dd>A simulated network device that sends and receives traffic. An
753 internal interface whose <ref column="name"/> is the same as its
754 bridge's <ref table="Open_vSwitch" column="name"/> is called the
755 ``local interface.'' It does not make sense to bond an internal
756 interface, so the terms ``port'' and ``interface'' are often used
757 imprecisely for internal interfaces.</dd>
758 <dt><code>tap</code></dt>
759 <dd>A TUN/TAP device managed by Open vSwitch.</dd>
760 <dt><code>gre</code></dt>
761 <dd>An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4
762 tunnel. Each tunnel must be uniquely identified by the
763 combination of <code>remote_ip</code>, <code>local_ip</code>, and
764 <code>in_key</code>. Note that if two ports are defined that are
765 the same except one has an optional identifier and the other does
766 not, the more specific one is matched first. <code>in_key</code>
767 is considered more specific than <code>local_ip</code> if a port
768 defines one and another port defines the other. The following
769 options may be specified in the <ref column="options"/> column:
771 <dt><code>remote_ip</code></dt>
772 <dd>Required. The tunnel endpoint.</dd>
775 <dt><code>local_ip</code></dt>
776 <dd>Optional. The destination IP that received packets must
777 match. Default is to match all addresses.</dd>
780 <dt><code>in_key</code></dt>
781 <dd>Optional. The GRE key that received packets must contain.
782 It may either be a 32-bit number (no key and a key of 0 are
783 treated as equivalent) or the word <code>flow</code>. If
784 <code>flow</code> is specified then any key will be accepted
785 and the key will be placed in the <code>tun_id</code> field
786 for matching in the flow table. The ovs-ofctl manual page
787 contains additional information about matching fields in
788 OpenFlow flows. Default is no key.</dd>
791 <dt><code>out_key</code></dt>
792 <dd>Optional. The GRE key to be set on outgoing packets. It may
793 either be a 32-bit number or the word <code>flow</code>. If
794 <code>flow</code> is specified then the key may be set using
795 the <code>set_tunnel</code> Nicira OpenFlow vendor extension (0
796 is used in the absence of an action). The ovs-ofctl manual
797 page contains additional information about the Nicira OpenFlow
798 vendor extensions. Default is no key.</dd>
801 <dt><code>key</code></dt>
802 <dd>Optional. Shorthand to set <code>in_key</code> and
803 <code>out_key</code> at the same time.</dd>
806 <dt><code>tos</code></dt>
807 <dd>Optional. The value of the ToS bits to be set on the
808 encapsulating packet. It may also be the word
809 <code>inherit</code>, in which case the ToS will be copied from
810 the inner packet if it is IPv4 or IPv6 (otherwise it will be
811 0). Note that the ECN fields are always inherited. Default is
815 <dt><code>ttl</code></dt>
816 <dd>Optional. The TTL to be set on the encapsulating packet.
817 It may also be the word <code>inherit</code>, in which case the
818 TTL will be copied from the inner packet if it is IPv4 or IPv6
819 (otherwise it will be the system default, typically 64).
820 Default is the system default TTL.</dd>
823 <dt><code>csum</code></dt>
824 <dd>Optional. Compute GRE checksums on outgoing packets.
825 Checksums present on incoming packets will be validated
826 regardless of this setting. Note that GRE checksums
827 impose a significant performance penalty as they cover the
828 entire packet. As the contents of the packet is typically
829 covered by L3 and L4 checksums, this additional checksum only
830 adds value for the GRE and encapsulated Ethernet headers.
831 Default is disabled, set to <code>true</code> to enable.</dd>
834 <dt><code>pmtud</code></dt>
835 <dd>Optional. Enable tunnel path MTU discovery. If enabled
836 ``ICMP destination unreachable - fragmentation'' needed
837 messages will be generated for IPv4 packets with the DF bit set
838 and IPv6 packets above the minimum MTU if the packet size
839 exceeds the path MTU minus the size of the tunnel headers. It
840 also forces the encapsulating packet DF bit to be set (it is
841 always set if the inner packet implies path MTU discovery).
842 Note that this option causes behavior that is typically
843 reserved for routers and therefore is not entirely in
844 compliance with the IEEE 802.1D specification for bridges.
845 Default is enabled, set to <code>false</code> to disable.</dd>
848 <dt><code>header_cache</code></dt>
849 <dd>Optional. Enable caching of tunnel headers and the output
850 path. This can lead to a significant performance increase
851 without changing behavior. In general it should not be
852 necessary to adjust this setting. However, the caching can
853 bypass certain components of the IP stack (such as IP tables)
854 and it may be useful to disable it if these features are
855 required or as a debugging measure. Default is enabled, set to
856 <code>false</code> to disable.</dd>
859 <dt><code>ipsec_gre</code></dt>
860 <dd>An Ethernet over RFC 2890 Generic Routing Encapsulation
861 over IPv4 IPsec tunnel. Each tunnel (including those of type
862 <code>gre</code>) must be uniquely identified by the
863 combination of <code>remote_ip</code> and
864 <code>local_ip</code>. Note that if two ports are defined
865 that are the same except one has an optional identifier and
866 the other does not, the more specific one is matched first.
867 An authentication method of <code>peer_cert</code> or
868 <code>psk</code> must be defined. The following options may
869 be specified in the <ref column="options"/> column:
871 <dt><code>remote_ip</code></dt>
872 <dd>Required. The tunnel endpoint.</dd>
875 <dt><code>local_ip</code></dt>
876 <dd>Optional. The destination IP that received packets must
877 match. Default is to match all addresses.</dd>
880 <dt><code>peer_cert</code></dt>
881 <dd>Required for certificate authentication. A string
882 containing the peer's certificate in PEM format.
883 Additionally the host's certificate must be specified
884 with the <code>certificate</code> option.</dd>
887 <dt><code>certificate</code></dt>
888 <dd>Required for certificate authentication. The name of a
889 PEM file containing a certificate that will be presented
890 to the peer during authentication.</dd>
893 <dt><code>private_key</code></dt>
894 <dd>Optional for certificate authentication. The name of
895 a PEM file containing the private key associated with
896 <code>certificate</code>. If <code>certificate</code>
897 contains the private key, this option may be omitted.</dd>
900 <dt><code>psk</code></dt>
901 <dd>Required for pre-shared key authentication. Specifies a
902 pre-shared key for authentication that must be identical on
903 both sides of the tunnel.</dd>
906 <dt><code>in_key</code></dt>
907 <dd>Optional. The GRE key that received packets must contain.
908 It may either be a 32-bit number (no key and a key of 0 are
909 treated as equivalent) or the word <code>flow</code>. If
910 <code>flow</code> is specified then any key will be accepted
911 and the key will be placed in the <code>tun_id</code> field
912 for matching in the flow table. The ovs-ofctl manual page
913 contains additional information about matching fields in
914 OpenFlow flows. Default is no key.</dd>
917 <dt><code>out_key</code></dt>
918 <dd>Optional. The GRE key to be set on outgoing packets. It may
919 either be a 32-bit number or the word <code>flow</code>. If
920 <code>flow</code> is specified then the key may be set using
921 the <code>set_tunnel</code> Nicira OpenFlow vendor extension (0
922 is used in the absence of an action). The ovs-ofctl manual
923 page contains additional information about the Nicira OpenFlow
924 vendor extensions. Default is no key.</dd>
927 <dt><code>key</code></dt>
928 <dd>Optional. Shorthand to set <code>in_key</code> and
929 <code>out_key</code> at the same time.</dd>
932 <dt><code>tos</code></dt>
933 <dd>Optional. The value of the ToS bits to be set on the
934 encapsulating packet. It may also be the word
935 <code>inherit</code>, in which case the ToS will be copied from
936 the inner packet if it is IPv4 or IPv6 (otherwise it will be
937 0). Note that the ECN fields are always inherited. Default is
941 <dt><code>ttl</code></dt>
942 <dd>Optional. The TTL to be set on the encapsulating packet.
943 It may also be the word <code>inherit</code>, in which case the
944 TTL will be copied from the inner packet if it is IPv4 or IPv6
945 (otherwise it will be the system default, typically 64).
946 Default is the system default TTL.</dd>
949 <dt><code>csum</code></dt>
950 <dd>Optional. Compute GRE checksums on outgoing packets.
951 Checksums present on incoming packets will be validated
952 regardless of this setting. Note that GRE checksums
953 impose a significant performance penalty as they cover the
954 entire packet. As the contents of the packet is typically
955 covered by L3 and L4 checksums, this additional checksum only
956 adds value for the GRE and encapsulated Ethernet headers.
957 Default is disabled, set to <code>true</code> to enable.</dd>
960 <dt><code>pmtud</code></dt>
961 <dd>Optional. Enable tunnel path MTU discovery. If enabled
962 ``ICMP destination unreachable - fragmentation'' needed
963 messages will be generated for IPv4 packets with the DF bit set
964 and IPv6 packets above the minimum MTU if the packet size
965 exceeds the path MTU minus the size of the tunnel headers. It
966 also forces the encapsulating packet DF bit to be set (it is
967 always set if the inner packet implies path MTU discovery).
968 Note that this option causes behavior that is typically
969 reserved for routers and therefore is not entirely in
970 compliance with the IEEE 802.1D specification for bridges.
971 Default is enabled, set to <code>false</code> to disable.</dd>
974 <dt><code>capwap</code></dt>
975 <dd>Ethernet tunneling over the UDP transport portion of CAPWAP
976 (RFC 5415). This allows interoperability with certain switches
977 where GRE is not available. Note that only the tunneling component
978 of the protocol is implemented. Due to the non-standard use of
979 CAPWAP, UDP ports 58881 and 58882 are used as the source and
980 destination ports respectively. Each tunnel must be uniquely
981 identified by the combination of <code>remote_ip</code> and
982 <code>local_ip</code>. If two ports are defined that are the same
983 except one includes <code>local_ip</code> and the other does not,
984 the more specific one is matched first. CAPWAP support is not
985 available on all platforms. Currently it is only supported in the
986 Linux kernel module with kernel versions >= 2.6.25. The following
987 options may be specified in the <ref column="options"/> column:
989 <dt><code>remote_ip</code></dt>
990 <dd>Required. The tunnel endpoint.</dd>
993 <dt><code>local_ip</code></dt>
994 <dd>Optional. The destination IP that received packets must
995 match. Default is to match all addresses.</dd>
998 <dt><code>tos</code></dt>
999 <dd>Optional. The value of the ToS bits to be set on the
1000 encapsulating packet. It may also be the word
1001 <code>inherit</code>, in which case the ToS will be copied from
1002 the inner packet if it is IPv4 or IPv6 (otherwise it will be
1003 0). Note that the ECN fields are always inherited. Default is
1007 <dt><code>ttl</code></dt>
1008 <dd>Optional. The TTL to be set on the encapsulating packet.
1009 It may also be the word <code>inherit</code>, in which case the
1010 TTL will be copied from the inner packet if it is IPv4 or IPv6
1011 (otherwise it will be the system default, typically 64).
1012 Default is the system default TTL.</dd>
1015 <dt><code>pmtud</code></dt>
1016 <dd>Optional. Enable tunnel path MTU discovery. If enabled
1017 ``ICMP destination unreachable - fragmentation'' needed
1018 messages will be generated for IPv4 packets with the DF bit set
1019 and IPv6 packets above the minimum MTU if the packet size
1020 exceeds the path MTU minus the size of the tunnel headers. It
1021 also forces the encapsulating packet DF bit to be set (it is
1022 always set if the inner packet implies path MTU discovery).
1023 Note that this option causes behavior that is typically
1024 reserved for routers and therefore is not entirely in
1025 compliance with the IEEE 802.1D specification for bridges.
1026 Default is enabled, set to <code>false</code> to disable.</dd>
1029 <dt><code>header_cache</code></dt>
1030 <dd>Optional. Enable caching of tunnel headers and the output
1031 path. This can lead to a significant performance increase
1032 without changing behavior. In general it should not be
1033 necessary to adjust this setting. However, the caching can
1034 bypass certain components of the IP stack (such as IP tables)
1035 and it may be useful to disable it if these features are
1036 required or as a debugging measure. Default is enabled, set to
1037 <code>false</code> to disable.</dd>
1040 <dt><code>patch</code></dt>
1043 A pair of virtual devices that act as a patch cable. The <ref
1044 column="options"/> column must have the following key-value pair:
1047 <dt><code>peer</code></dt>
1049 The <ref column="name"/> of the <ref table="Interface"/> for
1050 the other side of the patch. The named <ref
1051 table="Interface"/>'s own <code>peer</code> option must specify
1052 this <ref table="Interface"/>'s name. That is, the two patch
1053 interfaces must have reversed <ref column="name"/> and
1054 <code>peer</code> values.
1058 <dt><code>null</code></dt>
1059 <dd>An ignored interface.</dd>
1063 <column name="options">
1064 Configuration options whose interpretation varies based on
1065 <ref column="type"/>.
1069 <group title="Interface Status">
1071 Status information about interfaces attached to bridges, updated every
1072 5 seconds. Not all interfaces have all of these properties; virtual
1073 interfaces don't have a link speed, for example. Non-applicable
1074 columns will have empty values.
1076 <column name="admin_state">
1078 The administrative state of the physical network link.
1082 <column name="link_state">
1084 The observed state of the physical network link. This is ordinarily
1085 the link's carrier status. If the interface's <ref table="Port"/> is
1086 a bond configured for miimon monitoring, it is instead the network
1087 link's miimon status.
1091 <column name="link_speed">
1093 The negotiated speed of the physical network link.
1094 Valid values are positive integers greater than 0.
1098 <column name="duplex">
1100 The duplex mode of the physical network link.
1106 The MTU (maximum transmission unit); i.e. the largest
1107 amount of data that can fit into a single Ethernet frame.
1108 The standard Ethernet MTU is 1500 bytes. Some physical media
1109 and many kinds of virtual interfaces can be configured with
1113 This column will be empty for an interface that does not
1114 have an MTU as, for example, some kinds of tunnels do not.
1118 <column name="status">
1120 Key-value pairs that report port status. Supported status
1121 values are <code>type</code>-dependent; some interfaces may not have
1122 a valid <code>driver_name</code>, for example.
1124 <p>The currently defined key-value pairs are:</p>
1126 <dt><code>driver_name</code></dt>
1127 <dd>The name of the device driver controlling the network
1131 <dt><code>driver_version</code></dt>
1132 <dd>The version string of the device driver controlling the
1133 network adapter.</dd>
1136 <dt><code>firmware_version</code></dt>
1137 <dd>The version string of the network adapter's firmware, if
1141 <dt><code>source_ip</code></dt>
1142 <dd>The source IP address used for an IPv4 tunnel end-point,
1143 such as <code>gre</code> or <code>capwap</code>.</dd>
1146 <dt><code>tunnel_egress_iface</code></dt>
1147 <dd>Egress interface for tunnels. Currently only relevant for GRE
1148 and CAPWAP tunnels. On Linux systems, this column will show
1149 the name of the interface which is responsible for routing
1150 traffic destined for the configured <code>remote_ip</code>.
1151 This could be an internal interface such as a bridge port.</dd>
1154 <dt><code>tunnel_egress_iface_carrier</code></dt>
1155 <dd>Whether a carrier is detected on <ref
1156 column="tunnel_egress_iface"/>. Valid values are <code>down</code>
1157 and <code>up</code>.</dd>
1162 <group title="Ingress Policing">
1164 These settings control ingress policing for packets received on this
1165 interface. On a physical interface, this limits the rate at which
1166 traffic is allowed into the system from the outside; on a virtual
1167 interface (one connected to a virtual machine), this limits the rate at
1168 which the VM is able to transmit.
1171 Policing is a simple form of quality-of-service that simply drops
1172 packets received in excess of the configured rate. Due to its
1173 simplicity, policing is usually less accurate and less effective than
1174 egress QoS (which is configured using the <ref table="QoS"/> and <ref
1175 table="Queue"/> tables).
1178 Policing is currently implemented only on Linux. The Linux
1179 implementation uses a simple ``token bucket'' approach:
1183 The size of the bucket corresponds to <ref
1184 column="ingress_policing_burst"/>. Initially the bucket is full.
1187 Whenever a packet is received, its size (converted to tokens) is
1188 compared to the number of tokens currently in the bucket. If the
1189 required number of tokens are available, they are removed and the
1190 packet is forwarded. Otherwise, the packet is dropped.
1193 Whenever it is not full, the bucket is refilled with tokens at the
1194 rate specified by <ref column="ingress_policing_rate"/>.
1198 Policing interacts badly with some network protocols, and especially
1199 with fragmented IP packets. Suppose that there is enough network
1200 activity to keep the bucket nearly empty all the time. Then this token
1201 bucket algorithm will forward a single packet every so often, with the
1202 period depending on packet size and on the configured rate. All of the
1203 fragments of an IP packets are normally transmitted back-to-back, as a
1204 group. In such a situation, therefore, only one of these fragments
1205 will be forwarded and the rest will be dropped. IP does not provide
1206 any way for the intended recipient to ask for only the remaining
1207 fragments. In such a case there are two likely possibilities for what
1208 will happen next: either all of the fragments will eventually be
1209 retransmitted (as TCP will do), in which case the same problem will
1210 recur, or the sender will not realize that its packet has been dropped
1211 and data will simply be lost (as some UDP-based protocols will do).
1212 Either way, it is possible that no forward progress will ever occur.
1214 <column name="ingress_policing_rate">
1216 Maximum rate for data received on this interface, in kbps. Data
1217 received faster than this rate is dropped. Set to <code>0</code>
1218 (the default) to disable policing.
1222 <column name="ingress_policing_burst">
1223 <p>Maximum burst size for data received on this interface, in kb. The
1224 default burst size if set to <code>0</code> is 1000 kb. This value
1225 has no effect if <ref column="ingress_policing_rate"/>
1226 is <code>0</code>.</p>
1228 Specifying a larger burst size lets the algorithm be more forgiving,
1229 which is important for protocols like TCP that react severely to
1230 dropped packets. The burst size should be at least the size of the
1231 interface's MTU. Specifying a value that is numerically at least as
1232 large as 10% of <ref column="ingress_policing_rate"/> helps TCP come
1233 closer to achieving the full rate.
1238 <group title="Other Features">
1240 <column name="monitor">
1241 Connectivity monitor configuration for this interface.
1244 <column name="lacp_current">
1245 Boolean value indicating LACP status for this interface. If true, this
1246 interface has current LACP information about its LACP partner. This
1247 information may be used to monitor the health of interfaces in a LACP
1248 enabled port. This column will be empty if LACP is not enabled.
1251 <column name="external_ids">
1252 Key-value pairs for use by external frameworks that integrate
1253 with Open vSwitch, rather than by Open vSwitch itself. System
1254 integrators should either use the Open vSwitch development
1255 mailing list to coordinate on common key-value definitions, or
1256 choose key names that are likely to be unique. The currently
1257 defined common key-value pairs are:
1259 <dt><code>attached-mac</code></dt>
1261 The MAC address programmed into the ``virtual hardware'' for this
1262 interface, in the form
1263 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>.
1264 For Citrix XenServer, this is the value of the <code>MAC</code>
1265 field in the VIF record for this interface.</dd>
1266 <dt><code>iface-id</code></dt>
1267 <dd>A system-unique identifier for the interface. On XenServer,
1268 this will commonly be the same as <code>xs-vif-uuid</code>.</dd>
1271 Additionally the following key-value pairs specifically
1272 apply to an interface that represents a virtual Ethernet interface
1273 connected to a virtual machine. These key-value pairs should not be
1274 present for other types of interfaces. Keys whose names end
1275 in <code>-uuid</code> have values that uniquely identify the entity
1276 in question. For a Citrix XenServer hypervisor, these values are
1277 UUIDs in RFC 4122 format. Other hypervisors may use other
1280 <p>The currently defined key-value pairs for XenServer are:</p>
1282 <dt><code>xs-vif-uuid</code></dt>
1283 <dd>The virtual interface associated with this interface.</dd>
1284 <dt><code>xs-network-uuid</code></dt>
1285 <dd>The virtual network to which this interface is attached.</dd>
1286 <dt><code>xs-vm-uuid</code></dt>
1287 <dd>The VM to which this interface belongs.</dd>
1291 <column name="other_config">
1292 Key-value pairs for rarely used interface features.
1294 <dt><code>lacp-port-id</code></dt>
1295 <dd> The LACP port ID of this <ref table="Interface"/>. Port IDs are
1296 used in LACP negotiations to identify individual ports
1297 participating in a bond. Must be a number between 1 and
1299 <dt><code>lacp-port-priority</code></dt>
1300 <dd> The LACP port priority of this <ref table="Interface"/>. In
1301 LACP negotiations <ref table="Interface"/>s with numerically lower
1302 priorities are preferred for aggregation. Must be a number between
1304 <dt><code>lacp-aggregation-key</code></dt>
1305 <dd> The LACP aggregation key of this <ref table="Interface"/>.
1306 <ref table="Interface"/>s with different aggregation keys may not
1307 be active within a given <ref table="Port"/> at the same time. Must
1308 be a number between 1 and 65535.</dd>
1312 <column name="statistics">
1314 Key-value pairs that report interface statistics. The current
1315 implementation updates these counters periodically. In the future,
1316 we plan to, instead, update them when an interface is created, when
1317 they are queried (e.g. using an OVSDB <code>select</code> operation),
1318 and just before an interface is deleted due to virtual interface
1319 hot-unplug or VM shutdown, and perhaps at other times, but not on any
1320 regular periodic basis.</p>
1322 The currently defined key-value pairs are listed below. These are
1323 the same statistics reported by OpenFlow in its <code>struct
1324 ofp_port_stats</code> structure. If an interface does not support a
1325 given statistic, then that pair is omitted.</p>
1328 Successful transmit and receive counters:
1330 <dt><code>rx_packets</code></dt>
1331 <dd>Number of received packets.</dd>
1332 <dt><code>rx_bytes</code></dt>
1333 <dd>Number of received bytes.</dd>
1334 <dt><code>tx_packets</code></dt>
1335 <dd>Number of transmitted packets.</dd>
1336 <dt><code>tx_bytes</code></dt>
1337 <dd>Number of transmitted bytes.</dd>
1343 <dt><code>rx_dropped</code></dt>
1344 <dd>Number of packets dropped by RX.</dd>
1345 <dt><code>rx_frame_err</code></dt>
1346 <dd>Number of frame alignment errors.</dd>
1347 <dt><code>rx_over_err</code></dt>
1348 <dd>Number of packets with RX overrun.</dd>
1349 <dt><code>rx_crc_err</code></dt>
1350 <dd>Number of CRC errors.</dd>
1351 <dt><code>rx_errors</code></dt>
1353 Total number of receive errors, greater than or equal
1354 to the sum of the above.
1361 <dt><code>tx_dropped</code></dt>
1362 <dd>Number of packets dropped by TX.</dd>
1363 <dt><code>collisions</code></dt>
1364 <dd>Number of collisions.</dd>
1365 <dt><code>tx_errors</code></dt>
1367 Total number of transmit errors, greater
1368 than or equal to the sum of the above.
1377 <table name="QoS" title="Quality of Service configuration">
1378 <p>Quality of Service (QoS) configuration for each Port that
1381 <column name="type">
1382 <p>The type of QoS to implement. The <ref table="Open_vSwitch"
1383 column="capabilities"/> column in the <ref table="Open_vSwitch"/> table
1384 identifies the types that a switch actually supports. The currently
1385 defined types are listed below:</p>
1387 <dt><code>linux-htb</code></dt>
1389 Linux ``hierarchy token bucket'' classifier. See tc-htb(8) (also at
1390 <code>http://linux.die.net/man/8/tc-htb</code>) and the HTB manual
1391 (<code>http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm</code>)
1392 for information on how this classifier works and how to configure it.
1396 <dt><code>linux-hfsc</code></dt>
1398 Linux "Hierarchical Fair Service Curve" classifier.
1399 See <code>http://linux-ip.net/articles/hfsc.en/</code> for
1400 information on how this classifier works.
1405 <column name="queues">
1406 <p>A map from queue numbers to <ref table="Queue"/> records. The
1407 supported range of queue numbers depend on <ref column="type"/>. The
1408 queue numbers are the same as the <code>queue_id</code> used in
1409 OpenFlow in <code>struct ofp_action_enqueue</code> and other
1410 structures. Queue 0 is used by OpenFlow output actions that do not
1411 specify a specific queue.</p>
1414 <column name="other_config">
1415 <p>Key-value pairs for configuring QoS features that depend on
1416 <ref column="type"/>.</p>
1417 <p>The <code>linux-htb</code> and <code>linux-hfsc</code> classes support
1418 the following key-value pairs:</p>
1420 <dt><code>max-rate</code></dt>
1421 <dd>Maximum rate shared by all queued traffic, in bit/s.
1422 Optional. If not specified, for physical interfaces, the
1423 default is the link rate. For other interfaces or if the
1424 link rate cannot be determined, the default is currently 100
1429 <column name="external_ids">
1430 Key-value pairs for use by external frameworks that integrate with Open
1431 vSwitch, rather than by Open vSwitch itself. System integrators should
1432 either use the Open vSwitch development mailing list to coordinate on
1433 common key-value definitions, or choose key names that are likely to be
1434 unique. No common key-value pairs are currently defined.
1438 <table name="Queue" title="QoS output queue.">
1439 <p>A configuration for a port output queue, used in configuring Quality of
1440 Service (QoS) features. May be referenced by <ref column="queues"
1441 table="QoS"/> column in <ref table="QoS"/> table.</p>
1443 <column name="other_config">
1444 <p>Key-value pairs for configuring the output queue. The supported
1445 key-value pairs and their meanings depend on the <ref column="type"/>
1446 of the <ref column="QoS"/> records that reference this row.</p>
1447 <p>The key-value pairs defined for <ref table="QoS"/> <ref table="QoS"
1448 column="type"/> of <code>min-rate</code> are:</p>
1450 <dt><code>min-rate</code></dt>
1451 <dd>Minimum guaranteed bandwidth, in bit/s. Required. The
1452 floor value is 1500 bytes/s (12,000 bit/s).</dd>
1454 <p>The key-value pairs defined for <ref table="QoS"/> <ref table="QoS"
1455 column="type"/> of <code>linux-htb</code> are:</p>
1457 <dt><code>min-rate</code></dt>
1458 <dd>Minimum guaranteed bandwidth, in bit/s.</dd>
1459 <dt><code>max-rate</code></dt>
1460 <dd>Maximum allowed bandwidth, in bit/s. Optional. If specified, the
1461 queue's rate will not be allowed to exceed the specified value, even
1462 if excess bandwidth is available. If unspecified, defaults to no
1464 <dt><code>burst</code></dt>
1465 <dd>Burst size, in bits. This is the maximum amount of ``credits''
1466 that a queue can accumulate while it is idle. Optional. Details of
1467 the <code>linux-htb</code> implementation require a minimum burst
1468 size, so a too-small <code>burst</code> will be silently
1470 <dt><code>priority</code></dt>
1471 <dd>A nonnegative 32-bit integer. Defaults to 0 if
1472 unspecified. A queue with a smaller <code>priority</code>
1473 will receive all the excess bandwidth that it can use before
1474 a queue with a larger value receives any. Specific priority
1475 values are unimportant; only relative ordering matters.</dd>
1477 <p>The key-value pairs defined for <ref table="QoS"/> <ref table="QoS"
1478 column="type"/> of <code>linux-hfsc</code> are:</p>
1480 <dt><code>min-rate</code></dt>
1481 <dd>Minimum guaranteed bandwidth, in bit/s.</dd>
1482 <dt><code>max-rate</code></dt>
1483 <dd>Maximum allowed bandwidth, in bit/s. Optional. If specified, the
1484 queue's rate will not be allowed to exceed the specified value, even
1485 if excess bandwidth is available. If unspecified, defaults to no
1490 <column name="external_ids">
1491 Key-value pairs for use by external frameworks that integrate with Open
1492 vSwitch, rather than by Open vSwitch itself. System integrators should
1493 either use the Open vSwitch development mailing list to coordinate on
1494 common key-value definitions, or choose key names that are likely to be
1495 unique. No common key-value pairs are currently defined.
1499 <table name="Monitor" title="Connectivity Monitor configuration">
1501 A <ref table="Monitor"/> attaches to an <ref table="Interface"/> to
1502 implement 802.1ag Connectivity Fault Management (CFM). CFM allows a
1503 group of Maintenance Points (MPs) called a Maintenance Association (MA)
1504 to detect connectivity problems with each other. MPs within a MA should
1505 have complete and exclusive interconnectivity. This is verified by
1506 occasionally broadcasting Continuity Check Messages (CCMs) at a
1507 configurable transmission interval. A <ref table="Monitor"/> is
1508 responsible for collecting data about other MPs in its MA and
1512 <group title="Monitor Configuration">
1513 <column name="mpid">
1514 A Maintenance Point ID (MPID) uniquely identifies each endpoint within
1515 a Maintenance Association (see <ref column="ma_name"/>). The MPID is
1516 used to identify this <ref table="Monitor"/> to other endpoints in the
1520 <column name="remote_mps">
1521 A set of <ref table="Maintenance_Points"/> which this
1522 <ref table="Monitor"/> should have connectivity to. If this
1523 <ref table="Monitor"/> does not have connectivity to any MPs in this
1524 set, or has connectivity to any MPs not in this set, a fault is
1528 <column name="ma_name">
1529 A Maintenance Association (MA) name pairs with a Maintenance Domain
1530 (MD) name to uniquely identify a MA. A MA is a group of endpoints who
1531 have complete and exclusive interconnectivity. Defaults to
1532 <code>ovs</code> if unset.
1535 <column name="md_name">
1536 A Maintenance Domain name pairs with a Maintenance Association name to
1537 uniquely identify a MA. Defaults to <code>ovs</code> if unset.
1540 <column name="interval">
1541 The transmission interval of CCMs in milliseconds. Three missed CCMs
1542 indicate a connectivity fault. Defaults to 1000ms.
1546 <group title="Monitor Status">
1547 <column name="fault">
1548 Indicates a Connectivity Fault caused by a configuration error, a down
1549 remote MP, or unexpected connectivity to a remote MAID or remote MP.
1554 <table name="Maintenance_Point" title="Maintenance Point configuration">
1556 A <ref table="Maintenance_Point"/> represents a MP which a
1557 <ref table="Monitor"/> has or should have connectivity to.
1560 <group title="Maintenance_Point Configuration">
1561 <column name="mpid">
1562 A Maintenance Point ID (MPID) uniquely identifies each endpoint within
1563 a Maintenance Association. All MPs within a MA should have a unique
1568 <group title="Maintenance_Point Status">
1569 <column name="fault">
1570 Indicates a connectivity fault.
1575 <table name="Mirror" title="Port mirroring (SPAN/RSPAN).">
1576 <p>A port mirror within a <ref table="Bridge"/>.</p>
1577 <p>A port mirror configures a bridge to send selected frames to special
1578 ``mirrored'' ports, in addition to their normal destinations. Mirroring
1579 traffic may also be referred to as SPAN or RSPAN, depending on the
1580 mechanism used for delivery.</p>
1582 <column name="name">
1583 Arbitrary identifier for the <ref table="Mirror"/>.
1586 <group title="Selecting Packets for Mirroring">
1588 To be selected for mirroring, a given packet must enter or leave the
1589 bridge through a selected port and it must also be in one of the
1593 <column name="select_all">
1594 If true, every packet arriving or departing on any port is
1595 selected for mirroring.
1598 <column name="select_dst_port">
1599 Ports on which departing packets are selected for mirroring.
1602 <column name="select_src_port">
1603 Ports on which arriving packets are selected for mirroring.
1606 <column name="select_vlan">
1607 VLANs on which packets are selected for mirroring. An empty set
1608 selects packets on all VLANs.
1612 <group title="Mirroring Destination Configuration">
1614 These columns are mutually exclusive. Exactly one of them must be
1618 <column name="output_port">
1619 <p>Output port for selected packets, if nonempty.</p>
1620 <p>Specifying a port for mirror output reserves that port exclusively
1621 for mirroring. No frames other than those selected for mirroring
1622 will be forwarded to the port, and any frames received on the port
1623 will be discarded.</p>
1624 <p>This type of mirroring is sometimes called SPAN.</p>
1627 <column name="output_vlan">
1628 <p>Output VLAN for selected packets, if nonempty.</p>
1629 <p>The frames will be sent out all ports that trunk
1630 <ref column="output_vlan"/>, as well as any ports with implicit VLAN
1631 <ref column="output_vlan"/>. When a mirrored frame is sent out a
1632 trunk port, the frame's VLAN tag will be set to
1633 <ref column="output_vlan"/>, replacing any existing tag; when it is
1634 sent out an implicit VLAN port, the frame will not be tagged. This
1635 type of mirroring is sometimes called RSPAN.</p>
1636 <p><em>Please note:</em> Mirroring to a VLAN can disrupt a network that
1637 contains unmanaged switches. Consider an unmanaged physical switch
1638 with two ports: port 1, connected to an end host, and port 2,
1639 connected to an Open vSwitch configured to mirror received packets
1640 into VLAN 123 on port 2. Suppose that the end host sends a packet on
1641 port 1 that the physical switch forwards to port 2. The Open vSwitch
1642 forwards this packet to its destination and then reflects it back on
1643 port 2 in VLAN 123. This reflected packet causes the unmanaged
1644 physical switch to replace the MAC learning table entry, which
1645 correctly pointed to port 1, with one that incorrectly points to port
1646 2. Afterward, the physical switch will direct packets destined for
1647 the end host to the Open vSwitch on port 2, instead of to the end
1648 host on port 1, disrupting connectivity. If mirroring to a VLAN is
1649 desired in this scenario, then the physical switch must be replaced
1650 by one that learns Ethernet addresses on a per-VLAN basis. In
1651 addition, learning should be disabled on the VLAN containing mirrored
1652 traffic. If this is not done then intermediate switches will learn
1653 the MAC address of each end host from the mirrored traffic. If
1654 packets being sent to that end host are also mirrored, then they will
1655 be dropped since the switch will attempt to send them out the input
1656 port. Disabling learning for the VLAN will cause the switch to
1657 correctly send the packet out all ports configured for that VLAN. If
1658 Open vSwitch is being used as an intermediate switch, learning can be
1659 disabled by adding the mirrored VLAN to <ref column="flood_vlans"/>
1660 in the appropriate <ref table="Bridge"/> table or tables.</p>
1664 <group title="Other Features">
1665 <column name="external_ids">
1666 Key-value pairs for use by external frameworks that integrate with Open
1667 vSwitch, rather than by Open vSwitch itself. System integrators should
1668 either use the Open vSwitch development mailing list to coordinate on
1669 common key-value definitions, or choose key names that are likely to be
1670 unique. No common key-value pairs are currently defined.
1675 <table name="Controller" title="OpenFlow controller configuration.">
1676 <p>An OpenFlow controller.</p>
1679 Open vSwitch supports two kinds of OpenFlow controllers:
1683 <dt>Primary controllers</dt>
1686 This is the kind of controller envisioned by the OpenFlow 1.0
1687 specification. Usually, a primary controller implements a network
1688 policy by taking charge of the switch's flow table.
1692 Open vSwitch initiates and maintains persistent connections to
1693 primary controllers, retrying the connection each time it fails or
1694 drops. The <ref table="Bridge" column="fail_mode"/> column in the
1695 <ref table="Bridge"/> table applies to primary controllers.
1699 Open vSwitch permits a bridge to have any number of primary
1700 controllers. When multiple controllers are configured, Open
1701 vSwitch connects to all of them simultaneously. Because
1702 OpenFlow 1.0 does not specify how multiple controllers
1703 coordinate in interacting with a single switch, more than
1704 one primary controller should be specified only if the
1705 controllers are themselves designed to coordinate with each
1706 other. (The Nicira-defined <code>NXT_ROLE</code> OpenFlow
1707 vendor extension may be useful for this.)
1710 <dt>Service controllers</dt>
1713 These kinds of OpenFlow controller connections are intended for
1714 occasional support and maintenance use, e.g. with
1715 <code>ovs-ofctl</code>. Usually a service controller connects only
1716 briefly to inspect or modify some of a switch's state.
1720 Open vSwitch listens for incoming connections from service
1721 controllers. The service controllers initiate and, if necessary,
1722 maintain the connections from their end. The <ref table="Bridge"
1723 column="fail_mode"/> column in the <ref table="Bridge"/> table does
1724 not apply to service controllers.
1728 Open vSwitch supports configuring any number of service controllers.
1734 The <ref column="target"/> determines the type of controller.
1737 <group title="Core Features">
1738 <column name="target">
1739 <p>Connection method for controller.</p>
1741 The following connection methods are currently supported for primary
1745 <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
1747 <p>The specified SSL <var>port</var> (default: 6633) on the host at
1748 the given <var>ip</var>, which must be expressed as an IP address
1749 (not a DNS name). The <ref table="Open_vSwitch" column="ssl"/>
1750 column in the <ref table="Open_vSwitch"/> table must point to a
1751 valid SSL configuration when this form is used.</p>
1752 <p>SSL support is an optional feature that is not always built as
1753 part of Open vSwitch.</p>
1755 <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
1756 <dd>The specified TCP <var>port</var> (default: 6633) on the host at
1757 the given <var>ip</var>, which must be expressed as an IP address
1758 (not a DNS name).</dd>
1761 The following connection methods are currently supported for service
1765 <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
1768 Listens for SSL connections on the specified TCP <var>port</var>
1769 (default: 6633). If <var>ip</var>, which must be expressed as an
1770 IP address (not a DNS name), is specified, then connections are
1771 restricted to the specified local IP address.
1774 The <ref table="Open_vSwitch" column="ssl"/> column in the <ref
1775 table="Open_vSwitch"/> table must point to a valid SSL
1776 configuration when this form is used.
1778 <p>SSL support is an optional feature that is not always built as
1779 part of Open vSwitch.</p>
1781 <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
1783 Listens for connections on the specified TCP <var>port</var>
1784 (default: 6633). If <var>ip</var>, which must be expressed as an
1785 IP address (not a DNS name), is specified, then connections are
1786 restricted to the specified local IP address.
1789 <p>When multiple controllers are configured for a single bridge, the
1790 <ref column="target"/> values must be unique. Duplicate
1791 <ref column="target"/> values yield unspecified results.</p>
1794 <column name="connection_mode">
1795 <p>If it is specified, this setting must be one of the following
1796 strings that describes how Open vSwitch contacts this OpenFlow
1797 controller over the network:</p>
1800 <dt><code>in-band</code></dt>
1801 <dd>In this mode, this controller's OpenFlow traffic travels over the
1802 bridge associated with the controller. With this setting, Open
1803 vSwitch allows traffic to and from the controller regardless of the
1804 contents of the OpenFlow flow table. (Otherwise, Open vSwitch
1805 would never be able to connect to the controller, because it did
1806 not have a flow to enable it.) This is the most common connection
1807 mode because it is not necessary to maintain two independent
1809 <dt><code>out-of-band</code></dt>
1810 <dd>In this mode, OpenFlow traffic uses a control network separate
1811 from the bridge associated with this controller, that is, the
1812 bridge does not use any of its own network devices to communicate
1813 with the controller. The control network must be configured
1814 separately, before or after <code>ovs-vswitchd</code> is started.
1818 <p>If not specified, the default is implementation-specific.</p>
1822 <group title="Controller Failure Detection and Handling">
1823 <column name="max_backoff">
1824 Maximum number of milliseconds to wait between connection attempts.
1825 Default is implementation-specific.
1828 <column name="inactivity_probe">
1829 Maximum number of milliseconds of idle time on connection to
1830 controller before sending an inactivity probe message. If Open
1831 vSwitch does not communicate with the controller for the specified
1832 number of seconds, it will send a probe. If a response is not
1833 received for the same additional amount of time, Open vSwitch
1834 assumes the connection has been broken and attempts to reconnect.
1835 Default is implementation-specific. A value of 0 disables
1840 <group title="OpenFlow Rate Limiting">
1841 <column name="controller_rate_limit">
1842 <p>The maximum rate at which packets in unknown flows will be
1843 forwarded to the OpenFlow controller, in packets per second. This
1844 feature prevents a single bridge from overwhelming the controller.
1845 If not specified, the default is implementation-specific.</p>
1846 <p>In addition, when a high rate triggers rate-limiting, Open
1847 vSwitch queues controller packets for each port and transmits
1848 them to the controller at the configured rate. The number of
1849 queued packets is limited by
1850 the <ref column="controller_burst_limit"/> value. The packet
1851 queue is shared fairly among the ports on a bridge.</p><p>Open
1852 vSwitch maintains two such packet rate-limiters per bridge.
1853 One of these applies to packets sent up to the controller
1854 because they do not correspond to any flow. The other applies
1855 to packets sent up to the controller by request through flow
1856 actions. When both rate-limiters are filled with packets, the
1857 actual rate that packets are sent to the controller is up to
1858 twice the specified rate.</p>
1861 <column name="controller_burst_limit">
1862 In conjunction with <ref column="controller_rate_limit"/>,
1863 the maximum number of unused packet credits that the bridge will
1864 allow to accumulate, in packets. If not specified, the default
1865 is implementation-specific.
1869 <group title="Additional In-Band Configuration">
1870 <p>These values are considered only in in-band control mode (see
1871 <ref column="connection_mode"/>).</p>
1873 <p>When multiple controllers are configured on a single bridge, there
1874 should be only one set of unique values in these columns. If different
1875 values are set for these columns in different controllers, the effect
1878 <column name="local_ip">
1879 The IP address to configure on the local port,
1880 e.g. <code>192.168.0.123</code>. If this value is unset, then
1881 <ref column="local_netmask"/> and <ref column="local_gateway"/> are
1885 <column name="local_netmask">
1886 The IP netmask to configure on the local port,
1887 e.g. <code>255.255.255.0</code>. If <ref column="local_ip"/> is set
1888 but this value is unset, then the default is chosen based on whether
1889 the IP address is class A, B, or C.
1892 <column name="local_gateway">
1893 The IP address of the gateway to configure on the local port, as a
1894 string, e.g. <code>192.168.0.1</code>. Leave this column unset if
1895 this network has no gateway.
1899 <group title="Other Features">
1900 <column name="external_ids">
1901 Key-value pairs for use by external frameworks that integrate with Open
1902 vSwitch, rather than by Open vSwitch itself. System integrators should
1903 either use the Open vSwitch development mailing list to coordinate on
1904 common key-value definitions, or choose key names that are likely to be
1905 unique. No common key-value pairs are currently defined.
1909 <group title="Controller Status">
1910 <column name="is_connected">
1911 <code>true</code> if currently connected to this controller,
1912 <code>false</code> otherwise.
1915 <column name="role">
1916 <p>The level of authority this controller has on the associated
1917 bridge. Possible values are:</p>
1919 <dt><code>other</code></dt>
1920 <dd>Allows the controller access to all OpenFlow features.</dd>
1921 <dt><code>master</code></dt>
1922 <dd>Equivalent to <code>other</code>, except that there may be at
1923 most one master controller at a time. When a controller configures
1924 itself as <code>master</code>, any existing master is demoted to
1925 the <code>slave</code>role.</dd>
1926 <dt><code>slave</code></dt>
1927 <dd>Allows the controller read-only access to OpenFlow features.
1928 Attempts to modify the flow table will be rejected with an
1929 error. Slave controllers do not receive OFPT_PACKET_IN or
1930 OFPT_FLOW_REMOVED messages, but they do receive OFPT_PORT_STATUS
1935 <column name="status">
1936 <p>Key-value pairs that report controller status.</p>
1938 <dt><code>last_error</code></dt>
1939 <dd>A human-readable description of the last error on the connection
1940 to the controller; i.e. <code>strerror(errno)</code>. This key
1941 will exist only if an error has occurred.</dd>
1942 <dt><code>state</code></dt>
1943 <dd>The state of the connection to the controller. Possible values
1944 are: <code>VOID</code> (connection is disabled),
1945 <code>BACKOFF</code> (attempting to reconnect at an increasing
1946 period), <code>CONNECTING</code> (attempting to connect),
1947 <code>ACTIVE</code> (connected, remote host responsive), and
1948 <code>IDLE</code> (remote host idle, sending keep-alive). These
1949 values may change in the future. They are provided only for human
1951 <dt><code>sec_since_connect</code></dt>
1952 <dd>The amount of time since this controller last successfully
1953 connected to the switch (in seconds). Value is empty if controller
1954 has never successfully connected.</dd>
1955 <dt><code>sec_since_disconnect</code></dt>
1956 <dd>The amount of time since this controller last disconnected from
1957 the switch (in seconds). Value is empty if controller has never
1964 <table name="Manager" title="OVSDB management connection.">
1966 Configuration for a database connection to an Open vSwitch database
1971 This table primarily configures the Open vSwitch database
1972 (<code>ovsdb-server</code>), not the Open vSwitch switch
1973 (<code>ovs-vswitchd</code>). The switch does read the table to determine
1974 what connections should be treated as in-band.
1978 The Open vSwitch database server can initiate and maintain active
1979 connections to remote clients. It can also listen for database
1983 <group title="Core Features">
1984 <column name="target">
1985 <p>Connection method for managers.</p>
1987 The following connection methods are currently supported:
1990 <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
1993 The specified SSL <var>port</var> (default: 6632) on the host at
1994 the given <var>ip</var>, which must be expressed as an IP address
1995 (not a DNS name). The <ref table="Open_vSwitch" column="ssl"/>
1996 column in the <ref table="Open_vSwitch"/> table must point to a
1997 valid SSL configuration when this form is used.
2000 SSL support is an optional feature that is not always built as
2001 part of Open vSwitch.
2005 <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
2007 The specified TCP <var>port</var> (default: 6632) on the host at
2008 the given <var>ip</var>, which must be expressed as an IP address
2011 <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
2014 Listens for SSL connections on the specified TCP <var>port</var>
2015 (default: 6632). If <var>ip</var>, which must be expressed as an
2016 IP address (not a DNS name), is specified, then connections are
2017 restricted to the specified local IP address.
2020 The <ref table="Open_vSwitch" column="ssl"/> column in the <ref
2021 table="Open_vSwitch"/> table must point to a valid SSL
2022 configuration when this form is used.
2025 SSL support is an optional feature that is not always built as
2026 part of Open vSwitch.
2029 <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
2031 Listens for connections on the specified TCP <var>port</var>
2032 (default: 6632). If <var>ip</var>, which must be expressed as an
2033 IP address (not a DNS name), is specified, then connections are
2034 restricted to the specified local IP address.
2037 <p>When multiple managers are configured, the <ref column="target"/>
2038 values must be unique. Duplicate <ref column="target"/> values yield
2039 unspecified results.</p>
2042 <column name="connection_mode">
2044 If it is specified, this setting must be one of the following strings
2045 that describes how Open vSwitch contacts this OVSDB client over the
2050 <dt><code>in-band</code></dt>
2052 In this mode, this connection's traffic travels over a bridge
2053 managed by Open vSwitch. With this setting, Open vSwitch allows
2054 traffic to and from the client regardless of the contents of the
2055 OpenFlow flow table. (Otherwise, Open vSwitch would never be able
2056 to connect to the client, because it did not have a flow to enable
2057 it.) This is the most common connection mode because it is not
2058 necessary to maintain two independent networks.
2060 <dt><code>out-of-band</code></dt>
2062 In this mode, the client's traffic uses a control network separate
2063 from that managed by Open vSwitch, that is, Open vSwitch does not
2064 use any of its own network devices to communicate with the client.
2065 The control network must be configured separately, before or after
2066 <code>ovs-vswitchd</code> is started.
2071 If not specified, the default is implementation-specific.
2076 <group title="Client Failure Detection and Handling">
2077 <column name="max_backoff">
2078 Maximum number of milliseconds to wait between connection attempts.
2079 Default is implementation-specific.
2082 <column name="inactivity_probe">
2083 Maximum number of milliseconds of idle time on connection to the client
2084 before sending an inactivity probe message. If Open vSwitch does not
2085 communicate with the client for the specified number of seconds, it
2086 will send a probe. If a response is not received for the same
2087 additional amount of time, Open vSwitch assumes the connection has been
2088 broken and attempts to reconnect. Default is implementation-specific.
2089 A value of 0 disables inactivity probes.
2093 <group title="Other Features">
2094 <column name="external_ids">
2095 Key-value pairs for use by external frameworks that integrate with Open
2096 vSwitch, rather than by Open vSwitch itself. System integrators should
2097 either use the Open vSwitch development mailing list to coordinate on
2098 common key-value definitions, or choose key names that are likely to be
2099 unique. No common key-value pairs are currently defined.
2103 <group title="Status">
2104 <column name="is_connected">
2105 <code>true</code> if currently connected to this manager,
2106 <code>false</code> otherwise.
2109 <column name="status">
2110 <p>Key-value pairs that report manager status.</p>
2112 <dt><code>last_error</code></dt>
2113 <dd>A human-readable description of the last error on the connection
2114 to the manager; i.e. <code>strerror(errno)</code>. This key
2115 will exist only if an error has occurred.</dd>
2118 <dt><code>state</code></dt>
2119 <dd>The state of the connection to the manager. Possible values
2120 are: <code>VOID</code> (connection is disabled),
2121 <code>BACKOFF</code> (attempting to reconnect at an increasing
2122 period), <code>CONNECTING</code> (attempting to connect),
2123 <code>ACTIVE</code> (connected, remote host responsive), and
2124 <code>IDLE</code> (remote host idle, sending keep-alive). These
2125 values may change in the future. They are provided only for human
2129 <dt><code>sec_since_connect</code></dt>
2130 <dd>The amount of time since this manager last successfully connected
2131 to the database (in seconds). Value is empty if manager has never
2132 successfully connected.</dd>
2135 <dt><code>sec_since_disconnect</code></dt>
2136 <dd>The amount of time since this manager last disconnected from the
2137 database (in seconds). Value is empty if manager has never
2144 <table name="NetFlow">
2145 A NetFlow target. NetFlow is a protocol that exports a number of
2146 details about terminating IP flows, such as the principals involved
2149 <column name="targets">
2150 NetFlow targets in the form
2151 <code><var>ip</var>:<var>port</var></code>. The <var>ip</var>
2152 must be specified numerically, not as a DNS name.
2155 <column name="engine_id">
2156 Engine ID to use in NetFlow messages. Defaults to datapath index
2160 <column name="engine_type">
2161 Engine type to use in NetFlow messages. Defaults to datapath
2162 index if not specified.
2165 <column name="active_timeout">
2166 The interval at which NetFlow records are sent for flows that are
2167 still active, in seconds. A value of <code>0</code> requests the
2168 default timeout (currently 600 seconds); a value of <code>-1</code>
2169 disables active timeouts.
2172 <column name="add_id_to_interface">
2173 <p>If this column's value is <code>false</code>, the ingress and egress
2174 interface fields of NetFlow flow records are derived from OpenFlow port
2175 numbers. When it is <code>true</code>, the 7 most significant bits of
2176 these fields will be replaced by the least significant 7 bits of the
2177 engine id. This is useful because many NetFlow collectors do not
2178 expect multiple switches to be sending messages from the same host, so
2179 they do not store the engine information which could be used to
2180 disambiguate the traffic.</p>
2181 <p>When this option is enabled, a maximum of 508 ports are supported.</p>
2184 <column name="external_ids">
2185 Key-value pairs for use by external frameworks that integrate with Open
2186 vSwitch, rather than by Open vSwitch itself. System integrators should
2187 either use the Open vSwitch development mailing list to coordinate on
2188 common key-value definitions, or choose key names that are likely to be
2189 unique. No common key-value pairs are currently defined.
2194 SSL configuration for an Open_vSwitch.
2196 <column name="private_key">
2197 Name of a PEM file containing the private key used as the switch's
2198 identity for SSL connections to the controller.
2201 <column name="certificate">
2202 Name of a PEM file containing a certificate, signed by the
2203 certificate authority (CA) used by the controller and manager,
2204 that certifies the switch's private key, identifying a trustworthy
2208 <column name="ca_cert">
2209 Name of a PEM file containing the CA certificate used to verify
2210 that the switch is connected to a trustworthy controller.
2213 <column name="bootstrap_ca_cert">
2214 If set to <code>true</code>, then Open vSwitch will attempt to
2215 obtain the CA certificate from the controller on its first SSL
2216 connection and save it to the named PEM file. If it is successful,
2217 it will immediately drop the connection and reconnect, and from then
2218 on all SSL connections must be authenticated by a certificate signed
2219 by the CA certificate thus obtained. <em>This option exposes the
2220 SSL connection to a man-in-the-middle attack obtaining the initial
2221 CA certificate.</em> It may still be useful for bootstrapping.
2224 <column name="external_ids">
2225 Key-value pairs for use by external frameworks that integrate with Open
2226 vSwitch, rather than by Open vSwitch itself. System integrators should
2227 either use the Open vSwitch development mailing list to coordinate on
2228 common key-value definitions, or choose key names that are likely to be
2229 unique. No common key-value pairs are currently defined.
2233 <table name="sFlow">
2234 <p>An sFlow(R) target. sFlow is a protocol for remote monitoring
2237 <column name="agent">
2238 Name of the network device whose IP address should be reported as the
2239 ``agent address'' to collectors. If not specified, the IP address
2240 defaults to the <ref table="Controller" column="local_ip"/> in the
2241 collector's <ref table="Controller"/>. If an agent IP address cannot be
2242 determined either way, sFlow is disabled.
2245 <column name="header">
2246 Number of bytes of a sampled packet to send to the collector.
2247 If not specified, the default is 128 bytes.
2250 <column name="polling">
2251 Polling rate in seconds to send port statistics to the collector.
2252 If not specified, defaults to 30 seconds.
2255 <column name="sampling">
2256 Rate at which packets should be sampled and sent to the collector.
2257 If not specified, defaults to 400, which means one out of 400
2258 packets, on average, will be sent to the collector.
2261 <column name="targets">
2262 sFlow targets in the form
2263 <code><var>ip</var>:<var>port</var></code>.
2266 <column name="external_ids">
2267 Key-value pairs for use by external frameworks that integrate with Open
2268 vSwitch, rather than by Open vSwitch itself. System integrators should
2269 either use the Open vSwitch development mailing list to coordinate on
2270 common key-value definitions, or choose key names that are likely to be
2271 unique. No common key-value pairs are currently defined.
2275 <table name="Capability">
2276 <p>Records in this table describe functionality supported by the hardware
2277 and software platform on which this Open vSwitch is based. Clients
2278 should not modify this table.</p>
2280 <p>A record in this table is meaningful only if it is referenced by the
2281 <ref table="Open_vSwitch" column="capabilities"/> column in the
2282 <ref table="Open_vSwitch"/> table. The key used to reference it, called
2283 the record's ``category,'' determines the meanings of the
2284 <ref column="details"/> column. The following general forms of
2285 categories are currently defined:</p>
2288 <dt><code>qos-<var>type</var></code></dt>
2289 <dd><var>type</var> is supported as the value for
2290 <ref column="type" table="QoS"/> in the <ref table="QoS"/> table.
2294 <column name="details">
2295 <p>Key-value pairs that describe capabilities. The meaning of the pairs
2296 depends on the category key that the <ref table="Open_vSwitch"
2297 column="capabilities"/> column in the <ref table="Open_vSwitch"/> table
2298 uses to reference this record, as described above.</p>
2300 <p>The presence of a record for category <code>qos-<var>type</var></code>
2301 indicates that the switch supports <var>type</var> as the value of
2302 the <ref table="QoS" column="type"/> column in the <ref table="QoS"/>
2303 table. The following key-value pairs are defined to further describe
2304 QoS capabilities:</p>
2307 <dt><code>n-queues</code></dt>
2308 <dd>Number of supported queues, as a positive integer. Keys in the
2309 <ref table="QoS" column="queues"/> column for <ref table="QoS"/>
2310 records whose <ref table="QoS" column="type"/> value
2311 equals <var>type</var> must range between 0 and this value minus one,
git://git.onelab.eu / sliver-openvswitch.git / blob