When I turn "ovs stp_enable" up, the physical switch just disabled one of the ethernet port because of network loop, so what is the difference between "ovs lacp" and legacy lacp method?
Does the ovs drop the LACPDUs because of unaware of the bonding strategy? BR, Ryan 2013/4/23 Ryan Young <ryanyoung.so...@gmail.com> > Hi, > Sorry for the unprofessional behavior. I setup LACP Bonding following the > steps below: > > 1. Modify the configuration files for bond0,eth2,eth3 to enable lacp > bonding: > ################# > DEVICE="bond0" > BOOTPROTO="static" > ONBOOT="yes" > TYPE="ethernet" > IPADDR=192.168.234.2 > NETMASK=255.255.255.0 > BONDING_OPTS="miimon=100 mode=4 xmit_hash_policy=2" > ################## > DEVICE=eth2 > BOOTPROTO=none > TYPE="Ethernet" > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > ################## > DEVICE=eth3 > BOOTPROTO=none > TYPE="Ethernet" > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > ################### > > 2. Setup openvswitch and attach bond0 to ovs bridge: > #ifconfig > bond0 Link encap:Ethernet HWaddr 00:26:B9:52:3C:E9 > UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 > RX packets:87 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:21622 (21.1 KiB) TX bytes:3328 (3.2 KiB) > br0 Link encap:Ethernet HWaddr 00:26:B9:52:3C:E9 > inet addr:192.168.234.3 Bcast:192.168.234.255 > Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:24 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2505 (2.4 KiB) TX bytes:0 (0.0 b) > eth2 Link encap:Ethernet HWaddr 00:26:B9:52:3C:E9 > UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:32 Memory:da000000-da012800 > eth3 Link encap:Ethernet HWaddr 00:26:B9:52:3C:E9 > UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 > RX packets:87 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:21622 (21.1 KiB) TX bytes:3328 (3.2 KiB) > Interrupt:42 Memory:dc000000-dc012800 > ############################### > #ovs-vsctl show > 01ae1e95-9739-4c84-88e8-4eb2a2187ba0 > Bridge "br0" > Port "bond0" > Interface "bond0" > Port "br0" > Interface "br0" > type: internal > > After the configuration I found my network not stable. My ssh session > would have no response every 30s. Which I guess the legacy LACP method is > incompatible with ovs. If I changed the mode to active-backup, the network > works normally. > > Any suggestion would be appreciated. > > BR, > Ryan > > > > 2013/4/23 Ben Pfaff <b...@nicira.com> > >> Please keep questions on the mailing list. This is the only reply >> you'll get off-list. >> >> It doesn't make any sense to me. You're doing something wrong, but you >> haven't provided any information that would allow me to guess what. >> >> On Tue, Apr 23, 2013 at 01:33:17PM +0800, Ryan Young wrote: >> > Hi Ben?? >> > Any suggestion about my question? >> > Thanks. >> > >> > BR, >> > Ryan >> > >> > ---------- Forwarded message ---------- >> > From: Ryan Young <ryanyoung.so...@gmail.com> >> > Date: 2013/4/21 >> > Subject: Bonding issues with ovs >> > To: discuss@openvswitch.org >> > >> > >> > Hi, >> > Recently I am trying to using ovs together with bonding ethernet >> > ports(eth0,eth1) in LACP mode. The ethernet ports were bonded(bond0) >> before >> > the ovs was setup with configuring >> "/net/sysconfig/network-script/ifcfg-*", >> > and after I set up the openvswitch I just attached bond0 to the ovs >> bridge. >> > This works normally in active-backup mode. But when I changed the >> bonding >> > mode to lacp, the network looks instable as every 30s my ssh console >> lost >> > control. Any issues regarding to this problem? Is it incompatible >> between >> > ovs and the legacy bonding method? >> > >> > BR, >> > Ryan >> > >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
