RTMT REPORTING NTP EVENTS

[robert.cooley]

RTMT is porting the following from my Publisher and both Subscribers.

At Wed May 28 15:10:11 BST 2014 on node 10.211.7.100; the following SyslogSeverityMatchFound events generated:  SeverityMatch : Critical MatchedEvent : May 28 15:10:04 dbs-cm-donpub01 user 2 ntpRunningStatus.sh: The local NTP client is off by more than the acceptable threshold of 3 seconds from its remote NTP system peer.  The normal remedy is for NTP Watch Dog to automatically restart NTP.  However; an unusual number of automatic NTP restarts have already occurred on this node.  No additional automatic NTP restarts will be done until NTP time synchronization stabilizes. This is likely due to an excessive number of VMware Virtual Machine migrations or Storage VMotions.  Please consult your VMware Infrastructure Support Team. AppID : Cisco Syslog Agent ClusterID :  NodeID : dbs-cm-donpub01  TimeStamp : Wed May 28 15:10:04 BST 2014

I have run utils ntp restart on each server and still get the same error.

Any help please?

[Brian Meade · Accepted solution]

What does the output of "utils ntp status" look like?  What type of NTP source are you using?  What stratum is the source?

[David Hailey · Accepted solution]

First thing is to post the status of the utils ntp status as Brian noted above.  However, there are also a number of NTP-related bugs in CUCM 8.6 and higher.  I have had several customers with similar issues and it is generally been purely cosmetic.  See the following thread, review the bug IDs, and you may consider opening a TAC case as well:

https://supportforums.cisco.com/discussion/11275801/problem-ntp-after-upgrade-and-install-vmtools

Be sure to take a look at Aaron Harrison's recommendation as well in that thread.  He always has solid advice in the forum.

Hailey

Please rate helpful posts!

[Aman Soi]

Hi Robert,

you can also check for ntp version. As per SRND , The external NTP server specified for the primary node should be NTP v4 (version 4) to avoid potential compatibility, accuracy, and network jitter problems.

regds,

aman

[Aman Soi · Accepted solution]

Hi Robert,

.In addition to what Brian has said,check for NTP reachability as well. 

regds,

aman

[robert.cooley]

I have attached a jpeg showing output of publisher and 1 subscriber.  Publishers NTP source is Cisco 6500 and subscriber NTP source is Publisher on the same UCS. There are three scconds on the time difference to console from one device to other.

[Brian Meade]

I think the problem is most likely the 2 different NTP servers on the publisher with 2 different sources.  Can you remove one of them to just have one NTP server listed?

[richb1971]

Hi Robert,

I've got same issue on our CCX (8.5.1). It too has 2 NTP sources with different sources. Did you remove one of yours? Did you fix this issue

Rich

[robert.cooley]

Correct,  I just have one NTP source now and no errors.