•
•
Step 1
Step 3 Install and configure the GSS application (see the GSS Installation Management chapter in this guide).
Step 4 Setup the GSS support on the GSN (see the Managing the GSN-GSS Services chapter in this guide).Important: The hardware required for these components may vary depending on the number of clients that require access, other components managed, and other variables.
Important: It is recommended that you have separate interfaces (in IPMP) for mediation device and chassis. Also, for given IPMP, the two interfaces should be on different cards.
Important: If you plan to install software and maintain the servers and applications remotely, it is recommended that you use an X-Windows client.
Important: It is recommended that you have separate interfaces (in IPMP) for mediation device and chassis. Also, for given IPMP, the two interfaces should be on different cards.
Important: If you plan to install software and maintain the servers and applications remotely, it is recommended that you use an X-Windows client.
In addition to the minimum system requirements indicated in the Minimum System Requirements for Stand-alone Deployment and Minimum System Requirements for Cluster Deployment sections, the following section offers information that can help you to plan hardware sizing needs, based on the exact deployment scenario that you are using.
• /globaldevices should be at least 1 GB - This is applicable for Cluster mode only.
• /opt should be at least 10 GB
• /export/home should be the partition used for GSS and PostgreSQL.
• In case of Cluster mode installation PostgreSQL and CDR storage will be on /shareddisk for all cluster node hence may not require 20 GB free disk space.For IPMP configuration, refer to the Configuring IPMP on GSS Server section in the GSS Installation Management chapter.Important: IPMP is a feature supported on Sun® Solaris® provided by Sun Microsystems. The configuration is included in the System Administration Guide. For more information, refer to the Sun documentation.
Important: If none of the following formats meet your needs, you should contact your support representative to enquire about obtaining a customized file format.
• starent Format: This default file format encodes CDRs according to the following conventions:
• Header: No header
•
• EoF marker: \nGSN_<date>+<time>_<total-cdrs>_file<fileseqnum>GSN_<date>+<time>_<total-cdrs>_unacked_file<fileseqnum>
• custom1 Format: This file format encodes CDRs according to the starent file format explained above.Important: The use of either starent or custom1 file formats, imposes a few specific reactions: - files are generated without an extension; acknowledged and unacknowledged files are differentiated by their file names; the system deletes all the files after reaching the maximum storage period (1-7 days) configured during GSS configuration.
• custom2 Format: This customer-specific file format encodes CDRs according to the following conventions:
• Header: 24 byte header incorporating the following information:
• Contents: LEN1CDR1LEN2CDR2LEN3CDR3...LENnCDRn
• EoF marker: No EoF markerGSN_<date>+<time>_<total-cdrs>_file<fileseqnum>.u
• custom3 Format: This customer-specific file format encodes CDRs according to the following conventions:
• Header: No header
•
• EoF marker: No EoF markerGSN_<date>+<time>_<total-cdrs>_file<fileseqnum>.uImportant: The use of either custom2 or custom3 file formats imposes the following actions: - files are generated with the .u file extension (indicating an unprocessed file to the billing system); - the GSS system deletes files with .p extension as part of periodic clean-up.
• custom4 Format: This custom4 format was created to support writing CDRs in blocks. This file format is similar to custom3 file format except CDRs will be written in 2Kbyte blocks in a file.
• Header: No Header
• Contents: CDR1|CDR2FFFFFF|CDR3FFFFF..|..CDRnFFFF|
• EoF marker: No EoF markerImportant: With file format custom4, the files are generated with .u file extension indicating an unprocessed file by the billing system. Typically, the billing system would rename the file with .p extension after processing the files with CDR information. This also informs the GSS system that the file can be deleted during periodic cleanup.
• custom5 Format: This file format is similar to custom3 file format except that the sequence number for CDR file name is of six digits in length ranging from 000001 to 999999.
• Header: No Header
•
• EoF marker: No EoF marker
• custom7 Format: This customer-specific file format contains CDRs converted from ASN.1 format to ASCII format according to the following conventions. Each line in the file consists of one CDR which contains 33 parameters occupying 491 bytes.
• Header: No Header
•
• EoF marker: No EoF marker
• custom8 Format: This customer-specific file format encodes CDRs according to the following conventions:
• Header: No Header
•
• EoF marker: No EoF markerImportant: The custom2 to custom8 file formats are customer-specific. For more information on the file formats, contact your local sales representative.
For more information on CDR accounting attribute elements, refer to the AAA Interface Administration and Reference Guide.The FileGen utility includes an additional feature to generate redundant GSS files. When this feature is enabled, the FileGen utility automatically creates a directory called /<GSS_install_dir>/data_redundant (name cannot be changed). After the original data file is created and stored in the /<GSS_install_dir>/data directory, the FileGen utility creates a hard link between the /<GSS_install_dir>/data_redundant directory and the same tmp file that was used to create the original data file. Effectively, this creates a copy and stores a hard link duplicate in this redundant directory.Important: For information on Switching CDRs from HDD to GSS and Switching CDRs from GSS to HDD procedures, refer to the AAA Interface Administration and Reference Guide.
This feature enables support for multiple data streams from one server or a single cluster setup to utilize multiple instances of GSS with a single installation and multiple databases. In a cluster setup, there is only one installation per node. During installation, GSS is installed at a fixed location (/opt/gss_global directory). The initial GSS installation does not create any GSS instance. Once GSS is installed on both the nodes, the /opt/gss_global/make_gss_instance script utility creates instances as and when needed and validates the conflicting ports/username across the instances.For more information on the installation, uninstallation and upgrade procedures for multiple GSS instances, refer to Multiple Instances of GSS section in the GSS Installation Management chapter.This feature can be enabled after installation by configuring Notif_Disk_Usage_Postgres_Database and Notif_Disk_Usage_Gss_Base parameters from gss configuration file and there is no configuration support from installation script or during installation. For information on configuring these parameters, refer to Modifying a GSS Configuration section in the GTPP Storage Server Administration chapter of this guide.Important: This feature does not support backward compatibility and hence GSN build should always match with GSS build. If GSN build and GSS build mismatches, then disk usage alarm and GSN Storage Server Status CLI will not work as expected at GSN side and some malfunction may occur. In this case GSN and GSS will be functional only if disk usage alarm is disabled and Storage Server Status CLI is not used.
• GTPP Storage Server (GSS) is configured in the same context as the GSN service(s) or any other accounting context. The configuration of the GSN initiates the tasks that communicate with the GSS.
• UDP interface on the GSN is bound to the GTPP Storage Server (GSS). The UDP interface is a proprietary interface used by the GSN system to communicate with the GSS.
3. The GSS FileGen utility retrieves records from the database and generates CDR files. As explained in File Format Encoding for CDRs section, these CDR files have vendor specific extensions and formatting for the billing system to use.
• It starts writing a raw file in /<GSS_install_dir>/data directory with name tmp.Once the files are generated, then the files with .u extensions in the /<GSS_install_dir>/data directory can be pulled by a billing system for the processing of the charging details.
5.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |