Operating Instructions 8/1543-CSH 109 067/10 Uen C

SAF, AMF SI Unassigned
Ericsson Centralized User Database

Contents


1 Introduction

This instruction concerns alarm handling for the SAF, AMF SI Unassigned alarm.

1.1 Alarm Description

This alarm is associated with the Service Availability Forum (SAF). Refer to CUDB Node Fault Management Configuration Guide for more information.

For information on the possible alarm causes and the corresponding fault reasons, fault locations, and impacts, refer to COM SA, AMF SI Unassigned.

The alarm attributes are listed and explained in Table 1.

Table 1   Alarm Attributes

Attribute Name

Attribute Value

Auto Cease

Yes

Module

SAF

Error Code

2

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.9.2. . <length> . <NOI>

Alarm Model Description

AMF SI Unassigned, SAF

Alarm Active Description

SAF platform: AMF SI Unassigned @ <NON>

ITU Alarm Event Type

other (1)

ITU Alarm Probable Cause

softwareProgramError (546)

ITU Alarm Perceived Severity

(4) – Major

Originating source IP

Node IP where the alarm was raised.

Sequence Number

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

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

In Table 1, the indicated variables are as follows:

  • <NON> is the notifying object name that indicates where the component that generates the alarm is. For example:

    ManagedElement=1,SaAmfApplication.safApp=ERIC-CUDB_CUDBOI,SaAmfSI.safSi=2N-1

  • <NOI> is the notifying object identifier. It corresponds to <NON> in a dot-separated, ASCII-decimal-encoded, character-per-character format without the starting string "ManagedElement=1,". The "SAF, AMF Component Cleanup Failed" alarm <NOI> has been shortened to comply with the SNMP standard of maximum 128 characters. For example:

    .83.97.65.109.102.65.112.112.108.105.99.97.116.105.111.110.46.115.97.102.65.112.112.61.69.82.73.67.45.67.85.68.66.95.67.85.68.66.79.73.44.83.97.65.109.102.83.73.46.115.97.102.83.105.61.50.78.45.49 for SaAmfApplication.safApp=ERIC-CUDB_CUDBOI,SaAmfSI.safSi=2N-1.

  • <length> is the number of characters in <NON> without the starting string "ManagedElement=1,", which is equivalent to the number of octets in <NOI> . In the previous example, <length> is 59.

The alarm can be cleared following the instructions specified in COM SA, AMF SI Unassigned.

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. Follow the instructions specified in COM SA, AMF SI Unassigned, and refer to Core MW Management Guide for more information on the proposed troubleshooting commands. The alarm must cease.
  2. 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