1 Introduction
This instruction concerns alarm handling for the Storage Engine, DS Cluster in Maintenance Mode alarm.
1.1 Alarm Description
This alarm is raised when a Data Store (DS) Storage Engine is in maintenance mode.
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 |
|---|---|---|---|---|
|
DS Storage Engine in maintenance mode. |
A DS cluster has entered maintenance mode. |
Affected DS. |
Affected DS cluster cannot provide service. |
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
Yes |
|
Module |
STORAGE-ENGINE |
|
Error Code |
13 |
|
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.1.2.13.<DG> |
|
Alarm Model Description |
Cluster in maintenance mode, Storage Engine. |
|
Alarm Active Description |
Storage Engine (DS-group #<DG>): Storage Engine is in maintenance mode. |
|
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:
For further information about field description, 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 [4]
- Personal Health and Safety Information, Reference [5]
1.2.2 Tools
Not applicable.
1.2.3 Conditions
Not applicable.
2 Procedure
Do the following:
- Check if the cluster was ordered to enter maintenance mode. Refer to CUDB Node Logging Events, Reference [2] for more information on the logs to check.
- If the cluster was not ordered to enter maintenance mode, and the alarm does not cease automatically, then contact the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.
Glossary
For the terms, definitions, acronyms and abbreviations used in this document, refer to CUDB Glossary of Terms and Acronyms, Reference [3].
Reference List
| CUDB Documents |
|---|
| [1] CUDB Node Fault Management Configuration Guide. |
| [2] CUDB Node Logging Events. |
| [3] CUDB Glossary of Terms and Acronyms. |
| Other Ericsson Documents |
|---|
| [4] System Safety Information. |
| [5] Personal Health and Safety Information. |

Contents