[L2SWITCH-27] The Default L2Switch Idle (1800secs) and hard (3600seconds) timeouts are very high Created: 10/Dec/14  Updated: 20/May/16  Due: 02/Jan/15  Resolved: 20/May/16

Status: Resolved
Project: l2switch
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Kuldip Assignee: Sai MarapaReddy
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


External issue ID: 2501
Priority: High

 Description   

The Default L2Switch Idle (1800secs) and hard (3600seconds) timeouts as set in
~/opendaylight/etc/opendaylight/karaf/58-l2switchmain.xml

<is-learning-only-mode>false</is-learning-only-mode>
<is-install-dropall-flow>true</is-install-dropall-flow>
<dropall-flow-table-id>0</dropall-flow-table-id>
<dropall-flow-priority>0</dropall-flow-priority>
<dropall-flow-idle-timeout>0</dropall-flow-idle-timeout>
<dropall-flow-hard-timeout>0</dropall-flow-hard-timeout>
<reactive-flow-table-id>0</reactive-flow-table-id>
<reactive-flow-priority>10</reactive-flow-priority>
<reactive-flow-idle-timeout>1800</reactive-flow-idle-timeout> <-- here
<reactive-flow-hard-timeout>3600</reactive-flow-hard-timeout> <--here

are unrealistic for a real network.

As a result of this Unwanted flows are stuck are for an unimaginable amount of time
because of this.

The default values can be 300/600 for idle and hard timeout.



 Comments   
Comment by Sai MarapaReddy [ 19/Apr/16 ]

Agree with the timeout limits. This needs to be fixed unless there are any objections. I will assign this bug to myself.

Comment by Sai MarapaReddy [ 27/Apr/16 ]

https://git.opendaylight.org/gerrit/#/c/38161/

https://git.opendaylight.org/gerrit/#/c/38162/

Comment by Sai MarapaReddy [ 20/May/16 ]

Patches merged.

Generated at Wed Feb 07 20:05:44 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.