1 Alarm Description

This is an alarm of severity WARNING.

The alarm is issued when an SCTP path is unavailable.

Table 1 SCTP IP Path is Down Alarm Causes
Alarm Cause	Description	Fault Reason	Fault Location	Impact
An SCTP IP path became inactive, unavailable, or unreachable. Network disturbances.	SCTP IP path became unavailable.	Path is inactive, unavailable, or unreachable. Network problems.	Network	Normally this is a non-fatal alarm; SCTP uses other paths in the association for communicating with the remote peer. Follow the procedure in Section 2 Procedure if the alarm is raised for more than an hour without any known network disturbances.
	SCTP IP path became unavailable.		Network

Table 2 SCTP IP Path is Down Alarm Attributes
Attribute Name	Attribute Value
Major Type	`193`
Minor Type	`1586601228`
Managed Object Class	Not Applicable
Source	`RemoteAddress=<>,LocalAddress=<>,FEID_Association=<>,AssociationID=<>,Sctp.InstanceID=<*>`
Specific Problem	`SCTP IP Path is Down`
Perceived Severity	`SEVERITY_WARNING`

2 Procedure

Prerequisites

No documents are referenced.
No tools are required.
The following condition must apply:
- The alarm is raised for more than an hour.

Steps

Make sure that there are no disturbances in the network.
Enable trace on SCTP:
Note:
SCTP tracing is not recommended during hours of high traffic.
1. Log on to the controller node.
2. Start the Signalling Manager CLI:
  SC-1:~ # dsc-connect-signalling-mgr
  
  cli> connect;
  
  EXECUTED
3. Enable SCTP trace:
  cli> STTON;
  
  SCTP-Trace On Successful. EXECUTED
4. Keep the trace activated for 5 minutes.
5. Disable SCTP trace:
  cli> STTOF;
  
  SCTP-Trace Off Successful. EXECUTED
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.
Contact the next level of support and provide the files collected in Step 3.

1	Alarm Description
2	Procedure
2.1	Handle Alarm SCTP IP Path is Down