Preview Tool

Cisco Bug: CSCuq74155 - Function: egtpc_handle_modify_bearer_req_evt(100)

Last Modified

Dec 25, 2016

Products (1)

  • Cisco ASR 5000 Series

Known Affected Releases

Description (partial)

Seen "Assertion failure at sess/egtp/egtpc/egtpc_evt_handler_func.c:4350" during call model run along with task kill script.

Probable Scenario:

1) Attach and Activate (Primary and Secondary)
2) IU release, Release Access Bearer
3) Downlink Data, Sent Paging Request (Primary and Secondary)
4) Paging Resp and Sent RAB Estb Req (Primary and Secondary) and waiting for RAB Resp
5) Iu Release Req(Moved state from SMA_ST_Downlink_Data_Pending_RAB_Assign_Resp to SMA_ST_Downlink_Data_Pending_Complete)
5i) Iu Release Complete at state SMA_ST_Downlink_Data_Pending_Complete, no handler
6) Again Iu Release Req at state SMA_ST_Downlink_Data_Pending_Complete
7) Send Abort Proc first (which brings Primary state to ACTIVE) 
8) Restart Pending Procedure and start Downlink Data Indication (gtpu packets in buffer) 
   Here we post Downlink Data Indication only to Primary and Secondary.
   Primary received event S4_SMN_EVT_DOWNLINK_DATA_IND at state S4_SMN_ST_EPS_BEARER_ACTIVE and 
   Secondary received event S4_SMN_EVT_DOWNLINK_DATA_IND at state S4_SMN_ST_DOWNLINK_DATA_PENDING_COMPLETE, no handler.
9) Sent Paging Request and waiting for Response (Only Primary is waiting for Response)
10) when stack unwinds at step 7, it starts preservation only for Secondary because Secondary QoS is conversational.
(If we post Downlink Data Indication at step 8 to Secondary as well, then secondary will move to 
11) Continue Iu release (will move to Preservation call flow) because Secondary QoS is Conversational.
12) Paging Resp Received and Send RAB Request for Primary
13) Got Modify PDP from UE and sent Modify Bearer Command by Secondary and waiting for Response
14) Received RAB Resp for Primary and Sending MBR for Primary <--- Crash observed because Secondary is at UPDATE_BEARER_PENDING at EGTP du to Modify procedure
Bug details contain sensitive information and therefore require a 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.