Cisco Cisco Packet Data Gateway (PDG)
ECS Changes in Release 17
ECS Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
155
Previous Behavior: Transactional Rule Matching functionality was limited only to the charging rule match bypass.
Also, Accelerated ECS support for post-processing actions was not present.
Also, Accelerated ECS support for post-processing actions was not present.
New Behavior: The Transactional Rule Matching functionality has been extended to bypass post-processing rule
matching as well.
matching as well.
Customer Impact: Accelerated ECS will work for post-processing as well.
CSCup28989 - PGW session mgr memory usage increased in 17.0
Applicable Products: P-GW
Feature Changes
Limitation on Rules Recovery
Previous Behavior: There was no limit set for the number of Override Control (OC) rules / CA / exclude rules to be
recovered.
recovered.
New Behavior: In this release, only 15 OC rules/ CA / exclude rules will be recovered.
CSCup48914 - wsp user-agent ends-with is not getting optimized
Applicable Products: PDSN
Feature Changes
Optimization of WSP User-Agent Rules
Previous Behavior: There were several customer deployments using host based and http referrer based rules. Also
there were quite a large number of rules used with ‘ends-with’ operator for matching the URL, URI, user-agent or host
strings. Such types of rules were unoptimized and were matched with brute-force. This incured a significant cost during
rule matching.
there were quite a large number of rules used with ‘ends-with’ operator for matching the URL, URI, user-agent or host
strings. Such types of rules were unoptimized and were matched with brute-force. This incured a significant cost during
rule matching.
New Behavior: To improve the rule-matching performance, already existing DFA optimizer has been extended to
handle the optimization of these types of rules. As a result, user-agent based rules are now optimized and hence faster.
handle the optimization of these types of rules. As a result, user-agent based rules are now optimized and hence faster.
CSCup73278 - Incorrect ruledef match for frag traffic with reassembly timeout
Applicable Products: P-GW
Feature Changes
Incorrect RuleDef Match
Flow identification:
Previous Behavior: TCP layer info was not extracted for fragments earlier. Thus, for a fragment a new ads with
src/dest port = 0 was created. Subsequent fragments (which timeout) on this flow would continue to match this new ads.
src/dest port = 0 was created. Subsequent fragments (which timeout) on this flow would continue to match this new ads.