Cisco Bug: CSCuw35785 - Sessmgr does not respond to heart beat and is aborted
Dec 24, 2016
- Cisco ASR 5000 Series
Known Affected Releases
220.127.116.11333 18.104.22.168651 19.2.d0 20.0.0 20.0.S0.61526 20.0.v0
Symptom: Sessmgr restart observed. During unplanned migration, sessmgr does not respond to heartbeats. Since it goes into non-responding state, the management processes terminates it with ABORT signal. Conditions: This issue is observed only if call recovery failures occur to all the calls belonging to the sessmgr. There is no direct relationship to the reason for call recovery failure, it may be caused due to unrelated issues.
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