Cisco Bug: CSCuq51764 - [gn-gp]: Rule failure should not happen on UB Req rejection
Jan 28, 2017
- Cisco ASR 5000 Series
Known Affected Releases
Symptom: During Ho from 3G to 4G , when default bearer QoS modification is initiated from PCRF & new rule is sent to match with new default bearer QoS , if access side rejects UB request for some reason, then in such case default bearer QoS is not modified as expected but new rule which is sent also not installed. Create bearer request is expected for this rule which is not coming. Conditions: 1. Establish a 3G call (CPC has no CF/PCO). PCRF sends default-eps-bearer-qos along with a rule to match. PCRF enables Default-Eps-bearer-QoS-Change, QoS-Change, RAT-Change, Default-EPS-Bearer-QoS-Change-Failure, APN-AMBR-Modification-Failure trigger. PCRF also sends AMBR. 2. Handover to LTE happens. Different AMBR comes from access side, PCRF sends same AMBR along with different Default-EPS-Bearer-QoS along with the same rule with matching QoS. The update is rejected from access side. ISSUE : For event trigger 21 ccr-u is sent , in cca-u new default bearer QoS & rule is sent with new Qos , UB Req is rejected , default bearer QoS modification failed. but at this point , CCR-U generated with [V] [M] PCC-Rule-Status: INACTIVE (1) , [V] [M] Rule-Failure-Code: RESOURCE_ALLOCATION_FAILURE (10), [V] [M] Event-Trigger: DEFAULT_EPS_BEARER_QOS_MODIFICATION_FAILURE (34) . WHY Rule failure for rule sent in cca-u here ??? Instead directly CB req should initiate with new QoS sent.
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