Vlan not starting up on Bond interface on boot

Issues related to configuring your network
Post Reply
kiserp
Posts: 2
Joined: 2015/03/23 16:22:21

Vlan not starting up on Bond interface on boot

Post by kiserp » 2015/03/23 16:30:20

I have dell poweredge 1950 server with 2 NIC.
I created one bond interface with 2 slaves in it using nmtui, so all configs are created automatically and are standard
It works well, but after reboot vlans (bond0.xxx) won't start up automatically, all vlans starting up after I ran 'ifup bond0.2'.
Configs are below

Code: Select all

TYPE=Ethernet
NAME=eno1
UUID=d5d2b095-acec-4349-a8ef-b24772e69490
DEVICE=eno1
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
#NM_CONTROLLED=no

Code: Select all

TYPE=Ethernet
NAME=eno2
UUID=c28b6111-6e4b-486b-b8ee-65e1f1e1898b
DEVICE=eno2
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
#NM_CONTROLLED=no

Code: Select all

DEVICE=bond0
TYPE=Bond
BONDING_MASTER=yes
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=bond0
UUID=62effb3d-2881-4af9-ae18-7c9e5246d476
ONBOOT=yes
BOOTPROTO=none
BONDING_OPTS="updelay=0 resend_igmp=1 use_carrier=1 miimon=100 downdelay=0 xmit_hash_policy=0 primary_reselect=0 fail_over_mac=0 arp_validate=0 mode=802.3ad arp_interval=0 ad_select=0"
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

Code: Select all

VLAN=yes
TYPE=Vlan
DEVICE=bond0.9
PHYSDEV=bond0
VLAN_ID=9
REORDER_HDR=0
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=vlan9
UUID=23bc80ce-592b-485a-9770-65dd58b6f572
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes

sorry for my English

stephenw
Posts: 15
Joined: 2015/02/19 17:46:27

Re: Vlan not starting up on Bond interface on boot

Post by stephenw » 2015/03/27 08:39:57

Hello

What kernel version do you have?

There was a restriction on creating VLANs on a Bond with no slaves, which caused an issue where the VLAN would fail to come up if the slaves were not yet up. This restriction was removed as discussed here: http://patchwork.ozlabs.org/patch/364984/

I believe this fix was released in kernel-3.10.0-229.el7

Post Reply