SAF, AMF Component Instantiation Failed

Ericsson Centralized User Database

1 Introduction

This instruction concerns alarm handling for the SAF, AMF Component Instantiation Failed alarm.

1.1 Alarm Description

This alarm is associated with the Service Availability Forum (SAF). Refer to CUDB Node Fault Management Configuration Guide, Reference [2] for more details.

For information on the possible alarm causes and the corresponding fault reasons, fault locations, and impacts, refer to COM SA, AMF Component Instantiation Failed, Reference [2].

The alarm attributes are listed and explained in Table 1.

Table 1 Alarm Attributes
Attribute Name	Attribute Value
Auto Cease	`No`
Module	`SAF`
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 raise.
Resource ID	`.1.3.6.1.4.1.193.169.9.3.` `<length>.<NOI>`
Alarm Model Description	`AMF Component Instantiation, SAF`
Alarm Active Description	`SAF platform: AMF Component Instantiation @<NON>`
ITU Alarm Event Type	`other (1)`
ITU Alarm Probable Cause	`softwareProgramError (546)`
ITU Alarm Perceived Severity	`(3) – Critical`
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,SaAmfSG.safSg=2N,SaAmfSU.safSu=SC-1,SaAmfComp.safComp=CUDBOI
<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.71.46.115.97.102.83.103.61.50.78.44.83.97.65.109.102.83.85.46.115.97.102.83.117.61.83.67.45.49.44.83.97.65.109.102.67.111.109.112.46.115.97.102.67.111.109.112.61.67.85.68.66.79.73 for ManagedElement=1,SaAmfApplication.safApp=ERIC-CUDB_CUDBOI,SaAmfSG.safSg=2N,SaAmfSU.safSu=SC-1,SaAmfComp.safComp=CUDBOI.
<length> is the number of characters in <NON>, which is equivalent to the number of octets in <NOI>. In the previous example, <length> is 118.

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

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

Not applicable.

Not applicable.

Perform the following steps:

In a first approach, the alarm can be cleared with the previous <NON>, <NOI> and <length> and the following command:
If the alarm is on SC 1: cmw-alarm-clear instantiation 'ManagedElement=1,SaAmfApplication.safApp=ERIC-CUDB_CUDBOI,SaAmfSG.safSg=2N,SaAmfSU.safSu=SC-1,SaAmfComp.safComp=CUDBOI'

If the alarm is on SC 2: cmw-alarm-clear instantiation 'ManagedElement=1,SaAmfApplication.safApp=ERIC-CUDB_CUDBOI,SaAmfSG.safSg=2N,SaAmfSU.safSu=SC-2,SaAmfComp.safComp=CUDBOI'

Refer to Core MW Management Guide, Reference [5] for more information on the cmw-alarm-cease command.
For further details, follow the instructions specified in COM SA, AMF Component Instantiation Failed, Reference [2]. Refer to Core MW Management Guide, Reference [5] for more information on the commands used in the procedure.
Further actions are outside the scope of this Operating Instruction.

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

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