Cisco Bug: CSCup22790 - SGSN not deleting subs resulting in stale PDP's after GGSN reload.
Dec 26, 2016
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: SGSN not deleting subs resulting in stale PDP's after GGSN reload. Conditions: In the Customer network it is observed that after GGSN reload the SGSN is not deleting all the subs and they are stuck/stale position. As observed those subscribers were not present in the GGSN after reload but were there in SGSN, after manually clearing these subscribers from the SGSN things became fine ( there was low KPI for the PDP activation ). The situation arises when those apn's were not cleared manually ( clear sub apn ) in the GGSN before reloading it, as the same scenario would be in case of un-planned GGSN restart. Customer tried testing that with one APN by not deleting it from GSSN before the reload and experience the same problem of subs not being deleted from the SGSN as soon it detects the path-failure from the GGSN.
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