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

Using the lw-measure tool to detect latency between vCenter Server and Active Directory domain controllers (79317)

Last Updated: 4/20/2022Categories: How toTotal Views: 10343Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Slow or failed authentication due to vCenter/domain controller latency.

Purpose

This article shows how to use the lw-measure tool to detect latency between vCenter Server and Active Directory Domain controllers.

Resolution

Using the lw-measure tool

This tool should be run from a PSC or embedded vCenter Server. It will determine the network latency while connecting to the Domain Controllers in a domain as well as the time taken for user lookups of that domain.

For vCenter Server 7.0 and above, skip to step 5 as lw-measure is included in /opt/likewise/bin/lw-measure.

Download the lw_measure binary attached to this article.

From an SSH session to the vCenter Appliance, create a new directory for the tool

mkdir -p /root/debugging
cd /root/debugging

Move the lw_measure file to the /root/debugging directory

Make the file executable

chmod +x /root/debugging/lw-measure

Run lw-measure for 600 seconds (10 mins) from the directory its located in (/opt/likewise/bin/ in 7.0)

nohup ./lw-measure <Domain Name> <AD user UPN> <Time in Seconds> 2>&1 &

Example: nohup ./lw-measure vmware.com [email-masked] 600 2>&1 &

Use ctrl-c to return to the shell. This does not terminate the process, which will continue for the number of seconds specified in the command.

The output is saved to a file in the current working directory named nohup.out

The output will look like this:
Passed Parameters: likewise-ad2016.com, [email-masked], 600
Time(usec) | DC_Index | DC_Name | DC_Address | User_Sid | User_Info | GetUserSid_Error | GetUserInfo_Error | Call_Time_GetUserSid(usec) | Call_Time_GetUserInfo(usec)

Found DC at: 1571752678537100 | Domain: likewise-ad2016.com | Number of DCs: 2
1571752685655671 | 0 | WIN-9J28NIP66PV.likewise-ad2016.com | 10.108.124.22 | S-1-5-21-2993094862-2338724178-3221774877-500 | CN=Administrator,CN=Users,DC=likewise-ad2016,DC=com | 0 | 0 | 5607301 | 1511252
1571752692701943 | 1 | WIN-TBOQKG6ALDO.likewise-ad2016.com | 10.108.124.21 | S-1-5-21-2993094862-2338724178-3221774877-500 | CN=Administrator,CN=Users,DC=likewise-ad2016,DC=com | 0 | 0 | 5557150 | 1488192
Found DC at: 1571752693914490 | Domain: likewise-ad2016.com | Number of DCs: 2
1571752700338333 | 0 | WIN-TBOQKG6ALDO.likewise-ad2016.com | 10.108.124.21 | S-1-5-21-2993094862-2338724178-3221774877-500 | CN=Administrator,CN=Users,DC=likewise-ad2016,DC=com | 0 | 0 | 4932434 | 1491279
1571752706762249 | 1 | WIN-9J28NIP66PV.likewise-ad2016.com | 10.108.124.22 | S-1-5-21-2993094862-2338724178-3221774877-500 | CN=Administrator,CN=Users,DC=likewise-ad2016,DC=com | 0 | 0 | 4933276 | 1489925

Observe the output. If either of the last two columns has latencies more than 5,000,000 usec (5 seconds), it indicates a significant delay in the communication between vCenter and the domain controller. Even authentications with latencies below 5 seconds can cause problems if there are too many of them for likewise to keep up with.

Caution: Using an incorrect value for the domain name can leave a stale process of lw_measure after it is exited. See the example for the proper format. Use ps auxxx| grep lw-measure to find and kill these processes if they exist.

Related Information

For information on using checkADConfig to detect connectivity and DNS issues between vCenter Server and Active Directory, see https://kb.vmware.com/s/article/79323

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

lw-measure

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:

VMware vCenter Server

Related Versions:

Take Our Survey

Support Assistant