1 Overview

This instruction concerns alarm handling.

1.1 MRF Instance Overloaded Alarm Description

This alarm is a primary alarm. The alarm is issued by the MrfInstance Managed Object (MO). The severity of the alarm is Major.

The MRF Instance Overloaded alarm is received when 100% of the available processing capacity is used in MRF instance functions. The following functions are monitored:

MRF Application processor load
Media Stream Processing load
IP Pipeline load
IP Pipeline vSwitch load

The alarm detects MRF instance functions that are limiting the call handling capacity. It indicates that new virtual machines must be urgently created for MRF. If the alarm does not cease after a short period, the cluster reached the upper limit of virtual machines.

The possible alarm cause and alarm locations are explained in the table below.

Table 1 Alarm Causes
Cause	Description	Reason	Location	Impact
The amount of MRF traffic is too high.	Traffic has reached the available processing capacity.	High volume of MRF traffic. Possible reasons include disturbance in a network or incorrect network dimensioning.	Network.	No impact.

The alarm is updated in the following cases:

A function that is not yet in additionalText reaches the 100% limit. The function is added to additionalText.
A function that is in additionalText goes below the 90% limit. The function is removed from additionalText.
A change occurs in the load of the overloaded entities, and the new status lasts at least 30 seconds.

The alarm is ceased in the following case:

All MRF instance functions (MRF Application, Media Stream Processing, IP Pipeline, and IP Pipeline vSwitch) are running under the 90% of available processing capacity for at least 30 seconds.

The following are the consequences for the node if the alarm is not solved:

Only emergency and priority calls are accepted.
MRF traffic will continue to exceed the capacity limit.

The alarm attributes are listed and explained in Table 2.

Table 2 Alarm Attributes
Attribute Name	Attribute Value
Major Type	193
Minor Type	5308422
Managed Object Class	MrfInstance
Managed Object Instance	ManagedElement=1,MediaResourceFunction=1,MrfResource=1,MrfInstance=<mrf_instance>
Specific Problem	MRF Instance Overloaded
Event Type	QualityOfServiceAlarm (3)
Probable Cause	systemResourcesOverload (207)
Additional Text	100% of MRF instance capacity is used. Detected in: <List of MRF instance functions>; uuid:`<uuid>`⁽¹⁾
Perceived Severity	major (4)
isStateful	true

(1) <uuid> is the identity of the Virtual Machine from which the alarm is issued.

2 Procedure

The following procedure describes how to cease a MRF Instance Overloaded alarm.

2.1 Cease the MRF Instance Overloaded Alarm

Prerequisites:

You have logged in to the node.

Steps

View currently active alarms and browse the alarm log.
Check if other nodes in the network handling the same type of traffic are functioning correctly and there are no factors that temporarily cause heavy traffic, for example, public events. If a clear reason for increased traffic is found, consider to expand the capacity by adding more VMs to the cluster. If it is also possible to estimate when the situation disappears, consider removing the added VMs from the cluster after traffic went back to normal. If the situation disappears, go to Perform Concluding Routines.
Create a measurement job with the appropriate PM counters, and compare the results with the available processing capacity. Follow the counters periodically, and if the counter value shows an increase in MRF traffic that seems permanent, go to Step 4. If the readings show a temporary peak, go to Perform Concluding Routines.
Add additional VMs to the cluster to increase processing capacity. If the needed capacity is over the agreed capacity limit, contact the Cloud Administrator for capacity expansion, and contact Ericsson support.
If the alarm does not cease, consult the next level of maintenance support. Further actions are outside the scope of this instruction.

2.1.1 Perform Concluding Routines

Steps

Make a report.
The job is completed.

Copyright	© Ericsson AB 2016, 2017. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.
Disclaimer	The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.