<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
what version of CM? Many changes of NTP especially this one:<br>
CSCsk70971 publisher NTP down if configured NTP down or unreliable <br>
<br>
my interpretation:<br>
something on the network NTP source changed<br>
now subscribers giving error that pub is unreliable<br>
<br>
this is expected if pub cannot sync to NTP source. what changes did
they make? it is still a viable NTP source for hte publisher? if not,
publisher will use local clock which makes it an invalid source for all
subs.<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/netstruc.html#wpmkr1185636">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/netstruc.html#wpmkr1185636</a><br>
<div style="display: inline;"> </div>
<br>
/Wes<br>
<br>
Ed Leatherman wrote:
<blockquote
style="border: medium none ! important; padding-left: 0px ! important; padding-right: 0px ! important; margin-left: 0px ! important; margin-right: 0px ! important;"
cite="mid:AANLkTin8R1uRYomrYCkgezukkkH07CDOEBA_XrV0=GOY@mail.gmail.com"
type="cite">
<pre wrap="">Hi folks,
Our operations team updated the NTP service recently (infoblox), and
right after that happened, I started getting syslog errors per below
on two different CUCM 7 clusters, both of which use that NTP server.
ntpRunningStatus.sh: Primary node NTP server, OWP-PUB, 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'.
Looking at the status on these servers, the pub looks OK but the subs show:
utils ntp status on all secondary nodes comes up with (example):
remote refid st t when poll reach delay offset jitter
==============================================================================
*127.127.1.0 LOCAL(0) 10 l 32 64 377 0.000 0.000 0.004
10.192.20.10 .STEP. 16 u 488 512 376 0.244 16.553 0.052
Restarting NTP on all nodes fixes the problem temporarily (NTP status
goes back to normal) but only for a short time.
The NTP logs don't show anything other than what appears to be the NTP
service restarting every 30 minutes.. is this normal?
11/16/2010 23:00:02
sd_ntp|*********************************************************|<LVL::Info>
11/16/2010 23:00:02 sd_ntp| Running sd_ntp. Process Id=12302
|<LVL::Info>
11/16/2010 23:00:02
sd_ntp|*********************************************************|<LVL::Info>
11/16/2010 23:00:02 sd_ntp||<LVL::Info>
11/16/2010 23:00:02 sd_ntp|[528] Command Line parameters: -list -s|<LVL::Info>
11/16/2010 23:00:02 sd_ntp|[585] The file /etc/ntp.conf exists|<LVL::Debug>
11/16/2010 23:00:02 sd_ntp|[421] /etc/ntp/drift file is not changed|<LVL::Debug>
11/16/2010 23:00:02 sd_ntp|[603] Listing all the servers|<LVL::Debug>
11/16/2010 23:00:02 sd_ntp|sd_ntp exitinng normally.|<LVL::Info>
In both clusters, the pub and most or all of the subs are on the same
VLAN and physical switch.
What other traces can I look at on CM to troubleshoot this? Anyone
know if there is a debug for the process that's generating my syslog
errors?
I want to make sure it's not an error on my end and hopefully have
some better information on whats broke before I go back to the
operations group. All the IOS routers using infoblox for NTP appear to
be working just fine, so they see no problems :)
Thanks in advance!
</pre>
</blockquote>
</body>
</html>