Secondary Far End Not Reachable On One Association

Asset ID:	1-72-1998615.1
Update Date:	2016-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 1998615.1 : Secondary Far End Not Reachable On One Association

Applies to:

Oracle Communications EAGLE (Hardware) - Version EAGLE 45.0 and later
Information in this document applies to any platform.

Symptoms

The secondary far end is not reachable for a particular association

Cause

Far end was configured in uni homed and not in multi homed
By lack of secondary path on the far end side, Eagle which was configured as multi-homed could not reach the non existing secondary far end.

> rtrv-assoc:aname=ussducb101

     Eaglestp 15-03-27 11:46:09 EST EAGLE5 45.0.1-64.70.35
    ANAME Assoc101
          LOC      1301          IPLNK PORT A,B         LINK     A9
          ADAPTER M3UA          VER        M3UA RFC
          LHOST    localhost
          ALHOST   alternatehost
          RHOST    remotehost
          ARHOST   ---
          LPORT    2905          RPORT      2905
          ISTRMS   2             OSTRMS     2           BUFSIZE 200
          RMODE    LIN           RMIN       120         RMAX     800
          RTIMES   5             CWMIN      3000        UAPS     10
          OPEN     YES           ALW        NO          RTXTHR   10
          RHOSTVAL RELAXED

> rept-stat-assoc:aname=Assoc101

Eaglestp 15-03-27 11:46:53 EST EAGLE5 45.0.1-64.70.35
                       CARD IPLNK
   ANAME             LOC PORT   LINK PST             SST            ASPID
   Assoc101        1301 A,B    A9   IS-ANR          RESTRICTED       undefined

    LSN       ANAME             ASP STATE
    lsn101    Assoc101        ACTIVE

=> We see in the below pass command, the lack of alternate remote IP address :

> pass:loc=1301:cmd="sctp -a Assoc101"

   Eaglestp 15-03-27 14:57:54 EST EAGLE5 45.0.1-64.70.35
    Aname           Local              Local       Remote             Remote
                    Address            Port        Address            Port
    Assoc101        10.1xx.cd.xx       2905        10.aa.bac.ac       2905
                    10.1xx.xx.xx

                                 Nets Data

         IP Address     10.aa.bac.ac      State   Reachable
               Port     2905                  Primary   YES
                MTU     1500                      cwnd   55296
           ssthresh     55296                     RTO   120

         IP Address     10.aa.bad.ac      State   Not Reachable
               Port     2905                      Primary   NO
                MTU     1500                      cwnd   3000
           ssthresh     55296                     RTO   0

Solution

The user has configured the far end in multi-homing with the expected ip@ 10.aa.bad.ac and it solved the issue

Attachments

This solution has no attachment