MTAS Error Dump
MTAS

Contents

1Introduction
1.1Prerequisites

2

Supervision

3

Files

1   Introduction

If there is a crash or a failure in a processor or a process, error dump files are generated. These error dump files make it easier to locate the reason for the failure. This document describes which error dump files are generated and where these files are located.

Whatever caused the error dump can also have generated one or several alarms. If the reason for the error dump cannot be found, the error dump file (tgz-files, see Section 3 Files) must be sent to the next level of maintenance support for further analysis.

For more detailed information about logging mechanism, refer to vDicos documentation.

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 tool must be available before performing any procedure in this document:

2   Supervision

The generation of error dumps is monitored by the system. Error dumps are collected, compressed, associated to related error dumps and maintained in the file space where the error dump files are stored. The default value for the number of stored error dump files is 50. The older error dump files are removed if the number of stored error dumps exceeds the threshold, refer to LEM Error Dump and Log User Guide for more details.

3   Files

The log messages from all nodes are transferred to the System Controllers (SCs) for storage to file.

Both Linux and vDicos log messages can be lost during transfer at times of high traffic. These logs are only intended to provide best effort logging.

The dumps directory is created when the first MTAS error dump is generated and contains compressed vDicos process abortion dump files, core dump files, and different other log files collected from locations specified by MO cdclsPkOption=baseCdclsvOptions,cdclsPk=vDicos,cdcls=CDCLSvSite. Files in dumps directory use the following naming pattern: vDicos-<date>-<time>.tgz.

The /opt/cdclsv/storage/log directory contains all the logs for vDicos and vDicos related services.

The /opt/vdchsv directory contains the Load Module relocation repository that is needed for manual backtrace generation. This is included in the archive for situations when the automatically generated backtrace is no longer sufficient.

Note: The directory /opt/vdchsv is only accessible from a Payload (PL).

The /var/log directory contains the syslog files of all nodes.



Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    MTAS Error Dump         MTAS