AudioCodes Mediant 500 E-SBC, User Manual

Page: 719 / 920

User's Manual 54. Configuration Parameters Reference
Version 6.8 719 Mediant 500 E-SBC
Parameter Description
Web: Syslog Optimization
CLI: configure
system/logging/syslog-
optimization
[SyslogOptimization]
Enables the device to accumulate and bundle multiple debug
messages into a single UDP packet and then send it to a Syslog
server. The benefit of this feature is that it reduces the number of
UDP Syslog packets, thereby improving (optimizing) CPU utilization.

[0] Disable

[1] Enable (default)
Note: The size of the bundled message is configured by the
MaxBundleSyslogLength parameter.
CLI: mx-syslog-lgth
[MaxBundleSyslogLength]
Defines the maximum size (in bytes) threshold of logged Syslog
messages bundled into a single UDP packet, after which they are
sent to a Syslog server.
The valid value range is 0 to 1220 (where 0 indicates that no
bundling occurs). The default is 1220.
Note: This parameter is applicable only if the GWDebugLevel
parameter is enabled.
Web: Syslog CPU Protection
CLI: configure
system/logging/syslog-cpu-
protection
[SyslogCpuProtection]
Enables the protection of the device's CPU resources during debug
reporting, ensuring voice traffic is unaffected. If CPU resources drop
(i.e., high CPU usage) to a critical level (threshold), the device
automatically lowers the debug level to free up CPU resources that
were required for the previous debug-level functionality. When
sufficient CPU resources become available again, the device
increases the debug level. The threshold is configured by the 'Debug
Level High Threshold' parameter (see below).

[0] Disable

[1] Enable (default)
Web: Debug Level High
Threshold
CLI: debug-level-high-
threshold
[DebugLevelHighThreshold]
Defines the threshold (in percentage) for automatically switching to a
different debug level, depending on CPU usage. The parameter is
applicable only if the 'Syslog CPU Protection' parameter is enabled.
The valid value is 0 to 100. The default is 90.
The debug level is changed upon the following scenarios:

CPU usage equals threshold: Debug level is reduced one level.

CPU usage is at least 5% greater than threshold: Debug level is
reduced another level.

CPU usage is 5 to 19% less than threshold: Debug level is
increased by one level.

CPU usage is at least 20% less than threshold: Debug level is
increased by another level.
For example, assume that the threshold is set to 70% and the Debug
Level to Detailed (5). When CPU usage reaches 70%, the debug
level is reduced to Basic (1). When CPU usage increases by 5% or
more than the threshold (i.e., greater than 75%), the debug level is
disabled - No Debug (0). When the CPU usage decreases to 5% less
than the threshold (e.g., 65%), the debug level is increased to Basic
(1). When the CPU usage decreases to 20% less than the threshold
(e.g., 50%), the debug level changes to Detailed (5).
Note: The device does not increase the debug level to a level that is
higher than what you configured for the 'Debug Level' parameter.
Web: Syslog Facility Number
EMS: SyslogFacility
[SyslogFacility]
Defines the Facility level (0 through 7) of the device’s Syslog
messages, according to RFC 3164. This allows you to identify Syslog
messages generated by the device. This is useful, for example, if you
collect the device’s and other equipments’ Syslog messages, at one