]>
Commit | Line | Data |
---|---|---|
ce887677 | 1 | <?xml version="1.0" encoding="utf-8"?> |
89365653 | 2 | <database title="Open vSwitch Configuration Database"> |
c5f341ab BP |
3 | <p> |
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 | |
89365653 | 7 | record. Records in other tables are significant only when they |
c5f341ab BP |
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 | |
3fd8d445 | 12 | ``root set'' tables. |
c5f341ab | 13 | </p> |
89365653 | 14 | |
3fd8d445 BP |
15 | <h2>Common Columns</h2> |
16 | ||
17 | <p> | |
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 | |
21 | later. | |
22 | </p> | |
23 | ||
24 | <dl> | |
25 | <dt><code>other_config</code>: map of string-string pairs</dt> | |
26 | <dd> | |
27 | <p> | |
28 | Key-value pairs for configuring rarely used features. Supported keys, | |
29 | along with the forms taken by their values, are documented individually | |
30 | for each table. | |
31 | </p> | |
32 | <p> | |
33 | A few tables do not have <code>other_config</code> columns because no | |
34 | key-value pairs have yet been defined for them. | |
35 | </p> | |
36 | </dd> | |
37 | ||
38 | <dt><code>external_ids</code>: map of string-string pairs</dt> | |
39 | <dd> | |
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 | |
46 | table. | |
47 | </dd> | |
48 | </dl> | |
49 | ||
89365653 | 50 | <table name="Open_vSwitch" title="Open vSwitch configuration."> |
c5f341ab BP |
51 | Configuration for an Open vSwitch daemon. There must be exactly |
52 | one record in the <ref table="Open_vSwitch"/> table. | |
89365653 BP |
53 | |
54 | <group title="Configuration"> | |
55 | <column name="bridges"> | |
56 | Set of bridges managed by the daemon. | |
57 | </column> | |
58 | ||
89365653 BP |
59 | <column name="ssl"> |
60 | SSL used globally by the daemon. | |
61 | </column> | |
f5e7ed5d | 62 | |
3fd8d445 BP |
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"/>. | |
3fe80505 BP |
68 | </column> |
69 | ||
3fd8d445 BP |
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>. | |
f5e7ed5d | 73 | </column> |
89365653 BP |
74 | </group> |
75 | ||
76 | <group title="Status"> | |
77 | <column name="next_cfg"> | |
78 | Sequence number for client to increment. When a client modifies | |
79 | any part of the database configuration and wishes to wait for | |
80 | Open vSwitch to finish applying the changes, it may increment | |
81 | this sequence number. | |
82 | </column> | |
83 | ||
84 | <column name="cur_cfg"> | |
85 | Sequence number that Open vSwitch sets to the current value of | |
2e57b537 | 86 | <ref column="next_cfg"/> after it finishes applying a set of |
89365653 BP |
87 | configuration changes. |
88 | </column> | |
c1c9c9c4 | 89 | |
3fd8d445 | 90 | <group title="Statistics"> |
018f1525 | 91 | <p> |
3fd8d445 BP |
92 | The <code>statistics</code> column contains key-value pairs that |
93 | report statistics about a system running an Open vSwitch. These are | |
94 | updated periodically (currently, every 5 seconds). Key-value pairs | |
95 | that cannot be determined or that do not apply to a platform are | |
96 | omitted. | |
ce887677 BP |
97 | </p> |
98 | ||
f9e5e5b3 BP |
99 | <column name="other_config" key="enable-statistics" |
100 | type='{"type": "boolean"}'> | |
3fd8d445 BP |
101 | Statistics are disabled by default to avoid overhead in the common |
102 | case when statistics gathering is not useful. Set this value to | |
103 | <code>true</code> to enable populating the <ref column="statistics"/> | |
104 | column or to <code>false</code> to explicitly disable it. | |
105 | </column> | |
3fe80505 | 106 | |
f9e5e5b3 BP |
107 | <column name="statistics" key="cpu" |
108 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
109 | <p> |
110 | Number of CPU processors, threads, or cores currently online and | |
111 | available to the operating system on which Open vSwitch is running, | |
112 | as an integer. This may be less than the number installed, if some | |
113 | are not online or if they are not available to the operating | |
114 | system. | |
115 | </p> | |
116 | <p> | |
117 | Open vSwitch userspace processes are not multithreaded, but the | |
118 | Linux kernel-based datapath is. | |
119 | </p> | |
120 | </column> | |
ce887677 | 121 | |
3fd8d445 BP |
122 | <column name="statistics" key="load_average"> |
123 | A comma-separated list of three floating-point numbers, | |
124 | representing the system load average over the last 1, 5, and 15 | |
125 | minutes, respectively. | |
126 | </column> | |
ce887677 | 127 | |
3fd8d445 BP |
128 | <column name="statistics" key="memory"> |
129 | <p> | |
130 | A comma-separated list of integers, each of which represents a | |
131 | quantity of memory in kilobytes that describes the operating | |
132 | system on which Open vSwitch is running. In respective order, | |
133 | these values are: | |
134 | </p> | |
ce887677 | 135 | |
3fd8d445 BP |
136 | <ol> |
137 | <li>Total amount of RAM allocated to the OS.</li> | |
138 | <li>RAM allocated to the OS that is in use.</li> | |
139 | <li>RAM that can be flushed out to disk or otherwise discarded | |
140 | if that space is needed for another purpose. This number is | |
141 | necessarily less than or equal to the previous value.</li> | |
142 | <li>Total disk space allocated for swap.</li> | |
143 | <li>Swap space currently in use.</li> | |
144 | </ol> | |
ce887677 | 145 | |
3fd8d445 BP |
146 | <p> |
147 | On Linux, all five values can be determined and are included. On | |
148 | other operating systems, only the first two values can be | |
149 | determined, so the list will only have two values. | |
150 | </p> | |
151 | </column> | |
ce887677 | 152 | |
3fd8d445 BP |
153 | <column name="statistics" key="process_NAME"> |
154 | <p> | |
155 | One such key-value pair, with <code>NAME</code> replaced by | |
156 | a process name, will exist for each running Open vSwitch | |
157 | daemon process, with <var>name</var> replaced by the | |
158 | daemon's name (e.g. <code>process_ovs-vswitchd</code>). The | |
159 | value is a comma-separated list of integers. The integers | |
160 | represent the following, with memory measured in kilobytes | |
161 | and durations in milliseconds: | |
162 | </p> | |
ce887677 | 163 | |
3fd8d445 BP |
164 | <ol> |
165 | <li>The process's virtual memory size.</li> | |
166 | <li>The process's resident set size.</li> | |
167 | <li>The amount of user and system CPU time consumed by the | |
168 | process.</li> | |
169 | <li>The number of times that the process has crashed and been | |
170 | automatically restarted by the monitor.</li> | |
171 | <li>The duration since the process was started.</li> | |
172 | <li>The duration for which the process has been running.</li> | |
173 | </ol> | |
ce887677 | 174 | |
3fd8d445 BP |
175 | <p> |
176 | The interpretation of some of these values depends on whether the | |
177 | process was started with the <option>--monitor</option>. If it | |
178 | was not, then the crash count will always be 0 and the two | |
179 | durations will always be the same. If <option>--monitor</option> | |
180 | was given, then the crash count may be positive; if it is, the | |
181 | latter duration is the amount of time since the most recent crash | |
182 | and restart. | |
183 | </p> | |
ce887677 | 184 | |
3fd8d445 BP |
185 | <p> |
186 | There will be one key-value pair for each file in Open vSwitch's | |
187 | ``run directory'' (usually <code>/var/run/openvswitch</code>) | |
188 | whose name ends in <code>.pid</code>, whose contents are a | |
189 | process ID, and which is locked by a running process. The | |
190 | <var>name</var> is taken from the pidfile's name. | |
191 | </p> | |
ce887677 | 192 | |
3fd8d445 BP |
193 | <p> |
194 | Currently Open vSwitch is only able to obtain all of the above | |
195 | detail on Linux systems. On other systems, the same key-value | |
196 | pairs will be present but the values will always be the empty | |
197 | string. | |
198 | </p> | |
199 | </column> | |
ce887677 | 200 | |
3fd8d445 BP |
201 | <column name="statistics" key="file_systems"> |
202 | <p> | |
203 | A space-separated list of information on local, writable file | |
204 | systems. Each item in the list describes one file system and | |
205 | consists in turn of a comma-separated list of the following: | |
206 | </p> | |
ce887677 | 207 | |
3fd8d445 BP |
208 | <ol> |
209 | <li>Mount point, e.g. <code>/</code> or <code>/var/log</code>. | |
210 | Any spaces or commas in the mount point are replaced by | |
211 | underscores.</li> | |
212 | <li>Total size, in kilobytes, as an integer.</li> | |
213 | <li>Amount of storage in use, in kilobytes, as an integer.</li> | |
214 | </ol> | |
ce887677 | 215 | |
3fd8d445 BP |
216 | <p> |
217 | This key-value pair is omitted if there are no local, writable | |
218 | file systems or if Open vSwitch cannot obtain the needed | |
219 | information. | |
220 | </p> | |
221 | </column> | |
222 | </group> | |
89365653 | 223 | </group> |
94db5407 | 224 | |
538c6dfa BP |
225 | <group title="Version Reporting"> |
226 | <p> | |
6b4186af EJ |
227 | These columns report the types and versions of the hardware and |
228 | software running Open vSwitch. We recommend in general that software | |
229 | should test whether specific features are supported instead of relying | |
230 | on version number checks. These values are primarily intended for | |
231 | reporting to human administrators. | |
538c6dfa BP |
232 | </p> |
233 | ||
234 | <column name="ovs_version"> | |
d4da3acc | 235 | The Open vSwitch version number, e.g. <code>1.1.0</code>. |
538c6dfa BP |
236 | </column> |
237 | ||
8159b984 | 238 | <column name="db_version"> |
6b4186af | 239 | <p> |
8159b984 BP |
240 | The database schema version number in the form |
241 | <code><var>major</var>.<var>minor</var>.<var>tweak</var></code>, | |
242 | e.g. <code>1.2.3</code>. Whenever the database schema is changed in | |
243 | a non-backward compatible way (e.g. deleting a column or a table), | |
244 | <var>major</var> is incremented. When the database schema is changed | |
245 | in a backward compatible way (e.g. adding a new column), | |
246 | <var>minor</var> is incremented. When the database schema is changed | |
247 | cosmetically (e.g. reindenting its syntax), <var>tweak</var> is | |
248 | incremented. | |
249 | </p> | |
250 | ||
251 | <p> | |
252 | The schema version is part of the database schema, so it can also be | |
253 | retrieved by fetching the schema using the Open vSwitch database | |
254 | protocol. | |
255 | </p> | |
256 | </column> | |
257 | ||
538c6dfa BP |
258 | <column name="system_type"> |
259 | <p> | |
6b4186af EJ |
260 | An identifier for the type of system on top of which Open vSwitch |
261 | runs, e.g. <code>XenServer</code> or <code>KVM</code>. | |
262 | </p> | |
263 | <p> | |
264 | System integrators are responsible for choosing and setting an | |
265 | appropriate value for this column. | |
266 | </p> | |
538c6dfa BP |
267 | </column> |
268 | ||
269 | <column name="system_version"> | |
270 | <p> | |
6b4186af | 271 | The version of the system identified by <ref column="system_type"/>, |
404c1692 | 272 | e.g. <code>5.6.100-39265p</code> on XenServer 5.6.100 build 39265. |
6b4186af EJ |
273 | </p> |
274 | <p> | |
275 | System integrators are responsible for choosing and setting an | |
276 | appropriate value for this column. | |
277 | </p> | |
538c6dfa | 278 | </column> |
6b4186af | 279 | |
538c6dfa BP |
280 | </group> |
281 | ||
94db5407 BP |
282 | <group title="Database Configuration"> |
283 | <p> | |
284 | These columns primarily configure the Open vSwitch database | |
285 | (<code>ovsdb-server</code>), not the Open vSwitch switch | |
286 | (<code>ovs-vswitchd</code>). The OVSDB database also uses the <ref | |
287 | column="ssl"/> settings. | |
288 | </p> | |
289 | ||
290 | <p> | |
291 | The Open vSwitch switch does read the database configuration to | |
292 | determine remote IP addresses to which in-band control should apply. | |
293 | </p> | |
294 | ||
295 | <column name="manager_options"> | |
296 | Database clients to which the Open vSwitch database server should | |
297 | connect or to which it should listen, along with options for how these | |
298 | connection should be configured. See the <ref table="Manager"/> table | |
299 | for more information. | |
300 | </column> | |
94db5407 | 301 | </group> |
3fd8d445 BP |
302 | |
303 | <group title="Common Columns"> | |
304 | The overall purpose of these columns is described under <code>Common | |
305 | Columns</code> at the beginning of this document. | |
306 | ||
307 | <column name="other_config"/> | |
308 | <column name="external_ids"/> | |
309 | </group> | |
89365653 BP |
310 | </table> |
311 | ||
312 | <table name="Bridge"> | |
313 | <p> | |
314 | Configuration for a bridge within an | |
315 | <ref table="Open_vSwitch"/>. | |
316 | </p> | |
317 | <p> | |
318 | A <ref table="Bridge"/> record represents an Ethernet switch with one or | |
319 | more ``ports,'' which are the <ref table="Port"/> records pointed to by | |
320 | the <ref table="Bridge"/>'s <ref column="ports"/> column. | |
321 | </p> | |
322 | ||
323 | <group title="Core Features"> | |
324 | <column name="name"> | |
325 | Bridge identifier. Should be alphanumeric and no more than about 8 | |
326 | bytes long. Must be unique among the names of ports, interfaces, and | |
327 | bridges on a host. | |
328 | </column> | |
329 | ||
330 | <column name="ports"> | |
331 | Ports included in the bridge. | |
332 | </column> | |
333 | ||
334 | <column name="mirrors"> | |
335 | Port mirroring configuration. | |
336 | </column> | |
337 | ||
338 | <column name="netflow"> | |
339 | NetFlow configuration. | |
340 | </column> | |
341 | ||
342 | <column name="sflow"> | |
343 | sFlow configuration. | |
344 | </column> | |
345 | ||
346 | <column name="flood_vlans"> | |
6c2d2a9f BP |
347 | <p> |
348 | VLAN IDs of VLANs on which MAC address learning should be disabled, | |
349 | so that packets are flooded instead of being sent to specific ports | |
350 | that are believed to contain packets' destination MACs. This should | |
351 | ordinarily be used to disable MAC learning on VLANs used for | |
352 | mirroring (RSPAN VLANs). It may also be useful for debugging. | |
353 | </p> | |
354 | <p> | |
355 | SLB bonding (see the <ref table="Port" column="bond_mode"/> column in | |
356 | the <ref table="Port"/> table) is incompatible with | |
357 | <code>flood_vlans</code>. Consider using another bonding mode or | |
358 | a different type of mirror instead. | |
359 | </p> | |
89365653 BP |
360 | </column> |
361 | </group> | |
362 | ||
363 | <group title="OpenFlow Configuration"> | |
364 | <column name="controller"> | |
88f69f88 BP |
365 | <p> |
366 | OpenFlow controller set. If unset, then no OpenFlow controllers | |
367 | will be used. | |
368 | </p> | |
369 | ||
370 | <p> | |
371 | If there are primary controllers, removing all of them clears the | |
372 | flow table. If there are no primary controllers, adding one also | |
373 | clears the flow table. Other changes to the set of controllers, such | |
374 | as adding or removing a service controller, adding another primary | |
375 | controller to supplement an existing primary controller, or removing | |
376 | only one of two primary controllers, have no effect on the flow | |
377 | table. | |
378 | </p> | |
89365653 BP |
379 | </column> |
380 | ||
254750ce BP |
381 | <column name="flow_tables"> |
382 | Configuration for OpenFlow tables. Each pair maps from an OpenFlow | |
383 | table ID to configuration for that table. | |
384 | </column> | |
385 | ||
31681a5d JP |
386 | <column name="fail_mode"> |
387 | <p>When a controller is configured, it is, ordinarily, responsible | |
3fd8d445 BP |
388 | for setting up all flows on the switch. Thus, if the connection to |
389 | the controller fails, no new network connections can be set up. | |
390 | If the connection to the controller stays down long enough, | |
391 | no packets can pass through the switch at all. This setting | |
392 | determines the switch's response to such a situation. It may be set | |
393 | to one of the following: | |
394 | <dl> | |
395 | <dt><code>standalone</code></dt> | |
396 | <dd>If no message is received from the controller for three | |
397 | times the inactivity probe interval | |
398 | (see <ref column="inactivity_probe"/>), then Open vSwitch | |
399 | will take over responsibility for setting up flows. In | |
400 | this mode, Open vSwitch causes the bridge to act like an | |
401 | ordinary MAC-learning switch. Open vSwitch will continue | |
402 | to retry connecting to the controller in the background | |
403 | and, when the connection succeeds, it will discontinue its | |
404 | standalone behavior.</dd> | |
405 | <dt><code>secure</code></dt> | |
406 | <dd>Open vSwitch will not set up flows on its own when the | |
407 | controller connection fails or when no controllers are | |
408 | defined. The bridge will continue to retry connecting to | |
409 | any defined controllers forever.</dd> | |
410 | </dl> | |
31681a5d | 411 | </p> |
aed2db18 BP |
412 | <p> |
413 | The default is <code>standalone</code> if the value is unset, but | |
414 | future versions of Open vSwitch may change the default. | |
415 | </p> | |
7dea6ace BP |
416 | <p> |
417 | The <code>standalone</code> mode can create forwarding loops on a | |
418 | bridge that has more than one uplink port unless STP is enabled. To | |
419 | avoid loops on such a bridge, configure <code>secure</code> mode or | |
420 | enable STP (see <ref column="stp_enable"/>). | |
421 | </p> | |
299a244b | 422 | <p>When more than one controller is configured, |
3fd8d445 BP |
423 | <ref column="fail_mode"/> is considered only when none of the |
424 | configured controllers can be contacted.</p> | |
88f69f88 BP |
425 | <p> |
426 | Changing <ref column="fail_mode"/> when no primary controllers are | |
427 | configured clears the flow table. | |
428 | </p> | |
31681a5d JP |
429 | </column> |
430 | ||
89365653 | 431 | <column name="datapath_id"> |
8de67146 BP |
432 | Reports the OpenFlow datapath ID in use. Exactly 16 hex digits. |
433 | (Setting this column has no useful effect. Set <ref | |
434 | column="other-config" key="datapath-id"/> instead.) | |
89365653 | 435 | </column> |
3fd8d445 BP |
436 | |
437 | <column name="other_config" key="datapath-id"> | |
438 | Exactly 16 hex digits to set the OpenFlow datapath ID to a specific | |
439 | value. May not be all-zero. | |
440 | </column> | |
441 | ||
8b6ff729 BP |
442 | <column name="other_config" key="dp-desc"> |
443 | Human readable description of datapath. It it a maximum 256 | |
444 | byte-long free-form string to describe the datapath for | |
445 | debugging purposes, e.g. <code>switch3 in room 3120</code>. | |
446 | </column> | |
447 | ||
f9e5e5b3 BP |
448 | <column name="other_config" key="disable-in-band" |
449 | type='{"type": "boolean"}'> | |
3fd8d445 BP |
450 | If set to <code>true</code>, disable in-band control on the bridge |
451 | regardless of controller and manager settings. | |
452 | </column> | |
453 | ||
f9e5e5b3 BP |
454 | <column name="other_config" key="in-band-queue" |
455 | type='{"type": "integer", "minInteger": 0, "maxInteger": 4294967295}'> | |
3fd8d445 BP |
456 | A queue ID as a nonnegative integer. This sets the OpenFlow queue ID |
457 | that will be used by flows set up by in-band control on this bridge. | |
458 | If unset, or if the port used by an in-band control flow does not have | |
459 | QoS configured, or if the port does not have a queue with the specified | |
460 | ID, the default queue is used instead. | |
461 | </column> | |
7beaa082 SH |
462 | |
463 | <column name="protocols"> | |
464 | List of OpenFlow protocols that may be used when negotiating a | |
465 | connection with a controller. A default value of | |
466 | <code>OpenFlow10</code> will be used if this column is empty. | |
467 | </column> | |
89365653 BP |
468 | </group> |
469 | ||
21f7563c JP |
470 | <group title="Spanning Tree Configuration"> |
471 | The IEEE 802.1D Spanning Tree Protocol (STP) is a network protocol | |
472 | that ensures loop-free topologies. It allows redundant links to | |
473 | be included in the network to provide automatic backup paths if | |
474 | the active links fails. | |
475 | ||
476 | <column name="stp_enable"> | |
477 | Enable spanning tree on the bridge. By default, STP is disabled | |
478 | on bridges. Bond, internal, and mirror ports are not supported | |
479 | and will not participate in the spanning tree. | |
480 | </column> | |
9cc6bf75 | 481 | |
21f7563c JP |
482 | <column name="other_config" key="stp-system-id"> |
483 | The bridge's STP identifier (the lower 48 bits of the bridge-id) | |
484 | in the form | |
485 | <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>. | |
486 | By default, the identifier is the MAC address of the bridge. | |
487 | </column> | |
488 | ||
489 | <column name="other_config" key="stp-priority" | |
490 | type='{"type": "integer", "minInteger": 0, "maxInteger": 65535}'> | |
491 | The bridge's relative priority value for determining the root | |
492 | bridge (the upper 16 bits of the bridge-id). A bridge with the | |
493 | lowest bridge-id is elected the root. By default, the priority | |
494 | is 0x8000. | |
495 | </column> | |
496 | ||
497 | <column name="other_config" key="stp-hello-time" | |
498 | type='{"type": "integer", "minInteger": 1, "maxInteger": 10}'> | |
499 | The interval between transmissions of hello messages by | |
500 | designated ports, in seconds. By default the hello interval is | |
501 | 2 seconds. | |
502 | </column> | |
503 | ||
504 | <column name="other_config" key="stp-max-age" | |
505 | type='{"type": "integer", "minInteger": 6, "maxInteger": 40}'> | |
506 | The maximum age of the information transmitted by the bridge | |
507 | when it is the root bridge, in seconds. By default, the maximum | |
508 | age is 20 seconds. | |
509 | </column> | |
510 | ||
511 | <column name="other_config" key="stp-forward-delay" | |
512 | type='{"type": "integer", "minInteger": 4, "maxInteger": 30}'> | |
513 | The delay to wait between transitioning root and designated | |
514 | ports to <code>forwarding</code>, in seconds. By default, the | |
515 | forwarding delay is 15 seconds. | |
516 | </column> | |
517 | </group> | |
518 | ||
89365653 BP |
519 | <group title="Other Features"> |
520 | <column name="datapath_type"> | |
521 | Name of datapath provider. The kernel datapath has | |
522 | type <code>system</code>. The userspace datapath has | |
523 | type <code>netdev</code>. | |
524 | </column> | |
525 | ||
3fd8d445 BP |
526 | <column name="external_ids" key="bridge-id"> |
527 | A unique identifier of the bridge. On Citrix XenServer this will | |
528 | commonly be the same as | |
529 | <ref column="external_ids" key="xs-network-uuids"/>. | |
89365653 BP |
530 | </column> |
531 | ||
3fd8d445 BP |
532 | <column name="external_ids" key="xs-network-uuids"> |
533 | Semicolon-delimited set of universally unique identifier(s) for the | |
534 | network with which this bridge is associated on a Citrix XenServer | |
535 | host. The network identifiers are RFC 4122 UUIDs as displayed by, | |
536 | e.g., <code>xe network-list</code>. | |
537 | </column> | |
538 | ||
539 | <column name="other_config" key="hwaddr"> | |
540 | An Ethernet address in the form | |
541 | <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var> | |
542 | to set the hardware address of the local port and influence the | |
543 | datapath ID. | |
544 | </column> | |
545 | ||
f9e5e5b3 BP |
546 | <column name="other_config" key="flow-eviction-threshold" |
547 | type='{"type": "integer", "minInteger": 0}'> | |
3fd8d445 BP |
548 | <p> |
549 | A number of flows as a nonnegative integer. This sets number of | |
550 | flows at which eviction from the kernel flow table will be triggered. | |
551 | If there are a large number of flows then increasing this value to | |
552 | around the number of flows present can result in reduced CPU usage | |
553 | and packet loss. | |
554 | </p> | |
555 | <p> | |
556 | The default is 1000. Values below 100 will be rounded up to 100. | |
557 | </p> | |
558 | </column> | |
559 | ||
f9e5e5b3 BP |
560 | <column name="other_config" key="forward-bpdu" |
561 | type='{"type": "boolean"}'> | |
21f7563c JP |
562 | Option to allow forwarding of BPDU frames when NORMAL action is |
563 | invoked. Frames with reserved Ethernet addresses (e.g. STP | |
564 | BPDU) will be forwarded when this option is enabled and the | |
565 | switch is not providing that functionality. If STP is enabled | |
566 | on the port, STP BPDUs will never be forwarded. If the Open | |
567 | vSwitch bridge is used to connect different Ethernet networks, | |
568 | and if Open vSwitch node does not run STP, then this option | |
569 | should be enabled. Default is disabled, set to | |
570 | <code>true</code> to enable. | |
05be4e2c EJ |
571 | |
572 | The following destination MAC addresss will not be forwarded when this | |
573 | option is enabled. | |
574 | <dl> | |
575 | <dt><code>01:80:c2:00:00:00</code></dt> | |
576 | <dd>IEEE 802.1D Spanning Tree Protocol (STP).</dd> | |
577 | ||
578 | <dt><code>01:80:c2:00:00:01</code></dt> | |
579 | <dd>IEEE Pause frame.</dd> | |
580 | ||
581 | <dt><code>01:80:c2:00:00:0<var>x</var></code></dt> | |
582 | <dd>Other reserved protocols.</dd> | |
583 | ||
7d48a4cc BP |
584 | <dt><code>00:e0:2b:00:00:00</code></dt> |
585 | <dd>Extreme Discovery Protocol (EDP).</dd> | |
c93f9a78 | 586 | |
7d48a4cc BP |
587 | <dt> |
588 | <code>00:e0:2b:00:00:04</code> and <code>00:e0:2b:00:00:06</code> | |
589 | </dt> | |
590 | <dd>Ethernet Automatic Protection Switching (EAPS).</dd> | |
c93f9a78 | 591 | |
05be4e2c EJ |
592 | <dt><code>01:00:0c:cc:cc:cc</code></dt> |
593 | <dd> | |
594 | Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), | |
595 | Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAgP), | |
596 | and others. | |
597 | </dd> | |
598 | ||
599 | <dt><code>01:00:0c:cc:cc:cd</code></dt> | |
600 | <dd>Cisco Shared Spanning Tree Protocol PVSTP+.</dd> | |
601 | ||
602 | <dt><code>01:00:0c:cd:cd:cd</code></dt> | |
603 | <dd>Cisco STP Uplink Fast.</dd> | |
604 | ||
605 | <dt><code>01:00:0c:00:00:00</code></dt> | |
606 | <dd>Cisco Inter Switch Link.</dd> | |
7d48a4cc BP |
607 | |
608 | <dt><code>01:00:0c:cc:cc:c<var>x</var></code></dt> | |
609 | <dd>Cisco CFM.</dd> | |
05be4e2c | 610 | </dl> |
21f7563c | 611 | </column> |
e764773c BP |
612 | |
613 | <column name="other_config" key="mac-aging-time" | |
614 | type='{"type": "integer", "minInteger": 1}'> | |
615 | <p> | |
616 | The maximum number of seconds to retain a MAC learning entry for | |
617 | which no packets have been seen. The default is currently 300 | |
618 | seconds (5 minutes). The value, if specified, is forced into a | |
619 | reasonable range, currently 15 to 3600 seconds. | |
620 | </p> | |
621 | ||
622 | <p> | |
623 | A short MAC aging time allows a network to more quickly detect that a | |
624 | host is no longer connected to a switch port. However, it also makes | |
625 | it more likely that packets will be flooded unnecessarily, when they | |
626 | are addressed to a connected host that rarely transmits packets. To | |
627 | reduce the incidence of unnecessary flooding, use a MAC aging time | |
628 | longer than the maximum interval at which a host will ordinarily | |
629 | transmit packets. | |
630 | </p> | |
631 | </column> | |
c4069512 BP |
632 | |
633 | <column name="other_config" key="mac-table-size" | |
634 | type='{"type": "integer", "minInteger": 1}'> | |
635 | <p> | |
636 | The maximum number of MAC addresses to learn. The default is | |
637 | currently 2048. The value, if specified, is forced into a reasonable | |
638 | range, currently 10 to 1,000,000. | |
639 | </p> | |
640 | </column> | |
21f7563c JP |
641 | </group> |
642 | ||
643 | <group title="Bridge Status"> | |
644 | <p> | |
645 | Status information about bridges. | |
646 | </p> | |
647 | <column name="status"> | |
648 | Key-value pairs that report bridge status. | |
649 | </column> | |
650 | <column name="status" key="stp_bridge_id"> | |
651 | <p> | |
652 | The bridge-id (in hex) used in spanning tree advertisements. | |
653 | Configuring the bridge-id is described in the | |
654 | <code>stp-system-id</code> and <code>stp-priority</code> keys | |
655 | of the <code>other_config</code> section earlier. | |
656 | </p> | |
657 | </column> | |
658 | <column name="status" key="stp_designated_root"> | |
659 | <p> | |
660 | The designated root (in hex) for this spanning tree. | |
661 | </p> | |
662 | </column> | |
663 | <column name="status" key="stp_root_path_cost"> | |
664 | <p> | |
665 | The path cost of reaching the designated bridge. A lower | |
666 | number is better. | |
667 | </p> | |
89365653 BP |
668 | </column> |
669 | </group> | |
3fd8d445 BP |
670 | |
671 | <group title="Common Columns"> | |
672 | The overall purpose of these columns is described under <code>Common | |
673 | Columns</code> at the beginning of this document. | |
674 | ||
675 | <column name="other_config"/> | |
676 | <column name="external_ids"/> | |
677 | </group> | |
89365653 BP |
678 | </table> |
679 | ||
680 | <table name="Port" table="Port or bond configuration."> | |
681 | <p>A port within a <ref table="Bridge"/>.</p> | |
682 | <p>Most commonly, a port has exactly one ``interface,'' pointed to by its | |
3fd8d445 BP |
683 | <ref column="interfaces"/> column. Such a port logically |
684 | corresponds to a port on a physical Ethernet switch. A port | |
685 | with more than one interface is a ``bonded port'' (see | |
686 | <ref group="Bonding Configuration"/>).</p> | |
89365653 | 687 | <p>Some properties that one might think as belonging to a port are actually |
3fd8d445 | 688 | part of the port's <ref table="Interface"/> members.</p> |
89365653 BP |
689 | |
690 | <column name="name"> | |
691 | Port name. Should be alphanumeric and no more than about 8 | |
692 | bytes long. May be the same as the interface name, for | |
693 | non-bonded ports. Must otherwise be unique among the names of | |
694 | ports, interfaces, and bridges on a host. | |
695 | </column> | |
696 | ||
697 | <column name="interfaces"> | |
698 | The port's interfaces. If there is more than one, this is a | |
699 | bonded Port. | |
700 | </column> | |
701 | ||
702 | <group title="VLAN Configuration"> | |
ecac4ebf BP |
703 | <p>Bridge ports support the following types of VLAN configuration:</p> |
704 | <dl> | |
705 | <dt>trunk</dt> | |
706 | <dd> | |
707 | <p> | |
708 | A trunk port carries packets on one or more specified VLANs | |
709 | specified in the <ref column="trunks"/> column (often, on every | |
710 | VLAN). A packet that ingresses on a trunk port is in the VLAN | |
711 | specified in its 802.1Q header, or VLAN 0 if the packet has no | |
712 | 802.1Q header. A packet that egresses through a trunk port will | |
5e9ceccd | 713 | have an 802.1Q header if it has a nonzero VLAN ID. |
ecac4ebf BP |
714 | </p> |
715 | ||
716 | <p> | |
717 | Any packet that ingresses on a trunk port tagged with a VLAN that | |
718 | the port does not trunk is dropped. | |
719 | </p> | |
720 | </dd> | |
721 | ||
722 | <dt>access</dt> | |
723 | <dd> | |
724 | <p> | |
725 | An access port carries packets on exactly one VLAN specified in the | |
5e9ceccd BP |
726 | <ref column="tag"/> column. Packets egressing on an access port |
727 | have no 802.1Q header. | |
ecac4ebf BP |
728 | </p> |
729 | ||
730 | <p> | |
5e9ceccd BP |
731 | Any packet with an 802.1Q header with a nonzero VLAN ID that |
732 | ingresses on an access port is dropped, regardless of whether the | |
733 | VLAN ID in the header is the access port's VLAN ID. | |
ecac4ebf BP |
734 | </p> |
735 | </dd> | |
736 | ||
737 | <dt>native-tagged</dt> | |
738 | <dd> | |
739 | A native-tagged port resembles a trunk port, with the exception that | |
740 | a packet without an 802.1Q header that ingresses on a native-tagged | |
741 | port is in the ``native VLAN'' (specified in the <ref column="tag"/> | |
742 | column). | |
743 | </dd> | |
744 | ||
745 | <dt>native-untagged</dt> | |
746 | <dd> | |
747 | A native-untagged port resembles a native-tagged port, with the | |
748 | exception that a packet that egresses on a native-untagged port in | |
5e9ceccd | 749 | the native VLAN will not have an 802.1Q header. |
ecac4ebf BP |
750 | </dd> |
751 | </dl> | |
752 | <p> | |
753 | A packet will only egress through bridge ports that carry the VLAN of | |
754 | the packet, as described by the rules above. | |
89365653 BP |
755 | </p> |
756 | ||
ecac4ebf | 757 | <column name="vlan_mode"> |
7894d33b | 758 | <p> |
ecac4ebf BP |
759 | The VLAN mode of the port, as described above. When this column is |
760 | empty, a default mode is selected as follows: | |
7894d33b | 761 | </p> |
ecac4ebf BP |
762 | <ul> |
763 | <li> | |
764 | If <ref column="tag"/> contains a value, the port is an access | |
765 | port. The <ref column="trunks"/> column should be empty. | |
766 | </li> | |
767 | <li> | |
768 | Otherwise, the port is a trunk port. The <ref column="trunks"/> | |
769 | column value is honored if it is present. | |
770 | </li> | |
771 | </ul> | |
772 | </column> | |
773 | ||
774 | <column name="tag"> | |
7894d33b | 775 | <p> |
ecac4ebf BP |
776 | For an access port, the port's implicitly tagged VLAN. For a |
777 | native-tagged or native-untagged port, the port's native VLAN. Must | |
778 | be empty if this is a trunk port. | |
7894d33b | 779 | </p> |
89365653 BP |
780 | </column> |
781 | ||
782 | <column name="trunks"> | |
7894d33b | 783 | <p> |
ecac4ebf BP |
784 | For a trunk, native-tagged, or native-untagged port, the 802.1Q VLAN |
785 | or VLANs that this port trunks; if it is empty, then the port trunks | |
786 | all VLANs. Must be empty if this is an access port. | |
7894d33b BP |
787 | </p> |
788 | <p> | |
ecac4ebf BP |
789 | A native-tagged or native-untagged port always trunks its native |
790 | VLAN, regardless of whether <ref column="trunks"/> includes that | |
791 | VLAN. | |
7894d33b | 792 | </p> |
89365653 | 793 | </column> |
5e9ceccd BP |
794 | |
795 | <column name="other_config" key="priority-tags" | |
796 | type='{"type": "boolean"}'> | |
797 | <p> | |
798 | An 802.1Q header contains two important pieces of information: a VLAN | |
799 | ID and a priority. A frame with a zero VLAN ID, called a | |
800 | ``priority-tagged'' frame, is supposed to be treated the same way as | |
801 | a frame without an 802.1Q header at all (except for the priority). | |
802 | </p> | |
803 | ||
804 | <p> | |
805 | However, some network elements ignore any frame that has 802.1Q | |
806 | header at all, even when the VLAN ID is zero. Therefore, by default | |
807 | Open vSwitch does not output priority-tagged frames, instead omitting | |
808 | the 802.1Q header entirely if the VLAN ID is zero. Set this key to | |
809 | <code>true</code> to enable priority-tagged frames on a port. | |
810 | </p> | |
811 | ||
812 | <p> | |
813 | Regardless of this setting, Open vSwitch omits the 802.1Q header on | |
814 | output if both the VLAN ID and priority would be zero. | |
815 | </p> | |
816 | ||
817 | <p> | |
818 | All frames output to native-tagged ports have a nonzero VLAN ID, so | |
819 | this setting is not meaningful on native-tagged ports. | |
820 | </p> | |
821 | </column> | |
89365653 BP |
822 | </group> |
823 | ||
824 | <group title="Bonding Configuration"> | |
be02e7c3 | 825 | <p>A port that has more than one interface is a ``bonded port.'' Bonding |
d64e1870 BP |
826 | allows for load balancing and fail-over.</p> |
827 | ||
828 | <p> | |
829 | The following types of bonding will work with any kind of upstream | |
830 | switch. On the upstream switch, do not configure the interfaces as a | |
831 | bond: | |
832 | </p> | |
9f5073d8 EJ |
833 | |
834 | <dl> | |
835 | <dt><code>balance-slb</code></dt> | |
836 | <dd> | |
837 | Balances flows among slaves based on source MAC address and output | |
838 | VLAN, with periodic rebalancing as traffic patterns change. | |
839 | </dd> | |
840 | ||
841 | <dt><code>active-backup</code></dt> | |
842 | <dd> | |
843 | Assigns all flows to one slave, failing over to a backup slave when | |
629d868c BP |
844 | the active slave is disabled. This is the only bonding mode in which |
845 | interfaces may be plugged into different upstream switches. | |
9f5073d8 EJ |
846 | </dd> |
847 | </dl> | |
848 | ||
849 | <p> | |
fb0b29a3 | 850 | The following modes require the upstream switch to support 802.3ad with |
bdebeece | 851 | successful LACP negotiation: |
9f5073d8 EJ |
852 | </p> |
853 | ||
854 | <dl> | |
855 | <dt><code>balance-tcp</code></dt> | |
856 | <dd> | |
857 | Balances flows among slaves based on L2, L3, and L4 protocol | |
858 | information such as destination MAC address, IP address, and TCP | |
859 | port. | |
860 | </dd> | |
fb0b29a3 EJ |
861 | </dl> |
862 | ||
89365653 | 863 | <p>These columns apply only to bonded ports. Their values are |
3fd8d445 | 864 | otherwise ignored.</p> |
89365653 | 865 | |
27dcaa1a | 866 | <column name="bond_mode"> |
9f5073d8 | 867 | <p>The type of bonding used for a bonded port. Defaults to |
4df08875 | 868 | <code>active-backup</code> if unset. |
9f5073d8 | 869 | </p> |
be02e7c3 EJ |
870 | </column> |
871 | ||
96ada1a4 EJ |
872 | <column name="other_config" key="bond-hash-basis" |
873 | type='{"type": "integer"}'> | |
874 | An integer hashed along with flows when choosing output slaves in load | |
875 | balanced bonds. When changed, all flows will be assigned different | |
876 | hash values possibly causing slave selection decisions to change. Does | |
877 | not affect bonding modes which do not employ load balancing such as | |
878 | <code>active-backup</code>. | |
879 | </column> | |
880 | ||
3fd8d445 BP |
881 | <group title="Link Failure Detection"> |
882 | <p> | |
883 | An important part of link bonding is detecting that links are down so | |
884 | that they may be disabled. These settings determine how Open vSwitch | |
885 | detects link failure. | |
886 | </p> | |
89365653 | 887 | |
f9e5e5b3 BP |
888 | <column name="other_config" key="bond-detect-mode" |
889 | type='{"type": "string", "enum": ["set", ["carrier", "miimon"]]}'> | |
890 | The means used to detect link failures. Defaults to | |
3fd8d445 BP |
891 | <code>carrier</code> which uses each interface's carrier to detect |
892 | failures. When set to <code>miimon</code>, will check for failures | |
893 | by polling each interface's MII. | |
894 | </column> | |
89365653 | 895 | |
f9e5e5b3 BP |
896 | <column name="other_config" key="bond-miimon-interval" |
897 | type='{"type": "integer"}'> | |
3fd8d445 BP |
898 | The interval, in milliseconds, between successive attempts to poll |
899 | each interface's MII. Relevant only when <ref column="other_config" | |
900 | key="bond-detect-mode"/> is <code>miimon</code>. | |
901 | </column> | |
902 | ||
903 | <column name="bond_updelay"> | |
904 | <p> | |
1c144051 | 905 | The number of milliseconds for which the link must stay up on an |
3fd8d445 BP |
906 | interface before the interface is considered to be up. Specify |
907 | <code>0</code> to enable the interface immediately. | |
908 | </p> | |
909 | ||
910 | <p> | |
911 | This setting is honored only when at least one bonded interface is | |
912 | already enabled. When no interfaces are enabled, then the first | |
913 | bond interface to come up is enabled immediately. | |
914 | </p> | |
915 | </column> | |
916 | ||
917 | <column name="bond_downdelay"> | |
1c144051 | 918 | The number of milliseconds for which the link must stay down on an |
3fd8d445 BP |
919 | interface before the interface is considered to be down. Specify |
920 | <code>0</code> to disable the interface immediately. | |
921 | </column> | |
922 | </group> | |
c25c91fd | 923 | |
3fd8d445 BP |
924 | <group title="LACP Configuration"> |
925 | <p> | |
926 | LACP, the Link Aggregation Control Protocol, is an IEEE standard that | |
927 | allows switches to automatically detect that they are connected by | |
928 | multiple links and aggregate across those links. These settings | |
929 | control LACP behavior. | |
930 | </p> | |
931 | ||
932 | <column name="lacp"> | |
933 | Configures LACP on this port. LACP allows directly connected | |
76ea8efd AE |
934 | switches to negotiate which links may be bonded. LACP may be enabled |
935 | on non-bonded ports for the benefit of any switches they may be | |
c25c91fd EJ |
936 | connected to. <code>active</code> ports are allowed to initiate LACP |
937 | negotiations. <code>passive</code> ports are allowed to participate | |
938 | in LACP negotiations initiated by a remote switch, but not allowed to | |
bdebeece EJ |
939 | initiate such negotiations themselves. If LACP is enabled on a port |
940 | whose partner switch does not support LACP, the bond will be | |
941 | disabled. Defaults to <code>off</code> if unset. | |
3fd8d445 BP |
942 | </column> |
943 | ||
944 | <column name="other_config" key="lacp-system-id"> | |
945 | The LACP system ID of this <ref table="Port"/>. The system ID of a | |
946 | LACP bond is used to identify itself to its partners. Must be a | |
a9bf011b EJ |
947 | nonzero MAC address. Defaults to the bridge Ethernet address if |
948 | unset. | |
3fd8d445 BP |
949 | </column> |
950 | ||
f9e5e5b3 BP |
951 | <column name="other_config" key="lacp-system-priority" |
952 | type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'> | |
3fd8d445 BP |
953 | The LACP system priority of this <ref table="Port"/>. In LACP |
954 | negotiations, link status decisions are made by the system with the | |
f9e5e5b3 | 955 | numerically lower priority. |
3fd8d445 BP |
956 | </column> |
957 | ||
bf83f7c8 EJ |
958 | <column name="other_config" key="lacp-time" |
959 | type='{"type": "string", "enum": ["set", ["fast", "slow"]]}'> | |
3fd8d445 BP |
960 | <p> |
961 | The LACP timing which should be used on this <ref table="Port"/>. | |
bf83f7c8 EJ |
962 | By default <code>slow</code> is used. When configured to be |
963 | <code>fast</code> LACP heartbeats are requested at a rate of once | |
964 | per second causing connectivity problems to be detected more | |
965 | quickly. In <code>slow</code> mode, heartbeats are requested at a | |
966 | rate of once every 30 seconds. | |
3fd8d445 BP |
967 | </p> |
968 | </column> | |
3fd8d445 BP |
969 | </group> |
970 | ||
b62ee96f | 971 | <group title="Rebalancing Configuration"> |
3fd8d445 BP |
972 | <p> |
973 | These settings control behavior when a bond is in | |
b62ee96f | 974 | <code>balance-slb</code> or <code>balance-tcp</code> mode. |
3fd8d445 BP |
975 | </p> |
976 | ||
f9e5e5b3 | 977 | <column name="other_config" key="bond-rebalance-interval" |
bc1b010c EJ |
978 | type='{"type": "integer", "minInteger": 0, "maxInteger": 10000}'> |
979 | For a load balanced bonded port, the number of milliseconds between | |
980 | successive attempts to rebalance the bond, that is, to move flows | |
981 | from one interface on the bond to another in an attempt to keep usage | |
982 | of each interface roughly equal. If zero, load balancing is disabled | |
1c144051 | 983 | on the bond (link failure still cause flows to move). If |
bc1b010c | 984 | less than 1000ms, the rebalance interval will be 1000ms. |
3fd8d445 BP |
985 | </column> |
986 | </group> | |
987 | ||
988 | <column name="bond_fake_iface"> | |
989 | For a bonded port, whether to create a fake internal interface with the | |
990 | name of the port. Use only for compatibility with legacy software that | |
991 | requires this. | |
992 | </column> | |
89365653 BP |
993 | </group> |
994 | ||
21f7563c JP |
995 | <group title="Spanning Tree Configuration"> |
996 | <column name="other_config" key="stp-enable" | |
997 | type='{"type": "boolean"}'> | |
998 | If spanning tree is enabled on the bridge, member ports are | |
999 | enabled by default (with the exception of bond, internal, and | |
1000 | mirror ports which do not work with STP). If this column's | |
1001 | value is <code>false</code> spanning tree is disabled on the | |
1002 | port. | |
1003 | </column> | |
1004 | ||
1005 | <column name="other_config" key="stp-port-num" | |
1006 | type='{"type": "integer", "minInteger": 1, "maxInteger": 255}'> | |
1007 | The port number used for the lower 8 bits of the port-id. By | |
1008 | default, the numbers will be assigned automatically. If any | |
1009 | port's number is manually configured on a bridge, then they | |
1010 | must all be. | |
1011 | </column> | |
1012 | ||
1013 | <column name="other_config" key="stp-port-priority" | |
1014 | type='{"type": "integer", "minInteger": 0, "maxInteger": 255}'> | |
1015 | The port's relative priority value for determining the root | |
1016 | port (the upper 8 bits of the port-id). A port with a lower | |
1017 | port-id will be chosen as the root port. By default, the | |
1018 | priority is 0x80. | |
1019 | </column> | |
1020 | ||
1021 | <column name="other_config" key="stp-path-cost" | |
1022 | type='{"type": "integer", "minInteger": 0, "maxInteger": 65535}'> | |
1023 | Spanning tree path cost for the port. A lower number indicates | |
1024 | a faster link. By default, the cost is based on the maximum | |
1025 | speed of the link. | |
1026 | </column> | |
1027 | </group> | |
1028 | ||
89365653 | 1029 | <group title="Other Features"> |
c1c9c9c4 BP |
1030 | <column name="qos"> |
1031 | Quality of Service configuration for this port. | |
1032 | </column> | |
299a244b | 1033 | |
89365653 BP |
1034 | <column name="mac"> |
1035 | The MAC address to use for this port for the purpose of choosing the | |
1036 | bridge's MAC address. This column does not necessarily reflect the | |
1037 | port's actual MAC address, nor will setting it change the port's actual | |
1038 | MAC address. | |
1039 | </column> | |
1040 | ||
1041 | <column name="fake_bridge"> | |
1042 | Does this port represent a sub-bridge for its tagged VLAN within the | |
1043 | Bridge? See ovs-vsctl(8) for more information. | |
1044 | </column> | |
1045 | ||
3fd8d445 BP |
1046 | <column name="external_ids" key="fake-bridge-id-*"> |
1047 | External IDs for a fake bridge (see the <ref column="fake_bridge"/> | |
1048 | column) are defined by prefixing a <ref table="Bridge"/> <ref | |
1049 | table="Bridge" column="external_ids"/> key with | |
1050 | <code>fake-bridge-</code>, | |
1051 | e.g. <code>fake-bridge-xs-network-uuids</code>. | |
89365653 | 1052 | </column> |
3fd8d445 | 1053 | </group> |
89365653 | 1054 | |
21f7563c JP |
1055 | <group title="Port Status"> |
1056 | <p> | |
1057 | Status information about ports attached to bridges. | |
1058 | </p> | |
1059 | <column name="status"> | |
1060 | Key-value pairs that report port status. | |
1061 | </column> | |
1062 | <column name="status" key="stp_port_id"> | |
1063 | <p> | |
1064 | The port-id (in hex) used in spanning tree advertisements for | |
1065 | this port. Configuring the port-id is described in the | |
1066 | <code>stp-port-num</code> and <code>stp-port-priority</code> | |
1067 | keys of the <code>other_config</code> section earlier. | |
1068 | </p> | |
1069 | </column> | |
1070 | <column name="status" key="stp_state" | |
1071 | type='{"type": "string", "enum": ["set", | |
1072 | ["disabled", "listening", "learning", | |
1073 | "forwarding", "blocking"]]}'> | |
1074 | <p> | |
1075 | STP state of the port. | |
1076 | </p> | |
1077 | </column> | |
1078 | <column name="status" key="stp_sec_in_state" | |
1079 | type='{"type": "integer", "minInteger": 0}'> | |
1080 | <p> | |
1081 | The amount of time (in seconds) port has been in the current | |
1082 | STP state. | |
1083 | </p> | |
1084 | </column> | |
1085 | <column name="status" key="stp_role" | |
1086 | type='{"type": "string", "enum": ["set", | |
1087 | ["root", "designated", "alternate"]]}'> | |
1088 | <p> | |
1089 | STP role of the port. | |
1090 | </p> | |
1091 | </column> | |
1092 | </group> | |
1093 | ||
80740385 JP |
1094 | <group title="Port Statistics"> |
1095 | <p> | |
1096 | Key-value pairs that report port statistics. | |
1097 | </p> | |
1098 | <group title="Statistics: STP transmit and receive counters"> | |
1099 | <column name="statistics" key="stp_tx_count"> | |
1100 | Number of STP BPDUs sent on this port by the spanning | |
1101 | tree library. | |
1102 | </column> | |
1103 | <column name="statistics" key="stp_rx_count"> | |
1104 | Number of STP BPDUs received on this port and accepted by the | |
1105 | spanning tree library. | |
1106 | </column> | |
1107 | <column name="statistics" key="stp_error_count"> | |
1108 | Number of bad STP BPDUs received on this port. Bad BPDUs | |
1109 | include runt packets and those with an unexpected protocol ID. | |
1110 | </column> | |
1111 | </group> | |
1112 | </group> | |
1113 | ||
3fd8d445 BP |
1114 | <group title="Common Columns"> |
1115 | The overall purpose of these columns is described under <code>Common | |
1116 | Columns</code> at the beginning of this document. | |
1117 | ||
1118 | <column name="other_config"/> | |
1119 | <column name="external_ids"/> | |
89365653 BP |
1120 | </group> |
1121 | </table> | |
1122 | ||
1123 | <table name="Interface" title="One physical network device in a Port."> | |
1124 | An interface within a <ref table="Port"/>. | |
1125 | ||
1126 | <group title="Core Features"> | |
1127 | <column name="name"> | |
1128 | Interface name. Should be alphanumeric and no more than about 8 bytes | |
1129 | long. May be the same as the port name, for non-bonded ports. Must | |
1130 | otherwise be unique among the names of ports, interfaces, and bridges | |
1131 | on a host. | |
1132 | </column> | |
1133 | ||
1134 | <column name="mac"> | |
1135 | <p>Ethernet address to set for this interface. If unset then the | |
3fd8d445 | 1136 | default MAC address is used:</p> |
89365653 BP |
1137 | <ul> |
1138 | <li>For the local interface, the default is the lowest-numbered MAC | |
3fd8d445 BP |
1139 | address among the other bridge ports, either the value of the |
1140 | <ref table="Port" column="mac"/> in its <ref table="Port"/> record, | |
1141 | if set, or its actual MAC (for bonded ports, the MAC of its slave | |
1142 | whose name is first in alphabetical order). Internal ports and | |
1143 | bridge ports that are used as port mirroring destinations (see the | |
1144 | <ref table="Mirror"/> table) are ignored.</li> | |
2e57b537 | 1145 | <li>For other internal interfaces, the default MAC is randomly |
3fd8d445 | 1146 | generated.</li> |
89365653 | 1147 | <li>External interfaces typically have a MAC address associated with |
3fd8d445 | 1148 | their hardware.</li> |
89365653 BP |
1149 | </ul> |
1150 | <p>Some interfaces may not have a software-controllable MAC | |
1151 | address.</p> | |
1152 | </column> | |
1153 | ||
1154 | <column name="ofport"> | |
1155 | <p>OpenFlow port number for this interface. Unlike most columns, this | |
3fd8d445 BP |
1156 | column's value should be set only by Open vSwitch itself. Other |
1157 | clients should set this column to an empty set (the default) when | |
1158 | creating an <ref table="Interface"/>.</p> | |
89365653 | 1159 | <p>Open vSwitch populates this column when the port number becomes |
3fd8d445 BP |
1160 | known. If the interface is successfully added, |
1161 | <ref column="ofport"/> will be set to a number between 1 and 65535 | |
1162 | (generally either in the range 1 to 65279, inclusive, or 65534, the | |
1163 | port number for the OpenFlow ``local port''). If the interface | |
1164 | cannot be added then Open vSwitch sets this column | |
1165 | to -1.</p> | |
558e2cc5 GS |
1166 | <p>When <ref column="ofport_request"/> is not set, Open vSwitch picks |
1167 | an appropriate value for this column and then tries to keep the value | |
1168 | constant across restarts.</p> | |
89365653 | 1169 | </column> |
81816a5f JP |
1170 | |
1171 | <column name="ofport_request"> | |
1172 | <p>Requested OpenFlow port number for this interface. The port | |
1173 | number must be between 1 and 65279, inclusive. Some datapaths | |
1174 | cannot satisfy all requests for particular port numbers. When | |
1175 | this column is empty or the request cannot be fulfilled, the | |
1176 | system will choose a free port. The <ref column="ofport"/> | |
1177 | column reports the assigned OpenFlow port number.</p> | |
1178 | <p>The port number must be requested in the same transaction | |
1179 | that creates the port.</p> | |
1180 | </column> | |
89365653 BP |
1181 | </group> |
1182 | ||
1183 | <group title="System-Specific Details"> | |
1184 | <column name="type"> | |
3fd8d445 BP |
1185 | <p> |
1186 | The interface type, one of: | |
1187 | </p> | |
1188 | ||
89365653 BP |
1189 | <dl> |
1190 | <dt><code>system</code></dt> | |
1191 | <dd>An ordinary network device, e.g. <code>eth0</code> on Linux. | |
3fd8d445 BP |
1192 | Sometimes referred to as ``external interfaces'' since they are |
1193 | generally connected to hardware external to that on which the Open | |
1194 | vSwitch is running. The empty string is a synonym for | |
1195 | <code>system</code>.</dd> | |
1196 | ||
89365653 | 1197 | <dt><code>internal</code></dt> |
2e57b537 | 1198 | <dd>A simulated network device that sends and receives traffic. An |
3fd8d445 BP |
1199 | internal interface whose <ref column="name"/> is the same as its |
1200 | bridge's <ref table="Open_vSwitch" column="name"/> is called the | |
1201 | ``local interface.'' It does not make sense to bond an internal | |
1202 | interface, so the terms ``port'' and ``interface'' are often used | |
1203 | imprecisely for internal interfaces.</dd> | |
1204 | ||
89365653 BP |
1205 | <dt><code>tap</code></dt> |
1206 | <dd>A TUN/TAP device managed by Open vSwitch.</dd> | |
3fd8d445 | 1207 | |
89365653 | 1208 | <dt><code>gre</code></dt> |
3fd8d445 BP |
1209 | <dd> |
1210 | An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4 | |
79f827fa | 1211 | tunnel. |
e16a28b5 | 1212 | </dd> |
3fd8d445 | 1213 | |
e16a28b5 | 1214 | <dt><code>ipsec_gre</code></dt> |
3fd8d445 BP |
1215 | <dd> |
1216 | An Ethernet over RFC 2890 Generic Routing Encapsulation over IPv4 | |
9cc6bf75 | 1217 | IPsec tunnel. |
a28716da | 1218 | </dd> |
3fd8d445 | 1219 | |
2de795ad PS |
1220 | <dt><code>gre64</code></dt> |
1221 | <dd> | |
1222 | It is same as GRE, but it allows 64 bit key. To store higher 32-bits | |
1223 | of key, it uses GRE protocol sequence number field. This is non | |
1224 | standard use of GRE protocol since OVS does not increment | |
1225 | sequence number for every packet at time of encap as expected by | |
1226 | standard GRE implementation. See <ref group="Tunnel Options"/> | |
1227 | for information on configuring GRE tunnels. | |
1228 | </dd> | |
1229 | ||
1230 | <dt><code>ipsec_gre64</code></dt> | |
1231 | <dd> | |
1232 | Same as IPSEC_GRE except 64 bit key. | |
1233 | </dd> | |
1234 | ||
a28716da | 1235 | <dt><code>capwap</code></dt> |
3fd8d445 BP |
1236 | <dd> |
1237 | An Ethernet tunnel over the UDP transport portion of CAPWAP (RFC | |
1238 | 5415). This allows interoperability with certain switches that do | |
1239 | not support GRE. Only the tunneling component of the protocol is | |
1240 | implemented. UDP ports 58881 and 58882 are used as the source and | |
1241 | destination ports respectively. CAPWAP is currently supported only | |
89a1c6d0 | 1242 | with the Linux kernel datapath with kernel version 2.6.26 or later. |
1280bf0e PS |
1243 | |
1244 | CAPWAP support is deprecated and will be removed no earlier than | |
1245 | February 2013. | |
88720519 | 1246 | </dd> |
3fd8d445 | 1247 | |
79f827fa KM |
1248 | <dt><code>vxlan</code></dt> |
1249 | <dd> | |
1250 | <p> | |
1251 | An Ethernet tunnel over the experimental, UDP-based VXLAN | |
1252 | protocol described at | |
1253 | <code>http://tools.ietf.org/html/draft-mahalingam-dutt-dcops-vxlan-02</code>. | |
1254 | VXLAN is currently supported only with the Linux kernel datapath | |
1255 | with kernel version 2.6.26 or later. | |
1256 | </p> | |
1257 | <p> | |
1258 | As an experimental protocol, VXLAN has no officially assigned UDP | |
1259 | port. Open vSwitch currently uses UDP destination port 8472. | |
1260 | The source port used for VXLAN traffic varies on a per-flow basis | |
1261 | and is in the ephemeral port range. | |
1262 | </p> | |
1263 | </dd> | |
1264 | ||
8aed4223 | 1265 | <dt><code>patch</code></dt> |
eca2df31 | 1266 | <dd> |
3fd8d445 | 1267 | A pair of virtual devices that act as a patch cable. |
eca2df31 | 1268 | </dd> |
3fd8d445 | 1269 | |
84b32864 | 1270 | <dt><code>null</code></dt> |
0faed346 EJ |
1271 | <dd>An ignored interface. Deprecated and slated for removal in |
1272 | February 2013.</dd> | |
89365653 BP |
1273 | </dl> |
1274 | </column> | |
3fd8d445 BP |
1275 | </group> |
1276 | ||
1277 | <group title="Tunnel Options"> | |
1278 | <p> | |
1279 | These options apply to interfaces with <ref column="type"/> of | |
2de795ad | 1280 | <code>gre</code>, <code>ipsec_gre</code>, <code>gre64</code>, |
79f827fa KM |
1281 | <code>ipsec_gre64</code>, <code>capwap</code>, and |
1282 | <code>vxlan</code>. | |
3fd8d445 BP |
1283 | </p> |
1284 | ||
1285 | <p> | |
1286 | Each tunnel must be uniquely identified by the combination of <ref | |
1287 | column="type"/>, <ref column="options" key="remote_ip"/>, <ref | |
1288 | column="options" key="local_ip"/>, and <ref column="options" | |
1289 | key="in_key"/>. If two ports are defined that are the same except one | |
1290 | has an optional identifier and the other does not, the more specific | |
1291 | one is matched first. <ref column="options" key="in_key"/> is | |
1292 | considered more specific than <ref column="options" key="local_ip"/> if | |
1293 | a port defines one and another port defines the other. | |
1294 | </p> | |
1295 | ||
1296 | <column name="options" key="remote_ip"> | |
b37e6334 BP |
1297 | <p> |
1298 | Required. The tunnel endpoint. Unicast and multicast endpoints are | |
1299 | both supported. | |
1300 | </p> | |
1301 | ||
1302 | <p> | |
1303 | When a multicast endpoint is specified, a routing table lookup occurs | |
1304 | only when the tunnel is created. Following a routing change, delete | |
1305 | and then re-create the tunnel to force a new routing table lookup. | |
1306 | </p> | |
3fd8d445 BP |
1307 | </column> |
1308 | ||
1309 | <column name="options" key="local_ip"> | |
b37e6334 BP |
1310 | Optional. The destination IP that received packets must match. |
1311 | Default is to match all addresses. Must be omitted when <ref | |
1312 | column="options" key="remote_ip"/> is a multicast address. | |
3fd8d445 BP |
1313 | </column> |
1314 | ||
1315 | <column name="options" key="in_key"> | |
1316 | <p>Optional. The key that received packets must contain, one of:</p> | |
1317 | ||
1318 | <ul> | |
1319 | <li> | |
1320 | <code>0</code>. The tunnel receives packets with no key or with a | |
1321 | key of 0. This is equivalent to specifying no <ref column="options" | |
1322 | key="in_key"/> at all. | |
1323 | </li> | |
1324 | <li> | |
79f827fa KM |
1325 | A positive 24-bit (for VXLAN), 32-bit (for GRE) or 64-bit (for |
1326 | CAPWAP) number. The tunnel receives only packets with the | |
1327 | specified key. | |
3fd8d445 BP |
1328 | </li> |
1329 | <li> | |
1330 | The word <code>flow</code>. The tunnel accepts packets with any | |
1331 | key. The key will be placed in the <code>tun_id</code> field for | |
1332 | matching in the flow table. The <code>ovs-ofctl</code> manual page | |
1333 | contains additional information about matching fields in OpenFlow | |
1334 | flows. | |
1335 | </li> | |
1336 | </ul> | |
1337 | ||
1338 | <p> | |
1339 | </p> | |
1340 | </column> | |
1341 | ||
1342 | <column name="options" key="out_key"> | |
1343 | <p>Optional. The key to be set on outgoing packets, one of:</p> | |
1344 | ||
1345 | <ul> | |
1346 | <li> | |
1347 | <code>0</code>. Packets sent through the tunnel will have no key. | |
1348 | This is equivalent to specifying no <ref column="options" | |
1349 | key="out_key"/> at all. | |
1350 | </li> | |
1351 | <li> | |
79f827fa KM |
1352 | A positive 24-bit (for VXLAN), 32-bit (for GRE) or 64-bit (for |
1353 | CAPWAP) number. Packets sent through the tunnel will have the | |
1354 | specified key. | |
3fd8d445 BP |
1355 | </li> |
1356 | <li> | |
1357 | The word <code>flow</code>. Packets sent through the tunnel will | |
1358 | have the key set using the <code>set_tunnel</code> Nicira OpenFlow | |
1359 | vendor extension (0 is used in the absence of an action). The | |
1360 | <code>ovs-ofctl</code> manual page contains additional information | |
1361 | about the Nicira OpenFlow vendor extensions. | |
1362 | </li> | |
1363 | </ul> | |
1364 | </column> | |
1365 | ||
1366 | <column name="options" key="key"> | |
1367 | Optional. Shorthand to set <code>in_key</code> and | |
1368 | <code>out_key</code> at the same time. | |
1369 | </column> | |
1370 | ||
1371 | <column name="options" key="tos"> | |
1372 | Optional. The value of the ToS bits to be set on the encapsulating | |
749ae950 PS |
1373 | packet. ToS is interpreted as DSCP and ECN bits, ECN part must be |
1374 | zero. It may also be the word <code>inherit</code>, in which case | |
3fd8d445 BP |
1375 | the ToS will be copied from the inner packet if it is IPv4 or IPv6 |
1376 | (otherwise it will be 0). The ECN fields are always inherited. | |
1377 | Default is 0. | |
1378 | </column> | |
1379 | ||
1380 | <column name="options" key="ttl"> | |
1381 | Optional. The TTL to be set on the encapsulating packet. It may also | |
1382 | be the word <code>inherit</code>, in which case the TTL will be copied | |
1383 | from the inner packet if it is IPv4 or IPv6 (otherwise it will be the | |
1384 | system default, typically 64). Default is the system default TTL. | |
1385 | </column> | |
9cc6bf75 | 1386 | |
f9e5e5b3 BP |
1387 | <column name="options" key="df_default" |
1388 | type='{"type": "boolean"}'> | |
9b9f4d60 EJ |
1389 | Optional. If enabled, the Don't Fragment bit will be set on tunnel |
1390 | outer headers to allow path MTU discovery. Default is enabled; set | |
1391 | to <code>false</code> to disable. | |
3fd8d445 BP |
1392 | </column> |
1393 | ||
3fd8d445 BP |
1394 | <group title="Tunnel Options: gre and ipsec_gre only"> |
1395 | <p> | |
1396 | Only <code>gre</code> and <code>ipsec_gre</code> interfaces support | |
1397 | these options. | |
1398 | </p> | |
1399 | ||
f9e5e5b3 | 1400 | <column name="options" key="csum" type='{"type": "boolean"}'> |
3fd8d445 BP |
1401 | <p> |
1402 | Optional. Compute GRE checksums on outgoing packets. Default is | |
1403 | disabled, set to <code>true</code> to enable. Checksums present on | |
1404 | incoming packets will be validated regardless of this setting. | |
1405 | </p> | |
1406 | ||
1407 | <p> | |
1408 | GRE checksums impose a significant performance penalty because they | |
1409 | cover the entire packet. The encapsulated L3, L4, and L7 packet | |
1410 | contents typically have their own checksums, so this additional | |
1411 | checksum only adds value for the GRE and encapsulated L2 headers. | |
1412 | </p> | |
1413 | ||
1414 | <p> | |
1415 | This option is supported for <code>ipsec_gre</code>, but not useful | |
1416 | because GRE checksums are weaker than, and redundant with, IPsec | |
1417 | payload authentication. | |
1418 | </p> | |
1419 | </column> | |
1420 | </group> | |
1421 | ||
1422 | <group title="Tunnel Options: ipsec_gre only"> | |
1423 | <p> | |
1424 | Only <code>ipsec_gre</code> interfaces support these options. | |
1425 | </p> | |
1426 | ||
1427 | <column name="options" key="peer_cert"> | |
1428 | Required for certificate authentication. A string containing the | |
1429 | peer's certificate in PEM format. Additionally the host's | |
1430 | certificate must be specified with the <code>certificate</code> | |
1431 | option. | |
1432 | </column> | |
1433 | ||
1434 | <column name="options" key="certificate"> | |
1435 | Required for certificate authentication. The name of a PEM file | |
1436 | containing a certificate that will be presented to the peer during | |
1437 | authentication. | |
1438 | </column> | |
1439 | ||
1440 | <column name="options" key="private_key"> | |
1441 | Optional for certificate authentication. The name of a PEM file | |
1442 | containing the private key associated with <code>certificate</code>. | |
1443 | If <code>certificate</code> contains the private key, this option may | |
1444 | be omitted. | |
1445 | </column> | |
1446 | ||
1447 | <column name="options" key="psk"> | |
1448 | Required for pre-shared key authentication. Specifies a pre-shared | |
1449 | key for authentication that must be identical on both sides of the | |
1450 | tunnel. | |
1451 | </column> | |
1452 | </group> | |
1453 | </group> | |
1454 | ||
1455 | <group title="Patch Options"> | |
1456 | <p> | |
1457 | Only <code>patch</code> interfaces support these options. | |
1458 | </p> | |
89365653 | 1459 | |
3fd8d445 BP |
1460 | <column name="options" key="peer"> |
1461 | The <ref column="name"/> of the <ref table="Interface"/> for the other | |
1462 | side of the patch. The named <ref table="Interface"/>'s own | |
1463 | <code>peer</code> option must specify this <ref table="Interface"/>'s | |
1464 | name. That is, the two patch interfaces must have reversed <ref | |
1465 | column="name"/> and <code>peer</code> values. | |
89365653 | 1466 | </column> |
e210037e AE |
1467 | </group> |
1468 | ||
1469 | <group title="Interface Status"> | |
1470 | <p> | |
1471 | Status information about interfaces attached to bridges, updated every | |
1472 | 5 seconds. Not all interfaces have all of these properties; virtual | |
1473 | interfaces don't have a link speed, for example. Non-applicable | |
1474 | columns will have empty values. | |
1475 | </p> | |
1476 | <column name="admin_state"> | |
1477 | <p> | |
1478 | The administrative state of the physical network link. | |
1479 | </p> | |
1480 | </column> | |
1481 | ||
1482 | <column name="link_state"> | |
1483 | <p> | |
0b8024eb BP |
1484 | The observed state of the physical network link. This is ordinarily |
1485 | the link's carrier status. If the interface's <ref table="Port"/> is | |
1486 | a bond configured for miimon monitoring, it is instead the network | |
1487 | link's miimon status. | |
e210037e AE |
1488 | </p> |
1489 | </column> | |
1490 | ||
65c3058c EJ |
1491 | <column name="link_resets"> |
1492 | <p> | |
1493 | The number of times Open vSwitch has observed the | |
1494 | <ref column="link_state"/> of this <ref table="Interface"/> change. | |
1495 | </p> | |
1496 | </column> | |
1497 | ||
e210037e AE |
1498 | <column name="link_speed"> |
1499 | <p> | |
1500 | The negotiated speed of the physical network link. | |
1501 | Valid values are positive integers greater than 0. | |
1502 | </p> | |
1503 | </column> | |
1504 | ||
1505 | <column name="duplex"> | |
1506 | <p> | |
1507 | The duplex mode of the physical network link. | |
1508 | </p> | |
1509 | </column> | |
1510 | ||
1511 | <column name="mtu"> | |
1512 | <p> | |
1513 | The MTU (maximum transmission unit); i.e. the largest | |
1514 | amount of data that can fit into a single Ethernet frame. | |
1515 | The standard Ethernet MTU is 1500 bytes. Some physical media | |
1516 | and many kinds of virtual interfaces can be configured with | |
1517 | higher MTUs. | |
1518 | </p> | |
f915f1a8 BP |
1519 | <p> |
1520 | This column will be empty for an interface that does not | |
1521 | have an MTU as, for example, some kinds of tunnels do not. | |
1522 | </p> | |
e210037e | 1523 | </column> |
573c1db9 | 1524 | |
3fd8d445 BP |
1525 | <column name="lacp_current"> |
1526 | Boolean value indicating LACP status for this interface. If true, this | |
1527 | interface has current LACP information about its LACP partner. This | |
1528 | information may be used to monitor the health of interfaces in a LACP | |
1529 | enabled port. This column will be empty if LACP is not enabled. | |
1530 | </column> | |
1531 | ||
573c1db9 | 1532 | <column name="status"> |
3fd8d445 BP |
1533 | Key-value pairs that report port status. Supported status values are |
1534 | <ref column="type"/>-dependent; some interfaces may not have a valid | |
1535 | <ref column="status" key="driver_name"/>, for example. | |
1536 | </column> | |
1537 | ||
1538 | <column name="status" key="driver_name"> | |
1539 | The name of the device driver controlling the network adapter. | |
1540 | </column> | |
1541 | ||
1542 | <column name="status" key="driver_version"> | |
1543 | The version string of the device driver controlling the network | |
1544 | adapter. | |
1545 | </column> | |
1546 | ||
1547 | <column name="status" key="firmware_version"> | |
1548 | The version string of the network adapter's firmware, if available. | |
1549 | </column> | |
1550 | ||
1551 | <column name="status" key="source_ip"> | |
1552 | The source IP address used for an IPv4 tunnel end-point, such as | |
1553 | <code>gre</code> or <code>capwap</code>. | |
573c1db9 | 1554 | </column> |
3fd8d445 BP |
1555 | |
1556 | <column name="status" key="tunnel_egress_iface"> | |
1557 | Egress interface for tunnels. Currently only relevant for GRE and | |
1558 | CAPWAP tunnels. On Linux systems, this column will show the name of | |
1559 | the interface which is responsible for routing traffic destined for the | |
1560 | configured <ref column="options" key="remote_ip"/>. This could be an | |
1561 | internal interface such as a bridge port. | |
1562 | </column> | |
1563 | ||
f9e5e5b3 BP |
1564 | <column name="status" key="tunnel_egress_iface_carrier" |
1565 | type='{"type": "string", "enum": ["set", ["down", "up"]]}'> | |
1566 | Whether carrier is detected on <ref column="status" | |
1567 | key="tunnel_egress_iface"/>. | |
3fd8d445 BP |
1568 | </column> |
1569 | </group> | |
1570 | ||
1571 | <group title="Statistics"> | |
1572 | <p> | |
1573 | Key-value pairs that report interface statistics. The current | |
1574 | implementation updates these counters periodically. Future | |
1575 | implementations may update them when an interface is created, when they | |
1576 | are queried (e.g. using an OVSDB <code>select</code> operation), and | |
1577 | just before an interface is deleted due to virtual interface hot-unplug | |
1578 | or VM shutdown, and perhaps at other times, but not on any regular | |
1579 | periodic basis. | |
1580 | </p> | |
1581 | <p> | |
1582 | These are the same statistics reported by OpenFlow in its <code>struct | |
1583 | ofp_port_stats</code> structure. If an interface does not support a | |
1584 | given statistic, then that pair is omitted. | |
1585 | </p> | |
1586 | <group title="Statistics: Successful transmit and receive counters"> | |
1587 | <column name="statistics" key="rx_packets"> | |
1588 | Number of received packets. | |
1589 | </column> | |
1590 | <column name="statistics" key="rx_bytes"> | |
1591 | Number of received bytes. | |
1592 | </column> | |
1593 | <column name="statistics" key="tx_packets"> | |
1594 | Number of transmitted packets. | |
1595 | </column> | |
1596 | <column name="statistics" key="tx_bytes"> | |
1597 | Number of transmitted bytes. | |
1598 | </column> | |
1599 | </group> | |
1600 | <group title="Statistics: Receive errors"> | |
1601 | <column name="statistics" key="rx_dropped"> | |
1602 | Number of packets dropped by RX. | |
1603 | </column> | |
1604 | <column name="statistics" key="rx_frame_err"> | |
1605 | Number of frame alignment errors. | |
1606 | </column> | |
1607 | <column name="statistics" key="rx_over_err"> | |
1608 | Number of packets with RX overrun. | |
1609 | </column> | |
1610 | <column name="statistics" key="rx_crc_err"> | |
1611 | Number of CRC errors. | |
1612 | </column> | |
1613 | <column name="statistics" key="rx_errors"> | |
1614 | Total number of receive errors, greater than or equal to the sum of | |
1615 | the above. | |
1616 | </column> | |
9cc6bf75 | 1617 | </group> |
3fd8d445 BP |
1618 | <group title="Statistics: Transmit errors"> |
1619 | <column name="statistics" key="tx_dropped"> | |
1620 | Number of packets dropped by TX. | |
1621 | </column> | |
1622 | <column name="statistics" key="collisions"> | |
1623 | Number of collisions. | |
1624 | </column> | |
1625 | <column name="statistics" key="tx_errors"> | |
1626 | Total number of transmit errors, greater than or equal to the sum of | |
1627 | the above. | |
1628 | </column> | |
1629 | </group> | |
89365653 BP |
1630 | </group> |
1631 | ||
1632 | <group title="Ingress Policing"> | |
3f5d8c02 BP |
1633 | <p> |
1634 | These settings control ingress policing for packets received on this | |
1635 | interface. On a physical interface, this limits the rate at which | |
1636 | traffic is allowed into the system from the outside; on a virtual | |
1637 | interface (one connected to a virtual machine), this limits the rate at | |
1638 | which the VM is able to transmit. | |
1639 | </p> | |
1640 | <p> | |
1641 | Policing is a simple form of quality-of-service that simply drops | |
1642 | packets received in excess of the configured rate. Due to its | |
1643 | simplicity, policing is usually less accurate and less effective than | |
1644 | egress QoS (which is configured using the <ref table="QoS"/> and <ref | |
1645 | table="Queue"/> tables). | |
1646 | </p> | |
1647 | <p> | |
1648 | Policing is currently implemented only on Linux. The Linux | |
1649 | implementation uses a simple ``token bucket'' approach: | |
1650 | </p> | |
1651 | <ul> | |
1652 | <li> | |
1653 | The size of the bucket corresponds to <ref | |
1654 | column="ingress_policing_burst"/>. Initially the bucket is full. | |
1655 | </li> | |
1656 | <li> | |
1657 | Whenever a packet is received, its size (converted to tokens) is | |
1658 | compared to the number of tokens currently in the bucket. If the | |
1659 | required number of tokens are available, they are removed and the | |
1660 | packet is forwarded. Otherwise, the packet is dropped. | |
1661 | </li> | |
1662 | <li> | |
1663 | Whenever it is not full, the bucket is refilled with tokens at the | |
1664 | rate specified by <ref column="ingress_policing_rate"/>. | |
1665 | </li> | |
1666 | </ul> | |
1667 | <p> | |
1668 | Policing interacts badly with some network protocols, and especially | |
1669 | with fragmented IP packets. Suppose that there is enough network | |
1670 | activity to keep the bucket nearly empty all the time. Then this token | |
1671 | bucket algorithm will forward a single packet every so often, with the | |
1672 | period depending on packet size and on the configured rate. All of the | |
1673 | fragments of an IP packets are normally transmitted back-to-back, as a | |
1674 | group. In such a situation, therefore, only one of these fragments | |
1675 | will be forwarded and the rest will be dropped. IP does not provide | |
1676 | any way for the intended recipient to ask for only the remaining | |
1677 | fragments. In such a case there are two likely possibilities for what | |
1678 | will happen next: either all of the fragments will eventually be | |
1679 | retransmitted (as TCP will do), in which case the same problem will | |
1680 | recur, or the sender will not realize that its packet has been dropped | |
1681 | and data will simply be lost (as some UDP-based protocols will do). | |
1682 | Either way, it is possible that no forward progress will ever occur. | |
1683 | </p> | |
1684 | <column name="ingress_policing_rate"> | |
1685 | <p> | |
1686 | Maximum rate for data received on this interface, in kbps. Data | |
1687 | received faster than this rate is dropped. Set to <code>0</code> | |
1688 | (the default) to disable policing. | |
1689 | </p> | |
1690 | </column> | |
1691 | ||
89365653 BP |
1692 | <column name="ingress_policing_burst"> |
1693 | <p>Maximum burst size for data received on this interface, in kb. The | |
3fd8d445 BP |
1694 | default burst size if set to <code>0</code> is 1000 kb. This value |
1695 | has no effect if <ref column="ingress_policing_rate"/> | |
1696 | is <code>0</code>.</p> | |
3f5d8c02 BP |
1697 | <p> |
1698 | Specifying a larger burst size lets the algorithm be more forgiving, | |
1699 | which is important for protocols like TCP that react severely to | |
1700 | dropped packets. The burst size should be at least the size of the | |
1701 | interface's MTU. Specifying a value that is numerically at least as | |
1702 | large as 10% of <ref column="ingress_policing_rate"/> helps TCP come | |
1703 | closer to achieving the full rate. | |
1704 | </p> | |
89365653 BP |
1705 | </column> |
1706 | </group> | |
1707 | ||
93b8df38 EJ |
1708 | <group title="Connectivity Fault Management"> |
1709 | <p> | |
1710 | 802.1ag Connectivity Fault Management (CFM) allows a group of | |
1711 | Maintenance Points (MPs) called a Maintenance Association (MA) to | |
1712 | detect connectivity problems with each other. MPs within a MA should | |
1713 | have complete and exclusive interconnectivity. This is verified by | |
1714 | occasionally broadcasting Continuity Check Messages (CCMs) at a | |
1715 | configurable transmission interval. | |
1716 | </p> | |
1717 | ||
144216a3 EJ |
1718 | <p> |
1719 | According to the 802.1ag specification, each Maintenance Point should | |
1720 | be configured out-of-band with a list of Remote Maintenance Points it | |
1721 | should have connectivity to. Open vSwitch differs from the | |
1722 | specification in this area. It simply assumes the link is faulted if | |
1723 | no Remote Maintenance Points are reachable, and considers it not | |
1724 | faulted otherwise. | |
1725 | </p> | |
1726 | ||
b363bae4 EJ |
1727 | <p> |
1728 | When operating over tunnels which have no <code>in_key</code>, or an | |
1729 | <code>in_key</code> of <code>flow</code>. CFM will only accept CCMs | |
1730 | with a tunnel key of zero. | |
1731 | </p> | |
1732 | ||
93b8df38 EJ |
1733 | <column name="cfm_mpid"> |
1734 | A Maintenance Point ID (MPID) uniquely identifies each endpoint within | |
1735 | a Maintenance Association. The MPID is used to identify this endpoint | |
1736 | to other Maintenance Points in the MA. Each end of a link being | |
1737 | monitored should have a different MPID. Must be configured to enable | |
1738 | CFM on this <ref table="Interface"/>. | |
1739 | </column> | |
b31bcf60 | 1740 | |
93b8df38 | 1741 | <column name="cfm_fault"> |
144216a3 EJ |
1742 | <p> |
1743 | Indicates a connectivity fault triggered by an inability to receive | |
1744 | heartbeats from any remote endpoint. When a fault is triggered on | |
1745 | <ref table="Interface"/>s participating in bonds, they will be | |
1746 | disabled. | |
1747 | </p> | |
1748 | <p> | |
1749 | Faults can be triggered for several reasons. Most importantly they | |
1750 | are triggered when no CCMs are received for a period of 3.5 times the | |
1751 | transmission interval. Faults are also triggered when any CCMs | |
1752 | indicate that a Remote Maintenance Point is not receiving CCMs but | |
1753 | able to send them. Finally, a fault is triggered if a CCM is | |
1754 | received which indicates unexpected configuration. Notably, this | |
1755 | case arises when a CCM is received which advertises the local MPID. | |
1756 | </p> | |
93b8df38 | 1757 | </column> |
a5faa982 | 1758 | |
b9380396 EJ |
1759 | <column name="cfm_fault_status" key="recv"> |
1760 | Indicates a CFM fault was triggered due to a lack of CCMs received on | |
1761 | the <ref table="Interface"/>. | |
1762 | </column> | |
1763 | ||
1764 | <column name="cfm_fault_status" key="rdi"> | |
1765 | Indicates a CFM fault was triggered due to the reception of a CCM with | |
1766 | the RDI bit flagged. Endpoints set the RDI bit in their CCMs when they | |
1767 | are not receiving CCMs themselves. This typically indicates a | |
1768 | unidirectional connectivity failure. | |
1769 | </column> | |
1770 | ||
1771 | <column name="cfm_fault_status" key="maid"> | |
1772 | Indicates a CFM fault was triggered due to the reception of a CCM with | |
1773 | a MAID other than the one Open vSwitch uses. CFM broadcasts are tagged | |
1774 | with an identification number in addition to the MPID called the MAID. | |
1775 | Open vSwitch only supports receiving CCM broadcasts tagged with the | |
1776 | MAID it uses internally. | |
1777 | </column> | |
1778 | ||
1779 | <column name="cfm_fault_status" key="loopback"> | |
1780 | Indicates a CFM fault was triggered due to the reception of a CCM | |
1781 | advertising the same MPID configured in the <ref column="cfm_mpid"/> | |
1782 | column of this <ref table="Interface"/>. This may indicate a loop in | |
1783 | the network. | |
1784 | </column> | |
1785 | ||
1786 | <column name="cfm_fault_status" key="overflow"> | |
1787 | Indicates a CFM fault was triggered because the CFM module received | |
1788 | CCMs from more remote endpoints than it can keep track of. | |
1789 | </column> | |
1790 | ||
1791 | <column name="cfm_fault_status" key="override"> | |
1792 | Indicates a CFM fault was manually triggered by an administrator using | |
1793 | an <code>ovs-appctl</code> command. | |
1794 | </column> | |
1795 | ||
2b540ecb MM |
1796 | <column name="cfm_fault_status" key="interval"> |
1797 | Indicates a CFM fault was triggered due to the reception of a CCM | |
1798 | frame having an invalid interval. | |
1799 | </column> | |
1800 | ||
1c0333b6 EJ |
1801 | <column name="cfm_remote_opstate"> |
1802 | <p>When in extended mode, indicates the operational state of the | |
1803 | remote endpoint as either <code>up</code> or <code>down</code>. See | |
1804 | <ref column="other_config" key="cfm_opstate"/>. | |
1805 | </p> | |
1806 | </column> | |
1807 | ||
3967a833 MM |
1808 | <column name="cfm_health"> |
1809 | <p> | |
1810 | Indicates the health of the interface as a percentage of CCM frames | |
1811 | received over 21 <ref column="other_config" key="cfm_interval"/>s. | |
1812 | The health of an interface is undefined if it is communicating with | |
1813 | more than one <ref column="cfm_remote_mpids"/>. It reduces if | |
1814 | healthy heartbeats are not received at the expected rate, and | |
1815 | gradually improves as healthy heartbeats are received at the desired | |
1816 | rate. Every 21 <ref column="other_config" key="cfm_interval"/>s, the | |
1817 | health of the interface is refreshed. | |
1818 | </p> | |
1819 | <p> | |
1820 | As mentioned above, the faults can be triggered for several reasons. | |
1821 | The link health will deteriorate even if heartbeats are received but | |
1822 | they are reported to be unhealthy. An unhealthy heartbeat in this | |
1823 | context is a heartbeat for which either some fault is set or is out | |
1824 | of sequence. The interface health can be 100 only on receiving | |
1825 | healthy heartbeats at the desired rate. | |
1826 | </p> | |
1827 | </column> | |
1828 | ||
a5faa982 EJ |
1829 | <column name="cfm_remote_mpids"> |
1830 | When CFM is properly configured, Open vSwitch will occasionally | |
1831 | receive CCM broadcasts. These broadcasts contain the MPID of the | |
1832 | sending Maintenance Point. The list of MPIDs from which this | |
1833 | <ref table="Interface"/> is receiving broadcasts from is regularly | |
1834 | collected and written to this column. | |
1835 | </column> | |
3fd8d445 | 1836 | |
f9e5e5b3 BP |
1837 | <column name="other_config" key="cfm_interval" |
1838 | type='{"type": "integer"}'> | |
612ca9c5 BP |
1839 | <p> |
1840 | The interval, in milliseconds, between transmissions of CFM | |
1841 | heartbeats. Three missed heartbeat receptions indicate a | |
1842 | connectivity fault. | |
1843 | </p> | |
1844 | ||
1845 | <p> | |
1846 | In standard operation only intervals of 3, 10, 100, 1,000, 10,000, | |
1847 | 60,000, or 600,000 ms are supported. Other values will be rounded | |
1848 | down to the nearest value on the list. Extended mode (see <ref | |
1849 | column="other_config" key="cfm_extended"/>) supports any interval up | |
1850 | to 65,535 ms. In either mode, the default is 1000 ms. | |
1851 | </p> | |
1852 | ||
1853 | <p>We do not recommend using intervals less than 100 ms.</p> | |
3fd8d445 BP |
1854 | </column> |
1855 | ||
f9e5e5b3 BP |
1856 | <column name="other_config" key="cfm_extended" |
1857 | type='{"type": "boolean"}'> | |
3fd8d445 BP |
1858 | When <code>true</code>, the CFM module operates in extended mode. This |
1859 | causes it to use a nonstandard destination address to avoid conflicting | |
1860 | with compliant implementations which may be running concurrently on the | |
1861 | network. Furthermore, extended mode increases the accuracy of the | |
1862 | <code>cfm_interval</code> configuration parameter by breaking wire | |
1863 | compatibility with 802.1ag compliant implementations. Defaults to | |
167e393b | 1864 | <code>false</code>. |
3fd8d445 | 1865 | </column> |
dae57238 BP |
1866 | <column name="other_config" key="cfm_opstate" |
1867 | type='{"type": "string", "enum": ["set", ["down", "up"]]}'> | |
86dc6501 EJ |
1868 | When <code>down</code>, the CFM module marks all CCMs it generates as |
1869 | operationally down without triggering a fault. This allows remote | |
1870 | maintenance points to choose not to forward traffic to the | |
1871 | <ref table="Interface"/> on which this CFM module is running. | |
1872 | Currently, in Open vSwitch, the opdown bit of CCMs affects | |
1873 | <ref table="Interface"/>s participating in bonds, and the bundle | |
1874 | OpenFlow action. This setting is ignored when CFM is not in extended | |
1875 | mode. Defaults to <code>up</code>. | |
1876 | </column> | |
75a4ead1 EJ |
1877 | |
1878 | <column name="other_config" key="cfm_ccm_vlan" | |
1879 | type='{"type": "integer", "minInteger": 1, "maxInteger": 4095}'> | |
1880 | When set, the CFM module will apply a VLAN tag to all CCMs it generates | |
189cb9e4 EJ |
1881 | with the given value. May be the string <code>random</code> in which |
1882 | case each CCM will be tagged with a different randomly generated VLAN. | |
75a4ead1 EJ |
1883 | </column> |
1884 | ||
a7aa2d3c EJ |
1885 | <column name="other_config" key="cfm_ccm_pcp" |
1886 | type='{"type": "integer", "minInteger": 1, "maxInteger": 7}'> | |
1887 | When set, the CFM module will apply a VLAN tag to all CCMs it generates | |
b363bae4 | 1888 | with the given PCP value, the VLAN ID of the tag is governed by the |
a7aa2d3c EJ |
1889 | value of <ref column="other_config" key="cfm_ccm_vlan"/>. If |
1890 | <ref column="other_config" key="cfm_ccm_vlan"/> is unset, a VLAN ID of | |
1891 | zero is used. | |
1892 | </column> | |
1893 | ||
93b8df38 EJ |
1894 | </group> |
1895 | ||
3fd8d445 | 1896 | <group title="Bonding Configuration"> |
f9e5e5b3 BP |
1897 | <column name="other_config" key="lacp-port-id" |
1898 | type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'> | |
3fd8d445 BP |
1899 | The LACP port ID of this <ref table="Interface"/>. Port IDs are |
1900 | used in LACP negotiations to identify individual ports | |
f9e5e5b3 | 1901 | participating in a bond. |
a8172aa3 EJ |
1902 | </column> |
1903 | ||
f9e5e5b3 BP |
1904 | <column name="other_config" key="lacp-port-priority" |
1905 | type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'> | |
3fd8d445 BP |
1906 | The LACP port priority of this <ref table="Interface"/>. In LACP |
1907 | negotiations <ref table="Interface"/>s with numerically lower | |
f9e5e5b3 | 1908 | priorities are preferred for aggregation. |
89365653 | 1909 | </column> |
018f1525 | 1910 | |
f9e5e5b3 BP |
1911 | <column name="other_config" key="lacp-aggregation-key" |
1912 | type='{"type": "integer", "minInteger": 1, "maxInteger": 65535}'> | |
3fd8d445 BP |
1913 | The LACP aggregation key of this <ref table="Interface"/>. <ref |
1914 | table="Interface"/>s with different aggregation keys may not be active | |
f9e5e5b3 | 1915 | within a given <ref table="Port"/> at the same time. |
a3acf0b0 | 1916 | </column> |
3fd8d445 | 1917 | </group> |
a3acf0b0 | 1918 | |
3fd8d445 BP |
1919 | <group title="Virtual Machine Identifiers"> |
1920 | <p> | |
1921 | These key-value pairs specifically apply to an interface that | |
1922 | represents a virtual Ethernet interface connected to a virtual | |
1923 | machine. These key-value pairs should not be present for other types | |
1924 | of interfaces. Keys whose names end in <code>-uuid</code> have | |
1925 | values that uniquely identify the entity in question. For a Citrix | |
1926 | XenServer hypervisor, these values are UUIDs in RFC 4122 format. | |
1927 | Other hypervisors may use other formats. | |
1928 | </p> | |
1929 | ||
1930 | <column name="external_ids" key="attached-mac"> | |
1931 | The MAC address programmed into the ``virtual hardware'' for this | |
1932 | interface, in the form | |
1933 | <var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>:<var>xx</var>. | |
1934 | For Citrix XenServer, this is the value of the <code>MAC</code> field | |
1935 | in the VIF record for this interface. | |
1936 | </column> | |
1937 | ||
1938 | <column name="external_ids" key="iface-id"> | |
1939 | A system-unique identifier for the interface. On XenServer, this will | |
1940 | commonly be the same as <ref column="external_ids" key="xs-vif-uuid"/>. | |
1941 | </column> | |
1942 | ||
cf9deac5 BP |
1943 | <column name="external_ids" key="iface-status" |
1944 | type='{"type": "string", | |
1945 | "enum": ["set", ["active", "inactive"]]}'> | |
1946 | <p> | |
1947 | Hypervisors may sometimes have more than one interface associated | |
1948 | with a given <ref column="external_ids" key="iface-id"/>, only one of | |
1949 | which is actually in use at a given time. For example, in some | |
1950 | circumstances XenServer has both a ``tap'' and a ``vif'' interface | |
1951 | for a single <ref column="external_ids" key="iface-id"/>, but only | |
1952 | uses one of them at a time. A hypervisor that behaves this way must | |
1953 | mark the currently in use interface <code>active</code> and the | |
1954 | others <code>inactive</code>. A hypervisor that never has more than | |
1955 | one interface for a given <ref column="external_ids" key="iface-id"/> | |
1956 | may mark that interface <code>active</code> or omit <ref | |
1957 | column="external_ids" key="iface-status"/> entirely. | |
1958 | </p> | |
1959 | ||
1960 | <p> | |
1961 | During VM migration, a given <ref column="external_ids" | |
1962 | key="iface-id"/> might transiently be marked <code>active</code> on | |
1963 | two different hypervisors. That is, <code>active</code> means that | |
1964 | this <ref column="external_ids" key="iface-id"/> is the active | |
1965 | instance within a single hypervisor, not in a broader scope. | |
1966 | </p> | |
1967 | </column> | |
1968 | ||
3fd8d445 BP |
1969 | <column name="external_ids" key="xs-vif-uuid"> |
1970 | The virtual interface associated with this interface. | |
1971 | </column> | |
1972 | ||
1973 | <column name="external_ids" key="xs-network-uuid"> | |
1974 | The virtual network to which this interface is attached. | |
1975 | </column> | |
1976 | ||
c473936b GS |
1977 | <column name="external_ids" key="vm-id"> |
1978 | The VM to which this interface belongs. On XenServer, this will be the | |
1979 | same as <ref column="external_ids" key="xs-vm-uuid"/>. | |
1980 | </column> | |
1981 | ||
3fd8d445 BP |
1982 | <column name="external_ids" key="xs-vm-uuid"> |
1983 | The VM to which this interface belongs. | |
018f1525 | 1984 | </column> |
89365653 | 1985 | </group> |
3fd8d445 | 1986 | |
52a90c29 BP |
1987 | <group title="VLAN Splinters"> |
1988 | <p> | |
1989 | The ``VLAN splinters'' feature increases Open vSwitch compatibility | |
1990 | with buggy network drivers in old versions of Linux that do not | |
1991 | properly support VLANs when VLAN devices are not used, at some cost | |
1992 | in memory and performance. | |
1993 | </p> | |
1994 | ||
1995 | <p> | |
1996 | When VLAN splinters are enabled on a particular interface, Open vSwitch | |
1997 | creates a VLAN device for each in-use VLAN. For sending traffic tagged | |
1998 | with a VLAN on the interface, it substitutes the VLAN device. Traffic | |
1999 | received on the VLAN device is treated as if it had been received on | |
2000 | the interface on the particular VLAN. | |
2001 | </p> | |
2002 | ||
2003 | <p> | |
2004 | VLAN splinters consider a VLAN to be in use if: | |
2005 | </p> | |
2006 | ||
2007 | <ul> | |
45c580a3 BP |
2008 | <li> |
2009 | The VLAN is the <ref table="Port" column="tag"/> value in any <ref | |
2010 | table="Port"/> record. | |
2011 | </li> | |
2012 | ||
52a90c29 BP |
2013 | <li> |
2014 | The VLAN is listed within the <ref table="Port" column="trunks"/> | |
2015 | column of the <ref table="Port"/> record of an interface on which | |
2016 | VLAN splinters are enabled. | |
2017 | ||
2018 | An empty <ref table="Port" column="trunks"/> does not influence the | |
2019 | in-use VLANs: creating 4,096 VLAN devices is impractical because it | |
2020 | will exceed the current 1,024 port per datapath limit. | |
2021 | </li> | |
2022 | ||
2023 | <li> | |
2024 | An OpenFlow flow within any bridge matches the VLAN. | |
2025 | </li> | |
2026 | </ul> | |
2027 | ||
2028 | <p> | |
2029 | The same set of in-use VLANs applies to every interface on which VLAN | |
2030 | splinters are enabled. That is, the set is not chosen separately for | |
2031 | each interface but selected once as the union of all in-use VLANs based | |
2032 | on the rules above. | |
2033 | </p> | |
2034 | ||
2035 | <p> | |
2036 | It does not make sense to enable VLAN splinters on an interface for an | |
2037 | access port, or on an interface that is not a physical port. | |
2038 | </p> | |
2039 | ||
2040 | <p> | |
2041 | VLAN splinters are deprecated. When broken device drivers are no | |
2042 | longer in widespread use, we will delete this feature. | |
2043 | </p> | |
2044 | ||
2045 | <column name="other_config" key="enable-vlan-splinters" | |
2046 | type='{"type": "boolean"}'> | |
2047 | <p> | |
2048 | Set to <code>true</code> to enable VLAN splinters on this interface. | |
2049 | Defaults to <code>false</code>. | |
2050 | </p> | |
2051 | ||
2052 | <p> | |
2053 | VLAN splinters increase kernel and userspace memory overhead, so do | |
2054 | not use them unless they are needed. | |
2055 | </p> | |
7be6d701 BP |
2056 | |
2057 | <p> | |
2058 | VLAN splinters do not support 802.1p priority tags. Received | |
2059 | priorities will appear to be 0, regardless of their actual values, | |
2060 | and priorities on transmitted packets will also be cleared to 0. | |
2061 | </p> | |
52a90c29 BP |
2062 | </column> |
2063 | </group> | |
2064 | ||
3fd8d445 BP |
2065 | <group title="Common Columns"> |
2066 | The overall purpose of these columns is described under <code>Common | |
2067 | Columns</code> at the beginning of this document. | |
2068 | ||
2069 | <column name="other_config"/> | |
2070 | <column name="external_ids"/> | |
2071 | </group> | |
89365653 BP |
2072 | </table> |
2073 | ||
254750ce BP |
2074 | <table name="Flow_Table" title="OpenFlow table configuration"> |
2075 | <p>Configuration for a particular OpenFlow table.</p> | |
2076 | ||
2077 | <column name="name"> | |
2078 | The table's name. Set this column to change the name that controllers | |
2079 | will receive when they request table statistics, e.g. <code>ovs-ofctl | |
2080 | dump-tables</code>. The name does not affect switch behavior. | |
2081 | </column> | |
2082 | ||
2083 | <column name="flow_limit"> | |
2084 | If set, limits the number of flows that may be added to the table. Open | |
2085 | vSwitch may limit the number of flows in a table for other reasons, | |
2086 | e.g. due to hardware limitations or for resource availability or | |
2087 | performance reasons. | |
2088 | </column> | |
2089 | ||
2090 | <column name="overflow_policy"> | |
2091 | <p> | |
2092 | Controls the switch's behavior when an OpenFlow flow table modification | |
2093 | request would add flows in excess of <ref column="flow_limit"/>. The | |
2094 | supported values are: | |
2095 | </p> | |
2096 | ||
2097 | <dl> | |
2098 | <dt><code>refuse</code></dt> | |
2099 | <dd> | |
2100 | Refuse to add the flow or flows. This is also the default policy | |
2101 | when <ref column="overflow_policy"/> is unset. | |
2102 | </dd> | |
2103 | ||
2104 | <dt><code>evict</code></dt> | |
2105 | <dd> | |
2106 | Delete the flow that will expire soonest. See <ref column="groups"/> | |
2107 | for details. | |
2108 | </dd> | |
2109 | </dl> | |
2110 | </column> | |
2111 | ||
2112 | <column name="groups"> | |
2113 | <p> | |
2114 | When <ref column="overflow_policy"/> is <code>evict</code>, this | |
2115 | controls how flows are chosen for eviction when the flow table would | |
2116 | otherwise exceed <ref column="flow_limit"/> flows. Its value is a set | |
2117 | of NXM fields or sub-fields, each of which takes one of the forms | |
2118 | <code><var>field</var>[]</code> or | |
2119 | <code><var>field</var>[<var>start</var>..<var>end</var>]</code>, | |
2120 | e.g. <code>NXM_OF_IN_PORT[]</code>. Please see | |
2121 | <code>nicira-ext.h</code> for a complete list of NXM field names. | |
2122 | </p> | |
2123 | ||
2124 | <p> | |
2125 | When a flow must be evicted due to overflow, the flow to evict is | |
2126 | chosen through an approximation of the following algorithm: | |
2127 | </p> | |
2128 | ||
2129 | <ol> | |
2130 | <li> | |
2131 | Divide the flows in the table into groups based on the values of the | |
2132 | specified fields or subfields, so that all of the flows in a given | |
2133 | group have the same values for those fields. If a flow does not | |
2134 | specify a given field, that field's value is treated as 0. | |
2135 | </li> | |
2136 | ||
2137 | <li> | |
2138 | Consider the flows in the largest group, that is, the group that | |
2139 | contains the greatest number of flows. If two or more groups all | |
2140 | have the same largest number of flows, consider the flows in all of | |
2141 | those groups. | |
2142 | </li> | |
2143 | ||
2144 | <li> | |
2145 | Among the flows under consideration, choose the flow that expires | |
2146 | soonest for eviction. | |
2147 | </li> | |
2148 | </ol> | |
2149 | ||
2150 | <p> | |
2151 | The eviction process only considers flows that have an idle timeout or | |
2152 | a hard timeout. That is, eviction never deletes permanent flows. | |
7792bfe0 | 2153 | (Permanent flows do count against <ref column="flow_limit"/>.) |
254750ce BP |
2154 | </p> |
2155 | ||
2156 | <p> | |
2157 | Open vSwitch ignores any invalid or unknown field specifications. | |
2158 | </p> | |
2159 | ||
2160 | <p> | |
2161 | When <ref column="overflow_policy"/> is not <code>evict</code>, this | |
2162 | column has no effect. | |
2163 | </p> | |
2164 | </column> | |
2165 | </table> | |
2166 | ||
c1c9c9c4 BP |
2167 | <table name="QoS" title="Quality of Service configuration"> |
2168 | <p>Quality of Service (QoS) configuration for each Port that | |
3fd8d445 | 2169 | references it.</p> |
c1c9c9c4 BP |
2170 | |
2171 | <column name="type"> | |
b850dc6d BP |
2172 | <p>The type of QoS to implement. The currently defined types are |
2173 | listed below:</p> | |
c1c9c9c4 BP |
2174 | <dl> |
2175 | <dt><code>linux-htb</code></dt> | |
6784cb57 BP |
2176 | <dd> |
2177 | Linux ``hierarchy token bucket'' classifier. See tc-htb(8) (also at | |
2178 | <code>http://linux.die.net/man/8/tc-htb</code>) and the HTB manual | |
2179 | (<code>http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm</code>) | |
2180 | for information on how this classifier works and how to configure it. | |
2181 | </dd> | |
c1c9c9c4 | 2182 | </dl> |
a339aa81 EJ |
2183 | <dl> |
2184 | <dt><code>linux-hfsc</code></dt> | |
2185 | <dd> | |
2186 | Linux "Hierarchical Fair Service Curve" classifier. | |
2187 | See <code>http://linux-ip.net/articles/hfsc.en/</code> for | |
2188 | information on how this classifier works. | |
2189 | </dd> | |
2190 | </dl> | |
c1c9c9c4 BP |
2191 | </column> |
2192 | ||
2193 | <column name="queues"> | |
2194 | <p>A map from queue numbers to <ref table="Queue"/> records. The | |
3fd8d445 BP |
2195 | supported range of queue numbers depend on <ref column="type"/>. The |
2196 | queue numbers are the same as the <code>queue_id</code> used in | |
2197 | OpenFlow in <code>struct ofp_action_enqueue</code> and other | |
2c999774 BP |
2198 | structures.</p> |
2199 | ||
2200 | <p> | |
2201 | Queue 0 is the ``default queue.'' It is used by OpenFlow output | |
8bddb894 BP |
2202 | actions when no specific queue has been set. When no configuration for |
2203 | queue 0 is present, it is automatically configured as if a <ref | |
2204 | table="Queue"/> record with empty <ref table="Queue" column="dscp"/> | |
2205 | and <ref table="Queue" column="other_config"/> columns had been | |
2206 | specified. | |
2c999774 BP |
2207 | (Before version 1.6, Open vSwitch would leave queue 0 unconfigured in |
2208 | this case. With some queuing disciplines, this dropped all packets | |
2209 | destined for the default queue.) | |
2210 | </p> | |
c1c9c9c4 BP |
2211 | </column> |
2212 | ||
3fd8d445 BP |
2213 | <group title="Configuration for linux-htb and linux-hfsc"> |
2214 | <p> | |
2215 | The <code>linux-htb</code> and <code>linux-hfsc</code> classes support | |
2216 | the following key-value pair: | |
2217 | </p> | |
9cc6bf75 | 2218 | |
f9e5e5b3 | 2219 | <column name="other_config" key="max-rate" type='{"type": "integer"}'> |
3fd8d445 BP |
2220 | Maximum rate shared by all queued traffic, in bit/s. Optional. If not |
2221 | specified, for physical interfaces, the default is the link rate. For | |
2222 | other interfaces or if the link rate cannot be determined, the default | |
2223 | is currently 100 Mbps. | |
2224 | </column> | |
2225 | </group> | |
13008eb3 | 2226 | |
3fd8d445 BP |
2227 | <group title="Common Columns"> |
2228 | The overall purpose of these columns is described under <code>Common | |
2229 | Columns</code> at the beginning of this document. | |
2230 | ||
2231 | <column name="other_config"/> | |
2232 | <column name="external_ids"/> | |
2233 | </group> | |
c1c9c9c4 BP |
2234 | </table> |
2235 | ||
2236 | <table name="Queue" title="QoS output queue."> | |
2237 | <p>A configuration for a port output queue, used in configuring Quality of | |
3fd8d445 BP |
2238 | Service (QoS) features. May be referenced by <ref column="queues" |
2239 | table="QoS"/> column in <ref table="QoS"/> table.</p> | |
13008eb3 | 2240 | |
8b36f51e EJ |
2241 | <column name="dscp"> |
2242 | If set, Open vSwitch will mark all traffic egressing this | |
2243 | <ref table="Queue"/> with the given DSCP bits. Traffic egressing the | |
2244 | default <ref table="Queue"/> is only marked if it was explicitly selected | |
2245 | as the <ref table="Queue"/> at the time the packet was output. If unset, | |
2246 | the DSCP bits of traffic egressing this <ref table="Queue"/> will remain | |
2247 | unchanged. | |
2248 | </column> | |
2249 | ||
3fd8d445 BP |
2250 | <group title="Configuration for linux-htb QoS"> |
2251 | <p> | |
69822b3c EJ |
2252 | <ref table="QoS"/> <ref table="QoS" column="type"/> |
2253 | <code>linux-htb</code> may use <code>queue_id</code>s less than 61440. | |
2254 | It has the following key-value pairs defined. | |
3fd8d445 | 2255 | </p> |
9cc6bf75 | 2256 | |
f9e5e5b3 BP |
2257 | <column name="other_config" key="min-rate" |
2258 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
2259 | Minimum guaranteed bandwidth, in bit/s. |
2260 | </column> | |
2261 | ||
f9e5e5b3 BP |
2262 | <column name="other_config" key="max-rate" |
2263 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
2264 | Maximum allowed bandwidth, in bit/s. Optional. If specified, the |
2265 | queue's rate will not be allowed to exceed the specified value, even | |
2266 | if excess bandwidth is available. If unspecified, defaults to no | |
2267 | limit. | |
2268 | </column> | |
2269 | ||
f9e5e5b3 BP |
2270 | <column name="other_config" key="burst" |
2271 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
2272 | Burst size, in bits. This is the maximum amount of ``credits'' that a |
2273 | queue can accumulate while it is idle. Optional. Details of the | |
2274 | <code>linux-htb</code> implementation require a minimum burst size, so | |
2275 | a too-small <code>burst</code> will be silently ignored. | |
2276 | </column> | |
2277 | ||
f9e5e5b3 BP |
2278 | <column name="other_config" key="priority" |
2279 | type='{"type": "integer", "minInteger": 0, "maxInteger": 4294967295}'> | |
2280 | A queue with a smaller <code>priority</code> will receive all the | |
2281 | excess bandwidth that it can use before a queue with a larger value | |
2282 | receives any. Specific priority values are unimportant; only relative | |
2283 | ordering matters. Defaults to 0 if unspecified. | |
3fd8d445 BP |
2284 | </column> |
2285 | </group> | |
2286 | ||
2287 | <group title="Configuration for linux-hfsc QoS"> | |
2288 | <p> | |
69822b3c EJ |
2289 | <ref table="QoS"/> <ref table="QoS" column="type"/> |
2290 | <code>linux-hfsc</code> may use <code>queue_id</code>s less than 61440. | |
2291 | It has the following key-value pairs defined. | |
3fd8d445 | 2292 | </p> |
9cc6bf75 | 2293 | |
f9e5e5b3 BP |
2294 | <column name="other_config" key="min-rate" |
2295 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
2296 | Minimum guaranteed bandwidth, in bit/s. |
2297 | </column> | |
9cc6bf75 | 2298 | |
f9e5e5b3 BP |
2299 | <column name="other_config" key="max-rate" |
2300 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
2301 | Maximum allowed bandwidth, in bit/s. Optional. If specified, the |
2302 | queue's rate will not be allowed to exceed the specified value, even if | |
2303 | excess bandwidth is available. If unspecified, defaults to no | |
2304 | limit. | |
2305 | </column> | |
2306 | </group> | |
2307 | ||
2308 | <group title="Common Columns"> | |
2309 | The overall purpose of these columns is described under <code>Common | |
2310 | Columns</code> at the beginning of this document. | |
2311 | ||
2312 | <column name="other_config"/> | |
2313 | <column name="external_ids"/> | |
2314 | </group> | |
c1c9c9c4 BP |
2315 | </table> |
2316 | ||
9ae7ddc0 | 2317 | <table name="Mirror" title="Port mirroring."> |
89365653 BP |
2318 | <p>A port mirror within a <ref table="Bridge"/>.</p> |
2319 | <p>A port mirror configures a bridge to send selected frames to special | |
92ada132 | 2320 | ``mirrored'' ports, in addition to their normal destinations. Mirroring |
9ae7ddc0 | 2321 | traffic may also be referred to as SPAN or RSPAN, depending on how |
92ada132 | 2322 | the mirrored traffic is sent.</p> |
89365653 BP |
2323 | |
2324 | <column name="name"> | |
2325 | Arbitrary identifier for the <ref table="Mirror"/>. | |
2326 | </column> | |
2327 | ||
2328 | <group title="Selecting Packets for Mirroring"> | |
3e519d8e BP |
2329 | <p> |
2330 | To be selected for mirroring, a given packet must enter or leave the | |
2331 | bridge through a selected port and it must also be in one of the | |
2332 | selected VLANs. | |
2333 | </p> | |
2334 | ||
939ff267 BP |
2335 | <column name="select_all"> |
2336 | If true, every packet arriving or departing on any port is | |
2337 | selected for mirroring. | |
2338 | </column> | |
2339 | ||
89365653 BP |
2340 | <column name="select_dst_port"> |
2341 | Ports on which departing packets are selected for mirroring. | |
2342 | </column> | |
2343 | ||
2344 | <column name="select_src_port"> | |
939ff267 | 2345 | Ports on which arriving packets are selected for mirroring. |
89365653 BP |
2346 | </column> |
2347 | ||
2348 | <column name="select_vlan"> | |
2349 | VLANs on which packets are selected for mirroring. An empty set | |
2350 | selects packets on all VLANs. | |
2351 | </column> | |
2352 | </group> | |
2353 | ||
2354 | <group title="Mirroring Destination Configuration"> | |
3e519d8e BP |
2355 | <p> |
2356 | These columns are mutually exclusive. Exactly one of them must be | |
2357 | nonempty. | |
2358 | </p> | |
2359 | ||
89365653 | 2360 | <column name="output_port"> |
3e519d8e | 2361 | <p>Output port for selected packets, if nonempty.</p> |
89365653 | 2362 | <p>Specifying a port for mirror output reserves that port exclusively |
92ada132 | 2363 | for mirroring. No frames other than those selected for mirroring |
653fe3a3 | 2364 | via this column |
92ada132 BP |
2365 | will be forwarded to the port, and any frames received on the port |
2366 | will be discarded.</p> | |
2367 | <p> | |
2368 | The output port may be any kind of port supported by Open vSwitch. | |
9ae7ddc0 JP |
2369 | It may be, for example, a physical port (sometimes called SPAN) or a |
2370 | GRE tunnel. | |
92ada132 | 2371 | </p> |
89365653 BP |
2372 | </column> |
2373 | ||
2374 | <column name="output_vlan"> | |
3e519d8e | 2375 | <p>Output VLAN for selected packets, if nonempty.</p> |
89365653 | 2376 | <p>The frames will be sent out all ports that trunk |
3fd8d445 BP |
2377 | <ref column="output_vlan"/>, as well as any ports with implicit VLAN |
2378 | <ref column="output_vlan"/>. When a mirrored frame is sent out a | |
2379 | trunk port, the frame's VLAN tag will be set to | |
2380 | <ref column="output_vlan"/>, replacing any existing tag; when it is | |
2381 | sent out an implicit VLAN port, the frame will not be tagged. This | |
2382 | type of mirroring is sometimes called RSPAN.</p> | |
07817dfe | 2383 | <p> |
05be4e2c EJ |
2384 | See the documentation for |
2385 | <ref column="other_config" key="forward-bpdu"/> in the | |
2386 | <ref table="Interface"/> table for a list of destination MAC | |
2387 | addresses which will not be mirrored to a VLAN to avoid confusing | |
2388 | switches that interpret the protocols that they represent. | |
07817dfe | 2389 | </p> |
89365653 | 2390 | <p><em>Please note:</em> Mirroring to a VLAN can disrupt a network that |
3fd8d445 BP |
2391 | contains unmanaged switches. Consider an unmanaged physical switch |
2392 | with two ports: port 1, connected to an end host, and port 2, | |
2393 | connected to an Open vSwitch configured to mirror received packets | |
2394 | into VLAN 123 on port 2. Suppose that the end host sends a packet on | |
2395 | port 1 that the physical switch forwards to port 2. The Open vSwitch | |
2396 | forwards this packet to its destination and then reflects it back on | |
2397 | port 2 in VLAN 123. This reflected packet causes the unmanaged | |
2398 | physical switch to replace the MAC learning table entry, which | |
2399 | correctly pointed to port 1, with one that incorrectly points to port | |
2400 | 2. Afterward, the physical switch will direct packets destined for | |
2401 | the end host to the Open vSwitch on port 2, instead of to the end | |
2402 | host on port 1, disrupting connectivity. If mirroring to a VLAN is | |
2403 | desired in this scenario, then the physical switch must be replaced | |
2404 | by one that learns Ethernet addresses on a per-VLAN basis. In | |
2405 | addition, learning should be disabled on the VLAN containing mirrored | |
2406 | traffic. If this is not done then intermediate switches will learn | |
2407 | the MAC address of each end host from the mirrored traffic. If | |
2408 | packets being sent to that end host are also mirrored, then they will | |
2409 | be dropped since the switch will attempt to send them out the input | |
2410 | port. Disabling learning for the VLAN will cause the switch to | |
2411 | correctly send the packet out all ports configured for that VLAN. If | |
2412 | Open vSwitch is being used as an intermediate switch, learning can be | |
2413 | disabled by adding the mirrored VLAN to <ref column="flood_vlans"/> | |
2414 | in the appropriate <ref table="Bridge"/> table or tables.</p> | |
2415 | <p> | |
2416 | Mirroring to a GRE tunnel has fewer caveats than mirroring to a | |
2417 | VLAN and should generally be preferred. | |
2418 | </p> | |
89365653 BP |
2419 | </column> |
2420 | </group> | |
13008eb3 | 2421 | |
9d24de3b JP |
2422 | <group title="Statistics: Mirror counters"> |
2423 | <p> | |
2424 | Key-value pairs that report mirror statistics. | |
2425 | </p> | |
2426 | <column name="statistics" key="tx_packets"> | |
2427 | Number of packets transmitted through this mirror. | |
2428 | </column> | |
2429 | <column name="statistics" key="tx_bytes"> | |
2430 | Number of bytes transmitted through this mirror. | |
2431 | </column> | |
2432 | </group> | |
2433 | ||
3fd8d445 BP |
2434 | <group title="Common Columns"> |
2435 | The overall purpose of these columns is described under <code>Common | |
2436 | Columns</code> at the beginning of this document. | |
2437 | ||
2438 | <column name="external_ids"/> | |
13008eb3 | 2439 | </group> |
89365653 BP |
2440 | </table> |
2441 | ||
2442 | <table name="Controller" title="OpenFlow controller configuration."> | |
76ce9432 BP |
2443 | <p>An OpenFlow controller.</p> |
2444 | ||
7d674866 BP |
2445 | <p> |
2446 | Open vSwitch supports two kinds of OpenFlow controllers: | |
2447 | </p> | |
299a244b | 2448 | |
7d674866 BP |
2449 | <dl> |
2450 | <dt>Primary controllers</dt> | |
2451 | <dd> | |
2452 | <p> | |
2453 | This is the kind of controller envisioned by the OpenFlow 1.0 | |
2454 | specification. Usually, a primary controller implements a network | |
2455 | policy by taking charge of the switch's flow table. | |
2456 | </p> | |
2457 | ||
2458 | <p> | |
2459 | Open vSwitch initiates and maintains persistent connections to | |
2460 | primary controllers, retrying the connection each time it fails or | |
2461 | drops. The <ref table="Bridge" column="fail_mode"/> column in the | |
2462 | <ref table="Bridge"/> table applies to primary controllers. | |
2463 | </p> | |
2464 | ||
2465 | <p> | |
2466 | Open vSwitch permits a bridge to have any number of primary | |
2467 | controllers. When multiple controllers are configured, Open | |
2468 | vSwitch connects to all of them simultaneously. Because | |
2469 | OpenFlow 1.0 does not specify how multiple controllers | |
2470 | coordinate in interacting with a single switch, more than | |
2471 | one primary controller should be specified only if the | |
2472 | controllers are themselves designed to coordinate with each | |
2473 | other. (The Nicira-defined <code>NXT_ROLE</code> OpenFlow | |
2474 | vendor extension may be useful for this.) | |
2475 | </p> | |
2476 | </dd> | |
2477 | <dt>Service controllers</dt> | |
2478 | <dd> | |
2479 | <p> | |
2480 | These kinds of OpenFlow controller connections are intended for | |
2481 | occasional support and maintenance use, e.g. with | |
2482 | <code>ovs-ofctl</code>. Usually a service controller connects only | |
2483 | briefly to inspect or modify some of a switch's state. | |
2484 | </p> | |
2485 | ||
2486 | <p> | |
2487 | Open vSwitch listens for incoming connections from service | |
2488 | controllers. The service controllers initiate and, if necessary, | |
2489 | maintain the connections from their end. The <ref table="Bridge" | |
2490 | column="fail_mode"/> column in the <ref table="Bridge"/> table does | |
2491 | not apply to service controllers. | |
2492 | </p> | |
2493 | ||
2494 | <p> | |
2495 | Open vSwitch supports configuring any number of service controllers. | |
2496 | </p> | |
2497 | </dd> | |
2498 | </dl> | |
2499 | ||
2500 | <p> | |
2501 | The <ref column="target"/> determines the type of controller. | |
2502 | </p> | |
89365653 BP |
2503 | |
2504 | <group title="Core Features"> | |
2505 | <column name="target"> | |
7d674866 BP |
2506 | <p>Connection method for controller.</p> |
2507 | <p> | |
2508 | The following connection methods are currently supported for primary | |
2509 | controllers: | |
2510 | </p> | |
89365653 BP |
2511 | <dl> |
2512 | <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt> | |
2513 | <dd> | |
2514 | <p>The specified SSL <var>port</var> (default: 6633) on the host at | |
7d674866 BP |
2515 | the given <var>ip</var>, which must be expressed as an IP address |
2516 | (not a DNS name). The <ref table="Open_vSwitch" column="ssl"/> | |
2517 | column in the <ref table="Open_vSwitch"/> table must point to a | |
2518 | valid SSL configuration when this form is used.</p> | |
89365653 | 2519 | <p>SSL support is an optional feature that is not always built as |
3fd8d445 | 2520 | part of Open vSwitch.</p> |
89365653 BP |
2521 | </dd> |
2522 | <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt> | |
2523 | <dd>The specified TCP <var>port</var> (default: 6633) on the host at | |
3fd8d445 BP |
2524 | the given <var>ip</var>, which must be expressed as an IP address |
2525 | (not a DNS name).</dd> | |
7d674866 BP |
2526 | </dl> |
2527 | <p> | |
2528 | The following connection methods are currently supported for service | |
2529 | controllers: | |
2530 | </p> | |
2531 | <dl> | |
2532 | <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt> | |
2533 | <dd> | |
2534 | <p> | |
2535 | Listens for SSL connections on the specified TCP <var>port</var> | |
2536 | (default: 6633). If <var>ip</var>, which must be expressed as an | |
2537 | IP address (not a DNS name), is specified, then connections are | |
2538 | restricted to the specified local IP address. | |
2539 | </p> | |
2540 | <p> | |
2541 | The <ref table="Open_vSwitch" column="ssl"/> column in the <ref | |
2542 | table="Open_vSwitch"/> table must point to a valid SSL | |
2543 | configuration when this form is used. | |
2544 | </p> | |
2545 | <p>SSL support is an optional feature that is not always built as | |
3fd8d445 | 2546 | part of Open vSwitch.</p> |
7d674866 BP |
2547 | </dd> |
2548 | <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt> | |
2549 | <dd> | |
2550 | Listens for connections on the specified TCP <var>port</var> | |
2551 | (default: 6633). If <var>ip</var>, which must be expressed as an | |
2552 | IP address (not a DNS name), is specified, then connections are | |
2553 | restricted to the specified local IP address. | |
2554 | </dd> | |
89365653 | 2555 | </dl> |
9a3f4a49 | 2556 | <p>When multiple controllers are configured for a single bridge, the |
3fd8d445 BP |
2557 | <ref column="target"/> values must be unique. Duplicate |
2558 | <ref column="target"/> values yield unspecified results.</p> | |
89365653 BP |
2559 | </column> |
2560 | ||
2561 | <column name="connection_mode"> | |
9a3f4a49 JP |
2562 | <p>If it is specified, this setting must be one of the following |
2563 | strings that describes how Open vSwitch contacts this OpenFlow | |
2564 | controller over the network:</p> | |
2565 | ||
2566 | <dl> | |
2567 | <dt><code>in-band</code></dt> | |
2568 | <dd>In this mode, this controller's OpenFlow traffic travels over the | |
3fd8d445 BP |
2569 | bridge associated with the controller. With this setting, Open |
2570 | vSwitch allows traffic to and from the controller regardless of the | |
2571 | contents of the OpenFlow flow table. (Otherwise, Open vSwitch | |
2572 | would never be able to connect to the controller, because it did | |
2573 | not have a flow to enable it.) This is the most common connection | |
2574 | mode because it is not necessary to maintain two independent | |
2575 | networks.</dd> | |
9a3f4a49 JP |
2576 | <dt><code>out-of-band</code></dt> |
2577 | <dd>In this mode, OpenFlow traffic uses a control network separate | |
3fd8d445 BP |
2578 | from the bridge associated with this controller, that is, the |
2579 | bridge does not use any of its own network devices to communicate | |
2580 | with the controller. The control network must be configured | |
2581 | separately, before or after <code>ovs-vswitchd</code> is started. | |
9a3f4a49 JP |
2582 | </dd> |
2583 | </dl> | |
76ce9432 | 2584 | |
195c8086 | 2585 | <p>If not specified, the default is implementation-specific.</p> |
89365653 BP |
2586 | </column> |
2587 | </group> | |
2588 | ||
2589 | <group title="Controller Failure Detection and Handling"> | |
2590 | <column name="max_backoff"> | |
2591 | Maximum number of milliseconds to wait between connection attempts. | |
2592 | Default is implementation-specific. | |
2593 | </column> | |
2594 | ||
2595 | <column name="inactivity_probe"> | |
2596 | Maximum number of milliseconds of idle time on connection to | |
2597 | controller before sending an inactivity probe message. If Open | |
2598 | vSwitch does not communicate with the controller for the specified | |
2599 | number of seconds, it will send a probe. If a response is not | |
2600 | received for the same additional amount of time, Open vSwitch | |
2601 | assumes the connection has been broken and attempts to reconnect. | |
2bb82bf0 BP |
2602 | Default is implementation-specific. A value of 0 disables |
2603 | inactivity probes. | |
89365653 | 2604 | </column> |
89365653 BP |
2605 | </group> |
2606 | ||
9886b662 BP |
2607 | <group title="Asynchronous Message Configuration"> |
2608 | <p> | |
2609 | OpenFlow switches send certain messages to controllers spontanenously, | |
2610 | that is, not in response to any request from the controller. These | |
2611 | messages are called ``asynchronous messages.'' These columns allow | |
2612 | asynchronous messages to be limited or disabled to ensure the best use | |
2613 | of network resources. | |
2614 | </p> | |
2615 | ||
2616 | <column name="enable_async_messages"> | |
2617 | The OpenFlow protocol enables asynchronous messages at time of | |
2618 | connection establishment, which means that a controller can receive | |
2619 | asynchronous messages, potentially many of them, even if it turns them | |
2620 | off immediately after connecting. Set this column to | |
2621 | <code>false</code> to change Open vSwitch behavior to disable, by | |
2622 | default, all asynchronous messages. The controller can use the | |
2623 | <code>NXT_SET_ASYNC_CONFIG</code> Nicira extension to OpenFlow to turn | |
2624 | on any messages that it does want to receive, if any. | |
2625 | </column> | |
2626 | ||
3fd8d445 | 2627 | <column name="controller_rate_limit"> |
ebb65354 BP |
2628 | <p> |
2629 | The maximum rate at which the switch will forward packets to the | |
2630 | OpenFlow controller, in packets per second. This feature prevents a | |
2631 | single bridge from overwhelming the controller. If not specified, | |
2632 | the default is implementation-specific. | |
2633 | </p> | |
2634 | ||
2635 | <p> | |
2636 | In addition, when a high rate triggers rate-limiting, Open vSwitch | |
2637 | queues controller packets for each port and transmits them to the | |
2638 | controller at the configured rate. The <ref | |
2639 | column="controller_burst_limit"/> value limits the number of queued | |
2640 | packets. Ports on a bridge share the packet queue fairly. | |
2641 | </p> | |
2642 | ||
2643 | <p> | |
2644 | Open vSwitch maintains two such packet rate-limiters per bridge: one | |
2645 | for packets sent up to the controller because they do not correspond | |
2646 | to any flow, and the other for packets sent up to the controller by | |
2647 | request through flow actions. When both rate-limiters are filled with | |
2648 | packets, the actual rate that packets are sent to the controller is | |
2649 | up to twice the specified rate. | |
2650 | </p> | |
3fd8d445 BP |
2651 | </column> |
2652 | ||
2653 | <column name="controller_burst_limit"> | |
2654 | In conjunction with <ref column="controller_rate_limit"/>, | |
2655 | the maximum number of unused packet credits that the bridge will | |
2656 | allow to accumulate, in packets. If not specified, the default | |
2657 | is implementation-specific. | |
2658 | </column> | |
89365653 BP |
2659 | </group> |
2660 | ||
76ce9432 BP |
2661 | <group title="Additional In-Band Configuration"> |
2662 | <p>These values are considered only in in-band control mode (see | |
3fd8d445 | 2663 | <ref column="connection_mode"/>).</p> |
76ce9432 BP |
2664 | |
2665 | <p>When multiple controllers are configured on a single bridge, there | |
3fd8d445 BP |
2666 | should be only one set of unique values in these columns. If different |
2667 | values are set for these columns in different controllers, the effect | |
2668 | is unspecified.</p> | |
89365653 BP |
2669 | |
2670 | <column name="local_ip"> | |
76ce9432 BP |
2671 | The IP address to configure on the local port, |
2672 | e.g. <code>192.168.0.123</code>. If this value is unset, then | |
2673 | <ref column="local_netmask"/> and <ref column="local_gateway"/> are | |
2674 | ignored. | |
89365653 BP |
2675 | </column> |
2676 | ||
2677 | <column name="local_netmask"> | |
76ce9432 BP |
2678 | The IP netmask to configure on the local port, |
2679 | e.g. <code>255.255.255.0</code>. If <ref column="local_ip"/> is set | |
2680 | but this value is unset, then the default is chosen based on whether | |
2681 | the IP address is class A, B, or C. | |
2682 | </column> | |
2683 | ||
2684 | <column name="local_gateway"> | |
2685 | The IP address of the gateway to configure on the local port, as a | |
2686 | string, e.g. <code>192.168.0.1</code>. Leave this column unset if | |
2687 | this network has no gateway. | |
89365653 BP |
2688 | </column> |
2689 | </group> | |
13008eb3 | 2690 | |
bffc0589 AE |
2691 | <group title="Controller Status"> |
2692 | <column name="is_connected"> | |
2693 | <code>true</code> if currently connected to this controller, | |
2694 | <code>false</code> otherwise. | |
2695 | </column> | |
2696 | ||
f9e5e5b3 BP |
2697 | <column name="role" |
2698 | type='{"type": "string", "enum": ["set", ["other", "master", "slave"]]}'> | |
bffc0589 | 2699 | <p>The level of authority this controller has on the associated |
3fd8d445 | 2700 | bridge. Possible values are:</p> |
bffc0589 AE |
2701 | <dl> |
2702 | <dt><code>other</code></dt> | |
2703 | <dd>Allows the controller access to all OpenFlow features.</dd> | |
bffc0589 AE |
2704 | <dt><code>master</code></dt> |
2705 | <dd>Equivalent to <code>other</code>, except that there may be at | |
3fd8d445 BP |
2706 | most one master controller at a time. When a controller configures |
2707 | itself as <code>master</code>, any existing master is demoted to | |
2708 | the <code>slave</code>role.</dd> | |
bffc0589 AE |
2709 | <dt><code>slave</code></dt> |
2710 | <dd>Allows the controller read-only access to OpenFlow features. | |
3fd8d445 BP |
2711 | Attempts to modify the flow table will be rejected with an |
2712 | error. Slave controllers do not receive OFPT_PACKET_IN or | |
2713 | OFPT_FLOW_REMOVED messages, but they do receive OFPT_PORT_STATUS | |
2714 | messages.</dd> | |
bffc0589 AE |
2715 | </dl> |
2716 | </column> | |
2717 | ||
3fd8d445 BP |
2718 | <column name="status" key="last_error"> |
2719 | A human-readable description of the last error on the connection | |
2720 | to the controller; i.e. <code>strerror(errno)</code>. This key | |
2721 | will exist only if an error has occurred. | |
2722 | </column> | |
2723 | ||
f9e5e5b3 BP |
2724 | <column name="status" key="state" |
2725 | type='{"type": "string", "enum": ["set", ["VOID", "BACKOFF", "CONNECTING", "ACTIVE", "IDLE"]]}'> | |
3fd8d445 | 2726 | <p> |
f9e5e5b3 | 2727 | The state of the connection to the controller: |
3fd8d445 | 2728 | </p> |
bffc0589 | 2729 | <dl> |
3fd8d445 BP |
2730 | <dt><code>VOID</code></dt> |
2731 | <dd>Connection is disabled.</dd> | |
2732 | ||
2733 | <dt><code>BACKOFF</code></dt> | |
2734 | <dd>Attempting to reconnect at an increasing period.</dd> | |
2735 | ||
2736 | <dt><code>CONNECTING</code></dt> | |
2737 | <dd>Attempting to connect.</dd> | |
2738 | ||
2739 | <dt><code>ACTIVE</code></dt> | |
2740 | <dd>Connected, remote host responsive.</dd> | |
2741 | ||
2742 | <dt><code>IDLE</code></dt> | |
2743 | <dd>Connection is idle. Waiting for response to keep-alive.</dd> | |
bffc0589 | 2744 | </dl> |
3fd8d445 BP |
2745 | <p> |
2746 | These values may change in the future. They are provided only for | |
2747 | human consumption. | |
2748 | </p> | |
2749 | </column> | |
9cc6bf75 | 2750 | |
f9e5e5b3 BP |
2751 | <column name="status" key="sec_since_connect" |
2752 | type='{"type": "integer", "minInteger": 0}'> | |
3fd8d445 BP |
2753 | The amount of time since this controller last successfully connected to |
2754 | the switch (in seconds). Value is empty if controller has never | |
2755 | successfully connected. | |
bffc0589 | 2756 | </column> |
9cc6bf75 | 2757 | |
f9e5e5b3 BP |
2758 | <column name="status" key="sec_since_disconnect" |
2759 | type='{"type": "integer", "minInteger": 1}'> | |
3fd8d445 BP |
2760 | The amount of time since this controller last disconnected from |
2761 | the switch (in seconds). Value is empty if controller has never | |
2762 | disconnected. | |
2763 | </column> | |
2764 | </group> | |
2765 | ||
f125905c MM |
2766 | <group title="Connection Parameters"> |
2767 | <p> | |
2768 | Additional configuration for a connection between the controller | |
2769 | and the Open vSwitch. | |
2770 | </p> | |
2771 | ||
2772 | <column name="other_config" key="dscp" | |
2773 | type='{"type": "integer"}'> | |
cea15768 EJ |
2774 | The Differentiated Service Code Point (DSCP) is specified using 6 bits |
2775 | in the Type of Service (TOS) field in the IP header. DSCP provides a | |
2776 | mechanism to classify the network traffic and provide Quality of | |
2777 | Service (QoS) on IP networks. | |
2778 | ||
2779 | The DSCP value specified here is used when establishing the connection | |
0442efd9 MM |
2780 | between the controller and the Open vSwitch. If no value is specified, |
2781 | a default value of 48 is chosen. Valid DSCP values must be in the | |
2782 | range 0 to 63. | |
f125905c MM |
2783 | </column> |
2784 | </group> | |
2785 | ||
2786 | ||
3fd8d445 BP |
2787 | <group title="Common Columns"> |
2788 | The overall purpose of these columns is described under <code>Common | |
2789 | Columns</code> at the beginning of this document. | |
2790 | ||
2791 | <column name="external_ids"/> | |
f125905c | 2792 | <column name="other_config"/> |
bffc0589 | 2793 | </group> |
89365653 BP |
2794 | </table> |
2795 | ||
94db5407 BP |
2796 | <table name="Manager" title="OVSDB management connection."> |
2797 | <p> | |
2798 | Configuration for a database connection to an Open vSwitch database | |
2799 | (OVSDB) client. | |
2800 | </p> | |
2801 | ||
2802 | <p> | |
2803 | This table primarily configures the Open vSwitch database | |
2804 | (<code>ovsdb-server</code>), not the Open vSwitch switch | |
2805 | (<code>ovs-vswitchd</code>). The switch does read the table to determine | |
2806 | what connections should be treated as in-band. | |
2807 | </p> | |
2808 | ||
2809 | <p> | |
2810 | The Open vSwitch database server can initiate and maintain active | |
2811 | connections to remote clients. It can also listen for database | |
2812 | connections. | |
2813 | </p> | |
2814 | ||
2815 | <group title="Core Features"> | |
2816 | <column name="target"> | |
2817 | <p>Connection method for managers.</p> | |
2818 | <p> | |
2819 | The following connection methods are currently supported: | |
2820 | </p> | |
2821 | <dl> | |
2822 | <dt><code>ssl:<var>ip</var></code>[<code>:<var>port</var></code>]</dt> | |
2823 | <dd> | |
2824 | <p> | |
2825 | The specified SSL <var>port</var> (default: 6632) on the host at | |
2826 | the given <var>ip</var>, which must be expressed as an IP address | |
2827 | (not a DNS name). The <ref table="Open_vSwitch" column="ssl"/> | |
2828 | column in the <ref table="Open_vSwitch"/> table must point to a | |
2829 | valid SSL configuration when this form is used. | |
2830 | </p> | |
2831 | <p> | |
2832 | SSL support is an optional feature that is not always built as | |
2833 | part of Open vSwitch. | |
2834 | </p> | |
2835 | </dd> | |
2836 | ||
2837 | <dt><code>tcp:<var>ip</var></code>[<code>:<var>port</var></code>]</dt> | |
2838 | <dd> | |
2839 | The specified TCP <var>port</var> (default: 6632) on the host at | |
2840 | the given <var>ip</var>, which must be expressed as an IP address | |
2841 | (not a DNS name). | |
2842 | </dd> | |
2843 | <dt><code>pssl:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt> | |
2844 | <dd> | |
2845 | <p> | |
2846 | Listens for SSL connections on the specified TCP <var>port</var> | |
2847 | (default: 6632). If <var>ip</var>, which must be expressed as an | |
2848 | IP address (not a DNS name), is specified, then connections are | |
2849 | restricted to the specified local IP address. | |
2850 | </p> | |
2851 | <p> | |
2852 | The <ref table="Open_vSwitch" column="ssl"/> column in the <ref | |
2853 | table="Open_vSwitch"/> table must point to a valid SSL | |
2854 | configuration when this form is used. | |
2855 | </p> | |
2856 | <p> | |
2857 | SSL support is an optional feature that is not always built as | |
2858 | part of Open vSwitch. | |
2859 | </p> | |
2860 | </dd> | |
2861 | <dt><code>ptcp:</code>[<var>port</var>][<code>:<var>ip</var></code>]</dt> | |
2862 | <dd> | |
2863 | Listens for connections on the specified TCP <var>port</var> | |
2864 | (default: 6632). If <var>ip</var>, which must be expressed as an | |
2865 | IP address (not a DNS name), is specified, then connections are | |
2866 | restricted to the specified local IP address. | |
2867 | </dd> | |
2868 | </dl> | |
2869 | <p>When multiple managers are configured, the <ref column="target"/> | |
2870 | values must be unique. Duplicate <ref column="target"/> values yield | |
2871 | unspecified results.</p> | |
2872 | </column> | |
2873 | ||
2874 | <column name="connection_mode"> | |
2875 | <p> | |
2876 | If it is specified, this setting must be one of the following strings | |
2877 | that describes how Open vSwitch contacts this OVSDB client over the | |
2878 | network: | |
2879 | </p> | |
299a244b | 2880 | |
94db5407 BP |
2881 | <dl> |
2882 | <dt><code>in-band</code></dt> | |
2883 | <dd> | |
2884 | In this mode, this connection's traffic travels over a bridge | |
2885 | managed by Open vSwitch. With this setting, Open vSwitch allows | |
2886 | traffic to and from the client regardless of the contents of the | |
2887 | OpenFlow flow table. (Otherwise, Open vSwitch would never be able | |
2888 | to connect to the client, because it did not have a flow to enable | |
2889 | it.) This is the most common connection mode because it is not | |
2890 | necessary to maintain two independent networks. | |
2891 | </dd> | |
2892 | <dt><code>out-of-band</code></dt> | |
2893 | <dd> | |
2894 | In this mode, the client's traffic uses a control network separate | |
2895 | from that managed by Open vSwitch, that is, Open vSwitch does not | |
2896 | use any of its own network devices to communicate with the client. | |
2897 | The control network must be configured separately, before or after | |
2898 | <code>ovs-vswitchd</code> is started. | |
2899 | </dd> | |
2900 | </dl> | |
2901 | ||
2902 | <p> | |
2903 | If not specified, the default is implementation-specific. | |
2904 | </p> | |
2905 | </column> | |
2906 | </group> | |
2907 | ||
2908 | <group title="Client Failure Detection and Handling"> | |
2909 | <column name="max_backoff"> | |
2910 | Maximum number of milliseconds to wait between connection attempts. | |
2911 | Default is implementation-specific. | |
2912 | </column> | |
2913 | ||
2914 | <column name="inactivity_probe"> | |
2915 | Maximum number of milliseconds of idle time on connection to the client | |
2916 | before sending an inactivity probe message. If Open vSwitch does not | |
2917 | communicate with the client for the specified number of seconds, it | |
2918 | will send a probe. If a response is not received for the same | |
2919 | additional amount of time, Open vSwitch assumes the connection has been | |
2920 | broken and attempts to reconnect. Default is implementation-specific. | |
2bb82bf0 | 2921 | A value of 0 disables inactivity probes. |
94db5407 BP |
2922 | </column> |
2923 | </group> | |
2924 | ||
0b3e7a8b AE |
2925 | <group title="Status"> |
2926 | <column name="is_connected"> | |
2927 | <code>true</code> if currently connected to this manager, | |
2928 | <code>false</code> otherwise. | |
2929 | </column> | |
2930 | ||
3fd8d445 BP |
2931 | <column name="status" key="last_error"> |
2932 | A human-readable description of the last error on the connection | |
2933 | to the manager; i.e. <code>strerror(errno)</code>. This key | |
2934 | will exist only if an error has occurred. | |
2935 | </column> | |
2936 | ||
f9e5e5b3 BP |
2937 | <column name="status" key="state" |
2938 | type='{"type": "string", "enum": ["set", ["VOID", "BACKOFF", "CONNECTING", "ACTIVE", "IDLE"]]}'> | |
3fd8d445 | 2939 | <p> |
f9e5e5b3 | 2940 | The state of the connection to the manager: |
3fd8d445 | 2941 | </p> |
a11f6164 | 2942 | <dl> |
3fd8d445 BP |
2943 | <dt><code>VOID</code></dt> |
2944 | <dd>Connection is disabled.</dd> | |
2945 | ||
2946 | <dt><code>BACKOFF</code></dt> | |
2947 | <dd>Attempting to reconnect at an increasing period.</dd> | |
2948 | ||
2949 | <dt><code>CONNECTING</code></dt> | |
2950 | <dd>Attempting to connect.</dd> | |
2951 | ||
2952 | <dt><code>ACTIVE</code></dt> | |
2953 | <dd>Connected, remote host responsive.</dd> | |
2954 | ||
2955 | <dt><code>IDLE</code></dt> | |
2956 | <dd>Connection is idle. Waiting for response to keep-alive.</dd> | |
a11f6164 | 2957 | </dl> |
3fd8d445 BP |
2958 | <p> |
2959 | These values may change in the future. They are provided only for | |
2960 | human consumption. | |
2961 | </p> | |
2962 | </column> | |
2963 | ||
f9e5e5b3 BP |
2964 | <column name="status" key="sec_since_connect" |
2965 | type='{"type": "integer", "minInteger": 0}'> | |
3fd8d445 BP |
2966 | The amount of time since this manager last successfully connected |
2967 | to the database (in seconds). Value is empty if manager has never | |
2968 | successfully connected. | |
2969 | </column> | |
2970 | ||
f9e5e5b3 BP |
2971 | <column name="status" key="sec_since_disconnect" |
2972 | type='{"type": "integer", "minInteger": 0}'> | |
3fd8d445 BP |
2973 | The amount of time since this manager last disconnected from the |
2974 | database (in seconds). Value is empty if manager has never | |
2975 | disconnected. | |
2976 | </column> | |
2977 | ||
2978 | <column name="status" key="locks_held"> | |
2979 | Space-separated list of the names of OVSDB locks that the connection | |
2980 | holds. Omitted if the connection does not hold any locks. | |
2981 | </column> | |
2982 | ||
2983 | <column name="status" key="locks_waiting"> | |
2984 | Space-separated list of the names of OVSDB locks that the connection is | |
2985 | currently waiting to acquire. Omitted if the connection is not waiting | |
2986 | for any locks. | |
2987 | </column> | |
2988 | ||
2989 | <column name="status" key="locks_lost"> | |
2990 | Space-separated list of the names of OVSDB locks that the connection | |
2991 | has had stolen by another OVSDB client. Omitted if no locks have been | |
2992 | stolen from this connection. | |
2993 | </column> | |
2994 | ||
f9e5e5b3 BP |
2995 | <column name="status" key="n_connections" |
2996 | type='{"type": "integer", "minInteger": 2}'> | |
3fd8d445 BP |
2997 | <p> |
2998 | When <ref column="target"/> specifies a connection method that | |
2999 | listens for inbound connections (e.g. <code>ptcp:</code> or | |
3000 | <code>pssl:</code>) and more than one connection is actually active, | |
3001 | the value is the number of active connections. Otherwise, this | |
3002 | key-value pair is omitted. | |
3003 | </p> | |
3004 | <p> | |
3005 | When multiple connections are active, status columns and key-value | |
3006 | pairs (other than this one) report the status of one arbitrarily | |
3007 | chosen connection. | |
3008 | </p> | |
0b3e7a8b AE |
3009 | </column> |
3010 | </group> | |
3fd8d445 | 3011 | |
f125905c MM |
3012 | <group title="Connection Parameters"> |
3013 | <p> | |
3014 | Additional configuration for a connection between the manager | |
3015 | and the Open vSwitch Database. | |
3016 | </p> | |
3017 | ||
3018 | <column name="other_config" key="dscp" | |
3019 | type='{"type": "integer"}'> | |
cea15768 EJ |
3020 | The Differentiated Service Code Point (DSCP) is specified using 6 bits |
3021 | in the Type of Service (TOS) field in the IP header. DSCP provides a | |
3022 | mechanism to classify the network traffic and provide Quality of | |
3023 | Service (QoS) on IP networks. | |
3024 | ||
3025 | The DSCP value specified here is used when establishing the connection | |
0442efd9 MM |
3026 | between the manager and the Open vSwitch. If no value is specified, a |
3027 | default value of 48 is chosen. Valid DSCP values must be in the range | |
3028 | 0 to 63. | |
f125905c MM |
3029 | </column> |
3030 | </group> | |
3031 | ||
3fd8d445 BP |
3032 | <group title="Common Columns"> |
3033 | The overall purpose of these columns is described under <code>Common | |
3034 | Columns</code> at the beginning of this document. | |
3035 | ||
3036 | <column name="external_ids"/> | |
f125905c | 3037 | <column name="other_config"/> |
3fd8d445 | 3038 | </group> |
94db5407 BP |
3039 | </table> |
3040 | ||
89365653 BP |
3041 | <table name="NetFlow"> |
3042 | A NetFlow target. NetFlow is a protocol that exports a number of | |
3043 | details about terminating IP flows, such as the principals involved | |
3044 | and duration. | |
3045 | ||
3046 | <column name="targets"> | |
3047 | NetFlow targets in the form | |
3048 | <code><var>ip</var>:<var>port</var></code>. The <var>ip</var> | |
3049 | must be specified numerically, not as a DNS name. | |
3050 | </column> | |
3051 | ||
3052 | <column name="engine_id"> | |
3053 | Engine ID to use in NetFlow messages. Defaults to datapath index | |
3054 | if not specified. | |
3055 | </column> | |
3056 | ||
3057 | <column name="engine_type"> | |
3058 | Engine type to use in NetFlow messages. Defaults to datapath | |
3059 | index if not specified. | |
3060 | </column> | |
3061 | ||
3062 | <column name="active_timeout"> | |
3063 | The interval at which NetFlow records are sent for flows that are | |
3064 | still active, in seconds. A value of <code>0</code> requests the | |
3065 | default timeout (currently 600 seconds); a value of <code>-1</code> | |
3066 | disables active timeouts. | |
3067 | </column> | |
3068 | ||
3069 | <column name="add_id_to_interface"> | |
3070 | <p>If this column's value is <code>false</code>, the ingress and egress | |
3fd8d445 BP |
3071 | interface fields of NetFlow flow records are derived from OpenFlow port |
3072 | numbers. When it is <code>true</code>, the 7 most significant bits of | |
3073 | these fields will be replaced by the least significant 7 bits of the | |
3074 | engine id. This is useful because many NetFlow collectors do not | |
3075 | expect multiple switches to be sending messages from the same host, so | |
3076 | they do not store the engine information which could be used to | |
3077 | disambiguate the traffic.</p> | |
89365653 BP |
3078 | <p>When this option is enabled, a maximum of 508 ports are supported.</p> |
3079 | </column> | |
13008eb3 | 3080 | |
3fd8d445 BP |
3081 | <group title="Common Columns"> |
3082 | The overall purpose of these columns is described under <code>Common | |
3083 | Columns</code> at the beginning of this document. | |
3084 | ||
3085 | <column name="external_ids"/> | |
3086 | </group> | |
89365653 BP |
3087 | </table> |
3088 | ||
3089 | <table name="SSL"> | |
3090 | SSL configuration for an Open_vSwitch. | |
3091 | ||
3092 | <column name="private_key"> | |
3093 | Name of a PEM file containing the private key used as the switch's | |
3094 | identity for SSL connections to the controller. | |
3095 | </column> | |
3096 | ||
3097 | <column name="certificate"> | |
3098 | Name of a PEM file containing a certificate, signed by the | |
3099 | certificate authority (CA) used by the controller and manager, | |
3100 | that certifies the switch's private key, identifying a trustworthy | |
3101 | switch. | |
3102 | </column> | |
3103 | ||
3104 | <column name="ca_cert"> | |
3105 | Name of a PEM file containing the CA certificate used to verify | |
3106 | that the switch is connected to a trustworthy controller. | |
3107 | </column> | |
3108 | ||
3109 | <column name="bootstrap_ca_cert"> | |
3110 | If set to <code>true</code>, then Open vSwitch will attempt to | |
3111 | obtain the CA certificate from the controller on its first SSL | |
3112 | connection and save it to the named PEM file. If it is successful, | |
3113 | it will immediately drop the connection and reconnect, and from then | |
3114 | on all SSL connections must be authenticated by a certificate signed | |
3115 | by the CA certificate thus obtained. <em>This option exposes the | |
3fd8d445 BP |
3116 | SSL connection to a man-in-the-middle attack obtaining the initial |
3117 | CA certificate.</em> It may still be useful for bootstrapping. | |
89365653 | 3118 | </column> |
13008eb3 | 3119 | |
3fd8d445 BP |
3120 | <group title="Common Columns"> |
3121 | The overall purpose of these columns is described under <code>Common | |
3122 | Columns</code> at the beginning of this document. | |
3123 | ||
3124 | <column name="external_ids"/> | |
3125 | </group> | |
89365653 BP |
3126 | </table> |
3127 | ||
3128 | <table name="sFlow"> | |
3129 | <p>An sFlow(R) target. sFlow is a protocol for remote monitoring | |
3fd8d445 | 3130 | of switches.</p> |
89365653 BP |
3131 | |
3132 | <column name="agent"> | |
e723ff43 | 3133 | Name of the network device whose IP address should be reported as the |
733adf2a LG |
3134 | ``agent address'' to collectors. If not specified, the agent device is |
3135 | figured from the first target address and the routing table. If the | |
3136 | routing table does not contain a route to the target, the IP address | |
e723ff43 BP |
3137 | defaults to the <ref table="Controller" column="local_ip"/> in the |
3138 | collector's <ref table="Controller"/>. If an agent IP address cannot be | |
733adf2a | 3139 | determined any of these ways, sFlow is disabled. |
89365653 BP |
3140 | </column> |
3141 | ||
3142 | <column name="header"> | |
3143 | Number of bytes of a sampled packet to send to the collector. | |
3144 | If not specified, the default is 128 bytes. | |
3145 | </column> | |
3146 | ||
3147 | <column name="polling"> | |
3148 | Polling rate in seconds to send port statistics to the collector. | |
3149 | If not specified, defaults to 30 seconds. | |
3150 | </column> | |
3151 | ||
3152 | <column name="sampling"> | |
3153 | Rate at which packets should be sampled and sent to the collector. | |
3154 | If not specified, defaults to 400, which means one out of 400 | |
3155 | packets, on average, will be sent to the collector. | |
3156 | </column> | |
3157 | ||
3158 | <column name="targets"> | |
3159 | sFlow targets in the form | |
3160 | <code><var>ip</var>:<var>port</var></code>. | |
3161 | </column> | |
13008eb3 | 3162 | |
3fd8d445 BP |
3163 | <group title="Common Columns"> |
3164 | The overall purpose of these columns is described under <code>Common | |
3165 | Columns</code> at the beginning of this document. | |
3166 | ||
3167 | <column name="external_ids"/> | |
3168 | </group> | |
89365653 | 3169 | </table> |
c1c9c9c4 | 3170 | |
89365653 | 3171 | </database> |