1 Introduction
This instruction concerns alarm handling.
1.1 Alarm Description
The alarm is raised by the middleware Availability Management Framework (AMF) service.
The alarm is raised when the AMF cannot successfully instantiate a software component. Depending on the software component, a successful instantiation can, for example, encompass the following:
- A successful start of processes
- A successful creation of files
- A successful execution of commands
A software component instantiation can fail, either when encountering an error situation, or when it is unable to complete successfully within a specified time.
The possible alarm causes and fault locations are explained in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
Unable to instantiate a software component |
The software component that the AMF tries to instantiate does not acknowledge its successful instantiation in time |
The software component is defect |
The software component that fails to be instantiated |
The service the software component provides is lost. |
|
The AMF configuration of the software component is incorrect, for example, defines an incorrect instantiation command or too short time for instantiation |
The AMF configuration for the software component is defect |
The configuration of the software component that fails to be instantiated |
The software component is permanently taken out of operation. | |
- Note:
- The alarm can appear as a result of initial installation or software upgrade.
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
18568 |
|
Minor Type |
131074 |
|
Source |
safApp=<*>,safSg=<*>,safSu=<*>,safComp=<*> |
|
Specific Problem |
|
|
Event Type |
processingErrorAlarm (4) |
|
Probable Cause |
x736UnspecifiedReason (418) |
|
Additional Text |
Instantiation of Component <LDAP DN of component> failed |
|
Perceived Severity |
major (4) |
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 document:
1.2.2 Tools
No tools are required.
1.2.3 Conditions
Before starting this procedure, ensure that the following condition is met:
2 Procedure
Do the following:
- Was the alarm raised during initial installation or upgrade?
Yes: Contact the deployment organization. Proceed with Step 5.
No: Continue with the next step.
- Perform a health check, refer to Health Check documentation available in the library.
- Perform data collection, refer to Data Collection Guideline.
- Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
- Job is completed.

Contents