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/OPNFLWPLUG-736 OpenFlowPlugin <p>When i was trying to add a flow in to mininet using MASTER branch of openflowplugin project, i couldn't see flow in operational data store with correct flow id &amp; but seen on mininet.</p> <p>features installed :- feature:install odl-openflowplugin-flow-services-ui</p> <p>pastebin link operational data -&gt; <a href="http://pastebin.com/aPnx0AzF" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/aPnx0AzF</a></p> <p>pastebin link config dats -&gt; <a href="http://pastebin.com/gKATfvBJ" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/gKATfvBJ</a></p> <p>flows on mininet </p> <p>mininet&gt; sh ovs-ofctl dump-flows s1 -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=224.055s, table=0, n_packets=0, n_bytes=0, priority=3,ip,nw_dst=3.3.3.0 actions=dec_ttl<br/> cookie=0x0, duration=224.055s, table=0, n_packets=0, n_bytes=0, priority=400,ipv6,ipv6_src=fe80:2acf:e9ff:fe21::/64 actions=dec_ttl<br/> cookie=0x0, duration=224.057s, table=0, n_packets=0, n_bytes=0, priority=1,ip,nw_dst=1.1.1.0/24 actions=dec_ttl<br/> cookie=0x0, duration=224.054s, table=0, n_packets=0, n_bytes=0, priority=2,ip,nw_dst=2.2.0.0/16 actions=dec_ttl</p> <p>same result observed with </p> <p>features installed :- feature:install odl-openflowplugin-flow-services-ui &amp; feature:install odl-openflowplugin-flow-services-rest-he</p> <p>pastebin link operational data -&gt; <a href="http://pastebin.com/siXbim12" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/siXbim12</a></p> <p>pastebin link config dats -&gt; <a href="http://pastebin.com/1nWDzLx9" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/1nWDzLx9</a></p> <p>mininet&gt; sh ovs-ofctl dump-flows s1 -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=92.022s, table=0, n_packets=0, n_bytes=0, priority=3,ip,nw_dst=3.3.3.0 actions=dec_ttl<br/> cookie=0x0, duration=141.246s, table=0, n_packets=0, n_bytes=0, priority=1,ip,nw_dst=1.1.1.0/24 actions=dec_ttl<br/> cookie=0x0, duration=130.726s, table=0, n_packets=0, n_bytes=0, priority=400,ipv6,ipv6_src=fe80:2acf:e9ff:fe21::/64 actions=dec_ttl<br/> cookie=0x0, duration=84.443s, table=0, n_packets=0, n_bytes=0, priority=2,ip,nw_dst=2.2.0.0/16 actions=dec_ttl</p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-736

Flow doesn't show up in operational data with correct flow id

Bug Resolved Done Sai MarapaReddy Sai MarapaReddy Fri, 22 Jul 2016 22:35:23 +0000 Mon, 27 Sep 2021 09:01:51 +0000 Thu, 11 Aug 2016 17:17:19 +0000 General 0 6 <p>Flow with arbitrary mask works in stable/beryllium but not master</p> <p>Input in config -&gt; <a href="http://pastebin.com/Tq6finM5" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/Tq6finM5</a></p> <p>Output in operational -&gt; <a href="http://pastebin.com/vqpnea8v" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/vqpnea8v</a></p> <p>mininet output </p> <p>mininet&gt; sh ovs-ofctl dump-flows s1 -O OpenFlow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=321.38s, table=0, n_packets=0, n_bytes=0, priority=40,ip,nw_src=40.40.40.0,nw_dst=40.0.40.0/255.0.255.0 actions=dec_ttl</p> <p>All the above mentioned flows works in stable/beryllium as expected</p> <p>I just tested it now with the current code on master branch.</p> <p>Hi Andrej,</p> <p>I've tested this with master branch builds as early as distribution-karaf-0.5.0-20160727.205650-3885.tar.gz</p> <p>I noticed that the flows in the config datastore that Sai provided resulted in OFPBMC_BAD_WILDCARDS errors on a version 2.5.0 OVS Switch. After modifying the flow (see below*), I was able to get the flow installed on the switch and confirm that the operational flow ID indeed matched the config datastore flow ID. So, I could not reproduce this bug as Sai was seeing. Were you able to reproduce it?</p> <ul> <li>this would be a successful arbitrary bitmask config:<br/> &lt;ipv4-source-address-no-mask&gt;40.40.40.0&lt;/ipv4-source-address-no-mask&gt;<br/> &lt;ipv4-destination-address-no-mask&gt;40.0.40.0&lt;/ipv4-destination-address-no-mask&gt;<br/> &lt;ipv4-destination-arbitrary-bitmask&gt;255.0.255.0&lt;/ipv4-destination-arbitrary-bitmask&gt;<br/> &lt;ipv4-source-arbitrary-bitmask&gt;255.255.255.255&lt;/ipv4-source-arbitrary-bitmask&gt;</li> </ul> <p>Hi Andrej / Bertrand,</p> <p>I re-tested with latest master (which includes Anil's Patch)</p> <p>Seems Ipv4 arbitrary bit mask is ok, but some cases of Ipv6 arbitrary bit mask doesn't work.</p> <p>Please check the flow Id s 440,441,447 in config, there are not correctly reflected in operational. <br/> Where as Flow Id 473 is correctly represented. <br/> In case of stable/beryllium these work as expected. i.e., they show up in operational.</p> <p>config :- <a href="http://pastebin.com/raw/DaKk89H7" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/raw/DaKk89H7</a></p> <p>operational :- <a href="http://pastebin.com/raw/UXZC0iMp" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/raw/UXZC0iMp</a></p> <p>Hence the bug still exists. Please let me know any clarification.</p> <p>Following flow in Ipv4 doesn't work</p> <p>Config :-<a href="http://pastebin.com/6xce2rgU" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/6xce2rgU</a></p> <p>operational :- <a href="http://pastebin.com/uXCYB8BE" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/uXCYB8BE</a></p> <p>Hi guys, <br/> (didn't send details yesterday)<br/> The issue with incorrect flow id (i.e. alien id) is similar to <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-722" title="Some Flows not found in DeviceFlowRegistry" class="issue-link" data-issue-key="OPNFLWPLUG-722"><del>OPNFLWPLUG-722</del></a> and there are some improvements after <a href="https://git.opendaylight.org/gerrit/#/c/42510/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/42510/</a>.</p> <p>I also tested it with your first configuration Sai and for OVS 2.3.0 all flows are pushed to device and they show up in operational with correct flow id. (However if you would like to setup these flows in OVS 2.4.0 or 2.5.0 - as Bertrand mentioned, device will return error cause of incorrect masks. Newer versions are more clever.)</p> <p>But it seems that problem is if *address-no-mask + *arbitrary-bitmask fileds are used. Will try to check it.</p> <p>The problem was really with *address-no-mask + *arbitrary-bitmask fields not comparing properly with ipv4/6-source from device. I created patch that will fix this problem here: <a href="https://git.opendaylight.org/gerrit/#/c/43233/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/43233/</a></p> <p>Sai, could you please test it, it should work now.<br/> (if u r using OVS 2.4.0+ you need to edit address or mask in the last config u sent again, otherwise device will probably reject the flow)</p> <p>Hi Andrej / Tomas,</p> <p>With ovs version 2.3 following flows fail to show up in operational.</p> <p><a href="http://pastebin.com/8CYJt4Vx" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/8CYJt4Vx</a></p> <p>This was not issue related to alien id actually, but fixed here:</p> <p>master: <a href="https://git.opendaylight.org/gerrit/#/c/43641/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/43641/</a><br/> boron: <a href="https://git.opendaylight.org/gerrit/#/c/43643/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/43643/</a><br/> beryllium: <a href="https://git.opendaylight.org/gerrit/#/c/43647/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/43647/</a></p> <p>Thank you Andrej. <br/> Once the above three patches are merged, this bug can be closed.</p> <p>Guys, everything is fine and I am going to merge it. Just wonder why this errors weren't catch by JUNIT test. Please add/upgrade test to prevent further mistakes.</p> <p>With Andrej, we additionally replaced regexp, that was converting IPv6 adress to its short notation to proper byte array related method, because that regex was not shortening the longest groups of zeros, as it should.</p> <p>Also, Andrej tested it on OVS 2.3 and 2.4, and everything was working as it was supposed to (on 2.3, everything passed, and on 2.4, when there was bad wildcard, it was properly rejected).</p> <p>Patches are merged already, if its ok please close this bug.</p> <p>Jozef</p> Development External issue ID 6259 External issue URL Priority Rank 0|i032zr: