I have setup 15 servers so far and have had no troubles. This one though is giving me fits. When I issue the command "ntpq -c pe" to start the ntp setu process, I get a return of "No Association ID's returned". What is that? The knowledge base shows nothing on it.
Thanks for helping out a newcomer to the community.
Paul
It's case sensitive - esxcfg-firewall --enableService ntpClient
What we have done to configure the NTP setup is just VI the /etc/ntp.conf file and the /etc/ntp/stepticketer and then just restart the ntpd deamon
There is a knowledgebase article that works:
If the link doesn't work - go to vmware\support\knowledgebase and search for article 1339.
I've used the article to setup ntp on multiple systems.
HTH
Mike
Actually, those steps are the ones I have followed, yet I still get that blasted msg. Does anyone have a clue as to what it means?
Paul, The only thing that I can think of there is something in your ntp.conf file.
Here is what I have in my ntp.conf file
restrict kod nomodify notrap noquery nopeer
restrict 127.0.0.1
server 0.north-america.pool.ntp.org
server 1.north-america.pool.ntp.org
server 2.north-america.pool.ntp.org
server 3.north-america.pool.ntp.org
driftfile /var/lib/ntp/drift
and I have the 1st 2 servers in my steptickers file
Hope this helps.
Also do you have the firewall ports open on your esx server.
Thanks. I'll double check my ntp.conf file. Also, the firewall ports are open.
hi,
the ntp.conf file has a section that configures a fake driver.
If you leave that on, you will see the "LOCAL" peer.
When you comment it out, ntpq "peers" will return "No association ID's returned".
hope that helps,
Reinhard.
restrict default kod nomodify notrap
server 10.1x1.1.xx
server 10.1x1.1.xx
server 10.1x1.1.xx
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
That is the ntp.conf file we use and has worked just fine till this install. Any more ideas?
Did you opened the firewall port 123/NTP?
Yes, it is open.
Can you add "restrict 127.0.0.1" and try again?
pdowning,
You need a "restrict 127.0.0.1" entry in your configuration. As KB
Article 1339 explains, this allows you to contact the local DNS
resolver in the Service Console. Without it, none of your the NTP
servers get added. With no NTP servers, you have no associations:
that's what the NTP tools are trying to tell you.
Joe
I'll give that a shot and see what happens. Thanks guys.
I added the restrict 127 line. Now I get this error:
(1654) ERROR: Unknown service 'ntpclient'
when I type : esxcfg-firewall --enableService ntpclient
This is frustrating .....
It's case sensitive - esxcfg-firewall --enableService ntpClient
Duh .. thanks. I apparently can't read my own typing
Thanks fellas. This has been one of the most helpful support forums I've run across. I'll return to stump you again, I'm sure.