On Tue, Jun 4, 2013 at 8:56 AM, B-o-B De Mars <mr.chew.baka at gmail.com> wrote: > I would like to take advantage of both nics on the server & would like to > setup LACP (bonding mode 4) + the Bridge. I am no stranger to LACP, and all > my servers with more than 2 nics are setup this way. No problem. That should work well. > The problem I am having is getting the bonded links to work with the bridge. > Does anyone know how to do this? I currently have the bond 4 working, and > can confirm on the switch that LACP partnership is active & up. I cannot > ping/access the guests anymore, and the guests (using the bridge) cannot > access anything. Sounds like the bridge is misconfigured. > ifcfg-bond0 > DEVICE=bond0 > USERCTL=no > BOOTPROTO=none > ONBOOT=yes > BONDING_OPTS="miimon=100 mode=4" > IPV6INIT=no > IPADDR=192.168.12.240 > NETMASK=255.255.255.0 > GATEWAY=192.168.12.1 > DNS1=192.168.12.35 > > Up to this point bonding works, I can ping the host, and the host can access > outbound. It's been awhile since I set up KVM bridging, but it looks like you're awfully close. I think what you need to do is configure the KVM bridge to use bond0 as its one and only interface. Leave bond0 as a layer 2 interface and add the IP to br0 once br0 is configured against bond0. > Some of the docs online mention I need to setup a tagged vlan on the switch > for this config. Is this true, do I really need a vlan? I doubt it. Typically LACP is set up for trunking, hence you would be running multiple VLANs across the aggregate. By the sounds of it, you are not using any VLAN trunking (just an access port) so that wouldn't apply. Good luck, Brian