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

Reply via email to