Cisco Cisco Packet Data Gateway (PDG)
HDD Storage
Overview ▀
GTPP Interface Administration and Reference, StarOS Release 19 ▄
445
gateway. At the same time, this was implemented in a way that does not require any addition or modification to the
existing mediation/billing systems.
existing mediation/billing systems.
Supported Records on HDD
This section describes the various records supported on the HDD:
Accounting Request Records (ACR)
The Accounting Request Records are types of CDRs that contain offline charging information generated by the
Diameter Rf interface. If all the Diameter servers configured in a group are down, ACRs are written to files in formats
supported by the external node and stored on the HDD. These files are created when the chassis does not have
connection with the CDF. From the HDD, ACR files can be pushed/pulled using FTP/SFTP protocols.
Diameter Rf interface. If all the Diameter servers configured in a group are down, ACRs are written to files in formats
supported by the external node and stored on the HDD. These files are created when the chassis does not have
connection with the CDF. From the HDD, ACR files can be pushed/pulled using FTP/SFTP protocols.
Important:
ACRs are supported in 10.0 and later releases.
In StarOS releases prior to 12.3, in the standby chassis if HDD is configured and if the HDD profile status is
unavailable, the pending Diameter accounting requests will be removed. Release 12.3 onwards, when HDD is
configured in the standby chassis, irrespective of HDD profile status, the Diameter accounting requests will be retried to
HDD until it successfully writes in to HDD. Any misconfiguration of HDD can result in Diameter accounting requests
being piled up in to accounting archive list in the standby chassis. The only way to clean up the list can be either un-
configure the HDD or configure active HDD properly.
unavailable, the pending Diameter accounting requests will be removed. Release 12.3 onwards, when HDD is
configured in the standby chassis, irrespective of HDD profile status, the Diameter accounting requests will be retried to
HDD until it successfully writes in to HDD. Any misconfiguration of HDD can result in Diameter accounting requests
being piled up in to accounting archive list in the standby chassis. The only way to clean up the list can be either un-
configure the HDD or configure active HDD properly.
Directory Structure: By default, the ACR records are placed in the following directory paths:
RAM-disk: /records/acr/<policy_name>/
HDD: /hd-raid/data/records/acr/<policy_name>/
File Formats: Currently, file format1 to format10 are supported.
Supported Products: HSGW, P-GW, S-GW
Charging Data Records (CDR)
A Charging Data Record is a formatted collection of information about a chargeable event. The CDRs generated by
GGSN/SGSN are sent to an external node for storage. CDRs are written to files in formats supported by the external
node and stored on the HDD. From the HDD, CDR files can be pushed/pulled using FTP/SFTP protocols.
GGSN/SGSN are sent to an external node for storage. CDRs are written to files in formats supported by the external
node and stored on the HDD. From the HDD, CDR files can be pushed/pulled using FTP/SFTP protocols.
For information on how to configure push functionality, refer to the