The GSS can be configured to remove the processed CDR data files. The removal can be done periodically and automatically through a clean-up script (/<install_dir>/gss/bin/cleanup.sh) which can be run as a cron job.00 03 * * * * /<install_dir>/gss/bin/cleanup.sh -ext .p -dirpath <install_dir>/gss/data/extradata -clnintvl 7 >> /gss/log/cleanup.log 2>&1Adding the above entry to the crontab table instructs the system to execute the clean-up script every day at 3:00 AM and to delete all the files with a .p file extension that are older than the maximum storage period, 7 days.00 03 * * * * /<install_dir>/gss/bin/cleanup.sh -ext .p -dirpath /sharedgss/gss/clustgss1_log/gss/ -clnintvl 7 >> /sharedgss/gss/clustgss1_log/cleanup.log 2>&1Important: The command suggested for this step assumes that you have the vi editor set as the system’s default text editor, if not then use the appropriate exit command.
Step 5 View the changes in the crontab file by entering the following command:Each component and most processes generate their own log files to track activity, errors and warning messages. Use the less command or a a text editor to view the appropriate log.Important: Information inside angle brackets denotes a variable that you defined during the installation process.
There are several console commands available at the command line. Access is gained by moving to the /gss directory where the GSS files were installed.Depending upon the version of the GSS software, the root command will vary. For all versions with an extension number of 70 or lower (e.g., 7.1.67 or 8.0.70) the command is
Displays the version of the GSS software. Only used with serv command. # ./serv status <psmon | postgres | gss | gssfilegen># ./serv status [ <resource_name> |<resourcegroup_name> | <process_name> ]The gss.cfg file can be modified with any text editor but for the modifications to take affect, the server must be rebooted.Caution: Before making changes to a gss.cfg, ensure that there is a write-protected copy of the gss.cfg stored in a separate directory on each node. It is recommended to store the copy in the /<packages>/<gss_version> directory.
The following are the copies of gss.cfg. Besides providing the default GSS configuration values, this information can be copied to replace a damaged gss.cfg.To view a gss.cfg, use the following command:Cluster console commands are accessed from the /<clus_install_dir>/gss directory.If you do not receive similar information, then you need to start GSS which will automatically start GSS, FileGen, PostgreSQL, and PSMON.
• Stand-alone Node - enter the following command:
• GSS Node in Cluster - enter the following command:clresourcegroup manage <Resource Group>
• Stand-alone Node - If you do not receive similar information, then you need to restart the GSS stand-alone node which will automatically start the GSS, FileGen, PostgreSQL, and PSMON. To restart GSS on stand-alone node, refer to Accessing GSS Commands section.
• GSS Node in Cluster - If you do not receive similar information, then you need to restart the GSS node which will automatically stop all processes and then start the GSS, FileGen, PostgreSQL, and PSMON. To restart GSS on a cluster node, refer to Accessing GSS Commands section.If you encounter problems with GSS and need to seek assistance from customer support, you may be asked to send them support detail logs which are generated with the SupportDetail utility script. This script runs system commands and captures the output and resulting logs in an XML file.The SupportDetails utility is found in the <gss_install_dir>/gss/tools/supportdetails directory. There is also a README file that provides details about the use of the script.
Step 1 From the root directory, change to the /<gss_install_dir>/gss/tools/supportdetails directory.
Step 2
Step 3 ./getSupportDetails.pl --level=<number><number> specifies the level of debug actions to run. There are four levels:
•
• output of the following commands: ipcs, ps -eaf, scstat, prtdiagThe script generates a zipped file, gsssupportDetails.tar.gz and puts it in /tmp/log directory. You can e-mail this gzip to customer support for debugging purposes. This information will provide them with a quick but fairly complete view of the status of your system and the configuration.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |