Operating Instructions 4/1543-CNH 160 6135/10 Uen B

Control, Blackboard Coordination Cluster Down
Ericsson Centralized User Database

Contents


1 Introduction

This instruction concerns alarm handling for the Control, Blackboard Coordination Cluster Down alarm.

1.1 Alarm Description

This alarm is raised when a Blackboard Coordination (BC) cluster is down.

The possible alarm causes and the corresponding fault reasons, fault locations and impacts are described in Table 1.

Table 1   Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

BC cluster down.

A BC cluster is down.

  • More than half of the BC servers at a site go down or are unreachable.

  • The CUDB node(s) hosting more than half of the BC servers at a site go down or are unreachable.

  • The blades or Virtual Machines (VMs) hosting more than half of the BC servers at a site go down or are unreachable.

  • BC servers.

  • CUDB node(s) hosting BC servers.

  • Blades or VMs hosting BC servers.

Unavailable BC cluster.

The alarm attributes are listed and explained in Table 2.

Table 2   Alarm Attributes

Attribute Name

Attribute Value

Auto Cease

Yes

Module

CONTROL

Error Code

5

Timestamp First

Date and time when the alarm was raised for the first time.

Repeated Counter

Number which indicates how many times the alarm was raised.

Timestamp Last

Date and time of the most recent alarm raise.

Resource ID

1.3.6.1.4.1.193.169.7.5.<SI>

Alarm Model Description

Blackboard Coordination Cluster Down, Control.

Alarm Active Description

Control: Blackboard Coordination Cluster Down at site <SI>

ITU Alarm Event Type

processingErrorAlarm (4)

ITU Alarm Probable Cause

softwareProgramError (546)

ITU Alarm Perceived Severity

(3) – Critical

Originating source IP

Node IP where the alarm was raised.

Sequence Number

Number which indicates the order in which the alarms are raised.

In Table 2, the indicated variables are as follows:

  • <SI> is the identifier of the site where the BC cluster was running.

For further information about attribute descriptions, refer to CUDB Node Fault Management Configuration Guide.

1.2 Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.2 Tools

Not applicable.

1.2.3 Conditions

Not applicable.

2 Procedure

Do the following:

Steps

  1. Several alarms Control, Blackboard Coordination Server Down have not been cleared. Refer to Control, Blackboard Coordination Server Down on how to proceed for every single alarm.
  2. One or more Control, Remote Node Unreachable alarms have not been cleared. Refer to Control, Remote Node Unreachable on how to proceed for every single alarm.
  3. If the alarm does not cease, contact the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.
Legal |© Ericsson AB 2016,2018