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>.
75 <column name="other_config" key="stats-update-interval"
76 type='{"type": "integer", "minInteger": 5000}'>
78 Interval for updating statistics to the database, in milliseconds.
79 This option will affect the update of the <code>statistics</code>
80 column in the following tables: <code>Port</code>, <code>Interface
81 </code>, <code>Mirror</code>.
84 Default value is 5000 ms.
87 Getting statistics more frequently can be achieved via OpenFlow.
91 <column name="other_config" key="flow-restore-wait"
92 type='{"type": "boolean"}'>
94 When <code>ovs-vswitchd</code> starts up, it has an empty flow table
95 and therefore it handles all arriving packets in its default fashion
96 according to its configuration, by dropping them or sending them to
97 an OpenFlow controller or switching them as a standalone switch.
98 This behavior is ordinarily desirable. However, if
99 <code>ovs-vswitchd</code> is restarting as part of a ``hot-upgrade,''
100 then this leads to a relatively long period during which packets are
104 This option allows for improvement. When <code>ovs-vswitchd</code>
105 starts with this value set as <code>true</code>, it will neither
106 flush or expire previously set datapath flows nor will it send and
107 receive any packets to or from the datapath. When this value is
108 later set to <code>false</code>, <code>ovs-vswitchd</code> will
109 start receiving packets from the datapath and re-setup the flows.
112 Thus, with this option, the procedure for a hot-upgrade of
113 <code>ovs-vswitchd</code> becomes roughly the following:
117 Stop <code>ovs-vswitchd</code>.
120 Set <ref column="other_config" key="flow-restore-wait"/>
121 to <code>true</code>.
124 Start <code>ovs-vswitchd</code>.
127 Use <code>ovs-ofctl</code> (or some other program, such as an
128 OpenFlow controller) to restore the OpenFlow flow table
129 to the desired state.
132 Set <ref column="other_config" key="flow-restore-wait"/>
133 to <code>false</code> (or remove it entirely from the database).
137 The <code>ovs-ctl</code>'s ``restart'' and ``force-reload-kmod''
138 functions use the above config option during hot upgrades.
142 <column name="other_config" key="flow-limit"
143 type='{"type": "integer", "minInteger": 0}'>
146 number of flows allowed in the datapath flow table. Internally OVS
147 will choose a flow limit which will likely be lower than this number,
148 based on real time network conditions.
151 The default is 200000.
155 <column name="other_config" key="n-handler-threads"
156 type='{"type": "integer", "minInteger": 1}'>
158 Specifies the number of threads for software datapaths to use for
159 handling new flows. The default the number of online CPU cores minus
160 the number of revalidators.
163 This configuration is per datapath. If you have more than one
164 software datapath (e.g. some <code>system</code> bridges and some
165 <code>netdev</code> bridges), then the total number of threads is
166 <code>n-handler-threads</code> times the number of software
171 <column name="other_config" key="n-revalidator-threads"
172 type='{"type": "integer", "minInteger": 1}'>
174 Specifies the number of threads for software datapaths to use for
175 revalidating flows in the datapath. Typically, there is a direct
176 correlation between the number of revalidator threads, and the number
177 of flows allowed in the datapath. The default is the number of cpu
178 cores divided by four plus one. If <code>n-handler-threads</code> is
179 set, the default changes to the number of cpu cores minus the number
183 This configuration is per datapath. If you have more than one
184 software datapath (e.g. some <code>system</code> bridges and some
185 <code>netdev</code> bridges), then the total number of threads is
186 <code>n-handler-threads</code> times the number of software
192 <group title="Status">
193 <column name="next_cfg">
194 Sequence number for client to increment. When a client modifies
195 any part of the database configuration and wishes to wait for
196 Open vSwitch to finish applying the changes, it may increment
197 this sequence number.
200 <column name="cur_cfg">
201 Sequence number that Open vSwitch sets to the current value of
202 <ref column="next_cfg"/> after it finishes applying a set of
203 configuration changes.
206 <group title="Statistics">
208 The <code>statistics</code> column contains key-value pairs that
209 report statistics about a system running an Open vSwitch. These are
210 updated periodically (currently, every 5 seconds). Key-value pairs
211 that cannot be determined or that do not apply to a platform are
215 <column name="other_config" key="enable-statistics"
216 type='{"type": "boolean"}'>
217 Statistics are disabled by default to avoid overhead in the common
218 case when statistics gathering is not useful. Set this value to
219 <code>true</code> to enable populating the <ref column="statistics"/>
220 column or to <code>false</code> to explicitly disable it.
223 <column name="statistics" key="cpu"
224 type='{"type": "integer", "minInteger": 1}'>
226 Number of CPU processors, threads, or cores currently online and
227 available to the operating system on which Open vSwitch is running,
228 as an integer. This may be less than the number installed, if some
229 are not online or if they are not available to the operating
233 Open vSwitch userspace processes are not multithreaded, but the
234 Linux kernel-based datapath is.
238 <column name="statistics" key="load_average">
239 A comma-separated list of three floating-point numbers,
240 representing the system load average over the last 1, 5, and 15
241 minutes, respectively.
244 <column name="statistics" key="memory">
246 A comma-separated list of integers, each of which represents a
247 quantity of memory in kilobytes that describes the operating
248 system on which Open vSwitch is running. In respective order,
253 <li>Total amount of RAM allocated to the OS.</li>
254 <li>RAM allocated to the OS that is in use.</li>
255 <li>RAM that can be flushed out to disk or otherwise discarded
256 if that space is needed for another purpose. This number is
257 necessarily less than or equal to the previous value.</li>
258 <li>Total disk space allocated for swap.</li>
259 <li>Swap space currently in use.</li>
263 On Linux, all five values can be determined and are included. On
264 other operating systems, only the first two values can be
265 determined, so the list will only have two values.
269 <column name="statistics" key="process_NAME">
271 One such key-value pair, with <code>NAME</code> replaced by
272 a process name, will exist for each running Open vSwitch
273 daemon process, with <var>name</var> replaced by the
274 daemon's name (e.g. <code>process_ovs-vswitchd</code>). The
275 value is a comma-separated list of integers. The integers
276 represent the following, with memory measured in kilobytes
277 and durations in milliseconds:
281 <li>The process's virtual memory size.</li>
282 <li>The process's resident set size.</li>
283 <li>The amount of user and system CPU time consumed by the
285 <li>The number of times that the process has crashed and been
286 automatically restarted by the monitor.</li>
287 <li>The duration since the process was started.</li>
288 <li>The duration for which the process has been running.</li>
292 The interpretation of some of these values depends on whether the
293 process was started with the <option>--monitor</option>. If it
294 was not, then the crash count will always be 0 and the two
295 durations will always be the same. If <option>--monitor</option>
296 was given, then the crash count may be positive; if it is, the
297 latter duration is the amount of time since the most recent crash
302 There will be one key-value pair for each file in Open vSwitch's
303 ``run directory'' (usually <code>/var/run/openvswitch</code>)
304 whose name ends in <code>.pid</code>, whose contents are a
305 process ID, and which is locked by a running process. The
306 <var>name</var> is taken from the pidfile's name.
310 Currently Open vSwitch is only able to obtain all of the above
311 detail on Linux systems. On other systems, the same key-value
312 pairs will be present but the values will always be the empty
317 <column name="statistics" key="file_systems">
319 A space-separated list of information on local, writable file
320 systems. Each item in the list describes one file system and
321 consists in turn of a comma-separated list of the following:
325 <li>Mount point, e.g. <code>/</code> or <code>/var/log</code>.
326 Any spaces or commas in the mount point are replaced by
328 <li>Total size, in kilobytes, as an integer.</li>
329 <li>Amount of storage in use, in kilobytes, as an integer.</li>
333 This key-value pair is omitted if there are no local, writable
334 file systems or if Open vSwitch cannot obtain the needed
341 <group title="Version Reporting">
343 These columns report the types and versions of the hardware and
344 software running Open vSwitch. We recommend in general that software
345 should test whether specific features are supported instead of relying
346 on version number checks. These values are primarily intended for
347 reporting to human administrators.
350 <column name="ovs_version">
351 The Open vSwitch version number, e.g. <code>1.1.0</code>.
354 <column name="db_version">
356 The database schema version number in the form
357 <code><var>major</var>.<var>minor</var>.<var>tweak</var></code>,
358 e.g. <code>1.2.3</code>. Whenever the database schema is changed in
359 a non-backward compatible way (e.g. deleting a column or a table),
360 <var>major</var> is incremented. When the database schema is changed
361 in a backward compatible way (e.g. adding a new column),
362 <var>minor</var> is incremented. When the database schema is changed
363 cosmetically (e.g. reindenting its syntax), <var>tweak</var> is
368 The schema version is part of the database schema, so it can also be
369 retrieved by fetching the schema using the Open vSwitch database
374 <column name="system_type">
376 An identifier for the type of system on top of which Open vSwitch
377 runs, e.g. <code>XenServer</code> or <code>KVM</code>.
380 System integrators are responsible for choosing and setting an
381 appropriate value for this column.
385 <column name="system_version">
387 The version of the system identified by <ref column="system_type"/>,
388 e.g. <code>5.6.100-39265p</code> on XenServer 5.6.100 build 39265.
391 System integrators are responsible for choosing and setting an
392 appropriate value for this column.
398 <group title="Database Configuration">
400 These columns primarily configure the Open vSwitch database
401 (<code>ovsdb-server</code>), not the Open vSwitch switch
402 (<code>ovs-vswitchd</code>). The OVSDB database also uses the <ref
403 column="ssl"/> settings.
407 The Open vSwitch switch does read the database configuration to
408 determine remote IP addresses to which in-band control should apply.
411 <column name="manager_options">
412 Database clients to which the Open vSwitch database server should
413 connect or to which it should listen, along with options for how these
414 connection should be configured. See the <ref table="Manager"/> table
415 for more information.
419 <group title="Common Columns">
420 The overall purpose of these columns is described under <code>Common
421 Columns</code> at the beginning of this document.
423 <column name="other_config"/>
424 <column name="external_ids"/>
428 <table name="Bridge">
430 Configuration for a bridge within an
431 <ref table="Open_vSwitch"/>.
434 A <ref table="Bridge"/> record represents an Ethernet switch with one or
435 more ``ports,'' which are the <ref table="Port"/> records pointed to by
436 the <ref table="Bridge"/>'s <ref column="ports"/> column.
439 <group title="Core Features">
441 Bridge identifier. Should be alphanumeric and no more than about 8
442 bytes long. Must be unique among the names of ports, interfaces, and
446 <column name="ports">
447 Ports included in the bridge.
450 <column name="mirrors">
451 Port mirroring configuration.
454 <column name="netflow">
455 NetFlow configuration.
458 <column name="sflow">
459 sFlow(R) configuration.
462 <column name="ipfix">
466 <column name="flood_vlans">
468 VLAN IDs of VLANs on which MAC address learning should be disabled,
469 so that packets are flooded instead of being sent to specific ports
470 that are believed to contain packets' destination MACs. This should
471 ordinarily be used to disable MAC learning on VLANs used for
472 mirroring (RSPAN VLANs). It may also be useful for debugging.
475 SLB bonding (see the <ref table="Port" column="bond_mode"/> column in
476 the <ref table="Port"/> table) is incompatible with
477 <code>flood_vlans</code>. Consider using another bonding mode or
478 a different type of mirror instead.
483 <group title="OpenFlow Configuration">
484 <column name="controller">
486 OpenFlow controller set. If unset, then no OpenFlow controllers
491 If there are primary controllers, removing all of them clears the
492 flow table. If there are no primary controllers, adding one also
493 clears the flow table. Other changes to the set of controllers, such
494 as adding or removing a service controller, adding another primary
495 controller to supplement an existing primary controller, or removing
496 only one of two primary controllers, have no effect on the flow
501 <column name="flow_tables">
502 Configuration for OpenFlow tables. Each pair maps from an OpenFlow
503 table ID to configuration for that table.
506 <column name="fail_mode">
507 <p>When a controller is configured, it is, ordinarily, responsible
508 for setting up all flows on the switch. Thus, if the connection to
509 the controller fails, no new network connections can be set up.
510 If the connection to the controller stays down long enough,
511 no packets can pass through the switch at all. This setting
512 determines the switch's response to such a situation. It may be set
513 to one of the following:
515 <dt><code>standalone</code></dt>
516 <dd>If no message is received from the controller for three
517 times the inactivity probe interval
518 (see <ref column="inactivity_probe"/>), then Open vSwitch
519 will take over responsibility for setting up flows. In
520 this mode, Open vSwitch causes the bridge to act like an
521 ordinary MAC-learning switch. Open vSwitch will continue
522 to retry connecting to the controller in the background
523 and, when the connection succeeds, it will discontinue its
524 standalone behavior.</dd>
525 <dt><code>secure</code></dt>
526 <dd>Open vSwitch will not set up flows on its own when the
527 controller connection fails or when no controllers are
528 defined. The bridge will continue to retry connecting to
529 any defined controllers forever.</dd>
533 The default is <code>standalone</code> if the value is unset, but
534 future versions of Open vSwitch may change the default.
537 The <code>standalone</code> mode can create forwarding loops on a
538 bridge that has more than one uplink port unless STP is enabled. To
539 avoid loops on such a bridge, configure <code>secure</code> mode or
540 enable STP (see <ref column="stp_enable"/>).
542 <p>When more than one controller is configured,
543 <ref column="fail_mode"/> is considered only when none of the
544 configured controllers can be contacted.</p>
546 Changing <ref column="fail_mode"/> when no primary controllers are
547 configured clears the flow table.
551 <column name="datapath_id">
552 Reports the OpenFlow datapath ID in use. Exactly 16 hex digits.
553 (Setting this column has no useful effect. Set <ref
554 column="other-config" key="datapath-id"/> instead.)
557 <column name="other_config" key="datapath-id">
558 Exactly 16 hex digits to set the OpenFlow datapath ID to a specific
559 value. May not be all-zero.
562 <column name="other_config" key="dp-desc">
563 Human readable description of datapath. It it a maximum 256
564 byte-long free-form string to describe the datapath for
565 debugging purposes, e.g. <code>switch3 in room 3120</code>.
568 <column name="other_config" key="disable-in-band"
569 type='{"type": "boolean"}'>
570 If set to <code>true</code>, disable in-band control on the bridge
571 regardless of controller and manager settings.
574 <column name="other_config" key="in-band-queue"
575 type='{"type": "integer", "minInteger": 0, "maxInteger": 4294967295}'>
576 A queue ID as a nonnegative integer. This sets the OpenFlow queue ID
577 that will be used by flows set up by in-band control on this bridge.
578 If unset, or if the port used by an in-band control flow does not have
579 QoS configured, or if the port does not have a queue with the specified
580 ID, the default queue is used instead.
583 <column name="protocols">
585 List of OpenFlow protocols that may be used when negotiating
586 a connection with a controller. OpenFlow 1.0, 1.1, 1.2, and
587 1.3 are enabled by default if this column is empty.
591 OpenFlow 1.4 is not enabled by default because its implementation is
596 OpenFlow 1.5 has the same risks as OpenFlow 1.4, but it is even more
597 experimental because the OpenFlow 1.5 specification is still under
598 development and thus subject to change. Pass
599 <code>--enable-of15</code> to <code>ovs-vswitchd</code> to allow
600 OpenFlow 1.5 to be enabled.
605 <group title="Spanning Tree Configuration">
606 The IEEE 802.1D Spanning Tree Protocol (STP) is a network protocol
607 that ensures loop-free topologies. It allows redundant links to
608 be included in the network to provide automatic backup paths if
609 the active links fails.
611 <column name="stp_enable">
612 Enable spanning tree on the bridge. By default, STP is disabled
613 on bridges. Bond, internal, and mirror ports are not supported
614 and will not participate in the spanning tree.
617 <column name="other_config" key="stp-system-id">
618 The bridge's STP identifier (the lower 48 bits of the bridge-id)
620 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>.
621 By default, the identifier is the MAC address of the bridge.
624 <column name="other_config" key="stp-priority"
625 type='{"type": "integer", "minInteger": 0, "maxInteger": 65535}'>
626 The bridge's relative priority value for determining the root
627 bridge (the upper 16 bits of the bridge-id). A bridge with the
628 lowest bridge-id is elected the root. By default, the priority
632 <column name="other_config" key="stp-hello-time"
633 type='{"type": "integer", "minInteger": 1, "maxInteger": 10}'>
634 The interval between transmissions of hello messages by
635 designated ports, in seconds. By default the hello interval is
639 <column name="other_config" key="stp-max-age"
640 type='{"type": "integer", "minInteger": 6, "maxInteger": 40}'>
641 The maximum age of the information transmitted by the bridge
642 when it is the root bridge, in seconds. By default, the maximum
646 <column name="other_config" key="stp-forward-delay"
647 type='{"type": "integer", "minInteger": 4, "maxInteger": 30}'>
648 The delay to wait between transitioning root and designated
649 ports to <code>forwarding</code>, in seconds. By default, the
650 forwarding delay is 15 seconds.
653 <column name="other_config" key="mcast-snooping-aging-time"
654 type='{"type": "integer", "minInteger": 1}'>
656 The maximum number of seconds to retain a multicast snooping entry for
657 which no packets have been seen. The default is currently 300
658 seconds (5 minutes). The value, if specified, is forced into a
659 reasonable range, currently 15 to 3600 seconds.
663 <column name="other_config" key="mcast-snooping-table-size"
664 type='{"type": "integer", "minInteger": 1}'>
666 The maximum number of multicast snooping addresses to learn. The
667 default is currently 2048. The value, if specified, is forced into
668 a reasonable range, currently 10 to 1,000,000.
671 <column name="other_config" key="mcast-snooping-disable-flood-unregistered"
672 type='{"type": "boolean"}'>
674 If set to <code>false</code>, unregistered multicast packets are forwarded
676 If set to <code>true</code>, unregistered multicast packets are forwarded
677 to ports connected to multicast routers.
682 <group title="Multicast Snooping Configuration">
683 Multicast snooping (RFC 4541) monitors the Internet Group Management
684 Protocol (IGMP) traffic between hosts and multicast routers. The
685 switch uses what IGMP snooping learns to forward multicast traffic
686 only to interfaces that are connected to interested receivers.
687 Currently it supports IGMPv1 and IGMPv2 protocols.
689 <column name="mcast_snooping_enable">
690 Enable multicast snooping on the bridge. For now, the default
695 <group title="Other Features">
696 <column name="datapath_type">
697 Name of datapath provider. The kernel datapath has
698 type <code>system</code>. The userspace datapath has
699 type <code>netdev</code>.
702 <column name="external_ids" key="bridge-id">
703 A unique identifier of the bridge. On Citrix XenServer this will
704 commonly be the same as
705 <ref column="external_ids" key="xs-network-uuids"/>.
708 <column name="external_ids" key="xs-network-uuids">
709 Semicolon-delimited set of universally unique identifier(s) for the
710 network with which this bridge is associated on a Citrix XenServer
711 host. The network identifiers are RFC 4122 UUIDs as displayed by,
712 e.g., <code>xe network-list</code>.
715 <column name="other_config" key="hwaddr">
716 An Ethernet address in the form
717 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>
718 to set the hardware address of the local port and influence the
722 <column name="other_config" key="forward-bpdu"
723 type='{"type": "boolean"}'>
724 Option to allow forwarding of BPDU frames when NORMAL action is
725 invoked. Frames with reserved Ethernet addresses (e.g. STP
726 BPDU) will be forwarded when this option is enabled and the
727 switch is not providing that functionality. If STP is enabled
728 on the port, STP BPDUs will never be forwarded. If the Open
729 vSwitch bridge is used to connect different Ethernet networks,
730 and if Open vSwitch node does not run STP, then this option
731 should be enabled. Default is disabled, set to
732 <code>true</code> to enable.
734 The following destination MAC addresss will not be forwarded when this
737 <dt><code>01:80:c2:00:00:00</code></dt>
738 <dd>IEEE 802.1D Spanning Tree Protocol (STP).</dd>
740 <dt><code>01:80:c2:00:00:01</code></dt>
741 <dd>IEEE Pause frame.</dd>
743 <dt><code>01:80:c2:00:00:0<var>x</var></code></dt>
744 <dd>Other reserved protocols.</dd>
746 <dt><code>00:e0:2b:00:00:00</code></dt>
747 <dd>Extreme Discovery Protocol (EDP).</dd>
750 <code>00:e0:2b:00:00:04</code> and <code>00:e0:2b:00:00:06</code>
752 <dd>Ethernet Automatic Protection Switching (EAPS).</dd>
754 <dt><code>01:00:0c:cc:cc:cc</code></dt>
756 Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP),
757 Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAgP),
761 <dt><code>01:00:0c:cc:cc:cd</code></dt>
762 <dd>Cisco Shared Spanning Tree Protocol PVSTP+.</dd>
764 <dt><code>01:00:0c:cd:cd:cd</code></dt>
765 <dd>Cisco STP Uplink Fast.</dd>
767 <dt><code>01:00:0c:00:00:00</code></dt>
768 <dd>Cisco Inter Switch Link.</dd>
770 <dt><code>01:00:0c:cc:cc:c<var>x</var></code></dt>
775 <column name="other_config" key="mac-aging-time"
776 type='{"type": "integer", "minInteger": 1}'>
778 The maximum number of seconds to retain a MAC learning entry for
779 which no packets have been seen. The default is currently 300
780 seconds (5 minutes). The value, if specified, is forced into a
781 reasonable range, currently 15 to 3600 seconds.
785 A short MAC aging time allows a network to more quickly detect that a
786 host is no longer connected to a switch port. However, it also makes
787 it more likely that packets will be flooded unnecessarily, when they
788 are addressed to a connected host that rarely transmits packets. To
789 reduce the incidence of unnecessary flooding, use a MAC aging time
790 longer than the maximum interval at which a host will ordinarily
795 <column name="other_config" key="mac-table-size"
796 type='{"type": "integer", "minInteger": 1}'>
798 The maximum number of MAC addresses to learn. The default is
799 currently 2048. The value, if specified, is forced into a reasonable
800 range, currently 10 to 1,000,000.
805 <group title="Bridge Status">
807 Status information about bridges.
809 <column name="status">
810 Key-value pairs that report bridge status.
812 <column name="status" key="stp_bridge_id">
814 The bridge-id (in hex) used in spanning tree advertisements.
815 Configuring the bridge-id is described in the
816 <code>stp-system-id</code> and <code>stp-priority</code> keys
817 of the <code>other_config</code> section earlier.
820 <column name="status" key="stp_designated_root">
822 The designated root (in hex) for this spanning tree.
825 <column name="status" key="stp_root_path_cost">
827 The path cost of reaching the designated bridge. A lower
833 <group title="Common Columns">
834 The overall purpose of these columns is described under <code>Common
835 Columns</code> at the beginning of this document.
837 <column name="other_config"/>
838 <column name="external_ids"/>
842 <table name="Port" table="Port or bond configuration.">
843 <p>A port within a <ref table="Bridge"/>.</p>
844 <p>Most commonly, a port has exactly one ``interface,'' pointed to by its
845 <ref column="interfaces"/> column. Such a port logically
846 corresponds to a port on a physical Ethernet switch. A port
847 with more than one interface is a ``bonded port'' (see
848 <ref group="Bonding Configuration"/>).</p>
849 <p>Some properties that one might think as belonging to a port are actually
850 part of the port's <ref table="Interface"/> members.</p>
853 Port name. Should be alphanumeric and no more than about 8
854 bytes long. May be the same as the interface name, for
855 non-bonded ports. Must otherwise be unique among the names of
856 ports, interfaces, and bridges on a host.
859 <column name="interfaces">
860 The port's interfaces. If there is more than one, this is a
864 <group title="VLAN Configuration">
865 <p>Bridge ports support the following types of VLAN configuration:</p>
870 A trunk port carries packets on one or more specified VLANs
871 specified in the <ref column="trunks"/> column (often, on every
872 VLAN). A packet that ingresses on a trunk port is in the VLAN
873 specified in its 802.1Q header, or VLAN 0 if the packet has no
874 802.1Q header. A packet that egresses through a trunk port will
875 have an 802.1Q header if it has a nonzero VLAN ID.
879 Any packet that ingresses on a trunk port tagged with a VLAN that
880 the port does not trunk is dropped.
887 An access port carries packets on exactly one VLAN specified in the
888 <ref column="tag"/> column. Packets egressing on an access port
889 have no 802.1Q header.
893 Any packet with an 802.1Q header with a nonzero VLAN ID that
894 ingresses on an access port is dropped, regardless of whether the
895 VLAN ID in the header is the access port's VLAN ID.
899 <dt>native-tagged</dt>
901 A native-tagged port resembles a trunk port, with the exception that
902 a packet without an 802.1Q header that ingresses on a native-tagged
903 port is in the ``native VLAN'' (specified in the <ref column="tag"/>
907 <dt>native-untagged</dt>
909 A native-untagged port resembles a native-tagged port, with the
910 exception that a packet that egresses on a native-untagged port in
911 the native VLAN will not have an 802.1Q header.
915 A packet will only egress through bridge ports that carry the VLAN of
916 the packet, as described by the rules above.
919 <column name="vlan_mode">
921 The VLAN mode of the port, as described above. When this column is
922 empty, a default mode is selected as follows:
926 If <ref column="tag"/> contains a value, the port is an access
927 port. The <ref column="trunks"/> column should be empty.
930 Otherwise, the port is a trunk port. The <ref column="trunks"/>
931 column value is honored if it is present.
938 For an access port, the port's implicitly tagged VLAN. For a
939 native-tagged or native-untagged port, the port's native VLAN. Must
940 be empty if this is a trunk port.
944 <column name="trunks">
946 For a trunk, native-tagged, or native-untagged port, the 802.1Q VLAN
947 or VLANs that this port trunks; if it is empty, then the port trunks
948 all VLANs. Must be empty if this is an access port.
951 A native-tagged or native-untagged port always trunks its native
952 VLAN, regardless of whether <ref column="trunks"/> includes that
957 <column name="other_config" key="priority-tags"
958 type='{"type": "boolean"}'>
960 An 802.1Q header contains two important pieces of information: a VLAN
961 ID and a priority. A frame with a zero VLAN ID, called a
962 ``priority-tagged'' frame, is supposed to be treated the same way as
963 a frame without an 802.1Q header at all (except for the priority).
967 However, some network elements ignore any frame that has 802.1Q
968 header at all, even when the VLAN ID is zero. Therefore, by default
969 Open vSwitch does not output priority-tagged frames, instead omitting
970 the 802.1Q header entirely if the VLAN ID is zero. Set this key to
971 <code>true</code> to enable priority-tagged frames on a port.
975 Regardless of this setting, Open vSwitch omits the 802.1Q header on
976 output if both the VLAN ID and priority would be zero.
980 All frames output to native-tagged ports have a nonzero VLAN ID, so
981 this setting is not meaningful on native-tagged ports.
986 <group title="Bonding Configuration">
987 <p>A port that has more than one interface is a ``bonded port.'' Bonding
988 allows for load balancing and fail-over.</p>
991 The following types of bonding will work with any kind of upstream
992 switch. On the upstream switch, do not configure the interfaces as a
997 <dt><code>balance-slb</code></dt>
999 Balances flows among slaves based on source MAC address and output
1000 VLAN, with periodic rebalancing as traffic patterns change.
1003 <dt><code>active-backup</code></dt>
1005 Assigns all flows to one slave, failing over to a backup slave when
1006 the active slave is disabled. This is the only bonding mode in which
1007 interfaces may be plugged into different upstream switches.
1012 The following modes require the upstream switch to support 802.3ad with
1013 successful LACP negotiation. If LACP negotiation fails and
1014 other-config:lacp-fallback-ab is true, then <code>active-backup</code>
1019 <dt><code>balance-tcp</code></dt>
1021 Balances flows among slaves based on L2, L3, and L4 protocol
1022 information such as destination MAC address, IP address, and TCP
1027 <p>These columns apply only to bonded ports. Their values are
1028 otherwise ignored.</p>
1030 <column name="bond_mode">
1031 <p>The type of bonding used for a bonded port. Defaults to
1032 <code>active-backup</code> if unset.
1036 <column name="other_config" key="bond-hash-basis"
1037 type='{"type": "integer"}'>
1038 An integer hashed along with flows when choosing output slaves in load
1039 balanced bonds. When changed, all flows will be assigned different
1040 hash values possibly causing slave selection decisions to change. Does
1041 not affect bonding modes which do not employ load balancing such as
1042 <code>active-backup</code>.
1045 <group title="Link Failure Detection">
1047 An important part of link bonding is detecting that links are down so
1048 that they may be disabled. These settings determine how Open vSwitch
1049 detects link failure.
1052 <column name="other_config" key="bond-detect-mode"
1053 type='{"type": "string", "enum": ["set", ["carrier", "miimon"]]}'>
1054 The means used to detect link failures. Defaults to
1055 <code>carrier</code> which uses each interface's carrier to detect
1056 failures. When set to <code>miimon</code>, will check for failures
1057 by polling each interface's MII.
1060 <column name="other_config" key="bond-miimon-interval"
1061 type='{"type": "integer"}'>
1062 The interval, in milliseconds, between successive attempts to poll
1063 each interface's MII. Relevant only when <ref column="other_config"
1064 key="bond-detect-mode"/> is <code>miimon</code>.
1067 <column name="bond_updelay">
1069 The number of milliseconds for which the link must stay up on an
1070 interface before the interface is considered to be up. Specify
1071 <code>0</code> to enable the interface immediately.
1075 This setting is honored only when at least one bonded interface is
1076 already enabled. When no interfaces are enabled, then the first
1077 bond interface to come up is enabled immediately.
1081 <column name="bond_downdelay">
1082 The number of milliseconds for which the link must stay down on an
1083 interface before the interface is considered to be down. Specify
1084 <code>0</code> to disable the interface immediately.
1088 <group title="LACP Configuration">
1090 LACP, the Link Aggregation Control Protocol, is an IEEE standard that
1091 allows switches to automatically detect that they are connected by
1092 multiple links and aggregate across those links. These settings
1093 control LACP behavior.
1096 <column name="lacp">
1097 Configures LACP on this port. LACP allows directly connected
1098 switches to negotiate which links may be bonded. LACP may be enabled
1099 on non-bonded ports for the benefit of any switches they may be
1100 connected to. <code>active</code> ports are allowed to initiate LACP
1101 negotiations. <code>passive</code> ports are allowed to participate
1102 in LACP negotiations initiated by a remote switch, but not allowed to
1103 initiate such negotiations themselves. If LACP is enabled on a port
1104 whose partner switch does not support LACP, the bond will be
1105 disabled, unless other-config:lacp-fallback-ab is set to true.
1106 Defaults to <code>off</code> if unset.
1109 <column name="other_config" key="lacp-system-id">
1110 The LACP system ID of this <ref table="Port"/>. The system ID of a
1111 LACP bond is used to identify itself to its partners. Must be a
1112 nonzero MAC address. Defaults to the bridge Ethernet address if
1116 <column name="other_config" key="lacp-system-priority"
1117 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
1118 The LACP system priority of this <ref table="Port"/>. In LACP
1119 negotiations, link status decisions are made by the system with the
1120 numerically lower priority.
1123 <column name="other_config" key="lacp-time"
1124 type='{"type": "string", "enum": ["set", ["fast", "slow"]]}'>
1126 The LACP timing which should be used on this <ref table="Port"/>.
1127 By default <code>slow</code> is used. When configured to be
1128 <code>fast</code> LACP heartbeats are requested at a rate of once
1129 per second causing connectivity problems to be detected more
1130 quickly. In <code>slow</code> mode, heartbeats are requested at a
1131 rate of once every 30 seconds.
1135 <column name="other_config" key="lacp-fallback-ab"
1136 type='{"type": "boolean"}'>
1138 Determines the behavior of openvswitch bond in LACP mode. If
1139 the partner switch does not support LACP, setting this option
1140 to <code>true</code> allows openvswitch to fallback to
1141 active-backup. If the option is set to <code>false</code>, the
1142 bond will be disabled. In both the cases, once the partner switch
1143 is configured to LACP mode, the bond will use LACP.
1148 <group title="Rebalancing Configuration">
1150 These settings control behavior when a bond is in
1151 <code>balance-slb</code> or <code>balance-tcp</code> mode.
1154 <column name="other_config" key="bond-rebalance-interval"
1155 type='{"type": "integer", "minInteger": 0, "maxInteger": 10000}'>
1156 For a load balanced bonded port, the number of milliseconds between
1157 successive attempts to rebalance the bond, that is, to move flows
1158 from one interface on the bond to another in an attempt to keep usage
1159 of each interface roughly equal. If zero, load balancing is disabled
1160 on the bond (link failure still cause flows to move). If
1161 less than 1000ms, the rebalance interval will be 1000ms.
1165 <column name="bond_fake_iface">
1166 For a bonded port, whether to create a fake internal interface with the
1167 name of the port. Use only for compatibility with legacy software that
1172 <group title="Spanning Tree Configuration">
1173 <column name="other_config" key="stp-enable"
1174 type='{"type": "boolean"}'>
1175 If spanning tree is enabled on the bridge, member ports are
1176 enabled by default (with the exception of bond, internal, and
1177 mirror ports which do not work with STP). If this column's
1178 value is <code>false</code> spanning tree is disabled on the
1182 <column name="other_config" key="stp-port-num"
1183 type='{"type": "integer", "minInteger": 1, "maxInteger": 255}'>
1184 The port number used for the lower 8 bits of the port-id. By
1185 default, the numbers will be assigned automatically. If any
1186 port's number is manually configured on a bridge, then they
1190 <column name="other_config" key="stp-port-priority"
1191 type='{"type": "integer", "minInteger": 0, "maxInteger": 255}'>
1192 The port's relative priority value for determining the root
1193 port (the upper 8 bits of the port-id). A port with a lower
1194 port-id will be chosen as the root port. By default, the
1198 <column name="other_config" key="stp-path-cost"
1199 type='{"type": "integer", "minInteger": 0, "maxInteger": 65535}'>
1200 Spanning tree path cost for the port. A lower number indicates
1201 a faster link. By default, the cost is based on the maximum
1205 <group title="Multicast Snooping">
1206 <column name="other_config" key="mcast-snooping-flood"
1207 type='{"type": "boolean"}'>
1209 If set to <code>true</code>, multicast packets are unconditionally
1210 forwarded to the specific port.
1215 <group title="Other Features">
1217 Quality of Service configuration for this port.
1221 The MAC address to use for this port for the purpose of choosing the
1222 bridge's MAC address. This column does not necessarily reflect the
1223 port's actual MAC address, nor will setting it change the port's actual
1227 <column name="fake_bridge">
1228 Does this port represent a sub-bridge for its tagged VLAN within the
1229 Bridge? See ovs-vsctl(8) for more information.
1232 <column name="external_ids" key="fake-bridge-id-*">
1233 External IDs for a fake bridge (see the <ref column="fake_bridge"/>
1234 column) are defined by prefixing a <ref table="Bridge"/> <ref
1235 table="Bridge" column="external_ids"/> key with
1236 <code>fake-bridge-</code>,
1237 e.g. <code>fake-bridge-xs-network-uuids</code>.
1241 <group title="Port Status">
1243 Status information about ports attached to bridges.
1245 <column name="status">
1246 Key-value pairs that report port status.
1248 <column name="status" key="stp_port_id">
1250 The port-id (in hex) used in spanning tree advertisements for
1251 this port. Configuring the port-id is described in the
1252 <code>stp-port-num</code> and <code>stp-port-priority</code>
1253 keys of the <code>other_config</code> section earlier.
1256 <column name="status" key="stp_state"
1257 type='{"type": "string", "enum": ["set",
1258 ["disabled", "listening", "learning",
1259 "forwarding", "blocking"]]}'>
1261 STP state of the port.
1264 <column name="status" key="stp_sec_in_state"
1265 type='{"type": "integer", "minInteger": 0}'>
1267 The amount of time (in seconds) port has been in the current
1271 <column name="status" key="stp_role"
1272 type='{"type": "string", "enum": ["set",
1273 ["root", "designated", "alternate"]]}'>
1275 STP role of the port.
1280 <group title="Port Statistics">
1282 Key-value pairs that report port statistics. The update period
1283 is controlled by <ref column="other_config"
1284 key="stats-update-interval"/> in the <code>Open_vSwitch</code> table.
1286 <group title="Statistics: STP transmit and receive counters">
1287 <column name="statistics" key="stp_tx_count">
1288 Number of STP BPDUs sent on this port by the spanning
1291 <column name="statistics" key="stp_rx_count">
1292 Number of STP BPDUs received on this port and accepted by the
1293 spanning tree library.
1295 <column name="statistics" key="stp_error_count">
1296 Number of bad STP BPDUs received on this port. Bad BPDUs
1297 include runt packets and those with an unexpected protocol ID.
1302 <group title="Common Columns">
1303 The overall purpose of these columns is described under <code>Common
1304 Columns</code> at the beginning of this document.
1306 <column name="other_config"/>
1307 <column name="external_ids"/>
1311 <table name="Interface" title="One physical network device in a Port.">
1312 An interface within a <ref table="Port"/>.
1314 <group title="Core Features">
1315 <column name="name">
1316 Interface name. Should be alphanumeric and no more than about 8 bytes
1317 long. May be the same as the port name, for non-bonded ports. Must
1318 otherwise be unique among the names of ports, interfaces, and bridges
1322 <column name="ifindex">
1323 A positive interface index as defined for SNMP MIB-II in RFCs 1213 and
1324 2863, if the interface has one, otherwise 0. The ifindex is useful for
1325 seamless integration with protocols such as SNMP and sFlow.
1328 <column name="mac_in_use">
1329 The MAC address in use by this interface.
1333 <p>Ethernet address to set for this interface. If unset then the
1334 default MAC address is used:</p>
1336 <li>For the local interface, the default is the lowest-numbered MAC
1337 address among the other bridge ports, either the value of the
1338 <ref table="Port" column="mac"/> in its <ref table="Port"/> record,
1339 if set, or its actual MAC (for bonded ports, the MAC of its slave
1340 whose name is first in alphabetical order). Internal ports and
1341 bridge ports that are used as port mirroring destinations (see the
1342 <ref table="Mirror"/> table) are ignored.</li>
1343 <li>For other internal interfaces, the default MAC is randomly
1345 <li>External interfaces typically have a MAC address associated with
1346 their hardware.</li>
1348 <p>Some interfaces may not have a software-controllable MAC
1352 <column name="error">
1353 If the configuration of the port failed, as indicated by -1 in <ref
1354 column="ofport"/>, Open vSwitch sets this column to an error
1355 description in human readable form. Otherwise, Open vSwitch clears
1359 <group title="OpenFlow Port Number">
1361 When a client adds a new interface, Open vSwitch chooses an OpenFlow
1362 port number for the new port. If the client that adds the port fills
1363 in <ref column="ofport_request"/>, then Open vSwitch tries to use its
1364 value as the OpenFlow port number. Otherwise, or if the requested
1365 port number is already in use or cannot be used for another reason,
1366 Open vSwitch automatically assigns a free port number. Regardless of
1367 how the port number was obtained, Open vSwitch then reports in <ref
1368 column="ofport"/> the port number actually assigned.
1372 Open vSwitch limits the port numbers that it automatically assigns to
1373 the range 1 through 32,767, inclusive. Controllers therefore have
1374 free use of ports 32,768 and up.
1377 <column name="ofport">
1379 OpenFlow port number for this interface. Open vSwitch sets this
1380 column's value, so other clients should treat it as read-only.
1383 The OpenFlow ``local'' port (<code>OFPP_LOCAL</code>) is 65,534.
1384 The other valid port numbers are in the range 1 to 65,279,
1385 inclusive. Value -1 indicates an error adding the interface.
1389 <column name="ofport_request"
1390 type='{"type": "integer", "minInteger": 1, "maxInteger": 65279}'>
1392 Requested OpenFlow port number for this interface.
1396 A client should ideally set this column's value in the same
1397 database transaction that it uses to create the interface. Open
1398 vSwitch version 2.1 and later will honor a later request for a
1399 specific port number, althuogh it might confuse some controllers:
1400 OpenFlow does not have a way to announce a port number change, so
1401 Open vSwitch represents it over OpenFlow as a port deletion
1402 followed immediately by a port addition.
1406 If <ref column="ofport_request"/> is set or changed to some other
1407 port's automatically assigned port number, Open vSwitch chooses a
1408 new port number for the latter port.
1414 <group title="System-Specific Details">
1415 <column name="type">
1417 The interface type, one of:
1421 <dt><code>system</code></dt>
1422 <dd>An ordinary network device, e.g. <code>eth0</code> on Linux.
1423 Sometimes referred to as ``external interfaces'' since they are
1424 generally connected to hardware external to that on which the Open
1425 vSwitch is running. The empty string is a synonym for
1426 <code>system</code>.</dd>
1428 <dt><code>internal</code></dt>
1429 <dd>A simulated network device that sends and receives traffic. An
1430 internal interface whose <ref column="name"/> is the same as its
1431 bridge's <ref table="Open_vSwitch" column="name"/> is called the
1432 ``local interface.'' It does not make sense to bond an internal
1433 interface, so the terms ``port'' and ``interface'' are often used
1434 imprecisely for internal interfaces.</dd>
1436 <dt><code>tap</code></dt>
1437 <dd>A TUN/TAP device managed by Open vSwitch.</dd>
1439 <dt><code>geneve</code></dt>
1441 An Ethernet over Geneve (<code>http://tools.ietf.org/html/draft-gross-geneve-00</code>)
1444 Geneve supports options as a means to transport additional metadata,
1445 however, currently only the 24-bit VNI is supported. This is planned
1446 to be extended in the future.
1449 <dt><code>gre</code></dt>
1451 An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4
1455 <dt><code>ipsec_gre</code></dt>
1457 An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4
1461 <dt><code>gre64</code></dt>
1463 It is same as GRE, but it allows 64 bit key. To store higher 32-bits
1464 of key, it uses GRE protocol sequence number field. This is non
1465 standard use of GRE protocol since OVS does not increment
1466 sequence number for every packet at time of encap as expected by
1467 standard GRE implementation. See <ref group="Tunnel Options"/>
1468 for information on configuring GRE tunnels.
1471 <dt><code>ipsec_gre64</code></dt>
1473 Same as IPSEC_GRE except 64 bit key.
1476 <dt><code>vxlan</code></dt>
1479 An Ethernet tunnel over the experimental, UDP-based VXLAN
1480 protocol described at
1481 <code>http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-03</code>.
1484 Open vSwitch uses UDP destination port 4789. The source port used for
1485 VXLAN traffic varies on a per-flow basis and is in the ephemeral port
1490 <dt><code>lisp</code></dt>
1493 A layer 3 tunnel over the experimental, UDP-based Locator/ID
1494 Separation Protocol (RFC 6830).
1497 Only IPv4 and IPv6 packets are supported by the protocol, and
1498 they are sent and received without an Ethernet header. Traffic
1499 to/from LISP ports is expected to be configured explicitly, and
1500 the ports are not intended to participate in learning based
1501 switching. As such, they are always excluded from packet
1506 <dt><code>patch</code></dt>
1508 A pair of virtual devices that act as a patch cable.
1511 <dt><code>null</code></dt>
1512 <dd>An ignored interface. Deprecated and slated for removal in
1518 <group title="Tunnel Options">
1520 These options apply to interfaces with <ref column="type"/> of
1521 <code>geneve</code>, <code>gre</code>, <code>ipsec_gre</code>,
1522 <code>gre64</code>, <code>ipsec_gre64</code>, <code>vxlan</code>,
1523 and <code>lisp</code>.
1527 Each tunnel must be uniquely identified by the combination of <ref
1528 column="type"/>, <ref column="options" key="remote_ip"/>, <ref
1529 column="options" key="local_ip"/>, and <ref column="options"
1530 key="in_key"/>. If two ports are defined that are the same except one
1531 has an optional identifier and the other does not, the more specific
1532 one is matched first. <ref column="options" key="in_key"/> is
1533 considered more specific than <ref column="options" key="local_ip"/> if
1534 a port defines one and another port defines the other.
1537 <column name="options" key="remote_ip">
1538 <p>Required. The remote tunnel endpoint, one of:</p>
1542 An IPv4 address (not a DNS name), e.g. <code>192.168.0.123</code>.
1543 Only unicast endpoints are supported.
1546 The word <code>flow</code>. The tunnel accepts packets from any
1547 remote tunnel endpoint. To process only packets from a specific
1548 remote tunnel endpoint, the flow entries may match on the
1549 <code>tun_src</code> field. When sending packets to a
1550 <code>remote_ip=flow</code> tunnel, the flow actions must
1551 explicitly set the <code>tun_dst</code> field to the IP address of
1552 the desired remote tunnel endpoint, e.g. with a
1553 <code>set_field</code> action.
1558 The remote tunnel endpoint for any packet received from a tunnel
1559 is available in the <code>tun_src</code> field for matching in the
1564 <column name="options" key="local_ip">
1566 Optional. The tunnel destination IP that received packets must
1567 match. Default is to match all addresses. If specified, may be one
1573 An IPv4 address (not a DNS name), e.g. <code>192.168.12.3</code>.
1576 The word <code>flow</code>. The tunnel accepts packets sent to any
1577 of the local IP addresses of the system running OVS. To process
1578 only packets sent to a specific IP address, the flow entries may
1579 match on the <code>tun_dst</code> field. When sending packets to a
1580 <code>local_ip=flow</code> tunnel, the flow actions may
1581 explicitly set the <code>tun_src</code> field to the desired IP
1582 address, e.g. with a <code>set_field</code> action. However, while
1583 routing the tunneled packet out, the local system may override the
1584 specified address with the local IP address configured for the
1585 outgoing system interface.
1588 This option is valid only for tunnels also configured with the
1589 <code>remote_ip=flow</code> option.
1595 The tunnel destination IP address for any packet received from a
1596 tunnel is available in the <code>tun_dst</code> field for matching in
1601 <column name="options" key="in_key">
1602 <p>Optional. The key that received packets must contain, one of:</p>
1606 <code>0</code>. The tunnel receives packets with no key or with a
1607 key of 0. This is equivalent to specifying no <ref column="options"
1608 key="in_key"/> at all.
1611 A positive 24-bit (for Geneve, VXLAN, and LISP), 32-bit (for GRE)
1612 or 64-bit (for GRE64) number. The tunnel receives only packets
1613 with the specified key.
1616 The word <code>flow</code>. The tunnel accepts packets with any
1617 key. The key will be placed in the <code>tun_id</code> field for
1618 matching in the flow table. The <code>ovs-ofctl</code> manual page
1619 contains additional information about matching fields in OpenFlow
1628 <column name="options" key="out_key">
1629 <p>Optional. The key to be set on outgoing packets, one of:</p>
1633 <code>0</code>. Packets sent through the tunnel will have no key.
1634 This is equivalent to specifying no <ref column="options"
1635 key="out_key"/> at all.
1638 A positive 24-bit (for Geneve, VXLAN and LISP), 32-bit (for GRE) or
1639 64-bit (for GRE64) number. Packets sent through the tunnel will
1640 have the specified key.
1643 The word <code>flow</code>. Packets sent through the tunnel will
1644 have the key set using the <code>set_tunnel</code> Nicira OpenFlow
1645 vendor extension (0 is used in the absence of an action). The
1646 <code>ovs-ofctl</code> manual page contains additional information
1647 about the Nicira OpenFlow vendor extensions.
1652 <column name="options" key="key">
1653 Optional. Shorthand to set <code>in_key</code> and
1654 <code>out_key</code> at the same time.
1657 <column name="options" key="tos">
1658 Optional. The value of the ToS bits to be set on the encapsulating
1659 packet. ToS is interpreted as DSCP and ECN bits, ECN part must be
1660 zero. It may also be the word <code>inherit</code>, in which case
1661 the ToS will be copied from the inner packet if it is IPv4 or IPv6
1662 (otherwise it will be 0). The ECN fields are always inherited.
1666 <column name="options" key="ttl">
1667 Optional. The TTL to be set on the encapsulating packet. It may also
1668 be the word <code>inherit</code>, in which case the TTL will be copied
1669 from the inner packet if it is IPv4 or IPv6 (otherwise it will be the
1670 system default, typically 64). Default is the system default TTL.
1673 <column name="options" key="df_default"
1674 type='{"type": "boolean"}'>
1675 Optional. If enabled, the Don't Fragment bit will be set on tunnel
1676 outer headers to allow path MTU discovery. Default is enabled; set
1677 to <code>false</code> to disable.
1680 <group title="Tunnel Options: gre and ipsec_gre only">
1682 Only <code>gre</code> and <code>ipsec_gre</code> interfaces support
1686 <column name="options" key="csum" type='{"type": "boolean"}'>
1688 Optional. Compute GRE checksums on outgoing packets. Default is
1689 disabled, set to <code>true</code> to enable. Checksums present on
1690 incoming packets will be validated regardless of this setting.
1694 GRE checksums impose a significant performance penalty because they
1695 cover the entire packet. The encapsulated L3, L4, and L7 packet
1696 contents typically have their own checksums, so this additional
1697 checksum only adds value for the GRE and encapsulated L2 headers.
1701 This option is supported for <code>ipsec_gre</code>, but not useful
1702 because GRE checksums are weaker than, and redundant with, IPsec
1703 payload authentication.
1708 <group title="Tunnel Options: ipsec_gre only">
1710 Only <code>ipsec_gre</code> interfaces support these options.
1713 <column name="options" key="peer_cert">
1714 Required for certificate authentication. A string containing the
1715 peer's certificate in PEM format. Additionally the host's
1716 certificate must be specified with the <code>certificate</code>
1720 <column name="options" key="certificate">
1721 Required for certificate authentication. The name of a PEM file
1722 containing a certificate that will be presented to the peer during
1726 <column name="options" key="private_key">
1727 Optional for certificate authentication. The name of a PEM file
1728 containing the private key associated with <code>certificate</code>.
1729 If <code>certificate</code> contains the private key, this option may
1733 <column name="options" key="psk">
1734 Required for pre-shared key authentication. Specifies a pre-shared
1735 key for authentication that must be identical on both sides of the
1741 <group title="Patch Options">
1743 Only <code>patch</code> interfaces support these options.
1746 <column name="options" key="peer">
1747 The <ref column="name"/> of the <ref table="Interface"/> for the other
1748 side of the patch. The named <ref table="Interface"/>'s own
1749 <code>peer</code> option must specify this <ref table="Interface"/>'s
1750 name. That is, the two patch interfaces must have reversed <ref
1751 column="name"/> and <code>peer</code> values.
1755 <group title="Interface Status">
1757 Status information about interfaces attached to bridges, updated every
1758 5 seconds. Not all interfaces have all of these properties; virtual
1759 interfaces don't have a link speed, for example. Non-applicable
1760 columns will have empty values.
1762 <column name="admin_state">
1764 The administrative state of the physical network link.
1768 <column name="link_state">
1770 The observed state of the physical network link. This is ordinarily
1771 the link's carrier status. If the interface's <ref table="Port"/> is
1772 a bond configured for miimon monitoring, it is instead the network
1773 link's miimon status.
1777 <column name="link_resets">
1779 The number of times Open vSwitch has observed the
1780 <ref column="link_state"/> of this <ref table="Interface"/> change.
1784 <column name="link_speed">
1786 The negotiated speed of the physical network link.
1787 Valid values are positive integers greater than 0.
1791 <column name="duplex">
1793 The duplex mode of the physical network link.
1799 The MTU (maximum transmission unit); i.e. the largest
1800 amount of data that can fit into a single Ethernet frame.
1801 The standard Ethernet MTU is 1500 bytes. Some physical media
1802 and many kinds of virtual interfaces can be configured with
1806 This column will be empty for an interface that does not
1807 have an MTU as, for example, some kinds of tunnels do not.
1811 <column name="lacp_current">
1812 Boolean value indicating LACP status for this interface. If true, this
1813 interface has current LACP information about its LACP partner. This
1814 information may be used to monitor the health of interfaces in a LACP
1815 enabled port. This column will be empty if LACP is not enabled.
1818 <column name="status">
1819 Key-value pairs that report port status. Supported status values are
1820 <ref column="type"/>-dependent; some interfaces may not have a valid
1821 <ref column="status" key="driver_name"/>, for example.
1824 <column name="status" key="driver_name">
1825 The name of the device driver controlling the network adapter.
1828 <column name="status" key="driver_version">
1829 The version string of the device driver controlling the network
1833 <column name="status" key="firmware_version">
1834 The version string of the network adapter's firmware, if available.
1837 <column name="status" key="source_ip">
1838 The source IP address used for an IPv4 tunnel end-point, such as
1842 <column name="status" key="tunnel_egress_iface">
1843 Egress interface for tunnels. Currently only relevant for tunnels
1844 on Linux systems, this column will show the name of the interface
1845 which is responsible for routing traffic destined for the configured
1846 <ref column="options" key="remote_ip"/>. This could be an internal
1847 interface such as a bridge port.
1850 <column name="status" key="tunnel_egress_iface_carrier"
1851 type='{"type": "string", "enum": ["set", ["down", "up"]]}'>
1852 Whether carrier is detected on <ref column="status"
1853 key="tunnel_egress_iface"/>.
1857 <group title="Statistics">
1859 Key-value pairs that report interface statistics. The current
1860 implementation updates these counters periodically. The update period
1861 is controlled by <ref column="other_config"
1862 key="stats-update-interval"/> in the <code>Open_vSwitch</code> table.
1863 Future implementations may update them when an interface is created,
1864 when they are queried (e.g. using an OVSDB <code>select</code>
1865 operation), and just before an interface is deleted due to virtual
1866 interface hot-unplug or VM shutdown, and perhaps at other times, but
1867 not on any regular periodic basis.
1870 These are the same statistics reported by OpenFlow in its <code>struct
1871 ofp_port_stats</code> structure. If an interface does not support a
1872 given statistic, then that pair is omitted.
1874 <group title="Statistics: Successful transmit and receive counters">
1875 <column name="statistics" key="rx_packets">
1876 Number of received packets.
1878 <column name="statistics" key="rx_bytes">
1879 Number of received bytes.
1881 <column name="statistics" key="tx_packets">
1882 Number of transmitted packets.
1884 <column name="statistics" key="tx_bytes">
1885 Number of transmitted bytes.
1888 <group title="Statistics: Receive errors">
1889 <column name="statistics" key="rx_dropped">
1890 Number of packets dropped by RX.
1892 <column name="statistics" key="rx_frame_err">
1893 Number of frame alignment errors.
1895 <column name="statistics" key="rx_over_err">
1896 Number of packets with RX overrun.
1898 <column name="statistics" key="rx_crc_err">
1899 Number of CRC errors.
1901 <column name="statistics" key="rx_errors">
1902 Total number of receive errors, greater than or equal to the sum of
1906 <group title="Statistics: Transmit errors">
1907 <column name="statistics" key="tx_dropped">
1908 Number of packets dropped by TX.
1910 <column name="statistics" key="collisions">
1911 Number of collisions.
1913 <column name="statistics" key="tx_errors">
1914 Total number of transmit errors, greater than or equal to the sum of
1920 <group title="Ingress Policing">
1922 These settings control ingress policing for packets received on this
1923 interface. On a physical interface, this limits the rate at which
1924 traffic is allowed into the system from the outside; on a virtual
1925 interface (one connected to a virtual machine), this limits the rate at
1926 which the VM is able to transmit.
1929 Policing is a simple form of quality-of-service that simply drops
1930 packets received in excess of the configured rate. Due to its
1931 simplicity, policing is usually less accurate and less effective than
1932 egress QoS (which is configured using the <ref table="QoS"/> and <ref
1933 table="Queue"/> tables).
1936 Policing is currently implemented only on Linux. The Linux
1937 implementation uses a simple ``token bucket'' approach:
1941 The size of the bucket corresponds to <ref
1942 column="ingress_policing_burst"/>. Initially the bucket is full.
1945 Whenever a packet is received, its size (converted to tokens) is
1946 compared to the number of tokens currently in the bucket. If the
1947 required number of tokens are available, they are removed and the
1948 packet is forwarded. Otherwise, the packet is dropped.
1951 Whenever it is not full, the bucket is refilled with tokens at the
1952 rate specified by <ref column="ingress_policing_rate"/>.
1956 Policing interacts badly with some network protocols, and especially
1957 with fragmented IP packets. Suppose that there is enough network
1958 activity to keep the bucket nearly empty all the time. Then this token
1959 bucket algorithm will forward a single packet every so often, with the
1960 period depending on packet size and on the configured rate. All of the
1961 fragments of an IP packets are normally transmitted back-to-back, as a
1962 group. In such a situation, therefore, only one of these fragments
1963 will be forwarded and the rest will be dropped. IP does not provide
1964 any way for the intended recipient to ask for only the remaining
1965 fragments. In such a case there are two likely possibilities for what
1966 will happen next: either all of the fragments will eventually be
1967 retransmitted (as TCP will do), in which case the same problem will
1968 recur, or the sender will not realize that its packet has been dropped
1969 and data will simply be lost (as some UDP-based protocols will do).
1970 Either way, it is possible that no forward progress will ever occur.
1972 <column name="ingress_policing_rate">
1974 Maximum rate for data received on this interface, in kbps. Data
1975 received faster than this rate is dropped. Set to <code>0</code>
1976 (the default) to disable policing.
1980 <column name="ingress_policing_burst">
1981 <p>Maximum burst size for data received on this interface, in kb. The
1982 default burst size if set to <code>0</code> is 1000 kb. This value
1983 has no effect if <ref column="ingress_policing_rate"/>
1984 is <code>0</code>.</p>
1986 Specifying a larger burst size lets the algorithm be more forgiving,
1987 which is important for protocols like TCP that react severely to
1988 dropped packets. The burst size should be at least the size of the
1989 interface's MTU. Specifying a value that is numerically at least as
1990 large as 10% of <ref column="ingress_policing_rate"/> helps TCP come
1991 closer to achieving the full rate.
1996 <group title="Bidirectional Forwarding Detection (BFD)">
1998 BFD, defined in RFC 5880 and RFC 5881, allows point-to-point
1999 detection of connectivity failures by occasional transmission of
2000 BFD control messages. Open vSwitch implements BFD to serve
2001 as a more popular and standards compliant alternative to CFM.
2005 BFD operates by regularly transmitting BFD control messages at a rate
2006 negotiated independently in each direction. Each endpoint specifies
2007 the rate at which it expects to receive control messages, and the rate
2008 at which it is willing to transmit them. Open vSwitch uses a detection
2009 multiplier of three, meaning that an endpoint signals a connectivity
2010 fault if three consecutive BFD control messages fail to arrive. In the
2011 case of a unidirectional connectivity issue, the system not receiving
2012 BFD control messages signals the problem to its peer in the messages it
2017 The Open vSwitch implementation of BFD aims to comply faithfully
2018 with RFC 5880 requirements. Open vSwitch does not implement the
2019 optional Authentication or ``Echo Mode'' features.
2022 <group title="BFD Configuration">
2024 A controller sets up key-value pairs in the <ref column="bfd"/>
2025 column to enable and configure BFD.
2028 <column name="bfd" key="enable" type='{"type": "boolean"}'>
2029 True to enable BFD on this <ref table="Interface"/>.
2032 <column name="bfd" key="min_rx"
2033 type='{"type": "integer", "minInteger": 1}'>
2034 The shortest interval, in milliseconds, at which this BFD session
2035 offers to receive BFD control messages. The remote endpoint may
2036 choose to send messages at a slower rate. Defaults to
2040 <column name="bfd" key="min_tx"
2041 type='{"type": "integer", "minInteger": 1}'>
2042 The shortest interval, in milliseconds, at which this BFD session is
2043 willing to transmit BFD control messages. Messages will actually be
2044 transmitted at a slower rate if the remote endpoint is not willing to
2045 receive as quickly as specified. Defaults to <code>100</code>.
2048 <column name="bfd" key="decay_min_rx" type='{"type": "integer"}'>
2049 An alternate receive interval, in milliseconds, that must be greater
2050 than or equal to <ref column="bfd" key="min_rx"/>. The
2051 implementation switches from <ref column="bfd" key="min_rx"/> to <ref
2052 column="bfd" key="decay_min_rx"/> when there is no obvious incoming
2053 data traffic at the interface, to reduce the CPU and bandwidth cost
2054 of monitoring an idle interface. This feature may be disabled by
2055 setting a value of 0. This feature is reset whenever <ref
2056 column="bfd" key="decay_min_rx"/> or <ref column="bfd" key="min_rx"/>
2060 <column name="bfd" key="forwarding_if_rx" type='{"type": "boolean"}'>
2061 When <code>true</code>, traffic received on the
2062 <ref table="Interface"/> is used to indicate the capability of packet
2063 I/O. BFD control packets are still transmitted and received. At
2064 least one BFD control packet must be received every 100 * <ref
2065 column="bfd" key="min_rx"/> amount of time. Otherwise, even if
2066 traffic are received, the <ref column="bfd" key="forwarding"/>
2067 will be <code>false</code>.
2070 <column name="bfd" key="cpath_down" type='{"type": "boolean"}'>
2071 Set to true to notify the remote endpoint that traffic should not be
2072 forwarded to this system for some reason other than a connectivty
2073 failure on the interface being monitored. The typical underlying
2074 reason is ``concatenated path down,'' that is, that connectivity
2075 beyond the local system is down. Defaults to false.
2078 <column name="bfd" key="check_tnl_key" type='{"type": "boolean"}'>
2079 Set to true to make BFD accept only control messages with a tunnel
2080 key of zero. By default, BFD accepts control messages with any
2084 <column name="bfd" key="bfd_dst_mac">
2085 Set to an Ethernet address in the form
2086 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>
2087 to set the MAC used as destination for transmitted BFD packets and
2088 expected as destination for received BFD packets. The default is
2089 <code>00:23:20:00:00:01</code>.
2092 <column name="bfd" key="bfd_src_ip">
2093 Set to an IPv4 address to set the IP address used as source for
2094 transmitted BFD packets. The default is <code>169.254.1.0</code>.
2097 <column name="bfd" key="bfd_dst_ip">
2098 Set to an IPv4 address to set the IP address used as destination
2099 for transmitted BFD packets. The default is <code>169.254.1.1</code>.
2103 <group title="BFD Status">
2105 The switch sets key-value pairs in the <ref column="bfd_status"/>
2106 column to report the status of BFD on this interface. When BFD is
2107 not enabled, with <ref column="bfd" key="enable"/>, the switch clears
2108 all key-value pairs from <ref column="bfd_status"/>.
2111 <column name="bfd_status" key="state"
2112 type='{"type": "string",
2113 "enum": ["set", ["admin_down", "down", "init", "up"]]}'>
2114 Reports the state of the BFD session. The BFD session is fully
2115 healthy and negotiated if <code>UP</code>.
2118 <column name="bfd_status" key="forwarding" type='{"type": "boolean"}'>
2119 Reports whether the BFD session believes this <ref
2120 table="Interface"/> may be used to forward traffic. Typically this
2121 means the local session is signaling <code>UP</code>, and the remote
2122 system isn't signaling a problem such as concatenated path down.
2125 <column name="bfd_status" key="diagnostic">
2126 In case of a problem, set to a short message that reports what the
2127 local BFD session thinks is wrong.
2130 <column name="bfd_status" key="remote_state"
2131 type='{"type": "string",
2132 "enum": ["set", ["admin_down", "down", "init", "up"]]}'>
2133 Reports the state of the remote endpoint's BFD session.
2136 <column name="bfd_status" key="remote_diagnostic">
2137 In case of a problem, set to a short message that reports what the
2138 remote endpoint's BFD session thinks is wrong.
2141 <column name="bfd_status" key="flap_count"
2142 type='{"type": "integer", "minInteger": 0}'>
2143 Counts the number of <ref column="bfd_status" key="forwarding" />
2144 flaps since start. A flap is considered as a change of the
2145 <ref column="bfd_status" key="forwarding" /> value.
2150 <group title="Connectivity Fault Management">
2152 802.1ag Connectivity Fault Management (CFM) allows a group of
2153 Maintenance Points (MPs) called a Maintenance Association (MA) to
2154 detect connectivity problems with each other. MPs within a MA should
2155 have complete and exclusive interconnectivity. This is verified by
2156 occasionally broadcasting Continuity Check Messages (CCMs) at a
2157 configurable transmission interval.
2161 According to the 802.1ag specification, each Maintenance Point should
2162 be configured out-of-band with a list of Remote Maintenance Points it
2163 should have connectivity to. Open vSwitch differs from the
2164 specification in this area. It simply assumes the link is faulted if
2165 no Remote Maintenance Points are reachable, and considers it not
2170 When operating over tunnels which have no <code>in_key</code>, or an
2171 <code>in_key</code> of <code>flow</code>. CFM will only accept CCMs
2172 with a tunnel key of zero.
2175 <column name="cfm_mpid">
2177 A Maintenance Point ID (MPID) uniquely identifies each endpoint
2178 within a Maintenance Association. The MPID is used to identify this
2179 endpoint to other Maintenance Points in the MA. Each end of a link
2180 being monitored should have a different MPID. Must be configured to
2181 enable CFM on this <ref table="Interface"/>.
2184 According to the 802.1ag specification, MPIDs can only range between
2185 [1, 8191]. However, extended mode (see <ref column="other_config"
2186 key="cfm_extended"/>) supports eight byte MPIDs.
2190 <column name="cfm_flap_count">
2191 Counts the number of cfm fault flapps since boot. A flap is
2192 considered to be a change of the <ref column="cfm_fault"/> value.
2195 <column name="cfm_fault">
2197 Indicates a connectivity fault triggered by an inability to receive
2198 heartbeats from any remote endpoint. When a fault is triggered on
2199 <ref table="Interface"/>s participating in bonds, they will be
2203 Faults can be triggered for several reasons. Most importantly they
2204 are triggered when no CCMs are received for a period of 3.5 times the
2205 transmission interval. Faults are also triggered when any CCMs
2206 indicate that a Remote Maintenance Point is not receiving CCMs but
2207 able to send them. Finally, a fault is triggered if a CCM is
2208 received which indicates unexpected configuration. Notably, this
2209 case arises when a CCM is received which advertises the local MPID.
2213 <column name="cfm_fault_status" key="recv">
2214 Indicates a CFM fault was triggered due to a lack of CCMs received on
2215 the <ref table="Interface"/>.
2218 <column name="cfm_fault_status" key="rdi">
2219 Indicates a CFM fault was triggered due to the reception of a CCM with
2220 the RDI bit flagged. Endpoints set the RDI bit in their CCMs when they
2221 are not receiving CCMs themselves. This typically indicates a
2222 unidirectional connectivity failure.
2225 <column name="cfm_fault_status" key="maid">
2226 Indicates a CFM fault was triggered due to the reception of a CCM with
2227 a MAID other than the one Open vSwitch uses. CFM broadcasts are tagged
2228 with an identification number in addition to the MPID called the MAID.
2229 Open vSwitch only supports receiving CCM broadcasts tagged with the
2230 MAID it uses internally.
2233 <column name="cfm_fault_status" key="loopback">
2234 Indicates a CFM fault was triggered due to the reception of a CCM
2235 advertising the same MPID configured in the <ref column="cfm_mpid"/>
2236 column of this <ref table="Interface"/>. This may indicate a loop in
2240 <column name="cfm_fault_status" key="overflow">
2241 Indicates a CFM fault was triggered because the CFM module received
2242 CCMs from more remote endpoints than it can keep track of.
2245 <column name="cfm_fault_status" key="override">
2246 Indicates a CFM fault was manually triggered by an administrator using
2247 an <code>ovs-appctl</code> command.
2250 <column name="cfm_fault_status" key="interval">
2251 Indicates a CFM fault was triggered due to the reception of a CCM
2252 frame having an invalid interval.
2255 <column name="cfm_remote_opstate">
2256 <p>When in extended mode, indicates the operational state of the
2257 remote endpoint as either <code>up</code> or <code>down</code>. See
2258 <ref column="other_config" key="cfm_opstate"/>.
2262 <column name="cfm_health">
2264 Indicates the health of the interface as a percentage of CCM frames
2265 received over 21 <ref column="other_config" key="cfm_interval"/>s.
2266 The health of an interface is undefined if it is communicating with
2267 more than one <ref column="cfm_remote_mpids"/>. It reduces if
2268 healthy heartbeats are not received at the expected rate, and
2269 gradually improves as healthy heartbeats are received at the desired
2270 rate. Every 21 <ref column="other_config" key="cfm_interval"/>s, the
2271 health of the interface is refreshed.
2274 As mentioned above, the faults can be triggered for several reasons.
2275 The link health will deteriorate even if heartbeats are received but
2276 they are reported to be unhealthy. An unhealthy heartbeat in this
2277 context is a heartbeat for which either some fault is set or is out
2278 of sequence. The interface health can be 100 only on receiving
2279 healthy heartbeats at the desired rate.
2283 <column name="cfm_remote_mpids">
2284 When CFM is properly configured, Open vSwitch will occasionally
2285 receive CCM broadcasts. These broadcasts contain the MPID of the
2286 sending Maintenance Point. The list of MPIDs from which this
2287 <ref table="Interface"/> is receiving broadcasts from is regularly
2288 collected and written to this column.
2291 <column name="other_config" key="cfm_interval"
2292 type='{"type": "integer"}'>
2294 The interval, in milliseconds, between transmissions of CFM
2295 heartbeats. Three missed heartbeat receptions indicate a
2300 In standard operation only intervals of 3, 10, 100, 1,000, 10,000,
2301 60,000, or 600,000 ms are supported. Other values will be rounded
2302 down to the nearest value on the list. Extended mode (see <ref
2303 column="other_config" key="cfm_extended"/>) supports any interval up
2304 to 65,535 ms. In either mode, the default is 1000 ms.
2307 <p>We do not recommend using intervals less than 100 ms.</p>
2310 <column name="other_config" key="cfm_extended"
2311 type='{"type": "boolean"}'>
2312 When <code>true</code>, the CFM module operates in extended mode. This
2313 causes it to use a nonstandard destination address to avoid conflicting
2314 with compliant implementations which may be running concurrently on the
2315 network. Furthermore, extended mode increases the accuracy of the
2316 <code>cfm_interval</code> configuration parameter by breaking wire
2317 compatibility with 802.1ag compliant implementations. And extended
2318 mode allows eight byte MPIDs. Defaults to <code>false</code>.
2321 <column name="other_config" key="cfm_demand" type='{"type": "boolean"}'>
2323 When <code>true</code>, and
2324 <ref column="other_config" key="cfm_extended"/> is true, the CFM
2325 module operates in demand mode. When in demand mode, traffic
2326 received on the <ref table="Interface"/> is used to indicate
2327 liveness. CCMs are still transmitted and received. At least one
2328 CCM must be received every 100 * <ref column="other_config"
2329 key="cfm_interval"/> amount of time. Otherwise, even if traffic
2330 are received, the CFM module will raise the connectivity fault.
2334 Demand mode has a couple of caveats:
2337 To ensure that ovs-vswitchd has enough time to pull statistics
2338 from the datapath, the fault detection interval is set to
2339 3.5 * MAX(<ref column="other_config" key="cfm_interval"/>, 500)
2344 To avoid ambiguity, demand mode disables itself when there are
2345 multiple remote maintenance points.
2349 If the <ref table="Interface"/> is heavily congested, CCMs
2350 containing the <ref column="other_config" key="cfm_opstate"/>
2351 status may be dropped causing changes in the operational state to
2352 be delayed. Similarly, if CCMs containing the RDI bit are not
2353 received, unidirectional link failures may not be detected.
2359 <column name="other_config" key="cfm_opstate"
2360 type='{"type": "string", "enum": ["set", ["down", "up"]]}'>
2361 When <code>down</code>, the CFM module marks all CCMs it generates as
2362 operationally down without triggering a fault. This allows remote
2363 maintenance points to choose not to forward traffic to the
2364 <ref table="Interface"/> on which this CFM module is running.
2365 Currently, in Open vSwitch, the opdown bit of CCMs affects
2366 <ref table="Interface"/>s participating in bonds, and the bundle
2367 OpenFlow action. This setting is ignored when CFM is not in extended
2368 mode. Defaults to <code>up</code>.
2371 <column name="other_config" key="cfm_ccm_vlan"
2372 type='{"type": "integer", "minInteger": 1, "maxInteger": 4095}'>
2373 When set, the CFM module will apply a VLAN tag to all CCMs it generates
2374 with the given value. May be the string <code>random</code> in which
2375 case each CCM will be tagged with a different randomly generated VLAN.
2378 <column name="other_config" key="cfm_ccm_pcp"
2379 type='{"type": "integer", "minInteger": 1, "maxInteger": 7}'>
2380 When set, the CFM module will apply a VLAN tag to all CCMs it generates
2381 with the given PCP value, the VLAN ID of the tag is governed by the
2382 value of <ref column="other_config" key="cfm_ccm_vlan"/>. If
2383 <ref column="other_config" key="cfm_ccm_vlan"/> is unset, a VLAN ID of
2389 <group title="Bonding Configuration">
2390 <column name="other_config" key="lacp-port-id"
2391 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
2392 The LACP port ID of this <ref table="Interface"/>. Port IDs are
2393 used in LACP negotiations to identify individual ports
2394 participating in a bond.
2397 <column name="other_config" key="lacp-port-priority"
2398 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
2399 The LACP port priority of this <ref table="Interface"/>. In LACP
2400 negotiations <ref table="Interface"/>s with numerically lower
2401 priorities are preferred for aggregation.
2404 <column name="other_config" key="lacp-aggregation-key"
2405 type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'>
2406 The LACP aggregation key of this <ref table="Interface"/>. <ref
2407 table="Interface"/>s with different aggregation keys may not be active
2408 within a given <ref table="Port"/> at the same time.
2412 <group title="Virtual Machine Identifiers">
2414 These key-value pairs specifically apply to an interface that
2415 represents a virtual Ethernet interface connected to a virtual
2416 machine. These key-value pairs should not be present for other types
2417 of interfaces. Keys whose names end in <code>-uuid</code> have
2418 values that uniquely identify the entity in question. For a Citrix
2419 XenServer hypervisor, these values are UUIDs in RFC 4122 format.
2420 Other hypervisors may use other formats.
2423 <column name="external_ids" key="attached-mac">
2424 The MAC address programmed into the ``virtual hardware'' for this
2425 interface, in the form
2426 <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>.
2427 For Citrix XenServer, this is the value of the <code>MAC</code> field
2428 in the VIF record for this interface.
2431 <column name="external_ids" key="iface-id">
2432 A system-unique identifier for the interface. On XenServer, this will
2433 commonly be the same as <ref column="external_ids" key="xs-vif-uuid"/>.
2436 <column name="external_ids" key="iface-status"
2437 type='{"type": "string",
2438 "enum": ["set", ["active", "inactive"]]}'>
2440 Hypervisors may sometimes have more than one interface associated
2441 with a given <ref column="external_ids" key="iface-id"/>, only one of
2442 which is actually in use at a given time. For example, in some
2443 circumstances XenServer has both a ``tap'' and a ``vif'' interface
2444 for a single <ref column="external_ids" key="iface-id"/>, but only
2445 uses one of them at a time. A hypervisor that behaves this way must
2446 mark the currently in use interface <code>active</code> and the
2447 others <code>inactive</code>. A hypervisor that never has more than
2448 one interface for a given <ref column="external_ids" key="iface-id"/>
2449 may mark that interface <code>active</code> or omit <ref
2450 column="external_ids" key="iface-status"/> entirely.
2454 During VM migration, a given <ref column="external_ids"
2455 key="iface-id"/> might transiently be marked <code>active</code> on
2456 two different hypervisors. That is, <code>active</code> means that
2457 this <ref column="external_ids" key="iface-id"/> is the active
2458 instance within a single hypervisor, not in a broader scope.
2459 There is one exception: some hypervisors support ``migration'' from a
2460 given hypervisor to itself (most often for test purposes). During
2461 such a ``migration,'' two instances of a single <ref
2462 column="external_ids" key="iface-id"/> might both be briefly marked
2463 <code>active</code> on a single hypervisor.
2467 <column name="external_ids" key="xs-vif-uuid">
2468 The virtual interface associated with this interface.
2471 <column name="external_ids" key="xs-network-uuid">
2472 The virtual network to which this interface is attached.
2475 <column name="external_ids" key="vm-id">
2476 The VM to which this interface belongs. On XenServer, this will be the
2477 same as <ref column="external_ids" key="xs-vm-uuid"/>.
2480 <column name="external_ids" key="xs-vm-uuid">
2481 The VM to which this interface belongs.
2485 <group title="VLAN Splinters">
2487 The ``VLAN splinters'' feature increases Open vSwitch compatibility
2488 with buggy network drivers in old versions of Linux that do not
2489 properly support VLANs when VLAN devices are not used, at some cost
2490 in memory and performance.
2494 When VLAN splinters are enabled on a particular interface, Open vSwitch
2495 creates a VLAN device for each in-use VLAN. For sending traffic tagged
2496 with a VLAN on the interface, it substitutes the VLAN device. Traffic
2497 received on the VLAN device is treated as if it had been received on
2498 the interface on the particular VLAN.
2502 VLAN splinters consider a VLAN to be in use if:
2507 The VLAN is the <ref table="Port" column="tag"/> value in any <ref
2508 table="Port"/> record.
2512 The VLAN is listed within the <ref table="Port" column="trunks"/>
2513 column of the <ref table="Port"/> record of an interface on which
2514 VLAN splinters are enabled.
2516 An empty <ref table="Port" column="trunks"/> does not influence the
2517 in-use VLANs: creating 4,096 VLAN devices is impractical because it
2518 will exceed the current 1,024 port per datapath limit.
2522 An OpenFlow flow within any bridge matches the VLAN.
2527 The same set of in-use VLANs applies to every interface on which VLAN
2528 splinters are enabled. That is, the set is not chosen separately for
2529 each interface but selected once as the union of all in-use VLANs based
2534 It does not make sense to enable VLAN splinters on an interface for an
2535 access port, or on an interface that is not a physical port.
2539 VLAN splinters are deprecated. When broken device drivers are no
2540 longer in widespread use, we will delete this feature.
2543 <column name="other_config" key="enable-vlan-splinters"
2544 type='{"type": "boolean"}'>
2546 Set to <code>true</code> to enable VLAN splinters on this interface.
2547 Defaults to <code>false</code>.
2551 VLAN splinters increase kernel and userspace memory overhead, so do
2552 not use them unless they are needed.
2556 VLAN splinters do not support 802.1p priority tags. Received
2557 priorities will appear to be 0, regardless of their actual values,
2558 and priorities on transmitted packets will also be cleared to 0.
2563 <group title="Common Columns">
2564 The overall purpose of these columns is described under <code>Common
2565 Columns</code> at the beginning of this document.
2567 <column name="other_config"/>
2568 <column name="external_ids"/>
2572 <table name="Flow_Table" title="OpenFlow table configuration">
2573 <p>Configuration for a particular OpenFlow table.</p>
2575 <column name="name">
2576 The table's name. Set this column to change the name that controllers
2577 will receive when they request table statistics, e.g. <code>ovs-ofctl
2578 dump-tables</code>. The name does not affect switch behavior.
2581 <column name="flow_limit">
2582 If set, limits the number of flows that may be added to the table. Open
2583 vSwitch may limit the number of flows in a table for other reasons,
2584 e.g. due to hardware limitations or for resource availability or
2585 performance reasons.
2588 <column name="overflow_policy">
2590 Controls the switch's behavior when an OpenFlow flow table modification
2591 request would add flows in excess of <ref column="flow_limit"/>. The
2592 supported values are:
2596 <dt><code>refuse</code></dt>
2598 Refuse to add the flow or flows. This is also the default policy
2599 when <ref column="overflow_policy"/> is unset.
2602 <dt><code>evict</code></dt>
2604 Delete the flow that will expire soonest. See <ref column="groups"/>
2610 <column name="groups">
2612 When <ref column="overflow_policy"/> is <code>evict</code>, this
2613 controls how flows are chosen for eviction when the flow table would
2614 otherwise exceed <ref column="flow_limit"/> flows. Its value is a set
2615 of NXM fields or sub-fields, each of which takes one of the forms
2616 <code><var>field</var>[]</code> or
2617 <code><var>field</var>[<var>start</var>..<var>end</var>]</code>,
2618 e.g. <code>NXM_OF_IN_PORT[]</code>. Please see
2619 <code>nicira-ext.h</code> for a complete list of NXM field names.
2623 When a flow must be evicted due to overflow, the flow to evict is
2624 chosen through an approximation of the following algorithm:
2629 Divide the flows in the table into groups based on the values of the
2630 specified fields or subfields, so that all of the flows in a given
2631 group have the same values for those fields. If a flow does not
2632 specify a given field, that field's value is treated as 0.
2636 Consider the flows in the largest group, that is, the group that
2637 contains the greatest number of flows. If two or more groups all
2638 have the same largest number of flows, consider the flows in all of
2643 Among the flows under consideration, choose the flow that expires
2644 soonest for eviction.
2649 The eviction process only considers flows that have an idle timeout or
2650 a hard timeout. That is, eviction never deletes permanent flows.
2651 (Permanent flows do count against <ref column="flow_limit"/>.)
2655 Open vSwitch ignores any invalid or unknown field specifications.
2659 When <ref column="overflow_policy"/> is not <code>evict</code>, this
2660 column has no effect.
2664 <column name="prefixes">
2666 This string set specifies which fields should be used for
2667 address prefix tracking. Prefix tracking allows the
2668 classifier to skip rules with longer than necessary prefixes,
2669 resulting in better wildcarding for datapath flows.
2672 Prefix tracking may be beneficial when a flow table contains
2673 matches on IP address fields with different prefix lengths.
2674 For example, when a flow table contains IP address matches on
2675 both full addresses and proper prefixes, the full address
2676 matches will typically cause the datapath flow to un-wildcard
2677 the whole address field (depending on flow entry priorities).
2678 In this case each packet with a different address gets handed
2679 to the userspace for flow processing and generates its own
2680 datapath flow. With prefix tracking enabled for the address
2681 field in question packets with addresses matching shorter
2682 prefixes would generate datapath flows where the irrelevant
2683 address bits are wildcarded, allowing the same datapath flow
2684 to handle all the packets within the prefix in question. In
2685 this case many userspace upcalls can be avoided and the
2686 overall performance can be better.
2689 This is a performance optimization only, so packets will
2690 receive the same treatment with or without prefix tracking.
2693 The supported fields are: <code>tun_id</code>,
2694 <code>tun_src</code>, <code>tun_dst</code>,
2695 <code>nw_src</code>, <code>nw_dst</code> (or aliases
2696 <code>ip_src</code> and <code>ip_dst</code>),
2697 <code>ipv6_src</code>, and <code>ipv6_dst</code>. (Using this
2698 feature for <code>tun_id</code> would only make sense if the
2699 tunnel IDs have prefix structure similar to IP addresses.)
2703 By default, the <code>prefixes=ip_dst,ip_src</code> are used
2704 on each flow table. This instructs the flow classifier to
2705 track the IP destination and source addresses used by the
2706 rules in this specific flow table.
2710 The keyword <code>none</code> is recognized as an explicit
2711 override of the default values, causing no prefix fields to be
2716 To set the prefix fields, the flow table record needs to
2721 <dt><code>ovs-vsctl set Bridge br0 flow_tables:0=@N1 -- --id=@N1 create Flow_Table name=table0</code></dt>
2723 Creates a flow table record for the OpenFlow table number 0.
2726 <dt><code>ovs-vsctl set Flow_Table table0 prefixes=ip_dst,ip_src</code></dt>
2728 Enables prefix tracking for IP source and destination
2734 There is a maximum number of fields that can be enabled for any
2735 one flow table. Currently this limit is 3.
2739 <group title="Common Columns">
2740 The overall purpose of these columns is described under <code>Common
2741 Columns</code> at the beginning of this document.
2743 <column name="external_ids"/>
2747 <table name="QoS" title="Quality of Service configuration">
2748 <p>Quality of Service (QoS) configuration for each Port that
2751 <column name="type">
2752 <p>The type of QoS to implement. The currently defined types are
2755 <dt><code>linux-htb</code></dt>
2757 Linux ``hierarchy token bucket'' classifier. See tc-htb(8) (also at
2758 <code>http://linux.die.net/man/8/tc-htb</code>) and the HTB manual
2759 (<code>http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm</code>)
2760 for information on how this classifier works and how to configure it.
2764 <dt><code>linux-hfsc</code></dt>
2766 Linux "Hierarchical Fair Service Curve" classifier.
2767 See <code>http://linux-ip.net/articles/hfsc.en/</code> for
2768 information on how this classifier works.
2773 <column name="queues">
2774 <p>A map from queue numbers to <ref table="Queue"/> records. The
2775 supported range of queue numbers depend on <ref column="type"/>. The
2776 queue numbers are the same as the <code>queue_id</code> used in
2777 OpenFlow in <code>struct ofp_action_enqueue</code> and other
2781 Queue 0 is the ``default queue.'' It is used by OpenFlow output
2782 actions when no specific queue has been set. When no configuration for
2783 queue 0 is present, it is automatically configured as if a <ref
2784 table="Queue"/> record with empty <ref table="Queue" column="dscp"/>
2785 and <ref table="Queue" column="other_config"/> columns had been
2787 (Before version 1.6, Open vSwitch would leave queue 0 unconfigured in
2788 this case. With some queuing disciplines, this dropped all packets
2789 destined for the default queue.)
2793 <group title="Configuration for linux-htb and linux-hfsc">
2795 The <code>linux-htb</code> and <code>linux-hfsc</code> classes support
2796 the following key-value pair:
2799 <column name="other_config" key="max-rate" type='{"type": "integer"}'>
2800 Maximum rate shared by all queued traffic, in bit/s. Optional. If not
2801 specified, for physical interfaces, the default is the link rate. For
2802 other interfaces or if the link rate cannot be determined, the default
2803 is currently 100 Mbps.
2807 <group title="Common Columns">
2808 The overall purpose of these columns is described under <code>Common
2809 Columns</code> at the beginning of this document.
2811 <column name="other_config"/>
2812 <column name="external_ids"/>
2816 <table name="Queue" title="QoS output queue.">
2817 <p>A configuration for a port output queue, used in configuring Quality of
2818 Service (QoS) features. May be referenced by <ref column="queues"
2819 table="QoS"/> column in <ref table="QoS"/> table.</p>
2821 <column name="dscp">
2822 If set, Open vSwitch will mark all traffic egressing this
2823 <ref table="Queue"/> with the given DSCP bits. Traffic egressing the
2824 default <ref table="Queue"/> is only marked if it was explicitly selected
2825 as the <ref table="Queue"/> at the time the packet was output. If unset,
2826 the DSCP bits of traffic egressing this <ref table="Queue"/> will remain
2830 <group title="Configuration for linux-htb QoS">
2832 <ref table="QoS"/> <ref table="QoS" column="type"/>
2833 <code>linux-htb</code> may use <code>queue_id</code>s less than 61440.
2834 It has the following key-value pairs defined.
2837 <column name="other_config" key="min-rate"
2838 type='{"type": "integer", "minInteger": 1}'>
2839 Minimum guaranteed bandwidth, in bit/s.
2842 <column name="other_config" key="max-rate"
2843 type='{"type": "integer", "minInteger": 1}'>
2844 Maximum allowed bandwidth, in bit/s. Optional. If specified, the
2845 queue's rate will not be allowed to exceed the specified value, even
2846 if excess bandwidth is available. If unspecified, defaults to no
2850 <column name="other_config" key="burst"
2851 type='{"type": "integer", "minInteger": 1}'>
2852 Burst size, in bits. This is the maximum amount of ``credits'' that a
2853 queue can accumulate while it is idle. Optional. Details of the
2854 <code>linux-htb</code> implementation require a minimum burst size, so
2855 a too-small <code>burst</code> will be silently ignored.
2858 <column name="other_config" key="priority"
2859 type='{"type": "integer", "minInteger": 0, "maxInteger": 4294967295}'>
2860 A queue with a smaller <code>priority</code> will receive all the
2861 excess bandwidth that it can use before a queue with a larger value
2862 receives any. Specific priority values are unimportant; only relative
2863 ordering matters. Defaults to 0 if unspecified.
2867 <group title="Configuration for linux-hfsc QoS">
2869 <ref table="QoS"/> <ref table="QoS" column="type"/>
2870 <code>linux-hfsc</code> may use <code>queue_id</code>s less than 61440.
2871 It has the following key-value pairs defined.
2874 <column name="other_config" key="min-rate"
2875 type='{"type": "integer", "minInteger": 1}'>
2876 Minimum guaranteed bandwidth, in bit/s.
2879 <column name="other_config" key="max-rate"
2880 type='{"type": "integer", "minInteger": 1}'>
2881 Maximum allowed bandwidth, in bit/s. Optional. If specified, the
2882 queue's rate will not be allowed to exceed the specified value, even if
2883 excess bandwidth is available. If unspecified, defaults to no
2888 <group title="Common Columns">
2889 The overall purpose of these columns is described under <code>Common
2890 Columns</code> at the beginning of this document.
2892 <column name="other_config"/>
2893 <column name="external_ids"/>
2897 <table name="Mirror" title="Port mirroring.">
2898 <p>A port mirror within a <ref table="Bridge"/>.</p>
2899 <p>A port mirror configures a bridge to send selected frames to special
2900 ``mirrored'' ports, in addition to their normal destinations. Mirroring
2901 traffic may also be referred to as SPAN or RSPAN, depending on how
2902 the mirrored traffic is sent.</p>
2904 <column name="name">
2905 Arbitrary identifier for the <ref table="Mirror"/>.
2908 <group title="Selecting Packets for Mirroring">
2910 To be selected for mirroring, a given packet must enter or leave the
2911 bridge through a selected port and it must also be in one of the
2915 <column name="select_all">
2916 If true, every packet arriving or departing on any port is
2917 selected for mirroring.
2920 <column name="select_dst_port">
2921 Ports on which departing packets are selected for mirroring.
2924 <column name="select_src_port">
2925 Ports on which arriving packets are selected for mirroring.
2928 <column name="select_vlan">
2929 VLANs on which packets are selected for mirroring. An empty set
2930 selects packets on all VLANs.
2934 <group title="Mirroring Destination Configuration">
2936 These columns are mutually exclusive. Exactly one of them must be
2940 <column name="output_port">
2941 <p>Output port for selected packets, if nonempty.</p>
2942 <p>Specifying a port for mirror output reserves that port exclusively
2943 for mirroring. No frames other than those selected for mirroring
2945 will be forwarded to the port, and any frames received on the port
2946 will be discarded.</p>
2948 The output port may be any kind of port supported by Open vSwitch.
2949 It may be, for example, a physical port (sometimes called SPAN) or a
2954 <column name="output_vlan">
2955 <p>Output VLAN for selected packets, if nonempty.</p>
2956 <p>The frames will be sent out all ports that trunk
2957 <ref column="output_vlan"/>, as well as any ports with implicit VLAN
2958 <ref column="output_vlan"/>. When a mirrored frame is sent out a
2959 trunk port, the frame's VLAN tag will be set to
2960 <ref column="output_vlan"/>, replacing any existing tag; when it is
2961 sent out an implicit VLAN port, the frame will not be tagged. This
2962 type of mirroring is sometimes called RSPAN.</p>
2964 See the documentation for
2965 <ref column="other_config" key="forward-bpdu"/> in the
2966 <ref table="Interface"/> table for a list of destination MAC
2967 addresses which will not be mirrored to a VLAN to avoid confusing
2968 switches that interpret the protocols that they represent.
2970 <p><em>Please note:</em> Mirroring to a VLAN can disrupt a network that
2971 contains unmanaged switches. Consider an unmanaged physical switch
2972 with two ports: port 1, connected to an end host, and port 2,
2973 connected to an Open vSwitch configured to mirror received packets
2974 into VLAN 123 on port 2. Suppose that the end host sends a packet on
2975 port 1 that the physical switch forwards to port 2. The Open vSwitch
2976 forwards this packet to its destination and then reflects it back on
2977 port 2 in VLAN 123. This reflected packet causes the unmanaged
2978 physical switch to replace the MAC learning table entry, which
2979 correctly pointed to port 1, with one that incorrectly points to port
2980 2. Afterward, the physical switch will direct packets destined for
2981 the end host to the Open vSwitch on port 2, instead of to the end
2982 host on port 1, disrupting connectivity. If mirroring to a VLAN is
2983 desired in this scenario, then the physical switch must be replaced
2984 by one that learns Ethernet addresses on a per-VLAN basis. In
2985 addition, learning should be disabled on the VLAN containing mirrored
2986 traffic. If this is not done then intermediate switches will learn
2987 the MAC address of each end host from the mirrored traffic. If
2988 packets being sent to that end host are also mirrored, then they will
2989 be dropped since the switch will attempt to send them out the input
2990 port. Disabling learning for the VLAN will cause the switch to
2991 correctly send the packet out all ports configured for that VLAN. If
2992 Open vSwitch is being used as an intermediate switch, learning can be
2993 disabled by adding the mirrored VLAN to <ref column="flood_vlans"/>
2994 in the appropriate <ref table="Bridge"/> table or tables.</p>
2996 Mirroring to a GRE tunnel has fewer caveats than mirroring to a
2997 VLAN and should generally be preferred.
3002 <group title="Statistics: Mirror counters">
3004 Key-value pairs that report mirror statistics. The update period
3005 is controlled by <ref column="other_config"
3006 key="stats-update-interval"/> in the <code>Open_vSwitch</code> table.
3008 <column name="statistics" key="tx_packets">
3009 Number of packets transmitted through this mirror.
3011 <column name="statistics" key="tx_bytes">
3012 Number of bytes transmitted through this mirror.
3016 <group title="Common Columns">
3017 The overall purpose of these columns is described under <code>Common
3018 Columns</code> at the beginning of this document.
3020 <column name="external_ids"/>
3024 <table name="Controller" title="OpenFlow controller configuration.">
3025 <p>An OpenFlow controller.</p>
3028 Open vSwitch supports two kinds of OpenFlow controllers:
3032 <dt>Primary controllers</dt>
3035 This is the kind of controller envisioned by the OpenFlow 1.0
3036 specification. Usually, a primary controller implements a network
3037 policy by taking charge of the switch's flow table.
3041 Open vSwitch initiates and maintains persistent connections to
3042 primary controllers, retrying the connection each time it fails or
3043 drops. The <ref table="Bridge" column="fail_mode"/> column in the
3044 <ref table="Bridge"/> table applies to primary controllers.
3048 Open vSwitch permits a bridge to have any number of primary
3049 controllers. When multiple controllers are configured, Open
3050 vSwitch connects to all of them simultaneously. Because
3051 OpenFlow 1.0 does not specify how multiple controllers
3052 coordinate in interacting with a single switch, more than
3053 one primary controller should be specified only if the
3054 controllers are themselves designed to coordinate with each
3055 other. (The Nicira-defined <code>NXT_ROLE</code> OpenFlow
3056 vendor extension may be useful for this.)
3059 <dt>Service controllers</dt>
3062 These kinds of OpenFlow controller connections are intended for
3063 occasional support and maintenance use, e.g. with
3064 <code>ovs-ofctl</code>. Usually a service controller connects only
3065 briefly to inspect or modify some of a switch's state.
3069 Open vSwitch listens for incoming connections from service
3070 controllers. The service controllers initiate and, if necessary,
3071 maintain the connections from their end. The <ref table="Bridge"
3072 column="fail_mode"/> column in the <ref table="Bridge"/> table does
3073 not apply to service controllers.
3077 Open vSwitch supports configuring any number of service controllers.
3083 The <ref column="target"/> determines the type of controller.
3086 <group title="Core Features">
3087 <column name="target">
3088 <p>Connection method for controller.</p>
3090 The following connection methods are currently supported for primary
3094 <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
3096 <p>The specified SSL <var>port</var> on the host at the
3097 given <var>ip</var>, which must be expressed as an IP
3098 address (not a DNS name). The <ref table="Open_vSwitch"
3099 column="ssl"/> column in the <ref table="Open_vSwitch"/>
3100 table must point to a valid SSL configuration when this form
3102 <p>If <var>port</var> is not specified, it currently
3103 defaults to 6633. In the future, the default will change to
3104 6653, which is the IANA-defined value.</p>
3105 <p>SSL support is an optional feature that is not always built as
3106 part of Open vSwitch.</p>
3108 <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
3111 The specified TCP <var>port</var> on the host at the given
3112 <var>ip</var>, which must be expressed as an IP address (not a
3113 DNS name), where <var>ip</var> can be IPv4 or IPv6 address. If
3114 <var>ip</var> is an IPv6 address, wrap it in square brackets,
3115 e.g. <code>tcp:[::1]:6632</code>.
3118 If <var>port</var> is not specified, it currently defaults to
3119 6633. In the future, the default will change to 6653, which is
3120 the IANA-defined value.
3125 The following connection methods are currently supported for service
3129 <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
3132 Listens for SSL connections on the specified TCP <var>port</var>.
3133 If <var>ip</var>, which must be expressed as an IP address (not a
3134 DNS name), is specified, then connections are restricted to the
3135 specified local IP address (either IPv4 or IPv6). If
3136 <var>ip</var> is an IPv6 address, wrap it in square brackets,
3137 e.g. <code>pssl:6632:[::1]</code>.
3140 If <var>port</var> is not specified, it currently defaults to
3141 6633. If <var>ip</var> is not specified then it listens only on
3142 IPv4 (but not IPv6) addresses. The
3143 <ref table="Open_vSwitch" column="ssl"/>
3144 column in the <ref table="Open_vSwitch"/> table must point to a
3145 valid SSL configuration when this form is used.
3148 If <var>port</var> is not specified, it currently defaults to
3149 6633. In the future, the default will change to 6653, which is
3150 the IANA-defined value.
3153 SSL support is an optional feature that is not always built as
3154 part of Open vSwitch.
3157 <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
3160 Listens for connections on the specified TCP <var>port</var>. If
3161 <var>ip</var>, which must be expressed as an IP address (not a
3162 DNS name), is specified, then connections are restricted to the
3163 specified local IP address (either IPv4 or IPv6). If
3164 <var>ip</var> is an IPv6 address, wrap it in square brackets,
3165 e.g. <code>ptcp:6632:[::1]</code>. If <var>ip</var> is not
3166 specified then it listens only on IPv4 addresses.
3169 If <var>port</var> is not specified, it currently defaults to
3170 6633. In the future, the default will change to 6653, which is
3171 the IANA-defined value.
3175 <p>When multiple controllers are configured for a single bridge, the
3176 <ref column="target"/> values must be unique. Duplicate
3177 <ref column="target"/> values yield unspecified results.</p>
3180 <column name="connection_mode">
3181 <p>If it is specified, this setting must be one of the following
3182 strings that describes how Open vSwitch contacts this OpenFlow
3183 controller over the network:</p>
3186 <dt><code>in-band</code></dt>
3187 <dd>In this mode, this controller's OpenFlow traffic travels over the
3188 bridge associated with the controller. With this setting, Open
3189 vSwitch allows traffic to and from the controller regardless of the
3190 contents of the OpenFlow flow table. (Otherwise, Open vSwitch
3191 would never be able to connect to the controller, because it did
3192 not have a flow to enable it.) This is the most common connection
3193 mode because it is not necessary to maintain two independent
3195 <dt><code>out-of-band</code></dt>
3196 <dd>In this mode, OpenFlow traffic uses a control network separate
3197 from the bridge associated with this controller, that is, the
3198 bridge does not use any of its own network devices to communicate
3199 with the controller. The control network must be configured
3200 separately, before or after <code>ovs-vswitchd</code> is started.
3204 <p>If not specified, the default is implementation-specific.</p>
3208 <group title="Controller Failure Detection and Handling">
3209 <column name="max_backoff">
3210 Maximum number of milliseconds to wait between connection attempts.
3211 Default is implementation-specific.
3214 <column name="inactivity_probe">
3215 Maximum number of milliseconds of idle time on connection to
3216 controller before sending an inactivity probe message. If Open
3217 vSwitch does not communicate with the controller for the specified
3218 number of seconds, it will send a probe. If a response is not
3219 received for the same additional amount of time, Open vSwitch
3220 assumes the connection has been broken and attempts to reconnect.
3221 Default is implementation-specific. A value of 0 disables
3226 <group title="Asynchronous Message Configuration">
3228 OpenFlow switches send certain messages to controllers spontanenously,
3229 that is, not in response to any request from the controller. These
3230 messages are called ``asynchronous messages.'' These columns allow
3231 asynchronous messages to be limited or disabled to ensure the best use
3232 of network resources.
3235 <column name="enable_async_messages">
3236 The OpenFlow protocol enables asynchronous messages at time of
3237 connection establishment, which means that a controller can receive
3238 asynchronous messages, potentially many of them, even if it turns them
3239 off immediately after connecting. Set this column to
3240 <code>false</code> to change Open vSwitch behavior to disable, by
3241 default, all asynchronous messages. The controller can use the
3242 <code>NXT_SET_ASYNC_CONFIG</code> Nicira extension to OpenFlow to turn
3243 on any messages that it does want to receive, if any.
3246 <column name="controller_rate_limit">
3248 The maximum rate at which the switch will forward packets to the
3249 OpenFlow controller, in packets per second. This feature prevents a
3250 single bridge from overwhelming the controller. If not specified,
3251 the default is implementation-specific.
3255 In addition, when a high rate triggers rate-limiting, Open vSwitch
3256 queues controller packets for each port and transmits them to the
3257 controller at the configured rate. The <ref
3258 column="controller_burst_limit"/> value limits the number of queued
3259 packets. Ports on a bridge share the packet queue fairly.
3263 Open vSwitch maintains two such packet rate-limiters per bridge: one
3264 for packets sent up to the controller because they do not correspond
3265 to any flow, and the other for packets sent up to the controller by
3266 request through flow actions. When both rate-limiters are filled with
3267 packets, the actual rate that packets are sent to the controller is
3268 up to twice the specified rate.
3272 <column name="controller_burst_limit">
3273 In conjunction with <ref column="controller_rate_limit"/>,
3274 the maximum number of unused packet credits that the bridge will
3275 allow to accumulate, in packets. If not specified, the default
3276 is implementation-specific.
3280 <group title="Additional In-Band Configuration">
3281 <p>These values are considered only in in-band control mode (see
3282 <ref column="connection_mode"/>).</p>
3284 <p>When multiple controllers are configured on a single bridge, there
3285 should be only one set of unique values in these columns. If different
3286 values are set for these columns in different controllers, the effect
3289 <column name="local_ip">
3290 The IP address to configure on the local port,
3291 e.g. <code>192.168.0.123</code>. If this value is unset, then
3292 <ref column="local_netmask"/> and <ref column="local_gateway"/> are
3296 <column name="local_netmask">
3297 The IP netmask to configure on the local port,
3298 e.g. <code>255.255.255.0</code>. If <ref column="local_ip"/> is set
3299 but this value is unset, then the default is chosen based on whether
3300 the IP address is class A, B, or C.
3303 <column name="local_gateway">
3304 The IP address of the gateway to configure on the local port, as a
3305 string, e.g. <code>192.168.0.1</code>. Leave this column unset if
3306 this network has no gateway.
3310 <group title="Controller Status">
3311 <column name="is_connected">
3312 <code>true</code> if currently connected to this controller,
3313 <code>false</code> otherwise.
3317 type='{"type": "string", "enum": ["set", ["other", "master", "slave"]]}'>
3318 <p>The level of authority this controller has on the associated
3319 bridge. Possible values are:</p>
3321 <dt><code>other</code></dt>
3322 <dd>Allows the controller access to all OpenFlow features.</dd>
3323 <dt><code>master</code></dt>
3324 <dd>Equivalent to <code>other</code>, except that there may be at
3325 most one master controller at a time. When a controller configures
3326 itself as <code>master</code>, any existing master is demoted to
3327 the <code>slave</code>role.</dd>
3328 <dt><code>slave</code></dt>
3329 <dd>Allows the controller read-only access to OpenFlow features.
3330 Attempts to modify the flow table will be rejected with an
3331 error. Slave controllers do not receive OFPT_PACKET_IN or
3332 OFPT_FLOW_REMOVED messages, but they do receive OFPT_PORT_STATUS
3337 <column name="status" key="last_error">
3338 A human-readable description of the last error on the connection
3339 to the controller; i.e. <code>strerror(errno)</code>. This key
3340 will exist only if an error has occurred.
3343 <column name="status" key="state"
3344 type='{"type": "string", "enum": ["set", ["VOID", "BACKOFF", "CONNECTING", "ACTIVE", "IDLE"]]}'>
3346 The state of the connection to the controller:
3349 <dt><code>VOID</code></dt>
3350 <dd>Connection is disabled.</dd>
3352 <dt><code>BACKOFF</code></dt>
3353 <dd>Attempting to reconnect at an increasing period.</dd>
3355 <dt><code>CONNECTING</code></dt>
3356 <dd>Attempting to connect.</dd>
3358 <dt><code>ACTIVE</code></dt>
3359 <dd>Connected, remote host responsive.</dd>
3361 <dt><code>IDLE</code></dt>
3362 <dd>Connection is idle. Waiting for response to keep-alive.</dd>
3365 These values may change in the future. They are provided only for
3370 <column name="status" key="sec_since_connect"
3371 type='{"type": "integer", "minInteger": 0}'>
3372 The amount of time since this controller last successfully connected to
3373 the switch (in seconds). Value is empty if controller has never
3374 successfully connected.
3377 <column name="status" key="sec_since_disconnect"
3378 type='{"type": "integer", "minInteger": 1}'>
3379 The amount of time since this controller last disconnected from
3380 the switch (in seconds). Value is empty if controller has never
3385 <group title="Connection Parameters">
3387 Additional configuration for a connection between the controller
3388 and the Open vSwitch.
3391 <column name="other_config" key="dscp"
3392 type='{"type": "integer"}'>
3393 The Differentiated Service Code Point (DSCP) is specified using 6 bits
3394 in the Type of Service (TOS) field in the IP header. DSCP provides a
3395 mechanism to classify the network traffic and provide Quality of
3396 Service (QoS) on IP networks.
3398 The DSCP value specified here is used when establishing the connection
3399 between the controller and the Open vSwitch. If no value is specified,
3400 a default value of 48 is chosen. Valid DSCP values must be in the
3406 <group title="Common Columns">
3407 The overall purpose of these columns is described under <code>Common
3408 Columns</code> at the beginning of this document.
3410 <column name="external_ids"/>
3411 <column name="other_config"/>
3415 <table name="Manager" title="OVSDB management connection.">
3417 Configuration for a database connection to an Open vSwitch database
3422 This table primarily configures the Open vSwitch database
3423 (<code>ovsdb-server</code>), not the Open vSwitch switch
3424 (<code>ovs-vswitchd</code>). The switch does read the table to determine
3425 what connections should be treated as in-band.
3429 The Open vSwitch database server can initiate and maintain active
3430 connections to remote clients. It can also listen for database
3434 <group title="Core Features">
3435 <column name="target">
3436 <p>Connection method for managers.</p>
3438 The following connection methods are currently supported:
3441 <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
3444 The specified SSL <var>port</var> on the host at the given
3445 <var>ip</var>, which must be expressed as an IP address
3446 (not a DNS name). The <ref table="Open_vSwitch"
3447 column="ssl"/> column in the <ref table="Open_vSwitch"/>
3448 table must point to a valid SSL configuration when this
3452 If <var>port</var> is not specified, it currently defaults
3453 to 6632. In the future, the default will change to 6640,
3454 which is the IANA-defined value.
3457 SSL support is an optional feature that is not always
3458 built as part of Open vSwitch.
3462 <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt>
3465 The specified TCP <var>port</var> on the host at the given
3466 <var>ip</var>, which must be expressed as an IP address (not a
3467 DNS name), where <var>ip</var> can be IPv4 or IPv6 address. If
3468 <var>ip</var> is an IPv6 address, wrap it in square brackets,
3469 e.g. <code>tcp:[::1]:6632</code>.
3472 If <var>port</var> is not specified, it currently defaults
3473 to 6632. In the future, the default will change to 6640,
3474 which is the IANA-defined value.
3477 <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
3480 Listens for SSL connections on the specified TCP <var>port</var>.
3481 Specify 0 for <var>port</var> to have the kernel automatically
3482 choose an available port. If <var>ip</var>, which must be
3483 expressed as an IP address (not a DNS name), is specified, then
3484 connections are restricted to the specified local IP address
3485 (either IPv4 or IPv6 address). If <var>ip</var> is an IPv6
3486 address, wrap in square brackets,
3487 e.g. <code>pssl:6632:[::1]</code>. If <var>ip</var> is not
3488 specified then it listens only on IPv4 (but not IPv6) addresses.
3489 The <ref table="Open_vSwitch" column="ssl"/> column in the <ref
3490 table="Open_vSwitch"/> table must point to a valid SSL
3491 configuration when this form is used.
3494 If <var>port</var> is not specified, it currently defaults
3495 to 6632. In the future, the default will change to 6640,
3496 which is the IANA-defined value.
3499 SSL support is an optional feature that is not always built as
3500 part of Open vSwitch.
3503 <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt>
3506 Listens for connections on the specified TCP <var>port</var>.
3507 Specify 0 for <var>port</var> to have the kernel automatically
3508 choose an available port. If <var>ip</var>, which must be
3509 expressed as an IP address (not a DNS name), is specified, then
3510 connections are restricted to the specified local IP address
3511 (either IPv4 or IPv6 address). If <var>ip</var> is an IPv6
3512 address, wrap it in square brackets,
3513 e.g. <code>ptcp:6632:[::1]</code>. If <var>ip</var> is not
3514 specified then it listens only on IPv4 addresses.
3517 If <var>port</var> is not specified, it currently defaults
3518 to 6632. In the future, the default will change to 6640,
3519 which is the IANA-defined value.
3523 <p>When multiple managers are configured, the <ref column="target"/>
3524 values must be unique. Duplicate <ref column="target"/> values yield
3525 unspecified results.</p>
3528 <column name="connection_mode">
3530 If it is specified, this setting must be one of the following strings
3531 that describes how Open vSwitch contacts this OVSDB client over the
3536 <dt><code>in-band</code></dt>
3538 In this mode, this connection's traffic travels over a bridge
3539 managed by Open vSwitch. With this setting, Open vSwitch allows
3540 traffic to and from the client regardless of the contents of the
3541 OpenFlow flow table. (Otherwise, Open vSwitch would never be able
3542 to connect to the client, because it did not have a flow to enable
3543 it.) This is the most common connection mode because it is not
3544 necessary to maintain two independent networks.
3546 <dt><code>out-of-band</code></dt>
3548 In this mode, the client's traffic uses a control network separate
3549 from that managed by Open vSwitch, that is, Open vSwitch does not
3550 use any of its own network devices to communicate with the client.
3551 The control network must be configured separately, before or after
3552 <code>ovs-vswitchd</code> is started.
3557 If not specified, the default is implementation-specific.
3562 <group title="Client Failure Detection and Handling">
3563 <column name="max_backoff">
3564 Maximum number of milliseconds to wait between connection attempts.
3565 Default is implementation-specific.
3568 <column name="inactivity_probe">
3569 Maximum number of milliseconds of idle time on connection to the client
3570 before sending an inactivity probe message. If Open vSwitch does not
3571 communicate with the client for the specified number of seconds, it
3572 will send a probe. If a response is not received for the same
3573 additional amount of time, Open vSwitch assumes the connection has been
3574 broken and attempts to reconnect. Default is implementation-specific.
3575 A value of 0 disables inactivity probes.
3579 <group title="Status">
3580 <column name="is_connected">
3581 <code>true</code> if currently connected to this manager,
3582 <code>false</code> otherwise.
3585 <column name="status" key="last_error">
3586 A human-readable description of the last error on the connection
3587 to the manager; i.e. <code>strerror(errno)</code>. This key
3588 will exist only if an error has occurred.
3591 <column name="status" key="state"
3592 type='{"type": "string", "enum": ["set", ["VOID", "BACKOFF", "CONNECTING", "ACTIVE", "IDLE"]]}'>
3594 The state of the connection to the manager:
3597 <dt><code>VOID</code></dt>
3598 <dd>Connection is disabled.</dd>
3600 <dt><code>BACKOFF</code></dt>
3601 <dd>Attempting to reconnect at an increasing period.</dd>
3603 <dt><code>CONNECTING</code></dt>
3604 <dd>Attempting to connect.</dd>
3606 <dt><code>ACTIVE</code></dt>
3607 <dd>Connected, remote host responsive.</dd>
3609 <dt><code>IDLE</code></dt>
3610 <dd>Connection is idle. Waiting for response to keep-alive.</dd>
3613 These values may change in the future. They are provided only for
3618 <column name="status" key="sec_since_connect"
3619 type='{"type": "integer", "minInteger": 0}'>
3620 The amount of time since this manager last successfully connected
3621 to the database (in seconds). Value is empty if manager has never
3622 successfully connected.
3625 <column name="status" key="sec_since_disconnect"
3626 type='{"type": "integer", "minInteger": 0}'>
3627 The amount of time since this manager last disconnected from the
3628 database (in seconds). Value is empty if manager has never
3632 <column name="status" key="locks_held">
3633 Space-separated list of the names of OVSDB locks that the connection
3634 holds. Omitted if the connection does not hold any locks.
3637 <column name="status" key="locks_waiting">
3638 Space-separated list of the names of OVSDB locks that the connection is
3639 currently waiting to acquire. Omitted if the connection is not waiting
3643 <column name="status" key="locks_lost">
3644 Space-separated list of the names of OVSDB locks that the connection
3645 has had stolen by another OVSDB client. Omitted if no locks have been
3646 stolen from this connection.
3649 <column name="status" key="n_connections"
3650 type='{"type": "integer", "minInteger": 2}'>
3652 When <ref column="target"/> specifies a connection method that
3653 listens for inbound connections (e.g. <code>ptcp:</code> or
3654 <code>pssl:</code>) and more than one connection is actually active,
3655 the value is the number of active connections. Otherwise, this
3656 key-value pair is omitted.
3659 When multiple connections are active, status columns and key-value
3660 pairs (other than this one) report the status of one arbitrarily
3665 <column name="status" key="bound_port" type='{"type": "integer"}'>
3666 When <ref column="target"/> is <code>ptcp:</code> or
3667 <code>pssl:</code>, this is the TCP port on which the OVSDB server is
3668 listening. (This is is particularly useful when <ref
3669 column="target"/> specifies a port of 0, allowing the kernel to
3670 choose any available port.)
3674 <group title="Connection Parameters">
3676 Additional configuration for a connection between the manager
3677 and the Open vSwitch Database.
3680 <column name="other_config" key="dscp"
3681 type='{"type": "integer"}'>
3682 The Differentiated Service Code Point (DSCP) is specified using 6 bits
3683 in the Type of Service (TOS) field in the IP header. DSCP provides a
3684 mechanism to classify the network traffic and provide Quality of
3685 Service (QoS) on IP networks.
3687 The DSCP value specified here is used when establishing the connection
3688 between the manager and the Open vSwitch. If no value is specified, a
3689 default value of 48 is chosen. Valid DSCP values must be in the range
3694 <group title="Common Columns">
3695 The overall purpose of these columns is described under <code>Common
3696 Columns</code> at the beginning of this document.
3698 <column name="external_ids"/>
3699 <column name="other_config"/>
3703 <table name="NetFlow">
3704 A NetFlow target. NetFlow is a protocol that exports a number of
3705 details about terminating IP flows, such as the principals involved
3708 <column name="targets">
3709 NetFlow targets in the form
3710 <code><var>ip</var>:<var>port</var></code>. The <var>ip</var>
3711 must be specified numerically, not as a DNS name.
3714 <column name="engine_id">
3715 Engine ID to use in NetFlow messages. Defaults to datapath index
3719 <column name="engine_type">
3720 Engine type to use in NetFlow messages. Defaults to datapath
3721 index if not specified.
3724 <column name="active_timeout">
3725 The interval at which NetFlow records are sent for flows that are
3726 still active, in seconds. A value of <code>0</code> requests the
3727 default timeout (currently 600 seconds); a value of <code>-1</code>
3728 disables active timeouts.
3731 <column name="add_id_to_interface">
3732 <p>If this column's value is <code>false</code>, the ingress and egress
3733 interface fields of NetFlow flow records are derived from OpenFlow port
3734 numbers. When it is <code>true</code>, the 7 most significant bits of
3735 these fields will be replaced by the least significant 7 bits of the
3736 engine id. This is useful because many NetFlow collectors do not
3737 expect multiple switches to be sending messages from the same host, so
3738 they do not store the engine information which could be used to
3739 disambiguate the traffic.</p>
3740 <p>When this option is enabled, a maximum of 508 ports are supported.</p>
3743 <group title="Common Columns">
3744 The overall purpose of these columns is described under <code>Common
3745 Columns</code> at the beginning of this document.
3747 <column name="external_ids"/>
3752 SSL configuration for an Open_vSwitch.
3754 <column name="private_key">
3755 Name of a PEM file containing the private key used as the switch's
3756 identity for SSL connections to the controller.
3759 <column name="certificate">
3760 Name of a PEM file containing a certificate, signed by the
3761 certificate authority (CA) used by the controller and manager,
3762 that certifies the switch's private key, identifying a trustworthy
3766 <column name="ca_cert">
3767 Name of a PEM file containing the CA certificate used to verify
3768 that the switch is connected to a trustworthy controller.
3771 <column name="bootstrap_ca_cert">
3772 If set to <code>true</code>, then Open vSwitch will attempt to
3773 obtain the CA certificate from the controller on its first SSL
3774 connection and save it to the named PEM file. If it is successful,
3775 it will immediately drop the connection and reconnect, and from then
3776 on all SSL connections must be authenticated by a certificate signed
3777 by the CA certificate thus obtained. <em>This option exposes the
3778 SSL connection to a man-in-the-middle attack obtaining the initial
3779 CA certificate.</em> It may still be useful for bootstrapping.
3782 <group title="Common Columns">
3783 The overall purpose of these columns is described under <code>Common
3784 Columns</code> at the beginning of this document.
3786 <column name="external_ids"/>
3790 <table name="sFlow">
3791 <p>A set of sFlow(R) targets. sFlow is a protocol for remote
3792 monitoring of switches.</p>
3794 <column name="agent">
3795 Name of the network device whose IP address should be reported as the
3796 ``agent address'' to collectors. If not specified, the agent device is
3797 figured from the first target address and the routing table. If the
3798 routing table does not contain a route to the target, the IP address
3799 defaults to the <ref table="Controller" column="local_ip"/> in the
3800 collector's <ref table="Controller"/>. If an agent IP address cannot be
3801 determined any of these ways, sFlow is disabled.
3804 <column name="header">
3805 Number of bytes of a sampled packet to send to the collector.
3806 If not specified, the default is 128 bytes.
3809 <column name="polling">
3810 Polling rate in seconds to send port statistics to the collector.
3811 If not specified, defaults to 30 seconds.
3814 <column name="sampling">
3815 Rate at which packets should be sampled and sent to the collector.
3816 If not specified, defaults to 400, which means one out of 400
3817 packets, on average, will be sent to the collector.
3820 <column name="targets">
3821 sFlow targets in the form
3822 <code><var>ip</var>:<var>port</var></code>.
3825 <group title="Common Columns">
3826 The overall purpose of these columns is described under <code>Common
3827 Columns</code> at the beginning of this document.
3829 <column name="external_ids"/>
3833 <table name="IPFIX">
3834 <p>A set of IPFIX collectors. IPFIX is a protocol that exports a
3835 number of details about flows.</p>
3837 <column name="targets">
3838 IPFIX target collectors in the form
3839 <code><var>ip</var>:<var>port</var></code>.
3842 <column name="sampling">
3843 For per-bridge packet sampling, i.e. when this row is referenced
3844 from a <ref table="Bridge"/>, the rate at which packets should
3845 be sampled and sent to each target collector. If not specified,
3846 defaults to 400, which means one out of 400 packets, on average,
3847 will be sent to each target collector. Ignored for per-flow
3848 sampling, i.e. when this row is referenced from a <ref
3849 table="Flow_Sample_Collector_Set"/>.
3852 <column name="obs_domain_id">
3853 For per-bridge packet sampling, i.e. when this row is referenced
3854 from a <ref table="Bridge"/>, the IPFIX Observation Domain ID
3855 sent in each IPFIX packet. If not specified, defaults to 0.
3856 Ignored for per-flow sampling, i.e. when this row is referenced
3857 from a <ref table="Flow_Sample_Collector_Set"/>.
3860 <column name="obs_point_id">
3861 For per-bridge packet sampling, i.e. when this row is referenced
3862 from a <ref table="Bridge"/>, the IPFIX Observation Point ID
3863 sent in each IPFIX flow record. If not specified, defaults to
3864 0. Ignored for per-flow sampling, i.e. when this row is
3865 referenced from a <ref table="Flow_Sample_Collector_Set"/>.
3868 <column name="cache_active_timeout">
3869 The maximum period in seconds for which an IPFIX flow record is
3870 cached and aggregated before being sent. If not specified,
3871 defaults to 0. If 0, caching is disabled.
3874 <column name="cache_max_flows">
3875 The maximum number of IPFIX flow records that can be cached at a
3876 time. If not specified, defaults to 0. If 0, caching is
3880 <group title="Common Columns">
3881 The overall purpose of these columns is described under <code>Common
3882 Columns</code> at the beginning of this document.
3884 <column name="external_ids"/>
3888 <table name="Flow_Sample_Collector_Set">
3889 <p>A set of IPFIX collectors of packet samples generated by
3890 OpenFlow <code>sample</code> actions.</p>
3893 The ID of this collector set, unique among the bridge's
3894 collector sets, to be used as the <code>collector_set_id</code>
3895 in OpenFlow <code>sample</code> actions.
3898 <column name="bridge">
3899 The bridge into which OpenFlow <code>sample</code> actions can
3900 be added to send packet samples to this set of IPFIX collectors.
3903 <column name="ipfix">
3904 Configuration of the set of IPFIX collectors to send one flow
3905 record per sampled packet to.
3908 <group title="Common Columns">
3909 The overall purpose of these columns is described under <code>Common
3910 Columns</code> at the beginning of this document.
3912 <column name="external_ids"/>