Open activatedgeek opened 9 years ago
Can you run sudo -u flowvisor flowvisor -l and print the log.
Here is log output:
Starting FlowVisor
Setting debugging mode: all logs to stderr
--- Setting logging level to NOTE
CRIT:2015-03-03T19:42:07.009:none:: log level enabled: CRIT
ALERT:2015-03-03T19:42:07.048:none:: log level enabled: ALERT
WARN:2015-03-03T19:42:07.049:none:: log level enabled: WARN
INFO:2015-03-03T19:42:07.049:none:: log level enabled: INFO
NOTE:2015-03-03T19:42:07.049:none:: log level enabled: NOTE
INFO:2015-03-03T19:42:07.050:none:: initializing poll loop
INFO:2015-03-03T19:42:07.087:none:: initializing FlowVisor UserAPI JSONRPC SSL WebServer on port 8081
2015-03-03 19:42:07.173:INFO::Logging to StdErrLog::DEBUG=false via org.eclipse.jetty.util.log.StdErrLog
2015-03-03 19:42:07.206:INFO::jetty-7.0.2.v20100331
INFO:2015-03-03T19:42:07.262:OFSwitchAcceptor:: Listenning on port 6633
INFO:2015-03-03T19:42:07.345:none:: initializing FlowVisor UserAPI XMLRPC SSL WebServer on port 8080
2015-03-03 19:42:07.532:INFO::Started SslSelectChannelConnector@0.0.0.0:8081
INFO:2015-03-03T19:42:07.535:none:: flowdb: Disabled
INFO:2015-03-03T19:42:12.585:OFSwitchAcceptor:: got new connection: java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45866]
ALERT:2015-03-03T19:42:12.712:OFSwitchAcceptor:: STARVING: handling event took 128ms: org.flowvisor.events.FVIOEvent@73e9cf30
INFO:2015-03-03T19:42:12.713:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45866]:: got IO exception; closing because : java.io.IOException: got EOF from other side
WARN:2015-03-03T19:42:12.713:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45866]:: tearing down
INFO:2015-03-03T19:42:12.865:OFSwitchAcceptor:: got new connection: java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45867]
ALERT:2015-03-03T19:42:12.878:OFSwitchAcceptor:: STARVING: handling event took 13ms: org.flowvisor.events.FVIOEvent@52719fb6
WARN:2015-03-03T19:42:12.881:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45867]:: Mismatched version from switch java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45867] Got: 4 Wanted: 1
CRIT:2015-03-03T19:42:12.883:none:: dropping bad OF Message: c=0;t=0;err=we only support version 1 and you are not it
CRIT:2015-03-03T19:42:12.884:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45867]:: BUG: bad msg: org.flowvisor.exceptions.MalformedOFMessage: len=12,wrote=56 msg=c=0;t=0;err=we only support version 1 and you are not it
WARN:2015-03-03T19:42:12.884:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/192.168.122.1:6633 remote=/192.168.122.124:45867]:: tearing down
INFO:2015-03-03T19:42:12.886:classifier-dpid=00:00:00:00:00:00:00:01:: identified switch as dpid=00:00:00:00:00:00:00:01 on java.nio.channels.SocketChannel[closed]
INFO:2015-03-03T19:42:12.962:none:: No match for: OFMatch[]
Startup failed : null
INFO:2015-03-03T19:42:12.969:none:: Shutting down config database.
If you look at the following line:
BUG: bad msg: org.flowvisor.exceptions.MalformedOFMessage: len=12,wrote=56 msg=c=0;t=0;err=we only support version 1 and you are not it
You need to change your OpenFlow device to only use OF protocol 1.0 not 1.1,1.3, nor 1.4. I hope this helps.
Hello:
I meet the same messages when I try to connect Mininet
with FlowVisor
.
Starting FlowVisor Setting debugging mode: all logs to stderr --- Setting logging level to NOTE CRIT:2016-04-13T01:33:57.883:none:: log level enabled: CRIT ALERT:2016-04-13T01:33:57.886:none:: log level enabled: ALERT WARN:2016-04-13T01:33:57.886:none:: log level enabled: WARN INFO:2016-04-13T01:33:57.886:none:: log level enabled: INFO NOTE:2016-04-13T01:33:57.886:none:: log level enabled: NOTE INFO:2016-04-13T01:33:57.887:none:: initializing poll loop INFO:2016-04-13T01:33:57.930:none:: initializing FlowVisor UserAPI JSONRPC SSL WebServer on port 8888 2016-04-13 01:33:58.008:INFO::Logging to StdErrLog::DEBUG=false via org.eclipse.jetty.util.log.StdErrLog 2016-04-13 01:33:58.044:INFO::jetty-7.0.2.v20100331 INFO:2016-04-13T01:33:58.081:OFSwitchAcceptor:: Listenning on port 6666 INFO:2016-04-13T01:33:58.257:none:: initializing FlowVisor UserAPI XMLRPC SSL WebServer on port 8080 2016-04-13 01:33:58.487:INFO::Started SslSelectChannelConnector@0.0.0.0:8888 INFO:2016-04-13T01:33:58.528:none:: flowdb: Disabled INFO:2016-04-13T01:33:58.802:OFSwitchAcceptor:: got new connection: java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363] ALERT:2016-04-13T01:33:59.055:OFSwitchAcceptor:: STARVING: handling event took 255ms: org.flowvisor.events.FVIOEvent@3baa1c60 WARN:2016-04-13T01:33:59.058:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363]:: Mismatched version from switch java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363] Got: 4 Wanted: 1 CRIT:2016-04-13T01:33:59.059:none:: dropping bad OF Message: c=0;t=0;err=we only support version 1 and you are not it CRIT:2016-04-13T01:33:59.060:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363]:: BUG: bad msg: org.flowvisor.exceptions.MalformedOFMessage: len=12,wrote=56 msg=c=0;t=0;err=we only support version 1 and you are not it WARN:2016-04-13T01:33:59.060:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363]:: tearing down INFO:2016-04-13T01:33:59.066:classifier-dpid=00:00:00:00:00:00:00:01:: identified switch as dpid=00:00:00:00:00:00:00:01 on java.nio.channels.SocketChannel[closed] INFO:2016-04-13T01:33:59.163:none:: No match for: OFMatch[] Startup failed : null INFO:2016-04-13T01:33:59.165:none:: Shutting down config database.
is that means I can only run FlowVisor
(connect to Mininet
) with OpenFlow protocol 1.0?
the version of FlowVisor I'm using is 1.4-MAINT.
That is correct. FlowVisor only works with 1.0 (at least the last time I played with it). Change the Mininet setting to utilize OF protocol 1.0 and it will work. Good luck
On Wed, Apr 13, 2016 at 3:45 AM, KingsFish notifications@github.com wrote:
Hello: I meet the same messages when I try to connect Mininet with FlowVisor. Starting FlowVisor Setting debugging mode: all logs to stderr --- Setting logging level to NOTE CRIT:2016-04-13T01:33:57.883:none:: log level enabled: CRIT ALERT:2016-04-13T01:33:57.886:none:: log level enabled: ALERT WARN:2016-04-13T01:33:57.886:none:: log level enabled: WARN INFO:2016-04-13T01:33:57.886:none:: log level enabled: INFO NOTE:2016-04-13T01:33:57.886:none:: log level enabled: NOTE INFO:2016-04-13T01:33:57.887:none:: initializing poll loop INFO:2016-04-13T01:33:57.930:none:: initializing FlowVisor UserAPI JSONRPC SSL WebServer on port 8888 2016-04-13 01:33:58.008:INFO::Logging to StdErrLog::DEBUG=false via org.eclipse.jetty.util.log.StdErrLog 2016-04-13 01:33:58.044:INFO::jetty-7.0.2.v20100331 INFO:2016-04-13T01:33:58.081:OFSwitchAcceptor:: Listenning on port 6666 INFO:2016-04-13T01:33:58.257:none:: initializing FlowVisor UserAPI XMLRPC SSL WebServer on port 8080 2016-04-13 01:33:58.487:INFO::Started SslSelectChannelConnector@0.0.0.0:8888 INFO:2016-04-13T01:33:58.528:none:: flowdb: Disabled INFO:2016-04-13T01:33:58.802:OFSwitchAcceptor:: got new connection: java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/ 127.0.0.1:48363] ALERT:2016-04-13T01:33:59.055:OFSwitchAcceptor:: STARVING: handling event took 255ms: org.flowvisor.events.FVIOEvent@3baa1c60 WARN:2016-04-13T01:33:59.058:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363]:: Mismatched version from switch java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363] Got: 4 Wanted: 1 CRIT:2016-04-13T01:33:59.059:none:: dropping bad OF Message: c=0;t=0;err=we only support version 1 and you are not it CRIT:2016-04-13T01:33:59.060:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363]:: BUG: bad msg: org.flowvisor.exceptions.MalformedOFMessage: len=12,wrote=56 msg=c=0;t=0;err=we only support version 1 and you are not it WARN:2016-04-13T01:33:59.060:classifier-unidentified:java.nio.channels.SocketChannel[connected local=/127.0.0.1:6666 remote=/127.0.0.1:48363]:: tearing down INFO:2016-04-13T01:33:59.066:classifier-dpid=00:00:00:00:00:00:00:01:: identified switch as dpid=00:00:00:00:00:00:00:01 on java.nio.channels.SocketChannel[closed] INFO:2016-04-13T01:33:59.163:none:: No match for: OFMatch[] Startup failed : null INFO:2016-04-13T01:33:59.165:none:: Shutting down config database.
is that means I can only run FlowVisor (connect to Mininet) with OpenFlow protocol 1.0? the version of FlowVisor I'm using is 1.4-MAINT.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/opennetworkinglab/flowvisor/issues/278#issuecomment-209308824
Hi, I'm trying to slice a network with flowvisor. I'm using mininet as my testbed and I installed mininet and flowvisor in different VMs in my VirtualBox. The flowvisor version is 1.4. I also changed the flowvisor port from 6633 to 6666. So to connect my mininet topology to flowvisor I'm using this command : sudo mn --controller=remote,ip=192.168.56.101,port=6666 --switch=ovsk,protocols=OpenFlow10 The mininet topology connects successfully to flowvisor but i get those errors in flowvisor :
Help Please.
in fact,I also tried this way like you before, but it seems don't work.
So I tried another way:
first I started mininet like this
sudo mn --controller=remote,ip=192.168.56.101,port=6666
yes, I didn't set the protocol in the begining
later I opened another terminal and typed these code
ovs-vsctl set bridge s1 protocols=OpenFlow10
s1 was the swtich.
the most important thing is that you might set all switch's protocol to OpenFlow1.0
then start flowvisor, it will work.
I think it's not the best way to solve the problem, but it's the best way I find till now. Good Luck!
Hi, this is my log
I tried it your way . But I'm still having the same issue and the same log.
As stated before the last time I messed with flowvisor it only supported 1.0. Change your settings to utilize 1.0 in mininet if you want to use flowvisor.
I have already done that:
sudo mn --controller=remote,ip=192.168.56.101,port=6666 --switch=ovsk,protocols=OpenFlow10
Do you have a controller running? It says on the third to last line No Match for: OFMatch[]. It looks like its talking and registering the dip=00:00:00:00:00:00:01 but it doesn't look like there is a controller running possibly.
On Fri, Apr 22, 2016 at 6:43 PM, Sawsen CHAABNIA notifications@github.com wrote:
I have already done that:
sudo mn --controller=remote,ip=192.168.56.101,port=6666 --switch=ovsk,protocols=OpenFlow10
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/opennetworkinglab/flowvisor/issues/278#issuecomment-213627966
I did run two controllers opendaylight and floodlight after slicing the topology ( a more complicated one actually). But the starving switch error kept appearing in flowvisor and both of the controller. So I wanted to fix it first and see what happen.
I've never seen the starving switch error before.
On Fri, Apr 22, 2016 at 7:44 PM, Sawsen CHAABNIA notifications@github.com wrote:
I did run two controllers opendaylight and floodlight after slicing the topology ( a more complicated one actually). But the starving switch error kept appearing in flowvisor and both of the controller. So I wanted to fix it first and see what happen.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/opennetworkinglab/flowvisor/issues/278#issuecomment-213636442
Ok. Thank you for your time. I hope I can fix it so I can move on Le 23 avr. 2016 01:46, "Oscar Armbruster" notifications@github.com a écrit :
I've never seen the starving switch error before.
On Fri, Apr 22, 2016 at 7:44 PM, Sawsen CHAABNIA <notifications@github.com
wrote:
I did run two controllers opendaylight and floodlight after slicing the topology ( a more complicated one actually). But the starving switch error kept appearing in flowvisor and both of the controller. So I wanted to fix it first and see what happen.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub < https://github.com/opennetworkinglab/flowvisor/issues/278#issuecomment-213636442
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/opennetworkinglab/flowvisor/issues/278#issuecomment-213636553
I am trying get FlowVisor working with
Mininet
but it does not seem to work. Here is the way to replicate the error:sudo -u flowvisor flowvisor
sudo mn --controller=remote --mac --arp
(using the default topology in Mininet)The moment I run mininet,
flowvisor
crashes with the message: "Startup failed: null". I suspect that this error comes from theupdateDB()
method insrc/org/flowvisor/FlowVisor.java
because I haven't configured any database yet. It was not mentioned in any of the installation instructions. I have found anSQL
file though. Can somebody suggest me how do I get it configured?