DBS, NR, Out of Sync

1 AlarmDescription

The alarm is raised when the data in the redundant clusters are out of sync.

Table 1 DBS, NR, Out of Sync
Alarm Cause	Description	Fault Reason	Fault Location	Impact
Initial synchronization	After the initial synchronization of a cluster, there are temporary differences between the data in the clusters.	N/A	N/A	Data is not fully synchronized with the peer cluster. Changes are synchronized with high latency. If the system is overloaded and remains overloaded, database synchronization becomes impossible, therefore it stops.
Temporary overload	There is a temporary overload on the system.		N/A
Dimensioning problems	The system has not been dimensioned properly.		Dimensioning

Table 2 Alarm Attributes
Attribute Name	Attribute Value/Interpretation
Major Type	`193`
Minor Type	`918528`
MO Class	`DbsService`
Specific Problem	`DBS, NR, Out of Sync`
Event Type	`QUALITYOFSERVICEALARM`
Probable Cause	`frequencyHoppingFailure` (74)
Perceived Severity	`MAJOR`
Additional Information	Serialized transaction expired Serialized and queued transaction expired Queued transaction expired

2 Procedure

Prerequisites

No documents are required.
No tools are required.
Before starting this procedure, ensure that the following condition is met:
- The alarm is raised.

Steps

Did initial synchronization of one of the clusters end just recently?
Yes: Wait until the alarm is cleared automatically.

No: Continue with the next step.
Is one of the clusters overloaded?
Yes: Try to decrease load on the system, for example by re-routing traffic to other clusters or scaling out.

No: Continue with the next step.
Is the alarm cleared automatically?
Yes: Job is completed.

No: Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.