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-462 netvirt <p>When auto tunnel mode is enabled (default for netvirt, currently), there are some issues when L2GW and L2GW connection are configured. Usually, what I see is there will not be a tunnel between the TOR and the remote TEP (dump vtep db).</p> <p>If I delete the automatically created Transport Zones in ITM via restconf, and then create the L2GW and L2GW connection, the tunnel between the TOR and remote TEP will be created.</p> <p>This issue has also been observed and repored by Tomer Pearl in the OVSDB mailing list.</p> <p>One workaround that has been mentioned (I have not tried it yet) is to disable auto tunnel creation in netvirt config file.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-462

L2GW tunnel(s) not created when auto tunnel mode is enabled

Bug Medium Resolved Cannot Reproduce Akash Sahu Victor Pickard Mon, 6 Feb 2017 18:12:54 +0000 Thu, 3 May 2018 14:45:06 +0000 Thu, 5 Apr 2018 23:30:44 +0000 Boron General 0 1 <p>Email on ovsdb-dev, from Daya, about how this works.</p> <p>Hi pearl,<br/> First word of caution - I am not sure if this is tested with netvirt autoconfig tunnel creation mode, or works with the same.<br/> So, the assumption is that a transport zone is available, with a bunch of ovs nodes, which are already fully meshed.<br/> Given this,when the l2gw create commands comes through, netivirt will build tunnels from each ovs endpt in the TZ (or other hwvtep endpts) to the new l2gw device. Netvirt will also populate all the remote TEPs in the physical locator table of the hwvtep, to enable it to build its own tunnels as and when needed.</p> <p>Can you try the following –<br/> Switch off tunnel autocreation, use REST aPI to create TZ with all OVS, and then see if u face any issues.<br/> Use the netvirt autoconfig mode, but create the neutron network first, which will trigger creation of the TZ with OVS switches upfront, then add the l2gw API.</p> <p>If we know this is the issue, (and it may be different from the exception you are seeing below), we can update the l2gw code as follows in case the netvirt auto0config mode is enabled –<br/> It should not build tunnels as part of l2gw create operations. When l2gw conn-create comes through, it needs to look up the corresponding TZ, and add the hwvtep into this tz as an external endpt, this will enable tunnels from all ovs’s in that tz to the hwvtep, netvirt should also publish only the subset of physical locators in that tz onto the hwvtep.</p> <p>Thanks,<br/> daya</p> Development External issue ID 7743 External issue URL Rank 0|i01ry7: