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 toCUDB Node Fault Management Configuration Guide, Reference [1] 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, Reference [2].

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, Reference [1].

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. For example:

  77.97.110.97.103.101.100.69.108.101.109.101.110.116.61.49.44.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 ManagedElement=1,SaAmfApplication.safApp=ERIC-CUDB_CUDBOI,SaAmfSI.safSi=2N-1.

• <length> is the number of characters in <NON>, which is equivalent to the number of octets in <NOI>. In the previous example, <length> is 76.

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

1.2   Prerequisites

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

1.2.1   Documents

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

• CUDB Node Fault Management Configuration Guide, Reference [1], regarding alarm configuration.
• System Safety Information, Reference [3]
• Personal Health and Safety Information, Reference [4]

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

Do the following:

1. Follow the instructions specified in COM SA, AMF SI Unassigned, Reference [2], and refer to Core MW Management Guide, Reference [5] for more information on the proposed troubleshooting commands. The alarm must cease.
2. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.

Reference List

CUDB Documents
[1] CUDB Node Fault Management Configuration Guide.

Other Ericsson Documents
[2] COM SA, AMF SI Unassigned.
[3] System Safety Information.
[4] Personal Health and Safety Information.
[5] Core MW Management Guide.