1 Overview
This document is the Operating Instructions (OPI) for the alarm SS7 CAF OAM Connection Lost.
1.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).
The possible alarm causes and fault locations are explained in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
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 will be 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 below. |
The following alarm attributes apply to this alarm:
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
1586563328 |
|
Managed Object Class |
N/A |
|
Specific Problem |
OAM Connection Lost |
|
Perceived Severity |
SEVERITY_MAJOR |
2 Procedure
Perform the following steps if the alarm is persistent (raised for more than 1 min):
- Check other alarms from the cluster about the internal cluster network status.
- 2. Enable trace on OAM as follows.
- 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 3 above.

Contents