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-1397 netvirt <p>The test randomly fails across the three vms.</p> <p><a href="https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-pike-upstream-stateful-itm-direct-tunnels-oxygen/21/" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-pike-upstream-stateful-itm-direct-tunnels-oxygen/21/</a></p> <p><a href="https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-itm-direct-tunnels-fluorine/26/robot/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/netvirt-csit/job/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-itm-direct-tunnels-fluorine/26/robot/</a></p> NETVIRT-1397

SNAT - UDP connection to External Gateway From SNAT VM Instance fails in itm-direct-tunnels jobs

Bug Medium Resolved Done Chetan Arakere Gowdru Sam Hague csit:failures Tue, 7 Aug 2018 19:08:31 +0000 Wed, 19 Sep 2018 12:41:20 +0000 Wed, 19 Sep 2018 12:41:19 +0000 Fluorine-SR1 natservice 0 6 <p>Hi Edwin/Hema,</p> <p> </p> <p>I tried to narrow down this issue are following are the observation.</p> <p> </p> <p>Ref: <a href="https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-gate-stateful-itm-direct-tunnels-fluorine/1/robot-plugin/log_03_external_network.html.gz#s1-t19" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-gate-stateful-itm-direct-tunnels-fluorine/1/robot-plugin/log_03_external_network.html.gz#s1-t19</a></p> <p> </p> <ol> <li>An UDP packet is sent from Non-Napt Switch and enter via Tunnel-interface -tunaad8f9c7a1b. <b>Note here the lport been set with value 2</b></li> </ol> <p>cookie=0x8000001, duration=2756.820s, table=0, n_packets=6223, n_bytes=583936, priority=5,in_port=2 <b>actions=write_metadata:0x20000000001</b>/0xfffff0000000001,goto_table:36</p> <p> </p> <ol> <li>Now this packet entered NAT pipeline and been punted to ODL for programming SNAT flows.</li> <li>While sending packet the packet back to pipeline, using lport tag, we query the <b>operational/odl-interface-meta:if-indexes-interface-map</b> DS to get the interface name and found wrong interface name.</li> </ol> { "if-index": 2, "interface-name": "66664030340515:br-physnet1-pa:trunk"} <p> </p> <ol> <li>As a result, the packet is sent back to wrong dpn/interface(66664030340515:br-physnet1-pa) instead of sending back to tunnel port(tunaad8f9c7a1b).</li> <li>NAT first attempts to get the value from the above DS and if not found, will try to fetch from the packet. Since, in this case, if found an interface-name for a given lporttag, it sent to wrong interface(br-physnet1-pa) instead of sending to tunnel interface.</li> </ol> <p> </p> <p>Question: Why the table 0-&gt;36 setting the lporttag with value 2 which is not valid for tunnel interface - tunaad8f9c7a1b ?</p> <p> </p> <p>Thanks,</p> <p>Chetan</p> <p>Hi Chetan,</p> <p>  When you are using ITM direct tunnels,,all tunnel related information is stored by ITM and not interface manager. If you are referring to lport tag for a tunnel interface, then you should refer to <b>operational/odl-itm-meta:if-indexes-tunnel-map.</b></p> <p>The interface corresponding to the lport that you found in interface manager’s ifindexes map is that of vm interfaces and not tunnel interface.</p> <p>Regards,</p> <p>Hema</p> <p>Hi Hema,</p> <p> </p> <p>Thanks for the input.</p> <p> </p> <p>Is the if-index used for the tunnel-interface and other interface is not unique across these two DS(<b>if-indexes-tunnel-map/</b> <b>if-indexes-interface-map</b>) ??</p> <p> </p> <p>Thanks,</p> <p>Chetan</p> <p>Hi Chetan,</p> <p>  Yes, ifIndex has to be unique across tunnel and VM interfaces. In downstream ITM uses the same ID POOL as interface manager. This was not up-streamed correctly. I will raise a patch for this. Thanks for pointing this.</p> <p>Thanks,</p> <p>Hema</p> Development Rank 0|i03hpz: