NTP server not being set when updating node profile

Products

• VMware NSX

Issue/Introduction

• You configure or update NTP settings using the Node Profile in the NSX UI (System > Profiles > Node Profiles), but the NTP is not being saved.
• Using the NSXCLI command get ntp on Managers and Edges, you see no NTP servers applied.
• The node profile is enabled on the nodes:

  get node central-config
  Status: enabled

• Log lines similar to the below are encountered on the NSX Manager in /var/log/proton/nsxapi.log. You see an update to the central config profile (node profile), but the NTP configuration field is empty:

  INFO ThreadPoolTaskExecutor-1 CentralConfigConverterUtils ####### - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] getJsonStr returned with {"timezone":"#######/######","ntp":{"servers":[]},"syslog":{"exporters":[{"exporter_name":"#######-###-#####-","server":"##.###.##.##","port":514,"protocol":"##","level":"DEBUG"}]},"snmp":{"communities":[],"v2_targets":[],"v3_users":[],"v3_targets":[]}}

  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX 4.2.3.3

Resolution

This is a condition that may occur in a VMware NSX environment.

To resolve this, the NTP configuration must be applied directly via the NSX API:

1. Retrieve Current Configuration:
   Perform a GET call to retrieve the existing profile details:
   GET https://<nsx-mgr-ip>/api/v1/configs/central-config/node-config-profiles/00000000-0000-0000-0000-000000000001

2. Apply NTP Configuration via PUT:
   Use the output from the GET call as the body for a PUT request, ensuring the ntp section includes your server(s).
   PUT https://<nsx-mgr-ip>/api/v1/configs/central-config/node-config-profiles/00000000-0000-0000-0000-000000000001

3. Verify the NTP configuration has been applied:
   Check the NSX UI to confirm the NTP servers are now visible in the Node Profile.
   Alternatively, perform another GET call to verify the ntp servers field is populated.
   Or verify from NSXCLI with get ntp.

Additional Information

NSX-T API usage