NTP Servers Configured but not Operational: Check Point Configuration Alert Guide
indeni uses different commands for different devices to determine if NTP is working. Examples: See here
This is a real life sample alert from the leader in Proactive Network Management: indeni
Description:
While NTP is configured on this device it does not seem to be operating correctly for all of the configured servers.
indeni will re-check this alert every 1 minute. If indeni determines the issue has been resolved, it will automatically be flagged as such.
Problematic NTP Servers:
1.1.1.1:
Executed command “ntpdate 1.1.1.1” with the response:
27 Aug 12:36:30 ntpdate[29924]: no server suitable for synchronization found
Manual Remediation Steps:
Review the NTP configuration, firewall rules, routing tables and other elements of the network to determine the cause.
How does this alert work?
indeni uses different commands for different devices to determine if NTP is working. Examples:
- On many Linux-based OS’s, indeni will use ntpdate for each configured NTP server (essentially forcing an NTP update and reviewing the results).
- On Cisco devices and Juniper JunOS devices, “show ntp associations”.
- On Check Point IPSO devices and Juniper ScreenOS devices, ntpq or ntpdate depending on version.
- On Fortinet Fortigates, “diag sys ntp status”.