[OPNFLWPLUG-541] multiple reboot of ovs switch, not showing flows in operational data storage. Created: 27/Aug/15  Updated: 27/Sep/21  Resolved: 30/Jan/16

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

Type: Bug
Reporter: Anpukarasi Muthukumaran Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: Other


External issue ID: 4204

 Description   

No OVS flows found in operational data storage of controller, after doing multiple reboot of ovs switch, minimum of 10 times

I have connected 1 # css and 10 ovs (mininet) switches.

Configured flows for
40 # flows to css switch
50 # flows to mininet #1 switch
50 # flows to mininet #2 nd switch

Did multiple reboot on mininet switches say minimum 10 times, then checked the operational data storage, mininet flows are not found there. Please check the below details and let me know if i can raise TR for this in ODL

mininet:
==========

mininet@mininet-vm:~/mininet\> sudo mn --controller=remote,ip=10.183.254.252 --topo linear,10 --switch ovsk,protocols=OpenFlow13

      • Creating network
      • Adding controller
      • Adding hosts:
        h1 h2 h3 h4 h5 h6 h7 h8 h9 h10
      • Adding switches:
        have protcol params!
        s1 have protcol params!
        s2 have protcol params!
        s3 have protcol params!
        s4 have protcol params!
        s5 have protcol params!
        s6 have protcol params!
        s7 have protcol params!
        s8 have protcol params!
        s9 have protcol params!
        s10
      • Adding links:
        (h1, s1) (h2, s2) (h3, s3) (h4, s4) (h5, s5) (h6, s6) (h7, s7) (h8, s8) (h9, s9) (h10, s10) (s1, s2) (s2, s3) (s3, s4) (s4, s5) (s5, s6) (s6, s7) (s7, s8) (s8, s9) (s9, s10)
      • Configuring hosts
        h1 h2 h3 h4 h5 h6 h7 h8 h9 h10
      • Starting controller
      • Starting 10 switches
        s1 OVSswitch opts: protocols=OpenFlow13
        s2 OVSswitch opts: protocols=OpenFlow13
        s3 OVSswitch opts: protocols=OpenFlow13
        s4 OVSswitch opts: protocols=OpenFlow13
        s5 OVSswitch opts: protocols=OpenFlow13
        s6 OVSswitch opts: protocols=OpenFlow13
        s7 OVSswitch opts: protocols=OpenFlow13
        s8 OVSswitch opts: protocols=OpenFlow13
        s9 OVSswitch opts: protocols=OpenFlow13
        s10 OVSswitch opts: protocols=OpenFlow13
      • Starting CLI:
        mininet>
        mininet>
        mininet>
        mininet>

controller output:
==================
mininet@mininet-vm:~/test\> ./inventory_crawler.py --host 10.183.254.252 --auth --datastore operational
Crawling 'http://10.183.254.252:8181/restconf/operational/opendaylight-inventory:nodes'

Totals:
Nodes: 11
Reported flows: 41
Found flows: 41
mininet@mininet-vm:~/test\>
mininet@mininet-vm:~/test\> ./inventory_crawler.py --host 10.183.254.252 --auth --datastore config
Crawling 'http://10.183.254.252:8181/restconf/config/opendaylight-inventory:nodes'

Totals:
Nodes: 3
Reported flows: 0
Found flows: 141
mininet@mininet-vm:~/test\>

mininet output:
===============

mininet@mininet-vm:~/integration/test/tools/odl-mdsal-clustering-tests/clustering-performance-test/ovs-scripts\> ./get-total-found.sh
Switch s1: 50 flows
Switch s2: 50 flows
Switch s3: 0 flows
Switch s4: 0 flows
Switch s5: 0 flows
Switch s6: 0 flows
Switch s7: 0 flows
Switch s8: 0 flows
Switch s9: 0 flows
Switch s10: 0 flows

Total: 100



 Comments   
Comment by Abhijit Kumbhare [ 30/Jan/16 ]

Can you please test with the latest code? This should be fixed with flow reconciliation.

Comment by Shuva Jyoti Kar [ 30/Jan/16 ]

Abhijit,I have tested with mininet on the latest build , it works, so closing it.

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