<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >+1 to a very successful open and shut case of the local community helping the local community with the appropriate result of the OP giving the final rundown of the working solution. <div><br></div><div>I obviously have nothing cogent to add to this thread otherwise, just happy thoughts.</div><div><br></div><div><br></div><div><br></div><br><br><br>-------- Original message --------<br>From: B-o-B De Mars <mr.chew.baka@gmail.com> <br>Date: <br>To: tclug-list@mn-linux.org <br>Subject: Re: [tclug-list] Centos - KVM + LACP (Mode 4 bonding) + Bridge <br> <br><br>On 6/4/2013 11:50 AM, Brian Wall wrote::<br><br>Thanks Brian! I was able to get it working.<br><br>> Sounds like the bridge is misconfigured.<br><br>This was the problem.<br><br>> It's been awhile since I set up KVM bridging, but it looks like you're<br>> awfully close. I think what you need to do is configure the KVM<br>> bridge to use bond0 as its one and only interface. Leave bond0 as a<br>> layer 2 interface and add the IP to br0 once br0 is configured against<br>> bond0.<br><br>Layer 2 did the trick, and adding the BRIDGE setting to the bond0 config.<br><br>> I doubt it. Typically LACP is set up for trunking, hence you would be<br>> running multiple VLANs across the aggregate. By the sounds of it, you<br>> are not using any VLAN trunking (just an access port) so that wouldn't<br>> apply.<br><br>Agreed. I deleted the vlan from the switch, and removed all VLAN <br>references from the config files. It ended up being extremely easy. I <br>think I was just over thinking things (plus the lack of decent <br>documentation for this setup).<br><br>Here are the config files for the LACP (2 nics) + Bridge setup for KVM <br>in case anyone else needs help with this type of setup (Centos).<br><br> ifcfg-eth0<br>DEVICE=eth0<br>BOOTPROTO=none<br>ONBOOT=yes<br>MASTER=bond0<br>SLAVE=yes<br>USERCTL=no<br><br> ifcfg-eth1<br>DEVICE=eth1<br>BOOTPROTO=none<br>ONBOOT=yes<br>MASTER=bond0<br>SLAVE=yes<br>USERCTL=no<br><br> ifcfg-bond0<br>DEVICE=bond0<br>USERCTL=no<br>BOOTPROTO=none<br>ONBOOT=yes<br>BONDING_OPTS="miimon=100 mode=4"<br>BRIDGE=br0<br><br> ifcfg-br0<br>DEVICE="br0"<br>NM_CONTROLLED="yes"<br>ONBOOT=yes<br>TYPE=Bridge<br>BOOTPROTO=none<br>IPADDR=192.168.12.240<br>PREFIX=24<br>GATEWAY=192.168.12.1<br>DNS1=192.168.12.35<br>DNS2=192.168.11.10<br>DEFROUTE=yes<br>IPV4_FAILURE_FATAL=yes<br>IPV6INIT=no<br>NAME="System br0"<br><br>Restarted the network:<br><br>Bringing up loopback interface: [ OK ]<br>Bringing up interface bond0: [ OK ]<br>Bringing up interface br0: [ OK ]<br><br>Check the switch to make sure LACP still active:<br><br>PORT LACP TRUNK PORT LACP LACP<br>NUMB ENABLED GROUP STATUS PARTNER STATUS<br>---- ------- ------- ------- ------- -------<br>3 Active Trk9 Up Yes Success<br>4 Active Trk9 Up Yes Success<br><br>Was able to ping the host & guests again. Fantastic!<br><br>Have a great day everyone!<br><br>Mr. B-o-B<br>_______________________________________________<br>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>tclug-list@mn-linux.org<br>http://mailman.mn-linux.org/mailman/listinfo/tclug-list<br></body>