MTAS Performance Measurements
MTAS




Contents

1Introduction
1.1Prerequisites

2
Overview of Performance Management
2.1Performance Measurement Name Convention
2.2MTAS Performance Measurement File Location
2.3Measurement Description Template
2.4MTAS Performance Measurements
2.5Configure Threshold-Based Alarms
2.6Performance Management Report Files
2.7Platform-Specific Measurement Jobs and Counters
2.8Threshold Monitoring Job for MtasChargingBufferedEventsCount
2.9Threshold Monitoring Job for MtasMmtNoSubscriptionCall Received

3
MTAS Measurement Jobs and Counters

4
MTAS Measurement Groups

1   Introduction

This document describes the Performance Measurement (PM) parameters available in the MTAS.

Scope

This document covers the following topics:

Target Groups

This document is intended for personnel involved in initiation of performance monitoring of the MTAS, designing performance, reports, and evaluating performance data of the MTAS.

1.1   Prerequisites

It is assumed that the user of this document is familiar with the Operation and Maintenance (O&M) area, in general.

2   Overview of Performance Management

This section describes the MTAS performance measurements. MTAS reports performance measurement information using Core MW Performance Management.

For more information on Performance Management, refer to the Performance Management.

For more information on the counters and formulas used for Key Performance Indicators, refer to MTAS Performance Indicators and MTAS Signaling Traffic Performance Indicators.

For more information on used terms and acronyms in the Performance Measurement descriptions, refer to Glossary of Terms and Acronyms.

2.1   Performance Measurement Name Convention

Recommended format for performance measurement name is structured in the three parts described and exemplified in Table 1.

Table 1    Performance Measurement Name Structure
 

Node Instance

Object Class

Counter Name

Example:

MTAS

Mmt

InitOrigSessOk

The QoS counter names guide the operator where to take possible actions, as follows:

2.2   MTAS Performance Measurement File Location

The default file location for the performance measurement XML files is:
/cluster/storage/no-backup/nbi_root/PerformanceManagementReportFiles/

The report files have a default preventive maintenance policy in which the maximum number of PM report files is 1000.

If the preventive maintenance limit is exceeded, the oldest files are automatically deleted.

2.3   Measurement Description Template

Each parameter listed in this document is described as follows:

2.4   MTAS Performance Measurements

The MTAS provides measurements supporting the following features:

2.5   Configure Threshold-Based Alarms

Threshold-based Alarms can be configured for the measurement types that have threshold alarm support by defining Threshold Monitoring Jobs.

For information on how to create Threshold Monitoring Jobs refer to Create Threshold Monitoring Job.

2.6   Performance Management Report Files

Performance measurement results are reported in XML files, which must be transferred out of the MTAS node using the secure File Transfer mechanism.

For more information on File Transfer, refer to Fetch File in Logical File System.

For information of Performance Management Report File format, refer to Performance Management Report File Format.

2.7   Platform-Specific Measurement Jobs and Counters

This section describes the Platform Performance measurements with links. For information about the measurements, refer to Managed Object Model (MOM).

2.8   Threshold Monitoring Job for MtasChargingBufferedEventsCount

The threshold Monitoring Job for PM measurement Counter MtasChargingBufferedEventsCount has the threshold job parameters and values detailed in Table 2.

For more information on how to create Threshold Monitor Job refer Create Threshold Monitoring Job.

Table 2    Threshold Job Parameters for MtasChargingBufferedEventsCount

Parameter Name

Parameter Value

granularityPeriod

FIVE_MIN

thresholdRateOfVariation

PER_GP

thresholdHigh

10000

thresholdLow

8000

thresholdDirection

INCREASING

thresholdSeveritythresholdSeverity

MAJOR

2.9   Threshold Monitoring Job for MtasMmtNoSubscriptionCall Received

The threshold Monitoring Job for PM measurement Counter MtasMmtNoSubscriptionCallReceived has the threshold parameters and values detailed in Table 3.

For more information on how to create Threshold Monitor Job, refer Create Threshold Monitoring Job.

Table 3    Threshold Job Parameters for MtasMmtNoSubscriptionCall Received

Parameter Name

Parameter Value

granularityPeriod

ONE_HOUR

thresholdRateOfVariation

PER_GP

thresholdHigh

300

thresholdLow

150

thresholdDirection

INCREASING

thresholdSeveritythreshold Severity

MINOR

3   MTAS Measurement Jobs and Counters

In this section, the performance measurements defined in the MTAS are described in detail.

Node-Level Measurements

Service-Specific Measurements

Function-Specific Measurements

Interface-Specific Measurements

4   MTAS Measurement Groups

This section lists the performance measurement groups with links. For information about the measurements, refer to Managed Object Model (MOM).

Legal | © Ericsson AB 2017–2019