Contents

1   Overview

1.1   Description

The alarm is issued when the replication delay, between a slave Processing Layer Database (PLDB) cluster in the Ericsson Centralized User Database (CUDB), and the master PLDB cluster that it is replicating from, exceeds a predefined threshold. Replication delay is expressed as the estimated time needed for the slave to catch up with the master. The alarm is automatically cleared when the replication delay value drops below 85% of the threshold. The threshold is configured with the replicationTimeDelayAlarmThreshold parameter. Refer to CUDB Node Configuration Data Model Description, Reference [1] for more information.

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	20
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.1.20
Alarm Model Description	Replication Delay Too High, Storage Engine.
Alarm Active Description	Storage Engine (PLDB): replication delay is too high.
ITU Alarm Event Type	qualityOfServiceAlarm (3)
ITU Alarm Probable Cause	thresholdCrossed (549)
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 the alarms are raised.

For more information on attribute descriptions, refer to CUDB Node Fault Management Configuration Guide, Reference [2].

The possible causes are as follows:

• Network failure or network misconfiguration
• Network overload
• Master or slave replica server overload
• Replication has been re-established after an outage
• Slave replica has been restored from a backup

1.2   Prerequisites

1.2.1   Documents

Refer to CUDB Node Fault Management Configuration Guide, Reference [2] for more information.

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

If the alarm is not cleared automatically after a short period of time, perform the following steps:

1. Check the log of the faulty node.

   Refer to CUDB Node Logging Events, Reference [3] for more information.

2. Check network connections. If any failure is found, fix it. If the alarm does not cease, continue with the next step.
3. Check if the alarm Storage Engine, High Load in PLDB is raised for either the slave PLDB cluster or the corresponding master PLDB cluster. In yes, follow the related Operating Instructions, refer to Storage Engine, High Load in PLDB, Reference [4].
4. If the alarm does not cease, consult the next level of maintenance support. Further actions are outside the scope of this Operating Instructions.

Glossary

For the terms, definitions, acronyms and abbreviations used in this document, refer to CUDB Glossary of Terms and Acronyms, Reference [5].

Reference List

CUDB Documents
[1] CUDB Node Configuration Data Model Description.
[2] CUDB Node Fault Management Configuration Guide.
[3] CUDB Node Logging Events.
[4] Storage Engine, High Load in PLDB.
[5] CUDB Glossary of Terms and Acronyms.