No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

U2000 sends alarm to OSS with incorrect time

Publication Date:  2012-07-25  |   Views:  297  |   Downloads:  0  |   Author:  Cezar Tataru  |   Document ID:  EKB0000516730

Contents

Issue Description

U2000 management system it is sending alarms form the NE elements to OSS with incorrect time using Corba interface.
The time stamp for the alarms is - 3 hours(2h from local time timezone(GMT +2) and 1h (DST)).
Both U2000 and NE have the setup the correct time (2h from local time timezone(GMT +2) and 1h (DST)).
In U2000 the alarm appear with the correct time(from U2000 and NE)
Problem: the alarms are send to OSS with UTC time(Coordinated Universal Time)
      

Alarm Information

Null

Handling Process

Modiffy the 2 files:
u2000/server/nbi/corba/conf/ii_corbaagent_bundle u2000/server/nbi/corba/conf/ii_imap_corbaagent_bundle
Configuration to be done:
#@ ( drfault 0: UTC ; 1 :local )
#| TimeZoneRefPoint
TimeZoneRefPoint = 1
Restart the Corba Services(if not working restart all the services)

Root Cause

Check the U2000 configuration files:
u2000/server/nbi/corba/conf/ii_corbaagent_bundle u2000/server/nbi/corba/conf/ii_imap_corbaagent_bundle
Here we saw that -  TimeZoneRefPoint is set to 0(UTC)
#@  ( drfault 0: UTC ; 1 :local )
#| TimeZoneRefPoint
TimeZoneRefPoint = 0
      

Suggestions

Suggestion:
Use CORBA Notiffy Tests Tool to capture alarms sent using CORBA.
Check if the timestamp of the alarm generated is the same with the timep stamp from U2000