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-77-2197296.1
Update Date:2017-05-17
Keywords:

Solution Type  Sun Alert Sure

Solution  2197296.1 :   Message Timestamping Issue On EAGLE Running R46.3 May Affect Data Correlation On PIC  


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




In this Document
Description
Occurrence
Symptoms
Workaround
Patches
History
References


Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.3 to EAGLE 46.3 [Release EAGLE 46.0]
Oracle Communications Performance Intelligence Center (PIC) Software - Version 10.1.0 and later
Tekelec

Description

TSC Synchronization is an option for the Eagle that will allow all cards in the system, which contain a Time Slot Counter, to synchronize with one another. The ability to have synchronized timing between cards is used in optional applications such as system wide message time stamping. For the TSC Sync feature to work, EAGLE requires a valid external clock source connected to it, either a BITS or a HS (High Speed) clock. However EAGLEs running R46.3.0.0.x are unable to derive clock for TSC sync feature from HS clocks. This is impacting system wide message time stamping on EAGLEs which are not connected to a valid BITS (Composite) clock source. This may affect data correlation based on message timestamps (added by EAGLE) on monitoring solutions like PIC, as the messages getting copied on to it will have the EAGLE timestamps set to zero.

Occurrence

This issue will impact EAGLE system wide message time stamping when all of the following condition are true

  1.  EAGLEs running R46.3.0.0.X release
  2.  TSCSYNC and EISCOPY features are tuned ON for Integrated Monitoring Support on EAGLE
  3.  EAGLE is not connected a valid BITS/Composite clock source (although a valid HS clock source is available)

Sample capture:

Below sample capture shows TSCSYNC and EISCOPY features are tuned ON for Integrated Monitoring Supprt on EAGLE

> rtrv-feat

    eagle11 16-10-27 00:11:29 MST  EAGLE 46.3.0.0.2-68.28.0
    EAGLE FEATURE LIST
    GTT      = on      GWS      = off     NRT      = off
    LAN      = off     CRMD     = off     LFS      = off
    MTPRS    = off     FAN      = on      DSTN5000 = off
    WNP      = off     CNCF     = off     TLNP     = off
    SCCPCNV  = off     TCAPCNV  = off     IPISUP   = off
    PLNP     = off     NCR      = off     ITUMTPRS = off
    SLSOCB   = off     EGTT     = off     VGTT     = off
    MPC      = on      ITUDUPPC = off     MEASPLAT = on
    TSCSYNC  = on      E5IS     = on;

> rtrv-eisopts

    eagle11 16-10-27 00:11:45 MST  EAGLE 46.3.0.0.2-68.28.0
    EIS OPTIONS
    --------------------------------
    EISCOPY = ON
    FAST COPY OPTIONS
    --------------------------------
    FCGPL = IPSG      FCMODE = FCOPY
    FCGPL = IPGHC     FCMODE = OFF
    --------------------------------
;

Below capture shows EAGLE is not connected a valid BITS/Composite clock source (although a valid HS clock source is available)

> rept-stat-clk

    eagle11 16-10-27 00:12:14 MST  EAGLE 46.3.0.0.2-68.28.0
    COMPOSITE                            PST           SST       AST
        SYSTEM CLOCK                     IS-NR         Idle      -----
    ALARM STATUS = No Alarms.
        Primary Comp Clk 1114   (CLK A)  OOS-MT        Fault
        Primary Comp Clk 1116   (CLK B)  OOS-MT        Fault
        Secondary Comp Clk 1114 (CLK A)  OOS-MT        Fault
        Secondary Comp Clk 1116 (CLK B)  OOS-MT        Fault
 
    Clock      Using       Bad
    CLK A      13          0
    CLK B      0           0
    CLK I      0           --
 
    Prefer Clock A   for TSC CLOCK
 
    HIGH SPEED                            PST           SST       AST
        SYSTEM CLOCK                     IS-NR         Active    -----
    ALARM STATUS = No Alarms.
        Primary HS Clk 1114  (HS CLK A)  IS-NR         Active
        Primary HS Clk 1116  (HS CLK B)  IS-NR         Active
        Secondary HS Clk 1114(HS CLK A)  IS-NR         Idle
        Secondary HS Clk 1116(HS CLK B)  IS-NR         Idle
 
    HS CLK TYPE 1114     = RS422
    HS CLK LINELEN 1114  = -----
    HS CLK TYPE 1116     = RS422
    HS CLK LINELEN 1116  = -----
 
    Clock      Using       Bad
    HS CLK A   1           0
    HS CLK B   0           0
    HS CLK I   1           --
 
    Command Completed.
;

Symptoms

LIM and STC cards in the system may generate "Module ntp_utl.c Line 1471" severity-1 troubles with first 16 bytes set to 0 as shown below:

    Card xxxx   Module ntp_utl.c  Line  1471  Class 0001  Severity 1
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
        00 00 00 00 a7 a5 2f dd ca ee 96 dc dd b6 98 00  ....../.........
        dd b6 98 00                                     ....

 

Note: Missing NTP broadcast from PIC can also cause above severity 1 trouble on EAGLE

Workaround

GPL (Generic Program load) with fix is available on MOS for EAGLE 46.3.0.0.X releases. 

Workaround other than patch should not be executed without approval from EAGLE CoE. Each execution of the procedure requires a SR and a CoE collab SR.

Patches

Permanent fix is available in EAGLE release 46.3.1.

Additionally a new OAMHC and BLMCAP GPL (Generic Program load) containing fix is provided via MOS for EAGLE 46.3.0.0.X releases.     
Release 46.3.0.0.X - Patch 25162346

The fix resolves the following bugs:

  • 24834411 - "NTP_UTL.C LINE 1471" SEV-1S WITH 1ST 16 BYTES SET TO 0
  • 24425434 - "TSC CLOCK IS UNAVAIL" & CLOCK FAILED ALARMS

Follow below steps after applying the new OAMHC and BLMCAP GPL to verify that the EMP data are getting transferred to PIC with correct timestamps (if EMP data not coming in PIC with valid timestams then contact TAC via an SR):

  1. Run rtrv-trbl:loc=1113/1115 and see ntp_utl.c Line 1471" sev-1s with 1st 16 bytes (ETS) set to 0 is not occurring any more after applying the work around.
  2. Check with PIC system to verify if EMP data is received correctly.
Only E5-MASP cards need to be flashed with new BLMCAP GPL. So load BLMCAP on the E5-Disks as TRIAL GPL.

History

 26-OCT-2016 - KM Document Created.

 06-DEC-2016 - KM Document updated with patch number

References

<BUG:24834411> - SR: R46.3 - "NTP_UTL.C LINE 1471" SEV-1S WITH 1ST 16 BYTES SET TO 0
<BUG:24425434> - SR: R46.3 - "TSC CLOCK IS UNAVAIL" & CLOCK FAILED ALARMS

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