1 Red Hat network scripts integration
2 -----------------------------------
4 The RPM packages for Open vSwitch provide some integration with Red
5 Hat's network scripts. Using this integration is optional.
7 To use the integration for a Open vSwitch bridge or interface named
8 <name>, create or edit /etc/sysconfig/network-scripts/ifcfg-<name>.
9 This is a shell script that consists of a series of VARIABLE=VALUE
10 assignments. The following OVS-specific variable names are supported:
12 - DEVICETYPE: Always set to "ovs".
14 - TYPE: If this is "OVSBridge", then this file represents an OVS
15 bridge named <name>. Otherwise, it represents a port on an OVS
16 bridge and TYPE must have one of the following values:
18 * "OVSPort", if <name> is a physical port (e.g. eth0) or
19 virtual port (e.g. vif1.0).
21 * "OVSIntPort", if <name> is an internal port (e.g. a tagged
24 * "OVSBond", if <name> is an OVS bond.
26 * "OVSTunnel", if <name> is an OVS tunnel.
28 - OVS_BRIDGE: If TYPE is anything other than "OVSBridge", set to
29 the name of the OVS bridge to which the port should be attached.
31 - OVS_OPTIONS: Optionally, extra options to set in the "Port"
32 table when adding the port to the bridge, as a sequence of
33 column[:key]=value options. For example, "tag=100" to make the
34 port an access port for VLAN 100. See the documentation of
35 "add-port" in ovs-vsctl(8) for syntax and the section on the
36 Port table in ovs-vswitchd.conf.db(5) for available options.
38 - OVS_EXTRA: Optionally, additional ovs-vsctl commands, separated
39 by "--" (double dash).
41 - BOND_IFACES: For "OVSBond" interfaces, a list of physical
42 interfaces to bond together.
44 - OVS_TUNNEL_TYPE: For "OVSTunnel" interfaces, the type of the tunnel.
45 For example, "gre", "vxlan", etc.
47 - OVS_TUNNEL_OPTIONS: For "OVSTunnel" interfaces, this field should be
48 used to specify the tunnel options like remote_ip, key, etc.
53 * "ifdown" on a bridge will not bring individual ports on the bridge
54 down. "ifup" on a bridge will not add ports to the bridge. This
55 behavior should be compatible with standard bridges (with
58 * If 'ifup' on an interface is called multiple times, one can see
59 "RTNETLINK answers: File exists" printed on the console. This comes from
60 ifup-eth trying to add zeroconf route multiple times and is harmless.
67 ==> ifcfg-ovsbridge0 <==
77 Enable DHCP on the bridge:
78 * Needs OVSBOOTPROTO instead of BOOTPROTO.
79 * All the interfaces that can reach the DHCP server
80 as a space separated list in OVSDHCPINTERFACES.
87 OVSDHCPINTERFACES="eth0"
91 Adding Internal Port to ovsbridge0:
102 Internal Port with fixed IP address:
108 OVS_BRIDGE=ovsbridge0
114 Internal Port with DHCP:
115 * Needs OVSBOOTPROTO or BOOTPROTO.
116 * All the interfaces that can reach the DHCP server
117 as a space separated list in OVSDHCPINTERFACES.
123 OVS_BRIDGE=ovsbridge0
125 OVSDHCPINTERFACES="eth0"
128 Adding physical eth0 to ovsbridge0 described above:
135 OVS_BRIDGE=ovsbridge0
140 Tagged VLAN interface on top of ovsbridge0:
142 ==> ifcfg-vlan100 <==
150 OVS_BRIDGE=ovsbridge0
151 OVS_OPTIONS="tag=100"
152 OVS_EXTRA="set Interface $DEVICE external-ids:iface-id=$(hostname -s)-$DEVICE-vif"
163 OVS_BRIDGE=ovsbridge0
165 BOND_IFACES="gige-1b-0 gige-1b-1 gige-21-0 gige-21-1"
166 OVS_OPTIONS="bond_mode=balance-tcp lacp=active"
174 An Open vSwitch Tunnel:
181 OVS_BRIDGE=ovsbridge0
183 OVS_TUNNEL_OPTIONS="options:remote_ip=A.B.C.D"
188 Please report problems to bugs@openvswitch.org.