Related articles:

Use the Linux Logs window to determine which types of logs the Rsyslog service sends to a remote syslog server when the service is enabled. 

On the SBC main screen, go to All > OAM > Event Log > Platform Rsyslog > Linux Logs. The Linux Logs window opens. 

Figure 1: Linux Logs Window

By default, the Rsyslog service is disabled for all types of logs. To configure which logs are sent by Rsyslog:

  1. Click Enabled adjacent to any log types you want the Rsyslog service to send to the syslog server.
  2. Click Save.

Log Type

Log File Description

Platform Audit Log

Platform Linux audit log messages (/var/log/audit/audit.log)

Console Log 

Console activity messages (/var/log/session/session*)

Sftp Log 

Internal-sftp messages (/var/log/sftp.log)

Kern Log 

Kernal messages (/var/log/kern.log)

User Log 

User-level messages (/var/log/user.log)

Daemon Log 

System daemon messages (/var/log/daemon.log)

Auth Log

Auth and authpriv security/authorization messages (/var/log/auth.log)

Syslog Log 

Internally generated syslogd messages (/var/log/syslog)

NTP Log 

NTP subsystem messages (/var/log/sonus/tmp/ntp.log)

Cron Log 

Clock deamon messages (/var/log/cron.log)

Fips Log 

Fips messages (/var/log/fips.log)


FIPS Compliancy

The SBC 7.2.x release supports FIPS-140-2 and the 10.1.3 release supports FIPS-140-3. FIPS-140-2 is not supported in 10.1.3 and later releases and gets automatically converted to FIPS-140-3 as part of the upgrade.

To verify the current status of FIPS certification, contact the Global Support Assistance Center:

Refer to Event Log - CLI for more information on Rsyslog.


  • No labels