NTP Server settings might not be applied in some circumstances
search cancel

NTP Server settings might not be applied in some circumstances

book

Article ID: 405706

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • At [Time Synchronization] setting (https://<vIDM FQDN>:8443/cfg/configuretimesync), it might fail to save the settings:

    Time Sync : NTP
    NTP Server: <NTP Server FQDN or IP address>

    After [Save] button pressed with the above settings, [NTP Server] settings are still blank.

  • When trying to set NTP Server by ntpServer.hzn and get the status, it also fails:

    /usr/local/horizon/scripts/ntpServer.hzn --set <NTP Server IP address>

    /usr/local/horizon/scripts/ntpServer.hzn --get

         <output>
                    server=<NTP Server IP address>

    /usr/local/horizon/scripts/ntpServer.hzn --status

          <output>
                 ă€€ntpstatus=error

  • The issue can be reproduced by selecting at least Windows Server 2019 as a standalone server (no Active Directory joined) with enabling NTP Server.

     

 

Environment

VMware Identity Manager 3.3.7

Cause

  • NTP Server’s Root Dispersion is greater than 5 seconds. For Windows Server, it can be checked by the following command:

    w32tm /query /status

    <output example>
     :
    Root Dispersion: 10.0000000s
    :
    If Root Dispersion is greater than 5 seconds, vIDM default configuration might fail to update NTP Server settings. 

Resolution

1. Login to vIDM appliance by root account (by SSH connection).

2. Copy timesyncd.conf for backup.

    cp /etc/systemd/timesyncd.conf /etc/systemd/timesyncd.conf.org

3. Open /etc/systemd/timesyncd.conf by vi editor.

4. Change #RootDistanceMaxSec=5 to RootDistanceMaxSec=20, save the file and terminate vi editor.

5. Restart  systemd-timesyncd.service:

     systemctl restart systemd-timesyncd.service

6. Try again NTP Server setting at [Time Synchronization] menu.

Additional Information

The appropriate value by RootDistanceMaxSec might vary depending on the environment and the configuration of NTP Server. Try to increase the value to > 20 if it still fails.