Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

This is an alarm of severity MINOR.

The alarm is issued when an ECM has taken the active role.

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
The system has recently been started and ECM has determined which host that should be active. The active ECM is moved either because of user request or automatically.	The active ECM (its only one active ECM in the cluster) has moved to another node in the SS7 CAF cluster.	System start ECM is moved Internal cluster network problems	Internal cluster network	This notification requires no remedial action, it is an informative alarm. If this alarm is raised more than 5 times within 5 minutes or is persistent for 5 minutes, there is some problem with the internal cluster network.

The following alarm attributes apply to this alarm:

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	1586561542
Managed Object Class	N/A
Specific Problem	SS7 CAF ECM Goes Active
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 Active alarm is raised.

2   Procedure

Do the following if the alarm is raised multiple times or persistent:

1. Check other alarms from the cluster concerning the internal cluster network status.
2. Collect the ecm.log and 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.

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