Cisco Bug: CSCut61839 - Fatal Signal 6: Aborted at client_bounce()
Feb 06, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: Unexpected EgtpinMgr Recovery is observed on active Cisco ASR5000. Conditions: The problem is seen due to an issue with Gx Config, so most of the GnGp handoffs are being rejected. The call model also involves a high number of GnGp Handoffs. Sessmgr sends Update trigger to Demux(EgtpinMgr) on GnGp handoff as peer changes. As handoff is rejected and call is cleaned, additional Delete trigger is being sent to Demux. This creates a congestion at the Demux. The Demux finally reloads unexpectedly when CPU reaches 100%. The Path-Failures due to No-response from peer are also observed as Demux is too busy to handle Echo Rsp from the peer, which are getting dropped & later seen as Path-failures. These path-failures are false ones & peers are responding Echo Rsp on time.
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