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

NTP health for SDDC Manager is RED when two NTP servers are configured during Bring-up (65002)

Last Updated: 12/18/2018Categories: InformationalTotal Views: 4695Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You see that the NTP health for SDDC Manager is RED when running /opt/vmware/sddc-support/sos --ntp-health.

Two NTP servers were configured during Bring-up.

You see two IP addresses on a single server line in the /etc/ntp.conf file on the SDDC Manager VM, similar to the following:

tinker panic 0
restrict default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
driftfile /var/lib/ntp/drift/ntp.drift
server 10.113.60.176,192.168.16.1

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

You see output similar to the following when running ntpq -pn on the SDDC Manager VM:

No association ID's returned

Resolution

This is a known issue affecting VMware Cloud Foundation 3.x. There is currently no resolution.

Workaround

Use the following steps to workaround this issue:

Log in to the SDDC Manager VM as the vcf user and switch to the root user by issuing the su - commaond.

Issue the following command to make a copy of the /etc/ntp.conf file:

cp /etc/ntp.conf /var/tmp/ntp.conf.bak

Open the /etc/ntp.conf file in a text editor.

Remove the server line with two IP addresses on it.

Create two separate server lines, each with one of the NTP server IP addresses on it.

Save and close the file.

Note: The /etc/ntp.conf file should look similar to the following:

tinker panic 0
restrict default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
driftfile /var/lib/ntp/drift/ntp.drift
server 10.113.60.176
server 192.168.16.1

Issue the following command to restart the ntpd service:

systemctl restart ntpd

Related Information

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Customer Connect へのログインに失敗する (2014050)

KB
•
VIDM 用户无法向 vRealize Log Insight 4.x 进行身份验证 (54995)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 3.5.x

VMware Cloud Foundation 3.0.x

Take Our Survey

Support Assistant