License Management, Autonomous Mode Activated

MTAS

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 an installed license cannot be reached.

In a deployment with multiple license key files, the alarm is raised in response to a single missing or corrupted license key file.

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

Table 1 Alarm Causes
Alarm Cause	Description	Fault Reason	Fault Location	Impact
Failing to reach an installed license	The configured license servers do not respond to the ME⁽¹⁾ attempt to refresh its license inventory. License information remains unreachable. The ME enters Autonomous mode.	The Arwa server is unreachable	License servers	This fault leads to no service impact during the first 24 hours. If the fault duration exceeds 24 hours, the licensed services are affected (no availability or limited capacity) and the alarm License Management, Key File Fault is raised.
			Possible IP network issue
			DNS⁽²⁾ server
			Network interface

(1) Managed Element (ME)

(2) Domain Name System (DNS)

Note:: The alarm can be raised as a result of maintenance activities.

The alarm attributes are listed and explained in Table 2.

Table 2 Alarm Attributes
Attribute Name	Attribute Value
Major Type	193
Minor Type	393218
Managed Object Class	Lm
Managed Object Instance	`ManagedElement=<node_name>,SystemFunctions=1,Lm=1`
Specific Problem	License Management, Autonomous Mode Activated
Event Type	qualityOfServiceAlarm (3)
Probable Cause	x733CommunicationsSubsystemFailure (306)
Additional Text	Autonomous Mode has been activated
Perceived Severity	minor (5)

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 the following documents are available:

1.2.2 Tools

No tools are required.

1.2.3 Conditions

Before starting this procedure, ensure that the following conditions are met:

A License Management, Autonomous Mode Activated alarm is raised.
No ongoing maintenance activities are affecting the network or network elements.
If applicable, the address to the Arwa server is known.
If applicable, the Arwa DNS hostname is known.
The user has proper authority to handle configuration management of the network elements.
Root access to the System Controllers.
An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2 Procedure

Based on the selected communication channels, refer to section Configure RSG Connectivity or Configure HTTPS Connectivity in Update Arwa Connection.

Do the following:

Connect manually to the Arwa server, refer to section Connect to Arwa Server in Update Arwa Connection.
Is the alarm cleared?
Yes: Proceed with Step 5.

No: Continue with Step 3.
Perform data collection, refer to Data Collection Guideline for MTAS.
Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
Note:
If resolving the issue is expected to take more than 24 hours, Emergency Unlock can be used to prevent the system from entering Locked Mode. For more information on Emergency Unlock, refer to License Management.
Job is completed.