1 Introduction
This instruction concerns alarm handling for the Storage Engine, PLDB Cluster in Maintenance Mode alarm.
1.1 Alarm Description
This alarm is raised when a Processing Layer Database (PLDB) 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 |
|---|---|---|---|---|
|
PLDB Storage Engine in maintenance mode. |
A PLDB cluster has entered maintenance mode. |
Affected PLDB. |
Affected PLDB 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 raised. |
|
Resource ID |
.1.3.6.1.4.1.193.169.1.1.13 |
|
Alarm Model Description |
Cluster in maintenance mode, Storage Engine. |
|
Alarm Active Description |
Storage Engine (PLDB): 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 ID where the alarm was raised. |
|
Sequence Number |
Number which indicates the order in which alarms were raised. |
For further information about attribute descriptions, refer to CUDB Node Fault Management Configuration Guide.
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
This instruction references the following documents:
1.2.2 Tools
Not applicable.
1.2.3 Conditions
Not applicable.
2 Procedure
Steps
Do the following:
-
Check if the cluster was ordered to enter maintenance mode. Refer to CUDB Node Logging Events for more information on the logs to
check.
Cluster was not ordered to enter maintenance mode:If the alarm does not cease, contact the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.

Contents