NAME¶

ifcfg-ovs-bridge - openvswitch bridge configuration

SYNOPSIS¶

/etc/sysconfig/network/ifcfg-*

CONFIGURATION¶

To setup an ovs bridge interface you need a configuration file ifcfg-<interface-name> with the usual network settings. But you must add additional variables:

OVS_BRIDGE <yes|no>

This option must be set to 'yes' to identify this interface as ovs bridge interface.

OVS_BRIDGE_PORT_DEVICE[suffix] <port device name>

This suffix variable contains the names of port devices to enslave into the bridge, each port suffix has to be a unique keyword, e.g. _1 .. _N.

OVS_BRIDGE_VLAN_PARENT <parent device name>

Permits to create a ``fake bridge`` referring to the ``parent bridge`` with implicit VLAN on the ports of the ``parent bridge``.

OVS_BRIDGE_VLAN_TAG <vlan tag>

The 802.1Q VLAN tag or ID used to filter traffic for the ``fake bridge`` on ports of the ``parent bridge``.

EXAMPLE¶

Minimal example for a ovs bridge interface on eth2 and eth3, the bridge interface itself is configured via dhcp:

ifcfg-ovsbr0

	STARTMODE='nfsroot'
	BOOTPROTO='dhcp'
	OVS_BRIDGE='yes'
	OVS_BRIDGE_PORT_DEVICE_2='eth2'
	OVS_BRIDGE_PORT_DEVICE_3='eth3'

Note: STARTMODE='nfsroot' is recommended if additional ports are created on the bridge e.g. with ovs-vsctl. This start mode prevents the bridge from being teared down at system shutdown, which would cause all configuration saved in the openvswitch data base to be lost after rebooting the system. If no such local configuration is made, e.g. because the bridge is only used for ports being dynamically added by libvirt, other start modes can be used as well.

ADDITIONAL INFORMATION¶

For additional and more general information have a look into documentation provided at <http://openvswitch.org/>.

COPYRIGHT¶

Copyright (C) 2012 SUSE Linux GmbH, Nuernberg, Germany.

BUGS¶

Please report bugs as described at <https://bugs.opensuse.org>

AUTHOR¶

Marius Tomaschewski

SEE ALSO¶

ifcfg(5), wicked(8), ovs-vsctl(8).