I'm seeing another issue. I'm getting flow expired message even before a flow is started. I'm getting the flow expired messages when the switch is trying to connect to NOX. Please see the prints below. Why is flow expiry messages coming?
00041|openflow|DBG:Passive tcp interface bound to port 6633 00042|nox|INFO:nox bootstrap complete 00043|openflow|DBG:Passive tcp interface received connection 00044|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00045|nox|DBG:Success sending in 'sending switch config' 00046|nox|DBG:Success sending in 'receiving features reply' 00047|nox|DBG:Success receiving in 'receiving features reply' 00048|nox|DBG:Success sending in 'receiving ofmp capability reply' 00049|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00050|nox|DBG:Datapath 0036fb31fe75 sent error in response to capability reply, assuming no management support 00051|nox|DBG:No switch auth module registered, auto-approving switch 00052|nox|DBG:Registering switch with DPID = 36fb31fe75 00053|nox.coreapps.examples.pyswitch|INFO:Switch 36fb31fe75 has joined the network 00054|openflow-event|DBG:received flow expired event from 0036fb31fe75 00055|openflow-event|DBG:received flow expired event from 0036fb31fe75 00056|openflow-event|DBG:received flow expired event from 0036fb31fe75 00057|openflow-event|DBG:received flow expired event from 0036fb31fe75 00058|openflow|DBG:Passive tcp interface received connection 00059|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00060|nox|DBG:Success sending in 'sending switch config' 00061|nox|DBG:Success sending in 'receiving features reply' 00062|nox|DBG:Success receiving in 'receiving features reply' 00063|nox|DBG:Success sending in 'receiving ofmp capability reply' 00064|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00065|nox|DBG:Datapath 0036fb31fe76 sent error in response to capability reply, assuming no management support 00066|nox|DBG:No switch auth module registered, auto-approving switch 00067|nox|DBG:Registering switch with DPID = 36fb31fe76 00068|nox.coreapps.examples.pyswitch|INFO:Switch 36fb31fe76 has joined the network 00069|openflow-event|DBG:received flow expired event from 0036fb31fe76 00070|openflow-event|DBG:received flow expired event from 0036fb31fe76 00071|openflow-event|DBG:received flow expired event from 0036fb31fe76 00072|openflow-event|DBG:received flow expired event from 0036fb31fe76 Thanks & Regards, Candy On Thu, Oct 20, 2011 at 3:26 PM, kk yap <yap...@stanford.edu> wrote: > Hi, > > Try changing src/include/openflow-default.hh. Hope this is what you > are looking for. > > Regards > KK > > On 20 October 2011 13:42, Candy Floss <cndf...@gmail.com> wrote: > > Thanks for the reply. I'm not running discovery module. The idle time out > is > > set for 5 secs and the hard timeout is set to 0(i.e. permanent). These > are > > the parameters that are in the code by default. I have not changed > anything. > > > > Regards, > > Candy > > > > On Thu, Oct 20, 2011 at 1:39 PM, Kyriakos Zarifis <kyr.zari...@gmail.com > > > > wrote: > >> > >> Hi, > >> are you running 'discovery' or any other application that has discovery > as > >> a dependency? > >> If so, the packet_ins you see are most probably the control (LLDP) > packets > >> sent by discovery to discover neighbors. > >> ( http://noxrepo.org/noxwiki/index.php/Discovery ) > >> the flow expiration time is set from the controller, when you send the > >> flow_mods. The flow_mod includes arguments to set hard/idle timeout for > the > >> entry. 'Idle timeout' means the entry will expire X seconds after no > >> matching traffic has hit the switch, 'hard timeout' means it will expire > in > >> X seconds no matter what. > >> (Section 5.5.3 > >> in http://www.openflow.org/documents/openflow-spec-v1.0.0.pdf) > >> > >> On Thu, Oct 20, 2011 at 1:27 PM, Candy Floss <cndf...@gmail.com> wrote: > >>> > >>> I have copnnected NOX and two switches. Sometimes when I connect the > >>> switch to the NOX I see packet_in event in addition to datapath_join > event. > >>> This is happening randomly. Not able to find a pattern when this > eaxctly > >>> happens but it happens most of teh time. I'm not starting any flows but > I > >>> still see packet_in event coming continously. What could be the reason? > >>> > >>> And also when I start the flow I see flow expired event on NOX in 1-2 > >>> secs. Where can I change the default timeout? Do I have to change in > NOX or > >>> in openflow switch? > >>> > >>> Thanks & Regards, > >>> Candy > >>> > >>> _______________________________________________ > >>> nox-dev mailing list > >>> nox-dev@noxrepo.org > >>> http://noxrepo.org/mailman/listinfo/nox-dev > >>> > >> > > > > > > _______________________________________________ > > nox-dev mailing list > > nox-dev@noxrepo.org > > http://noxrepo.org/mailman/listinfo/nox-dev > > > > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
