NTP_Response Error: unable to contact host, You might want to try with type = SNTP.
This can happen in case if the local host or remote NTP server ip address is not being updated in /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.
Response time exceeds
No contact with server
Server is not updated from any peer
Server is not fully initialized
1) If the machine where NTP_Response probe is deployed is 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 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.
- Login to NTP Server with root user (Eighter it could be local host or remote host)
- Open /etc/ntp.conf file and add the below lines and save it.
- restrict 127.0.0.1
- restrict -6 ::1
- restrict <IP Address of Probe Machine>
- restrict <IP Address of Local Machine>
- Note: The
-6option is required before an
IPv6address. So only third line will be enough in case NTP server and client (probe machine) are different.
- Restart the NTP service by running the command. "service ntpd restart"
- Confirm the service is running using command "ps -eaf | grep -i ntp"
- Test the connectivity on NTP_Response probe and confirm whether it works or not.
In case if still the issue is not resolved, please feel free to contact CA UIM Technical support team.
NTP_Response probe documentation can be found here.
Reference Documents from Redhat: