Contents

1   Alarm Description

This alarm is raised when a congestion situation occurs in a Media Resource Function Processor (MRFP). The MRFP sends a notification to the MTAS indicating that the MRFP is overloaded.

The MTAS provides a mechanism for an MRFP to report congestion to the MTAS so that the MTAS can reduce the amount of resource requests to the congested MRFP.

The MtasMpController, One or More MRFPs Overloaded alarm relates to connection between the MTAS and an MRFP node. This connection relates to the Media Resource Function Controller (MRFC) function. For more information, refer to MTAS Media Control Management Guide.

The MRFC function is a part of the MTAS. The operation requests are started by request from MTAS services and it operates external MRFPs by use of the standard Mp interface with text encoded H.248 over SCTP.

Note:  

Requests for adding new terminations to the MRFP can be rejected if a critical overload situation occurs.

Table 1    MtasMpController, One or More MRFPs Overloaded Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Congestion in one or more MRFPs.	A congestion situation has occurred in one or several MRFPs.	One or more MRFPs cannot handle the amount of resource requests initiated by MTAS.	One or more MRFPs.	Congested MRFPs might not be able to handle media properly, certain services might not work as expected.

Note:  

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

Table 2    MtasMpController, One or More MRFPs Overloaded Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6619167
Managed Object Class	MtasMpController
Managed Object Instance	MtasFunction.applicationName=MtasFunction,MtasMpController.mtasMrfc=0
Specific Problem	MtasMpController, One or More MRFPs Overloaded
Event Type	qualityOfServiceAlarm (3)
Probable Cause	x733Congestion (308)
Additional Text	-
Perceived Severity	The severity of the alarm can be minor, major, or critical depending on the number of MRFPs that are overloaded and the number of MRFPs that are configured in the system, see Table 3.

Table 3    MtasMpController, One or More MRFPs Overloaded Severity Levels

Number of MRFPs	Number of Overloaded MRFPs	Alarm Severity
1	All	Critical(3)
2	All	Critical(3)
	All but one	Major(4)
>2	All	Critical(3)
	At least one	Major(4)
	One	Minor(5)

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

2   Procedure

2.1   Handle MtasMpController, One or More MRFPs Overloaded

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

1. Depending on how many MRFPs are configured in the system, the severity changes when one or more MRFPs returns to normal operation, see Table 3. When the last MRFP has returned to normal operation, the alarm is cleared. The delay before the alarm is cleared or the severity is lowered is 30 minutes.
2. Check the alarm status, refer to Check Alarm Status. Is the alarm still active or is the severity level the same after 30 minutes?

   Yes: Continue with the next step.

   No: Proceed with Step 5.

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