Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is raised when the monitored system resources exceed the configured load regulation thresholds.

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

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Incorrect dimensioning	The load regulation dimensioning is incorrect	System is not dimensioned to handle the engineered capacity	Dimensioning process	Calls are rejected by load regulation
Software fault leading to high resource use	A software fault leads to high resource use	Software fault	Leaked use of resources by software

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	1116165
Source	ManagedElement=<node_name>,LPMSv.lpmsv=LPMSvSite
Specific Problem	LPM, Load Regulation Limit Passed
Event Type	qualityOfServiceAlarm (3)
Probable Cause	systemResourcesOverload (207)
Additional Text	Load regulation rejected on nodes: <list_of_nodes>
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

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:

• An LPM, Load Regulation Limit Passed alarm is raised.

2   Procedure

Do the following:

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