We recently installed new LAN gear and assigned new IP addresses to the systems in a few locations. Now it seems that some of those locations cannot reach our internal NTP servers to get the correct time updates. Nothing about the NTP servers themselves has changed, they are not in the locations that have new addressing. The network guys say it's reachable from there (and I can ping the NTP server from the CM server)but I'm not getting synched. Anyone run into this before?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Network Time Synch issues - CM 3.1
- Thread starter dabrow
- Start date
sroush
Programmer
- Jun 5, 2007
- 47
I'd bet one of the new routers is dropping the NTP packets. NTP is a UDP protocol. Ping uses ICMP, so pinging does not prove that the "new" router(s) will pass NTP packets.
Go to shell on the CM and type this:
nmap -sU -p123 "IP_address_or_name_of_NTP_server"
(I think nmap is on the CM system)
This will tell you if the CM can see the NTP port on the server.
steve
Go to shell on the CM and type this:
nmap -sU -p123 "IP_address_or_name_of_NTP_server"
(I think nmap is on the CM system)
This will tell you if the CM can see the NTP port on the server.
steve
- Thread starter
- #3
Thanks for the feedback, I found the problem. Evidently, when you change the IP address of the management interfaces on the CM server, it won't re-establish connection with the NTP server until you "re-submit" the values on the NTP setup form again. I did that, and it synched right back up. I'm going to open a ticket with Avaya to raise the issue, just doesn't seem like that should be necessary.
- Status