Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Unable to Configure NTP in vCenter Server Appliance 6.7 VAMI (59729)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 45075Language:
Chinese (Simplified)JapaneseEnglish

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Symptoms

In the vCenter Server Appliance Virtual Appliance Management Interface (VAMI), you cannot configure an NTP server unless the NTP server replies to ICMP traffic (ping).

The "Edit Time Synchronization Settings" wizard displays, "<SERVER>, and <SERVER> are unreachable"

If trying to configure "time.windows.com" and "time.nist.gov" as NTP servers, the applmgmt.log reports messages similar to:

/var/log/vmware/applmgmt/applmgmt.log

2018-11-07T00:03:08.843 [3001]DEBUG:vmware.appliance.timesync.impl:com.vmware.appliance.ntp.test(['time.windows.com', 'time.nist.gov'])
2018-11-07T00:03:08.843 [3001]DEBUG:vmware.appliance.networking.testUtils:Testing connection to: ['time.windows.com', 'time.nist.gov']
2018-11-07T00:03:10.993 [3001]DEBUG:vmware.appliance.networking.testUtils:ping out: b'PING time.microsoft.akadns.net (51.141.32.51) 56(84) bytes of data.\n\n--- time.microsoft.akadns.net ping statistics ---\n10 packets transmitted, 0 received, 100% packet loss, time 1871ms\n\n', err: b'', returncode: 1
2018-11-07T00:03:11.100 [3001]DEBUG:vmware.appliance.networking.testUtils:ping out: b'PING ntp1.glb.nist.gov (129.6.15.28) 56(84) bytes of data.\n\n--- ntp1.glb.nist.gov ping statistics ---\n10 packets transmitted, 0 received, 100% packet loss, time 1872ms\n\n', err: b'', returncode: 1
2018-11-07T00:03:11.101 [3001]DEBUG:root:TestRunStatuses: servers=['time.windows.com', 'time.nist.gov']
statuses=['SERVER_UNREACHABLE', 'SERVER_UNREACHABLE']
messages=[Structure('LocalizableMessage', dict(defaultMessage='Failed to reach server.', id='com.vmware.appliance.ping.failure', args=[])), Structure('LocalizableMessage', dict(defaultMessage='Failed to reach server.', id='com.vmware.appliance.ping.failure', args=[]))]

Cause

The vCenter Server Appliance 6.7 GA and 6.7 U1 use ICMP to validate the NTP servers that have been configured.

Resolution

This issue is resolved in VMware vCenter Server 6.7 Update 2, available at VMware Downloads.

Workaround

If your desired NTP servers do not respond to ICMP / ping, you can configure this using the command line.

Log into the Appliance Shell as root

Run the following command to set the desired NTP servers

com.vmware.appliance.ntp.set --servers SERVER1,SERVER2

Run the following command to validate these NTP servers

com.vmware.appliance.ntp.get

To validate NTP is running and view the offset/jitter, start by switching to the bash shell

shell

Start NTP

service ntpd start

Query NTP

ntpq -p

Optionally, configure NTP to start automatically upon boot

systemctl enable ntpd.service

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant