Cisco Bug: CSCuw21465 - ASR5500: rmctrl cpu goes to warn state after service configuration
Jan 28, 2017
- Cisco ASR 5000 Series
Known Affected Releases
19.0.0 20.0.0 20.0.M0.61220 20.0.v0
Symptom: In a minimally configured DPC2 ASR5500 setup that is one DPC2 configured for call processing, one DPC2 as demux and one DPC2 as standby, it was observed that rmctrl gets into warn state due to high CPU utilisation. Furthermore aaamgr initialisation failures were also observed. Conditions: ASR5500 chassis with minimal configuration. Note that issue is irrespective of whether session recovery is configured or not.
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