Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2215582.1
Update Date:2016-12-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  2215582.1 :   All Assoc Down When The Primary Path Only Became Down.  


Related Items
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec Eagle 5
  •  




In this Document
Symptoms
Cause
Solution


Created from <SR 3-13642090961>

Applies to:

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

Symptoms

All assoc down to dest1, when only one switch became down.
The associations are multi-homed, so why do they become down when one switch only is down ?
Why Eagle sent ABORT messages ?

Cause

The ABORT message was sent by the Eagle to answer the latest received protocol message from Dest1, as this destination was being detected by the Eagle as being prohibited
 
The links of the destination were down but the association level was still up, so Eagle could communicate at this level and send an ABORT message to answer the latest received message
 

Solution

All links of the linkset Dest1 experienced an IP connection failure with the far end at 11:43 am during less than one minute.
This is the time at which Eagle issued the ABORT message to the far end.
The 15 min measurements files indicate also an outage at the Link layer and at the Assoc layer.
All associations of the linkset went down with the far end during 51 sec. See hereafter the measurements.

So, it was not only one single switch becoming down, it was actually all links to the destination having an outage.

If the fr end did not detect the association failure it is likely because it did not shutdown properly and did not last long enough. So the Far end still had a status as active whereas on Eagle side it was down. This is why Eagle sent the ABORT messages.
However, that is strange that the Far End did not detect it.
Eagle is reporting the issue in various logs and also it pegged the counters for the measurements, so the far end should have detected the failures.


I would recommend to monitor these associations

==============================================
Extract of the logs and measurements :
==============================================

REPT-STAT-SLK:L2STATS=BOTH:PORT=A:LOC=xxx :

SLK      LSN    CLLI   PST    SST   AST
1216,A   dest1  dest1  IS-NR  Avail -----

Service Event Timestamp
IP Connection failure 16-11-14 11:43:09.870

SLK      LSN    CLLI  PST    SST   AST
1304,A   dest1  dest1 IS-NR  Avail -----


Service Event Timestamp
IP Connection failure 16-11-14 11:43:09.890

And son on...


IVALDATE     IVALSTART IVALEND                 IVALDATE    IVALSTART IVALEND
14/11/2016 11:30:00    11:45:00                14/11/2016 11:30:00 11:45:00
--------------------------------------         -----------------------------------------------------------
LSN    LOC  LINK     DURLKOTG                  ASSOC    ECASNEST DURASNEST
dest1  1215 A          50                      dest1as0    1       50
dest1  1216 A          51                      dest1as4    1       51
dest1  1303 A          50                      dest1as2    1       50

 

 

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback