1 Alarm Description

This 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.

Table 1 MtasMrfp, Connection to Remote MRFP Node Lost 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 are not working as expected.
		The MRFP node does not work properly, might not be operational.	MRFP node.
			MRFP node.

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

Table 2 MtasMrfp, Connection to Remote MRFP Node Lost 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)

For more information about the alarm information, refer to Handling Alarms.

2 Procedure

2.1 Handle MtasMrfp, Connection to Remote MRFP Node Lost

Prerequisites

This instruction references the following documents:
- Check Alarm Status
- Data Collection Guideline for MTAS
No tools are required.
The following conditions must apply:
- The alarm is raised.
- 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.

Steps

Check the status of the remote MRFP node to verify that MtasMrfpNodeAdministrativeState is set to UNLOCKED and MtasMrfpNodeOperationalState is set to ENABLED.

Navigate to a MtasMrfpNode MO, for example:
>dn ManagedElement=1,MtasFunction=MtasFunction,MtasMediaFramework=0,MtasMrf=0,MtasMpController=0

Show the state of the MtasMrfpNode, for example:

(MtasMpController=0)>show-table -m MtasMrfpNode

The following is an example output where both MRFPs are disabled and MRFP2 has been locked:

=================================================================================================== 
| mtasMrfpNode | mtasMrfpNodeAdministrativeState | mtasMrfpNodeOperationalState | ... | ... | ... |
===================================================================================================
| MRFP1        | UNLOCKED                        | DISABLED                     | ... | ... | ... |
| MRFP2        | LOCKED                          | DISABLED                     | ... | ... | ... |
===================================================================================================

Are the MRFP node attributes set to UNLOCKED and ENABLED?
Yes: Continue with the next step.

No: Proceed with Step 4.
Confirm that the alarm has ceased, refer to Check Alarm Status. Is the alarm still active?
Yes: Continue with the next step.

No: Proceed with Step 6.
Perform data collection using Data Collection Tool with a Full profile. For more information, refer to Data Collection Guideline for MTAS.
Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
Job is completed.

1	Alarm Description
2	Procedure
2.1	Handle MtasMrfp, Connection to Remote MRFP Node Lost