Association Is Connecting And Does Not Establish

Asset ID:	1-72-2244174.1
Update Date:	2017-03-15
Keywords:

Solution Type Problem Resolution Sure

Solution 2244174.1 : Association Is Connecting And Does Not Establish

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 3x.x and later
Information in this document applies to any platform.

Symptoms

The association 4111-B8 remains in CONNECTING status.

Cause

There is an issue at the IP layer with the far end

Indeed, it does not answers the INIT_ACK sent by the Eagle :
SCTP Event Log

Time Event Reason Ripaddr Rport
  --------------------------------------------------------------------------
  14:11:03.995 INIT Rcv Unknown 10.216.90.8 2911
  14:11:03.995 Datagram Ignored No Assoc Found 10.216.90.8 2911
  14:11:03.995 Init ack sent Unknown 10.216.90.8 2911
...
  14:11:10.000 INIT Rcv Unknown 10.216.90.8 2911
  14:11:10.000 Datagram Ignored No Assoc Found 10.216.90.8 2911
  14:11:10.000 Init ack sent Unknown 10.216.90.8 2911
...
  14:11:16.005 INIT Rcv Unknown 10.216.90.8 2911
  14:11:16.005 Datagram Ignored No Assoc Found 10.216.90.8 2911
  14:11:16.005 Init ack sent Unknown 10.216.90.8 2911
....
and so on...
  14:12:04.020 INIT Rcv Unknown 10.216.90.8 2911
  14:12:04.020 Datagram Ignored No Assoc Found 10.216.90.8 2911
  14:12:04.020 Init ack sent Unknown 10.216.90.8 2911

It does not answers the PING sent by the Eagle :

> pass:loc=4111:cmd="ping 10.216.90.8 "

eaglestp 17-03-08 14:17:11 BRA EAGLE5 45.0.1-64.70.35
  PING 10.216.90.8: 56 data bytes
  PING: no answer from 10.216.90.8
  PING command complete

> pass:loc=4111:cmd="traceroute 10.216.90.8 "

eaglestp 17-03-08 14:17:48 BRA EAGLE5 45.0.1-64.70.35
  Traceroute to yxspo102a (10.216.90.8),
  10 hops max, 100 byte packets
  1 30ms 0ms 1ms (10.210.0.3)
  2 37ms 36ms 36ms (10.210.64.149)
  3 37ms 36ms 36ms (10.239.255.173)
  4 42ms 40ms 41ms (10.223.238.253)
  5 41ms 40ms 40ms (10.239.255.90)
  6 43ms 40ms 40ms (10.223.237.253)
  7 39ms 36ms 36ms (10.216.250.130)
  8 36ms 36ms 36ms (10.216.250.166)
  9 * * * Request timed out
  10 * * * Request timed out
  Maximum number of hops reached

Solution

There is nothing to do on the Eagle side.
If the far end does not establish the SCTP layer, we won't be able to get anything.
Also it would be good to understand the reason of the timeout for the pings toward the far end. Maybe is there an equipment after the 10.216.250.166 which is having some issues :
  ...
  8 36ms 36ms 36ms (10.216.250.166)
  9 * * * Request timed out

=> So, the fist thing is to have a valid IP connection with the far end.

Attachments

This solution has no attachment