Cisco Cisco Packet Data Gateway (PDG)
HDD Storage
▀ Overview
▄ GTPP Interface Administration and Reference, StarOS Release 18
442
Overview
The hard disk was introduced in the ASR 5x00 platform to add storage capability. The first application is used in
CDMA environments to increase buffering for I/O between the gateway and L-ESS to alleviate tight linkage required to
avoid record loss due to overrun on the ASR 5x00 PSC buffers.
CDMA environments to increase buffering for I/O between the gateway and L-ESS to alleviate tight linkage required to
avoid record loss due to overrun on the ASR 5x00 PSC buffers.
The External Storage System (ESS) is a high availability, fault tolerant, redundant solution for short-term storage of
files containing detail records (UDRs/EDRs/FDRs (xDRs)). To avoid loss of xDRs on the chassis due to overwriting,
deletion, or unforeseen events such as power or network failure or unplanned chassis switchover, xDRs are off-loaded to
ESS for storage and analysis to avoid loss of charging and network analysis information contained in the xDRs. The
xDR files can be pulled by the L-ESS from the chassis, or the chassis can push the xDR files to the L-ESS using SFTP
protocol. In the Push mode, the L-ESS URL to which the xDR files need to be transferred to is specified. The
configuration allows a primary and a secondary server to be configured. Configuring the secondary server is optional.
Whenever a file transfer to the primary server fails for four consecutive times, the files will be transferred to the
secondary server. The system running with ECS stores xDRs on an L-ESS, and the billing system collects the xDRs
form the L-ESS and correlates them with the AAA accounting messages using 3GPP2-Correlation-IDs (for PDSN) or
Charging IDs (for GGSN).
files containing detail records (UDRs/EDRs/FDRs (xDRs)). To avoid loss of xDRs on the chassis due to overwriting,
deletion, or unforeseen events such as power or network failure or unplanned chassis switchover, xDRs are off-loaded to
ESS for storage and analysis to avoid loss of charging and network analysis information contained in the xDRs. The
xDR files can be pulled by the L-ESS from the chassis, or the chassis can push the xDR files to the L-ESS using SFTP
protocol. In the Push mode, the L-ESS URL to which the xDR files need to be transferred to is specified. The
configuration allows a primary and a secondary server to be configured. Configuring the secondary server is optional.
Whenever a file transfer to the primary server fails for four consecutive times, the files will be transferred to the
secondary server. The system running with ECS stores xDRs on an L-ESS, and the billing system collects the xDRs
form the L-ESS and correlates them with the AAA accounting messages using 3GPP2-Correlation-IDs (for PDSN) or
Charging IDs (for GGSN).
This release now supports purging/deleting xDR records based on time or volume limit to restrict hard-disk space usage
for charging records. When configured, old records can be deleted based on specified storage or time limits.
for charging records. When configured, old records can be deleted based on specified storage or time limits.
The second application is intended for UMTS environment. Records generated on ASR 5x00 are sent through UDP to
an external storage application running on possibly clustered SUN servers utilizing shared storage. In parallel, records
are sent over GTPP to a CGF. In addition to (e)GCDRs, the hard disk supports SCDRs and MCDRs generated by
SGSN.
an external storage application running on possibly clustered SUN servers utilizing shared storage. In parallel, records
are sent over GTPP to a CGF. In addition to (e)GCDRs, the hard disk supports SCDRs and MCDRs generated by
SGSN.
Important:
The hard disk is not designed to support all features supported by the external storage application and
not intended to replace this application in all situations.
The hard disk is useful for other applications:
Store the Content Filtering static ratings database instead of using FLASH; valuable for other users including
recovery scenarios.
IPMS
Large volume firewall and other DPI information such as applications/particular user, and users/bay station
heretofore not store-able embedded.
The hard drive serves a number of uses in providing storage for various records generated by the mobile gateway that
formerly require buffering or treatment outside of the gateway, necessitating purchase and operation of auxiliary
servers. For 3GPP2 accounts the hard disk is an enhancement to service, and not a replacement. The hard drive is
required to provide non-volatile storage in the ASR 5x00. For 3GPP accounts the hard disk can be used instead of
external storage in networks where storage and record formatting needs can be met by the hard disk. The
communication link between the ASR 5x00 and external storage is removed. GTPP continues to be supported. Files can
be accessed by either GTPP (streaming) or sFTP (file I/O), but not both. At the same time, different files can be
accessed by GTPP or sFTP.
formerly require buffering or treatment outside of the gateway, necessitating purchase and operation of auxiliary
servers. For 3GPP2 accounts the hard disk is an enhancement to service, and not a replacement. The hard drive is
required to provide non-volatile storage in the ASR 5x00. For 3GPP accounts the hard disk can be used instead of
external storage in networks where storage and record formatting needs can be met by the hard disk. The
communication link between the ASR 5x00 and external storage is removed. GTPP continues to be supported. Files can
be accessed by either GTPP (streaming) or sFTP (file I/O), but not both. At the same time, different files can be
accessed by GTPP or sFTP.
Benefits
The HDD functionality provides an additional level of protection to the wireless operator by ensuring the charging
records are preserved in case the Charging Gateway (CGF) goes down or loses connectivity with the ASR 5x00
records are preserved in case the Charging Gateway (CGF) goes down or loses connectivity with the ASR 5x00