[ovs-discuss] Controller Connection openvswitch

Ben Pfaff blp at nicira.com
Mon Mar 24 21:00:16 UTC 2014


I won't say it's impossible for there to be a switch bug here.
In-band control is tricky, and maybe we've screwed it up.  But we need
more analysis before we can say that there's a bug or exactly what it
is.  I'm happy to hear some details later when Filipe or someone else
has looked more closely at the problem.

On Mon, Mar 24, 2014 at 04:57:57PM -0400, Brent Salisbury wrote:
> Echoing what Ben said, the issue will certainly be on the controller or
> configuration issue with the fabric the control channel is on (loops etc).
> I would forward the email along with logs from the OSGI console or the
> /logging directory to controller-dev at lists.opendaylight.org
> 
> Alternatively you can pop into #opendaylight (controller/overall channel)
> or #opendaylight-ovsdb (ODL OVSDB plugin) channel for a realtime assist.
> 
> Thanks,
> -Brent
> 
> 
> On 3/24/14, 4:25 PM, "Ben Pfaff" <blp at nicira.com> wrote:
> 
> >It seems likely that the controller is doing something that kills the
> >connection.
> >
> >On Mon, Mar 24, 2014 at 05:30:19PM +0000, filipe Antonio wrote:
> >> Hi,
> >> 
> >> Those are the logs I get,
> >> 
> >> 
> >>2014-03-24T16:43:52.127Z|04226|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connected
> >> 2014-03-24T16:43:52.162Z|04227|fail_open|WARN|No longer in fail-open
> >>mode
> >> 
> >>2014-03-24T16:44:02.122Z|04228|rconn|ERR|of-switch<->tcp:192.168.0.253:66
> >>33:
> >> no response to inactivity probe after 5 seconds, disconnecting
> >> 
> >>2014-03-24T16:44:03.121Z|04229|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connecting...
> >> 
> >>2014-03-24T16:44:04.121Z|04230|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connection timed out
> >> 
> >>2014-03-24T16:44:04.121Z|04231|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> waiting 2 seconds before reconnect
> >> 
> >>2014-03-24T16:44:06.121Z|04232|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connecting...
> >> 2014-03-24T16:44:07.151Z|04233|fail_open|WARN|Could not connect to
> >> controller (or switch failed controller's post-connection admission
> >> control policy) for 15 seconds, failing open
> >> 
> >>2014-03-24T16:44:08.121Z|04234|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connection timed out
> >> 
> >>2014-03-24T16:44:08.121Z|04235|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> waiting 4 seconds before reconnect
> >> 
> >>2014-03-24T16:44:12.121Z|04236|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connecting...
> >> 
> >>2014-03-24T16:44:12.127Z|04237|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connected
> >> 2014-03-24T16:44:12.158Z|04238|fail_open|WARN|No longer in fail-open
> >>mode
> >> 2014-03-24T16:44:17.287Z|04239|ofproto|INFO|of-switch: 3 flow_mods in
> >> the 39 s starting 45 s ago (3 deletes)
> >> 
> >>2014-03-24T16:44:22.121Z|04240|rconn|ERR|of-switch<->tcp:192.168.0.253:66
> >>33:
> >> no response to inactivity probe after 5 seconds, disconnecting
> >> 
> >>2014-03-24T16:44:23.121Z|04241|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connecting...
> >> 
> >>2014-03-24T16:44:24.121Z|04242|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connection timed out
> >> 
> >>2014-03-24T16:44:24.121Z|04243|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> waiting 2 seconds before reconnect
> >> 
> >>2014-03-24T16:44:26.121Z|04244|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connecting...
> >> 2014-03-24T16:44:27.179Z|04245|fail_open|WARN|Could not connect to
> >> controller (or switch failed controller's post-connection admission
> >> control policy) for 15 seconds, failing open
> >> 
> >>2014-03-24T16:44:28.121Z|04246|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> connection timed out
> >> 
> >>2014-03-24T16:44:28.121Z|04247|rconn|INFO|of-switch<->tcp:192.168.0.253:6
> >>633:
> >> waiting 4 seconds before reconnect
> >> 
> >> Filipe
> >> 
> >> 
> >> Em 24-03-2014 16:23, Ben Pfaff escreveu:
> >> > On Mon, Mar 24, 2014 at 03:57:55PM +0000, filipe Antonio wrote:
> >> >> My LAN has two openvswitch and an ODL controller. I run the command
> >> >> ovs-vsctl set controller in each openvswitch to connect to the
> >> >> controller, with success. I can visualize the network in ODL. When I
> >> >> run repeatedly the command *List Controller* in the console of one of
> >> >> the openvswitch, the is_connected field alternate between true and
> >> >> false, which i think it means the connection is not stable. Why is it
> >> >> happening?
> >> > You can find more information in the Open vSwitch log.
> >> 
> >_______________________________________________
> >discuss mailing list
> >discuss at openvswitch.org
> >http://openvswitch.org/mailman/listinfo/discuss
> 
> 



More information about the discuss mailing list