How to Capture all Log Files on Acme Packet systems including 3820,3900,4500, 4600, 6100, 6300

Asset ID:	1-71-1589489.1
Update Date:	2017-05-30
Keywords:

Solution Type Technical Instruction Sure

Solution 1589489.1 : How to Capture all Log Files on Acme Packet systems including 3820,3900,4500, 4600, 6100, 6300

Applies to:

Acme Packet 4500 - Version S-Cx6.3.x and later
Net-Net 3810 - Version S-Cx6.4.x and later
Acme Packet 6100 - Version S-Cz7.0.2 and later
Acme Packet 6300 - Version S-Cz7.0.2 and later
Acme Packet 3820 - Version S-Cx6.3.7 and later
Acme Packet OS

Goal

How to capture all log files on Acme Packet 3820,3900,4500, 4600, 6100, 6300

Solution

Acme Packet may request all log files be provided from a system to help with troubleshooting an issue.

There is no need to FTP off each individual file. There is a command to create a file archive containing all logs files at the time. This is helpful when there is a need to reboot a system, but want to ensure all logs are captured prior to reboot. This file is saved in a persistent area of memory (/code), so the system can be rebooted and the logs archive retrieved after the system has booted back up.

Procedure:

telnet, ssh, or console into the system and enter "enable" mode:

TAC-SD-150> enable Password:
Enter Archives tool mode by typing "archives" at the prompt

TAC-SD-150# archives
Create a logs file with details of the case number or date. In the example below the name of the file is ticket123456dec29.2008

TAC-SD-150(archives)# create LOGS ticket123456dec29.2008
task done

This tars and gzips the contents of /ramdrv/logs and drops it permanently into /code/logs.
The resulting gzipped tar file can be retrieved by using FTP or sftp, and changing directory to /code/logs .

ftp> cd /code/logs 250 CWD command successful.

ftp> dir 200 PORT command successful.

150 Opening ASCII mode data connection for 'file list'. size

date                                          time       name
--------       ------                       ------    --------
4096        Dec-29-2008             19:25:40   .

4096 Dec-29-2008 19:25:41 ..

1469680 Dec-29-2008 19:25:42 ticket123456dec29.2008.tar.gz

NOTE on Versions:

It is observed that for 6.x.x versions, Archive logs are stored in /code/logs

For 7.x.x versions, Archive logs are stored in /opt/archives

for example:

Acme Packet 4500 - Version S-Cx6.3.x ------> Found in /code/logs

Acme Packet 4500 - Version SCZ7.2.0 -------> Found in /opt/archives

ACME Net-Net 3820 Firmware SCX6.3.9 ---------------> Found in /code/logs
Net-Net 3810 - Version S-Cx6.4.x ------------------> Found in /code/logs
Acme Packet Net-Net 3820 SCZ7.2.0 and later -------> Found in /opt/archives

Acme Packet 6100 - Version S-Cz7.0.2 and later -----------------> Found in /opt/archives
Acme Packet 6300 - Version S-Cz7.0.2 and later -----------------> Found in /opt/archives

* On S-CZ7.0.2 and above package-logfiles command can also be used to capture the logs -

Enter the SBC in super user mode and run command package-logfiles which create a zip archive of log files in directory /opt/logs.The resulting gzipped tar file can be retrieved by using FTP or SFTP, and changing directory to /opt/logs .

The command can also be run with below arguments

all - create a zip archive of log files in directory /opt/logs
name - Specify the name of the saved file
newer-than - Specify a time limit, in days, on the files to be compressed and saved. This option counts backwards, starting with the current day. Thus the option newer-than 5 would compress and save files for the past 5 days only

Syntax

package-logfiles [all] [name <file>.tar.gz] [newer-than <days>]

package-logfiles

Attachments

This solution has no attachment