Is anybody using vlan trunking with network bonds? I can configure a network bond using 802.3ad on my 3.3.2 ovm environment, but when I try to use vlan interfaces with the bond, it stops working reliably. Symtoms are indicative of one port in the bond not working.
One thing I see when we have vlan trunking configured, is that the aggregator id of the two ports in the bond are not the same. Normally, the aggregator ids of the bond and slave ports should all be the same. Here is the contents of /proc/net/bonding/bond1 when trunking is configured. Also, there is no partner mac address.
Any ideas?
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 250
Up Delay (ms): 500
Down Delay (ms): 500
802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
Active Aggregator Info:
Aggregator ID: 2
Number of ports: 1
Actor Key: 17
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00
Slave Interface: em2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 4
Permanent HW addr: b0:83:fe:d5:56:50
Aggregator ID: 1
Slave queue ID: 0
Slave Interface: p3p2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 4
Permanent HW addr: 00:0e:1e:86:e7:32
Aggregator ID: 2
Slave queue ID: 0