[OPNFLWPLUG-726] Flows are not updated on device on 3 node cluster Created: 07/Jul/16  Updated: 27/Sep/21  Resolved: 22/Jul/16

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Juraj Sebin Assignee: Bertrand Low
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC


Attachments: Text File flow-dump.txt     File inventory-config.xml    
External issue ID: 6171

 Description   

Using this distribution: 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

Steps to reproduce bug:
1. Start cluster
2. Start mininet
3. Put flows on cluster via config ds
4. Mininet device should have correct flows installed
5. Put new flows (same as in step 3 but with changed action)
6. Changed flows are correctly in config, but flow-dump shows still old flows on device



 Comments   
Comment by Juraj Sebin [ 07/Jul/16 ]

Attachment inventory-config.xml has been added with description: inventory config flows

Comment by Juraj Sebin [ 07/Jul/16 ]

Attachment flow-dump.txt has been added with description: flow dump from device

Comment by Anil Vishnoi [ 08/Jul/16 ]

Hi juraj,

Can you provide some more details about which version of openflowplugin and which design are you using ?

Comment by Anil Vishnoi [ 08/Jul/16 ]

Hi juraj,

Can you provide some more details about which version of openflowplugin and which design are you using ?

Comment by Shuva Jyoti Kar [ 10/Jul/16 ]

Hi juraj,

Also do let us know whether you are using OFHA and are you provisioning from the leader/follower ?

thanks

Comment by Juraj Sebin [ 11/Jul/16 ]

Hi Anil/Shuva

Openflowplugin version/design:
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).

Provisioning:
I've tried both follower and leader and it seems to be happening in both cases.

OFHA:
I'm not familiar with this term, could you please provide more info?

Thanks,
Juraj

Comment by Shuva Jyoti Kar [ 11/Jul/16 ]

Is the ofswitch connected to all the 3 instances of the controller or is 1 switch connected to 1 instance of the controller ?

Comment by Juraj Sebin [ 11/Jul/16 ]

It's connected to all 3 instances

Comment by Bertrand Low [ 22/Jul/16 ]

Hi there,

I'm unable to reproduce this bug with distribution-karaf-0.5.0-20160722.203805-3759

I have a 3-node cluster and I'm able to push flows with changed action to the device.

Here is the flow-dump with flows that have had their actions changed:

root@mininet-vm:~# ovs-ofctl dump-flows s1 -O Openflow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
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
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
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
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
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
root@mininet-vm:~# ovs-ofctl dump-flows s1 -O Openflow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
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
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
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
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
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
root@mininet-vm:~# ovs-ofctl dump-flows s1 -O Openflow13
OFPST_FLOW reply (OF1.3) (xid=0x2):
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
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
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
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
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

Comment by Bertrand Low [ 22/Jul/16 ]

I noticed that perhaps you were trying to push a FLOOD action. Try using this configuration:

<action>
<order>0</order>
<output-action>
<output-node-connector>FLOOD</output-node-connector>
<max-length>60</max-length>
</output-action>
</action>

Generated at Wed Feb 07 20:33:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.