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

Smarts NCM: How to change timeout value of health check (329812)

Last Updated: 5/29/2020Categories: TroubleshootingTotal Views: 11464Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

To adjust the timeout value used for Smarts NCM health check
This article explains how to increase or decrease the timeout value used by Smarts NCM for Health checks.

Errors similar to the following may be seen in the Smarts NCM Healthcheck.log file indicating a timeout has occurred:

ERROR: Task 0113675027710000 failed to complete on device server <DEVICE_SERVER_IP> (<DEVICE_SERVER_IP>) within the 300 second threshold

Cause

This timeout may be occurring because of a problem with the Smarts NCM device server in the environment or because of network latency that is normal for the environment.

Resolution

If you encounter this issue, do the following:

Determine the cause of the timeout and do either of the following:

If the timeout is caused by a problem with the Smarts NCM Device Server, investigate and resolve that issue.

If the timeout issue is caused by normal network latency, you can adjust/increase the Health Check timeout value as specified in the following steps.

For Linux environments, execute the following command to set the voyence.conf file as source (this step is not necessary in Windows Server environments):

source /etc/voyence.conf

Change (cd) to the Smarts NCM/Voyence Healthcheck directory:

Linux:
cd $NCM INSTALL DIR/Healthcheck

Windows

cd $NCM INSTALL DIR\Healthcheck

Open the healthcheck.conf file for editing.

Find the line for THRESHOLD='300' (300 is the default configured value).

Change/increase the value to the desired timeout value in seconds.

The default threshold of 300 seconds equals 5 mintues.

Save and close the healthcheck.conf file.

Restart services on the Smarts NCM Application Server to apply the new threshold setting in the active environment.

Related Information

If you are looking for how to enable the health check please see article: 167065: Smarts NCM: How to enable Health Check monitoring.

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant