On Wed, Sep 23, 2015 at 01:58:37PM +0800, 渔舟 wrote:
>
> On 9/23/15 13:46, 渔舟 wrote:
> > On 9/23/15 10:35, Jesse Gross wrote:
> >> On Tue, Sep 22, 2015 at 7:28 PM, 渔舟 wrote:
> >>> On 9/23/15 09:35, Jesse Gross wrote:
> On Fri, Sep 18, 2015 at 7:30 PM, 渔舟 wrote:
> > Hi, all
> > Commun
On 9/23/15 13:46, 渔舟 wrote:
> On 9/23/15 10:35, Jesse Gross wrote:
>> On Tue, Sep 22, 2015 at 7:28 PM, 渔舟 wrote:
>>> On 9/23/15 09:35, Jesse Gross wrote:
On Fri, Sep 18, 2015 at 7:30 PM, 渔舟 wrote:
> Hi, all
> Communication failed happened sometimes (about fifty-fifty) with
> co
On 9/23/15 10:35, Jesse Gross wrote:
> On Tue, Sep 22, 2015 at 7:28 PM, 渔舟 wrote:
>> On 9/23/15 09:35, Jesse Gross wrote:
>>> On Fri, Sep 18, 2015 at 7:30 PM, 渔舟 wrote:
Hi, all
Communication failed happened sometimes (about fifty-fifty) with
combination of ovs
and linux nati
On Tue, Sep 22, 2015 at 7:28 PM, 渔舟 wrote:
>
> On 9/23/15 09:35, Jesse Gross wrote:
>> On Fri, Sep 18, 2015 at 7:30 PM, 渔舟 wrote:
>>> Hi, all
>>> Communication failed happened sometimes (about fifty-fifty) with
>>> combination of ovs
>>> and linux native bonding( 802.3ad mode), but if I use ovs
On 9/23/15 09:35, Jesse Gross wrote:
> On Fri, Sep 18, 2015 at 7:30 PM, 渔舟 wrote:
>> Hi, all
>> Communication failed happened sometimes (about fifty-fifty) with combination
>> of ovs
>> and linux native bonding( 802.3ad mode), but if I use ovs own
>> bonding(lacp=active) instead,
>> the failure
On Fri, Sep 18, 2015 at 7:30 PM, 渔舟 wrote:
> Hi, all
> Communication failed happened sometimes (about fifty-fifty) with combination
> of ovs
> and linux native bonding( 802.3ad mode), but if I use ovs own
> bonding(lacp=active) instead,
> the failure disappeared, any ideas?
>
> I read below post
Hi, all
Communication failed happened sometimes (about fifty-fifty) with combination of
ovs
and linux native bonding( 802.3ad mode), but if I use ovs own
bonding(lacp=active) instead,
the failure disappeared, any ideas?
I read below post, which mentioned that "it may not be possible to use the