Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The MtasMrfp, Connection to Remote MRFP Node Lost alarm relates to the connection between the MTAS and a Media Resource Function Processor (MRFP) node. The connection relates to the Media Resource Function Controller (MRFC) function, described in MTAS Media Control Management Guide.

The alarm is not issued for a newly defined and unlocked MRFP, until the MRFP has performed a successful H.248 Service Change to the MTAS node.

The connection between the MTAS and an MRFP node is used by the MRFC function to provide the signalling plane with the possibility to control media in the communications handled by the MTAS. For example, to play network announcements and connect media to conference bridges, by using media resources in the MRFP.

The MRFC function is a part of the MTAS, and does not have the external Mr interface, as specified optionally in the IMS standard. The traffic operation requests are started by request from the MTAS services on an internal API, and it operates external MRFPs by use of the standard Mp interface with text encoded H.248 over SCTP over IPv4.

The alarm is issued in the following situations:

• Communication problem between MTAS and MRFP.

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

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Communication problem between MTAS and MRFP.	The heartbeat on the SCTP link has failed.	The SCTP link between MTAS and MRFP node does not work properly.	SCTP link.	If communication problem prevents MTAS from controlling media resources, certain services is not working as expected.
		The MRFP node does not work properly, might not be operational.	MRFP node.

Note:  

The alarm can appear as a result of the maintenance activity.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6619168
Managed Object Class	MtasMrfp
Managed Object Instance	MtasFunction.applicationName=MtasFunction,MtasMrfc.mtasMrfc=0,MtasMrfp.mtasMrfp=<mrfpMoId>
Specific Problem	MtasMrfp, Connection to Remote MRFP Node Lost
Event Type	communicationsAlarm (2)
Probable Cause	x733LossOfSignal (8)
Additional Text	SCTP link failure, Mrfp MId, where MId indicates the MRFP Identity as configured in the MtasMrfp MOC for the MRFP, which is specified when the MRFP is installed with the MTAS. For more information, refer to Managed Object Model (MOM).
Perceived Severity	Major (4)

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 are read:

• Check Alarm Status
• Fault Management
• LOTC Ethernet Bonding
• Managed Object Model (MOM)

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

This section describes the procedure to follow when this alarm is received.

Do the following:

1. Check for related alarms. For more information, refer to LOTC Ethernet Bonding.
2. Check the status of the remote MRFP node.
3. Confirm that the alarm has ceased. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.