flowvisor icon indicating copy to clipboard operation
flowvisor copied to clipboard

displaying connected switches when no switches are running

Open brandonheller opened this issue 11 years ago • 11 comments

This comes from the tutorial and can be seen as unexpected, confusing behavior.

After a machine reboot and flowvisor restart,

mininet@mininet:~$ fvctl -f /dev/null list-datapaths
Connected switches: 
  1 : 00:00:00:00:00:00:00:01
  2 : 00:00:00:00:00:00:00:02
  3 : 00:00:00:00:00:00:00:03
  4 : 00:00:00:00:00:00:00:04

I don't know much about FV internals or operation, but it would seem that if I restart FV and have no network running, my connected switches list would be empty, or at least indicate that the "Connected Switches" are likely dead, because they last connected pre-reboot, pre-FV-restart, and minutes ago.

brandonheller avatar Apr 12 '13 18:04 brandonheller

In this case switches are actually connected to FlowVisor. Since the switches are configured to connect to their controller which, in this case, is flowvisor. It's actually nice to have this work the way it does, because it at least tells you that your switches are connecting to FV.

On Apr 12, 2013, at 11:33 AM, Brandon Heller [email protected] wrote:

This comes from the tutorial and can be seen as unexpected, confusing behavior.

After a machine reboot and flowvisor restart,

mininet@mininet:~$ fvctl -f /dev/null list-datapaths Connected switches: 1 : 00:00:00:00:00:00:00:01 2 : 00:00:00:00:00:00:00:02 3 : 00:00:00:00:00:00:00:03 4 : 00:00:00:00:00:00:00:04

I don't know much about FV internals or operation, but it would seem that if I restart FV and have no network running, my connected switches list would be empty, or at least indicate that the "Connected Switches" are likely dead, because they last connected pre-reboot, pre-FV-restart, and minutes ago.

— Reply to this email directly or view it on GitHub.

alshabib avatar Apr 12 '13 18:04 alshabib

Then maybe connected is the wrong word. Again, NO SWITCHES EXIST in this network. I haven't created them.

How about:

Switches configured to connect:
...

brandonheller avatar Apr 12 '13 18:04 brandonheller

So you are saying that mininet is NOT running and you are getting this output?

On Apr 12, 2013, at 11:46 AM, Brandon Heller [email protected] wrote:

Then maybe connected is the wrong word. Again, NO SWITCHES EXIST in this network. I haven't created them.

How about:

Switches configured to connect: ...

— Reply to this email directly or view it on GitHub.

alshabib avatar Apr 12 '13 18:04 alshabib

Exactly. Fresh from a reboot:

mininet@mininet:~$ ps -A | grep mn
mininet@mininet:~$ sudo /etc/init.d/flowvisor restart
Sleeping a bit to let FlowVisor shutdown
Starting flowvisor with the configuration stored in DB
If DB unpopulated, laod config using 'fvconfig load config.json'
mininet@mininet:~$ fvctl -f /dev/null list-datapaths
Connected switches: 
  1 : 00:00:00:00:00:00:00:01
  2 : 00:00:00:00:00:00:00:02
  3 : 00:00:00:00:00:00:00:03
  4 : 00:00:00:00:00:00:00:04
mininet@mininet:~$ 

brandonheller avatar Apr 12 '13 21:04 brandonheller

Ahh. Then this should not happen at all. Something is odd there. Thanks for reporting.

On Apr 12, 2013, at 2:16 PM, Brandon Heller [email protected] wrote:

Exactly. Fresh from a reboot:

mininet@mininet:~$ ps -A | grep mn mininet@mininet:~$ sudo /etc/init.d/flowvisor restart Sleeping a bit to let FlowVisor shutdown Starting flowvisor with the configuration stored in DB If DB unpopulated, laod config using 'fvconfig load config.json' mininet@mininet:~$ fvctl -f /dev/null list-datapaths Connected switches: 1 : 00:00:00:00:00:00:00:01 2 : 00:00:00:00:00:00:00:02 3 : 00:00:00:00:00:00:00:03 4 : 00:00:00:00:00:00:00:04 mininet@mininet:~$

— Reply to this email directly or view it on GitHub.

alshabib avatar Apr 12 '13 21:04 alshabib

I am unable to reproduce this bug. Do you have a specific procedure you could walk me throuhg?

alshabib avatar Apr 26 '13 20:04 alshabib

It was seen when going through this exercise: https://github.com/onstutorial/onstutorial/wiki/Flowvisor-Exercise

Sorry, I don't recall the exact steps, but I think it just required the steps above: restarting FV, then using fvctl.

VM is here: http://epic.stanford.edu/ons-2013-tutorial.ova md5sum: b190e1e1073e8a5501fc491603e66f27

brandonheller avatar Apr 26 '13 21:04 brandonheller

Hi, Does anyone have a working link for the "ons-2013-tutorial.ova" VM ?? The Stanford link above seems to be down.

redamaged avatar Aug 22 '13 07:08 redamaged

Just have a link to the ons tutorial, but guess there is no vm image in it... https://github.com/onstutorial/onstutorial/wiki/Install-Required-Software#wiki-Install_and_Verify

On Thu, Aug 22, 2013 at 12:46 AM, redamaged [email protected]:

Hi, Does anyone have a working link for the "ons-2013-tutorial.ova" VM ?? The Stanford above link seems to be down.

— Reply to this email directly or view it on GitHubhttps://github.com/OPENNETWORKINGLAB/flowvisor/issues/198#issuecomment-23073189 .

mssumanth avatar Aug 22 '13 16:08 mssumanth

yeah, I can't find it anywhere :/

redamaged avatar Aug 22 '13 18:08 redamaged

redamaged, a bit late but I think I found it here: https://github.com/onstutorial/onstutorial/wiki/onstutorial#Download_Files

guillermochica avatar Oct 16 '15 15:10 guillermochica