Contents

1   Introduction

This document describes the MtasJc, ICBS Data Not Found Alarm.

1.1   Alarm Description

The Alarm MtasJc, ICBS Data Not Found indicates an unsuccessful lookup of ICBS data in the MTAS database. The location information for which lookup is failed is stated in the Additional Info of the alarm. The alarm indicates a location Information configuration missing in MtasCommonDataAccNetwTypeAccInfo

The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.

The following is a list of the alarm attributes:

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
A Lookup of ICBS Data failed in MTAS because of the missing configuration	Unsuccessful lookup of the ICBS Data in MTAS	Missing configuration in LDAP for the specific access type and access info	Configuration	Lookup is to be Reattempted with home location obtained from the subscriber’s transparent data

The alarm attributes are described in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6619218
Managed Object Class	MtasJc
Managed Object Instance	MtasFunction.applicationName=MtasFunction,MtasServices.mtasServices=0,MtasMmt.mtasMmt=0,MtasJc.mtasJc=0
Specific Problem	MtasJc, ICBS Data Not Found
Event Type	PROCESSINGERRORALARM (4)
Probable Cause	configurationOrCustomisationError(159)
Additional Text	-
Perceived Severity	WARNING
Additional Info	<MCC><MNC><CellID>

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

Before starting this procedure, ensure that the following documents have been read:

• Check Alarm Status
• Fault Management

1.2.2   Tools

No tools are required.

1.2.3   Conditions

Before starting this procedure, ensure that the following conditions are met:

• No ongoing maintenance activities are affecting the network or network elements.
• The user has proper authority to handle configuration management of the network elements.
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2   Procedure

Do the following:

1. Check if an entry exists in MtasCommonDataAccNetwTypeAccInfo with the access information received in the Additional Info of the alarm
2. Define the MO entry with the required key based on the additional information attribute of the event. The key is defined as <accessType>& <access-info> For more information on how to configure MtasCommonDataAccNetwTypeAccInfo refer to Parameter Description for Provisioning MTAS MOCs.
3. Clear the alarm manually using the CLI.

   #ntfsend --notificationClassId=193,101,82 --perceivedSeverity=0

Note:  

The alarm generation can be turned off by setting the mtasJcFailureNotification to DISABLED.