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/NETVIRT-525 netvirt <p>Netvirt-ELAN service<br/> The ELAN data-path test failed with 100% packet loss in Sandbox.</p> <p>I have verified the flow table and it has entry to drop the packet. <br/> Log:<br/> <a href="https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-mitaka-upstream-transparent-boron/3" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-mitaka-upstream-transparent-boron/3</a></p> <p>In some build, When i do VM delete and recreate then the flow table updated with corresponding port and data-path works fine. <br/> Log:<br/> <a href="https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-mitaka-upstream-learn-boron/1" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-mitaka-upstream-learn-boron/1</a></p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-525

ELAN Datapath failed with 100% packet loss

Bug Resolved Won't Do P Govinda Rajulu Suvitha Balu Mon, 13 Mar 2017 09:02:50 +0000 Tue, 18 Apr 2017 11:50:34 +0000 Tue, 18 Apr 2017 11:50:34 +0000 Boron General 0 2 <p>This issue is fixed.</p> <p>code-review contains fix: <a href="https://git.opendaylight.org/gerrit/#/c/53588/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/53588/</a> </p> <p>Please test with the latest build.</p> <p>I have tested with latest boron and carbon build and seen the same issue.</p> <p>carbon log:<br/> <a href="https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-newton-upstream-learn-carbon/9" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-newton-upstream-learn-carbon/9</a> </p> <p>boron log:<br/> <a href="https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-newton-upstream-transparent-boron/1" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/sandbox/jenkins091/netvirt-csit-1node-openstack-newton-upstream-transparent-boron/1</a></p> <p>Hi,</p> <p>On the Carbon report:</p> <p>Here I see two tunnel interfaces are created b/w DPNs (like below) which is wrong. </p> { "destination-DPN": 123772809692053, "source-DPN": 49069236146780, "transport-type": "odl-interface:tunnel-type-vxlan", "tunnel-interface-names": [ "tuna8f4b6ca395", "tun231de31af6e" ] } <p>There should be only one tunnel interface exist b/w DPNs. Also out of which one tunnel interface doesn’t have any interface state created.<br/> Due to this, when ELAN queries tunnel interface name from ITM and it returns interface name which doesn’t have interface state. <br/> This leads to remote DMAC (51) programmed with drop action and Remote BC group is not updated.</p> <p>Can you make sure single tunnel interface exist between DPNs ?</p> <p>On the Boron report:</p> <p>There is ITM tunnel state up event is received b/w dpIds 18042706445918 and 83764721875373 at 2017-04-18 06:00:02,613 and ELAN is able to retrieve tunnel egress action properly till 2017-04-18 06:57:23,087. Suddenly it stopped working till 2017-04-18 07:07:40,801 which table 51 is programmed with drop action. </p> <p>Is tunnel got deleted during this period ?</p> <p>Please make sure ITM tunnels are configured correctly before running ELAN tests across DPNs if you are not using auto-tunnel configuration.</p> Development External issue ID 7961 External issue URL Rank 0|i01sc7: