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-75-1675062.1
Update Date:2017-01-20
Keywords:

Solution Type  Troubleshooting Sure

Solution  1675062.1 :   Data Collection Guide - Eagle STP Dynamic Data Base (DDB) issues  


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




In this Document
Purpose
Troubleshooting Steps
 Oracle Communications. Eagle Dynamic DataBase (DDB) issues
 Upload Files / Attachments


Applies to:

Oracle Communications EAGLE (Hardware)
Oracle Communications EAGLE (Software)
Tekelec

Purpose

 This Document is intended to facilitate Troubleshooting for Oracle Eagle STP Dynamic Data Base (DDB) issues.

Troubleshooting Steps

Oracle Communications. Eagle Dynamic DataBase (DDB) issues

 

Upload Files / Attachments

Please obtain and upload the following log files:

    • Logfile created during the execution of below mentioned commands.(Mandatory)

    • Please upload any other relevant screenshots that you feel would help with the troubleshooting of this issue.

Additional Information

 

1. Please indicate how the issue is affecting your business.

  • Is this issue for a Production or Lab system?

  • What impact is this fault currently having on system functionality?

 

 

 2.  Answer all of the following questions:                   

  • When was the issue discovered?

  • Are any cards in the system booting or generating obits?

  • Have there been any recent network events that would generate excessive network management messages?  (i.e. fiber cut or other transport imparement?)

  • Are there any GPL alarms?

  • Are there any IMT alarms present?

 

 

 

3. Please collect the following commands from the Eagle command line. These are a mandatory requirement

• clr-imt-stats:all=yes

• rept-stat-trbl:display=timestamp

• rept-stat-mux

• rept-stat-imt:mode=full

• rept-imt-info:report=hiprerr (or report=hipr2err or both depending on system configuration)

• rept-imt-lvl1:r=summary:sloc=1201:eloc=1115 

• rtrv-log:dir=bkwd:snum=0911:enum=0912:num=40

• rtrv-log:dir=bkwd:snum=0311:enum=0316:num=100

 

If one or more point codes is observed to be changing state for no reason issue the command

“rst-dstn:force=yes”

 for that point code and watch to see if this action clears the inconsistency.

 

• rept-stat-ddb:display=all

• dbg-ddb:loc=<loc of card reporting inconsistency>:tbl=rte:audtype=uc:action=disp:rloc=<a card of the same application that is consistent>

• If there are five or fewer cards inconsistent try booting them with init-card

• If there are more than five inconsistent consult with an engineer

  

 


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