Cisco Cisco Packet Data Interworking Function (PDIF)
S-GW Changes in Release 17
S-GW Enhancements for 17.3 ▀
Release Change Reference, StarOS Release 17 ▄
569
S-GW Enhancements for 17.3
This section identifies all of the S-GW enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the S-GW Administration Guide
for this release.
for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface
Reference for this release.
Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
Important:
This release includes enhancements that are applicable to multiple products. The following lists the
various multi-product enhancements sections, some of which might include content applicable to your S-GW.
AAA Enhancements
CF Enhancements
ECS Enhancements
Firewall Enhancements
GTPP Enhancements
Lawful Intercept Enhancements
MVG Enhancements
NAT Enhancements
SNMP MIB Enhancements
System and Platform Enhancements
CSCut14324 - SGW sending PDP Reject with No resources on 3G Attach dual
Bearer.
Feature Changes
Behavior Change Due to Implementation of Fix for CSCut14324
The fix for CSCut14324 has resulted in a behavior change.
Previous Behavior: When two Create Session Requests are received back to back with zero TEID from the
MME/SGSN, the second CSReq is rejected by SGW with cause "No Resources Available.”
MME/SGSN, the second CSReq is rejected by SGW with cause "No Resources Available.”
New Behavior: When two Create Session Requests are received back to back with zero TEID from the MME/SGSN,
the SGW handles both CSReqs and sends a CSRsp with cause "Request Accepted" for both PDNs.
the SGW handles both CSReqs and sends a CSRsp with cause "Request Accepted" for both PDNs.
Customer Impact: Operators can see that both the PDNs are successfully created.