Operating Instructions 1/1543-CNH 160 6161/10 Uen A

LDAP Front End, Processing Redundancy Lost
Ericsson Centralized User Database

Contents


1 Introduction

This instruction concerns alarm handling for the LDAP Front End, Processing Redundancy Lost alarm.

1.1 Alarm Description

The alarm is issued when the number of Lightweight Directory Access Protocol (LDAP) Front Ends (FEs) down equals to the number of LDAP FEs set as the redundancy level (maximum number of LDAP FEs down permitted).

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

Number of LDAP FEs down is equal to the number of LDAP FEs set as the redundancy level.

Maximum number of LDAP FEs down permitted is reached..

Too many LDAP FEs are down.

LDAP Front Ends

System ability to maintain the optimum level of service is degraded.

The alarm attributes are listed and explained in Table 2:

Table 2   Alarm Attributes

Attribute Name

Attribute Value

Auto Cease

Yes

Module

LDAP-FE

Error Code

1

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 raised.

Resource ID

.1.3.6.1.4.1.193.169.2.1

Alarm Model Description

LDAP processing redundancy lost, LDAP front-end.

Alarm Active Description

LDAP front-end: LDAP processing redundancy lost.

ITU Alarm Event Type

qualityOfServiceAlarm (3)

ITU Alarm Probable Cause

softwareProgramError (546)

ITU Alarm Perceived Severity

(6) – Warning

Originating Source IP

Node IP where the alarm was raised.

Sequence Number

Number which indicates the order in which alarms were raised.

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

1.2 Prerequisites

1.2.2 Tools

Not applicable.

1.2.3 Conditions

Not applicable.

2 Procedure

Perform the following steps:

Steps

  1. If the alarm is not cleared automatically in a short period of time, check the log in faulty LDAP FE(s). For more information, refer to CUDB Node Logging Events.
  2. For the faulty LDAP FE(s), check if the LDAP Front End, Server Down alarm is issued. For more information, refer to LDAP Front End, Server Down and follow the procedure detailed there.
  3. If the alarm does not cease, contact the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.