That's a fair point, Jesse, and thanks for your feedback.

Yes, a lot more than what I itemized was changed on the system from a
software version perspective. The systems configs were constant and no
physical switch changes were made between the working and non-working
states, for what that's worth. There was also one other test performed
before the larger upgrade, which was an isolated upgrade to OVS 1.10
(built from source). There was no difference in the problem behaviour,
which would lead me away from the issue being on the OVS-related.

A little background on my purposes, I'm putting up an OpenStack cluster
for the first time. As such, it's the first time not only to work with
their networking paradigms, but also my first time to use OVS. From what
I can tell, many folks in the OpenStack community are slow to adopt
quantum (and OVS), because it's just not that well understood yet. The
help I've found for OpenStack doesn't ever discuss bonding, and the
simpler configurations were functional. As noob it's sometime difficult
to know whether the issue is fundamentally one's understanding or the
components.

Still, I'm convinced there's something going on in that particular stack
(limited quite possibly to Ubuntu's flavour of it) and I thought you all
might like to know. That and maybe another web searcher will find it
useful when they come across the email archive. :)

Best,

- John


On 06/27/2013 10:07 AM, Jesse Gross wrote:
> Nobody has reported such an incompatibility before and it's hard to
> reach that conclusion because you've changed the version of nearly
> every piece of software on the machine. If I had to take a guess, I
> suspect that your upstream switch is being confused by the bonding you
> are doing.
>
> On Thu, Jun 27, 2013 at 8:12 AM, John Eckhardt
> <[email protected]> wrote:
>> This appears to be an incompatibility between OpenVswitch 1.4 and Linux
>> kernel version 3.2, and / or possibly bridge-utils.
>>
>> I upgraded from Ubuntu 12.04 (with standard packages) to Ubuntu 13.04 (with
>> standard packages) and everything started working.
>>
>> === 12.04 vs 13.04 ===
>>
>> 12.04
>>
>> kernel - 3.2.0-48-generic
>> openvswitch - 1.4.0-1ubuntu1.5
>> ifenslave - 1.1.0-19ubuntu5
>> bridge-utils - 1.5-2ubuntu7
>> vlan - 1.9-3ubuntu6
>>
>> 13.04
>>
>> kernel - 3.8.0-25-generic
>> openvswitch - 1.9.0-0ubuntu1
>> ifenslave - 1.1.0-20ubuntu3
>> bridge-utils - 1.5-6ubuntu1
>> vlan - 1.9-3ubuntu8
>>
>> Given this, it looks like the incompatibility is somewhere between
>> OpenVswitch and the kernel, or possibly bridge-utils.
>>
>>
>> On 06/26/2013 12:28 PM, John Eckhardt wrote:
>>
>>
>> I'm trying to understand why a bridge I've created, and added an IP address
>> to, isn't reliably reaching it's network.
>>
>> root@vwc-s35:~# ping -I br-2064v 10.26.95.254
>> PING 10.26.95.254 (10.26.95.254) from 10.26.75.35 br-2064v: 56(84) bytes of
>> data.
>> 64 bytes from 10.26.95.254: icmp_req=1 ttl=255 time=0.735 ms
>> 64 bytes from 10.26.95.254: icmp_req=2 ttl=255 time=0.236 ms
>> 64 bytes from 10.26.95.254: icmp_req=3 ttl=255 time=0.226 ms
>> 64 bytes from 10.26.95.254: icmp_req=46 ttl=255 time=2.31 ms
>> 64 bytes from 10.26.95.254: icmp_req=47 ttl=255 time=0.248 ms
>> 64 bytes from 10.26.95.254: icmp_req=48 ttl=255 time=0.255 ms
>> 64 bytes from 10.26.95.254: icmp_req=49 ttl=255 time=0.683 ms
>> 64 bytes from 10.26.95.254: icmp_req=50 ttl=255 time=0.343 ms
>> 64 bytes from 10.26.95.254: icmp_req=51 ttl=255 time=3.03 ms
>> 64 bytes from 10.26.95.254: icmp_req=93 ttl=255 time=0.414 ms
>> 64 bytes from 10.26.95.254: icmp_req=94 ttl=255 time=0.279 ms
>> 64 bytes from 10.26.95.254: icmp_req=95 ttl=255 time=0.604 ms
>> 64 bytes from 10.26.95.254: icmp_req=96 ttl=255 time=0.293 ms
>> 64 bytes from 10.26.95.254: icmp_req=97 ttl=255 time=0.292 ms
>>
>> The bridge's only port is a OS (linux) bonded interface.
>>
>> root@vwc-s35:~# ovs-vsctl show
>> 0a2349d6-77fa-40c6-b71f-989e3f28b740
>>     Bridge br-ex
>>         Port br-ex
>>             Interface br-ex
>>                 type: internal
>>     Bridge br-int
>>         Port br-int
>>             Interface br-int
>>                 type: internal
>>     Bridge "br-2064v"
>>         Port "br-2064v"
>>             Interface "br-2064v"
>>                 type: internal
>>         Port "Bond10G"
>>             Interface "Bond10G"
>>     ovs_version: "1.10.0"
>>
>> Where can I start with this?
>>
>> Many thanks in advance,
>>
>> - John
>>
>> === More System Details ===
>>
>> - Running "Ubuntu 12.04.2 LTS"
>> - Was originally running the ubuntu-packaged OVS version 1.4, which had the
>> same issue.
>> - Upgraded to OVS version 1.10 to see if it would help, same behavior.
>> - Snippets from interfaces follow:
>>
>>
>> ## Interface eth0 ##
>> auto eth0
>> iface eth0 inet manual
>>     bond-master Bond10G
>>
>> ## Interface eth1 ##
>> auto eth1
>> iface eth1 inet manual
>>     bond-master Bond10G
>>
>> ...
>>
>> ## Interface Bond10G ##
>> auto Bond10G
>> iface Bond10G inet manual
>>     bond-downdelay 200
>>     bond-fail_over_mac none
>>     bond-miimon 100
>>     bond-mode balance-alb
>>     bond-slaves none
>>     bond-updelay 200
>>     mtu 9000
>>     up ifconfig $IFACE 0.0.0.0 up
>>     up ip link set $IFACE promisc on
>>     down ip link set $IFACE promisc off
>>     down ifconfig $IFACE down
>>
>> ...
>>
>> auto br-2064v
>> iface br-2064v inet static
>>     address 10.26.75.35
>>     up GATEWAY=10.26.95.254; ip route add 10.26.64.0/255.255.224.0 dev
>> Bond10G src 10.26.75.35 table Bond10G; ip route add default via 10.26.95.254
>> dev Bond10G src 10.26.75.35 table Bond10G; ip rule add from 10.26.75.35
>> table Bond10G
>>     netmask 255.255.224.0
>>     network 10.26.64.0
>>     dns-nameservers 8.8.8.8
>>     dns-search at.solidfire.net
>>
>>
>>
>> --
>>
>> John Eckhardt
>> Automation Engineer, SolidFire Inc.
>> e: [email protected]
>> c: 720.244.5262
>> Advancing the way the world uses the cloud™
>>
>>
>>
>> --
>>
>> John Eckhardt
>> Automation Engineer, SolidFire Inc.
>> e: [email protected]
>> c: 720.244.5262
>> Advancing the way the world uses the cloud™
>>
>> _______________________________________________
>> discuss mailing list
>> [email protected]
>> http://openvswitch.org/mailman/listinfo/discuss
>>


-- 

John Eckhardt
Automation Engineer, *SolidFire Inc*.
e: [email protected] <mailto:[email protected]>
c: 720.244.5262
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>™
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to