NTP_Response Error: unable to contact host

Document ID:  TEC1386156
Last Modified Date:  07/07/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Unified Infrastructure Management

Releases

  • CA Unified Infrastructure Management:Release:8.4
  • CA Unified Infrastructure Management:Release:8.2
  • CA Unified Infrastructure Management:Release:8.31

Components

  • UNIFIED INFRASTRUCTURE MGMT:CAUIM
  • UIM NTP RESPONSE:UIMNRP
Issue:

NTP_Response Error: unable to contact host, You might want to try with type = SNTP.

                                11.jpg

Environment:
UIM: 8.3, 8.4 or later NTP_Response: 1.40
Cause:

This can happen in case if the local host or remote NTP server ip address is not being updated in /etc/ntp.conf file.

Workaround:

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 
        Offset exceeds 
        Jitter 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.

  1. Login to NTP Server with root user (Eighter it could be local host or remote host)
  2. 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>
    • 2.jpg
    • Note: The -6 option is required before an IPv6address. So only third line will be enough in case NTP server and client (probe machine) are different.
  3. Restart the NTP service by running the command. "service ntpd restart"
  4. Confirm the service is running using command "ps -eaf | grep -i ntp"
    1. 3.jpg
  5. 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.

                   44.jpg

 

 

 

Additional Information:

NTP_Response probe documentation can be found here.

        https://docops.ca.com/ca-unified-infrastructure-management-probes/en/alphabetical-probe-articles/ntp_response-network-time-protocol-response-monitoring

Reference Documents from Redhat:

        https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html

 

        https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-Understanding_the_ntpd_Configuration_File.html

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >