Cisco Cisco Packet Data Gateway (PDG)
GTPP Changes in Release 17
GTPP Enhancements for 17.0 ▀
Release Change Reference, StarOS Release 17 ▄
207
HDD: /hd-raid/data/records/cdr/hdd_sec_stor_<gtpp-group-name><vpn-id>
New Behavior: The CDRs are now placed in the following directory paths for local mode:
RAM-disk: /records/cdr/<gtpp-group-name>_<context-name>
HDD: /hd-raid/data/records/cdr/<gtpp-group-name>_<context-name>
For streaming mode, the directory structure is as follows:
RAM-disk: /records/cdr/hdd_sec_stor_<gtpp-group-name>_<context-name>
HDD: /hd-raid/data/records/cdr/hdd_sec_stor_<gtpp-group-name>_<context-name>
CSCuo75702 - CDR module restructuring : Integration changes
Applicable Products: GGSN, P-GW
Feature Changes
Configuration Support for Direct Tunnel Attribute
Previous Behavior: Earlier, the “
gtpp trigger direct-tunnel
” has been used to control the presence of Direct-
Tunnel Record Extensions attribute in the CDR.
New Behavior: Now with the implementation of new CDR framework, a new CLI command “
gtpp attribute
direct-tunnel
” has been introduced to control the presence of Direct-Tunnel Record Extensions attribute in the
CDR.
Customer Impact: Customer will have to use “
gtpp egcdr dynamic-path
” CLI command to use the new CDR
framework. Then, the customer should use the “
gtpp trigger direct-tunnel
” command to trigger CDR for
direct-tunnel, and the “
gtpp attribute direct-tunnel
” to display direct-tunnel in CDR.
Command Changes
gtpp attribute
A new keyword “
direct-tunnel
” has been added to this command to control the Direct-Tunnel attribute to be present
in GGSN/P-GW CDRs.
configure
context context_name
gtpp group group_name
[ default | no ] gtpp attribute direct-tunnel
end
CSCup04619 - PGW-Gz CDR HDD: CGF parse shows few AVPs incorrect
Applicable Products: P-GW