NTP updated Call Server Time

[Biskad]

Running CS1000 version 5.5, The DST patch was applied a couple weeks ago.
DST was updated correctly on Sunday morning; and was fine until 2:15am this morning. I printed the history and found this:

% TIM000 02:00 9/3/2009 CPU 1
%
% DTC010
%
%
% DTC001
%
%
% AUD000
% NTP is not running in secured mode
% " ERR0061": Delta between server clock and system clock exceeds the critical threshold level.
%
% Updated Call Server Time to 01:15:56 on 9-3-2009
%
% DTC010
%
%
% DTC001
%
%
% TIM000 01:30 9/3/2009 CPU 1

This will happen periodically where it will correct the time but this it the first time it moved the time one hour behind. @ 2:15am today it moved the time to 1:15am.
Can anyone tell me why this would happen? The server it is syncing to has the correct time.

 

[GHTROUT]

I assume because of Daylight Saving Time settings... You did not want that?

~~~
[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[bigindian65]

With the 5.0 patch, the DST box instruction was to not check it once the patch was applied, leaving the updates/time to the NTP protocol.

Mato' Was'aka

 

[Biskad]

It changed back this morning(Monday), not Sunday morning. Sunday morning it moved the time one hour ahead which is what it was supposed to do.

 

[Biskad]

bigindian65, Box was unchecked, again everything was fine until Monday morning @ 2:15.

 

[GHTROUT]

You're posts are timeless (timefull?) today big-I. I've put in a few good words to the "Thank bigindian65 for this valuable post!" department.

~~~
[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[bigindian65]

lmao.you're kill'n me Gene....call me crazy, but if I went off by an hour, I would check the damn box....

Mato' Was'aka

 

[GHTROUT]

It does seem odd that it changed Monday AM though, doesn't it. I bet it has do with sumpin computerated or electronical.

~~~
[©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators

 

[nhphoneguy]

I had the same issue today, Monday Morning-
Time changed on Sunday as scheduled,
Today it changed backed and DST was unchecked in element manager. Unless someone offers something concrete, I will probabably open a case with Nortel.

 

[Slider55]

Does this look set up correct? 172.20.8.1 is the NTP server. Do I need to build a gateway in the PBX call server for elan to be able to ping the 172.20.8 network?
I'm scratchn' to figure out how this thing works.
Thanks for the help...

prt route
Route entry(ies) not found.

OK

=> prt elnk
ACTIVE ETHERNET: "PRIMARY_ENET" "137.135.128.253"
INACTIVE ETHERNET: "SECONDARY_ENET" "137.135.128.254"
OK



stat ntp
CURRENT NTP CONFIGURATION
NTP Status: ENABLED
Primary IP address: 172.20.8.1
Secondary IP address: 0.0.0.0
UTC Offset: -06:00
Last Updated: 12:30:29 on 9-3-2009
Delta: 04
Threshold: MINIMUM
Security Mode for Primary: INSECURE
Security Mode for Secondary: INSECURE
Synchronization Status: ACTIVE
Mode of Synchronization: BACKGROUND

COUNTERS
Packets Sent: 68
Packets Received: 68
LAST NTP CONFIGURATION
NTP Status: ENABLED
Primary IP address: 172.20.8.1
Secondary IP address: 0.0.0.0
UTC Offset: -06:00
Delta: 00
Threshold: MINIMUM
Security Mode for Primary: INSECURE
Security Mode for Secondary: INSECURE
Syncing Mode: ACTIVE

LAST SYNCHRONIZATION ERROR
Date and Time: 12:30:26 on 9-3-2009
Type of Error: ERR0063


=> ping 172.20.8.1

PING 172.20.8.1 FAILED

 

[bigindian65]

I think you answered your question, they have to talk.

Mato' Was'aka

 

[Biskad]

Although nortel directs us to keep DST unchecked after applying the patch when using NTP, that only worked for 24 hours in my case. My PBX UTC was @ -05:00 needless to say the time was wrong.
After checking the DST box the UTC changed to -04:00 and now the time is correct. I wonder if that patch was tested for more than 24hrs after being applied, just hope nothing strange happens again.

 

[Slider55]

Does the NTP server update through the elan on the PBX core or does it update through the tlan on the sig server and then the sig server update the core? How does this work?

 

[MagnaRGP]

Depends on how you set it up. My preference would be the TLAN on the SS. Otherwise, you will need to change your network so that the 137 addresses are routable to hosts on the 172 network.

 

[GTexx]

Here is my take on the situation. If you are updating the time and date using the NTP and through the signaling server, then this is what I suspect. The DST box was unchecked and the schedule update/synch interval is set to every 24 hours. What I did to correct this using an NTP is to select the DST checkbox and do a re-synch. Remember the NTP is providing GMT Timez, if your are in the EST time zone then the Time zone would be -5:00, with the DST checked it should adjust to -4:00 which is what you would want. Hopefully this helps.

 

[nhphoneguy]

I opened a case and Nortel determined that patch p26202 is defective. Waiting for an updated patch at this point.

 

[bigindian65]

I have NTP in effect with DST checked on 5.5 running with no problems.

Mato' Was'aka