Skip to content
CA Unified Infrastructure Management Probes
Documentation powered by DocOps

ntp_response (Network Time Protocol Response Monitoring) Release Notes

Last update September 24, 2018

The Network Time Protocol Response Monitoring (ntp_response) probe monitors the response of Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) servers. The probe measures the quality of a network connection through the following parameters:

  • Response time
  • Offset
  • Jitter
  • No contact with the server
  • Server not updated from any peer
  • Server not fully initialized


Revision History

This section describes the history of the revisions for the (ntp_response) probe.

Note:  Support case(s) may not be viewable to all customers.

Version Description State Date

What's New:

  • The probe supports monitoring within an IPv6 environment.

  • (IM Interface only) Added support for:

    • AES-128 encryption that is required for FIPS compliance

    • Monitor Windows systems where FIPS encryption is enabled Before you deploy the probe version 1.42 on your IM, you must enable the FIPS encryption on the system where the probe is deployed.

      Important! In a FIPS encryption enabled environment, you cannot configure the probe from Admin Console (AC) interface.

Fixed Defects:

  • The probe displayed incorrect values for NTP Response time on entering a value greater than 32000 ms through the probe configuration interface. Support case number 632899
  • (On Linux) The probe did not connect to the NTP Server after restarting the NTP services. Support case number 434182
GA January 2017

Fixed Defect:

  • The probe generated incorrect QoS messages. Support case number 305033
GA July 2016

What's New:

  • Added support for NTPv4.
  • Added a feature to select the NTP server version when configuring the probe.
GA February 2015
1.32 To view the updated alarm subsystem Id as, reinstall the probe after removing any previous version of the probe from the target robot. In case of upgrading the probe version, the alarm subsystem Id remains same as 2.5. GA April 2014
  • Fixed a defect to send clear alarm when response time is less than threshold.
  • Fixed a defect on sending QOS_DEFINITIONS on inactive profiles and when QOS are not checked.
  • Deactivated the test profile in the probe defaults.
  April 2013

Added Solaris support for the following:

  • SPARC 64 bit (10/11)
  • SPARC 32 bit
  • x86_64 bit (10/11)
  • x86_32 bit
  November 2012
1.24 Fixed SOC issues.   June 2012
1.23 Introduced source override for Alarm and QoS.   April 2012
1.22 Fixed SOC issues.   December 2011
  • Added support for reading alarm tokens from cfg.
  • Fixed token id mappings with alarm messages.
  March 2011
  • Added support for localized alarm messages.

  • Added fix to properly deploy the probe on 64-bit Linux machines

  March 2011
  • Added support for Windows 64-bits.
  • Added support for Linux (both 32-bits and 64-bits).
  • Added fix for proper severity level in alarms.
  • Added fix to send alarms on negative values of offset and jitter limits also.
  • Added NIS (TNT2) Changes.
  June 2010
1.04 Added sending of initial clear alarm on all profiles on startup and reconfigure.   May 2010
1.0 Fixed problem which sometimes caused program failure in the configurator when using the 'Test' button.   April 2004

Probe Specific Hardware Requirements

The ntp_response probe should be installed on systems with the following minimum resources:

  • Memory: 2-4GB of RAM. Probe's OOB configuration requires 256MB of RAM
  • CPU: 3GHz dual-core processor, 32-bit or 64-bit

Probe Specific Software Requirements

The ntp_response probe requires the following software environment.

  • CA Unified Infrastructure Management 8.0 or later
  • Robot 7.62 or later (recommended)
  • (to enable FIPS encryption) Bus (Robot) version 7.80
  • Java JRE 6 or later (required for Admin Console)
  • (From version 1.42) IPv6
  • Probe Provisioning Manager (ppm) probe version 2.38 and above (required for Admin Console)

Note: For SOC functionality, the probe requires NM server 5.6 or later and UMP 2.5.2 or later.

Was this helpful?

Please log in to post comments.