actyler1001
Enthusiast
Enthusiast

NTP broken after ESXi 7u3 upgrade

NTP time sync appears to have broken after the 7U3 upgrade.  Anyone else run into this and have suggestions on how I might fix?  I've deleted and re-created the service, checked FW policy, tried different servers...  Nothing helps.

Original Build: VMware ESXi, 7.0.2, 17867351

actyler1001_1-1635089620144.png

 

New Build: VMware ESXi, 7.0.3, 18644231

actyler1001_0-1635089532365.png

 

Labels (2)
108 Replies
actyler555
Enthusiast
Enthusiast

I've just deployed Update 3f Build 20036589 into my VMware environment.  This NTP problem appears to be solved.  Wow, that only took VMware 9 months to fix.....

mbuster25
Contributor
Contributor

Yup i upgraded  to 3f too, and no more time sync issues!  Seems to be a silent fix as nothing was mentioned in release notes.

0 Kudos
LabMasterBeta
Enthusiast
Enthusiast

**** My NTP cleanup/fix on vSphere 7.0 Update 3(g) ****

VMware vSphere update: 7.0u3 (aka 7.0.3)
Patched ESXi version: 7.0u3g.
Patched vCenter version: 7.0u3g.

FIRST: Verify Time Zone are same on ESXi and vCenter.. I only point this out because you can now finally change Zone on VCSA admin port 5480..

===============

 

**NTP KB ARTICLE; NOTE! ONLY FOR 7.0-U3+**

https://kb.vmware.com/s/article/87488

[root@localhost:~] vi /scratch/ntpconfig.txt
[root@localhost:~] cat /scratch/ntpconfig.txt

server time.nist.gov
server pool.ntp.org
tos maxdist 30

[root@localhost:~] esxcli system ntp set -f /scratch/ntpconfig.txt
[root@localhost:~] esxcli system ntp set -e 1

 

===============

**NTP KB ARTICLE; NOTE! ONLY FOR 7.0-U3+**

https://kb.vmware.com/s/article/87176

To display current configuration:

# esxcli system ntp get
# esxcli system ptp get

To change configuration:

# esxcli system ntp set
# esxcli system ptp set

To get a list of ALL new 7.0 Update-3 commands, use help:

# esxcli system ntp --help

 

===============

**HELPFUL OLD NTP KB ARTICLE, FOR SYNTAX COMMANDS ONLY**

((This KB specifically states issues after u3 upgrade))

https://kb.vmware.com/s/article/86255

**WARNING!! "RESOLUTION" AT END OF ARTICLE DESTROYS 7.0.3 HOST**
**ONLY USE THE NEW KB ARTICLES ABOVE FOR U3 NTP TEXT FILE METHOD**

  ((VMware should insert a warning about this for Update-3!!))

===============
===============

After KP Articles, vCenter was showing as broken (red alerts).

 

To get vCenter to re-sync NTP based on Host, this worked for me:

**Reset NTP settings on ESXi host, back to defaults:**

[root@localhost:~] esxcli system ntp set -r

 

**Reload NTP service on ESXi host:**

[root@localhost:~] /etc/init.d/ntpd restart

 

**Use vCenter GUI to input NTP addresses into ESXi host again**
((I'm using GUI because I want to see it work as designed...)

**Reset NTP on ESXi host again**

[root@localhost:~] /etc/init.d/ntpd restart

 

**Poll the NTP server on ESXi host a few times, give it a minute:**

[root@localhost:~] ntpq -p

 

**Wait until NTP server on ESXi host shows Time Sync = True:**

[root@localhost:~] esxcli system ntp test

((Diags output omitted..)

Service analysis completed.
Timeinsync: true

 

[root@localhost:~] esxcli system ntp get
Enabled: true
Loglevel: warning
PID: 2126728
Runtime Seconds: 260
Servers: time.nist.gov, pool.ntp.org
Service Providing Kernel Time: Network Time Protocol
Time Service Enabled: true
Time Synchronized: true

 

**Check ESXi host and vCenter GUI's**
((In vCenter > Host > Configure > Time Config > Test Service))
**Finally, for 1st time since 7.0u2, this test passed for me!**

 

Note-1:
This final NTP bug is annoying but not a deal-breaker:
In ESXi host NTP config GUI (not vCenter) version 7.0u3g:
ESXi GUI: Clicking "Actions" is still broken (it does nothing).
ESXi GUI: Clicking "Refresh" finally works again as expected.

 

Note-2:

After all this cleanup work and fiddling with ESXi and vCenter (both version 7.0.3g), finally now, NTP tests pass in both ESXi and vCenter when vCenter is set to ESXI Host for time sync.

I did not try all this with ESXi version 7.0.3f. but if you read 7.0.3f release notes, you'll want to upgrade to patch 7.0.3g immediately...

0 Kudos
Kinnison
Enthusiast
Enthusiast

Hi,


I beg your pardon, could you please explain which of the commands (or resulting condition) given as a solution in KB 86255 article goes so far as to destroy an ESXi host running version 7.0U3 and later. The && is nothing more than a chaining operator, which executes the next command provided the previous one was executed without errors and the commands itself are the same that could be executed one by one.


The import of an empty file will be ignored, and we agree that the imported text file as to contain valid NTP command and option.
Mind you, I'm not here to discuss what your personal experience had been and no offence meant, but to say that using a set of commands from a KB article outright "destroy" an host running ESXi 7.0U3 and above it doesn't seem "a little too strong".


The documented method (in my test cases) worked with ESXi 7.0U3 d/e/f/g (honestly I would have been surprised otherwise).


Regards,
Ferdinando

0 Kudos
CMorrisMCC
Contributor
Contributor

How is this a false alert when I'm suffering issues on three of my hosts using build 19482537? Just saying. 

0 Kudos
Kinnison
Enthusiast
Enthusiast

Hi,


I have no doubt at all that with the version of ESXi you currently use you can have problems with time synchronization, I have had them too and, I presume, many others besides those who have written in this thread.


Explaining in what specific conditions the use of the commands contained in the aforementioned article can result in the destruction of a host running ESXi version 7.0U3 and higher could help anyone who might (have to) use them in the future.


Regards,
Ferdinando

0 Kudos
actyler555
Enthusiast
Enthusiast

Well, we've started our vSphere 7 upgrades in production.  Deployed ESXi, 7.0.3, 20328353 to our first host and guess what?  Yes, the NTP problem persists.  What a joke.  I've opened a support request with VMware, we'll see where this goes.

Support Request #22363318109

actyler555_0-1663272762273.png

 

0 Kudos
jdptechnc
Expert
Expert

Deployed a fresh 7.0.3 Build 20328383 server, and I am seeing this problem as well.

Please consider marking as "helpful", if you find this post useful. Thanks!... IT Guy since 12/2000... Virtual since 10/2006... VCAP-DCA #2222
0 Kudos
actyler555
Enthusiast
Enthusiast

I just got done running the commands that @LabMasterBeta posted above and it did work...

 

for reference...

**Reset NTP settings on ESXi host, back to defaults:**
esxcli system ntp set -r


**Reload NTP service on ESXi host:**
/etc/init.d/ntpd restart


**Use vCenter GUI to input NTP addresses into ESXi host again**
((I'm using GUI because I want to see it work as designed...)

**Reset NTP on ESXi host again**
/etc/init.d/ntpd restart


**Poll the NTP server on ESXi host a few times, give it a minute:**
ntpq -p


**Wait until NTP server on ESXi host shows Time Sync = True:**
esxcli system ntp test

((Diags output omitted..)

Service analysis completed.
Timeinsync: true

 

**Check ESXi host and vCenter GUI's**
((In vCenter > Host > Configure > Time Config > Test Service))
**Finally, for 1st time since 7.0u2, this test passed for me!**

0 Kudos