Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

This is an alarm of severity MINOR.

This alarm is issued when ECM detects a failure that it is unable to recover from.

The possible alarm causes, fault locations, and impacts are explained in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
ECM has run out of memory ECM has used all its message buffers for sending of internal messages ECM has detected corrupt internal data structures	ECM detected a failure that it is unable to recover from	Running out of memory Corrupted data structure	Internal cluster network	The ECM process is shut down immediately. The ECM process is automatically restarted by the SS7 CAF AMF process. If the alarm is raised more than 5 times in 5 minutes or is persistent for 5 minutes, follow the procedure in Section 2.

The alarm attributes are listed and described in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	1586561538
Managed Object Class	N/A
Specific Problem	ECM Goes Down
Perceived Severity	SEVERITY_MINOR

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 ECM Goes Down alarm is raised.

2   Procedure

Do the following if the alarm is raised multiple times:

1. 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 ecm.log and active.om.cim and all the files with the extension *.cnf.

2. Contact next level of support and provide the files collected in Step 1.