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 The SBC releases that are officially FIPS-compliant are releases 5.1, 6.2, and 7.2. For each event type, an event class (subsystem) and severity threshold can be configured. Event classes include: 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.
Event Facility System 16 local0 Debug 17 local1 Trace 18 local2 Security 19 local3 Audit 20 local4 Accounting 22 local6 Platform Audit Logs 23 local7 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
Note
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.
For configuration details, see:
- CLI – Event Log - CLI
- EMA – OAM - Event Log, Accounting and Logs - Event Log
- D-SBC – Distributed SBC
Overview
Content Tools