SipContainer, Queue Threshold Exceeded

1	Introduction
1.1	Alarm Description
1.2	Prerequisites
2	Procedure

1 Introduction

This instruction concerns alarm handling.

1.1 Alarm Description

The alarm is raised when the thread pool work queue percentage exceeds a configured upper threshold value.

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

Table 1 Alarm Causes
Alarm Cause	Description	Fault Reason	Fault Location	Impact
Queue use exceeds upper threshold value for SIP initial requests	Queue use exceeds the `queueIrUpperThreshold` threshold value	Incorrect configuration	Thread pool work queue	All initial SIP requests are rejected before reaching the application with a 503 response (service unavailable). Initial SIP requests are defined as a SIP initial request and non-sticky HTTP requests when CLB is used.
		System is not dimensioned to handle the engineered capacity
Queue use exceeds upper threshold value for subsequent SIP requests	Queue use exceeds the `queueSrUpperThreshold` threshold value			All subsequent SIP requests are rejected before reaching the application with a 503 response. Subsequent requests are defined as a SIP subsequent request and sticky HTTP requests.
Queue use exceeds upper threshold value for all SIP requests	Queue use exceeds the `queueMmUpperThreshold` threshold value			All SIP requests are dropped before reaching the application without sending a response.

The alarm attributes are listed and explained in Table 2.

Table 2 Alarm Attributes
Attribute Name	Attribute Value
Major Type	193
Minor Type	1283558015
Managed Object Class	JavaSipOverloadProtection
Managed Object Instance	`ManagedElement=<node_name>,JavaSip=clusterName:<cluster_name>:instanceId:<id>,JavaSipOverloadProtection=1`
Specific Problem	SipContainer, Queue Threshold Exceeded
Event Type	processingErrorAlarm (4)
Probable Cause	x736UnspecifiedReason (418)
Additional Text	⁽¹⁾
Perceived Severity	One of the following: critical(3): All SIP requests are dropped before reaching the application without sending a response. major(4): All subsequent SIP requests are rejected before reaching the application with a 503 response. minor(5): All initial SIP requests are rejected before reaching the application with a 503 response.

(1) No additional text exists.

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 conditions are met:

A SipContainer, Queue Threshold Exceeded alarm is raised.
An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2 Procedure

Do the following:

Navigate to the JavaSipOverloadProtection managed object, for example:
>dn ManagedElement=NODE06ST,JavaSip=clusterName:traffic:instanceId:3,JavaSipOverloadProtection=1

View the heap memory overload protection configuration:

(JavaSipOverloadProtection=1)> show

The following is an example output:

JavaSipOverloadProtection=1
[...]
   queueOverloadProtection=true
[...]
   enabled=true
   queueIrLowerThreshold=80
   queueIrUpperThreshold=90
   queueMmLowerThreshold=93
   queueMmUpperThreshold=98
[...]
   queueSrLowerThreshold=80
   queueSrUpperThreshold=90
[...]

Provide configuration information and order the planning department to replan the setting.
Perform data collection, refer to Data Collection Guideline.
Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
Job is completed.