Contents

1   Overview

1.1   Description

The alarm is issued when a restore in the Processing Layer (PL) has failed during either a system restore or a replica restore.

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	7
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.7
Alarm Model Description	Restore fault, Storage Engine.
Alarm Active Description	Storage Engine (PLDB): restore failed.
ITU Alarm Event Type	processingErrorAlarm (4)
ITU Alarm Probable Cause	fileError (161)
ITU Alarm Perceived Severity	(3) – Critical
Originating Source IP	Node IP 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, Reference [1].

The possible causes of the alarm are as follows:

• It is impossible to connect to the Management server.
• Backup files are missing.

1.2   Prerequisites

1.2.1   Documents

Refer to CUDB Node Fault Management Configuration Guide, Reference [1] for further information.

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

Perform the following steps:

1. Check faulty PLDB traces to see if restore failed due to the incapability of repopulating the System Monitor tables. If this was the case, repeat the restore procedure. Another cause which could trigger this alarm is a missing restore file. Log into the System Controller (SC) where the restore was run, and execute the following command:
   # grep -i restore /var/log/messages

   For more information about logs, refer to CUDB Node Logging Events, Reference [2].

   Execute again the restore after fixing logged problems. Being this alarm autocease, it should be cleared once a correct restore is done.

2. If the alarm does not cease, 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.