Cisco Cisco Packet Data Interworking Function (PDIF)
ECS Changes in Release 17
▀ ECS Enhancements for 17.0
▄ Release Change Reference, StarOS Release 17
156
New Behavior: Now, if 1st fragment for this frag-chain is received and has tcp header, tcp src/dest ports are extracted.
This fragment will now be mapped to the existing flow (if it exists). If 1st fragment is missing or does not have tcp
header, a new ads with src/dest port = 0 is created. This fragment is sent for rule-matching. The newly created ads is
immediately destroyed once the fragment is processed. This is followed for all such subsequent packets.
This fragment will now be mapped to the existing flow (if it exists). If 1st fragment is missing or does not have tcp
header, a new ads with src/dest port = 0 is created. This fragment is sent for rule-matching. The newly created ads is
immediately destroyed once the fragment is processed. This is followed for all such subsequent packets.
Rule-matching:
Previous Behavior: Dnl fragments on reassembly timeout, matched the rule on default bearer.
New Behavior: Dnl fragments which map to the existing bearer (returned by flow identification), now match rules
installed on flow bearer. For example: If a flow is established and packets start coming on dedicated bearer, then flow
bearer will be dedicated. Now when a dnl fragment comes, it will match the dedicated bearer rules.
installed on flow bearer. For example: If a flow is established and packets start coming on dedicated bearer, then flow
bearer will be dedicated. Now when a dnl fragment comes, it will match the dedicated bearer rules.
CSCup86339 - Assert sessmgr_ipv4.c:10235 :
sessmgr_ipv4_process_user_pkt_part2()
Applicable Products: GGSN, P-GW
Feature Changes
Processing of Data Packets in S2b Handoff for Dormant Bearer
Previous Behavior: During S2b handoff, DCCA was trying to send the bufferred data packets to session manager even
for a dormant bearer. Such dormant bearer existed only at ECS and not at session manager, and thereby resulting in
system crash.
for a dormant bearer. Such dormant bearer existed only at ECS and not at session manager, and thereby resulting in
system crash.
New Behavior: With the current implementation, after OCS response is received, it is verified to determine if the
bearer is in dormant state at ECS. If the bearer is found to be in dormant state, then such buffered packets will be
dropped.
bearer is in dormant state at ECS. If the bearer is found to be in dormant state, then such buffered packets will be
dropped.
CSCuq20248 - Fail planned switchover when OC batch processing is in
progress
Applicable Products: GGSN, HA, HSGW, IPSG, PDSN, P-GW, S-GW
Feature Changes
SRP Switchover Event During Batch Processing for Override Control
When SRP switchover is initiated and the session manager is batch processing the subscribers for Override Control
(OC), the switchover event will fail. Administrator will have to retry the switchover later.
(OC), the switchover event will fail. Administrator will have to retry the switchover later.
CSCuq30728 - PGW:Assertion failure at process_bearer_binding_rsp
Applicable Products: GGSN, P-GW