Well, actually this is exactly the same problem as: http://openvswitch.org/pipermail/discuss/2011-September/005768.html
No answers in that thread, so I was wondering if there was any progress on this topic. Br, Frido On Tue, Jan 31, 2012 at 10:40 AM, Frido Roose <[email protected]> wrote: > Yep, > > # lsmod | grep openvswitch > openvswitch_mod 82997 2 brcompat_mod > > # lsmod | egrep "openvswitch_mod|brcompat_mod" > brcompat_mod 5713 0 > openvswitch_mod 82997 2 brcompat_mod > > # grep COMPAT /etc/sysconfig/openvswitch > BRCOMPAT=yes > > # ps auxw | grep brcompat > root 23731 0.0 0.0 40016 616 pts/0 S< 10:26 0:00 > ovs-brcompatd: monitoring pid 23732 (healthy) > > > root 23732 0.0 0.0 40020 876 ? S<s 10:26 0:00 > ovs-brcompatd -vANY:CONSOLE:EMER -vANY:SYSLOG:ERR -vANY:FILE:INFO > --no-chdir --log-file=/var/log/openvswitch/ovs-brcompatd.log > --pidfile=/var/run/openvswitch/ovs-brcompatd.pid --detach --monitor > > > The /sys/class/net/vbr314/bridge/ directory actually exists, despite the > error messages. The content differs a bit from a standard bridge > configuration in Linux (it lacks some files): > server1# ls /sys/class/net/vbr314/bridge/ | sort >/tmp/vbr314.ovs > server2# ls /sys/class/net/vbr314/bridge/ | sort >/tmp/vbr314.bridge > # diff /tmp/vbr314.ovs /tmp/vbr314.bridge > 2a3 > > flush > 5a7,8 > > hash_elasticity > > hash_max > 8a12,21 > > multicast_last_member_count > > multicast_last_member_interval > > multicast_membership_interval > > multicast_querier_interval > > multicast_query_interval > > multicast_query_response_interval > > multicast_router > > multicast_snooping > > multicast_startup_query_count > > multicast_startup_query_interval > > Br, > Frido > > > On Tue, Jan 31, 2012 at 10:30 AM, Justin Pettit <[email protected]>wrote: > >> I assume you have the kernel module "brcompat_mod.ko" loaded? >> >> --Justin >> >> >> On Jan 31, 2012, at 1:21 AM, Frido Roose wrote: >> >> > Hello, >> > >> > I'm currently trying openvswitch in a KVM environment on CentOS 6.2, >> and I'm having a problem with the compatibility mode when running >> ovs-brcompatd. >> > >> > # ovs-vsctl add-br vbr314 >> > # brctl show >> > bridge name bridge id STP enabled interfaces >> > vbr314 /sys/class/net/vbr314/bridge: No such file or >> directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > /sys/class/net/vbr314/bridge: No such file or directory >> > 0000.cade601c144d no >> > >> > I've read somewhere on the net that the bridge tools in RHEL 6.x are >> too recent. Are there any workarounds, or is an update on this planned for >> a coming release? >> > Btw, downgrading to 5.x is not an option for us. >> > >> > Best regards, >> > Frido Roose >> > _______________________________________________ >> > discuss mailing list >> > [email protected] >> > http://openvswitch.org/mailman/listinfo/discuss >> >> >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
