Hi, There is a patchset under review [1] for this functionality. You can try this out locally or wait it to be accepted in upstream.
1: https://patchwork.ozlabs.org/project/ovn/list/?series=410010 regards, Vladislav Odintsov -----Original Message----- From: discuss <ovs-discuss-boun...@openvswitch.org> on behalf of ab via discuss <ovs-discuss@openvswitch.org> Reply to: ab <a...@hostvds.com> Date: Monday, 24 June 2024 at 17:46 To: "ovs-discuss@openvswitch.org" <ovs-discuss@openvswitch.org> Subject: [ovs-discuss] Incorrect max_tunid Hello In continue the thread ovs-discuss@openvswitch.org <https://www.mail-archive.com/<a href=>/msg08817.html">ovs-discuss@openvswitch.org <https://www.mail-archive.com/<a href=>/msg08817.html">https://www.mail-archive.com/ovs-discuss@openvswitch.org/msg08817.html We want to make a patch so that the OVN return the correct number of max_tunid. We are trying to add a new value "ovn-vxlan-for-hw-vtep-only" in the chassis->other_config section. If this value is true, then the max_tunid value will be 16 million, if false - max_tunid=4095. The condition will be met if the value of ovn-vxlan-for-hw-vtep-only=true on any of the chassis. Please tell us, will the patch be correct? Can we add such a feature this way? _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
