Cisco Cisco Packet Data Gateway (PDG)
SAEGW Changes in Release 17
▀ SAEGW Enhancements for 17.3
▄ Release Change Reference, StarOS Release 17
416
CSCuu37427 - Assertion failure
egtpc_handle_create_sess_req_msg_at_sgw_ingress
Applicable Products: SAEGW
Feature Changes
Behavior Change Due to Implementation of Fix for CSCuu37427
The fix implemented for CSCuu37427 has resulted in a behavior change.
Previous Behavior: When two parallel CSReqs with different ebi and 0 TEID were received from the S4-SGSN, the
second CSReq was rejected with cause "No Resource Available."
second CSReq was rejected with cause "No Resource Available."
New Behavior: When two parallel CSReqs with different ebi and 0 TEID are received from S4-SGSN, both of the
CSReqs are processed and the PDNs are created successfully.
CSReqs are processed and the PDNs are created successfully.
Customer Impact:
1. Operators will see that both the PDNs are created successfully after the fix if the two CSReqs are received from
S4-SGSN with 0 TEID and different ebi.
2. If both PDNs are received from the MME then the old behaviour of rejecting the CSReq with cause "No
Resource Available" is applicable.
3. If one CSReq is received from the MME and the other from the S4-SGSN, or vice-versa, with the same or
different ebi, then context replacement is triggered and the second CSReq replaces the existing PDN with a
new PDN.
new PDN.