This website requires JavaScript.
Explore
Help
Sign In
mirrors
/
onos
Watch
1
Star
0
Fork
0
You've already forked onos
mirror of
https://github.com/opennetworkinglab/onos.git
synced
2025-10-28 14:51:37 +01:00
Code
Issues
Projects
Releases
Wiki
Activity
onos
/
core
/
net
History
Gamze Abaka
8d03f1896f
ONOS controls the packet count field from flow statistics to check flow liveness, but some switches (such as Pica8) do not support packet count field of the flow statistics. Pica8 switch sends "-1" as the packet count. Even though packets match flow rules, when the idle-timeout time is up, ONOS deletes these rules based on the packet count field anyways. Therefore, just checking the packet count field is not enough for this situation. Pica8 sends byte count properly. If ONOS checks both packet and byte count, this problem will be solved. I would like to add byte count check to FlowRuleManager - checkRuleLiveness method.
...
Change-Id: I4ade01bcd17c4b0a7a59750bd1834b87e78f9972
2017-07-25 23:13:54 +00:00
..
src
ONOS controls the packet count field from flow statistics to check flow liveness, but some switches (such as Pica8) do not support packet count field of the flow statistics. Pica8 switch sends "-1" as the packet count. Even though packets match flow rules, when the idle-timeout time is up, ONOS deletes these rules based on the packet count field anyways. Therefore, just checking the packet count field is not enough for this situation. Pica8 sends byte count properly. If ONOS checks both packet and byte count, this problem will be solved. I would like to add byte count check to FlowRuleManager - checkRuleLiveness method.
2017-07-25 23:13:54 +00:00
BUCK
ONOS-6605 PI flow rule translator implementation
2017-06-21 20:29:45 +00:00
pom.xml
Starting snapshot 1.11.0-SNAPSHOT
2017-07-20 15:46:52 -07:00