On 3/26/21 1:14 AM, Moshe Levi wrote: > > >> -----Original Message----- >> From: Dumitru Ceara <dce...@redhat.com> >> Sent: Friday, March 26, 2021 12:58 AM >> To: Moshe Levi <mosh...@nvidia.com>; ovs-discuss@openvswitch.org >> Subject: Re: [ovs-discuss] [ovn] help with creating logical topology with l3 >> gateway >> >> External email: Use caution opening links or attachments >> >> >> On 3/25/21 10:50 PM, Moshe Levi wrote: >>> >>> >>>> -----Original Message----- >>>> From: Dumitru Ceara <dce...@redhat.com> >>>> Sent: Thursday, March 25, 2021 1:44 PM >>>> To: Moshe Levi <mosh...@nvidia.com>; ovs-discuss@openvswitch.org >>>> Subject: Re: [ovs-discuss] [ovn] help with creating logical topology >>>> with l3 gateway >>>> >>>> External email: Use caution opening links or attachments >>>> >>>> >>>> On 3/25/21 12:40 PM, Dumitru Ceara wrote: >>>>>> Also, to see exactly where the packet is dropped, please share the >>>>>> output of: >>>>>> >>>>>> inport=$(ovs-vsctl --bare --columns ofport list interface vm1) >>>>>> >>>> >> flow=40440000000340440000000108004500005417cd40004001b3980a00010264 >>>> 40 >>>>>> >>>> >> 00020800e1d35d0a0001c1635c6000000000d78905000000000010111213141516 >>>> 171 >>>>>> >> 8191a1b1c1d1e1f202122232425262728292a2b2c2d2e2f3031323334353637 >>>>> To "demystify" this a bit, I got the packet contents by running the >>>>> following command while ping was running from vm1: >>>>> >>>>> ip netns exec vm1 tcpdump -vvvnne -i vm1 -c1 -XX | ovs-tcpundump >>>>> >>>>>> ovs-appctl ofproto/trace br-int in_port=$in_port $flow | >>>>>> ovn-detrace >>>> >>>> And here's a typo, sorry, should be: >>>> >>>> ovs-appctl ofproto/trace br-int in_port=$inport $flow | ovn-detrace >>> Here is the output [1] >>> >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpast >>> >> ebin.ubuntu.com%2Fp%2FjDYz9Dfy2t%2F&data=04%7C01%7Cmoshele >> %40nvidi >>> >> a.com%7C960a360b887d4d8946ec08d8efe17a1b%7C43083d15727340c1b7db3 >> 9efd9c >>> >> cc17a%7C0%7C0%7C637523098980876494%7CUnknown%7CTWFpbGZsb3d8e >> yJWIjoiMC4 >>> >> wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&a >> mp;sda >>> >> ta=JuapJNoC0iQEQfmuQtAsh%2BqmqKNtYajgJtV%2FamT2jQo%3D&res >> erved=0 >>> >>> OVN 21.03 -> commit da028c72bdc7742b3065d1df95a3789fbc16b27a >>> OVS 2.15 -> commit d5dc16670ec95702058fccad253ed6d24ebd5329 >>> >> >> I think I know what the problem is (aside from the missing route). >> Is it possible that the node's chassis-id (OVS system-id) isn't >> 9a790be7-a876- >> 48a9-b7c5-1c45c6946dd4? >> >> In your the commands you shared you had: >> ovn-nbctl create Logical_Router name=gw-worker1 >> options:chassis=9a790be7-a876-48a9-b7c5-1c45c6946dd4 >> >> The chassis-id should correspond to the system-id OVS was started with on >> the node. You can retrieve this with: >> >> ovs-vsctl get open_vswitch . external_ids:system-id > Thanks with you command to get the chassis-id it works. I used the uuid from > ovn-sbctl list chassis. Shouldn't that work as well?
You need to use the "name" of the SB.Chassis record, not its uuid. For reference, section "Logical_Router TABLE", "options : chassis": https://www.ovn.org/support/dist-docs/ovn-nb.5.html "If set, indicates that the logical router in question is a Gate‐ way router (which is centralized) and resides in the set chas‐ sis. The same value is also used by ovn-controller to uniquely identify the chassis in the OVN deployment and comes from exter‐ nal_ids:system-id in the Open_vSwitch table of Open_vSwitch database." Regards, Dumitru _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
