https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-309 ovsdb <p>I am analyzing ARP responder feature in ODL using openstack.<br/> Am using one control and 2 compute nodes.<br/> Created two networks (tenant1 and tenant2)</p> <p>While Adding router interface with tenant1 , arp flows are installed both control and compute nodes as expected for DHCP port and default gateway.</p> <p>And then, if I added router interface with tenant2, in control node arp flows are installed as expected, but, in compute nodes teanant1 default gateway IP is overwritten with teanant2 default gateway IP.</p> <p>Please find below dump flows:</p> <p>Added Router interface with tenant1 (10.0.0.0/24)</p> <p>Control node :</p> <p> cookie=0x0, duration=496.642s, table=0, n_packets=3, n_bytes=258, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=76.476s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x412,arp_tpa=10.0.0.2,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:a4:7b:03</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ea47b03-&gt;NXM_NX_ARP_SHA[],load:0xa000002-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=45.164s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x400,arp_tpa=20.0.0.2,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:3c:f1:d5</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163e3cf1d5-&gt;NXM_NX_ARP_SHA[],load:0x14000002-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=2.998s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x412,arp_tpa=10.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:a4:bf:1b</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ea4bf1b-&gt;NXM_NX_ARP_SHA[],load:0xa000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=496.642s, table=20, n_packets=16, n_bytes=1296, priority=0 actions=goto_table:30</p> <p>Compute1:</p> <p> cookie=0x0, duration=314.362s, table=0, n_packets=10, n_bytes=788, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=8.498s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x412,arp_tpa=10.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:a4:bf:1b</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ea4bf1b-&gt;NXM_NX_ARP_SHA[],load:0xa000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=314.362s, table=20, n_packets=10, n_bytes=788, priority=0 actions=goto_table:30</p> <p>Compute2:</p> <p> cookie=0x0, duration=313.912s, table=0, n_packets=10, n_bytes=788, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=14.214s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x412,arp_tpa=10.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:a4:bf:1b</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ea4bf1b-&gt;NXM_NX_ARP_SHA[],load:0xa000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=313.912s, table=20, n_packets=10, n_bytes=788, priority=0 actions=goto_table:30</p> <p>Added Router interface with tenant2 (20.0.0.0/24)</p> <p>Control:</p> <p> cookie=0x0, duration=591.999s, table=0, n_packets=3, n_bytes=258, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=140.521s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x400,arp_tpa=20.0.0.2,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:3c:f1:d5</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163e3cf1d5-&gt;NXM_NX_ARP_SHA[],load:0x14000002-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=171.833s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x412,arp_tpa=10.0.0.2,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:a4:7b:03</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ea47b03-&gt;NXM_NX_ARP_SHA[],load:0xa000002-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=98.355s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x412,arp_tpa=10.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:a4:bf:1b</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ea4bf1b-&gt;NXM_NX_ARP_SHA[],load:0xa000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=8.945s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x400,arp_tpa=20.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:e6:97:f1</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ee697f1-&gt;NXM_NX_ARP_SHA[],load:0x14000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=591.999s, table=20, n_packets=16, n_bytes=1296, priority=0 actions=goto_table:30</p> <p>Compute1:</p> <p> cookie=0x0, duration=427.876s, table=0, n_packets=10, n_bytes=788, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=32.892s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x400,arp_tpa=20.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:e6:97:f1</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ee697f1-&gt;NXM_NX_ARP_SHA[],load:0x14000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=427.876s, table=20, n_packets=10, n_bytes=788, priority=0 actions=goto_table:30</p> <p>Compute2:</p> <p> cookie=0x0, duration=450.695s, table=0, n_packets=10, n_bytes=788, priority=0 actions=goto_table:20<br/> cookie=0x0, duration=61.874s, table=20, n_packets=0, n_bytes=0, priority=1024,arp,tun_id=0x400,arp_tpa=20.0.0.1,arp_op=1 actions=move:NXM_OF_ETH_SRC[]<del>&gt;NXM_OF_ETH_DST[],set_field:fa:16:3e:e6:97:f1</del>&gt;eth_src,load:0x2-&gt;NXM_OF_ARP_OP[],move:NXM_NX_ARP_SHA[]<del>&gt;NXM_NX_ARP_THA[],move:NXM_OF_ARP_SPA[]</del>&gt;NXM_OF_ARP_TPA[],load:0xfa163ee697f1-&gt;NXM_NX_ARP_SHA[],load:0x14000001-&gt;NXM_OF_ARP_SPA[],IN_PORT<br/> cookie=0x0, duration=450.695s, table=20, n_packets=10, n_bytes=788, priority=0 actions=goto_table:30</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-309

Arp flows are not getting installed properly in compute nodes

Bug Resolved Done Oded Shvartz Hari Prasidh Fri, 26 Feb 2016 10:57:53 +0000 Mon, 30 Oct 2017 15:36:33 +0000 Mon, 21 Mar 2016 21:48:08 +0000 unspecified openstack.net-virt 0 3 <p>Attachment karaf_logs.zip has been added with description: karaf_logs</p> <p>just a wild guess is that net-virt is using the overlapping flow names, so when it tries to install the flow for tenant 2, it generates the same flow name and end up modifying the existing flow rather then installing new flow.</p> <p>This issue related to the fact that before we creates ARP responder rules we validate that the rules are needed on the specific node and if not we delete it :</p> <p>DistributedArpService:</p> <p>// Arp rule is only needed when segmentation exists in the given node (<a href="https://jira.opendaylight.org/browse/OVSDB-235" title="distributed arp in old l3 for ovsdb should not install rules for arp unless tenant network exists in the compute node" class="issue-link" data-issue-key="OVSDB-235"><del>OVSDB-235</del></a>).<br/> boolean arpNeeded = tenantNetworkManager.isTenantNetworkPresentInNode(node, providerSegmentationId);<br/> final Action actionForNode = arpNeeded ? actionToPerform : Action.DELETE; <br/> ...</p> <p>Once we will have the network on the node (first VM will be created) the ARP responder rules will be created (for the DHCP port and for the router interface).</p> <p>Now the question is if we want to fix it by not having the new rule as well ?</p> <p>(In reply to Oded Shvartz from comment #2)<br/> &gt; This issue related to the fact that before we creates ARP responder rules we<br/> &gt; validate that the rules are needed on the specific node and if not we delete<br/> &gt; it :<br/> &gt; <br/> &gt; DistributedArpService:<br/> &gt; <br/> &gt; // Arp rule is only needed when segmentation exists in the given node (bug<br/> &gt; 4752).<br/> &gt; boolean arpNeeded = tenantNetworkManager.isTenantNetworkPresentInNode(node,<br/> &gt; providerSegmentationId);<br/> &gt; final Action actionForNode = arpNeeded ? actionToPerform : Action.DELETE; <br/> &gt; ...<br/> &gt; <br/> &gt; Once we will have the network on the node (first VM will be created) the ARP<br/> &gt; responder rules will be created (for the DHCP port and for the router<br/> &gt; interface).<br/> &gt; <br/> &gt; <br/> &gt; Now the question is if we want to fix it by not having the new rule as well ?</p> <p>So after more debugging I found why the new rule (after adding the second interface to the router) was not deleted like the first interface.</p> <p>After calling the distributedArpService.handlePortEvent (where we delete all the rules that are not needed to a specific node) we then calling the neutronL3Adapter.handleNeutronPortEvent and there we are not checking if the rule is needed, because we assume that ARP responder rules for router interface are needed always :</p> <p>// Enable ARP responder by default, because router interface needs to be responded always.<br/> distributedArpService.programStaticRuleStage1(dpid, destinationSegmentationId, macAddress, ipStr, actionForNode);</p> <p>From functionality perspective I don't think we need it (I hope I'm not missing something here), because once we will have the first VM for this network we will create it, but I think we should be more consistent and to decide if we want to create those rules or not in both places.</p> <p>Hi Oded,</p> <p>Assume we have 2 networks(tenat1 and tenant2) and 2 Vm instances in control node, one instance in compute1 and one instance in compute2,<br/> Control node Vms<br/> VM1(10.0.0.3)<br/> VM2(20.0.0.3)</p> <p>Compute1 node Vm<br/> VM3(10.0.0.4)</p> <p>Compute2 node Vm<br/> VM4(20.0.0.4)</p> <p>now, if we are trying to ping VM4(20.0.0.4) to VM1(10.0.0.3). If compute2 not having Arp flows for default gateway ip, then the Arp request will be broad casted to all nodes .</p> <p>So I think by default arp responder should be enable for router interface.</p> <p>(In reply to hari prasad from comment #4)<br/> &gt; Hi Oded,<br/> &gt; <br/> &gt; Assume we have 2 networks(tenat1 and tenant2) and 2 Vm instances in control<br/> &gt; node, one instance in compute1 and one instance in compute2,<br/> &gt; Control node Vms<br/> &gt; VM1(10.0.0.3)<br/> &gt; VM2(20.0.0.3)<br/> &gt; <br/> &gt; Compute1 node Vm<br/> &gt; VM3(10.0.0.4)<br/> &gt; <br/> &gt; Compute2 node Vm<br/> &gt; VM4(20.0.0.4)<br/> &gt; <br/> &gt; now, if we are trying to ping VM4(20.0.0.4) to VM1(10.0.0.3). If compute2<br/> &gt; not having Arp flows for default gateway ip, then the Arp request will be<br/> &gt; broad casted to all nodes .<br/> &gt; <br/> &gt; So I think by default arp responder should be enable for router interface.</p> <p>Hi Hari,</p> <p>I think that when VM4(20.0.0.4) will try to ping VM1(10.0.0.3) it will send ARP request to find the default gateway on network 20.0.0.0 and we will have the arp responder rule for it, because it will be added once you created the VM (VM4).</p> <p>VM4 will send the packet to the default gateway (OVS) and OVS will do the routing without sending ARP request. You can look on table 70 which will add the relevant mac for the requested IP (10.0.0.4 in your case).</p> <p>Please let me know what do you think.</p> <p>be: <a href="https://git.opendaylight.org/gerrit/#/c/36268/1" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/36268/1</a><br/> master: <a href="https://git.opendaylight.org/gerrit/#/c/36231/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/36231/</a></p> Development External issue ID 5435 External issue URL Rank 0|i021xr: