для Cisco Cisco Packet Data Gateway (PDG)
HDD Storage
▀ Overview
▄ GTPP Interface Administration and Reference, StarOS Release 19
446
Directory Structure: In releases prior to 16.0, by default, the CDRs are placed in the following directory paths for local
mode:
mode:
RAM-disk: /records/cdr/<gtpp_group_name><vpn_id>/
HDD: /hd-raid/data/records/cdr/<gtpp_group_name><vpn_id>/
In releases prior to 16.0, the CDRs are defaulted to be stored in the following directory paths for GTPP Streaming
mode:
mode:
RAM-disk: /records/cdr/hdd_sec_stor_<gtpp-group-name><vpn-id>/
HDD: /hd-raid/data/records/cdr/hdd_sec_stor_<gtpp-group-name><vpn-id>/
In 16.0 and later releases, by default, the CDRs are placed in the following directory paths for local mode:
RAM-disk: /records/cdr/<gtpp-group-name>_<context-name>/
HDD: /hd-raid/records/cdr/<gtpp-group-name>_<context-name>/
In 16.0 and later releases, the CDRs are defaulted to be stored in the following directory paths for GTPP Streaming
mode:
mode:
RAM-disk: /records/cdr/hdd_sec_stor_<gtpp-group-name>_<context-name>/
HDD: /hd-raid/records/cdr/hdd_sec_stor_<gtpp-group-name>_<context-name>/
File Formats: The GSS file formats, Custom1 to Custom8 are supported.
Supported Products: ePDG, GGSN, SGSN, P-GW, S-GW
Diameter Records
The Diameter Records contain CCR messages generated by the Diameter Gy interface. In cases where the Assume-
Positive interim-quota is allocated, and CCR-T is not reported/answered, the CCR-T message is written to a local file,
and saved in the HDD. This local file and directory information can be fetched and parsed to account for the lost
bytes/usage. The retrieval of the file can be done with the PULL mechanism.
Positive interim-quota is allocated, and CCR-T is not reported/answered, the CCR-T message is written to a local file,
and saved in the HDD. This local file and directory information can be fetched and parsed to account for the lost
bytes/usage. The retrieval of the file can be done with the PULL mechanism.
Important:
This feature requires a valid license to be installed prior to configuring this feature. Contact your
Cisco account representative for more information on the licensing requirements.
Important:
Diameter records are supported in 19 and later releases.
When the
diameter hdd
CLI command is configured in the Credit Control Group Configuration mode, the Gy
application sends the failed CCR-T messages to the CDR module for storing in the HDD. For more information, see the
Command Line Interface Reference guide.
Command Line Interface Reference guide.
Directory Structure: By default, the Diameter records are placed in the following directory path:
RAM-disk: /records/diameter/
HDD: /hd-raid/data/records/diameter/
Supported Products: HA, P-GW
Event Data Records (EDR)
The Event Data Records are responsible for definition, generation, and offloading of EDRs generated in the system (as a
result of occurrence of an event) to the external billing system. EDRs are basically used for content billing purposes,
result of occurrence of an event) to the external billing system. EDRs are basically used for content billing purposes,