DBS, NR, Redundancy Disabled

1	Alarm Description
2	Procedure
2.1	Handle Alarm DBS, NR, Redundancy Disabled

1 AlarmDescription

The alarm is raised when the Geographical Network Redundancy (GeoRed) is disabled.

Table 1 DBS, NR, Redundancy Disabled
Alarm Cause	Description	Fault Reason	Fault Location	Impact
Redundancy disabled by user	Network Redundancy configuration is explicitly disabled by the user. That is, Network Redundancy specific configuration is not empty but the `isEnabled` attribute in the `NetsharedConfig` class is set to `false`.	N/A	N/A	Network Redundancy is out of operation. All related clusters work as stand-alone clusters. Traffic handling is possible in all clusters on database level. Effectively, this is a split-brain situation. This means that after enabling Network Redundancy, changes in one cluster are going to remain and changes in other clusters are lost.
Redundancy disabled by DBN	Network Redundancy was disabled by DBN during a schema upgrade of one of the clusters.		N/A
Configuration mismatch	Netshared data configuration mismatch on the two clusters.		Configuration

If the configuration is disabled deliberately due to planned maintenance, disregard the alarm until the relevant operation is finished. Application settings, network routing, or both make sure that only one of the clusters receives traffic.

Typical cases when Network Redundancy is deliberately disabled:

Network Redundancy configuration
Software upgrade

2 Procedure

2.1 Handle Alarm DBS, NR, Redundancy Disabled

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

Was the configuration disabled deliberately due to planned maintenance?
Yes: Disregard the alarm until the relevant operation is finished—application settings, network routing, or both must make sure that only one of the clusters receives traffic. Proceed to Step 5.

No: Continue with the next step.
Is the isEnabled attribute in the NetsharedConfig class set to true?
Yes: Continue with the next step.

No: Set the class to true.
Verify that the same POTs are configured to be netshared by inspecting NetsharedPOT and NetsharedLocallyCreatedPOT instances under NetsharedApplication on both clusters.
Do the two clusters contain the same dbsNetsharedPOTRtid and dbsNetsharedLocallyCreatedPOTRtid attributes?

Yes: Continue with the next step.

No: Align the mismatching configuration by upgrading the application to compatible versions on the two clusters (if applicable).
If the cluster is not expected to work in a network redundant way, then remove all configuration classes under the NetsharedConfig class. The NetsharedConfig class itself cannot be removed.
Is the alarm cleared?
Yes: Job is completed.

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