Operating Instructions 3/1543-CNH 160 6161/10 Uen C

LDAP Front End, Server Down
Ericsson Centralized User Database

Contents


1 Introduction

This instruction concerns alarm handling for the LDAP Front End, Server Down alarm.

1.1 Alarm Description

The alarm is issued when a Lightweight Directory Access Protocol (LDAP) Front End (FE) is not reachable.

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

An LDAP FE server is down.

An LDAP FE is unreachable.

An LDAP FE is unavailable at IP address <IP> and port number <PN> .

Blade or Virtual Machine (VM).

The affected LDAP FE cannot be used.

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

3

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.3. <IP> . <PN>

Alarm Model Description

Service Down, LDAP front-end.

Alarm Active Description

LDAP front-end: server down <ND> @ <IP>, uuid: <uuid>

ITU Alarm Event Type

qualityOfServiceAlarm (3)

ITU Alarm Probable Cause

softwareProgramError (546)

ITU Alarm Perceived Severity

(5) – Minor

Originating Source IP

Node IP where the alarm was raised.

Sequence Number

Number which indicates the order in which alarms were raised.

In Table 2, the indicated variables are as follows

  • <PN> is the port number.

  • <ND> is the CUDB node number where the alarm was raised.

  • <IP> is the Internet Protocol (IP) address of the LDAP FE that is down.

  • <uuid> is the universally unique identifier of the computing resource (blade or VM). It is blank if it is not possible to figure out its value.

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

If the alarm is raised, do the following:

Steps

  1. If the alarm is not cleared automatically in a short period of time, check the log in faulty LDAP FE. For more information, refer to CUDB Node Logging Events.
  2. Try to start the LDAP FE manually at IP address indicated in Alarm Description. For more information, refer to CUDB Node Commands and Parameters.
  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