1 Introduction
This instruction concerns alarm handling.
1.1 Alarm Description
This is an alarm of severity MAJOR.
The alarm is issued when an attempt to start a process failed.
The possible alarm causes, fault locations, and impacts are explained in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
An attempt to start a process failed. |
|
Internal cluster network |
Normally this is a non-fatal alarm; the ECM will automatically make new attempts to start the process. If the alarm is raised more than 5 times within 5 minutes or is persistent for 5 minutes, follow the procedure in Section 2. |
The alarm attributes are listed and explained in Table 2:
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
1586561539 |
|
Managed Object Class |
N/A |
|
Specific Problem |
Start Process Failed |
|
Perceived Severity |
SEVERITY_MAJOR |
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
No documents are referenced.
1.2.2 Tools
No tools are required.
1.2.3 Conditions
Before starting this procedure, ensure that the following conditions are met:
- An SS7 CAF Start Process alarm is raised.
2 Procedure
Do the following if the alarm is raised multiple times or is persistent:
- Collect the ss7trace.log located in /opt/sign/log.
Also collect the current configuration which is located in the folder /opt/sign/etc. Collect the file active.om.cim and all the files with the extension *.cnf.
- Contact next level of support and provide the files collected in Step 1 .

Contents