1 Introduction
This instruction concerns alarm handling for the Licensing, Emergency Unlock Reset Key Required, License Management alarm.
1.1 Alarm Description
This alarm is raised when the activationLeft counter of the Emergency Unlock Managed Object is decremented.
The alarm is issued in the following situations:
- If the Emergency Unlock Mode can be activated for one additional seven-day period, a warning alarm is raised.
- If the Emergency Unlock Mode cannot be reactivated, a major alarm is raised.
- Note:
- Activation of the Emergency Unlock Mode unlocks only the capacity licenses, except the Payload Blades / Virtual Machines capacity license.
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 |
|---|---|---|---|---|
|
The Emergency Unlock Mode has been activated. |
The Emergency Unlock Mode has been activated and it can be activated again for one additional seven-day period. |
The remaining number of activations for emergency unlock decreased to one. |
License Manager |
Warning that the Emergency Unlock Mode can be activated again for one additional seven-day period. |
|
The Emergency Unlock Mode has been activated. |
The Emergency Unlock Mode has been activated and it cannot be activated again. An Emergency Unlock Reset Key is required. |
The remaining number of activations for emergency unlock has reached zero. |
License Manager |
Major impact: The Emergency Unlock Mode cannot be activated again, until the Emergency Unlock reset key is provided. |
The alarm attributes with WARNING severity are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
Yes |
|
Module |
LICENSING |
|
Error Code |
8 |
|
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.5 |
|
Alarm Model Description |
License Management, Licensing |
|
Alarm Active Description |
Emergency Unlock Reset Key Required |
|
ITU Alarm Event Type |
qualityOfServiceAlarm (3) |
|
ITU Alarm Probable Cause |
aIS (1) |
|
ITU Alarm Perceived Severity |
Warning (6) |
|
Originating source IP |
Node IP where the alarm was raised. |
|
Sequence Number |
Number which indicates the order in which the alarms are raised. |
The alarm attributes with MAJOR severity are listed and explained in Table 3.
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
Yes |
|
Module |
LICENSING |
|
Error Code |
7 |
|
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.5 |
|
Alarm Model Description |
License Management, Licensing |
|
Alarm Active Description |
Emergency Unlock Reset Key Required |
|
ITU Alarm Event Type |
qualityOfServiceAlarm (3) |
|
ITU Alarm Probable Cause |
aIS (1) |
|
ITU Alarm Perceived Severity |
Major(4) |
|
Originating source IP |
Node IP where the alarm was raised. |
|
Sequence Number |
Number which indicates the order in which the alarms are raised. |
The following is the consequence for the node if the alarm is not solved:
- Either one or no activations of the emergency unlock is possible.
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, Emergency Unlock Reset Key Required 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, Emergency Unlock Reset Key Required. |

Contents