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-726 OpenFlowPlugin <p>Using this distribution: <a href="https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.0-SNAPSHOT/distribution-karaf-0.5.0-20160706.150806-3364.zip" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.5.0-SNAPSHOT/distribution-karaf-0.5.0-20160706.150806-3364.zip</a></p> <p>Steps to reproduce bug:<br/> 1. Start cluster<br/> 2. Start mininet<br/> 3. Put flows on cluster via config ds<br/> 4. Mininet device should have correct flows installed<br/> 5. Put new flows (same as in step 3 but with changed action)<br/> 6. Changed flows are correctly in config, but flow-dump shows still old flows on device</p> <p>Operating System: Linux<br/> Platform: PC</p> OPNFLWPLUG-726

Flows are not updated on device on 3 node cluster

Bug Resolved Cannot Reproduce Bertrand Low Juraj Sebin Thu, 7 Jul 2016 13:06:46 +0000 Mon, 27 Sep 2021 09:01:51 +0000 Fri, 22 Jul 2016 22:16:52 +0000 General 0 5 <p>Attachment inventory-config.xml has been added with description: inventory config flows</p> <p>Attachment flow-dump.txt has been added with description: flow dump from device</p> <p>Hi juraj,</p> <p>Can you provide some more details about which version of openflowplugin and which design are you using ?</p> <p>Hi juraj,</p> <p>Can you provide some more details about which version of openflowplugin and which design are you using ?</p> <p>Hi juraj,</p> <p>Also do let us know whether you are using OFHA and are you provisioning from the leader/follower ?</p> <p>thanks</p> <p>Hi Anil/Shuva</p> <p>Openflowplugin version/design:<br/> I'm using default openflowplugin version which should be lithium. I'm not sure about exact openflowplugin version, but it should be one which has been integrated in distribution-karaf zip that I'm using (from 6.7.2015).</p> <p>Provisioning:<br/> I've tried both follower and leader and it seems to be happening in both cases.</p> <p>OFHA:<br/> I'm not familiar with this term, could you please provide more info?</p> <p>Thanks,<br/> Juraj</p> <p>Is the ofswitch connected to all the 3 instances of the controller or is 1 switch connected to 1 instance of the controller ?</p> <p>It's connected to all 3 instances</p> <p>Hi there,</p> <p>I'm unable to reproduce this bug with distribution-karaf-0.5.0-20160722.203805-3759</p> <p>I have a 3-node cluster and I'm able to push flows with changed action to the device.</p> <p>Here is the flow-dump with flows that have had their actions changed:</p> <p>root@mininet-vm:~# ovs-ofctl dump-flows s1 -O Openflow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=3.625s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.1 actions=dec_ttl<br/> cookie=0x2, duration=3.450s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.3 actions=dec_ttl<br/> cookie=0x1, duration=3.268s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.2 actions=dec_ttl<br/> cookie=0x3, duration=3.089s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.4 actions=dec_ttl<br/> cookie=0x4, duration=2.912s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.5 actions=dec_ttl<br/> root@mininet-vm:~# ovs-ofctl dump-flows s1 -O Openflow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=3.314s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.1 actions=drop<br/> cookie=0x2, duration=3.148s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.3 actions=drop<br/> cookie=0x1, duration=2.958s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.2 actions=drop<br/> cookie=0x3, duration=2.775s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.4 actions=drop<br/> cookie=0x4, duration=2.597s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.5 actions=drop<br/> root@mininet-vm:~# ovs-ofctl dump-flows s1 -O Openflow13<br/> OFPST_FLOW reply (OF1.3) (xid=0x2):<br/> cookie=0x0, duration=2.991s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.1 actions=FLOOD<br/> cookie=0x2, duration=2.828s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.3 actions=FLOOD<br/> cookie=0x1, duration=2.647s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.2 actions=FLOOD<br/> cookie=0x3, duration=2.471s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.4 actions=FLOOD<br/> cookie=0x4, duration=2.270s, table=0, n_packets=0, n_bytes=0, idle_timeout=65000, hard_timeout=65000, priority=2,ip,nw_dst=10.0.0.5 actions=FLOOD</p> <p>I noticed that perhaps you were trying to push a FLOOD action. Try using this configuration:</p> <p>&lt;action&gt;<br/> &lt;order&gt;0&lt;/order&gt;<br/> &lt;output-action&gt;<br/> &lt;output-node-connector&gt;FLOOD&lt;/output-node-connector&gt;<br/> &lt;max-length&gt;60&lt;/max-length&gt;<br/> &lt;/output-action&gt;<br/> &lt;/action&gt;</p> Development External issue ID 6171 External issue URL Rank 0|i032xj: