Cisco Cisco Packet Data Gateway (PDG)
HDD Storage
▀ Overview
▄ GTPP Interface Administration and Reference, StarOS Release 16
402
HDD: /hd-raid/data/records/cdr/<gtpp_group_name>+<vpn_id>/
File Formats: The GSS file formats, Custom1 to Custom8 are supported.
Supported Products: GGSN, SGSN, P-GW, S-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,
wherein it is required that a different charging unit be employed for different types of content e.g. HTTP, SMTP, MMS,
etc. EDRs are a type of usage records that are configurable by the operator. EDRs are generated per flow subject to
available configuration.
result of occurrence of an event) to the external billing system. EDRs are basically used for content billing purposes,
wherein it is required that a different charging unit be employed for different types of content e.g. HTTP, SMTP, MMS,
etc. EDRs are a type of usage records that are configurable by the operator. EDRs are generated per flow subject to
available configuration.
Directory Structure: By default, the EDRs are placed in the following directory paths:
RAM-disk: /records/edr/
HDD: /hd-raid/data/records/edr/
File Formats: In this release, EDRs are supported in the Comma Separated Values (CSV) format.
Supported Products: ECS and other products/features using ECS
Event Records
The Event reporting is a mechanism using which subscriber activities like session creation/deletion, bearer
creation/modification/update/deletion are reported to the external server (RTT server). The event report logs assist
network operators in maintaining and troubleshooting the network. The event records are stored as files in the HDD and
these files are later SFTPd to the external RTT server. To store the event records in the form of files, compress the event
record file using the Call Detail Records Module (CDRMOD) which provides support for collecting, storing, and
compressing the event records.
creation/modification/update/deletion are reported to the external server (RTT server). The event report logs assist
network operators in maintaining and troubleshooting the network. The event records are stored as files in the HDD and
these files are later SFTPd to the external RTT server. To store the event records in the form of files, compress the event
record file using the Call Detail Records Module (CDRMOD) which provides support for collecting, storing, and
compressing the event records.
Important:
Event Records are supported in 12.2 and later releases.
Directory Structure: By default, the Event records are placed in the following directory paths:
RAM-disk: /records/event/
HDD: /hd-raid/data/records/event/
File Formats: In this release, Event Records are supported in the Comma Separated Values (CSV) format.
Supported Products: SGSN, S-GW
Reporting Event Data Records (REDR)
Reporting Event Data Records are a type of CDRs that contain EDRs generated on flow end conditions, that is reporting
flow end EDRs and HTTP transaction EDRs. REDR records are written to files in formats supported by the external
node and stored in the HDD. From the HDD, REDR records can be pushed/pulled using FTP/SFTP protocols.
flow end EDRs and HTTP transaction EDRs. REDR records are written to files in formats supported by the external
node and stored in the HDD. From the HDD, REDR records can be pushed/pulled using FTP/SFTP protocols.
Important:
REDRs are supported in 12.2 and later releases.
Directory Structure: By default, the REDRs are placed in the following directory paths: