Hi all,
Thanks for your replays.
Yes, I decrement the counter when the flow removed by idle_timeout and used
flow-removed_handler to know this. But the problem in this case is the
packet-in generated more than once for the same packet but the flow is added
once and this increments the counter more than one time for the same flow,
which is incorrect.
I can’t understand why there is multiple packet-in generated??
Regards,
Eman Bany Salameh
> On Feb 28, 2018, at 2:56 PM, Vasu Dasari <vdas...@gmail.com> wrote:
>
> You could look for flow-removed messages from switch and use that to adjust
> flows installed in your app accordingly.
>
> In OpenFlow version >= 1.4 you could use flow monitoring as well. This way
> you can keep a check on flows in the switch.
>
> 7.3.5.19 Flow Monitoring
> https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-switch-v1.5.0.noipr.pdf#page149
>
>> On Feb 28, 2018, at 12:49 AM, knet solutions <knetsolutio...@gmail.com>
>> wrote:
>>
>> If we maintain the count in SDN controller, There is a possibility of
>> mismatch in the count between the switch and controller .
>> Each flow has a timeout(idle and hard), it will be flushed out after the
>> timeout period.
>>
>>> On Wed, Feb 28, 2018 at 1:59 PM, Moh'd Reza Abbasi <mr.mrabb...@gmail.com>
>>> wrote:
>>> I don't think OpenFlow v.1.3 has such a feature, but how about adding a
>>> counter in your Ryu app to keep track of added/removed rules...
>>>
>>>> On Wed, Feb 28, 2018 at 11:53 AM, Eman Bany salameh via Ryu-devel
>>>> <ryu-devel@lists.sourceforge.net> wrote:
>>>> Hi,
>>>>
>>>> I need to know the number of flows installed on the switch before adding
>>>> new one. What I did before is to request stat from the switch then read
>>>> the length of the list returned.
>>>> This way is not useful for me.
>>>> Is there any way to count them inside packet-in handler before adding new
>>>> flow? I want to limit the number of flows added to 1500.
>>>>
>>>> Regards,
>>>> Eman Bany Salameh
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Ryu-devel mailing list
>>>> Ryu-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Ryu-devel mailing list
>>> Ryu-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
>>>
>>
>>
>>
>> --
>> Regards,
>> Knet solutions.
>>
>> https://github.com/knetsolutions/KNet
>> http://knet-topology-builder.readthedocs.io/
>> http://knetsolutions.in/
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Ryu-devel mailing list
>> Ryu-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/ryu-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Ryu-devel mailing list
Ryu-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ryu-devel
