User guide

3–InfiniBand
®
Cluster Setup and Administration
IB Bonding
3-6 IB0054606-02 A
NAME field specified in the CREATE block. The following is an example of the
ifcfg-NAME file:
DEVICE=ib1
BOOTPROTO=static
BROADCAST=192.168.18.255
IPADDR=192.168.18.120
NETMASK=255.255.255.0
ONBOOT=yes
NM_CONTROLLED=no
2. After modifying the /etc/sysconfig/ipoib.cfg file, restart the IPoIB driver
with the following:
/etc/init.d/openibd restart
IB Bonding
IB bonding is a high availability solution for IPoIB interfaces. It is based on the
Linux Ethernet Bonding Driver and was adopted to work with IPoIB. The support
for IPoIB interfaces is only for the active-backup mode, other modes should not be
used. QLogic supports bonding across HCA ports and bonding port 1 and port 2
on the same HCA.
Interface Configuration Scripts
Create interface configuration scripts for the ibX and bondX interfaces. Once the
configurations are in place, perform a server reboot, or a service network restart.
For SLES operating systems (OS), a server reboot is required. Refer to the
following standard syntax for bonding configuration by the OS.
NOTE
For IPoIB, the INSTALL script for the adapter now helps the user
create the
ifcfg files.
NOTE
For all of the following OS configuration script examples that set MTU,
MTU=65520 is valid only if all IPoIB slaves operate in connected mode and
are configured with the same value. For IPoIB slaves that work in datagram
mode, use MTU=2044. If the MTU is not set correctly or the MTU is not set
at all (set to the default value), performance of the interface may be lower.