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
15 <h2>Common Columns</h2>
18 Most tables contain two special columns, named <code>other_config</code>
19 and <code>external_ids</code>. These columns have the same form and
20 purpose each place that they appear, so we describe them here to save space
25 <dt><code>other_config</code>: map of string-string pairs</dt>
28 Key-value pairs for configuring rarely used features. Supported keys,
29 along with the forms taken by their values, are documented individually
33 A few tables do not have <code>other_config</code> columns because no
34 key-value pairs have yet been defined for them.
38 <dt><code>external_ids</code>: map of string-string pairs</dt>
40 Key-value pairs for use by external frameworks that integrate with Open
41 vSwitch, rather than by Open vSwitch itself. System integrators should
42 either use the Open vSwitch development mailing list to coordinate on
43 common key-value definitions, or choose key names that are likely to be
44 unique. In some cases, where key-value pairs have been defined that are
45 likely to be widely useful, they are documented individually for each
50 <table name="Open_vSwitch" title="Open vSwitch configuration.">
51 Configuration for an Open vSwitch daemon. There must be exactly
52 one record in the <ref table="Open_vSwitch"/> table.
54 <group title="Configuration">
55 <column name="bridges">
56 Set of bridges managed by the daemon.
60 SSL used globally by the daemon.
63 <column name="external_ids" key="system-id">
64 A unique identifier for the Open vSwitch's physical host.
65 The form of the identifier depends on the type of the host.
66 On a Citrix XenServer, this will likely be the same as
67 <ref column="external_ids" key="xs-system-uuid"/>.
70 <column name="external_ids" key="xs-system-uuid">
71 The Citrix XenServer universally unique identifier for the physical
72 host as displayed by <code>xe host-list</code>.
76 <group title="Status">
77 <column name="next_cfg">
78 Sequence number for client to increment. When a client modifies
79 any part of the database configuration and wishes to wait for
80 Open vSwitch to finish applying the changes, it may increment
84 <column name="cur_cfg">
85 Sequence number that Open vSwitch sets to the current value of
86 <ref column="next_cfg"/> after it finishes applying a set of
87 configuration changes.
90 <group title="Statistics">
92 The <code>statistics</code> column contains key-value pairs that
93 report statistics about a system running an Open vSwitch. These are
94 updated periodically (currently, every 5 seconds). Key-value pairs
95 that cannot be determined or that do not apply to a platform are
99 <column name="other_config" key="enable-statistics"
100 type='{"type": "boolean"}'>
101 Statistics are disabled by default to avoid overhead in the common
102 case when statistics gathering is not useful. Set this value to
103 <code>true</code> to enable populating the <ref column="statistics"/>
104 column or to <code>false</code> to explicitly disable it.
107 <column name="statistics" key="cpu"
108 type='{"type": "integer", "minInteger": 1}'>
110 Number of CPU processors, threads, or cores currently online and
111 available to the operating system on which Open vSwitch is running,
112 as an integer. This may be less than the number installed, if some
113 are not online or if they are not available to the operating
117 Open vSwitch userspace processes are not multithreaded, but the
118 Linux kernel-based datapath is.
122 <column name="statistics" key="load_average">
123 A comma-separated list of three floating-point numbers,
124 representing the system load average over the last 1, 5, and 15
125 minutes, respectively.
128 <column name="statistics" key="memory">
130 A comma-separated list of integers, each of which represents a
131 quantity of memory in kilobytes that describes the operating
132 system on which Open vSwitch is running. In respective order,
137 <li>Total amount of RAM allocated to the OS.</li>
138 <li>RAM allocated to the OS that is in use.</li>
139 <li>RAM that can be flushed out to disk or otherwise discarded
140 if that space is needed for another purpose. This number is
141 necessarily less than or equal to the previous value.</li>
142 <li>Total disk space allocated for swap.</li>
143 <li>Swap space currently in use.</li>
147 On Linux, all five values can be determined and are included. On
148 other operating systems, only the first two values can be
149 determined, so the list will only have two values.
153 <column name="statistics" key="process_NAME">
155 One such key-value pair, with <code>NAME</code> replaced by
156 a process name, will exist for each running Open vSwitch
157 daemon process, with <var>name</var> replaced by the
158 daemon's name (e.g. <code>process_ovs-vswitchd</code>). The
159 value is a comma-separated list of integers. The integers
160 represent the following, with memory measured in kilobytes
161 and durations in milliseconds:
165 <li>The process's virtual memory size.</li>
166 <li>The process's resident set size.</li>
167 <li>The amount of user and system CPU time consumed by the
169 <li>The number of times that the process has crashed and been
170 automatically restarted by the monitor.</li>
171 <li>The duration since the process was started.</li>
172 <li>The duration for which the process has been running.</li>
176 The interpretation of some of these values depends on whether the
177 process was started with the <option>--monitor</option>. If it
178 was not, then the crash count will always be 0 and the two
179 durations will always be the same. If <option>--monitor</option>
180 was given, then the crash count may be positive; if it is, the
181 latter duration is the amount of time since the most recent crash
186 There will be one key-value pair for each file in Open vSwitch's
187 ``run directory'' (usually <code>/var/run/openvswitch</code>)
188 whose name ends in <code>.pid</code>, whose contents are a
189 process ID, and which is locked by a running process. The
190 <var>name</var> is taken from the pidfile's name.
194 Currently Open vSwitch is only able to obtain all of the above
195 detail on Linux systems. On other systems, the same key-value
196 pairs will be present but the values will always be the empty
201 <column name="statistics" key="file_systems">
203 A space-separated list of information on local, writable file
204 systems. Each item in the list describes one file system and
205 consists in turn of a comma-separated list of the following:
209 <li>Mount point, e.g. <code>/</code> or <code>/var/log</code>.
210 Any spaces or commas in the mount point are replaced by
212 <li>Total size, in kilobytes, as an integer.</li>
213 <li>Amount of storage in use, in kilobytes, as an integer.</li>
217 This key-value pair is omitted if there are no local, writable
218 file systems or if Open vSwitch cannot obtain the needed
225 <group title="Version Reporting">
227 These columns report the types and versions of the hardware and
228 software running Open vSwitch. We recommend in general that software
229 should test whether specific features are supported instead of relying
230 on version number checks. These values are primarily intended for
231 reporting to human administrators.
234 <column name="ovs_version">
235 The Open vSwitch version number, e.g. <code>1.1.0</code>.
238 <column name="db_version">
240 The database schema version number in the form
241 <code><var>major</var>.<var>minor</var>.<var>tweak</var></code>,
242 e.g. <code>1.2.3</code>. Whenever the database schema is changed in
243 a non-backward compatible way (e.g. deleting a column or a table),
244 <var>major</var> is incremented. When the database schema is changed
245 in a backward compatible way (e.g. adding a new column),
246 <var>minor</var> is incremented. When the database schema is changed
247 cosmetically (e.g. reindenting its syntax), <var>tweak</var> is
252 The schema version is part of the database schema, so it can also be
253 retrieved by fetching the schema using the Open vSwitch database
258 <column name="system_type">
260 An identifier for the type of system on top of which Open vSwitch
261 runs, e.g. <code>XenServer</code> or <code>KVM</code>.
264 System integrators are responsible for choosing and setting an
265 appropriate value for this column.
269 <column name="system_version">
271 The version of the system identified by <ref column="system_type"/>,
272 e.g. <code>5.6.100-39265p</code> on XenServer 5.6.100 build 39265.
275 System integrators are responsible for choosing and setting an
276 appropriate value for this column.
282 <group title="Database Configuration">
284 These columns primarily configure the Open vSwitch database
285 (<code>ovsdb-server</code>), not the Open vSwitch switch
286 (<code>ovs-vswitchd</code>). The OVSDB database also uses the <ref
287 column="ssl"/> settings.
291 The Open vSwitch switch does read the database configuration to
292 determine remote IP addresses to which in-band control should apply.
295 <column name="manager_options">
296 Database clients to which the Open vSwitch database server should
297 connect or to which it should listen, along with options for how these
298 connection should be configured. See the <ref table="Manager"/> table
299 for more information.
303 <group title="Common Columns">
304 The overall purpose of these columns is described under <code>Common
305 Columns</code> at the beginning of this document.
307 <column name="other_config"/>
308 <column name="external_ids"/>
312 <table name="Bridge">
314 Configuration for a bridge within an
315 <ref table="Open_vSwitch"/>.
318 A <ref table="Bridge"/> record represents an Ethernet switch with one or
319 more ``ports,'' which are the <ref table="Port"/> records pointed to by
320 the <ref table="Bridge"/>'s <ref column="ports"/> column.
323 <group title="Core Features">
325 Bridge identifier. Should be alphanumeric and no more than about 8
326 bytes long. Must be unique among the names of ports, interfaces, and
330 <column name="ports">
331 Ports included in the bridge.
334 <column name="mirrors">
335 Port mirroring configuration.
338 <column name="netflow">
339 NetFlow configuration.
342 <column name="sflow">
343 sFlow(R) configuration.
346 <column name="ipfix">
350 <column name="flood_vlans">
352 VLAN IDs of VLANs on which MAC address learning should be disabled,
353 so that packets are flooded instead of being sent to specific ports
354 that are believed to contain packets' destination MACs. This should
355 ordinarily be used to disable MAC learning on VLANs used for
356 mirroring (RSPAN VLANs). It may also be useful for debugging.
359 SLB bonding (see the <ref table="Port" column="bond_mode"/> column in
360 the <ref table="Port"/> table) is incompatible with
361 <code>flood_vlans</code>. Consider using another bonding mode or
362 a different type of mirror instead.
367 <group title="OpenFlow Configuration">
368 <column name="controller">
370 OpenFlow controller set. If unset, then no OpenFlow controllers
375 If there are primary controllers, removing all of them clears the
376 flow table. If there are no primary controllers, adding one also
377 clears the flow table. Other changes to the set of controllers, such
378 as adding or removing a service controller, adding another primary
379 controller to supplement an existing primary controller, or removing
380 only one of two primary controllers, have no effect on the flow
385 <column name="flow_tables">
386 Configuration for OpenFlow tables. Each pair maps from an OpenFlow
387 table ID to configuration for that table.
390 <column name="fail_mode">
391 <p>When a controller is configured, it is, ordinarily, responsible
392 for setting up all flows on the switch. Thus, if the connection to
393 the controller fails, no new network connections can be set up.
394 If the connection to the controller stays down long enough,
395 no packets can pass through the switch at all. This setting
396 determines the switch's response to such a situation. It may be set
397 to one of the following:
399 <dt><code>standalone</code></dt>
400 <dd>If no message is received from the controller for three
401 times the inactivity probe interval
402 (see <ref column="inactivity_probe"/>), then Open vSwitch
403 will take over responsibility for setting up flows. In
404 this mode, Open vSwitch causes the bridge to act like an
405 ordinary MAC-learning switch. Open vSwitch will continue
406 to retry connecting to the controller in the background
407 and, when the connection succeeds, it will discontinue its
408 standalone behavior.</dd>
409 <dt><code>secure</code></dt>
410 <dd>Open vSwitch will not set up flows on its own when the
411 controller connection fails or when no controllers are
412 defined. The bridge will continue to retry connecting to
413 any defined controllers forever.</dd>
417 The default is <code>standalone</code> if the value is unset, but
418 future versions of Open vSwitch may change the default.
421 The <code>standalone</code> mode can create forwarding loops on a
422 bridge that has more than one uplink port unless STP is enabled. To
423 avoid loops on such a bridge, configure <code>secure</code> mode or
424 enable STP (see <ref column="stp_enable"/>).
426 <p>When more than one controller is configured,
427 <ref column="fail_mode"/> is considered only when none of the
428 configured controllers can be contacted.</p>
430 Changing <ref column="fail_mode"/> when no primary controllers are
431 configured clears the flow table.
435 <column name="datapath_id">
436 Reports the OpenFlow datapath ID in use. Exactly 16 hex digits.
437 (Setting this column has no useful effect. Set <ref
438 column="other-config" key="datapath-id"/> instead.)
441 <column name="other_config" key="datapath-id">
442 Exactly 16 hex digits to set the OpenFlow datapath ID to a specific
443 value. May not be all-zero.
446 <column name="other_config" key="dp-desc">
447 Human readable description of datapath. It it a maximum 256
448 byte-long free-form string to describe the datapath for
449 debugging purposes, e.g. <code>switch3 in room 3120</code>.
452 <column name="other_config" key="disable-in-band"
453 type='{"type": "boolean"}'>
454 If set to <code>true</code>, disable in-band control on the bridge
455 regardless of controller and manager settings.
458 <column name="other_config" key="in-band-queue"
459 type='{"type": "integer", "minInteger": 0, "maxInteger": 4294967295}'>
460 A queue ID as a nonnegative integer. This sets the OpenFlow queue ID
461 that will be used by flows set up by in-band control on this bridge.
462 If unset, or if the port used by an in-band control flow does not have
463 QoS configured, or if the port does not have a queue with the specified
464 ID, the default queue is used instead.
467 <column name="protocols">
468 List of OpenFlow protocols that may be used when negotiating a
469 connection with a controller. A default value of
470 <code>OpenFlow10</code> will be used if this column is empty.
474 <group title="Spanning Tree Configuration">
475 The IEEE 802.1D Spanning Tree Protocol (STP) is a network protocol
476 that ensures loop-free topologies. It allows redundant links to
477 be included in the network to provide automatic backup paths if
478 the active links fails.
480 <column name="stp_enable">
481 Enable spanning tree on the bridge. By default, STP is disabled
482 on bridges. Bond, internal, and mirror ports are not supported
483 and will not participate in the spanning tree.
486 <column name="other_config" key="stp-system-id">
487 The bridge's STP identifier (the lower 48 bits of the bridge-id)
489 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>.
490 By default, the identifier is the MAC address of the bridge.
493 <column name="other_config" key="stp-priority"
494 type='{"type": "integer", "minInteger": 0, "maxInteger": 65535}'>
495 The bridge's relative priority value for determining the root
496 bridge (the upper 16 bits of the bridge-id). A bridge with the
497 lowest bridge-id is elected the root. By default, the priority
501 <column name="other_config" key="stp-hello-time"
502 type='{"type": "integer", "minInteger": 1, "maxInteger": 10}'>
503 The interval between transmissions of hello messages by
504 designated ports, in seconds. By default the hello interval is
508 <column name="other_config" key="stp-max-age"
509 type='{"type": "integer", "minInteger": 6, "maxInteger": 40}'>
510 The maximum age of the information transmitted by the bridge
511 when it is the root bridge, in seconds. By default, the maximum
515 <column name="other_config" key="stp-forward-delay"
516 type='{"type": "integer", "minInteger": 4, "maxInteger": 30}'>
517 The delay to wait between transitioning root and designated
518 ports to <code>forwarding</code>, in seconds. By default, the
519 forwarding delay is 15 seconds.
523 <group title="Other Features">
524 <column name="datapath_type">
525 Name of datapath provider. The kernel datapath has
526 type <code>system</code>. The userspace datapath has
527 type <code>netdev</code>.
530 <column name="external_ids" key="bridge-id">
531 A unique identifier of the bridge. On Citrix XenServer this will
532 commonly be the same as
533 <ref column="external_ids" key="xs-network-uuids"/>.
536 <column name="external_ids" key="xs-network-uuids">
537 Semicolon-delimited set of universally unique identifier(s) for the
538 network with which this bridge is associated on a Citrix XenServer
539 host. The network identifiers are RFC 4122 UUIDs as displayed by,
540 e.g., <code>xe network-list</code>.
543 <column name="other_config" key="hwaddr">
544 An Ethernet address in the form
545 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>
546 to set the hardware address of the local port and influence the
550 <column name="other_config" key="flow-eviction-threshold"
551 type='{"type": "integer", "minInteger": 0}'>
553 A number of flows as a nonnegative integer. This sets number of
554 flows at which eviction from the kernel flow table will be triggered.
555 If there are a large number of flows then increasing this value to
556 around the number of flows present can result in reduced CPU usage
560 The default is 1000. Values below 100 will be rounded up to 100.
564 <column name="other_config" key="forward-bpdu"
565 type='{"type": "boolean"}'>
566 Option to allow forwarding of BPDU frames when NORMAL action is
567 invoked. Frames with reserved Ethernet addresses (e.g. STP
568 BPDU) will be forwarded when this option is enabled and the
569 switch is not providing that functionality. If STP is enabled
570 on the port, STP BPDUs will never be forwarded. If the Open
571 vSwitch bridge is used to connect different Ethernet networks,
572 and if Open vSwitch node does not run STP, then this option
573 should be enabled. Default is disabled, set to
574 <code>true</code> to enable.
576 The following destination MAC addresss will not be forwarded when this
579 <dt><code>01:80:c2:00:00:00</code></dt>
580 <dd>IEEE 802.1D Spanning Tree Protocol (STP).</dd>
582 <dt><code>01:80:c2:00:00:01</code></dt>
583 <dd>IEEE Pause frame.</dd>
585 <dt><code>01:80:c2:00:00:0<var>x</var></code></dt>
586 <dd>Other reserved protocols.</dd>
588 <dt><code>00:e0:2b:00:00:00</code></dt>
589 <dd>Extreme Discovery Protocol (EDP).</dd>
592 <code>00:e0:2b:00:00:04</code> and <code>00:e0:2b:00:00:06</code>
594 <dd>Ethernet Automatic Protection Switching (EAPS).</dd>
596 <dt><code>01:00:0c:cc:cc:cc</code></dt>
598 Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP),
599 Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAgP),
603 <dt><code>01:00:0c:cc:cc:cd</code></dt>
604 <dd>Cisco Shared Spanning Tree Protocol PVSTP+.</dd>
606 <dt><code>01:00:0c:cd:cd:cd</code></dt>
607 <dd>Cisco STP Uplink Fast.</dd>
609 <dt><code>01:00:0c:00:00:00</code></dt>
610 <dd>Cisco Inter Switch Link.</dd>
612 <dt><code>01:00:0c:cc:cc:c<var>x</var></code></dt>
617 <column name="other_config" key="mac-aging-time"
618 type='{"type": "integer", "minInteger": 1}'>
620 The maximum number of seconds to retain a MAC learning entry for
621 which no packets have been seen. The default is currently 300
622 seconds (5 minutes). The value, if specified, is forced into a
623 reasonable range, currently 15 to 3600 seconds.
627 A short MAC aging time allows a network to more quickly detect that a
628 host is no longer connected to a switch port. However, it also makes
629 it more likely that packets will be flooded unnecessarily, when they
630 are addressed to a connected host that rarely transmits packets. To
631 reduce the incidence of unnecessary flooding, use a MAC aging time
632 longer than the maximum interval at which a host will ordinarily
637 <column name="other_config" key="mac-table-size"
638 type='{"type": "integer", "minInteger": 1}'>
640 The maximum number of MAC addresses to learn. The default is
641 currently 2048. The value, if specified, is forced into a reasonable
642 range, currently 10 to 1,000,000.
647 <group title="Bridge Status">
649 Status information about bridges.
651 <column name="status">
652 Key-value pairs that report bridge status.
654 <column name="status" key="stp_bridge_id">
656 The bridge-id (in hex) used in spanning tree advertisements.
657 Configuring the bridge-id is described in the
658 <code>stp-system-id</code> and <code>stp-priority</code> keys
659 of the <code>other_config</code> section earlier.
662 <column name="status" key="stp_designated_root">
664 The designated root (in hex) for this spanning tree.
667 <column name="status" key="stp_root_path_cost">
669 The path cost of reaching the designated bridge. A lower
675 <group title="Common Columns">
676 The overall purpose of these columns is described under <code>Common
677 Columns</code> at the beginning of this document.
679 <column name="other_config"/>
680 <column name="external_ids"/>
684 <table name="Port" table="Port or bond configuration.">
685 <p>A port within a <ref table="Bridge"/>.</p>
686 <p>Most commonly, a port has exactly one ``interface,'' pointed to by its
687 <ref column="interfaces"/> column. Such a port logically
688 corresponds to a port on a physical Ethernet switch. A port
689 with more than one interface is a ``bonded port'' (see
690 <ref group="Bonding Configuration"/>).</p>
691 <p>Some properties that one might think as belonging to a port are actually
692 part of the port's <ref table="Interface"/> members.</p>
695 Port name. Should be alphanumeric and no more than about 8
696 bytes long. May be the same as the interface name, for
697 non-bonded ports. Must otherwise be unique among the names of
698 ports, interfaces, and bridges on a host.
701 <column name="interfaces">
702 The port's interfaces. If there is more than one, this is a
706 <group title="VLAN Configuration">
707 <p>Bridge ports support the following types of VLAN configuration:</p>
712 A trunk port carries packets on one or more specified VLANs
713 specified in the <ref column="trunks"/> column (often, on every
714 VLAN). A packet that ingresses on a trunk port is in the VLAN
715 specified in its 802.1Q header, or VLAN 0 if the packet has no
716 802.1Q header. A packet that egresses through a trunk port will
717 have an 802.1Q header if it has a nonzero VLAN ID.
721 Any packet that ingresses on a trunk port tagged with a VLAN that
722 the port does not trunk is dropped.
729 An access port carries packets on exactly one VLAN specified in the
730 <ref column="tag"/> column. Packets egressing on an access port
731 have no 802.1Q header.
735 Any packet with an 802.1Q header with a nonzero VLAN ID that
736 ingresses on an access port is dropped, regardless of whether the
737 VLAN ID in the header is the access port's VLAN ID.
741 <dt>native-tagged</dt>
743 A native-tagged port resembles a trunk port, with the exception that
744 a packet without an 802.1Q header that ingresses on a native-tagged
745 port is in the ``native VLAN'' (specified in the <ref column="tag"/>
749 <dt>native-untagged</dt>
751 A native-untagged port resembles a native-tagged port, with the
752 exception that a packet that egresses on a native-untagged port in
753 the native VLAN will not have an 802.1Q header.
757 A packet will only egress through bridge ports that carry the VLAN of
758 the packet, as described by the rules above.
761 <column name="vlan_mode">
763 The VLAN mode of the port, as described above. When this column is
764 empty, a default mode is selected as follows:
768 If <ref column="tag"/> contains a value, the port is an access
769 port. The <ref column="trunks"/> column should be empty.
772 Otherwise, the port is a trunk port. The <ref column="trunks"/>
773 column value is honored if it is present.
780 For an access port, the port's implicitly tagged VLAN. For a
781 native-tagged or native-untagged port, the port's native VLAN. Must
782 be empty if this is a trunk port.
786 <column name="trunks">
788 For a trunk, native-tagged, or native-untagged port, the 802.1Q VLAN
789 or VLANs that this port trunks; if it is empty, then the port trunks
790 all VLANs. Must be empty if this is an access port.
793 A native-tagged or native-untagged port always trunks its native
794 VLAN, regardless of whether <ref column="trunks"/> includes that
799 <column name="other_config" key="priority-tags"
800 type='{"type": "boolean"}'>
802 An 802.1Q header contains two important pieces of information: a VLAN
803 ID and a priority. A frame with a zero VLAN ID, called a
804 ``priority-tagged'' frame, is supposed to be treated the same way as
805 a frame without an 802.1Q header at all (except for the priority).
809 However, some network elements ignore any frame that has 802.1Q
810 header at all, even when the VLAN ID is zero. Therefore, by default
811 Open vSwitch does not output priority-tagged frames, instead omitting
812 the 802.1Q header entirely if the VLAN ID is zero. Set this key to
813 <code>true</code> to enable priority-tagged frames on a port.
817 Regardless of this setting, Open vSwitch omits the 802.1Q header on
818 output if both the VLAN ID and priority would be zero.
822 All frames output to native-tagged ports have a nonzero VLAN ID, so
823 this setting is not meaningful on native-tagged ports.
828 <group title="Bonding Configuration">
829 <p>A port that has more than one interface is a ``bonded port.'' Bonding
830 allows for load balancing and fail-over.</p>
833 The following types of bonding will work with any kind of upstream
834 switch. On the upstream switch, do not configure the interfaces as a
839 <dt><code>balance-slb</code></dt>
841 Balances flows among slaves based on source MAC address and output
842 VLAN, with periodic rebalancing as traffic patterns change.
845 <dt><code>active-backup</code></dt>
847 Assigns all flows to one slave, failing over to a backup slave when
848 the active slave is disabled. This is the only bonding mode in which
849 interfaces may be plugged into different upstream switches.
854 The following modes require the upstream switch to support 802.3ad with
855 successful LACP negotiation:
859 <dt><code>balance-tcp</code></dt>
861 Balances flows among slaves based on L2, L3, and L4 protocol
862 information such as destination MAC address, IP address, and TCP
867 <p>These columns apply only to bonded ports. Their values are
868 otherwise ignored.</p>
870 <column name="bond_mode">
871 <p>The type of bonding used for a bonded port. Defaults to
872 <code>active-backup</code> if unset.
876 <column name="other_config" key="bond-hash-basis"
877 type='{"type": "integer"}'>
878 An integer hashed along with flows when choosing output slaves in load
879 balanced bonds. When changed, all flows will be assigned different
880 hash values possibly causing slave selection decisions to change. Does
881 not affect bonding modes which do not employ load balancing such as
882 <code>active-backup</code>.
885 <group title="Link Failure Detection">
887 An important part of link bonding is detecting that links are down so
888 that they may be disabled. These settings determine how Open vSwitch
889 detects link failure.
892 <column name="other_config" key="bond-detect-mode"
893 type='{"type": "string", "enum": ["set", ["carrier", "miimon"]]}'>
894 The means used to detect link failures. Defaults to
895 <code>carrier</code> which uses each interface's carrier to detect
896 failures. When set to <code>miimon</code>, will check for failures
897 by polling each interface's MII.
900 <column name="other_config" key="bond-miimon-interval"
901 type='{"type": "integer"}'>
902 The interval, in milliseconds, between successive attempts to poll
903 each interface's MII. Relevant only when <ref column="other_config"
904 key="bond-detect-mode"/> is <code>miimon</code>.
907 <column name="bond_updelay">
909 The number of milliseconds for which the link must stay up on an
910 interface before the interface is considered to be up. Specify
911 <code>0</code> to enable the interface immediately.
915 This setting is honored only when at least one bonded interface is
916 already enabled. When no interfaces are enabled, then the first
917 bond interface to come up is enabled immediately.
921 <column name="bond_downdelay">
922 The number of milliseconds for which the link must stay down on an
923 interface before the interface is considered to be down. Specify
924 <code>0</code> to disable the interface immediately.
928 <group title="LACP Configuration">
930 LACP, the Link Aggregation Control Protocol, is an IEEE standard that
931 allows switches to automatically detect that they are connected by
932 multiple links and aggregate across those links. These settings
933 control LACP behavior.
937 Configures LACP on this port. LACP allows directly connected
938 switches to negotiate which links may be bonded. LACP may be enabled
939 on non-bonded ports for the benefit of any switches they may be
940 connected to. <code>active</code> ports are allowed to initiate LACP
941 negotiations. <code>passive</code> ports are allowed to participate
942 in LACP negotiations initiated by a remote switch, but not allowed to
943 initiate such negotiations themselves. If LACP is enabled on a port
944 whose partner switch does not support LACP, the bond will be
945 disabled. Defaults to <code>off</code> if unset.
948 <column name="other_config" key="lacp-system-id">
949 The LACP system ID of this <ref table="Port"/>. The system ID of a
950 LACP bond is used to identify itself to its partners. Must be a
951 nonzero MAC address. Defaults to the bridge Ethernet address if
955 <column name="other_config" key="lacp-system-priority"
956 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
957 The LACP system priority of this <ref table="Port"/>. In LACP
958 negotiations, link status decisions are made by the system with the
959 numerically lower priority.
962 <column name="other_config" key="lacp-time"
963 type='{"type": "string", "enum": ["set", ["fast", "slow"]]}'>
965 The LACP timing which should be used on this <ref table="Port"/>.
966 By default <code>slow</code> is used. When configured to be
967 <code>fast</code> LACP heartbeats are requested at a rate of once
968 per second causing connectivity problems to be detected more
969 quickly. In <code>slow</code> mode, heartbeats are requested at a
970 rate of once every 30 seconds.
975 <group title="Rebalancing Configuration">
977 These settings control behavior when a bond is in
978 <code>balance-slb</code> or <code>balance-tcp</code> mode.
981 <column name="other_config" key="bond-rebalance-interval"
982 type='{"type": "integer", "minInteger": 0, "maxInteger": 10000}'>
983 For a load balanced bonded port, the number of milliseconds between
984 successive attempts to rebalance the bond, that is, to move flows
985 from one interface on the bond to another in an attempt to keep usage
986 of each interface roughly equal. If zero, load balancing is disabled
987 on the bond (link failure still cause flows to move). If
988 less than 1000ms, the rebalance interval will be 1000ms.
992 <column name="bond_fake_iface">
993 For a bonded port, whether to create a fake internal interface with the
994 name of the port. Use only for compatibility with legacy software that
999 <group title="Spanning Tree Configuration">
1000 <column name="other_config" key="stp-enable"
1001 type='{"type": "boolean"}'>
1002 If spanning tree is enabled on the bridge, member ports are
1003 enabled by default (with the exception of bond, internal, and
1004 mirror ports which do not work with STP). If this column's
1005 value is <code>false</code> spanning tree is disabled on the
1009 <column name="other_config" key="stp-port-num"
1010 type='{"type": "integer", "minInteger": 1, "maxInteger": 255}'>
1011 The port number used for the lower 8 bits of the port-id. By
1012 default, the numbers will be assigned automatically. If any
1013 port's number is manually configured on a bridge, then they
1017 <column name="other_config" key="stp-port-priority"
1018 type='{"type": "integer", "minInteger": 0, "maxInteger": 255}'>
1019 The port's relative priority value for determining the root
1020 port (the upper 8 bits of the port-id). A port with a lower
1021 port-id will be chosen as the root port. By default, the
1025 <column name="other_config" key="stp-path-cost"
1026 type='{"type": "integer", "minInteger": 0, "maxInteger": 65535}'>
1027 Spanning tree path cost for the port. A lower number indicates
1028 a faster link. By default, the cost is based on the maximum
1033 <group title="Other Features">
1035 Quality of Service configuration for this port.
1039 The MAC address to use for this port for the purpose of choosing the
1040 bridge's MAC address. This column does not necessarily reflect the
1041 port's actual MAC address, nor will setting it change the port's actual
1045 <column name="fake_bridge">
1046 Does this port represent a sub-bridge for its tagged VLAN within the
1047 Bridge? See ovs-vsctl(8) for more information.
1050 <column name="external_ids" key="fake-bridge-id-*">
1051 External IDs for a fake bridge (see the <ref column="fake_bridge"/>
1052 column) are defined by prefixing a <ref table="Bridge"/> <ref
1053 table="Bridge" column="external_ids"/> key with
1054 <code>fake-bridge-</code>,
1055 e.g. <code>fake-bridge-xs-network-uuids</code>.
1059 <group title="Port Status">
1061 Status information about ports attached to bridges.
1063 <column name="status">
1064 Key-value pairs that report port status.
1066 <column name="status" key="stp_port_id">
1068 The port-id (in hex) used in spanning tree advertisements for
1069 this port. Configuring the port-id is described in the
1070 <code>stp-port-num</code> and <code>stp-port-priority</code>
1071 keys of the <code>other_config</code> section earlier.
1074 <column name="status" key="stp_state"
1075 type='{"type": "string", "enum": ["set",
1076 ["disabled", "listening", "learning",
1077 "forwarding", "blocking"]]}'>
1079 STP state of the port.
1082 <column name="status" key="stp_sec_in_state"
1083 type='{"type": "integer", "minInteger": 0}'>
1085 The amount of time (in seconds) port has been in the current
1089 <column name="status" key="stp_role"
1090 type='{"type": "string", "enum": ["set",
1091 ["root", "designated", "alternate"]]}'>
1093 STP role of the port.
1098 <group title="Port Statistics">
1100 Key-value pairs that report port statistics.
1102 <group title="Statistics: STP transmit and receive counters">
1103 <column name="statistics" key="stp_tx_count">
1104 Number of STP BPDUs sent on this port by the spanning
1107 <column name="statistics" key="stp_rx_count">
1108 Number of STP BPDUs received on this port and accepted by the
1109 spanning tree library.
1111 <column name="statistics" key="stp_error_count">
1112 Number of bad STP BPDUs received on this port. Bad BPDUs
1113 include runt packets and those with an unexpected protocol ID.
1118 <group title="Common Columns">
1119 The overall purpose of these columns is described under <code>Common
1120 Columns</code> at the beginning of this document.
1122 <column name="other_config"/>
1123 <column name="external_ids"/>
1127 <table name="Interface" title="One physical network device in a Port.">
1128 An interface within a <ref table="Port"/>.
1130 <group title="Core Features">
1131 <column name="name">
1132 Interface name. Should be alphanumeric and no more than about 8 bytes
1133 long. May be the same as the port name, for non-bonded ports. Must
1134 otherwise be unique among the names of ports, interfaces, and bridges
1138 <column name="mac_in_use">
1139 The MAC address in use by this interface.
1143 <p>Ethernet address to set for this interface. If unset then the
1144 default MAC address is used:</p>
1146 <li>For the local interface, the default is the lowest-numbered MAC
1147 address among the other bridge ports, either the value of the
1148 <ref table="Port" column="mac"/> in its <ref table="Port"/> record,
1149 if set, or its actual MAC (for bonded ports, the MAC of its slave
1150 whose name is first in alphabetical order). Internal ports and
1151 bridge ports that are used as port mirroring destinations (see the
1152 <ref table="Mirror"/> table) are ignored.</li>
1153 <li>For other internal interfaces, the default MAC is randomly
1155 <li>External interfaces typically have a MAC address associated with
1156 their hardware.</li>
1158 <p>Some interfaces may not have a software-controllable MAC
1162 <column name="ofport">
1163 <p>OpenFlow port number for this interface. Unlike most columns, this
1164 column's value should be set only by Open vSwitch itself. Other
1165 clients should set this column to an empty set (the default) when
1166 creating an <ref table="Interface"/>.</p>
1167 <p>Open vSwitch populates this column when the port number becomes
1168 known. If the interface is successfully added,
1169 <ref column="ofport"/> will be set to a number between 1 and 65535
1170 (generally either in the range 1 to 65279, inclusive, or 65534, the
1171 port number for the OpenFlow ``local port''). If the interface
1172 cannot be added then Open vSwitch sets this column
1174 <p>When <ref column="ofport_request"/> is not set, Open vSwitch picks
1175 an appropriate value for this column and then tries to keep the value
1176 constant across restarts.</p>
1179 <column name="ofport_request">
1180 <p>Requested OpenFlow port number for this interface. The port
1181 number must be between 1 and 65279, inclusive. Some datapaths
1182 cannot satisfy all requests for particular port numbers. When
1183 this column is empty or the request cannot be fulfilled, the
1184 system will choose a free port. The <ref column="ofport"/>
1185 column reports the assigned OpenFlow port number.</p>
1186 <p>The port number must be requested in the same transaction
1187 that creates the port.</p>
1191 <group title="System-Specific Details">
1192 <column name="type">
1194 The interface type, one of:
1198 <dt><code>system</code></dt>
1199 <dd>An ordinary network device, e.g. <code>eth0</code> on Linux.
1200 Sometimes referred to as ``external interfaces'' since they are
1201 generally connected to hardware external to that on which the Open
1202 vSwitch is running. The empty string is a synonym for
1203 <code>system</code>.</dd>
1205 <dt><code>internal</code></dt>
1206 <dd>A simulated network device that sends and receives traffic. An
1207 internal interface whose <ref column="name"/> is the same as its
1208 bridge's <ref table="Open_vSwitch" column="name"/> is called the
1209 ``local interface.'' It does not make sense to bond an internal
1210 interface, so the terms ``port'' and ``interface'' are often used
1211 imprecisely for internal interfaces.</dd>
1213 <dt><code>tap</code></dt>
1214 <dd>A TUN/TAP device managed by Open vSwitch.</dd>
1216 <dt><code>gre</code></dt>
1218 An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4
1222 <dt><code>ipsec_gre</code></dt>
1224 An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4
1228 <dt><code>gre64</code></dt>
1230 It is same as GRE, but it allows 64 bit key. To store higher 32-bits
1231 of key, it uses GRE protocol sequence number field. This is non
1232 standard use of GRE protocol since OVS does not increment
1233 sequence number for every packet at time of encap as expected by
1234 standard GRE implementation. See <ref group="Tunnel Options"/>
1235 for information on configuring GRE tunnels.
1238 <dt><code>ipsec_gre64</code></dt>
1240 Same as IPSEC_GRE except 64 bit key.
1243 <dt><code>vxlan</code></dt>
1246 An Ethernet tunnel over the experimental, UDP-based VXLAN
1247 protocol described at
1248 <code>http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-03</code>.
1249 VXLAN is currently supported only with the Linux kernel datapath
1250 with kernel version 2.6.26 or later.
1253 Open vSwitch uses UDP destination port 4789. The source port used for
1254 VXLAN traffic varies on a per-flow basis and is in the ephemeral port
1259 <dt><code>lisp</code></dt>
1261 A layer 3 tunnel over the experimental, UDP-based Locator/ID
1262 Separation Protocol (RFC 6830). LISP is currently supported only
1263 with the Linux kernel datapath with kernel version 2.6.26 or later.
1266 <dt><code>patch</code></dt>
1268 A pair of virtual devices that act as a patch cable.
1271 <dt><code>null</code></dt>
1272 <dd>An ignored interface. Deprecated and slated for removal in
1278 <group title="Tunnel Options">
1280 These options apply to interfaces with <ref column="type"/> of
1281 <code>gre</code>, <code>ipsec_gre</code>, <code>gre64</code>,
1282 <code>ipsec_gre64</code>, <code>vxlan</code>, and <code>lisp</code>.
1286 Each tunnel must be uniquely identified by the combination of <ref
1287 column="type"/>, <ref column="options" key="remote_ip"/>, <ref
1288 column="options" key="local_ip"/>, and <ref column="options"
1289 key="in_key"/>. If two ports are defined that are the same except one
1290 has an optional identifier and the other does not, the more specific
1291 one is matched first. <ref column="options" key="in_key"/> is
1292 considered more specific than <ref column="options" key="local_ip"/> if
1293 a port defines one and another port defines the other.
1296 <column name="options" key="remote_ip">
1297 Required. The tunnel endpoint. Only unicast endpoints are supported.
1300 <column name="options" key="local_ip">
1301 Optional. The destination IP that received packets must match.
1302 Default is to match all addresses.
1305 <column name="options" key="in_key">
1306 <p>Optional. The key that received packets must contain, one of:</p>
1310 <code>0</code>. The tunnel receives packets with no key or with a
1311 key of 0. This is equivalent to specifying no <ref column="options"
1312 key="in_key"/> at all.
1315 A positive 24-bit (for VXLAN and LISP), 32-bit (for GRE) or 64-bit
1316 (for GRE64) number. The tunnel receives only packets with the
1320 The word <code>flow</code>. The tunnel accepts packets with any
1321 key. The key will be placed in the <code>tun_id</code> field for
1322 matching in the flow table. The <code>ovs-ofctl</code> manual page
1323 contains additional information about matching fields in OpenFlow
1332 <column name="options" key="out_key">
1333 <p>Optional. The key to be set on outgoing packets, one of:</p>
1337 <code>0</code>. Packets sent through the tunnel will have no key.
1338 This is equivalent to specifying no <ref column="options"
1339 key="out_key"/> at all.
1342 A positive 24-bit (for VXLAN and LISP), 32-bit (for GRE) or 64-bit
1343 (for GRE64) number. Packets sent through the tunnel will have the
1347 The word <code>flow</code>. Packets sent through the tunnel will
1348 have the key set using the <code>set_tunnel</code> Nicira OpenFlow
1349 vendor extension (0 is used in the absence of an action). The
1350 <code>ovs-ofctl</code> manual page contains additional information
1351 about the Nicira OpenFlow vendor extensions.
1356 <column name="options" key="key">
1357 Optional. Shorthand to set <code>in_key</code> and
1358 <code>out_key</code> at the same time.
1361 <column name="options" key="tos">
1362 Optional. The value of the ToS bits to be set on the encapsulating
1363 packet. ToS is interpreted as DSCP and ECN bits, ECN part must be
1364 zero. It may also be the word <code>inherit</code>, in which case
1365 the ToS will be copied from the inner packet if it is IPv4 or IPv6
1366 (otherwise it will be 0). The ECN fields are always inherited.
1370 <column name="options" key="ttl">
1371 Optional. The TTL to be set on the encapsulating packet. It may also
1372 be the word <code>inherit</code>, in which case the TTL will be copied
1373 from the inner packet if it is IPv4 or IPv6 (otherwise it will be the
1374 system default, typically 64). Default is the system default TTL.
1377 <column name="options" key="df_default"
1378 type='{"type": "boolean"}'>
1379 Optional. If enabled, the Don't Fragment bit will be set on tunnel
1380 outer headers to allow path MTU discovery. Default is enabled; set
1381 to <code>false</code> to disable.
1384 <group title="Tunnel Options: gre and ipsec_gre only">
1386 Only <code>gre</code> and <code>ipsec_gre</code> interfaces support
1390 <column name="options" key="csum" type='{"type": "boolean"}'>
1392 Optional. Compute GRE checksums on outgoing packets. Default is
1393 disabled, set to <code>true</code> to enable. Checksums present on
1394 incoming packets will be validated regardless of this setting.
1398 GRE checksums impose a significant performance penalty because they
1399 cover the entire packet. The encapsulated L3, L4, and L7 packet
1400 contents typically have their own checksums, so this additional
1401 checksum only adds value for the GRE and encapsulated L2 headers.
1405 This option is supported for <code>ipsec_gre</code>, but not useful
1406 because GRE checksums are weaker than, and redundant with, IPsec
1407 payload authentication.
1412 <group title="Tunnel Options: ipsec_gre only">
1414 Only <code>ipsec_gre</code> interfaces support these options.
1417 <column name="options" key="peer_cert">
1418 Required for certificate authentication. A string containing the
1419 peer's certificate in PEM format. Additionally the host's
1420 certificate must be specified with the <code>certificate</code>
1424 <column name="options" key="certificate">
1425 Required for certificate authentication. The name of a PEM file
1426 containing a certificate that will be presented to the peer during
1430 <column name="options" key="private_key">
1431 Optional for certificate authentication. The name of a PEM file
1432 containing the private key associated with <code>certificate</code>.
1433 If <code>certificate</code> contains the private key, this option may
1437 <column name="options" key="psk">
1438 Required for pre-shared key authentication. Specifies a pre-shared
1439 key for authentication that must be identical on both sides of the
1445 <group title="Patch Options">
1447 Only <code>patch</code> interfaces support these options.
1450 <column name="options" key="peer">
1451 The <ref column="name"/> of the <ref table="Interface"/> for the other
1452 side of the patch. The named <ref table="Interface"/>'s own
1453 <code>peer</code> option must specify this <ref table="Interface"/>'s
1454 name. That is, the two patch interfaces must have reversed <ref
1455 column="name"/> and <code>peer</code> values.
1459 <group title="Interface Status">
1461 Status information about interfaces attached to bridges, updated every
1462 5 seconds. Not all interfaces have all of these properties; virtual
1463 interfaces don't have a link speed, for example. Non-applicable
1464 columns will have empty values.
1466 <column name="admin_state">
1468 The administrative state of the physical network link.
1472 <column name="link_state">
1474 The observed state of the physical network link. This is ordinarily
1475 the link's carrier status. If the interface's <ref table="Port"/> is
1476 a bond configured for miimon monitoring, it is instead the network
1477 link's miimon status.
1481 <column name="link_resets">
1483 The number of times Open vSwitch has observed the
1484 <ref column="link_state"/> of this <ref table="Interface"/> change.
1488 <column name="link_speed">
1490 The negotiated speed of the physical network link.
1491 Valid values are positive integers greater than 0.
1495 <column name="duplex">
1497 The duplex mode of the physical network link.
1503 The MTU (maximum transmission unit); i.e. the largest
1504 amount of data that can fit into a single Ethernet frame.
1505 The standard Ethernet MTU is 1500 bytes. Some physical media
1506 and many kinds of virtual interfaces can be configured with
1510 This column will be empty for an interface that does not
1511 have an MTU as, for example, some kinds of tunnels do not.
1515 <column name="lacp_current">
1516 Boolean value indicating LACP status for this interface. If true, this
1517 interface has current LACP information about its LACP partner. This
1518 information may be used to monitor the health of interfaces in a LACP
1519 enabled port. This column will be empty if LACP is not enabled.
1522 <column name="status">
1523 Key-value pairs that report port status. Supported status values are
1524 <ref column="type"/>-dependent; some interfaces may not have a valid
1525 <ref column="status" key="driver_name"/>, for example.
1528 <column name="status" key="driver_name">
1529 The name of the device driver controlling the network adapter.
1532 <column name="status" key="driver_version">
1533 The version string of the device driver controlling the network
1537 <column name="status" key="firmware_version">
1538 The version string of the network adapter's firmware, if available.
1541 <column name="status" key="source_ip">
1542 The source IP address used for an IPv4 tunnel end-point, such as
1546 <column name="status" key="tunnel_egress_iface">
1547 Egress interface for tunnels. Currently only relevant for GRE tunnels
1548 On Linux systems, this column will show the name of the interface
1549 which is responsible for routing traffic destined for the configured
1550 <ref column="options" key="remote_ip"/>. This could be an internal
1551 interface such as a bridge port.
1554 <column name="status" key="tunnel_egress_iface_carrier"
1555 type='{"type": "string", "enum": ["set", ["down", "up"]]}'>
1556 Whether carrier is detected on <ref column="status"
1557 key="tunnel_egress_iface"/>.
1561 <group title="Statistics">
1563 Key-value pairs that report interface statistics. The current
1564 implementation updates these counters periodically. Future
1565 implementations may update them when an interface is created, when they
1566 are queried (e.g. using an OVSDB <code>select</code> operation), and
1567 just before an interface is deleted due to virtual interface hot-unplug
1568 or VM shutdown, and perhaps at other times, but not on any regular
1572 These are the same statistics reported by OpenFlow in its <code>struct
1573 ofp_port_stats</code> structure. If an interface does not support a
1574 given statistic, then that pair is omitted.
1576 <group title="Statistics: Successful transmit and receive counters">
1577 <column name="statistics" key="rx_packets">
1578 Number of received packets.
1580 <column name="statistics" key="rx_bytes">
1581 Number of received bytes.
1583 <column name="statistics" key="tx_packets">
1584 Number of transmitted packets.
1586 <column name="statistics" key="tx_bytes">
1587 Number of transmitted bytes.
1590 <group title="Statistics: Receive errors">
1591 <column name="statistics" key="rx_dropped">
1592 Number of packets dropped by RX.
1594 <column name="statistics" key="rx_frame_err">
1595 Number of frame alignment errors.
1597 <column name="statistics" key="rx_over_err">
1598 Number of packets with RX overrun.
1600 <column name="statistics" key="rx_crc_err">
1601 Number of CRC errors.
1603 <column name="statistics" key="rx_errors">
1604 Total number of receive errors, greater than or equal to the sum of
1608 <group title="Statistics: Transmit errors">
1609 <column name="statistics" key="tx_dropped">
1610 Number of packets dropped by TX.
1612 <column name="statistics" key="collisions">
1613 Number of collisions.
1615 <column name="statistics" key="tx_errors">
1616 Total number of transmit errors, greater than or equal to the sum of
1622 <group title="Ingress Policing">
1624 These settings control ingress policing for packets received on this
1625 interface. On a physical interface, this limits the rate at which
1626 traffic is allowed into the system from the outside; on a virtual
1627 interface (one connected to a virtual machine), this limits the rate at
1628 which the VM is able to transmit.
1631 Policing is a simple form of quality-of-service that simply drops
1632 packets received in excess of the configured rate. Due to its
1633 simplicity, policing is usually less accurate and less effective than
1634 egress QoS (which is configured using the <ref table="QoS"/> and <ref
1635 table="Queue"/> tables).
1638 Policing is currently implemented only on Linux. The Linux
1639 implementation uses a simple ``token bucket'' approach:
1643 The size of the bucket corresponds to <ref
1644 column="ingress_policing_burst"/>. Initially the bucket is full.
1647 Whenever a packet is received, its size (converted to tokens) is
1648 compared to the number of tokens currently in the bucket. If the
1649 required number of tokens are available, they are removed and the
1650 packet is forwarded. Otherwise, the packet is dropped.
1653 Whenever it is not full, the bucket is refilled with tokens at the
1654 rate specified by <ref column="ingress_policing_rate"/>.
1658 Policing interacts badly with some network protocols, and especially
1659 with fragmented IP packets. Suppose that there is enough network
1660 activity to keep the bucket nearly empty all the time. Then this token
1661 bucket algorithm will forward a single packet every so often, with the
1662 period depending on packet size and on the configured rate. All of the
1663 fragments of an IP packets are normally transmitted back-to-back, as a
1664 group. In such a situation, therefore, only one of these fragments
1665 will be forwarded and the rest will be dropped. IP does not provide
1666 any way for the intended recipient to ask for only the remaining
1667 fragments. In such a case there are two likely possibilities for what
1668 will happen next: either all of the fragments will eventually be
1669 retransmitted (as TCP will do), in which case the same problem will
1670 recur, or the sender will not realize that its packet has been dropped
1671 and data will simply be lost (as some UDP-based protocols will do).
1672 Either way, it is possible that no forward progress will ever occur.
1674 <column name="ingress_policing_rate">
1676 Maximum rate for data received on this interface, in kbps. Data
1677 received faster than this rate is dropped. Set to <code>0</code>
1678 (the default) to disable policing.
1682 <column name="ingress_policing_burst">
1683 <p>Maximum burst size for data received on this interface, in kb. The
1684 default burst size if set to <code>0</code> is 1000 kb. This value
1685 has no effect if <ref column="ingress_policing_rate"/>
1686 is <code>0</code>.</p>
1688 Specifying a larger burst size lets the algorithm be more forgiving,
1689 which is important for protocols like TCP that react severely to
1690 dropped packets. The burst size should be at least the size of the
1691 interface's MTU. Specifying a value that is numerically at least as
1692 large as 10% of <ref column="ingress_policing_rate"/> helps TCP come
1693 closer to achieving the full rate.
1698 <group title="Bidirectional Forwarding Detection (BFD)">
1700 BFD, defined in RFC 5880 and RFC 5881, allows point to point
1701 detection of connectivity failures by occasional transmission of
1702 BFD control messages. It is implemented in Open vSwitch to serve
1703 as a more popular and standards compliant alternative to CFM.
1707 BFD operates by regularly transmitting BFD control messages at a
1708 rate negotiated independently in each direction. Each endpoint
1709 specifies the rate at which it expects to receive control messages,
1710 and the rate at which it's willing to transmit them. Open vSwitch
1711 uses a detection multiplier of three, meaning that an endpoint
1712 which fails to receive BFD control messages for a period of three
1713 times the expected reception rate, will signal a connectivity
1714 fault. In the case of a unidirectional connectivity issue, the
1715 system not receiving BFD control messages will signal the problem
1716 to its peer in the messages is transmists.
1720 The Open vSwitch implementation of BFD aims to comply faithfully
1721 with the requirements put forth in RFC 5880. Currently, the only
1722 known omission is ``Demand Mode'', which we hope to include in
1723 future. Open vSwitch does not implement the optional
1724 Authentication or ``Echo Mode'' features.
1727 <column name="bfd" key="enable">
1728 When <code>true</code> BFD is enabled on this
1729 <ref table="Interface"/>, otherwise it's disabled. Defaults to
1733 <column name="bfd" key="min_rx"
1734 type='{"type": "integer", "minInteger": 1}'>
1735 The fastest rate, in milliseconds, at which this BFD session is
1736 willing to receive BFD control messages. The actual rate may be
1737 slower if the remote endpoint isn't willing to transmit as quickly as
1738 specified. Defaults to <code>1000</code>.
1741 <column name="bfd" key="min_tx"
1742 type='{"type": "integer", "minInteger": 1}'>
1743 The fastest rate, in milliseconds, at which this BFD session is
1744 willing to transmit BFD control messages. The actual rate may be
1745 slower if the remote endpoint isn't willing to receive as quickly as
1746 specified. Defaults to <code>100</code>.
1749 <column name="bfd" key="cpath_down" type='{"type": "boolean"}'>
1750 Concatenated path down may be used when the local system should not
1751 have traffic forwarded to it for some reason other than a connectivty
1752 failure on the interface being monitored. When a controller thinks
1753 this may be the case, it may set <code>cpath_down</code> to
1754 <code>true</code> which may cause the remote BFD session not to
1755 forward traffic to this <ref table="Interface"/>. Defaults to
1759 <column name="bfd_status" key="state"
1760 type='{"type": "string",
1761 "enum": ["set", ["admin_down", "down", "init", "up"]]}'>
1762 State of the BFD session. The BFD session is fully healthy and
1763 negotiated if <code>UP</code>.
1766 <column name="bfd_status" key="forwarding" type='{"type": "boolean"}'>
1767 True if the BFD session believes this <ref table="Interface"/> may be
1768 used to forward traffic. Typically this means the local session is
1769 signaling <code>UP</code>, and the remote system isn't signaling a
1770 problem such as concatenated path down.
1773 <column name="bfd_status" key="diagnostic">
1774 A short message indicating what the BFD session thinks is wrong in
1778 <column name="bfd_status" key="remote_state"
1779 type='{"type": "string",
1780 "enum": ["set", ["admin_down", "down", "init", "up"]]}'>
1781 State of the remote endpoint's BFD session.
1784 <column name="bfd_status" key="remote_diagnostic">
1785 A short message indicating what the remote endpoint's BFD session
1786 thinks is wrong in case of a problem.
1790 <group title="Connectivity Fault Management">
1792 802.1ag Connectivity Fault Management (CFM) allows a group of
1793 Maintenance Points (MPs) called a Maintenance Association (MA) to
1794 detect connectivity problems with each other. MPs within a MA should
1795 have complete and exclusive interconnectivity. This is verified by
1796 occasionally broadcasting Continuity Check Messages (CCMs) at a
1797 configurable transmission interval.
1801 According to the 802.1ag specification, each Maintenance Point should
1802 be configured out-of-band with a list of Remote Maintenance Points it
1803 should have connectivity to. Open vSwitch differs from the
1804 specification in this area. It simply assumes the link is faulted if
1805 no Remote Maintenance Points are reachable, and considers it not
1810 When operating over tunnels which have no <code>in_key</code>, or an
1811 <code>in_key</code> of <code>flow</code>. CFM will only accept CCMs
1812 with a tunnel key of zero.
1815 <column name="cfm_mpid">
1816 A Maintenance Point ID (MPID) uniquely identifies each endpoint within
1817 a Maintenance Association. The MPID is used to identify this endpoint
1818 to other Maintenance Points in the MA. Each end of a link being
1819 monitored should have a different MPID. Must be configured to enable
1820 CFM on this <ref table="Interface"/>.
1823 <column name="cfm_fault">
1825 Indicates a connectivity fault triggered by an inability to receive
1826 heartbeats from any remote endpoint. When a fault is triggered on
1827 <ref table="Interface"/>s participating in bonds, they will be
1831 Faults can be triggered for several reasons. Most importantly they
1832 are triggered when no CCMs are received for a period of 3.5 times the
1833 transmission interval. Faults are also triggered when any CCMs
1834 indicate that a Remote Maintenance Point is not receiving CCMs but
1835 able to send them. Finally, a fault is triggered if a CCM is
1836 received which indicates unexpected configuration. Notably, this
1837 case arises when a CCM is received which advertises the local MPID.
1841 <column name="cfm_fault_status" key="recv">
1842 Indicates a CFM fault was triggered due to a lack of CCMs received on
1843 the <ref table="Interface"/>.
1846 <column name="cfm_fault_status" key="rdi">
1847 Indicates a CFM fault was triggered due to the reception of a CCM with
1848 the RDI bit flagged. Endpoints set the RDI bit in their CCMs when they
1849 are not receiving CCMs themselves. This typically indicates a
1850 unidirectional connectivity failure.
1853 <column name="cfm_fault_status" key="maid">
1854 Indicates a CFM fault was triggered due to the reception of a CCM with
1855 a MAID other than the one Open vSwitch uses. CFM broadcasts are tagged
1856 with an identification number in addition to the MPID called the MAID.
1857 Open vSwitch only supports receiving CCM broadcasts tagged with the
1858 MAID it uses internally.
1861 <column name="cfm_fault_status" key="loopback">
1862 Indicates a CFM fault was triggered due to the reception of a CCM
1863 advertising the same MPID configured in the <ref column="cfm_mpid"/>
1864 column of this <ref table="Interface"/>. This may indicate a loop in
1868 <column name="cfm_fault_status" key="overflow">
1869 Indicates a CFM fault was triggered because the CFM module received
1870 CCMs from more remote endpoints than it can keep track of.
1873 <column name="cfm_fault_status" key="override">
1874 Indicates a CFM fault was manually triggered by an administrator using
1875 an <code>ovs-appctl</code> command.
1878 <column name="cfm_fault_status" key="interval">
1879 Indicates a CFM fault was triggered due to the reception of a CCM
1880 frame having an invalid interval.
1883 <column name="cfm_remote_opstate">
1884 <p>When in extended mode, indicates the operational state of the
1885 remote endpoint as either <code>up</code> or <code>down</code>. See
1886 <ref column="other_config" key="cfm_opstate"/>.
1890 <column name="cfm_health">
1892 Indicates the health of the interface as a percentage of CCM frames
1893 received over 21 <ref column="other_config" key="cfm_interval"/>s.
1894 The health of an interface is undefined if it is communicating with
1895 more than one <ref column="cfm_remote_mpids"/>. It reduces if
1896 healthy heartbeats are not received at the expected rate, and
1897 gradually improves as healthy heartbeats are received at the desired
1898 rate. Every 21 <ref column="other_config" key="cfm_interval"/>s, the
1899 health of the interface is refreshed.
1902 As mentioned above, the faults can be triggered for several reasons.
1903 The link health will deteriorate even if heartbeats are received but
1904 they are reported to be unhealthy. An unhealthy heartbeat in this
1905 context is a heartbeat for which either some fault is set or is out
1906 of sequence. The interface health can be 100 only on receiving
1907 healthy heartbeats at the desired rate.
1911 <column name="cfm_remote_mpids">
1912 When CFM is properly configured, Open vSwitch will occasionally
1913 receive CCM broadcasts. These broadcasts contain the MPID of the
1914 sending Maintenance Point. The list of MPIDs from which this
1915 <ref table="Interface"/> is receiving broadcasts from is regularly
1916 collected and written to this column.
1919 <column name="other_config" key="cfm_interval"
1920 type='{"type": "integer"}'>
1922 The interval, in milliseconds, between transmissions of CFM
1923 heartbeats. Three missed heartbeat receptions indicate a
1928 In standard operation only intervals of 3, 10, 100, 1,000, 10,000,
1929 60,000, or 600,000 ms are supported. Other values will be rounded
1930 down to the nearest value on the list. Extended mode (see <ref
1931 column="other_config" key="cfm_extended"/>) supports any interval up
1932 to 65,535 ms. In either mode, the default is 1000 ms.
1935 <p>We do not recommend using intervals less than 100 ms.</p>
1938 <column name="other_config" key="cfm_extended"
1939 type='{"type": "boolean"}'>
1940 When <code>true</code>, the CFM module operates in extended mode. This
1941 causes it to use a nonstandard destination address to avoid conflicting
1942 with compliant implementations which may be running concurrently on the
1943 network. Furthermore, extended mode increases the accuracy of the
1944 <code>cfm_interval</code> configuration parameter by breaking wire
1945 compatibility with 802.1ag compliant implementations. Defaults to
1948 <column name="other_config" key="cfm_opstate"
1949 type='{"type": "string", "enum": ["set", ["down", "up"]]}'>
1950 When <code>down</code>, the CFM module marks all CCMs it generates as
1951 operationally down without triggering a fault. This allows remote
1952 maintenance points to choose not to forward traffic to the
1953 <ref table="Interface"/> on which this CFM module is running.
1954 Currently, in Open vSwitch, the opdown bit of CCMs affects
1955 <ref table="Interface"/>s participating in bonds, and the bundle
1956 OpenFlow action. This setting is ignored when CFM is not in extended
1957 mode. Defaults to <code>up</code>.
1960 <column name="other_config" key="cfm_ccm_vlan"
1961 type='{"type": "integer", "minInteger": 1, "maxInteger": 4095}'>
1962 When set, the CFM module will apply a VLAN tag to all CCMs it generates
1963 with the given value. May be the string <code>random</code> in which
1964 case each CCM will be tagged with a different randomly generated VLAN.
1967 <column name="other_config" key="cfm_ccm_pcp"
1968 type='{"type": "integer", "minInteger": 1, "maxInteger": 7}'>
1969 When set, the CFM module will apply a VLAN tag to all CCMs it generates
1970 with the given PCP value, the VLAN ID of the tag is governed by the
1971 value of <ref column="other_config" key="cfm_ccm_vlan"/>. If
1972 <ref column="other_config" key="cfm_ccm_vlan"/> is unset, a VLAN ID of
1978 <group title="Bonding Configuration">
1979 <column name="other_config" key="lacp-port-id"
1980 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
1981 The LACP port ID of this <ref table="Interface"/>. Port IDs are
1982 used in LACP negotiations to identify individual ports
1983 participating in a bond.
1986 <column name="other_config" key="lacp-port-priority"
1987 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
1988 The LACP port priority of this <ref table="Interface"/>. In LACP
1989 negotiations <ref table="Interface"/>s with numerically lower
1990 priorities are preferred for aggregation.
1993 <column name="other_config" key="lacp-aggregation-key"
1994 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
1995 The LACP aggregation key of this <ref table="Interface"/>. <ref
1996 table="Interface"/>s with different aggregation keys may not be active
1997 within a given <ref table="Port"/> at the same time.
2001 <group title="Virtual Machine Identifiers">
2003 These key-value pairs specifically apply to an interface that
2004 represents a virtual Ethernet interface connected to a virtual
2005 machine. These key-value pairs should not be present for other types
2006 of interfaces. Keys whose names end in <code>-uuid</code> have
2007 values that uniquely identify the entity in question. For a Citrix
2008 XenServer hypervisor, these values are UUIDs in RFC 4122 format.
2009 Other hypervisors may use other formats.
2012 <column name="external_ids" key="attached-mac">
2013 The MAC address programmed into the ``virtual hardware'' for this
2014 interface, in the form
2015 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>.
2016 For Citrix XenServer, this is the value of the <code>MAC</code> field
2017 in the VIF record for this interface.
2020 <column name="external_ids" key="iface-id">
2021 A system-unique identifier for the interface. On XenServer, this will
2022 commonly be the same as <ref column="external_ids" key="xs-vif-uuid"/>.
2025 <column name="external_ids" key="iface-status"
2026 type='{"type": "string",
2027 "enum": ["set", ["active", "inactive"]]}'>
2029 Hypervisors may sometimes have more than one interface associated
2030 with a given <ref column="external_ids" key="iface-id"/>, only one of
2031 which is actually in use at a given time. For example, in some
2032 circumstances XenServer has both a ``tap'' and a ``vif'' interface
2033 for a single <ref column="external_ids" key="iface-id"/>, but only
2034 uses one of them at a time. A hypervisor that behaves this way must
2035 mark the currently in use interface <code>active</code> and the
2036 others <code>inactive</code>. A hypervisor that never has more than
2037 one interface for a given <ref column="external_ids" key="iface-id"/>
2038 may mark that interface <code>active</code> or omit <ref
2039 column="external_ids" key="iface-status"/> entirely.
2043 During VM migration, a given <ref column="external_ids"
2044 key="iface-id"/> might transiently be marked <code>active</code> on
2045 two different hypervisors. That is, <code>active</code> means that
2046 this <ref column="external_ids" key="iface-id"/> is the active
2047 instance within a single hypervisor, not in a broader scope.
2048 There is one exception: some hypervisors support ``migration'' from a
2049 given hypervisor to itself (most often for test purposes). During
2050 such a ``migration,'' two instances of a single <ref
2051 column="external_ids" key="iface-id"/> might both be briefly marked
2052 <code>active</code> on a single hypervisor.
2056 <column name="external_ids" key="xs-vif-uuid">
2057 The virtual interface associated with this interface.
2060 <column name="external_ids" key="xs-network-uuid">
2061 The virtual network to which this interface is attached.
2064 <column name="external_ids" key="vm-id">
2065 The VM to which this interface belongs. On XenServer, this will be the
2066 same as <ref column="external_ids" key="xs-vm-uuid"/>.
2069 <column name="external_ids" key="xs-vm-uuid">
2070 The VM to which this interface belongs.
2074 <group title="VLAN Splinters">
2076 The ``VLAN splinters'' feature increases Open vSwitch compatibility
2077 with buggy network drivers in old versions of Linux that do not
2078 properly support VLANs when VLAN devices are not used, at some cost
2079 in memory and performance.
2083 When VLAN splinters are enabled on a particular interface, Open vSwitch
2084 creates a VLAN device for each in-use VLAN. For sending traffic tagged
2085 with a VLAN on the interface, it substitutes the VLAN device. Traffic
2086 received on the VLAN device is treated as if it had been received on
2087 the interface on the particular VLAN.
2091 VLAN splinters consider a VLAN to be in use if:
2096 The VLAN is the <ref table="Port" column="tag"/> value in any <ref
2097 table="Port"/> record.
2101 The VLAN is listed within the <ref table="Port" column="trunks"/>
2102 column of the <ref table="Port"/> record of an interface on which
2103 VLAN splinters are enabled.
2105 An empty <ref table="Port" column="trunks"/> does not influence the
2106 in-use VLANs: creating 4,096 VLAN devices is impractical because it
2107 will exceed the current 1,024 port per datapath limit.
2111 An OpenFlow flow within any bridge matches the VLAN.
2116 The same set of in-use VLANs applies to every interface on which VLAN
2117 splinters are enabled. That is, the set is not chosen separately for
2118 each interface but selected once as the union of all in-use VLANs based
2123 It does not make sense to enable VLAN splinters on an interface for an
2124 access port, or on an interface that is not a physical port.
2128 VLAN splinters are deprecated. When broken device drivers are no
2129 longer in widespread use, we will delete this feature.
2132 <column name="other_config" key="enable-vlan-splinters"
2133 type='{"type": "boolean"}'>
2135 Set to <code>true</code> to enable VLAN splinters on this interface.
2136 Defaults to <code>false</code>.
2140 VLAN splinters increase kernel and userspace memory overhead, so do
2141 not use them unless they are needed.
2145 VLAN splinters do not support 802.1p priority tags. Received
2146 priorities will appear to be 0, regardless of their actual values,
2147 and priorities on transmitted packets will also be cleared to 0.
2152 <group title="Common Columns">
2153 The overall purpose of these columns is described under <code>Common
2154 Columns</code> at the beginning of this document.
2156 <column name="other_config"/>
2157 <column name="external_ids"/>
2161 <table name="Flow_Table" title="OpenFlow table configuration">
2162 <p>Configuration for a particular OpenFlow table.</p>
2164 <column name="name">
2165 The table's name. Set this column to change the name that controllers
2166 will receive when they request table statistics, e.g. <code>ovs-ofctl
2167 dump-tables</code>. The name does not affect switch behavior.
2170 <column name="flow_limit">
2171 If set, limits the number of flows that may be added to the table. Open
2172 vSwitch may limit the number of flows in a table for other reasons,
2173 e.g. due to hardware limitations or for resource availability or
2174 performance reasons.
2177 <column name="overflow_policy">
2179 Controls the switch's behavior when an OpenFlow flow table modification
2180 request would add flows in excess of <ref column="flow_limit"/>. The
2181 supported values are:
2185 <dt><code>refuse</code></dt>
2187 Refuse to add the flow or flows. This is also the default policy
2188 when <ref column="overflow_policy"/> is unset.
2191 <dt><code>evict</code></dt>
2193 Delete the flow that will expire soonest. See <ref column="groups"/>
2199 <column name="groups">
2201 When <ref column="overflow_policy"/> is <code>evict</code>, this
2202 controls how flows are chosen for eviction when the flow table would
2203 otherwise exceed <ref column="flow_limit"/> flows. Its value is a set
2204 of NXM fields or sub-fields, each of which takes one of the forms
2205 <code><var>field</var>[]</code> or
2206 <code><var>field</var>[<var>start</var>..<var>end</var>]</code>,
2207 e.g. <code>NXM_OF_IN_PORT[]</code>. Please see
2208 <code>nicira-ext.h</code> for a complete list of NXM field names.
2212 When a flow must be evicted due to overflow, the flow to evict is
2213 chosen through an approximation of the following algorithm:
2218 Divide the flows in the table into groups based on the values of the
2219 specified fields or subfields, so that all of the flows in a given
2220 group have the same values for those fields. If a flow does not
2221 specify a given field, that field's value is treated as 0.
2225 Consider the flows in the largest group, that is, the group that
2226 contains the greatest number of flows. If two or more groups all
2227 have the same largest number of flows, consider the flows in all of
2232 Among the flows under consideration, choose the flow that expires
2233 soonest for eviction.
2238 The eviction process only considers flows that have an idle timeout or
2239 a hard timeout. That is, eviction never deletes permanent flows.
2240 (Permanent flows do count against <ref column="flow_limit"/>.)
2244 Open vSwitch ignores any invalid or unknown field specifications.
2248 When <ref column="overflow_policy"/> is not <code>evict</code>, this
2249 column has no effect.
2254 <table name="QoS" title="Quality of Service configuration">
2255 <p>Quality of Service (QoS) configuration for each Port that
2258 <column name="type">
2259 <p>The type of QoS to implement. The currently defined types are
2262 <dt><code>linux-htb</code></dt>
2264 Linux ``hierarchy token bucket'' classifier. See tc-htb(8) (also at
2265 <code>http://linux.die.net/man/8/tc-htb</code>) and the HTB manual
2266 (<code>http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm</code>)
2267 for information on how this classifier works and how to configure it.
2271 <dt><code>linux-hfsc</code></dt>
2273 Linux "Hierarchical Fair Service Curve" classifier.
2274 See <code>http://linux-ip.net/articles/hfsc.en/</code> for
2275 information on how this classifier works.
2280 <column name="queues">
2281 <p>A map from queue numbers to <ref table="Queue"/> records. The
2282 supported range of queue numbers depend on <ref column="type"/>. The
2283 queue numbers are the same as the <code>queue_id</code> used in
2284 OpenFlow in <code>struct ofp_action_enqueue</code> and other
2288 Queue 0 is the ``default queue.'' It is used by OpenFlow output
2289 actions when no specific queue has been set. When no configuration for
2290 queue 0 is present, it is automatically configured as if a <ref
2291 table="Queue"/> record with empty <ref table="Queue" column="dscp"/>
2292 and <ref table="Queue" column="other_config"/> columns had been
2294 (Before version 1.6, Open vSwitch would leave queue 0 unconfigured in
2295 this case. With some queuing disciplines, this dropped all packets
2296 destined for the default queue.)
2300 <group title="Configuration for linux-htb and linux-hfsc">
2302 The <code>linux-htb</code> and <code>linux-hfsc</code> classes support
2303 the following key-value pair:
2306 <column name="other_config" key="max-rate" type='{"type": "integer"}'>
2307 Maximum rate shared by all queued traffic, in bit/s. Optional. If not
2308 specified, for physical interfaces, the default is the link rate. For
2309 other interfaces or if the link rate cannot be determined, the default
2310 is currently 100 Mbps.
2314 <group title="Common Columns">
2315 The overall purpose of these columns is described under <code>Common
2316 Columns</code> at the beginning of this document.
2318 <column name="other_config"/>
2319 <column name="external_ids"/>
2323 <table name="Queue" title="QoS output queue.">
2324 <p>A configuration for a port output queue, used in configuring Quality of
2325 Service (QoS) features. May be referenced by <ref column="queues"
2326 table="QoS"/> column in <ref table="QoS"/> table.</p>
2328 <column name="dscp">
2329 If set, Open vSwitch will mark all traffic egressing this
2330 <ref table="Queue"/> with the given DSCP bits. Traffic egressing the
2331 default <ref table="Queue"/> is only marked if it was explicitly selected
2332 as the <ref table="Queue"/> at the time the packet was output. If unset,
2333 the DSCP bits of traffic egressing this <ref table="Queue"/> will remain
2337 <group title="Configuration for linux-htb QoS">
2339 <ref table="QoS"/> <ref table="QoS" column="type"/>
2340 <code>linux-htb</code> may use <code>queue_id</code>s less than 61440.
2341 It has the following key-value pairs defined.
2344 <column name="other_config" key="min-rate"
2345 type='{"type": "integer", "minInteger": 1}'>
2346 Minimum guaranteed bandwidth, in bit/s.
2349 <column name="other_config" key="max-rate"
2350 type='{"type": "integer", "minInteger": 1}'>
2351 Maximum allowed bandwidth, in bit/s. Optional. If specified, the
2352 queue's rate will not be allowed to exceed the specified value, even
2353 if excess bandwidth is available. If unspecified, defaults to no
2357 <column name="other_config" key="burst"
2358 type='{"type": "integer", "minInteger": 1}'>
2359 Burst size, in bits. This is the maximum amount of ``credits'' that a
2360 queue can accumulate while it is idle. Optional. Details of the
2361 <code>linux-htb</code> implementation require a minimum burst size, so
2362 a too-small <code>burst</code> will be silently ignored.
2365 <column name="other_config" key="priority"
2366 type='{"type": "integer", "minInteger": 0, "maxInteger": 4294967295}'>
2367 A queue with a smaller <code>priority</code> will receive all the
2368 excess bandwidth that it can use before a queue with a larger value
2369 receives any. Specific priority values are unimportant; only relative
2370 ordering matters. Defaults to 0 if unspecified.
2374 <group title="Configuration for linux-hfsc QoS">
2376 <ref table="QoS"/> <ref table="QoS" column="type"/>
2377 <code>linux-hfsc</code> may use <code>queue_id</code>s less than 61440.
2378 It has the following key-value pairs defined.
2381 <column name="other_config" key="min-rate"
2382 type='{"type": "integer", "minInteger": 1}'>
2383 Minimum guaranteed bandwidth, in bit/s.
2386 <column name="other_config" key="max-rate"
2387 type='{"type": "integer", "minInteger": 1}'>
2388 Maximum allowed bandwidth, in bit/s. Optional. If specified, the
2389 queue's rate will not be allowed to exceed the specified value, even if
2390 excess bandwidth is available. If unspecified, defaults to no
2395 <group title="Common Columns">
2396 The overall purpose of these columns is described under <code>Common
2397 Columns</code> at the beginning of this document.
2399 <column name="other_config"/>
2400 <column name="external_ids"/>
2404 <table name="Mirror" title="Port mirroring.">
2405 <p>A port mirror within a <ref table="Bridge"/>.</p>
2406 <p>A port mirror configures a bridge to send selected frames to special
2407 ``mirrored'' ports, in addition to their normal destinations. Mirroring
2408 traffic may also be referred to as SPAN or RSPAN, depending on how
2409 the mirrored traffic is sent.</p>
2411 <column name="name">
2412 Arbitrary identifier for the <ref table="Mirror"/>.
2415 <group title="Selecting Packets for Mirroring">
2417 To be selected for mirroring, a given packet must enter or leave the
2418 bridge through a selected port and it must also be in one of the
2422 <column name="select_all">
2423 If true, every packet arriving or departing on any port is
2424 selected for mirroring.
2427 <column name="select_dst_port">
2428 Ports on which departing packets are selected for mirroring.
2431 <column name="select_src_port">
2432 Ports on which arriving packets are selected for mirroring.
2435 <column name="select_vlan">
2436 VLANs on which packets are selected for mirroring. An empty set
2437 selects packets on all VLANs.
2441 <group title="Mirroring Destination Configuration">
2443 These columns are mutually exclusive. Exactly one of them must be
2447 <column name="output_port">
2448 <p>Output port for selected packets, if nonempty.</p>
2449 <p>Specifying a port for mirror output reserves that port exclusively
2450 for mirroring. No frames other than those selected for mirroring
2452 will be forwarded to the port, and any frames received on the port
2453 will be discarded.</p>
2455 The output port may be any kind of port supported by Open vSwitch.
2456 It may be, for example, a physical port (sometimes called SPAN) or a
2461 <column name="output_vlan">
2462 <p>Output VLAN for selected packets, if nonempty.</p>
2463 <p>The frames will be sent out all ports that trunk
2464 <ref column="output_vlan"/>, as well as any ports with implicit VLAN
2465 <ref column="output_vlan"/>. When a mirrored frame is sent out a
2466 trunk port, the frame's VLAN tag will be set to
2467 <ref column="output_vlan"/>, replacing any existing tag; when it is
2468 sent out an implicit VLAN port, the frame will not be tagged. This
2469 type of mirroring is sometimes called RSPAN.</p>
2471 See the documentation for
2472 <ref column="other_config" key="forward-bpdu"/> in the
2473 <ref table="Interface"/> table for a list of destination MAC
2474 addresses which will not be mirrored to a VLAN to avoid confusing
2475 switches that interpret the protocols that they represent.
2477 <p><em>Please note:</em> Mirroring to a VLAN can disrupt a network that
2478 contains unmanaged switches. Consider an unmanaged physical switch
2479 with two ports: port 1, connected to an end host, and port 2,
2480 connected to an Open vSwitch configured to mirror received packets
2481 into VLAN 123 on port 2. Suppose that the end host sends a packet on
2482 port 1 that the physical switch forwards to port 2. The Open vSwitch
2483 forwards this packet to its destination and then reflects it back on
2484 port 2 in VLAN 123. This reflected packet causes the unmanaged
2485 physical switch to replace the MAC learning table entry, which
2486 correctly pointed to port 1, with one that incorrectly points to port
2487 2. Afterward, the physical switch will direct packets destined for
2488 the end host to the Open vSwitch on port 2, instead of to the end
2489 host on port 1, disrupting connectivity. If mirroring to a VLAN is
2490 desired in this scenario, then the physical switch must be replaced
2491 by one that learns Ethernet addresses on a per-VLAN basis. In
2492 addition, learning should be disabled on the VLAN containing mirrored
2493 traffic. If this is not done then intermediate switches will learn
2494 the MAC address of each end host from the mirrored traffic. If
2495 packets being sent to that end host are also mirrored, then they will
2496 be dropped since the switch will attempt to send them out the input
2497 port. Disabling learning for the VLAN will cause the switch to
2498 correctly send the packet out all ports configured for that VLAN. If
2499 Open vSwitch is being used as an intermediate switch, learning can be
2500 disabled by adding the mirrored VLAN to <ref column="flood_vlans"/>
2501 in the appropriate <ref table="Bridge"/> table or tables.</p>
2503 Mirroring to a GRE tunnel has fewer caveats than mirroring to a
2504 VLAN and should generally be preferred.
2509 <group title="Statistics: Mirror counters">
2511 Key-value pairs that report mirror statistics.
2513 <column name="statistics" key="tx_packets">
2514 Number of packets transmitted through this mirror.
2516 <column name="statistics" key="tx_bytes">
2517 Number of bytes transmitted through this mirror.
2521 <group title="Common Columns">
2522 The overall purpose of these columns is described under <code>Common
2523 Columns</code> at the beginning of this document.
2525 <column name="external_ids"/>
2529 <table name="Controller" title="OpenFlow controller configuration.">
2530 <p>An OpenFlow controller.</p>
2533 Open vSwitch supports two kinds of OpenFlow controllers:
2537 <dt>Primary controllers</dt>
2540 This is the kind of controller envisioned by the OpenFlow 1.0
2541 specification. Usually, a primary controller implements a network
2542 policy by taking charge of the switch's flow table.
2546 Open vSwitch initiates and maintains persistent connections to
2547 primary controllers, retrying the connection each time it fails or
2548 drops. The <ref table="Bridge" column="fail_mode"/> column in the
2549 <ref table="Bridge"/> table applies to primary controllers.
2553 Open vSwitch permits a bridge to have any number of primary
2554 controllers. When multiple controllers are configured, Open
2555 vSwitch connects to all of them simultaneously. Because
2556 OpenFlow 1.0 does not specify how multiple controllers
2557 coordinate in interacting with a single switch, more than
2558 one primary controller should be specified only if the
2559 controllers are themselves designed to coordinate with each
2560 other. (The Nicira-defined <code>NXT_ROLE</code> OpenFlow
2561 vendor extension may be useful for this.)
2564 <dt>Service controllers</dt>
2567 These kinds of OpenFlow controller connections are intended for
2568 occasional support and maintenance use, e.g. with
2569 <code>ovs-ofctl</code>. Usually a service controller connects only
2570 briefly to inspect or modify some of a switch's state.
2574 Open vSwitch listens for incoming connections from service
2575 controllers. The service controllers initiate and, if necessary,
2576 maintain the connections from their end. The <ref table="Bridge"
2577 column="fail_mode"/> column in the <ref table="Bridge"/> table does
2578 not apply to service controllers.
2582 Open vSwitch supports configuring any number of service controllers.
2588 The <ref column="target"/> determines the type of controller.
2591 <group title="Core Features">
2592 <column name="target">
2593 <p>Connection method for controller.</p>
2595 The following connection methods are currently supported for primary
2599 <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
2601 <p>The specified SSL <var>port</var> (default: 6633) on the host at
2602 the given <var>ip</var>, which must be expressed as an IP address
2603 (not a DNS name). The <ref table="Open_vSwitch" column="ssl"/>
2604 column in the <ref table="Open_vSwitch"/> table must point to a
2605 valid SSL configuration when this form is used.</p>
2606 <p>SSL support is an optional feature that is not always built as
2607 part of Open vSwitch.</p>
2609 <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
2610 <dd>The specified TCP <var>port</var> (default: 6633) on the host at
2611 the given <var>ip</var>, which must be expressed as an IP address
2612 (not a DNS name).</dd>
2615 The following connection methods are currently supported for service
2619 <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
2622 Listens for SSL connections on the specified TCP <var>port</var>
2623 (default: 6633). If <var>ip</var>, which must be expressed as an
2624 IP address (not a DNS name), is specified, then connections are
2625 restricted to the specified local IP address.
2628 The <ref table="Open_vSwitch" column="ssl"/> column in the <ref
2629 table="Open_vSwitch"/> table must point to a valid SSL
2630 configuration when this form is used.
2632 <p>SSL support is an optional feature that is not always built as
2633 part of Open vSwitch.</p>
2635 <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
2637 Listens for connections on the specified TCP <var>port</var>
2638 (default: 6633). If <var>ip</var>, which must be expressed as an
2639 IP address (not a DNS name), is specified, then connections are
2640 restricted to the specified local IP address.
2643 <p>When multiple controllers are configured for a single bridge, the
2644 <ref column="target"/> values must be unique. Duplicate
2645 <ref column="target"/> values yield unspecified results.</p>
2648 <column name="connection_mode">
2649 <p>If it is specified, this setting must be one of the following
2650 strings that describes how Open vSwitch contacts this OpenFlow
2651 controller over the network:</p>
2654 <dt><code>in-band</code></dt>
2655 <dd>In this mode, this controller's OpenFlow traffic travels over the
2656 bridge associated with the controller. With this setting, Open
2657 vSwitch allows traffic to and from the controller regardless of the
2658 contents of the OpenFlow flow table. (Otherwise, Open vSwitch
2659 would never be able to connect to the controller, because it did
2660 not have a flow to enable it.) This is the most common connection
2661 mode because it is not necessary to maintain two independent
2663 <dt><code>out-of-band</code></dt>
2664 <dd>In this mode, OpenFlow traffic uses a control network separate
2665 from the bridge associated with this controller, that is, the
2666 bridge does not use any of its own network devices to communicate
2667 with the controller. The control network must be configured
2668 separately, before or after <code>ovs-vswitchd</code> is started.
2672 <p>If not specified, the default is implementation-specific.</p>
2676 <group title="Controller Failure Detection and Handling">
2677 <column name="max_backoff">
2678 Maximum number of milliseconds to wait between connection attempts.
2679 Default is implementation-specific.
2682 <column name="inactivity_probe">
2683 Maximum number of milliseconds of idle time on connection to
2684 controller before sending an inactivity probe message. If Open
2685 vSwitch does not communicate with the controller for the specified
2686 number of seconds, it will send a probe. If a response is not
2687 received for the same additional amount of time, Open vSwitch
2688 assumes the connection has been broken and attempts to reconnect.
2689 Default is implementation-specific. A value of 0 disables
2694 <group title="Asynchronous Message Configuration">
2696 OpenFlow switches send certain messages to controllers spontanenously,
2697 that is, not in response to any request from the controller. These
2698 messages are called ``asynchronous messages.'' These columns allow
2699 asynchronous messages to be limited or disabled to ensure the best use
2700 of network resources.
2703 <column name="enable_async_messages">
2704 The OpenFlow protocol enables asynchronous messages at time of
2705 connection establishment, which means that a controller can receive
2706 asynchronous messages, potentially many of them, even if it turns them
2707 off immediately after connecting. Set this column to
2708 <code>false</code> to change Open vSwitch behavior to disable, by
2709 default, all asynchronous messages. The controller can use the
2710 <code>NXT_SET_ASYNC_CONFIG</code> Nicira extension to OpenFlow to turn
2711 on any messages that it does want to receive, if any.
2714 <column name="controller_rate_limit">
2716 The maximum rate at which the switch will forward packets to the
2717 OpenFlow controller, in packets per second. This feature prevents a
2718 single bridge from overwhelming the controller. If not specified,
2719 the default is implementation-specific.
2723 In addition, when a high rate triggers rate-limiting, Open vSwitch
2724 queues controller packets for each port and transmits them to the
2725 controller at the configured rate. The <ref
2726 column="controller_burst_limit"/> value limits the number of queued
2727 packets. Ports on a bridge share the packet queue fairly.
2731 Open vSwitch maintains two such packet rate-limiters per bridge: one
2732 for packets sent up to the controller because they do not correspond
2733 to any flow, and the other for packets sent up to the controller by
2734 request through flow actions. When both rate-limiters are filled with
2735 packets, the actual rate that packets are sent to the controller is
2736 up to twice the specified rate.
2740 <column name="controller_burst_limit">
2741 In conjunction with <ref column="controller_rate_limit"/>,
2742 the maximum number of unused packet credits that the bridge will
2743 allow to accumulate, in packets. If not specified, the default
2744 is implementation-specific.
2748 <group title="Additional In-Band Configuration">
2749 <p>These values are considered only in in-band control mode (see
2750 <ref column="connection_mode"/>).</p>
2752 <p>When multiple controllers are configured on a single bridge, there
2753 should be only one set of unique values in these columns. If different
2754 values are set for these columns in different controllers, the effect
2757 <column name="local_ip">
2758 The IP address to configure on the local port,
2759 e.g. <code>192.168.0.123</code>. If this value is unset, then
2760 <ref column="local_netmask"/> and <ref column="local_gateway"/> are
2764 <column name="local_netmask">
2765 The IP netmask to configure on the local port,
2766 e.g. <code>255.255.255.0</code>. If <ref column="local_ip"/> is set
2767 but this value is unset, then the default is chosen based on whether
2768 the IP address is class A, B, or C.
2771 <column name="local_gateway">
2772 The IP address of the gateway to configure on the local port, as a
2773 string, e.g. <code>192.168.0.1</code>. Leave this column unset if
2774 this network has no gateway.
2778 <group title="Controller Status">
2779 <column name="is_connected">
2780 <code>true</code> if currently connected to this controller,
2781 <code>false</code> otherwise.
2785 type='{"type": "string", "enum": ["set", ["other", "master", "slave"]]}'>
2786 <p>The level of authority this controller has on the associated
2787 bridge. Possible values are:</p>
2789 <dt><code>other</code></dt>
2790 <dd>Allows the controller access to all OpenFlow features.</dd>
2791 <dt><code>master</code></dt>
2792 <dd>Equivalent to <code>other</code>, except that there may be at
2793 most one master controller at a time. When a controller configures
2794 itself as <code>master</code>, any existing master is demoted to
2795 the <code>slave</code>role.</dd>
2796 <dt><code>slave</code></dt>
2797 <dd>Allows the controller read-only access to OpenFlow features.
2798 Attempts to modify the flow table will be rejected with an
2799 error. Slave controllers do not receive OFPT_PACKET_IN or
2800 OFPT_FLOW_REMOVED messages, but they do receive OFPT_PORT_STATUS
2805 <column name="status" key="last_error">
2806 A human-readable description of the last error on the connection
2807 to the controller; i.e. <code>strerror(errno)</code>. This key
2808 will exist only if an error has occurred.
2811 <column name="status" key="state"
2812 type='{"type": "string", "enum": ["set", ["VOID", "BACKOFF", "CONNECTING", "ACTIVE", "IDLE"]]}'>
2814 The state of the connection to the controller:
2817 <dt><code>VOID</code></dt>
2818 <dd>Connection is disabled.</dd>
2820 <dt><code>BACKOFF</code></dt>
2821 <dd>Attempting to reconnect at an increasing period.</dd>
2823 <dt><code>CONNECTING</code></dt>
2824 <dd>Attempting to connect.</dd>
2826 <dt><code>ACTIVE</code></dt>
2827 <dd>Connected, remote host responsive.</dd>
2829 <dt><code>IDLE</code></dt>
2830 <dd>Connection is idle. Waiting for response to keep-alive.</dd>
2833 These values may change in the future. They are provided only for
2838 <column name="status" key="sec_since_connect"
2839 type='{"type": "integer", "minInteger": 0}'>
2840 The amount of time since this controller last successfully connected to
2841 the switch (in seconds). Value is empty if controller has never
2842 successfully connected.
2845 <column name="status" key="sec_since_disconnect"
2846 type='{"type": "integer", "minInteger": 1}'>
2847 The amount of time since this controller last disconnected from
2848 the switch (in seconds). Value is empty if controller has never
2853 <group title="Connection Parameters">
2855 Additional configuration for a connection between the controller
2856 and the Open vSwitch.
2859 <column name="other_config" key="dscp"
2860 type='{"type": "integer"}'>
2861 The Differentiated Service Code Point (DSCP) is specified using 6 bits
2862 in the Type of Service (TOS) field in the IP header. DSCP provides a
2863 mechanism to classify the network traffic and provide Quality of
2864 Service (QoS) on IP networks.
2866 The DSCP value specified here is used when establishing the connection
2867 between the controller and the Open vSwitch. If no value is specified,
2868 a default value of 48 is chosen. Valid DSCP values must be in the
2874 <group title="Common Columns">
2875 The overall purpose of these columns is described under <code>Common
2876 Columns</code> at the beginning of this document.
2878 <column name="external_ids"/>
2879 <column name="other_config"/>
2883 <table name="Manager" title="OVSDB management connection.">
2885 Configuration for a database connection to an Open vSwitch database
2890 This table primarily configures the Open vSwitch database
2891 (<code>ovsdb-server</code>), not the Open vSwitch switch
2892 (<code>ovs-vswitchd</code>). The switch does read the table to determine
2893 what connections should be treated as in-band.
2897 The Open vSwitch database server can initiate and maintain active
2898 connections to remote clients. It can also listen for database
2902 <group title="Core Features">
2903 <column name="target">
2904 <p>Connection method for managers.</p>
2906 The following connection methods are currently supported:
2909 <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
2912 The specified SSL <var>port</var> (default: 6632) on the host at
2913 the given <var>ip</var>, which must be expressed as an IP address
2914 (not a DNS name). The <ref table="Open_vSwitch" column="ssl"/>
2915 column in the <ref table="Open_vSwitch"/> table must point to a
2916 valid SSL configuration when this form is used.
2919 SSL support is an optional feature that is not always built as
2920 part of Open vSwitch.
2924 <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
2926 The specified TCP <var>port</var> (default: 6632) on the host at
2927 the given <var>ip</var>, which must be expressed as an IP address
2930 <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
2933 Listens for SSL connections on the specified TCP <var>port</var>
2934 (default: 6632). Specify 0 for <var>port</var> to have the
2935 kernel automatically choose an available port. If <var>ip</var>,
2936 which must be expressed as an IP address (not a DNS name), is
2937 specified, then connections are restricted to the specified local
2941 The <ref table="Open_vSwitch" column="ssl"/> column in the <ref
2942 table="Open_vSwitch"/> table must point to a valid SSL
2943 configuration when this form is used.
2946 SSL support is an optional feature that is not always built as
2947 part of Open vSwitch.
2950 <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
2952 Listens for connections on the specified TCP <var>port</var>
2953 (default: 6632). Specify 0 for <var>port</var> to have the kernel
2954 automatically choose an available port. If <var>ip</var>, which
2955 must be expressed as an IP address (not a DNS name), is specified,
2956 then connections are restricted to the specified local IP address.
2959 <p>When multiple managers are configured, the <ref column="target"/>
2960 values must be unique. Duplicate <ref column="target"/> values yield
2961 unspecified results.</p>
2964 <column name="connection_mode">
2966 If it is specified, this setting must be one of the following strings
2967 that describes how Open vSwitch contacts this OVSDB client over the
2972 <dt><code>in-band</code></dt>
2974 In this mode, this connection's traffic travels over a bridge
2975 managed by Open vSwitch. With this setting, Open vSwitch allows
2976 traffic to and from the client regardless of the contents of the
2977 OpenFlow flow table. (Otherwise, Open vSwitch would never be able
2978 to connect to the client, because it did not have a flow to enable
2979 it.) This is the most common connection mode because it is not
2980 necessary to maintain two independent networks.
2982 <dt><code>out-of-band</code></dt>
2984 In this mode, the client's traffic uses a control network separate
2985 from that managed by Open vSwitch, that is, Open vSwitch does not
2986 use any of its own network devices to communicate with the client.
2987 The control network must be configured separately, before or after
2988 <code>ovs-vswitchd</code> is started.
2993 If not specified, the default is implementation-specific.
2998 <group title="Client Failure Detection and Handling">
2999 <column name="max_backoff">
3000 Maximum number of milliseconds to wait between connection attempts.
3001 Default is implementation-specific.
3004 <column name="inactivity_probe">
3005 Maximum number of milliseconds of idle time on connection to the client
3006 before sending an inactivity probe message. If Open vSwitch does not
3007 communicate with the client for the specified number of seconds, it
3008 will send a probe. If a response is not received for the same
3009 additional amount of time, Open vSwitch assumes the connection has been
3010 broken and attempts to reconnect. Default is implementation-specific.
3011 A value of 0 disables inactivity probes.
3015 <group title="Status">
3016 <column name="is_connected">
3017 <code>true</code> if currently connected to this manager,
3018 <code>false</code> otherwise.
3021 <column name="status" key="last_error">
3022 A human-readable description of the last error on the connection
3023 to the manager; i.e. <code>strerror(errno)</code>. This key
3024 will exist only if an error has occurred.
3027 <column name="status" key="state"
3028 type='{"type": "string", "enum": ["set", ["VOID", "BACKOFF", "CONNECTING", "ACTIVE", "IDLE"]]}'>
3030 The state of the connection to the manager:
3033 <dt><code>VOID</code></dt>
3034 <dd>Connection is disabled.</dd>
3036 <dt><code>BACKOFF</code></dt>
3037 <dd>Attempting to reconnect at an increasing period.</dd>
3039 <dt><code>CONNECTING</code></dt>
3040 <dd>Attempting to connect.</dd>
3042 <dt><code>ACTIVE</code></dt>
3043 <dd>Connected, remote host responsive.</dd>
3045 <dt><code>IDLE</code></dt>
3046 <dd>Connection is idle. Waiting for response to keep-alive.</dd>
3049 These values may change in the future. They are provided only for
3054 <column name="status" key="sec_since_connect"
3055 type='{"type": "integer", "minInteger": 0}'>
3056 The amount of time since this manager last successfully connected
3057 to the database (in seconds). Value is empty if manager has never
3058 successfully connected.
3061 <column name="status" key="sec_since_disconnect"
3062 type='{"type": "integer", "minInteger": 0}'>
3063 The amount of time since this manager last disconnected from the
3064 database (in seconds). Value is empty if manager has never
3068 <column name="status" key="locks_held">
3069 Space-separated list of the names of OVSDB locks that the connection
3070 holds. Omitted if the connection does not hold any locks.
3073 <column name="status" key="locks_waiting">
3074 Space-separated list of the names of OVSDB locks that the connection is
3075 currently waiting to acquire. Omitted if the connection is not waiting
3079 <column name="status" key="locks_lost">
3080 Space-separated list of the names of OVSDB locks that the connection
3081 has had stolen by another OVSDB client. Omitted if no locks have been
3082 stolen from this connection.
3085 <column name="status" key="n_connections"
3086 type='{"type": "integer", "minInteger": 2}'>
3088 When <ref column="target"/> specifies a connection method that
3089 listens for inbound connections (e.g. <code>ptcp:</code> or
3090 <code>pssl:</code>) and more than one connection is actually active,
3091 the value is the number of active connections. Otherwise, this
3092 key-value pair is omitted.
3095 When multiple connections are active, status columns and key-value
3096 pairs (other than this one) report the status of one arbitrarily
3101 <column name="status" key="bound_port" type='{"type": "integer"}'>
3102 When <ref column="target"/> is <code>ptcp:</code> or
3103 <code>pssl:</code>, this is the TCP port on which the OVSDB server is
3104 listening. (This is is particularly useful when <ref
3105 column="target"/> specifies a port of 0, allowing the kernel to
3106 choose any available port.)
3110 <group title="Connection Parameters">
3112 Additional configuration for a connection between the manager
3113 and the Open vSwitch Database.
3116 <column name="other_config" key="dscp"
3117 type='{"type": "integer"}'>
3118 The Differentiated Service Code Point (DSCP) is specified using 6 bits
3119 in the Type of Service (TOS) field in the IP header. DSCP provides a
3120 mechanism to classify the network traffic and provide Quality of
3121 Service (QoS) on IP networks.
3123 The DSCP value specified here is used when establishing the connection
3124 between the manager and the Open vSwitch. If no value is specified, a
3125 default value of 48 is chosen. Valid DSCP values must be in the range
3130 <group title="Common Columns">
3131 The overall purpose of these columns is described under <code>Common
3132 Columns</code> at the beginning of this document.
3134 <column name="external_ids"/>
3135 <column name="other_config"/>
3139 <table name="NetFlow">
3140 A NetFlow target. NetFlow is a protocol that exports a number of
3141 details about terminating IP flows, such as the principals involved
3144 <column name="targets">
3145 NetFlow targets in the form
3146 <code><var>ip</var>:<var>port</var></code>. The <var>ip</var>
3147 must be specified numerically, not as a DNS name.
3150 <column name="engine_id">
3151 Engine ID to use in NetFlow messages. Defaults to datapath index
3155 <column name="engine_type">
3156 Engine type to use in NetFlow messages. Defaults to datapath
3157 index if not specified.
3160 <column name="active_timeout">
3161 The interval at which NetFlow records are sent for flows that are
3162 still active, in seconds. A value of <code>0</code> requests the
3163 default timeout (currently 600 seconds); a value of <code>-1</code>
3164 disables active timeouts.
3167 <column name="add_id_to_interface">
3168 <p>If this column's value is <code>false</code>, the ingress and egress
3169 interface fields of NetFlow flow records are derived from OpenFlow port
3170 numbers. When it is <code>true</code>, the 7 most significant bits of
3171 these fields will be replaced by the least significant 7 bits of the
3172 engine id. This is useful because many NetFlow collectors do not
3173 expect multiple switches to be sending messages from the same host, so
3174 they do not store the engine information which could be used to
3175 disambiguate the traffic.</p>
3176 <p>When this option is enabled, a maximum of 508 ports are supported.</p>
3179 <group title="Common Columns">
3180 The overall purpose of these columns is described under <code>Common
3181 Columns</code> at the beginning of this document.
3183 <column name="external_ids"/>
3188 SSL configuration for an Open_vSwitch.
3190 <column name="private_key">
3191 Name of a PEM file containing the private key used as the switch's
3192 identity for SSL connections to the controller.
3195 <column name="certificate">
3196 Name of a PEM file containing a certificate, signed by the
3197 certificate authority (CA) used by the controller and manager,
3198 that certifies the switch's private key, identifying a trustworthy
3202 <column name="ca_cert">
3203 Name of a PEM file containing the CA certificate used to verify
3204 that the switch is connected to a trustworthy controller.
3207 <column name="bootstrap_ca_cert">
3208 If set to <code>true</code>, then Open vSwitch will attempt to
3209 obtain the CA certificate from the controller on its first SSL
3210 connection and save it to the named PEM file. If it is successful,
3211 it will immediately drop the connection and reconnect, and from then
3212 on all SSL connections must be authenticated by a certificate signed
3213 by the CA certificate thus obtained. <em>This option exposes the
3214 SSL connection to a man-in-the-middle attack obtaining the initial
3215 CA certificate.</em> It may still be useful for bootstrapping.
3218 <group title="Common Columns">
3219 The overall purpose of these columns is described under <code>Common
3220 Columns</code> at the beginning of this document.
3222 <column name="external_ids"/>
3226 <table name="sFlow">
3227 <p>A set of sFlow(R) targets. sFlow is a protocol for remote
3228 monitoring of switches.</p>
3230 <column name="agent">
3231 Name of the network device whose IP address should be reported as the
3232 ``agent address'' to collectors. If not specified, the agent device is
3233 figured from the first target address and the routing table. If the
3234 routing table does not contain a route to the target, the IP address
3235 defaults to the <ref table="Controller" column="local_ip"/> in the
3236 collector's <ref table="Controller"/>. If an agent IP address cannot be
3237 determined any of these ways, sFlow is disabled.
3240 <column name="header">
3241 Number of bytes of a sampled packet to send to the collector.
3242 If not specified, the default is 128 bytes.
3245 <column name="polling">
3246 Polling rate in seconds to send port statistics to the collector.
3247 If not specified, defaults to 30 seconds.
3250 <column name="sampling">
3251 Rate at which packets should be sampled and sent to the collector.
3252 If not specified, defaults to 400, which means one out of 400
3253 packets, on average, will be sent to the collector.
3256 <column name="targets">
3257 sFlow targets in the form
3258 <code><var>ip</var>:<var>port</var></code>.
3261 <group title="Common Columns">
3262 The overall purpose of these columns is described under <code>Common
3263 Columns</code> at the beginning of this document.
3265 <column name="external_ids"/>
3269 <table name="IPFIX">
3270 <p>A set of IPFIX collectors. IPFIX is a protocol that exports a
3271 number of details about flows.</p>
3273 <column name="targets">
3274 IPFIX target collectors in the form
3275 <code><var>ip</var>:<var>port</var></code>.
3278 <column name="sampling">
3279 For per-bridge packet sampling, i.e. when this row is referenced
3280 from a <ref table="Bridge"/>, the rate at which packets should
3281 be sampled and sent to each target collector. If not specified,
3282 defaults to 400, which means one out of 400 packets, on average,
3283 will be sent to each target collector. Ignored for per-flow
3284 sampling, i.e. when this row is referenced from a <ref
3285 table="Flow_Sample_Collector_Set"/>.
3288 <column name="obs_domain_id">
3289 For per-bridge packet sampling, i.e. when this row is referenced
3290 from a <ref table="Bridge"/>, the IPFIX Observation Domain ID
3291 sent in each IPFIX packet. If not specified, defaults to 0.
3292 Ignored for per-flow sampling, i.e. when this row is referenced
3293 from a <ref table="Flow_Sample_Collector_Set"/>.
3296 <column name="obs_point_id">
3297 For per-bridge packet sampling, i.e. when this row is referenced
3298 from a <ref table="Bridge"/>, the IPFIX Observation Point ID
3299 sent in each IPFIX flow record. If not specified, defaults to
3300 0. Ignored for per-flow sampling, i.e. when this row is
3301 referenced from a <ref table="Flow_Sample_Collector_Set"/>.
3304 <group title="Common Columns">
3305 The overall purpose of these columns is described under <code>Common
3306 Columns</code> at the beginning of this document.
3308 <column name="external_ids"/>
3312 <table name="Flow_Sample_Collector_Set">
3313 <p>A set of IPFIX collectors of packet samples generated by
3314 OpenFlow <code>sample</code> actions.</p>
3317 The ID of this collector set, unique among the bridge's
3318 collector sets, to be used as the <code>collector_set_id</code>
3319 in OpenFlow <code>sample</code> actions.
3322 <column name="bridge">
3323 The bridge into which OpenFlow <code>sample</code> actions can
3324 be added to send packet samples to this set of IPFIX collectors.
3327 <column name="ipfix">
3328 Configuration of the set of IPFIX collectors to send one flow
3329 record per sampled packet to.
3332 <group title="Common Columns">
3333 The overall purpose of these columns is described under <code>Common
3334 Columns</code> at the beginning of this document.
3336 <column name="external_ids"/>