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-71-2196922.1
Update Date:2017-06-19
Keywords:

Solution Type  Technical Instruction Sure

Solution  2196922.1 :   How To Check Past Fluctuations In The Associations  


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




In this Document
Goal
Solution


Created from <SR 3-13475432251>

Applies to:

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

Goal

If the fluctuations are over, here is described what can be run if the data have not yet been overwritten.
 

Solution

- pass:loc=:cmd="connmgr -n"
- pass:loc=:cmd="connmgr -l"
- pass:loc=:cmd="linkinfo -a " (if the bouncing is at the link layer)
- pass:loc=:cmd="linkinfo -l " (if the bouncing is at the link layer)
- rept-stat-slk:loc=:port=:l2stats=both (if the bouncing is at the link layer)
- rtrv-log:sdate=::stime=:etime=
- rtrv-trbl:loc= (to check any troubles in one card which could impact the fluctuation)
- rtrv-obit:loc= (to check any troubles in one card which could impact the fluctuation)

Also checking the .CSV measurements files and see the link outage counters.

What I would recommend this is to have a dedicated computer connected every day to the Eagles with TRM setting having all=yes, and having a capture running that you save every day somewhere to have an history.
 


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