Cisco Bug: CSCvt52240 - [BP_PCT CUSP] Flow is getting set as ineligible if any discard action is hit mid-flow
Sep 17, 2020
- Cisco ASR 5000 Series
- Cisco ASR 5500
Known Affected Releases
21.15.29 184.108.40.206000 21.15.30 21.19.0 21.19.n1
Symptom: Reject reason "Unsupported Flow Action" is incorrectly set even though CUSP is actually enabled on the TCP flow. Conditions: The issue may be observed in any of the following conditions occur after CUSP is already enabled on the TCP flow: 1. FUI redirect/restrict rules are installed on the flow. 2. Packets of the flow get dropped due to bandwidth limiting. 3. Flow or session is terminated due to charging-action taken on the flow.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases