stats for reverse flow not correct when a evicted flow entry becomes active again
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Anand H. Krishnan | |||
Trunk |
Fix Committed
|
High
|
Anand H. Krishnan |
Bug Description
R2.20 Build 111 Ubuntu 14.04 Juno multinode
Steps :
From 219.14.75.4,
send(IP(
Flow -l shows this :
=======
root@nodek1:~# flow -l | grep -A 2 2000
155104<=>2993244 219.14.75.4:2000 219.14.75.3:9099 6 (6)
(K(nh):51, Action:F, Flags:, TCP:S, S(nh):51, Stats:1/54, SPort:49690)
--
2993244<=>155104 219.14.75.3:9099 219.14.75.4:2000 6 (6)
(K(nh):51, Action:F, Flags:, TCP:Sr, S(nh):14, Stats:0/0, SPort:61910)
root@nodek1:~#
=======
From 219.14.75.3,
send(IP(
Then, flow gets evicted :
root@nodek1:~# flow -l | grep -A 2 2000
root@nodek1:~#
Then, send the first syn packet again
send(IP(
The same flow indices get used. But the reverse flow would show a count of 1 even when there are no reverse packets for this session
root@nodek1:~# flow -l | grep -A 2 2000
155104<=>2993244 219.14.75.4:2000 219.14.75.3:9099 6 (6)
(K(nh):51, Action:F, Flags:, TCP:S, S(nh):51, Stats:1/54, SPort:49690)
--
2993244<=>155104 219.14.75.3:9099 219.14.75.4:2000 6 (6)
(K(nh):51, Action:F, Flags:, TCP:Sr, S(nh):14, Stats:1/54, SPort:61910)
root@nodek1:~#
The counter seems to accumulate everytime i do this..
Reviewed: https:/ /review. opencontrail. org/15477 github. org/Juniper/ contrail- vrouter/ commit/ 8d9a87f2c34b61d db1bb2956045150 53e2fd7860
Committed: http://
Submitter: Zuul
Branch: R2.20
commit 8d9a87f2c34b61d db1bb2956045150 53e2fd7860
Author: Anand H. Krishnan <email address hidden>
Date: Mon Nov 30 14:14:14 2015 +0530
Logic to reset statistics of the evicted reverse flow
The point where we reset statistics for an evicted flow is when we
trap the first packet to the agent. The trap message carries the
old statistics. However, for the reverse flow, there is no trap.
Hence, the statistics of the evicted reverse flow entry is sent
back to the agent in the sandesh flow message and reset once the
agent tries to add the reverse flow entry.
Change-Id: Ic67318b9632f39 560292512be503f 90eb6f33068
Closes-BUG: 1362701