Guest

Preview Tool

Cisco Bug: CSCum58869 - ATT lab: duplication of IRI seen in ASR 15.0

Last Modified

May 21, 2017

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

15.0(16)

Description (partial)

Symptom:
During performing test for Lawful interception, two issues were observed, in the SAEGW mode of operation for a collocated call.
1) Duplication of IRI End records seen.
2) Suspected duplication of IRI continue records as well.

Conditions:
As with the latest implementation, in the SAEGW mode of operation, although the SAEGW has both SGW and PGW running, the LI messages for both HI2 and HI3 interfaces are sent only once, instead of both the SGW and PGW nodes, so as compared to the operation of a SGW and PGW handling calls separately and performing the Lawful interception independently and generating two sets of intercepted packets, in SAEGW mode there will be only one set of intercepted packets.

1) For the condition of IRI end record duplication, during DELETE SESSION REQUEST message processing, both the SGW and PGW parts of the SAEGW were trying to generate a IRI end message, resulting in wrong behavior - This issue has been fixed and needs no further investigation or clarifications.

2) For the condition of IRI continue records, there is an introduction of a feature in the latest release of the 15.0, to support APN AMBR and bearer QoS information updating failure indication, this indication is to inform the PCRF when the APN AMBR or bearer QoS , or both were not successfully accepted at the Access side, to be able to handle and report failure of any one of APN AMBR and QoS information, the PGW always generates two separate update bearer requests towards, the access side, one for each kind of update APN AMBR and QoS information, even though the update of both APN AMBR and QoS information, can be requested by Access side in same MODIFY BEARER COMMAND, or from the PCRF in the same CCR-U (RAR) message. - This is the reason we are bound to see two IRI continue messages.
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.