The CSS run a process called Garbage collection, this is because when booting up the CSS allocates part of its memory into FCBs (Flow Control Blocks) which are used to allocate flows on the flow table.
If the CSS would run out of FCBs, then it would not be able to handle more flows, for that reason iddle flows are removed from the Flow table, this is what "Garbage collection" is.
The default timeout for flows to be moved from the Flow Table to a spoof table is 16sec, so it is possible that those flows are getting garbage collected.
This is a possibility, but many other things might cause the issue, you said that traces show RST, did you got traces at both sides of the CSS? is the RST showing only between the CSS and the client? is it present on the server side?
Since this traffic is on port 13059 I would guess your content rule is layer 4, if so the CSS will just pass the traffic (no spoofing) so it would be important to veirfy that the RST is actually not coming from the server itself and being just forwarded as this is also a possibility.
Could you provide the CSS configuration and/or showtech? Can I see those traces?
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...