Log Management window provides options to:
On SBC main screen, go to Troubleshooting > Call Trace/Logs/Monitors > Log Management. The Log Management window is displayed.
The Log Management pane is divided into the two vertical sections:
Right section provides the details of log management parameters for the log type selected in the left section:
Parameter | Description |
---|---|
| Specifies the name of the log file. |
| Indicates the date when the log was generated. |
| Indicates the time (in HH:MM:SS format) when the log was generated. The time is indicated in the 24-hr format. The time displayed is in Greenwich Mean Time (GMT) zone. |
This section remains blank until a log type is selected from the list.
The following log types are displayed in the Log Management pane:
Log | Description |
---|---|
Core Dumps | Logs the operating system dump information, which consists of the recorded state of the working memory of kernel programs at a specific time, generally when the program is terminated abnormally (crashed). |
Diagnostics Logs | These log files contain the information logged during a System Diagnostics operation of the SBC. |
Event Logs | Event log stores the activities of accounting, system, call tracing, packet capture, security, debugging, and audit in EMA or CLI. It also provides information about the configuration activities of EMA, EMS, and CLI. The logs include system logs, debug logs, core dumps, call trace logs, and packet logs. |
Message Logs | Message log stores the different types of interactive logs. Interactive logs store the system messages appearing on the EMA Platform Mode. |
System Dump | Logs the system dump information, which consists of the recorded state of the working memory of application program at a specific time, generally when the program is terminated abnormally (crashed). |
T-shark | T-shark traces are used to analyze the network issues by capturing the packet traces. These captured packets are saved as .pcap files. |
Back Trace | These traces are used to diagnose the root cause of various system problems. |
Apache | Apache server stores any error/activity from the apache2.access.log process. It also provides information about the interaction between EMA and Apache server. |
Netconf | Netconf stores the details about ConfD and Netconf access. It also provides information about the interaction between EMA and Oracle database. |
User Activity | These log files store the user activities on the EMA Platform Mode. For more information, refer to Troubleshooting Tools - User Activity Log. |
Install Logs | These log files store the process of the SBC application installation. |
Upgrade Logs | These log files capture the process of upgrading an SBC application, or the operating system. |
Runtime Diagnostic Tests | These log files contain information about the runtime environment, events, and errors of the diagnostics tests that runs on the SBC. |
Archived Live Upgrade Logs | These log files serve as an archive of the logs captured stored during the process of undergoing a Live Software Upgrade. |
The log files related to user activities in the EMA are available at the following directory of the SBC: /var/log/sonus/ema/log
Click displayed against the respective log.
Depending on the browser settings, the file either opens in a text viewer automatically or a download confirmation window is displayed. You can view the log in a notepad or save it on local drive.
Once a log file is deleted, it cannot be retrieved from any location.
Click displayed against the respective logs.
A delete confirmation dialog box is displayed.