DO NOT SHARE THESE DOCS WITH CUSTOMERS!
This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.
In this section:
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. The SBC releases 7.2.x and 10.1.3 are compliant with FIPS-140-2 and FIPS-140-3 respectively. To verify the current status of FIPS certification, contact the Global Support Assistance Center: Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal Voice: +1-833-RIBBON1 (1-833-742-2661) 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 Types
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
The Event Log object allows you to create event log filters to capture debug, security, system, trace, and accounting events using following parameters:
For security protection, the Netconf interface does not support "/aaa" records.
If using INFO filter level is needed for troubleshooting, the SBC triggers the alarm sonusCpEventLogFileDebugLevelInfoNotification any time the Debug Event Log filter level is set to INFO as a reminder of potential memory congestion due to the accumulation of a large number of Debug Event logs in memory. The alarm includes a warning message to set the filter level to MAJOR. The alarm is enabled or disabled using both CLI and EMA When the filter level is set to Once the troubleshooting is completed, set the filter level to When the filter level is changed, the clear alarm
The SBC records the maximum number of Debug Event logs, which can potentially cause memory to become congested resulting in unexpected or undesirable SBC performance.INFO
, the following events occur: sonusCpEventLogFileDebugLevelInfoNotification
every five minutes.Debug Event Log filter level is set to INFO. Set to MAJOR if finished troubleshooting
on the last modified Debug Event Log file.MAJOR
. The alarms are cleared when the filter level is set to MAJOR
.sonusCpEventLogFileDebugLevelInfoClearNotification
is triggered and a message Debug Event Log filter level is no longer set to INFO
is displayed in the log file.
% set oam eventLog filterAdmin <node name> <event_type: audit | debug | memusage | security | system | trace> <event_class: audit | callproc | directory | netmgmt | policy | resmgmt | routing | security | signaling | sysmgmt | trace> level <info | major | minor | noevents> state <off | on>
Parameter | Description |
---|---|
| Event Log Class Filter configuration table. |
| SBC node name. |
| The type of event log to configure:
|
| For each event type, configure one of the following event:
|
| Minimum severity level threshold for event logging:
Note: Info level logs which are traps or faults are always reported in the system logs. |
| Administrative state of event logging for this event type. Set to “on” if filter entry should take precedence over per-node settings.
|
% request oam eventLog filterStatus <node name> <event_type: audit | debug | memusage | security | system | trace> <event_class: audit | callproc | directory | netmgmt | policy | resmgmt | routing | security | signaling | sysmgmt | trace> resetStats
Parameter | Description |
---|---|
| Event log class filter status table. |
| SBC system name. |
| The type of event log:
|
| Event class for each event type:
|
| Use this control to reset the value of Events Filtered column of the |
The active and standby SBC are designed to turn off INFO level logging if the system becomes congested. The "request oam eventLog infoLevelLoggingEnable clearInfoLevelLoggingDisabled
" command is used to re-enable INFO level logging once it is disabled. See sonusCpEventLogInfoLevelLoggingDisabledNotfication - MAJOR for associated trap details.
To view INFO LEVEL LOGGING DISABLED state, run the following command.
> show table oam eventLog typeStatus INFO TOTAL LEVEL CURRENT FILE FILE TOTAL FILE FILES NEXT LOG LOGGING TYPE FILE RECORDS BYTES FILES BYTES DROPPED ROLLOVER DESTINATION LAST FILE DROP DISABLED ------------------------------------------------------------------------------------------------------------------------------ system 1000005.SYS 216 31756 32 1032744 0 0 localDisk 0000-00-00T00:00:00+00:00 false debug 1000014.DBG 1601 188964 32 27489838 0 0 localDisk 0000-00-00T00:00:00+00:00 false trace 1000005.TRC 0 128 32 5224 0 0 localDisk 0000-00-00T00:00:00+00:00 false acct 1000085.ACT 1 202 32 7592 0 0 localDisk 0000-00-00T00:00:00+00:00 false security 1000005.SEC 7 1047 32 23610 0 0 localDisk 0000-00-00T00:00:00+00:00 false audit 1000005.AUD 1002 186238 32 4267027 0 0 localDisk 0000-00-00T00:00:00+00:00 false packet 1000005.PKT 0 128 32 872 0 0 localDisk 0000-00-00T00:00:00+00:00 false
% request oam eventLog infoLevelLoggingEnable clearInfoLevelLoggingDisabled
Parameter | Description |
---|---|
| Use this command to re-enable info level logging after it becomes disabled due to system congestion. If this command is executed while the system is still congested, this may cause the system to become further congested. Note: Only issue this command once system congestion dissipates. The system may become further congested if this command is executed while the system is still congested |
The SBC Core uses the OAM Event Log memusage command to log the memory usage of each process over a configurable interval. The SBC generates a memory log which is uses to capture and log process heap memory usage over time. The following limitations apply in this release: The number of bytes used by an active process are captured in the memory usage log file: Processes are identified by the log entries encoded by the system. For example, the format of a log entry: The memory usage details are logged to the hard drive in the directory: Use the log number to locate the correct log file. For example: where the 113 03282017 073341.007995:1.01.00.00006.MAJOR .PRS: memusage: 1516445696
/var/log/sonus/sbx/evlog
/var/log/sonus/sbx/evlog/<log number>.mem
<log number>.mem
is the memory usage log file.
% set oam eventLog process memusage state <enable | disable> level <summary | detailed> interval <0...140>
Parameter | Length/Range | Description |
---|---|---|
memusage | N/A | The peer process memory usage configuration details. |
| N/A | Enable this flag to measure the memory usage of each active process.
|
level | N/A | Specifies the level of details to be displayed.
|
Interval | 0-1440 minutes | The time interval, in minutes, to elapse between the recording of each memory usage file to the hard drive. (Default = 5) Note: An interval of 1440 minutes (24 hours) equates to one log entry per day for a process. |
% set oam eventLog platformAuditLogs state <disabled | enabled>
Parameter | Length/Range | Description |
---|---|---|
platformAuditLogs | N/A | Use this object to configure a remote server IP address, port, and protocol type to push the platform audit logs to a remote server. |
| N/A | Enable this flag to allow platform audit logging of administrative, privileged, and security actions.
|
Use Rsyslog to configure a remote server IP address, port, and protocol type to push platform logs of administrative, privileged, and security actions to a remote server.
When platformRsyslog
is enabled, the /etc/
rsyslog.conf
file is configured to send the configured platform logs to the remote syslog server. The remote server's /etc/rsyslog.conf
file must match the configuration of the SBC to receive platform logs. The SBC automatically adds an Access Control List (ACL) rule to send the audit logs through the application layer to the remote server.
The SBC Syslog configuration does not provide a setting for specifying an Interface to use for connectivity to remote syslog servers; instead, the interface is decided using the configured Static Routes. The SBC application automatically creates an ACL to allow connections from the remote server to the mgmt interface.
If traffic to the remote server is routed out of a different interface due to the configured Static Routes, then you must either add a new Static Route to route the traffic out of the mgmt interface, or create a new ACL for that interface.
The following logs are not supported: Monit, Mail, Printer, dpkg and the /var/log/messages file.
platformRsyslog
is disabled.For a High Availability (HA) pair, the
file is updated both on the Active and the Standby SBCs to push the audit logs to the remote server./etc/
rsyslog.conf
% set oam eventLog platformRsyslog linuxLogs authLog <disabled | enabled> consoleLog <disabled | enabled> cronLog <disabled | enabled> daemonLog <disabled | enabled> fipsLog <disabled | enabled> kernLog <disabled | enabled> ntpLog <disabled | enabled> platformAuditLog <disabled | enabled> sftpLog <disabled | enabled> syslogLog <disabled | enabled> userLog <disabled | enabled> servers server<server1 | server2 | server3> port <port #> protocolType <relp | tcp | tls-tcp | udp> remoteHost <host_ip> syslogState <disabled | enabled>
Ensure the Platform Rsyslog state
is set to "disabled" before configuring/re-configuring the IP address, port, and/or protocol type of the remote server.
Parameter | Length/Range | Default | Description | M/O |
---|---|---|---|---|
| 1-3 | 1 | Number of server. | M |
host_ip | N/A | N/A | Host IP of server. | M |
protocol | N/A | TCP | The protocol used to send messages to the Remote Server.
| M |
port | N/A | 514 | Specifies the port used to send messages to the remote Server. | M |
Parameter | Description |
---|---|
| Use this flag to enable/disable the Rsyslog service:
|
To determine which types of logs the Rsyslog service sends to a remote syslog server when the service is enabled, use linuxLogs.
Parameter | Description |
---|---|
| Platform Linux audit log messages ( |
| Console activity messages ( |
| Internal-sftp messages ( |
| Kernal messages ( |
| User-level messages ( |
| System daemon messages ( |
| Auth and authpriv security/authorization messages ( |
| Internally generated syslogd messages ( |
| NTP subsystem messages ( |
| Clock deamon messages ( |
| Fips messages ( FIPS Compliancy
The SBC releases 7.2.x and 10.1.3 are compliant with FIPS-140-2 and FIPS-140-3 respectively. To verify the current status of FIPS certification, contact the Global Support Assistance Center: Ribbon Support Portal: https://ribboncommunications.com/services/ribbon-support-portal Voice: +1-833-RIBBON1 (1-833-742-2661) |
Mandatory parameters required to configure an Event log subsystem event type:
% set oam eventLog subsystemAdmin <system_name> <subsys_ID>
Non-mandatory parameters to configure an Event log subsystem event type:
% set oam eventLog subsystemAdmin <system_name> <subsys_ID> infoLogState <disabled | enabled> maxEventID <0-4.294967295E9> minEventID <0-4.294967295E9>
Parameter | Description |
---|---|
| Subsystem event logging configuration. |
| Name of system. |
| The subsystem/task ID. See Subsystem IDs table below for a list of subsystem IDs. |
| Use this flag to enable/disable event logging of INFO level messages to DBG and SYS logs for the specified subsystem. By default, infoLogSate is enabled for all subsystems.
Note:
|
aka | arm | asg | brm | cam | cc |
chm | cpx | dbl | dcm | debug | dfe |
dht | diamc | dnsc | drm | ds | dsa |
dtls/srtp | ema | enm | enm_am | enm_test | fm |
gcl mbs | gclcomm | gwcm | gwfe | gwsg | h248fe |
h323fe | h323sg | ice | iceapp1 | iceapp2 | iceapp3 |
iceapp4 | iceapp5 | iceapp6 | iceapp7 | iceapp8 | icms_test1 |
icms_test2 | ike | im | ipacl | ipm | kfqdn |
les | license_sm | lvm | lwresd | mgsg | mim |
mrm | mtrm | nim | nrm | nrma | nrs |
pathchk | perfs | perfs | pes | pipe | prsnp |
rgm | rtm | rtma | sbcintf | scpa | sec |
sg | sipcm | sipfe | sipsg | sm | sma |
ssa | ssreq | surrreg | trcrt | trm | xrm |
The syslog
ACL rules are added and removed by enabling/disabling syslogState
and configuring the syslog
log fields.
To guard against overlogging, the SBC logs up to 4,294,976,295 messages per second in the event logs (configurable with set oam eventLog typeAdmin system diskThrottleLimit
), but additional event messages above that threshold are discarded. If log events must be discarded, the SBC writes an error message about the skipped messages in the system (.SYS) log.
The following syntax applies to the set oam eventLog typeAdmin command:
% set oam eventLog typeAdmin <acct | audit | debug | memusage | packet | security | system | trace> cdrFileTransferType <compressed | uncompressed> compressionSupport <both | none | only> compressionDaysToKeep <1-7> compressionCleanupDirectory <alternate directory name> diskThrottleLimit <0-4294976295> encryptFile <disabled | enabled> encryptionPublicKey <encryptionPublicKey_name> eventLogValidation fileCount <1-2048> fileSize <256-65535> fileWriteMode <default | optimize> filterLevel <info> messageQueueSize <2-100> renameOpenFiles <disabled | enabled> rolloverAction <start | stop> rolloverInterval <0-31536000> rolloverStartTime <time> rolloverType <repetitive | nonrepetitive> saveTo <none | disk> servers <syslogRemoteHost | syslogRemotePort | syslogRemoteProtocol> syslogState <disabled | enabled>
Only the Administrator can execute the above command using the audit
and security
attributes:
% set oam eventLog typeAdmin audit...
% set oam eventLog typeAdmin security...
The SBC logs configuration changes made to the encryptFile
and encryptionPublicKey
parameters. For more detailed information, refer to Encrypting Auto-traced Media.
The following syntax applies to the request oam eventLog typeAdmin
command:
% request oam eventLog typeAdmin <acct | audit | debug | memusage | packet | security | system | trace> rolloverLogNow % request oam filterStatus <card name> <audit | debug | memusage | security | system | trace> <audit | callproc | directory | netmgmt | policy | resmgmt | routing | security | signaling | sysmgmt | trace
Only the Administrator can execute the following commands using the "audit" and "security" attributes:
% request oam eventLog typeAdmin audit rolloverLogNow % request oam eventLog typeAdmin security rolloverLogNow % request oam eventLog filterStatus <card name> security security resetStats
The System log displays Info level logs which are traps or faults when the System log filterLevel is configured to log Major and/or Critical events.
Parameter | Length/Range | Description |
---|---|---|
| N/A | Event Log configuration table for configuration items related to each Event Log type. |
| N/A | Specifies the type of event log being configured:
NOTE: packet ( |
cdrFileTransferType | N/A | Write CDRs as compressed, or uncompressed.
|
compressionSupport | N/A | Type of compression.
|
compressionDaysToKeep | 1-7 | The number of days to keep compressed files before deleting. Default = 5. |
compressionCleanupDirectory | N/A | The alternate directory name (containing no slashes) under the evlog file directory from which compressed files are removed after Note
You must create a script to transfer the compressed file to the newly-created directory. |
diskThrottleLimit | 0-4294976295 | Specifies the limit on INFO level messages logged to the disk in one second. A value of 0 disables the limit. The default value is 10000. Note: For the trace log, if tracing is being performed to capture all of the SIP PDU for all of the calls on the system for use in conjunction with Ribbon Analytics, then this value needs to be tuned to accommodate the maximum call load anticipated for the SBC instance. For example, for a call rate of 1350 cps and assuming 14 messages in a basic SIP call (ingress and egress legs), it would require a total of 18,900 messages. Adding this to the default 10000, the recommendation in this case would be to set the limit at 30,000. |
encryptFile | N/A | Specifies whether the packet files are encrypted.
Note: You can configure this parameter only when For more detailed information, refer to Encrypting Auto-traced Media. |
encryptionPublicKey | 128-1024 bytes | This is the RSA public key without ssh-rsa at the beginning of the key contents and without the user email at the end of the key contents. This key uses a minimum of 2048 bits and accommodates public keys of up to 4096 bits in length. Note: This parameter is mandatory when Note: You can configure this parameter only when For more detailed information, refer to Encrypting Auto-traced Media. |
eventLogValidation | N/A | Specifies whether the logs at rest for this log type should be cryptographically hashed. Hashing is only recommended for the security and audit logs. These are the main logs required to triage security issues and do not roll very frequently. Hashing must be disabled for logs that are rolling over frequently as would occur for the trace log if the call rate is 1350 cps and it is being used to capture all SIP PDU's for use with Ribbon Analytics. If logs are being exported using Rsyslog then there is no need to enable Event Log Validation as the logs are copied off the SBC before they could be modified. Refer to OAM - Event Log - Platform Rsyslog.
IMPORTANT: You must disable this control for any logs which are rolling at a very high rate (e.g. capturing trace logs of all SIP PDUs for use with Ribbon Analytics). Hash Notes:
|
| 1-2048 | Specifies the number of event log files that will be maintained for this event type. (default = 32). |
| 256-65535 | Maximum size (in KB) that a single event log file will ever grow to. (default = 2048). Note: Set the file size to 65535 for trace and account logs when attempting to trace all calls on the system for use with Ribbon Analytics. |
| N/A | Event log NFS write mode.
|
| N/A | Logs every possible event. |
| 2-100 | The number of event log message entries to buffer before writing to disk. (default = 10). If capturing all of the SIP PDU messages in the trace log for use with Ribbon Analytics, set this value to 100 for the trace log. |
| N/A | Enable this flag to append an ".OPEN" extension to accounting and files which are open for writing.
Note: You must enable the global callTrace Once |
| N/A | Event log rollover actions.
|
| 0-31536000 | Event log rollover interval, in seconds. Note: When using this service, you must set a value of 15 seconds or more. |
| N/A | Specifies the start time for event log rollover. The format is |
| N/A | Event log rollover type.
|
| N/A | Use flag to specify that the events are saved to disk or not saved.
|
| N/A | Specifies the requested state of the given Event Log type.
Do not disable accounting and audit logs. |
servers | N/A | Configure a remote Rsyslog Server for a single log type:
Note: packet ( |
syslogState | N/A | Enable flag to log events of specified type to syslog.
|
For Hardware and SWe-Based Systems
<System Name>_<timestamp>_xxxxxxx.ACT.gz
...where System Name
is the name of the Redundancy group. Example: SBX30_1571352583_1000018.ACT.gz
fileCount
configured for the accounting log.For N:1 Cloud-Based Systems
< Hostname i.e. VM Name >_<timestamp>_xxxxxxx.ACT.gz
You cannot use the system name because, in an N:1 system, multiple instances running in active mode would have the same system name.
The SBC uses the actualCeName
as the Hostname
because this is the name specified in the user metadata. Example: vsbc1Site1_1571352902_1000003.ACT.gz
fileCount
configured for the accounting log.For 1:1 Cloud-Based Systems
<System Name>_<timestamp>_xxxxxxx.ACT.gz
...where System Name is the actualSystemName
, as this is the name specified in the user metadata. Example: vsbcSystem22_1571348519_1000001.ACT.gz
fileCount
configured for the accounting log.Parameter | Description |
---|---|
| Event Log configuration table for configuration items related to each Event Log type. |
| Specifies the type of event log to roll over:
|
| This control is used with request command to perform a roll-over of the specified log immediately. |