Re: [nox-dev] Flow expired events in NOX

2011-10-21 Thread Candy Floss
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

Re: [nox-dev] Flow expired events in NOX

2011-10-20 Thread kk yap
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 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). The

Re: [nox-dev] Flow expired events in NOX

2011-10-20 Thread Candy Floss
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 wro

Re: [nox-dev] Flow expired events in NOX

2011-10-20 Thread Kyriakos Zarifis
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

[nox-dev] Flow expired events in NOX

2011-10-20 Thread Candy Floss
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 s