Data Collection Guideline for MTAS

MTAS

1	Introduction
1.1	Prerequisites
2	Workflow
3	Mandatory Data
3.1	General Data to Be Collected
3.2	Data Collected Based on Specific Problems
4	Collecting Data
4.1	Collecting Data Using MTAS Data Collection Feature
5	Other Useful Information

1 Introduction

This document describes the procedure to collect data from an MTAS node not working as expected.

Correct information included in Customer Service Requests (CSRs) or Trouble Reports (TRs) reduces answering lead times.

Consider the recommended printouts and tracings listed in the document as requirements for meaningful CSR/TR analysis. If necessary data, descriptions, or enclosures are missing, it can result in more data requests from the Ericsson Customer Support.

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 virtualized environment and the MTAS. It is assumed that the reader is familiar with concepts, terminology, and abbreviations within these areas.

1.1.1 Parameters

Necessary parameters when performing data collection of the MTAS are shown in Table 1.

Table 1 Installation and Configuration Parameters
Name	Value	Description
oam-vip	____.____.____.____	The external VIP address of the O&M network. For an explanation of the VIP address concept, refer to the following document: • Virtual IP Address Management
linux_user_name		The platform administrator name on the SC processors.
linux_user_password		The platform administrator password on the SC processors.

1.1.2 Tools

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

A workstation with SSH client

2 Workflow

The workflow for collecting data from the MTAS node is as follows:

Collect mandatory data that is needed in connection to any problems experienced. Go to Section 3 Mandatory Data.
Collect specific data based on the type of problem that is experienced. Go to Section 3.2 Data Collected Based on Specific Problems and the collecting procedures specified in Section 4.1 Collecting Data Using MTAS Data Collection Feature.
Collect other useful information in case it is available within an acceptable amount of time and effort. Go to Section 5 Other Useful Information.

3 Mandatory Data

The data described in this section is always to be included in a CSR/TR.

It is important that data is collected as soon as possible after the problem has occurred as the relevant data can be lost if this activity is postponed.

3.1 General Data to Be Collected

The following types of data are to be collected:

Version information of the MTAS product and other relevant nodes.
A detailed description of the problem and for which scenarios the problem has been observed.
If known, a detailed step by step description of how the fault can be provoked.
Information about alarms and notifications that can be related to the observed problem.
References to other CSR/TR problems, which have been observed when the fault occurred. Slightly rewritten
Complete node configuration, exported from the Configuration Management browser.
Information about recent configuration changes, software upgrades, and similar activities that have been performed.
Values of MTAS counters *Error, *Failed, *NoKE, and ‘ *NoKI; Refer to section Checking Counters in MTAS Health Check.
Any crashcollector files that can be related to the observed problem.

3.2 Data Collected Based on Specific Problems

This section describes different types of data based on specific problem types that can be collected. The data types to be collected and included in a CSR/TR depend on the problem experienced.

This section describes different types of data that can be collected. The problem experienced is the source to which of the following data types is to be included in a CSR/TR.

3.2.1 Software Versions

The version information for the MTAS software components is to be collected.

3.2.2 MTAS Log Files

The following logging information is to be collected:

vDicos Virtual Machine log files
Processor log files
MTAS application log files
Crash collector files

3.2.3 Routing Information

The following logging information is to be collected:

Routing Information on the SC and PL processors
Configuration of eVIP

3.2.4 Alarms, Notifications, and Events

The MTAS triggers alarms for the most critical events that require operator intervention. The alarm information is accessible through the command lde-alarm. Alerts are also triggered to report relevant events for the operator.

Alarms and notifications information can be found in the FaultManagementLog/alarm and FaultManagementLog/alert directories that are stored on the SC under:
/cluster/storage/no-backup/coremw/var/log/saflog/

Operating Instructions (OPIs) for each event describe the actions to be taken to cease alarms.

A list of the different alarms generated by the MTAS can be found in MTAS Alarm List.

3.2.5 Performance Measurement Counters

Performance Measurement (PM) counters are useful problem indicators. In particular, this includes the PMF counter reports from the period when the faulty situation occurred.

These counters are available with COM File Management in PerformanceManagementReportFiles file group.

Note:: For more information on how to transfer counter-files, refer to File Management.

Alternatively, it is also possible to collect only counter-information for the service to be reported.