Contents

1   AlarmDescription

The alarm is raised when the clusters are not synchronized.

Table 1    DBS, NR, Synchronization Needed

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Connection loss	The clusters are not synchronized due to earlier connection loss. For causes of connection loss, refer to DBS, NR, Connection Lost.	N/A	Network or configuration	Data is not synchronized with the peer cluster. However, the local database is available. If the peer cluster is in the same state, this is a split-brain situation. This means that after recovery, changes in one cluster remain and changes in the other cluster are lost.

Table 2    Alarm Attributes

Attribute Name	Attribute Value/Interpretation
Major Type	193
Minor Type	918529
MO Class	DbsService
Specific Problem	DBS, NR, Synchronization Needed
Event Type	QUALITYOFSERVICEALARM
Probable Cause	frequencyHoppingFailure (74)
Perceived Severity	MAJOR

2   Procedure

2.1   Handle Alarm DBS, NR, Synchronization Needed

Prerequisites

• This instruction references the following documents:
  • DBS, NR, Connection Lost
• No tools are required.
• Before starting this procedure, ensure that the following condition is met:
  • The alarm is raised.

Steps

1. Is the DBS, NR, Connection Lost alarm active?

   Yes: Take the necessary actions to clear that alarm.

   No: Continue with the next step.

2. Is the same alarm also active in the peer cluster?

   Yes: Check the preferredCluster attribute of the NetsharedConfig class in both clusters.

   If none of them is preferred, start the syncFromPeer() action in the PeerCluster class in one of the clusters. The relevant cluster clears netshared data, restarts application processes, and synchronizes the database contents with its peer. Meanwhile, the peer cluster handles traffic.

   No: Continue with the next step.

3. Is the alarm cleared?

   Yes: Job is completed.

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