Cisco Bug: CSCui98507 - Call loss when SGW restoration with same SGW in progress
Jan 28, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: When SGW Restoration feature is ENABLED and SGW restoration is in progress with the same SGW recovered, and starts reusing same TEID range for GTPU sessions prior to restart, there may be 50% call loss. Conditions: This call loss will happen when sessions are in SGW-Restoration-In-Progress state and old SGW recovers back. If MME chooses the same old SGW to recover all the session and recovered SGW chooses same TEIDs for GTPU session in MBReq (which it has assigned to some other call prior to restoration), this results into crash and may result into deletion of the old call. As per the spec 23.007, section 16.1.0 The SGW should ensure as far as possible that previously used TEID values are not immediately reused after a SGW restart, in order to avoid inconsistent TEID allocation throughout the network.
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