[ovs-dev] [ovn] howto? L3 support in HW VTEP

Vladislav Odintsov odivlad at gmail.com
Tue Jul 13 18:03:55 UTC 2021


Hi Numan,

could you please look at my case if you have time? Earlier I’ve sent you NB DB dump.
Thanks in advance.

Regards,
Vladislav Odintsov

> On 1 Jul 2021, at 11:44, Vladislav Odintsov <odivlad at gmail.com> wrote:
> 
> I looked at the patch and couldn’t understand how to use it in my case.
> Can you clarify your idea please?
> 
> Regards,
> Vladislav Odintsov
> 
>> On 28 Jun 2021, at 23:34, Numan Siddique <numans at ovn.org <mailto:numans at ovn.org>> wrote:
>> 
>> On Fri, Jun 25, 2021 at 4:13 AM Vladislav Odintsov <odivlad at gmail.com <mailto:odivlad at gmail.com>> wrote:
>>> 
>>> Hi Numan,
>>> 
>>> did you have a chance to look at db dump?
>> 
>> Sorry.  I didn't get a chance.
>> 
>> Will this patch help your use case  ? -
>> https://patchwork.ozlabs.org/project/ovn/patch/9d24b588-9527-f7bc-7e39-b9f9d31954f6@oracle.com/ <https://patchwork.ozlabs.org/project/ovn/patch/9d24b588-9527-f7bc-7e39-b9f9d31954f6@oracle.com/>
>> 
>> Thanks
>> Numan
>> 
>>> 
>>> Regards,
>>> Vladislav Odintsov
>>> 
>>>> On 18 Jun 2021, at 23:34, Vladislav Odintsov <odivlad at gmail.com <mailto:odivlad at gmail.com>> wrote:
>>>> 
>>>> Sorry, there was a typo.
>>>> Sure, VM has IP 192.168.1.2/24 and host 192.168.2.2/24.
>>>> 
>>>> [root at ovn-1 ~]# ovn-nbctl show
>>>> switch 8e1e2828-67b2-432b-8b2e-088f312dab5d (switch1)
>>>>    port switch1-uplink
>>>>        type: router
>>>>        router-port: switch1-gw
>>>>    port switch1-vm
>>>>        addresses: ["00:00:00:00:00:01 192.168.1.2"]
>>>> switch 42127732-2b67-483e-9768-777eae4d9cbe (switch2)
>>>>    port switch2-uplink
>>>>        type: router
>>>>        router-port: switch2-gw
>>>>    port switch2-vtep
>>>>        type: vtep
>>>>        addresses: ["unknown"]
>>>> router b11e7ebe-0dde-4a9f-b006-37c177f38bae (router1)
>>>>    port switch1-gw
>>>>        mac: "00:00:00:00:00:f1"
>>>>        networks: ["192.168.1.1/24"]
>>>>    port switch2-gw
>>>>        mac: "00:00:00:00:00:f2"      # <-- this mac address I created as a Ucast_Macs_Remote record in VTEP DB.
>>>>        networks: ["192.168.2.1/24”]  #  When physical host sends traffic to its chassis, routing between sw1 and sw2 works.
>>>>        gateway chassis: [9721a9e9-73ef-4a9a-8a50-afa84811c6ef]
>>>> 
>>>> 
>>>> OVN NB DB is in attachment.
>>>> 
>>>> <test.db>
>>>> 
>>>> Regards,
>>>> Vladislav Odintsov
>>>> 
>>>>> On 18 Jun 2021, at 21:27, Numan Siddique <numans at ovn.org <mailto:numans at ovn.org> <mailto:numans at ovn.org <mailto:numans at ovn.org>>> wrote:
>>>>> 
>>>>> On Fri, Jun 18, 2021 at 7:42 AM Vladislav Odintsov <odivlad at gmail.com <mailto:odivlad at gmail.com> <mailto:odivlad at gmail.com <mailto:odivlad at gmail.com>>> wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>> I’m trying to implement support for L3 routing between OVN and HW VTEP devices.
>>>>>> In my setup I use Cumulus Linux-managed Mellanox SN2000 switches.
>>>>>> Current L2 functionality in this setup works well: ovn-controller-vtep and a
>>>>>> small python service on the switch (which installs necessary mcast_macs entries
>>>>>> in switch fdb, since Cumulus Linux vtep support is limited to service_node
>>>>>> replication mode).
>>>>>> 
>>>>>> My logical topology for L3 setup:
>>>>>> 
>>>>>> 2 logical_switches connected to same logical_router:
>>>>>> Net1: 192.168.1.0/24, gw ip (lrouter): 192.168.1.1, VM 192.168.1.2
>>>>>> Net2: 192.168.2.0/24, gw ip (lrouter): 192.168.2.1, Physical host 192.168.2.2
>>>>>> 
>>>>>> Net1 has attached logical_switch_port with type vtep. In Net2 there is a VM
>>>>>> (192.168.2.2/24), which needs ip connectivity to physical host (192.168.1.2/24)
>>>>>> connected to HW VTEP Mellanox switch over vtep lport from Net1.
>>>>> 
>>>>> I'm a little confused.  Above you said the physical host has IP
>>>>> 192.168.2.2 but you also
>>>>> mentioned there is a VM (192.168.2.2/24).
>>>>> 
>>>>> So in Net2 is there a logical switch port with IP 192.168.2.2 (and the
>>>>> corresponding VIF)
>>>>> and it wants to ping to a physical host 192.168.1.2 ?
>>>>> 
>>>>> Maybe you can share the ovn north db to better understand the problem ?
>>>>> 
>>>>> Thanks
>>>>> Numan
>>>>> 
>>>>> 
>>>>>> 
>>>>>> For Net1’s LRP (192.168.1.1) I’ve created chassis_redirect port_binding to some
>>>>>> Chassis and patched controller-step code so that such CR LRP’s MAC is also
>>>>>> added to Ucast_Macs_Remote vtep table.
>>>>>> Traffic from ovn-host to vtep (192.168.1.2 to 192.168.2.2) passes well, but in
>>>>>> reverse direction physical server sends to all ovn-hosts ARP request Who has
>>>>>> 192.168.2.1? tell 192.168.2.2. But no answer. If I manually configure arp on
>>>>>> this physical server, connectivity between VM and physical host works well!
>>>>>> 
>>>>>> Now I’m stuck with arp resolution for LRP from VTEP lport from OVN side. Can
>>>>>> somebody give an idea how to make ovn-controllers answer such ARP request?
>>>>>> 
>>>>>> Thanks.
>>>>>> 
>>>>>> Regards,
>>>>>> Vladislav Odintsov
>>>>>> 
>>>>>> _______________________________________________
>>>>>> dev mailing list
>>>>>> dev at openvswitch.org <mailto:dev at openvswitch.org> <mailto:dev at openvswitch.org <mailto:dev at openvswitch.org>>
>>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev <https://mail.openvswitch.org/mailman/listinfo/ovs-dev> <https://mail.openvswitch.org/mailman/listinfo/ovs-dev <https://mail.openvswitch.org/mailman/listinfo/ovs-dev>>
>>>>> _______________________________________________
>>>>> dev mailing list
>>>>> dev at openvswitch.org <mailto:dev at openvswitch.org> <mailto:dev at openvswitch.org <mailto:dev at openvswitch.org>>
>>>>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev <https://mail.openvswitch.org/mailman/listinfo/ovs-dev> <https://mail.openvswitch.org/mailman/listinfo/ovs-dev <https://mail.openvswitch.org/mailman/listinfo/ovs-dev>>
>>> 
>>> _______________________________________________
>>> dev mailing list
>>> dev at openvswitch.org <mailto:dev at openvswitch.org>
>>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev <https://mail.openvswitch.org/mailman/listinfo/ovs-dev>



More information about the dev mailing list