Contents

1   Overview

1.1   Description

The alarm is issued when there is a possible temporary data inconsistency between the Processing Layer Database (PLDB) and a given Data Store data partition (DS).

The alarm attributes are listed and explained in Table 1:

Table 1    Alarm Attributes

Attribute Name	Attribute Value
Auto Cease	Yes
Module	STORAGE-ENGINE
Error Code	11
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.2.11.<DG>
Alarm Model Description	Temporary data inconsistency, Storage Engine.
Alarm Active Description	Storage Engine (DS-group #<DG> : Temporary data inconsistency.
ITU Alarm Event Type	communicationsAlarm (2)
ITU Alarm Probable Cause	databaseInconsistency (160)
ITU Alarm Perceived Severity	(5) – Minor
Originating Source IP	Node IP where the alarm was raised.
Sequence Number	Number which indicates the order in which alarms were raised.

In Table 1, the indicated variables are as follows:

• <DG>: The DS-group where the temporary data inconsistency is suspected to be.

For further information about attribute descriptions, refer to CUDB Node Fault Management Configuration Guide, Reference [1].

The possible causes of the alarm are as follows:

• Mastership change situation for the DS-group where the temporary data inconsistency is suspected to be.
• Mastership change situation for the PL-group, being local PL the new elected master and local CUDB node having any DS being master of its respective group. A possible temporary data inconsistency for each aforementioned DS can appear with respect to local PL.

1.2   Prerequisites

1.2.1   Documents

Refer to CUDB System Administrator Guide, Reference [2] for further information.

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

Perform the following steps in case the alarm is not cleared automatically (it might take some time):

1. Establish an admin "CUDB CLI" session towards the target CUDB node:

   ssh <admin_user>@<CUDB_Node_OAM_IP_Address>

2. Run the following command to check if there are any pending or ongoing reconciliation tasks:

   sudo cudbReconciliationMgr -c <dsId>

   Where:

   • -c or --check is an option used to check if a specific task is in the Pending Task List.
   • dsId is the DS-group of the involved DS.

   This command returns the dsId in affirmative case. Otherwise, it returns nothing. In affirmative case, wait for the task to be completed.

   Refer to CUDB Node Commands and Parameters, Reference [3] for further information about this command.

3. If the alarm does not cease, consult 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 [4].

Reference List

CUDB Documents
[1] CUDB Node Fault Management Configuration Guide.
[2] CUDB System Administrator Guide.
[3] CUDB Node Commands and Parameters.
[4] CUDB Glossary of Terms and Acronyms.