1 Introduction
This instruction concerns alarm handling for the SAF, AMF Component Cleanup Failed 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 details.
For information on the possible alarm causes and the corresponding fault reasons, fault locations, and impacts, refer to COM SA, AMF Component Cleanup Failed.
The alarm attributes are listed and explained in Table 1.
|
Attribute Name |
Attribute Value |
|---|---|
|
Auto Cease |
Yes |
|
Module |
|
|
Error Code |
1 |
|
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.1. <length> . <NOI> |
|
Alarm Model Description |
|
|
Alarm Active Description |
SAF platform: Component Cleanup Failed @ <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.
In Table 1, the indicated variables are as follows:
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
This instruction references the following documents:
1.2.2 Tools
Not applicable.
1.2.3 Conditions
Not applicable.
2 Procedure
Do the following:
Steps

Contents