Cisco Bug: CSCup13397 - GW returns wrong "Default-EPS-Bearer-Qos-modification-failure" on attach
Jan 28, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: Problem Details: The PGW is incorrectly reporting "Default-EPS-Bearer-Qos-modification-failure" to PCRF on initial attach. The reporting of the Event-trigger to PCRF, the PGW incorrectly indicating QCI ?5 as default bearer, while is should be QCI 8. - Create Session Request ? PKT# 29 - CCR-I to PCRF (with the HSS provided QoS ? 8 , ARP ? 10) - PKT # 36 - CCA-I from PCRF installs rule RTRRule3300 (with Default bearer QoS ? Qci ? 8) - PKT# 37 - CCR-I to RTR. PKT # 38 - CCA-I to RTR (Successful) - PKT# 39 - CCR-U to PCRF (DEFAULT-EPS-BEARER-QOS-MODIFICATION-FAILURE) with Default QoS, QCI ? 5. PKT# 40 <<<<< This is where the issue appears to be - Create Session Response (successful with QCI ? 8) - PKT# 44 - CCA-U from PCRF sends Default-EPS-Bearr-QoS with QoS-QCI ? 5 # PKT# 42 This is forcing PGW to send the update bearer request. Rightfully the access side/MME is rejecting the UBRequest. Conditions: Normal use.
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