[PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

[Fabio Fantoni]

Il 03/01/2015 18:47, Gurucharan Shetty ha scritto:
>> I removed eth0 and eth1 definitions.
>> Seems that ovs configuration add them but network is still not working.
>> I tried also ifdown and ifup of xenbr0 but not solves the problem, don't
>> show errors and "ovs-vsctl show" output always the same result (screen in
>> attachment)
> The 'ovs-vsctl show' o/p hints at correct configuration of bond. As
> Gustavo suggested, look to see if eth0, eth1, bond0 are all admin up
> (it should automatically be up). Have you used ovs bonds before
> (without using 'interfaces'?). Have you made sure that 'eth0' and
> 'eth1' are connected to physical switches that support 802.3ad with
> successful  LACP  negotiation? If you are just experimenting, you can
> also look at 'balance-slb' and 'active-backup'. Have you read the
> section 'Bonding Configuration' in 'man ovs-vswitchd.conf.db'?
>

Thanks for your reply.
Seems that problem was LACP configuration in the switch, the model is 
HP1910V-48G, it should support LACP automatic and manually but I had to 
configure it manually on the 2 switch ports to have xenbr0 working.
Is strange, for what I remember on older switch (also it was good 
managed switch) and also older ovs (I don't know if can be ovs 
regression) one year ago or more I not configured it in the switch but 
was automatically.
Is correct configuring LACP manually in switch or ovs should configure 
LACP automatically instead?

Thanks for any reply and sorry for my bad english.