On Thu, Feb 10, 2011 at 09:35:55PM +0800, Jerry Ma wrote: > I am using OVS in RHEL54. Actually I created a bonding device using mode 4, > which is 802.3ad, with 2 interfaces enslaved to it. I configured it to be > part of the bridge by modifying the xend-config.sxp, Everything is OK, I got > a bridge device named bond0, and a bonding device pbond0 attached to it. The > network works well then. > > After that, I am using OVS bridge to take place the Linux bridge, but even > if I attached pbond0 to OVS bridge, network is down. I cannot ping any host, > with error is Destination Unreachable. > > I am not sure if mode 4 bonding is OK with OVS. Hope somebody could help me
I believe that Linux LACP bonds should be OK with OVS. However the latest version of OVS on the "master" branch also has built-in support LACP-based bonding that you could use as an alternative. We can probably help you debug your issue. A good place to start would be the information requested in the REPORTING-BUGS file. You have told us the first set of information, but the second and third sets may allow us to give you some better advice: ---------------------------------------------------------------------- Reporting Bugs in Open vSwitch ============================== We are eager to hear from users about problems that they have encountered with Open vSwitch. This file documents how best to report bugs so as to ensure that they can be fixed as quickly as possible. Please report bugs by sending email to [email protected]. The most important parts of your bug report are the following: * What you did that make the problem appear. * What you expected to happen. * What actually happened. Please also include the following information: * The Open vSwitch version number (as output by "ovs-vswitchd --version"). * The Git commit number (as output by "git rev-parse HEAD"), if you built from a Git snapshot. * Any local patches or changes you have applied (if any). The following are also handy sometimes: * The kernel version on which Open vSwitch is running (from /proc/version) and the distribution and version number of your OS (e.g. "Centos 5.0"). * The contents of the vswitchd configuration database (usually /etc/ovs-vswitchd.conf.db). * The output of "ovs-dpctl show". * If you have Open vSwitch configured to connect to an OpenFlow controller, the output of "ovs-ofctl show <bridge>" for each <bridge> configured in the vswitchd configuration database. * A fix or workaround, if you have one. * Any other information that you think might be relevant. [email protected] is a public mailing list, to which anyone can subscribe, so please do not include confidential information in your bug report. Contact ------- [email protected] http://openvswitch.org/ _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
