Guest

Preview Tool

Cisco Bug: CSCur66201 - ASR 5500 not enforcing bearer-id check for BCM:UE-only

Last Modified

Feb 06, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

16.2.2

Description (partial)

Symptom:
In the lab, we have a scenario where, Bearer control mode for 3G-S4 SGSN was changed to BCM= UE only,  as a workaround scenario for IP-Messaging with a plan that PCEF will  not  push TFT's on the UE, while on 3G. ASR is however requesting packet filters in UBReq, which seems to indicate that it's not honoring the BCM=UE_Only received in CCA-I.

 Image Version:                  16.2.2
  Image Build Number:             56875

The GW sends a CCR-I with Network-Request-Support: NETWORK_REQUEST_SUPPORTED (1) for the S4-SGSN, PCRF sends a UE-Only BCM mode (this is as a work around for the device issue) in the CCA-I. However the GW sends a UBR to push TFTs to UE without enforcing the bearer-id check for BCM:UE-only to follow specs defined behavior. Thus hitting the device issue with TFTs failing when pushed to UE on 3G

Conditions:
In the lab, we have a scenario where, Bearer control mode for 3G-S4 SGSN was changed to BCM= UE only,  as a workaround scenario for IP-Messaging with a plan that PCEF will  not  push TFT's on the UE, while on 3G. ASR is however requesting packet filters in UBReq, which seems to indicate that it's not honoring the BCM=UE_Only received in CCA-I.
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)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.