SUSECON
Results 1 to 7 of 7

Thread: bonding apply fails upon reboot

Threaded View

  1. #1

    Post bonding apply fails upon reboot

    Hello,

    I have configured bonding mode 4 (802.3ad) with 4 physical NICs.

    ifcfg-public
    STARTMODE='auto'
    BOOTPROTO='none'
    MTU=9000
    BONDING_MASTER='yes'
    BONDING_SLAVE_0='eth2'
    BONDING_SLAVE_1='eth3'
    BONDING_SLAVE_2='eth4'
    BONDING_SLAVE_3='eth5'
    BONDING_MODULE_OPTS='mode=802.3ad miimon=100'

    ifcfg-eth2 (same for ifcfg-eth3~eth5)
    BOOTPROTO=None
    STARTMODE=hotplug

    A problem is if I reboot the node, the bond mode is reset to 1 (round robin) as confirmed in /proc/net/bonding/public.
    I am suspicious SLES fails to apply the configured bond mode (4) during the start-up process.

    This log just repeats without further progress.
    kernel: [ 20.011781] bonding: public is being created...
    kernel: [ 20.323366] bonding: public: enslaving eth5 as an active interface with an up link.
    kernel: [ 21.490152] bonding: public: enslaving eth2 as an active interface with an up link.
    kernel: [ 21.892754] bonding: public: enslaving eth3 as an active interface with an up link.
    kernel: [ 22.289116] bonding: public: enslaving eth4 as an active interface with an up link.

    To resolve it, I found I have to run 'systemctl restart wicked wickedd', then the bond mode is changed to 4 (802.3ad) again.
    However I want to avoid such manual operation upon reboot.

    Has anyone experienced it or any suggestion?

    SLES 12 SP1

    Thanks,
    Jerry
    Last edited by jerry98; 18-Jul-2016 at 22:52.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •