Contents

1   Introduction

This instruction concerns alarm handling for the Licensing, Key File Fault alarm.

1.1   Alarm Description

This alarm is raised when License Manager automatically enters Locked Mode because a license key file is missing or corrupted for more than 24 hours.

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
License key file is missing or corrupted for more than 24 hours.	Key file fault	License key file is missing or corrupted for more then 24 hours	License Manager	Configuration changes subject to licensing will not be accepted until the license key file is restored.

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	10
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.4
Alarm Model Description	License Management, Licensing
Alarm Active Description	Key File Fault
ITU Alarm Event Type	qualityOfServiceAlarm (3)
ITU Alarm Probable Cause	communicationsSubsystemFailure (159)
ITU Alarm Perceived Severity	Critical (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:

• Configuration changes subject to licensing will not be accepted until the license key file is restored.

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, Key File Fault, Reference [5] document for the procedure to perform.

Note:  

Perform only the actions that are applicable for LM deployments using ELIM license key files.

Also, consider that Emergency Unlock cannot be used to prevent the CUDB system from entering Locked mode, because if CUDB is in emergency unlock status, then the configuration changes subject to licensing will not be accepted. The only possible action in this case is the license key file restoration.

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, Key File Fault.