Cisco Bug: CSCvt39484 - Random Delay between service stop & session STOP even though there is ongoing session
Sep 02, 2020
- Cisco ASR 9000 Series Aggregation Services Routers
Known Affected Releases
Symptom: Random Delay between service stop & session STOP even though there is ongoing session Conditions: The issue observed in customer network from iedge POV is that statsd sends a delayed accounting stats notification (stats type 6) to iedge, while the service (stats type 7) and protocol (stats type 10, 11, 12 and 13) final stats notifications are sent on time as soon as the session goes down. Statsd notifies access clients of final stats notification for a given stats type, ONLY after it has received the final stats update from ALL collectors for a given interface and stats type. As soon as an interface is deleted (session going down), stats mgr is notified by IM of this deletion, and we start an internal timer for 30 secs and wait for all collectors to update us final stats before we trigger a final stats notification to clients. As and when collectors updates us with final stats for a given stats type, we send the notification to stats client (iedge). At the end of 30 secs if we still haven’t got final stats for any of the stats type in our tree (corresponding to that deleted subscriber interface), then we trigger a final stats notification from our side without waiting any further for collectors to update us with final stats, and remove the entry from our tree. This is so that we do not get blocked on a badly behaving collector or a collector that disappeared forever for a different reason.
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