Hi,
Thank you for the reply.
When you ask "Did you set OpenFlow version compatibility level for the
bridge?", is about the line*ovs-vsctl set bridge br0
protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow1**3*, I run that command before
connect the openvswitch to the controller.
Regards,
Filipe
On 23-05-2014 18:04, Andrey Korolyov wrote:
On 05/22/2014 03:39 PM, Filipe Antonio wrote:
Hi,
I connect a openvswitch (ovs_version: "2.1.90") to a Opendaylight
Controller. The Controller recognize the switch, but the switch doesn´t
accept flows from Controller. It seems the connection is temporarely lost.
The output of ovs-vswitchd.log logfile from openvswitch is:
2014-05-21T16:30:17.118Z|01741|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connection timed out
2014-05-21T16:30:17.118Z|01742|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
waiting 4 seconds before reconnect
2014-05-21T16:30:21.118Z|01743|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connecting...
2014-05-21T16:30:21.124Z|01744|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connected
2014-05-21T16:30:21.140Z|01745|fail_open|WARN|No longer in fail-open mode
2014-05-21T16:30:31.118Z|01746|rconn|ERR|of-switch<->tcp:192.168.0.253:6633:
no response to inactivity probe after 5 seconds, disconnecting
2014-05-21T16:30:32.118Z|01747|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connecting...
2014-05-21T16:30:33.119Z|01748|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connection timed out
2014-05-21T16:30:33.119Z|01749|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
waiting 2 seconds before reconnect
2014-05-21T16:30:35.118Z|01750|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connecting...
2014-05-21T16:30:36.164Z|01751|fail_open|WARN|Could not connect to
controller (or switch failed controller's post-connection admission
control policy) for 15 seconds, failing open
2014-05-21T16:30:37.119Z|01752|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connection timed out
2014-05-21T16:30:37.119Z|01753|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
waiting 4 seconds before reconnect
2014-05-21T16:30:41.118Z|01754|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connecting...
2014-05-21T16:30:41.124Z|01755|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connected
2014-05-21T16:30:41.137Z|01756|fail_open|WARN|No longer in fail-open mode
2014-05-21T16:30:51.119Z|01757|rconn|ERR|of-switch<->tcp:192.168.0.253:6633:
no response to inactivity probe after 5 seconds, disconnecting
2014-05-21T16:30:52.118Z|01758|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connecting...
2014-05-21T16:30:53.118Z|01759|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connection timed out
2014-05-21T16:30:53.118Z|01760|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
waiting 2 seconds before reconnect
2014-05-21T16:30:55.118Z|01761|rconn|INFO|of-switch<->tcp:192.168.0.253:6633:
connecting...
I searched for solutions but I didn´t found one to solve this problem.
How can I solve this matter?
Did you set OpenFlow version compatibility level for the bridge?
Thank you
Regards,
Filipe
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
