Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2013244

Summary: Enable user to control dynamic_neigh_routers ovn option
Product: Red Hat OpenStack Reporter: anil venkata <vkommadi>
Component: python-networking-ovnAssignee: Lucas Alvares Gomes <lmartins>
Status: CLOSED ERRATA QA Contact: Slawek Kaplonski <skaplons>
Severity: high Docs Contact:
Priority: high    
Version: 16.2 (Train)CC: apevec, ekuris, jschluet, lhh, lmartins, majopela, scohen
Target Milestone: z4Keywords: Scale, TestBlocker, Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: python-networking-ovn-7.4.2-2.20220409154863.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-07 19:21:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description anil venkata 2021-10-12 12:43:38 UTC
Description of problem:
As per ovn-nb(5),

       options : dynamic_neigh_routers: optional string, either true or false
              If set to true, the router will resolve neighbor routers’ MAC addresses only by dynamic ARP/ND, instead of prepop‐
              ulating static mappings for all neighbor routers in the ARP/ND Resolution stage. This reduces number of flows, but
              requires ARP/ND messages to resolve the IP-MAC bindings when needed. It is false by default. It is recommended  to
              set to true when a large number of logical routers are connected to the same logical switch but most of them never
              need to send traffic between each other. By default, ovn-northd does not create mappings to NAT and load  balancer
              addresess. However, for NAT and load balancer addresses that have the add_route option added, ovn-northd will cre‐
              ate logical flows that map NAT and load balancer  IP  addresses  to  the  appropriate  MAC  address.  Setting  dy‐
              namic_neigh_routers to true will prevent the automatic creation of these logical flows.


setting dynamic_neigh_routers to true is recommended for scale scenarios to avoid logical flow explosion. Neutron needs to provide an option for the user to control this setting.

Comment 13 errata-xmlrpc 2022-12-07 19:21:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.4), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8794