Contents

1   AlarmDescription

The alarm is raised when the connection is lost with the peer cluster.

Table 1    DBS, NR, Connection Lost

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Reload	The connection endpoint reloaded (on software or hardware level).	N/A	N/A	Minor severity: After automatic recovery, additional resources will temporarily be needed to restore functionality. This can result in overload. Major severity: Data is not synchronized with the relevant peer cluster. Changes in one cluster are kept and the changes in the other cluster are lost.
Network unavailability	The connection was closed because of network unavailability.		Network
Configuration change	The peer cluster closed the connection because of configuration changes.		N/A
Backlog size limit reached	One of the clusters closed the connection as it reached the relevant limits on backlog size.		Network/Configuration

2   Procedure

2.1   Handle Alarm DBS, NR, Connection Lost

Prerequisites

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

Steps

1. Are there any software or hardware problems in the peer cluster?

   Yes: Take the necessary actions there to allow recovery.

   No: Continue with the next step.

2. Is the DBS, NR, Redundancy Disabled alarm raised in the peer cluster?

   Yes: Take the necessary actions to clear that alarm.

   No: Continue with the next step.

3. Is the alarm still active?

   Yes: Check network availability between the clusters. For the list of nodes that lost the connection, check the infoValue attribute of the alarm.

   No: Contact the next level of maintenance support, as it is possible that the alarm was raised due to a dimensioning problem resulting in overload.

4. Job is completed.