Contents

1   Introduction

This User Guide describes the logs to be used for troubleshooting purposes by Ericsson service personnel in case of faults, when MTAS is running in virtualized environment.

The operating system writes events used for troubleshooting the faults, as all programs do. The logs are stored as files on the System Controllers (SCs).

1.1   Prerequisites

This section describes the possible documents, tools, and required conditions before starting the data collection procedure.

It is expected that the reader has prior knowledge about telecommunication including knowledge about the MTAS and the virtualized environment. It is assumed that the reader is familiar with concepts, terminology, and abbreviations within these areas.

1.1.1   Tools

The following tools must be available before performing any procedure in this document:

• A workstation with SSH client.

2   Current Logs

Error information to be used for troubleshooting can be found in the following logs:

• Syslog - Used by Linux standard "syslog"
• vDicosApplog - Used by the MTAS application
• Console logs - Used by vDicos and the MTAS application

3   Log Files

Messages from all Payloads (PLs) are transferred to the System Controllers (SCs) for storage in respective log files.

When an error has occurred, the logs are compiled into an archive together with the error dump file by the CrashCollector to be sent to Ericsson for analysis. For more details, refer to MTAS Error Dump.

3.1   Syslog

The syslog from each node (SCs and PLs) is stored in a file
/var/log/<node_name>/messages respectively.

In addition to that, the syslog for SCs are also merged into the file
/var/log/messages

Note:  

Based on log size, the directory, /var/log/<node_name>/ can also contain rotated messages.<integer> file from the respective node.
/var/log/<node_name>/messages.1: First rotated messages file from node.

3.2   vDicosApplog

For each application, vDicosApplog is stored in the directory
/cluster/storage/no-backup/coremw/var/log/saflog/MTASAppLogs/vdicos

MTAS log files are stored with the following name template:

• MTAS_<timestamp_start>.log

Note:  

Based on log size, the directory, /cluster/storage/no-backup/coremw/var/log/saflog/MTASAppLogs/vdicoscan also contain rotated MTAS_<timestamp_start>_<timestamp_end>.log files.

3.3   Console Log

The Console logs are stored in directory
/cluster/storage/no-backup/cdclsv/log/lpmsv

The log of each vDicos instance (Virtual Machine (VM)) and processor is saved under the name of that specific VM instance and processor as follows:

• vm<X>-<PL>-<Y>

When a processor starts a new console log, based on log size, the previous log file name is overwritten with the following name format
vm<X>-<PL>-<Y>-<date>.<timestamp>.000.

3.4   Additional vDicos Logs

Additional vDicos log files are stored in the directory

/opt/cdclsv/storage/log/

The log file names created under this directory has the following template:

• <process_name>-<log_source><-instance_id><-timestamp>