The idle_timeout defaults to 5 seconds in NOX.
That's hardcoded in openflow-default.hh:

#define DEFAULT_FLOW_TIMEOUT 5
The hard_timeout is 0 (=no hard timeout) unless otherwise specified in the
flow_mod.


On Wed, Apr 18, 2012 at 9:42 AM, Kalapriya Kannan1 <[email protected]>wrote:

>
> hi,
>
> I am more interested in how these idle_timeout and hard_timeout 's are
> calculated if we dont set it explicitly during the insertion of the flow
> entry.  Is there any method used by default for computing these times.
>
> regards,
> kalapriya.
>
>
>
>
> From:        Kyriakos Zarifis <[email protected]>
> To:        Kalapriya Kannan1/India/IBM@IBMIN
> Cc:        "[email protected]" <[email protected]>
> Date:        04/17/2012 06:47 PM
> Subject:        Re: [nox-dev] nox installation
> ------------------------------
>
>
>
> Hi,
>
> this is controlled by the *idle_timeout / hard_timeout* values you set in
> the flow_mod message that installs the flow entry.
>
> From the specification:
>
> If the idle_timeout is set and the hard_timeout is zero, the entry must
> expire after idle_timeout seconds with no received tra ffic. If the
> idle_timeout is zero and the hard_timeout is set, the entry must expire in
> hard_timeout seconds regardless of whether or not packets are hitting the
> entry. If both idle_timeout and hard_timeout are set, the flowow will
> timeout after idle_timeout seconds
> with no traffi c, or hard_timeout seconds, whichever comes fi rst. If both
> idle_timeout and hard_timeout are zero, the entry is considered permanent
> and will never time out. It can still be removed with a flow_mod message of
> type OFPFC_DELETE.
>
> hope this helps
>
> On Tue, Apr 17, 2012 at 9:52 AM, Kalapriya Kannan1 
> <*[email protected]*<[email protected]>>
> wrote:
>
> hi,
>
> I would like to get more details of how the time out for the flow entries
> in the flow tables are calculated? Like what method is used and how do i
> see the code for it..
>
> regards,
> kalapriya.
>
>
>
>
> From:        Murphy McCauley 
> <*[email protected]*<[email protected]>
> >
> To:        Andry Anthony 
> <*[email protected]*<[email protected]>
> >
> Cc:        "*[email protected]* <[email protected]>" <*
> [email protected]* <[email protected]>>
> Date:        04/16/2012 08:52 PM
> Subject:        Re: [nox-dev] nox installation
> Sent by:        
> *[email protected]*<[email protected]>
>  ------------------------------
>
>
>
>
> Do the next steps fail?
>
> mkdir build
> cd build
> ../configure
>
> -- Murphy
>
> On Apr 16, 2012, at 2:15 AM, Andry Anthony wrote:
>
> when i try install nox with *
> ./boot.sh*
> i've got this error
>
> building with all apps
> Disabling noxext...
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.
> libtoolize: copying file `config/config.guess'
> libtoolize: copying file `config/config.sub'
> libtoolize: copying file `config/install-sh'
> libtoolize: copying file `config/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `config'.
> libtoolize: copying file `config/libtool.m4'
> libtoolize: You should add the contents of `config/libtool.m4' to
> `aclocal.m4'.
> libtoolize: copying file `config/ltoptions.m4'
> libtoolize: You should add the contents of `config/ltoptions.m4' to
> `aclocal.m4'.
> libtoolize: copying file `config/ltsugar.m4'
> libtoolize: You should add the contents of `config/ltsugar.m4' to
> `aclocal.m4'.
> libtoolize: copying file `config/ltversion.m4'
> libtoolize: copying file `config/lt~obsolete.m4'
> libtoolize: You should add the contents of `config/lt~obsolete.m4' to
> `aclocal.m4'.
>
>
> can someone tell me what should i do??
>
> thanks
>
> regards
> Andy
>
>
>

Reply via email to