NTP error while insalling cucm 8.5 subscriber

[osama_abdo]

Please find below the error i'm facing :

the output of "utils ntp status" is

admin:utils ntp status

ntpd (pid 4814) is running...

     remote          refid     st t when poll reach   delay   offset jitter

==============================================================================

10.0.1.21       10.0.1.22       3 u   21   64 377   0.346 126.507 51.418

10.0.1.22       10.0.1.22       2 u  14   64 377   0.239 129.458 45.550

unsynchronised

time server re-starting

   polling server every 64 s

Current time in UTC is : Sun Sep 25 14:48:24 UTC 2011

Current time in Africa/Harare is : Sun Sep 25 16:48:24 CAT 2011

------------------------------------------------------------------------------------------------------------------------------------------------------------------

The two server are used to install publisher and both  are accessible when navigating from OS any one has an explanation ,and why it's

unsynchronized .

[Calin Lupas]

Out of a few US-accessible NTP stratum one server, I found that only this one worked for me:

162.213.2.253 found on this link

Hope it helps!

[abbaswalikhan]

HI,

our pub says

    remote           refid      st t when poll reach   delay   offset  jitter

==============================================================================

127.127.1.0     LOCAL(0)        10 l   50   64  377    0.000    0.000   0.001

*172.22.13.101   51.63.224.28    8 u   25 1024  377    0.598    0.909   0.102

synchronised to NTP server (172.22.13.101) at stratum 9

   time correct to within 129 ms

   polling server every 1024 s

shows startum is set to 8 (as you were mentioning that it should be between 1-8)

also the Primary NTP is showing st 9.

we are getting alot of NTP critical alerts from the RTMT regarding NTP as below,

At Tue Sep 04 07:31:01 BST 2012 on node 172.29.2.10, the following SyslogSeverityMatchFound events generated:

SeverityMatch : Critical

MatchedEvent : Sep 4 07:30:42 NCCGH-CCM-PUB user 2 ntpRunningStatus.sh: Primary node NTP server, 172.22.13.101, is currently inaccessible or down. Verify the network between the primary and secondary nodes. Check the status of NTP on both the primary and secondary nodes via CLI 'utils ntp status'. If the network is fine, try restarting NTP using CLI 'utils ntp restart'.

not sure why. can you please help.

thanks

Abbas

[Ganesh Babu]

Hi,

did you deleted the subscriber from the list of server(system-> server) and then added again, if you have done so what i would suggest is to delete the Subscriber from the list of server and restart the publisher CUCM and then add the subscriber CUCM in the list of servers, hope it will help.

Please make sure there is no issue with the network connectivity,

thanks,