Page History
| Noprint | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
| Panel | |
|---|---|
|
Log Management window provides options to:
- view the log types
- download the logs
- delete the logs.
On SBC main screen, go to Troubleshooting > Call Trace/Logs/Monitors > Log Management. The Log Management window is displayed.
| Caption | ||||
|---|---|---|---|---|
| ||||
The Log Management pane is divided into the two vertical sections:
- Left section provides a list of all the available log types.
Right section provides the details of log management parameters for the log type selected in the left section:
Caption 0 Table 1 Log Management Parameters Parameter
Description
NameSpecifies the name of the log file.
DateIndicates the date when the log was generated.
TimeIndicates 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.
Note This section remains blank until a log type is selected from the list.
Log Types
The following log types are displayed in the Log Management pane:
| Caption | ||||
|---|---|---|---|---|
| ||||
| Log | Description |
|---|---|
| Core Dumps | Core Dumps are used to diagnose and debug the errors generated when SBC or any process crashes. The report of such activities are captured in Core Dumps. It also provides information about the debugging errors in the system. |
| 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. |
| T-shark | T-shark is a tool that analyses network protocol. It captures packet data from the network and save it as packet trace. This is viewed only when the T-shark logs are generated in T-shark tool. For more information, refer to Troubleshooting Tools - TShark. |
| Back Trace | When any process crashes, back-trace of that crash report is stored in Back Trace log. It also provides information about the end-to-end testing of the core dumps. |
| 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 | This stores the user activities on the EMA Platform Mode. For more information, refer to Troubleshooting Tools - User Activity Log. |
| Install Logs | This log stores the process of the SBC application installation. |
| Runtime Diagnostic | Runtime Diagnostic test detects the faults on the system hardware. The test results of the log provides the details whether there is a need to change the faulty hardware or re-install the operating system. For more information, refer to Troubleshooting Tools - Runtime Diagnostic Tests. |
Example Log Parameters
| Caption | ||||
|---|---|---|---|---|
| ||||
To Download Logs
Click
displayed against the respective log.
Caption 0 Figure 1 Download Log File
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.Caption 0 Figure 1 Save Log File
To Delete Logs
| Note |
|---|
Once a log file is deleted, it cannot be retrieved from any location. |
Click
Caption 0 Figure 1 Runtime Diagnostic Test Delete Logs A delete confirmation dialog box is displayed.
Caption 0 Figure 1 Runtime Diagnostics Test - Delete Confirmation - Click Delete to remove the log from the list.
Overview
Content Tools