NTP_Response Error: unable to contact host, You might want to try with type = SNTP.
This can happen if the local host or remote NTP server ip address is not being updated in the /etc/ntp.conf file.
Type SNTP: Configured probe on client and you can only monitor “Response time exceeds” and “No contact with server” for this.
Type NTP: Configured probe on server and you can enable monitoring for below monitors.
1) If the machine where ntp_response probe is deployed is an NTP client (NTP service running on server) and synchronizing with NTP server, "SNTP type" would work.
2) If the machine where ntp_response probe is deployed is an NTP server, then NTP type will work.
Once the probe is deployed and adding the required host profile for ntp_response, please follow the below mentioned steps.
-6option is required before an
IPv6address. So only third line will be enough in case NTP server and client (probe machine) are different.
Test the connectivity on ntp_response probe and confirm whether it works or not.
ntp_response probe documentation:
Reference Documents from Redhat:
The ntp_response probe does not currently support chrony ( If the device is a NTP v4 - RFC5905)
Check if the server is running the chrony daemon rather than the ntp daemon.