NTP on CS1000E

[RyanEOD]

So, or clock keeps working its way to being 4-5 minutes off. So, I was trying to set it up to use a NTP server and sync off of that. Somehow I don't think I am configuring it correctly in the Element Manager. Any help? Thanks!

 

[Malcybood]

There is a limitation on CS1000 v4.5 for NTP.

This is fixed in 5.0 and above I believe.

 

[RyanEOD]

I am running 5.0. I just don't know the proper way to configure a to a NTP server. I am trying to Microsoft recommended NTP ones but nothing seems to work without errors.

 

[ansellrk]

You either need a time server within your network or allow your Firewall to pass NTP requests out to the internet (there are loads of time servers out there!). We have purchased a rack mounted time server for our main computer room and send all NTP requests to it this is a more secure way of doing NTP and it works much better!

You can also configure a microsoft time server on a Windows server (for free NTP) but in our experience this is crap. It is worth the small investment in a proper device.

With a proper time server the CS1000 (v5.0) works fine and keeps perfect time.

 

[RyanEOD]

Well I keep getting errors for some reason and it doesn't appear the firewall is blocking it. I go into Element Manger, Tools, Date and time. I have under my Network Time Protocol that it is enabled but every time I hit Sync now I get a Last Synchronization Error at the time I clicked Sync Now.

Also my Packets Sent: 16
Packets Received: 4

So, I go into the configure of the NTP;

For Communication Path I have Directly from Call Server,

The Primary Server is IP Address; 152.1.58.124 (NTP server found on internet)

Transfer Mode is Insecure. No Secondary Server, and Automatic Background Sync is turned off.

Any ideas? Thanks!

 

[RyanEOD]

Any ideas?

 

[ansellrk]

Yes... I have an idea...

Directly from call server? Call server is on the ELAN only which is normally a closed network... non routeable. Try changing your NTP to go via signalling server which is on the TLAN.

 

[RyanEOD]

Ok I changed it to: Through the Signaling Server

still giving me an error and only up to 22 Packets sent and 4 received.

 

[ansellrk]

and it still has an error from the "SYNC NOW" you have just done? My packets sent are 11, received 6... check last sync error is not from last time you tried.

 

[RyanEOD]

Yeah seems to be still broke:

Last Synchronization Error: 15:53:35 PM on Tuesday June 10, 2008
Packets sent: 25
Packets received: 4

 

[ansellrk]

mmmm... I don't know what else to suggest other than trying an internal one. You are certain Firewall is not blocking outbound or inbound NTP requests? Some Firewalls will act as a STRATUM III NTP server too?

 

[RyanEOD]

Being told we aren't blocking anything outbound.

You know which ports it might be so I can do some checking? And how would I find out which IP it is coming from?

 

[ansellrk]

Yep, NTP uses port 123. The source IP will be the TLAN address of your leader signalling server.

 

[ansellrk]

Of course you can check Firewall drops against destination address which you know already... NTP uses UDP port 123 BTW.

 

[RyanEOD]

Is there anyway to test it with my computer sitting here at my desk? Besides clicking the Sync Now button?

 

[ansellrk]

I only know that way... there is probably a way through the console, but I have no idea what it is. Sorry.

 

[911guru]

Trace the connection with wireshark or try a different NTP server. Many will not let you constantly ping them.

Try time.windows.com 207.46.232.182

911Guru

http://pbx-e911.com

E911 FAQs are located at:

http://www.tek-tips.com/faq.cfm?pid=798&handle=911guru

 

[RyanEOD]

I tried to ping the time.windows.com and I get it to resolve to 207.46.232.182 but keep getting Request timed out. Don't know if SNMP is turned off on those servers though. Anyone else able to ping it?

 

[RyanEOD]

Ok I tried something else;

time.nist.gov

Which I am able to ping from my computer. Ok now how do I figure out the TLAN IP address so I can make sure the firewall is open?

 

[RyanEOD]

WOW So I think it is fixed. I blanked out the Communication Path, hit sync now and didn't get an error. STRANGE.