1 AlarmDescription
The alarm is raised when the database is not synchronized after a cluster reload.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
Cluster reload |
The database is not yet synchronized with the peer cluster after a cluster reload. |
N/A |
N/A |
Data is not synchronized with the peer cluster. The local database is not available for changes. Traffic handling is not yet possible on shared data. |
|
Attribute Name |
Attribute Value/Interpretation |
|---|---|
|
Major Type |
193 |
|
Minor Type |
918530 |
|
MO Class |
DbsService |
|
Specific Problem |
DBS, NR, Initial Synchronization Needed |
|
Event Type |
QUALITYOFSERVICEALARM |
|
Probable Cause |
frequencyHoppingFailure (74) |
|
Perceived Severity |
MAJOR |
2 Procedure
2.1 Handle Alarm DBS, NR, Initial Synchronization Needed
Prerequisites
- This instruction references the following documents:
- No tools are required.
- Before starting this procedure, ensure that the following
condition is met:
- The alarm is raised.
Steps
- Is the DBS, NR, Connection Lost alarm active?
Yes: Take the necessary actions to clear that alarm.
No: Continue with the next step.
- Is the alarm cleared automatically after the cluster synchronization
finished?
Yes: Job is completed.
No: Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.

Contents