Acme Packet 3820
 
Acme Packet 6100
 
Acme Packet 4600
 
Acme Packet 4500
 
Acme Packet Legacy Platform Software
 
Acme Packet 6300
 

PLA-Support>Sun Systems>CommsGBU>Session Delivery Network>SN-SND: Acme Service Provider
 

In this Document

Goal

Solution

Created from <SR 3-10279959981>

Applies to:

Goal

 How to configure the SBC to direct process logs to an external server

Solution

 Logs will be rotated on the server as they would be on an SD. A logfile will grow in size until it reaches 1MB at which time it will be rotated. For example if log.sipd reaches 1MB, it will be renamed log.sipd.1 and new entries will continue to be written to log.sipd. This process will continue until log.sipd.12 is full, at which time the oldest log (log.sipd.12) will be purged.

The logfile size may be changed from its default of 1000000 (1MB) by modifying the $maxRotateBytes value in the logger.pl script. The maximum number of logfiles may be changed by modifying the $maxFiles value from its default of 12.

With these instructions logging will be persistent across server reboots.

In the following instructions <CR> stands for Carriage Return (the Enter key).

Please follow the below steps to enable the external process-logging:

On the Solaris server:

1. Login to the server as root.
2. Make an /acmelog directory by typing the following:

          mkdir /acmelog <CR>

3. Place the “logger” and “logger.pl” scripts in /acmelog.
4. Change the owner to root (if required) and make the scripts executable:

        cd /acmelog <CR>
        chown root * <CR>
        chmod +x * <CR>

5. Create a startup script on run level 2:

        ln -s /acmelog/logger /etc/rc2.d/S99logger <CR>

6. Start the logger:

        /acmelog/logger start <CR>

7. You should see the following:

starting Acme Packet logger
# logger.pl: Listening on socket 2500; Logging to '/acmelog' multi=Y rotate=12@1000000

On each SD pair, perform the following:

1. Archive the existing configuration on the SD. See the “Archiving and Restoring Configurations.pdf” document for details on this procedure.
2. SSH/Telnet or go in through the console port to the Active SD in the pair. Make sure you’re on the Active system by typing the following:

show health <CR>

Verify the system’s State is “Active”.

3. From the # prompt on the Active system, type the following. Setting “log-filter” to “logs” will keep the sipmsg.log files on the SDs but write the process logs to the server.

config t <CR>
system system-config <CR>
select <CR>
process-log-ip-address <server_ip>
process-log-port 2500 <CR>
log-filter logs <CR>
done <CR>

4. Type exit <CR> three times to get back to the # prompt.
5. Type save <CR>.
6. Type activate <CR>.
7. Archive the new configuration.

On the Solaris server:

1. Make sure the script is creating directories for each SD and updating the files. Each SD will have its own directory with its wancom0 IP address as the directory name, e.g. /acmelog/10.53.20.19, and each process will have its own logfile, e.g. log.sipd, log.mbcd, log.berpd, acmelog, etc., as shown in the following example.

# cd /acmelog <CR>
# ls –l <CR>

total 24
drwxr-xr-x 2 root other 512 Feb 13 09:58 10.53.20.14
drwxr-xr-x 2 root other 512 Feb 13 09:58 10.53.20.15
drwxr-xr-x 2 root other 512 Feb 13 10:09 10.53.20.19
drwxr-xr-x 2 root other 512 Feb 13 09:58 10.53.20.20
drwxr-xr-x 2 root other 512 Feb 13 09:58 10.53.30.19
drwxr-xr-x 2 root other 512 Feb 13 09:58 10.53.30.20
-rwx--x--x 1 root other 427 Feb 13 09:56 logger
-rwx--x--x 1 root other 3949 Feb 9 12:52 logger.pl

# cd 10.53.20.14 <CR>
# ls –l <CR>

total 110
-rw-r--r-- 1 root other 9088 Feb 13 11:09 log.h323d
-rw-r--r-- 1 root other 37219 Feb 13 11:09 log.radd
-rw-r--r-- 1 root other 8946 Feb 13 11:09 log.sipd

Please note log-filter parameter:

system-config
       process-log-level                 NOTICE
       process-log-ip-address        10.10.10.10
       process-log-port                  2500
       log-filter                             all-fork ==>

The default is to have the logs ONLY sent to the external server. They would not be kept locally. The recommendation is to set it to "all-fork" to allow the logs to be kept internally as well as sent to the external receiver.

Script is attached here . You could run the script on Linux or windows machine.

This solution has no attachment