Cisco Bug: CSCur72019 - RAR-CCR collision with mscc-per-ccr-update single triggering extra CCR-U
Dec 25, 2016
- Cisco ASR 5000 Series
Known Affected Releases
CCR-U messages over Gy are retried to secondary server, though the responses are already received which might result in duplicated messages on both servers. Symptom: CCR-U messages retried to secondary Gy server, even after receiving response. Conditions: This issue is seen only when <diameter mscc-per-ccr-update single> is configured under credit control group and CCR-U's are sent for each RG.
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