Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 16
▀ ECS Enhancements for 16.3
▄ Release Change Reference, StarOS Release 16
108
ECS Enhancements for 16.3
This section identifies all of the ECS enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the ECS 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.
CSCup74913 - 17.0:Volume Stat mismatches in case session is in Local Policy
Applicable Products: P-GW
Feature Changes
Flows hitting the static discard flow charging action are not accelerated
Previous Behavior: Acceleration eligible flows matching a rule-action whose charging-action had discard flow action
configured were accelerated. As a result of this feature, there was a charging issue with some flows where packets were
getting discarded due to other reasons (such as bandwidth limiting). Since discarded packets do not go for charging, the
charging buckets that need to be updated in the acceleration path, were not getting recorded. So the accelerated packets
were not getting charged.
configured were accelerated. As a result of this feature, there was a charging issue with some flows where packets were
getting discarded due to other reasons (such as bandwidth limiting). Since discarded packets do not go for charging, the
charging buckets that need to be updated in the acceleration path, were not getting recorded. So the accelerated packets
were not getting charged.
New Behavior: Now, acceleration is not enabled when the packet is being discarded. When there is a packet which is
not discarded and goes for charging, if the conditions are conducive, the flow is accelerated from that point. As a result,
the actions and charging buckets can be recorded.
not discarded and goes for charging, if the conditions are conducive, the flow is accelerated from that point. As a result,
the actions and charging buckets can be recorded.
CSCuq15304 - Out-Of-Order timeout expires unexpectedly leading to misbilling
Applicable Products: GGSN, HSGW, PDSN, P-GW, SAEGW
Feature Changes
Change in ‘Out-Of-Order Timeout’ Functionality
Previous Behavior: Earlier, when using active-charging and ruledefs to differentiate billing for different flows, for
some flows which contained a lot of out-of-order packets (and retransmitted packets), the OOO timeout might fire
unexpectedly; the TCP in-order packets were forwarded and TCP OOO timeout was still being run.
some flows which contained a lot of out-of-order packets (and retransmitted packets), the OOO timeout might fire
unexpectedly; the TCP in-order packets were forwarded and TCP OOO timeout was still being run.
New Behavior: Now, when the TCP in-order packets are received, the list is checked for any pending packets. If there
are any pending packets in the list, the timer is extended so that packet in list can get configured time for reordering.
are any pending packets in the list, the timer is extended so that packet in list can get configured time for reordering.