1 Introduction
This instruction concerns alarm handling for the Control, Automatic Master Election Locked Down alarm.
1.1 Alarm Description
This alarm is raised when the distribution of masters has been frozen and the automatic master re-election procedure has been blocked. This can only happen when Ericsson personnel is running advanced recovery and troubleshooting actions on a CUDB system.
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 distribution of masters is frozen. |
Automatic master re-election is blocked. |
The cudbManageSite command has been executed on one of the nodes of the site to lock down the master election. |
The CUDB node where command was executed. |
In case of failures, CUDB system availability could be compromised. |
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
Yes |
|
Module |
CONTROL |
|
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 raise. |
|
Resource ID |
1.3.6.1.4.1.193.169.7.6.SI |
|
Alarm Model Description |
CUDB automatic master election locked down, Control. |
|
Alarm Active Description |
Control: CUDB automatic master election is locked down at Site SI |
|
ITU Alarm Event Type |
processingErrorAlarm (4) |
|
ITU Alarm Probable Cause |
softwareProgramError (546) |
|
ITU Alarm Perceived Severity |
(6) – Warning |
|
Originating source IP |
Node IP where the alarm was raised. |
|
Sequence Number |
Number which indicates the order in which the alarms are raised. |
In Table 2, the indicated variables are as follows:
- SI is the identifier of the site where the master re-election is locked down.
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 [2].
- Personal Health and Safety Information, Reference [3].
1.2.2 Tools
Not applicable.
1.2.3 Conditions
Not applicable.
2 Procedure
Do the following:
- The alarm will be cleared by Ericsson personnel, when there is no longer a need to keep the distribution of masters frozen.
Reference List
| CUDB Documents |
|---|
| [1] CUDB Node Fault Management Configuration Guide. |
| Other Ericsson Documents |
|---|
| [2] System Safety Information. |
| [3] Personal Health and Safety Information. |

Contents