The SBC Edge logging service allows you to troubleshoot issues such as call signaling, call quality and performance by collecting activity logs from its subsystems. These logging records can then be analyzed to diagnose problems and optimize the performance of SBC Edge for your environment.
The SBC Edge system supports the following methods for recording logs:
Local Log configuration (available only on the , Ribbon SBC 1000 v2 equipped with eUSB, and SBC SWe Lite), stores temporary log files directly on the system. Each local log file retains a limited amount of recorded log messages. Local logging is only useful for quick, high level, troubleshooting, and is not recommended (nor suited) for extended troubleshooting sessions.
When troubleshooting Authentication or Authorization issues, you must apply the Authentication log profile. See Managing Subsystems Logging and Log Profiles for details.
A fully running SBC Edge system can generate a large amount of logging information. For this reason, the SBC Edge logging service allows you to customize the types of logging messages (and level of detail) you wish to be recorded by Managing Subsystems Logging and Log Profiles.
Refer to documentation for details.
This section includes how to capture logs for debugging Easy Configuration errors as follows:
In the Logs page, click the Logs > Web Error Logs.
View the lighttpd.error.log file.
If Easy Configuration encounters an error condition, the system will roll back the changes made up to that point. To help with troubleshooting, you can view where the roll back began in the lighttpd.error.log file.