I had a similar problem a while back.
I was trying to bring the vlans up in a similar way to what you are
doing, and i had the following configuration:
auto vlan50
iface vlan50 inet dhcp
bond-mode 802.3ad
bond-miimon 100
xmit_hash_policy layer2+3
lacp_rate slow
slaves all
auto vlan60
iface vlan60 inet dhcp
bond-mode 802.3ad
bond-miimon 100
xmit_hash_policy layer2+3
lacp_rate slow
slaves all
That would create havoc with my network configuration, because it would
try and create a bond using all interfaces including the vlans when it
brought up vlan 50 and then fail when trying to bring up vlan60 because
the slaves where allready bonded in vlan 50.
It seems the correct way to use bonding and vlans is to:
# Create the Link Aggregation without assigning it an address and defining the
interfaces to enslave
auto bond0
iface bond0 inet manual
bond-mode 802.3ad
bond-miimon 100
xmit_hash_policy layer2+3
lacp_rate slow
slaves eth0 eth1 eth2 eth3
# Create vlan50
auto vlan50
iface vlan50 inet dhcp
vlan_raw_device bond0
# Create vlan60
auto vlan60
iface vlan60 inet dhcp
vlan_raw_device bond0
Could you please try the above configuration adapted to your needs and
see if it works?
--
can not add vlans to a bond network device
https://bugs.launchpad.net/bugs/352384
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
