Hi Rob, I attach a pcap that shows the problem. You can see the keep-alive I mention at packet 68 and 236. This is when the connection is already established (i.e. features-request/replies, ofp_vendor already completed). Note that before the TCP RST, nox's ECHO_REQUEST has been acked by the ofprotocol side.
Thanks, Y. p.s. when ofprotocol tries to reconnect it fails twice as it cannot connect to ofdatapath, therefore failing on features reply. I think this is not related with this problem, but rather in the ofprotocol-ofdatapath connection based on unix-domain sockets.. On Mon, Feb 14, 2011 at 9:15 PM, Rob Sherwood <rob.sherw...@stanford.edu>wrote: > [keeping cross posting b/c it re-enforces my concerns about > artificially dividing our mailing lists] > > Hi Yiannis, > > First, I would look at wireshark to figure out the exact sequence of > messages. > > But second, nox sends a ofp_vendor message and gives the disconnect > message similar to what you're seeing if it does not get a reply > (either the right ofp_vendor reply or an ofp_error with unsupported). > Did you somehow break this sequence? > > - Rob > . > > > On Mon, Feb 14, 2011 at 7:16 PM, Yiannis Yiakoumis > <yiann...@stanford.edu> wrote: > > Hi, > > Sorry for the cross-posting, not sure what's the most appropriate list. > > i use OpenFlow 1.0 (reference impl) and nox-zaku. By default, both > > ofprotocol and nox will start with a keep-alive of 15 secs. After a few > > minutes of inactivity, the switch side disconnects, sending a tcp request > > and complaining as follows : > > Feb 15 02:02:04 172.24.74.231 sysinit: Feb 15 > > 02:02:04|02563|rconn|ERR|tcp:openflow3.stanford.edu:6633: no response to > > inactivity probe after 15 seconds, disconnecting > > I changed nox keep-alive to 10 secs and ofprotocol to 20. I don't see any > > resets at that point, but I am still confused with the switch sending > > ECHO_REQUESTs. I was expecting that since it receives requests from nox, > it > > will consider the connection ACTIVE, thus not sending any keep-alives on > its > > own. Instead it keeps sending "echo requests" every 20 secs. What's the > > intended behavior of rconn/vconn here? I suspect that this is related > with > > the periodic disconnects I mentioned earlier. > > Note that this happens only when there is no traffic in the channel (aka > no > > LLDP or any other packets). > > Srini, is this related with what we've seen with the > > circuit-aggregation/flowvisor setup? > > Thanks, > > Yiannis > > _______________________________________________ > > openflow-discuss mailing list > > openflow-disc...@lists.stanford.edu > > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > > > > >
nox-ofprotocol-reset.pcap
Description: Binary data
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org