SyslogSeverityMatchFound CM7

Answered Question
Jan 4th, 2012
User Badges:

I recieved this alert yesterday and also today, any ideas as to what could be causing this?


At Wed Jan 04 07:01:05 EST 2012 on node 10.1.144.12, the following SyslogSeverityMatchFound events generated:

SeverityMatch - Critical ntpRunningStatus.sh: Primary node NTP server, icmcucmpub, 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'.

Correct Answer by Chris Deren about 5 years 7 months ago

It looks good now, it looks like you might have had some communication issues with your NTP server when the alert was generated. perhaps some network hickups?


Chris

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Chris Deren Wed, 01/04/2012 - 07:33
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 IP Telephony, Contact Center, Unified Communications

This is very self explanatory, looks like there are issues with NTP on the Publisher, as recommended investigate by going to CLI of that server and enter 'utils ntp status'.


HTH,


Chris

jason._charles@... Wed, 01/04/2012 - 08:22
User Badges:

I ran the utils ntp status on the publisher and received the following information back:


Correct Answer
Chris Deren Wed, 01/04/2012 - 08:33
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,
  • Cisco Designated VIP,

    2017 IP Telephony, Contact Center, Unified Communications

It looks good now, it looks like you might have had some communication issues with your NTP server when the alert was generated. perhaps some network hickups?


Chris

jason._charles@... Thu, 01/12/2012 - 05:32
User Badges:

The same error messge came up today, I wonder if it was another network glitch.



ntp status
ntpd (pid 3935) is running...

     remote           refid              st t when poll  reach   delay   offset  jitter
==============================================================================
*127.127.1.0      LOCAL(0)        10 l    30     64  377    0.000    0.000   0.004
10.1.201.106    129.6.15.29      2  u  662 1024  377    3.489  292.067 137.236


synchronised to local net at stratum 11
   time correct to within 12 ms
   polling server every 1024 s

Current time in UTC is : Thu Jan 12 13:30:28 UTC 2012
Current time in America/New_York is : Thu Jan 12 08:30:28 EST 2012
admin:

Actions

This Discussion

Related Content