Advanced Networking Concepts Applied Using Linux on System z: Changes to Implementing the Bonding Module

Abstract

There are changes to using channel bonding interfaces introduced with SLES 11 SP 2. Eric Marins, an IBM® IT Specialist for Linux on IBM System z®, offers insight into these changes with the following updates to section 4.2 of the IBM Redbooks® publication Advanced Networking Concepts Applied Using Linux on IBM System z, SG24-7995.

For related information about this topic, refer to the following IBM Redbooks publication:
Advanced Networking Concepts Applied Using Linux on IBM System z, SG24-7995-00

Contents

This example provides updates for the files and commands used by Linux on System z running SLES 11 SP2.

1. To activate the bonding module when the network interface is loaded, create a new file called /etc/modprobe.d/bonding.conf with the following content:

      #/etc/modprobe.d/bonding.conf file
      alias netdev-bond0 bonding
      options lacp_rate=fast miimon=500 mode=4 xmit_hash_policy=layer2
    2. Ensure that you have the correct module name listed in /etc/modprobe.d/bonding.conf (shown in red.)

        #/etc/modprobe.d/bonding.conf file:
        alias
        netdev-bond0 bonding
        options lacp_rate=fast miimon=500 mode=4 xmit_hash_policy=layer2


    3. Load the module by issuing the following command from a command prompt:

    modprobe bonding

    4. Add the following tags in the /etc/sysconfig/network/ifcfg-bond0 file:

        NAME='Bond0'
        DEVICE=bond0

    5. Remove the following tag in the /etc/sysconfig/network/ifcfg-eth1, /etc/sysconfig/network/ifcfg-eth2 and /etc/sysconfig/network/ifcfg-bond0 files:
        LLADDR=X:X:X:X:X:X #where X:X:X:X:X:X is a MAC address

    6. Recycle the network service to load the bonding device by issuing the following command from a command prompt:

    /etc/init.d/network restart

    7. Use the new command ip link show to report the relationship between the interfaces MASTER and SLAVE:

        ip link show

    The ip link show command produces the following output:

        1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
        link/ether 02:a0:a1:00:00:1a brd ff:ff:ff:ff:ff:ff
        3: eth1: <BROADCAST,MULTICAST,
        SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UNKNOWN qlen 1000
        link/ether 02:00:00:0e:d0:05 brd ff:ff:ff:ff:ff:ff
        4: eth2: <BROADCAST,MULTICAST,
        SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UNKNOWN qlen 1000
        link/ether 02:00:00:0e:d0:05 brd ff:ff:ff:ff:ff:ff
        7: bond0: <BROADCAST,MULTICAST
        ,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
        link/ether 02:00:00:0e:d0:05 brd ff:ff:ff:ff:ff:ff

    Special Notices

    This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment. publib-b.boulder.ibm.com

    Profile

    Publish Date
    29 March 2013


    Rating:
    (based on 1 review)


    Author(s)

    IBM Form Number
    TIPS1000