NTP server

Description

This module activates and configures the NTP (Network Time Protocol) server. The NTP server is responsible for providing the correct date and time to the different IP Phones.

Release notes

Show release notes
Version 1.9.0 - Early deployment
  • Feature: Convert plugins to new library model (M14774)
  • Potential update impact level 1 DONE: no critical impact expected. Update can be applied without risk of breaking critical functionality.: You will have to upgrade the Shell module and other modules too. Please verify the release notes of the Shell module 1.23.0 to find out which modules need to be upgraded. (M14774)

Version 1.8.3 - Early deployment
  • Bugfix: Removed false error when installing on a vSOP (M12492)

Version 1.8.2 - General deployment
  • Improvement: Use iburst for faster initial NTP sync (M4620)
  • Bugfix: Shell plugin was not able to resync NTP correctly (M4620)
  • Improvement: Reduce module installation time on high latency networks (M8766)

Version 1.8.1 - General deployment
  • Bugfix: Packages were not cached between SOP reboots (M7066)

Version 1.8.0 - General deployment
  • Improvement: Compatibility with baseline 3

Version 1.7.3 - General deployment
  • Bugfix: ntp-server tried to sync with ipv6 server when available (M4439)

Version 1.7.2 - General deployment
  • Bugfix: shell plugin broken. (M0003797)

Version 1.7.1 - General deployment
  • Bugfix: Watchdog reliability improvements

Version 1.7.0 - General deployment
  • Feature: Added support for baseline 2.0 (M0003103)

Version 1.6.0 - General deployment
  • Improved the watchdog for the NTP server

Version 1.5.0 - General deployment
  • Corrected stratum of local server to enable sync after connectivity loss
  • Restricted modify access
  • Add a plugin to SopShell to allow users to Resync ntp server/client, check the Synchronization and also check the current date/time

Version 1.4.0 - General deployment
  • Corrected stratum of local server to enable sync after connectivity loss
  • Restricted modify access

Version 1.3.0 - General deployment
  • Stopping NTP server before starting NTP server on module install
  • Synchronise system clock to hardware clock

Version 1.2.0 - General deployment
  • NTP server will be restarted when the NTP and local time are more then 1000 seconds apart

Version 1.1.0 - General deployment
  • initial version

Version 0.0.0 - Deprecated
  • Corrected stratum of local server to enable sync after connectivity loss
  • Restricted modify access
  • Add a plugin to SopShell to allow users to Resync ntp server/client, check the Synchronization and also check the current date/time

Module configuration interface

create_resource_form: .:/usr/share/escaux/glue/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib:/usr/share/escaux/glue/bin/gen_wiki_documentation/src/lib/

NTP server 1
NTP server 2
NTP server 3

Module configuration parameters

  • NTP server 1: Alternative NTP server to use (optional)
  • NTP server 2: Alternative NTP server to use (optional)
  • NTP server 3: Alternative NTP server to use (optional)

This can be left empty to use the default values: 

0.europe.pool.ntp.org
1.europe.pool.ntp.org
2.europe.pool.ntp.org

These are part of of the NTP Pool Project (http://www.pool.ntp.org/) and should be used if no customer-specific internal NTP server is available. If the SOP is not in Europe, a variant of these can be used (see http://www.pool.ntp.org/zone/@).

Unless there is a request to use a specific NTP server (e.g. a local one provided by the customer), it is recommended to always use 3 separate sources usually from the NTP Pool.
Copyright © Escaux SA