User Manual

Features Overview and ConfigurationRev 2.3-1.0.1
Mellanox Technologies
132
• The only meaningful bonding policy in IPoIB is High-Availability (bonding mode num-
ber 1, or active-backup)
• Bonding parameter "fail_over_mac" is meaningless in IPoIB interfaces, hence, the only
supported value is the default: 0 (or "none" in SLES1
1)
For a persistent bonding IPoIB Network configuration, use the same Linux Network Scripts
semantics, with the following exceptions/ additions:
• In the bonding master configuration file (e.g: ifcfg-bond0), in addition to Linux bonding
semantics, use the following parameter: MTU=65520
65520 is a valid MTU value only if all IPoIB slaves operate in Connected mode (See
Section 3.2.5.1.1, “IPoIB Mode Setting”, on page 126) and are configured with
the same value. For IPoIB slaves that work in datagram mode, use MTU=2044. If you
do not set the correct MTU or do not set MTU at all, performance of the interface
might decrease.
• In the bonding slave configuration file (e.g: ifcfg-ib0), use the same Linux Network
Scripts semantics. In particular: DEVICE=ib0
• In the bonding slave configuration file (e.g: ifcfg-ib0.8003), the line TYPE=InfiniBand
is necessary when using bonding over devices configured with partitions (p_key)
• For RHEL users:
In /etc/modprobe.b/bond.conf add the following lines:
alias bond0 bonding
• For SLES users:
It is necessary to update the MANDATORY_DEVICES environment variable in /etc/syscon-
fig/network/config with the names of the IPoIB slave devices (e.g. ib0, ib1, etc.). Otherwise,
bonding master may be created before IPoIB slave interfaces at boot time.
It is possible to have multiple IPoIB bonding masters and a mix of IPoIB bonding master and
Ethernet bonding master
. However, It is NOT possible to mix Ethernet and IPoIB slaves under
the same bonding master
Restarting openibd does no keep the bonding configuration via Network Scripts. You
have to restart the network service in order to bring up the bonding master. After the
configuration is saved, restart the network service by running: /etc/init.d/network
restart.
3.2.5.2 Ethernet Tunneling Over IPoIB Driver (eIPoIB)
The eth_ipoib driver provides a standard Ethernet interface to be used as a Physical Interface
(PIF) into the Hypervisor virtual network, and serves one or more
Virtual Interfaces (VIF). This
driver supports L2 Switching (Direct Bridging) as well as other L3 Switching modes (e.g. NAT).
This document explains the configuration and driver behavior when configured in Bridging
mode.
In virtualization environment, a virtual machine can be expose to the physical network by per-
forming the next setting:
Step 1. Create a virtual bridge
Step 2. Attach the para-virtualized interface created by the eth_ipoib driver to the bridge