This group is locked. No changes can be made to the group while it is locked.
Date
1 - 3 of 3
openflowplugin oxygen-stable couldn't get links
Mingming
Hi Jamo,
Thank you! Now I got a update. After tried for more times, sometimes I got links with openflowplugin, sometimes I did not. So is this a unstable problem? But h1 ping h2 still doesn't work.
Another problem which I think is more important: I still can get nodes (http://172.16.129.1:8181/restconf/operational/opendaylight-inventory:nodes/) when I shutdown mininet. Just links in topo (http://localhost:8181/restconf/operational/network-topology:network-topology) are gone. If so, I can't notice node failure. In other words, I can't figure out disconnections happened in "switch to controller" or "switch to switch" just by checking link status in topology.
I think operational data store means get the sync info from switches. config data store means odl configuration information which is fine to keep records when switches are gone.
I really want to catch up with latest odl so I could do something on it. Thank you for your help!
Best regards,
Mingming
At 2018-04-19 01:49:02, "Jamo Luhrsen" <jluhrsen@...> wrote: >adding the openflowplugin-dev list as I think there will >be more people reading that to help you. > >On 4/18/18 10:16 AM, Mingming Chen wrote: >> Hi all, >> >> Recently, I am working on openflowplugin oxygen-stable. I met a problem: I couldn't get links using >> "http://localhost:8181/restconf/operational/network-topology:network-topology" >> <http://localhost:8181/restconf/operational/network-topology:network-topology",>, but other info like topo-ids work >> well. As a result, h1 ping h2 (mininet) couldn't succeed. However, links are shown in topology when I use l2switch. >> >> Besides, I have done some works trying to figure out the problem. According to: >> " >> http://docs.opendaylight.org/en/stable-oxygen/user-guide/openflow-plugin-project-user-guide.html#running-the-controller-with-the-new-openflow-plugin. >> >> In case topology is required then the first one should be installed. >> >> feature:install odl-openflowplugin-app-lldp-speaker-li >> >> " >> There should be "odl-openflowplugin-app-lldp-speaker-li", but I didn't find it. I have read code as well. Is it the one >> called "odl-openflowplugin-app-topology"? I saw some lldp dependencies in it. >> >> Another problem is that port 6633 will stop being listening if I "feature:installed featuers-openflowplugin and >> features-l2switch". >> >> Did I make some mistakes so I failed? Or there are some designs here? Really need your help! Thank you! >> >> Best regards, >> Mingming >> >> >> >> _______________________________________________ >> openflowplugin-users mailing list >> openflowplugin-users@... >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-users >>
Jamo Luhrsen <jluhrsen@...>
adding the openflowplugin-dev list as I think there will
be more people reading that to help you.
toggle quoted message
Show quoted text
be more people reading that to help you.
On 4/18/18 10:16 AM, Mingming Chen wrote:
Hi all,
Recently, I am working on openflowplugin oxygen-stable. I met a problem: I couldn't get links using "http://localhost:8181/restconf/operational/network-topology:network-topology" <http://localhost:8181/restconf/operational/network-topology:network-topology",>, but other info like topo-ids work well. As a result, h1 ping h2 (mininet) couldn't succeed. However, links are shown in topology when I use l2switch.
Besides, I have done some works trying to figure out the problem. According to:
"
http://docs.opendaylight.org/en/stable-oxygen/user-guide/openflow-plugin-project-user-guide.html#running-the-controller-with-the-new-openflow-plugin. In case topology is required then the first one should be installed.
feature:install odl-openflowplugin-app-lldp-speaker-li
"
There should be "odl-openflowplugin-app-lldp-speaker-li", but I didn't find it. I have read code as well. Is it the one called "odl-openflowplugin-app-topology"? I saw some lldp dependencies in it.
Another problem is that port 6633 will stop being listening if I "feature:installed featuers-openflowplugin and features-l2switch".
Did I make some mistakes so I failed? Or there are some designs here? Really need your help! Thank you!
Best regards,
Mingming
_______________________________________________
openflowplugin-users mailing list
openflowplugin-users@...
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-users
Mingming
Hi all,
Recently, I am working on openflowplugin oxygen-stable. I met a problem: I couldn't get links using "http://localhost:8181/restconf/operational/network-topology:network-topology", but other info like topo-ids work well. As a result, h1 ping h2 (mininet) couldn't succeed. However, links are shown in topology when I use l2switch.
Besides, I have done some works trying to figure out the problem. According to:
"
In case topology is required then the first one should be installed.
feature:install odl-openflowplugin-app-lldp-speaker-li
"
There should be "odl-openflowplugin-app-lldp-speaker-li", but I didn't find it. I have read code as well. Is it the one called "odl-openflowplugin-app-topology"? I saw some lldp dependencies in it.
Another problem is that port 6633 will stop being listening if I "feature:installed featuers-openflowplugin and features-l2switch".
Did I make some mistakes so I failed? Or there are some designs here? Really need your help! Thank you!
Best regards,
Mingming