Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is raised by the middleware Model Delivery Function (MDF) service.

The alarm is raised when the MDF attempts to deliver a pending model to a model consumer through a callback, which returns a model error. The model remains in a pending state in a First In, First Out (FIFO) buffer. When the error occurs, the MDF logs the available information to the Service Availability Forum (SAF) system log.

The possible alarm causes and fault locations are explained in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
The delivered model is defect	A model delivered as part of the software package is incorrectly designed by the producer of the package	The model is defect	Model	The function related to the model is degraded
The consumer of the model is defect	A model-driven component, the "model consumer", cannot receive a correctly designed model	The model consumer is defect	Model consumer

Note:  

The alarm can appear as a result of an initial installation or a software upgrade.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	849346562
Source	ManagedElement=<node_name>,CmwSysConfig=1,CmwMdf=1
Specific Problem	COM SA, MDF Detected Model Error
Event Type	processingErrorAlarm (4)
Probable Cause	x736UnspecifiedReason (418)
Additional Text	Core MW MDF detected model error
Perceived Severity	critical (3)

1.2   Prerequisites

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

1.2.1   Documents

This instruction references the following document:

• Data Collection Guideline

1.2.2   Tools

No tools are required.

1.2.3   Conditions

Before starting this procedure, ensure that the following condition is met:

• A COM SA, MDF Detected Model Error alarm is raised.
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2   Procedure

Do the following:

1. Was the alarm raised during initial installation or upgrade?

   Yes: Contact the deployment organization. Proceed with Step 5.

   No: Continue with the next step.

2. Perform a health check, refer to Health Check documentation available in the library.
3. Perform data collection, refer to Data Collection Guideline.
4. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
5. Job is completed.