![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||
Solution Type Sun Alert Sure Solution 2197296.1 : Message Timestamping Issue On EAGLE Running R46.3 May Affect Data Correlation On PIC
In this Document
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 DescriptionTSC 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. OccurrenceThis issue will impact EAGLE system wide message time stamping when all of the following condition are true
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 > rtrv-eisopts eagle11 16-10-27 00:11:45 MST EAGLE 46.3.0.0.2-68.28.0 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 SymptomsLIM 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
Note: Missing NTP broadcast from PIC can also cause above severity 1 trouble on EAGLE
WorkaroundGPL (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. PatchesPermanent 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. The fix resolves the following bugs:
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):
Only E5-MASP cards need to be flashed with new BLMCAP GPL. So load BLMCAP on the E5-Disks as TRIAL GPL.
History26-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 |
||||||||||||||||||||||||
|