Hello,
thanks for your advices but i'm still stuck.
At the beginning, everything is OK :
$ sudo ovs-dpctl dump-flows sw0
in_port(3),eth(src=08:00:27:9b:24:12,dst=08:00:27:77:b1:55),eth_type(0x0800),ipv4(src=10.0.0.1,dst=10.0.0.2,proto=1,tos=0,ttl=128,frag=no),icmp(type=0,code=0),
packets:119,
Well, based on the output you've given, the bond looks healthy.
You'll have to figure out where precisely the packets are getting
dropped. Typically I do this by using ovs-dpctl dump-flows to figure
out what the datapath is a given packet. If you're still stuck, you
may want to check out the ovs-
Le 26/07/2012 23:21, Ethan Jackson a écrit :
Please keep replies on the list.
Ooops sorry !
Thank you for your help. What I tried since your last message :
This my startup configuration (VMs halted) :
-
killall ovsdb-server
killall ovs-vswitchd
for tap in `seq 0 3`; do ip tuntap del m
Do I understand correctly that you're creating a lacp bond within a
hypervisor going from a guest to DOM0? That's a bit strange . . .
> - play with ovs-appctl bond/set-active-slave and change active slave
set-active-slave shouldn't affect LACP bonds. If you want to trigger
a failover you will n
Hello,
I'm a perfect newbie with Openvswtich, read the reference manual and try
to configure LACP Failover with 2 VMs under VirtualBox :
Host : Fedora 17 (kernel 3.4.6-2) + Openvswitch 1.4.0
Guests : Windows 2008R2 with 2 NICs Intel Pro 1000 MT and Linux Debian 6
with 1 NIC Intel Pro 1000 MT
