Operating Instructions 200/1543-AXB 901 33/7 Uen A1

Policy Control, Connection to External Repository Failed
Ericsson Service-Aware Policy Controller

Contents


1 Alarm Description

The SAPC raises this alarm when the connection to an external repository fails.

The SAPC clears the alarm when the connection to an external repository is re-established.

The possible causes of this alarm are:

  • The SAPC cannot establish a connection to an external repository.

  • A previously established connection to an external repository has gone down.

As a result of the fault, no data are retrieved from the external repository for which the connection is down.

The main attributes of the alarm are the following:

Table 1   Alarm Attributes

Attribute Name

Attribute Value

Alarm Type Id

ExternalRepositoryConnectionFailure

Major Type

193

Minor Type

7077897

Specific Problem

Policy Control, Connection to External Repository Failed.

Severity

Major

Source

ManagedElement=1,PolicyControlFunction=1,EntityData=1,EDSources=1,ExternalRepository=<ip>:<port>

Probable Cause

100505

Event Type

Communications

Additional Text

URL used to connect to external repository failed: <protocol>://<ip>:<port>/

Last Event Time

YYYY-MM-DDTHH:mm:ss<time zone>

2 Procedure

2.1 Handle Alarm Policy Control, Connection to External Repository Failed

Prerequisites

  • Before starting this procedure, ensure that you have read the following documents:

  • No specific tools are required.

  • No conditions are required.

Steps

Steps

  1. Check that the external repository (Additional Text field in alarmAttributesTable) is up and running and is accepting connections.
  2. Check that there is IP connectivity between the SAPC and the external repository.
  3. Check that the entities data source configured in the SAPC objects contains correct values in:

    • dataSource field (host, port, user) in definition attribute.

    • dbPassword attribute.

    Refer to Database Access for details on how to configure these objects properly. It is possible to obtain further details about the probable cause in the logged event related to external database.
  4. If the external repository is a CUDB node, check that it is defined as CUDB-FE VIP address. For details, refer to Integration in User Data Consolidation.
  5. If the alarm does not cease, consult next level of maintenance support. Further actions are outside the scope of this procedure.
Legal |© Ericsson España, S.A. 2018