| 다음 판 | 이전 판 |
| ovs_for_legacy_network-script [2021/07/05 03:32] – 만듦 koov | ovs_for_legacy_network-script [2021/07/27 06:55] (현재) – [ovs for legacy network-script] koov |
|---|
| The RPM packages for Open vSwitch provide some integration with RedHat’s network scripts. Using this integration is optional. | The RPM packages for Open vSwitch provide some integration with RedHat’s network scripts. Using this integration is optional. |
| |
| To use the integration for a Open vSwitch bridge or interface named <name>, create or edit /etc/sysconfig/network-scripts/ifcfg-<name>. | To use the integration for a Open vSwitch bridge or interface named <name>, create or edit ''/etc/sysconfig/network-scripts/ifcfg-<name>''. |
| This is a shell script that consists of a series of VARIABLE=VALUE assignments. The following OVS-specific variable names are supported: | This is a shell script that consists of a series of ''VARIABLE=VALUE'' assignments. The following OVS-specific variable names are supported: |
| |
| - ''DEVICETYPE'': Always set to "ovs". | - ''DEVICETYPE'': Always set to ''ovs''. |
| - ''TYPE'': If this is "OVSBridge", then this file represents an OVS bridge named <name>. Otherwise, it represents a port on an OVS bridge and TYPE must have one of the following values: | - ''TYPE'': If this is ''OVSBridge'', then this file represents an OVS bridge named <name>. Otherwise, it represents a port on an OVS bridge and TYPE must have one of the following values: |
| * ''OVSPort'', if <name> is a physical port (e.g. eth0) or virtual port (e.g. vif1.0). | * ''OVSPort'', if <name> is a physical port (e.g. eth0) or virtual port (e.g. vif1.0). |
| * ''OVSIntPort'', if <name> is an internal port (e.g. a tagged VLAN). | * ''OVSIntPort'', if <name> is an internal port (e.g. a tagged VLAN). |
| * ''OVSTunnel'', if <name> is an OVS tunnel. | * ''OVSTunnel'', if <name> is an OVS tunnel. |
| * ''OVSPatchPort'', if <name> is a patch port | * ''OVSPatchPort'', if <name> is a patch port |
| - ''OVS_BRIDGE'': If TYPE is anything other than "OVSBridge", set to the name of the OVS bridge to which the port should be attached. | - ''OVS_BRIDGE'': If TYPE is anything other than ''OVSBridge'', set to the name of the OVS bridge to which the port should be attached. |
| - ''OVS_OPTIONS'': Optionally, extra options to set in the "Port" table when adding the port to the bridge, as a sequence of column[:key]=value options. For example, "tag=100" to make the port an access port for VLAN 100. See the documentation of "add-port" in ovs-vsctl(8) for syntax and the section on the Port table in ovs-vswitchd.conf.db(5) for available options. | - ''OVS_OPTIONS'': Optionally, extra options to set in the ''Port'' table when adding the port to the bridge, as a sequence of ''column[:key]=value'' options. For example, ''tag=100'' to make the port an access port for VLAN 100. See the documentation of ''add-port'' in ovs-vsctl(8) for syntax and the section on the Port table in ''ovs-vswitchd.conf.db(5)'' for available options. |
| - ''OVS_EXTRA'': Optionally, additional ovs-vsctl commands, separated by "--" (double dash). | - ''OVS_EXTRA'': Optionally, additional ovs-vsctl commands, separated by ''%%--%%'' (double dash). |
| - ''BOND_IFACES'': For "OVSBond" interfaces, a list of physical interfaces to bond together. | - ''BOND_IFACES'': For ''OVSBond'' interfaces, a list of physical interfaces to bond together. |
| - ''OVS_TUNNEL_TYPE'': For "OVSTunnel" interfaces, the type of the tunnel. | - ''OVS_TUNNEL_TYPE'': For ''OVSTunnel'' interfaces, the type of the tunnel. |
| For example, "gre", "vxlan", etc. | For example, ''gre'', ''vxlan'', etc. |
| - ''OVS_TUNNEL_OPTIONS'': For "OVSTunnel" interfaces, this field should be used to specify the tunnel options like remote_ip, key, etc. | - ''OVS_TUNNEL_OPTIONS'': For ''OVSTunnel'' interfaces, this field should be used to specify the tunnel options like remote_ip, key, etc. |
| - ''OVS_PATCH_PEER'': For "OVSPatchPort" devices, this field specifies the patch's peer on the other bridge. | - ''OVS_PATCH_PEER'': For ''OVSPatchPort'' devices, this field specifies the patch's peer on the other bridge. |
| |
| ===== 주의사항 ===== | ===== 주의사항 ===== |
| |
| * "ifdown" on a bridge will not bring individual ports on the bridge down. "ifup" on a bridge will not add ports to the bridge. This behavior should be compatible with standard bridges (with TYPE=Bridge). | * ''ifdown'' on a bridge will not bring individual ports on the bridge down. ''ifup'' on a bridge will not add ports to the bridge. This behavior should be compatible with standard bridges (with ''TYPE=Bridge''). |
| * If 'ifup' on an interface is called multiple times, one can see "RTNETLINK answers: File exists" printed on the console. This comes from ifup-eth trying to add zeroconf route multiple times and is harmless. | * If ''ifup'' on an interface is called multiple times, one can see ''RTNETLINK answers: File exists'' printed on the console. This comes from ''ifup-eth'' trying to add zeroconf route multiple times and is harmless. |
| |
| ===== 사용예제 ===== | ===== 사용예제 ===== |
| NETMASK=X.Y.Z.0 | NETMASK=X.Y.Z.0 |
| HOTPLUG=no | HOTPLUG=no |
| | STP=on |
| </code> | </code> |
| </WRAP> | </WRAP> |
| ==== Internal Port with DHCP: ==== | ==== Internal Port with DHCP: ==== |
| |
| * Needs OVSBOOTPROTO or BOOTPROTO. | * Needs ''OVSBOOTPROTO'' or ''BOOTPROTO''. |
| * All the interfaces that can reach the DHCP server as a space separated list in OVSDHCPINTERFACES. | * All the interfaces that can reach the DHCP server as a space separated list in ''OVSDHCPINTERFACES''. |
| <WRAP prewrap> | <WRAP prewrap> |
| <code vim> | <code vim> |