Use the Event Log object to create, configure, disable and enable system and subsystem level log files to capture system, security, debug, packet, trace and accounting events.

Event Types
EventFacility
System16local0
Debug17local1
Trace18local2
Security19local3
Audit20local4
Accounting22local6
Platform Audit Logs23local7
Console log
lpr
SFTP log
ftp
Kern Log
kern
User Log
user
Daemon Log
daemon
Auth Log
auth, authpriv
Syslog Log
news
NTP Log
uucp
Cron Log
cron
FIPS Log
local5


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:

For each event type, an event class (subsystem) and severity threshold can be configured. Event classes include:

  • Audit
  • Call processing
  • Directory services
  • Network management
  • Policy
  • Resource management
  • Network routing
  • Platform Rsyslog
  • Security
  • Signaling
  • System management
  • Call trace

The ROLLFILE facility provides a means of closing the active log file and opening a new one with an incremented (name) suffix. This facilitates real-time analysis of system events by performing the analysis on closed, rather than opened and growing, files.

Note

 In the DBG and TRC log files, the call-related trace lines for the Node Resource Manager Agent (NRMA) and the Distributed FE (DFE) are tagged with the VNFC-ID and GCID pair in the D-SBC log header.

Note

This is applicable only for OpenStack Cloud platform and does not support other platforms like KVM, VMWare, and so on. Refer to Basic Debugging for more information.

Note

For configuration details, refer to: