1 Introduction
This instruction concerns alarm handling for the Licensing, License Key Not Available, Minor alarm.
1.1 Alarm Description
This alarm is raised when the CUDB Customer Trial deployment license has entered the expiration warning period, and is about to expire.
The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
CUDB detected that the license of the CUDB Customer Trial is about to expire. |
The CUDB Customer Trial is about to expire. |
The available license on the node is about to expire. |
License Manager |
Violation of license agreements, if the new license key file is not ordered and installed before the Customer Trial license expires. |
The following is the consequence for the node if the alarm is not solved:
- Violation of license agreements.
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
Yes |
|
Module |
LICENSING |
|
Error Code |
3 |
|
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 raise. |
|
Resource ID |
1.3.6.1.4.1.193.169.14.2.2.15 |
|
Alarm Model Description |
License Management, Licensing |
|
Alarm Active Description |
License key not available, CUDB Customer Trial license is about to expire |
|
ITU Alarm Event Type |
qualityOfServiceAlarm (3) |
|
ITU Alarm Probable Cause |
configurationOrCustomisationError (159) |
|
ITU Alarm Perceived Severity |
(5) – Minor |
|
Originating source IP |
Node IP where the alarm was raised. |
|
Sequence Number |
Number which indicates the order in which the alarms are raised. |
For further information about attribute descriptions, refer to 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], regarding alarm configuration.
- 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, License Key Not Available, Reference [5] document for the procedure to perform.
- Note:
- Perform only the actions that are applicable for LM deployments using ELIM license key files.
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, License Key Not Available. |

Contents