Preview Tool

Cisco Bug: CSCuq15304 - Out-Of-Order timeout expires unexpectedly leading to misbilling

Last Modified

Dec 26, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases


Description (partial)

When using active-charging and ruledefs to differentiate billing for different flows, it might be that for some flows which contain a lot of out-of-order packets (and retransmitted packets), the OOO timeout might fire unexpectedly.
In this case the rest of the flow will be L4 matched (and the relevant L7 ruledef will no longer be hit).

This will happen very rarely and only for flows which have a lot of retransmits/out-of-order packets.
The likelihood of this occurring depends on the OOO timeout configured (by default: 5 seconds)
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.