SBC session border controllers
39
Basic settings
–
Device name
— the device name displayed in the web configurator header (not used in this software
version);
–
Local disk drive for traces —
it is possible to save debugging information (traces) to RAM or to an
installed SSD:
–
default —
debugging information (traces) is saved to RAM;
–
/mnt/sdX —
a path to a local SSD drive, the setting is displayed when a SSD drive is installed.
When you select a drive, a logs directory will be created to store the trace files;
Tracing file storage is available for SSD/SATA drives only; this function is not available for USB
storage devices.
–
Local disk drive for alarm logging
— selection of an SSD drive for saving critical alarm messages to
non-volatile memory. This option may be required for troubleshooting device restart or failure is-
sues.
–
/mnt/sdX —
select a path to a local storage device
.
When this option is enabled, the file
'alarm.txt' containing alarm data will be created on the storage device.
Example of alarm.txt file:
0. 24/09/13 20:03:22. Software started.
1. 24/09/13 20:03:22. state ALARM. Sync from local source, but sync source table not empty
2. 24/09/13 20:03:22. state OK. PowerModule#1. Unit ok! or absent
3. 24/09/13 20:03:31. state OK. MSP-module lost: 1
4. 24/09/13 20:03:34. state OK. MSP-module lost: 2
5. 24/09/13 20:03:38. state OK. MSP-module lost: 3
6. 24/09/13 20:03:42. state OK. MSP-module lost: 4
File format description:
0, 1, 2… — event ordinal number;
24/09/13 — event occurrence date;
20:03:22 — event occurrence time;
ALARM/OK — event current state (OK— alarm is resolved, ALARM — alarm is active).
Table 17 — Alarm message examples
Alarm message
Meaning
Configuration has not been read
Configuration file error
High CPU utilization
High CPU load alarm
Port Scan Detector disabled
Information message about disabled Port Scan protection in
the configuration
The dynamic firewall blocked the new address
A warning about blocking a new address with the reason in
the description
Subscriber registration is restricted
Registration request received, the service of which is
restricted
Call is restricted
A call came in that is not allowed to be serviced
Running firmware V.1.X.X.X
Firmware is running
Slave device has another firmware version
Reserve devices have different firmware versions
No connection with slave
No connection with the reserve device either completely or
on one of the links. In the second case, the parameters will
indicate on which link the connection is lost
Change of state in the reserve group
Renegotiation of the devices in the reserve
