I participated in the vSphere 6.0 beta program and played with it in a couple test and development environments but haven’t had it in a clustered environment yet. Today, I installed the Dell customized image (VMware-VMvisor-Installer-6.0.0-2494585.x86_64-Dell_Customized-A00) on an M520 blade in a Dell VRTX chassis. The M520 is equipped with two Intel Xeon E5-2430’s and 64GB of RAM. There are two of these M520 blades in the chassis as well as an M620 blade with two Intel Xeon E5-2680’s and 256GB of RAM installed.
Getting ESXi 6.0 on the two M520’s is the first step to setting up this 6.0 cluster, as some crafty migration will need to be used since the VRTX is using the shared PERC 8 and there’s a couple VMs that need to remain up. Part of that migration will involve moving some VMs over to the production clusters we have and flashing the PERC firmware to the latest in order to support write-back cache… but that’s another story.
As usual, one of the first things I configure on a host is the NTP settings. I usually just enable NTP to start and stop with the host and set the NTP server to pool.ntp.org – pretty simple. However, that didn’t go as well as I had expected.
Here you can see the ordinary NTP settings:
So, nothing special there by any means, but it seems vSphere has an issue with it:
Pretty disappointing. Just to confirm my sanity I tried again. Same effect. I wanted to try to set the NTP settings up through the vSphere Web Client but of course I can’t do that as I intend to build the vCenter Server 6.0 setup within this cluster and I am not there yet. So, yeah, not very confidence inspiring. Thinking that it may just be the vSphere client (C#) acting up I checked /etc/ntp.conf:
And that’s looking pretty empty. Disappointing VMware! So, for some reason, the vSphere C# client does not properly allow you to set up NTP settings as it does not seem to write your NTP server to the configuration file. I didn’t go much further with it – I am sure if I add the NTP server in the ntp.conf file manually it’ll work, but that’s lame. I am also certain I didn’t have this issue in the beta program when I was running the vSphere Web Client – so, I’ll wait to setup NTP when I have vCenter setup and configured. Odd, though. I know ESXi 6.0 went GA very recently, but c’mon, this is basic and should have been tested. Not only that, but if you’re setting up ESXi 6.0 on a new host you’re obviously going to probably connect and configure it with the vSphere client. Oh well…