With options:dynamic_neigh_routers=true, a logical router does not install static ARP/ND entries in lr_in_arp_resolve for neighbor routers connected to the same logical switch. However, in OVN-IC deployments, router ports from other AZs are represented on the transit switch as LSPs of type "remote". These are not "router" LSPs, so northd treated them as regular VIFs and still installed a static entry for each of their addresses on every local router attached to the transit switch.
Since remote ports represent neighbor routers, skip the static ARP/ND entries for them when the local router has dynamic_neigh_routers enabled, and let them be resolved dynamically like local neighbor routers. This avoids flows proportional to the number of AZs/routers on large transit switches. Assisted-by: Claude Opus 5.5, Claude Code Signed-off-by: Lucas Vargas Dias <[email protected]> --- NEWS | 4 ++++ northd/northd.c | 17 +++++++++++++++ ovn-nb.xml | 7 ++++++ tests/ovn-northd.at | 52 +++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 80 insertions(+) diff --git a/NEWS b/NEWS index 6415fb973..7d99ce4b4 100644 --- a/NEWS +++ b/NEWS @@ -62,6 +62,10 @@ Post v26.09.0 table at startup; it defers its kernel route updates until the initial dump of the advertised routes of the local route-exchange datapaths is complete. + - The Logical_Router "options:dynamic_neigh_routers" option now also + applies to logical switch ports of type "remote" (e.g. ports on + OVN-IC transit switches), so no static ARP/ND mappings are created + for their addresses. OVN v26.09.0 - xxx xx xxxx -------------------------- diff --git a/northd/northd.c b/northd/northd.c index 750dd4d29..89edec0d8 100644 --- a/northd/northd.c +++ b/northd/northd.c @@ -16217,6 +16217,11 @@ build_arp_resolve_flows_for_lsp( * connects) and if the address in question is reachable from the * router port, add an ARP/ND entry in that router's pipeline. */ + /* Remote ports (OVN-IC transit switches) represent router ports in + * other AZs. Treat them as neighbor routers: skip the static + * ARP/ND entry when the local router has dynamic_neigh_routers. */ + bool is_remote = lsp_is_remote(op->nbsp); + for (size_t i = 0; i < op->n_lsp_addrs; i++) { const char *ea_s = op->lsp_addrs[i].ea_s; for (size_t j = 0; j < op->lsp_addrs[i].n_ipv4_addrs; j++) { @@ -16230,6 +16235,12 @@ build_arp_resolve_flows_for_lsp( continue; } + if (is_remote && peer->od->nbr && + smap_get_bool(&peer->od->nbr->options, + "dynamic_neigh_routers", false)) { + continue; + } + if (lrp_is_l3dgw(peer)) { const char *redirect_type = smap_get(&peer->nbrp->options, "redirect-type"); @@ -16268,6 +16279,12 @@ build_arp_resolve_flows_for_lsp( continue; } + if (is_remote && peer->od->nbr && + smap_get_bool(&peer->od->nbr->options, + "dynamic_neigh_routers", false)) { + continue; + } + if (!lrp_find_member_ip(peer, ip_s)) { continue; } diff --git a/ovn-nb.xml b/ovn-nb.xml index c69905a68..911b2bc3b 100644 --- a/ovn-nb.xml +++ b/ovn-nb.xml @@ -3452,6 +3452,13 @@ or <var>dynamic_neigh_routers</var> to <code>true</code> will prevent the automatic creation of these logical flows. </p> + <p> + This also applies to logical switch ports of type + <code>remote</code> (e.g. ports on OVN-IC transit switches that + represent router ports in other availability zones): no static + mappings are created for their addresses, and they are resolved + by dynamic ARP/ND instead. + </p> </column> <column name="options" key="always_learn_from_arp_request" type='{"type": "boolean"}'> <p> diff --git a/tests/ovn-northd.at b/tests/ovn-northd.at index d42ea34ae..3a8658050 100644 --- a/tests/ovn-northd.at +++ b/tests/ovn-northd.at @@ -25837,3 +25837,55 @@ AT_CHECK([ovn-sbctl lflow-list lr0 | grep "lr_in_policy[[^_]]" | ovn_strip_lflow OVN_CLEANUP_NORTHD AT_CLEANUP ]) + +OVN_FOR_EACH_NORTHD_NO_HV([ +AT_SETUP([dynamic_neigh_routers skips ARP resolve for remote LSPs]) +ovn_start + +dnl lr0 is connected to a transit switch "ts" that has a remote LSP +dnl (router port in another AZ) and a regular VIF. +check ovn-nbctl lr-add lr0 +check ovn-nbctl lrp-add lr0 lr0-ts 00:00:00:00:00:01 169.254.100.1/24 fd00::1/64 +check ovn-nbctl ls-add ts +check ovn-nbctl lsp-add-router-port ts ts-lr0 lr0-ts +check ovn-nbctl lsp-add ts remote1 \ + -- lsp-set-type remote1 remote \ + -- lsp-set-addresses remote1 "00:00:00:00:00:02 169.254.100.2 fd00::2" +check ovn-nbctl lsp-add ts vif1 \ + -- lsp-set-addresses vif1 "00:00:00:00:00:03 169.254.100.3 fd00::3" +check ovn-nbctl --wait=sb sync + +dnl Without the option, static entries exist for both ports. +AT_CHECK([ovn-sbctl lflow-list lr0 | grep lr_in_arp_resolve | \ + grep priority=100 | grep -E '::[[23]]|169\.254\.100\.[[23]]' | \ + ovn_strip_lflows], [0], [dnl + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && reg0 == 169.254.100.2), action=(eth.dst = 00:00:00:00:00:02; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && reg0 == 169.254.100.3), action=(eth.dst = 00:00:00:00:00:03; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && xxreg0 == fd00::2), action=(eth.dst = 00:00:00:00:00:02; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && xxreg0 == fd00::3), action=(eth.dst = 00:00:00:00:00:03; next;) +]) + +dnl With dynamic_neigh_routers, the remote LSP entries go away but the +dnl regular VIF entries are kept. +check ovn-nbctl --wait=sb set logical_router lr0 options:dynamic_neigh_routers=true +AT_CHECK([ovn-sbctl lflow-list lr0 | grep lr_in_arp_resolve | \ + grep priority=100 | grep -E '::[[23]]|169\.254\.100\.[[23]]' | \ + ovn_strip_lflows], [0], [dnl + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && reg0 == 169.254.100.3), action=(eth.dst = 00:00:00:00:00:03; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && xxreg0 == fd00::3), action=(eth.dst = 00:00:00:00:00:03; next;) +]) + +dnl Disabling the option brings the remote LSP entries back. +check ovn-nbctl --wait=sb set logical_router lr0 options:dynamic_neigh_routers=false +AT_CHECK([ovn-sbctl lflow-list lr0 | grep lr_in_arp_resolve | \ + grep priority=100 | grep -E '::[[23]]|169\.254\.100\.[[23]]' | \ + ovn_strip_lflows], [0], [dnl + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && reg0 == 169.254.100.2), action=(eth.dst = 00:00:00:00:00:02; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && reg0 == 169.254.100.3), action=(eth.dst = 00:00:00:00:00:03; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && xxreg0 == fd00::2), action=(eth.dst = 00:00:00:00:00:02; next;) + table=??(lr_in_arp_resolve ), priority=100 , match=(outport == "lr0-ts" && xxreg0 == fd00::3), action=(eth.dst = 00:00:00:00:00:03; next;) +]) + +OVN_CLEANUP_NORTHD +AT_CLEANUP +]) -- 2.43.0 -- _'Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas'._ * **'Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos'.* _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
