SS7 CAF OAM Connection Lost
Call Session Control Function

Contents


1   Alarm Description

This is an alarm of severity MAJOR.

The alarm is issued when the SM NTF Agent loses its connection towards the stack to the OAM process.

Table 1    SS7 CAF OAM Connection Lost Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

  • The OAM process has crashed.

  • Internal cluster network problem.

Operation and Maintenance connection lost

SM NTF Agent loses its connection towards the stack to the OAM process.

Network


Cluster

Any alarms or notifications sent by the stack during the time the connection is down are lost.


The connection is automatically established once the OAM process is restarted or the internal cluster network is available again.


If this alarm is raised for more than 1 minute, follow the procedure in Section 2.

 
Table 2    SS7 CAF OAM Connection Lost Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

1586563328

Managed Object Class

Not Applicable

Source

SM_NTF_Agent=<*>

Specific Problem

OAM Connection Lost

Perceived Severity

SEVERITY_MAJOR

2   Procedure

2.1   Handle Alarm SS7 CAF OAM Connection Lost

Prerequisites

Steps

  1. Check other alarms from the cluster concerning the internal cluster network status.
  2. Enable trace on OAM as follows:
    1. Log on to the controller node.
    2. Start the Signalling Manager CLI:

      SC-1:~ # dsc-connect-signalling-mgr

      cli> connect;

      EXECUTED

    3. Enable OAM trace:

      cli> OAMTON;

      OAM-Trace On Successful
      EXECUTED

    4. Keep the trace activated for 5 minutes.
    5. Disable SCTP trace:

      cli> OAMTOF;

      OAM-Trace Off Successful.
      EXECUTED

  3. Collect the ss7trace.log located in /opt/sign/log.

    Also collect the current configuration that is located in folder /opt/sign/etc. Collect the file active.om.cim and all the files with the extension *.cnf.

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