Contents

1   Introduction

This instruction concerns alarm handling for the Licensing, Capacity Usage Threshold Reached, Major alarm.

1.1   Alarm Description

This alarm is raised when the reserved capacity limit in a capacity license has been reached.

The alarm is issued in the following situations:

• The capacity usage limit has been reached for the Payload Blades / Virtual Machines.
• The capacity usage limit has been reached for the active HLR Profile.
• The capacity usage limit has been reached for the active HSS-IMS Profile.
• The capacity usage limit has been reached for the active HSS-EPC Profile.
• The capacity usage limit has been reached for the active AUC Profile.
• The capacity usage limit has been reached for the Small Generic Profile.
• The capacity usage limit has been reached for the Medium Generic Profile.
• The capacity usage limit has been reached for the Large Generic Profile.
• The capacity usage limit has been reached for the active IoT Profile.
• The capacity usage limit has been reached for the active HSS-EPC 5G Profile.

The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
The licence capacity limit of the capacity profile license has been reached.	The capacity usage limit has been reached.	The requested capacity has reached the total licensed capacity defined in the capacity profile license.	License Manager	Violation of license agreements.
The license capacity limit of the Payload Blades / Virtual Machines capacity license has been reached.	The capacity usage limit has been reached.	The requested capacity has reached the total licensed capacity defined in the Payload Blades / Virtual Machines capacity license.	License Manager	Additional capacity exceeding the usage limit is unavailable.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Auto Cease	Yes
Module	LICENSING
Error Code	6
Timestamp First	Date and time when the alarm was raised for the first time.
Repeated Counter	Number which indicates how many times the alarm was raised.
Timestamp Last	Date and time of the most recent alarm raised.
Resource ID	1.3.6.1.4.1.193.169.14.2.3.<# SUB_LICENSE_SUFFIX>
Alarm Model Description	License Management, Licensing
Alarm Active Description	Capacity Usage Threshold Reached for <#LICENSE_TYPE>, Major
ITU Alarm Event Type	qualityOfServiceAlarm (3)
ITU Alarm Probable Cause	thresholdCrossed (549)
ITU Alarm Perceived Severity	(4) – Major
Originating source IP	Node IP where the alarm was raised.
Sequence Number	Number which indicates the order in which the alarms are raised.

The available values of the <#SUB_LICENSE_SUFFIX> and <#LICENSE_TYPE> variables shown in Table 2 are listed below. The list follows the below format:
"<#SUB_LICENSE_SUFFIX>" for the <#LICENSE_TYPE>.

• "1" for the Payload Blades / VMs.
• "2" for the HLR Profile.
• "3" for the HSS-IMS Profile.
• "4" for the HSS-EPC Profile.
• "5" for the AUC Profile.
• "6" for the Small Generic Profile.
• "7" for the Medium Generic Profile.
• "8" for the Large Generic Profile.
• "9" for the IoT Profile.
• "10" for the HSS-EPC 5G Profile.

For further information about attribute descriptions, refer to the Alarm Format and Description section of CUDB Node Fault Management Configuration Guide, Reference [1].

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

Before starting this procedure, ensure that you have read the following documents:

• CUDB Node Fault Management Configuration Guide, Reference [1]
• System Safety Information, Reference [3]
• Personal Health and Safety Information, Reference [4]

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

If the alarm is raised, then refer to the License Management, Capacity Usage Threshold Reached, Reference [5] document for the procedure to perform.

Note:  

Perform only the actions that are applicable for LM deployments using ELIM license key files. The applicable severity is "Major".

Glossary

For the terms, definitions, acronyms and abbreviations used in this document, refer to CUDB Glossary of Terms and Acronyms, Reference [2].

Reference List

CUDB Documents
[1] CUDB Node Fault Management Configuration Guide.
[2] CUDB Glossary of Terms and Acronyms.

Other Ericsson Documents
[3] System Safety Information.
[4] Personal Health and Safety Information.
[5] License Management, Capacity Usage Threshold Reached.