Policy - HOW TO collect or capture a savelog / savestate / logs

Asset ID:	1-71-1676858.1
Update Date:	2018-03-01
Keywords:

Solution Type Technical Instruction Sure

Solution 1676858.1 : Policy - HOW TO collect or capture a savelog / savestate / logs

Applies to:

Oracle Communications Subscriber Data Management (SDM) - Version SDM 7.0.22 and later
Oracle Communications Policy Management - Version POLICY 7.5.0 and later
Tekelec

Goal

Successfully collect and upload a savelog

Solution

Method of Procedure for collecting Savelogs

The procedure below can be used to collect a savelog from the active server. If the issue involves a standby (replication, communication, etc), the same process should be run on the standby server to collect a standby savelog.

1. SSH into the system as root and change to the "platcfg" user

# su - platcfg

2. Select the "Maintenance" option

Maintenance Option

3. Select "Save Platform Debug Logs"

Save Option

4. Click OK to start creating the savelog file. Change the name to a more specific name if preferred or if uploading more than one savelog (Example: "mpe1a-050514-savelogs.tar.bz2")

OK Option

5. Information is collected and saved to /var/TKLC/log/savelogs/savelogs_plat_results.tar.bz2.

The savelogs file should then be transferred to the submitters local machine and attached directly to the SR, or uploaded to the Oracle SFTP Server (See Doc ID 1676882 for SFTP Instructions).

WARNING: If a server is at or near maximum TPS capacity, the savelog process may disrupt requests and cause DIAMETER_BUSYs.

Attachments

This solution has no attachment