[ovs-discuss] Problem with mac address learning.

[Krist van Besien]

Hi Alex,

No, this is an openstack installation, so, linux, ivm and openvswitch.
And the problem indeed was really due to the interfaces being in
promiscuous mode. I'll rebuild my networking node with this in mind.

Krist

On Fri, Oct 3, 2014 at 5:41 PM, Alex Wang <alexw at nicira.com> wrote:
> Hey Krist,
>
> are you using esx?  if so, do you add the two ports of the bond on the same
> switch in esx (or vsphere)?  the two ports should be added to two different
> switch~
>
> Thanks,
> Alex Wang,
>
> On Fri, Oct 3, 2014 at 2:44 AM, Krist van Besien <krist.vanbesien at gmail.com>
> wrote:
>>
>> Hi,
>>
>> It was indeed related to the interfaces being in promiscuous mode. I
>> managed to find the root cause, and have a workaround.
>>
>> On Fri, Oct 3, 2014 at 4:32 AM, Chris Bennett <chris at ceegeebee.com> wrote:
>> >> I'm running my LXC base & container on top of VMware ESX, and thus my
>> >> vSwitch
>> > has to be in promiscuous mode.  I'm seeing frames coming in on the
>> > uplink port
>> > (equiv to your port 1) with a source mac of that of the LXC container.
>> > That to
>> > me would explain why OVS's fdb shows port id 1 for those mac addresses.
>> >
>>
>> The networking hosts have two interfaces, which are bonded. This is
>> the cause of the ovswitch seeing arp requests also appearing on port
>> 1, and thus incorrectly learning where that mac address is.
>> I disabled on link, and the problem went away.
>>
>> However I need both those links for redundance. So now the question
>> has become how to use these two links, without creating arp loops.
>>
>> Any ideas there?
>>
>> Krist
>>
>> --
>> krist.vanbesien at gmail.com
>> krist at vanbesien.org
>> Bern, Switzerland
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> http://openvswitch.org/mailman/listinfo/discuss
>
>



-- 
krist.vanbesien at gmail.com
krist at vanbesien.org
Bern, Switzerland