[Mainline-Build 2704]: Fat flow- IPv6 Fat flow gets deleted after connection closure

[alok kumar]

Fat flow should not be deleted/evicted after connection closure.

In case of IPv6, flow gets deleted after connection closure.
I see connection status is being tracked in the flow, so after closure it gets deleted.

root@nodec62:~# flow -l | grep 2002:1::4:22 -A2 -B2
    Index Source:Port/Destination:Port Proto(V)
-----------------------------------------------------------------------------------
    73308<=>396416 2002:1::4:22 6 (1)
                         2002:1::3:0
    (K(nh):22, Action:F, Flags:, TCP:SSrEEr, S(nh):22, Statistics:11/3371 UdpSrcPort 60956
--

   396416<=>73308 2002:1::3:0 6 (1)
                         2002:1::4:22
    (K(nh):22, Action:F, Flags:, TCP:SSrEEr, S(nh):13, Statistics:11/2473 UdpSrcPort 63952

[Ashok Singh (ashoksr)]

vrouter kernel module is evicting the IPv6 TCP flow

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17219
Submitter: Anand H. Krishnan (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17219
Committed: http://github.org/Juniper/contrail-vrouter/commit/4c9dc661b85d4f5e5a3cc970911d0166248d76a0
Submitter: Zuul
Branch: master

commit 4c9dc661b85d4f5e5a3cc970911d0166248d76a0
Author: Anand H. Krishnan <email address hidden>
Date: Mon Feb 15 10:15:18 2016 +0530

ipv6 version of fat flow identifier

Some packet processing, such as TCP state machine, should not be
applied to fat flows. Hence, there should be a way to determine
whether an existing flow is a fat flow or not. ipv4 version of
such an identifier already existed. Extend that identifier for
ipv6 flows too.

Change-Id: I159de2274e3202753a5fee7fe7075a48f84e66ba
Closes-BUG: #1541872

[alok kumar (kalok)]

verified the fix on R3.0 2717.

[alok kumar (kalok)]

covered in test_fat_flow_no_tcp_eviction.