PBX Time 1

[JHerm]

Anyone have any idea why the time on Opt81 does not keep? I change it one day, and two days later it's 3 mintues behind again. Small issue but drives exec's nuts. Thanks

 

[trvlr1]

In load 2 there is an adjustment that can be set (TDTA to print and SDTA to enter the adjustment) All PBX tend to drift some and using this adjustment helps keep it on track. That being said, I have never seen one drift as badly as you say here, it looks like you might have some other issue going on. A couple of minutes a MONTH is excessive from my experience.

 

[bigindian65]

TDTA could be set wrong.

Mato' Was'aka

 

[acewarlock]

That is just the way life is in the Nortel world. you can make time adjustments in LD 2 that can speed up or slow down the clock as needed. in your case you want to speed it up. you will need to make adjustments every day or 2 until you get it right.


Set daily time adjustment
The time of day can be adjusted during the midnight routines to compensate
for a fast or slow system clock.
To print the current adjustment: TDTA X y
To set the adjustment: SDTA X y -- X Y
Legend
x = 0 (negative increment) or 1 (positive increment)
y = 0-60 second adjustment in increments of 100 ms




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[JHerm]

TDTA is 1 000, is that correct?

 

[acewarlock]

Did you read my post? It will answer your question.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[phonz1]

different on every PBX, but your TDTA is 1000, that's 1000ms. Post your LD 2 tdta here

 

[bigindian65]

yes = not being used because of the 000 so it isn't causing the slip.

make it 1 100

and what it for a couple days, and adjust from there

Mato' Was'aka

 

[JHerm]

acewarlock, yes, thanks for the reply, I think we posted at the same time.

 

[johnpoole]

here's a script that i run at login.. it's syncs the switch to the networked pc that i use..

proc main
integer iDay, iMonth, iYear, iMin, iHour, iSec
   string sSend
  
   ltimeints $LTIME iYear iMonth iDay iHour iMin iSec
   
   strfmt sSend "STAD %02d %02d %d %02d %02d %02d" iDay iMonth iYear iHour iMin iSec
   set txpace 20
   transmit "****^M"
 
  
   
   waitfor ">" forever
   
   transmit "ld 2^M"
   waitfor "."
   transmit "TTAD^M"
   waitfor "."
   transmit sSend
   transmit "^M"
   waitfor "."
   mspause 20
   transmit "TTAD^M"
   waitfor "."
   mspause 20
   transmit "****^M"
   
   
   endproc

the time is on the cpu or ssc card so changing one due to a bad clock is a little much... the adjust does work if you play withit for long enough.. the problem i've seen with that is on a larger switch the switch can gain time on cpu 0 and not on cpu 1...

john poole
bellsouth business
columbia,sc

 

[marcuspb]

It seems like I heard something about being able to use a time server in the near future.
Has anyone else heard/deployed that?

 

[Telephonist]

There was a patch released to correct time drift on the Pentium 4 processors - p23200_2

If you don't have P4 processors, it doesn't apply to your situation.

Even with the patch, I still have to tweak the time adjustment.

Software release 5.5 was supposed to allow synching with a network time server via Element Manager, but I think you would have to have a signaling server to do that.