Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VMware Smart Assurance NCM: How to enable debug and session logging on a Device Server? (323701)

Last Updated: 7/28/2021Categories: How toTotal Views: 4671Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

How to turn on verbose logging to troubleshoot a device driver related issue in NCM?

Resolution

Root access to the Combination Server (or) Application server and Device server(s) is needed to edit the necessary files mentioned in the following instructions.

To enable session logging and full debug:
1) Run the following command on NCM Application Server / Combination Server (all on one line):
. /etc/voyence.conf; $VOYENCE_HOME/cgi-bin/cflist.cgi |sed 's/^POP .*/& CM_DEBUGSESSION=1/g' |$VOYENCE_HOME/cgi-bin/cfwrite.cgi

2) Open the logs.cfg file in the Device server(s) / Combination Server:
vi $VOYENCE_HOME/conf/logs.cfg

3) Uncomment the following line in the logs.cfg file:
#*:log(0-9):file(10x1000000)

4) Save and close the logs.cfg file.

5) Restart the voyence service on Device Server(s) / Combination Server as follows:
service voyence restart

To generate log bundle after enabling full debug & session logging:
After executing the device discovery/pull config/push config/OS update etc operation on the device(s) to replicate the issue present, bundle the logs with below commands on Device Server / Combination Server and upload the zip file generated to the VMware Support Request.

source /etc/voyence.conf
$VOYENCE_HOME/tools/saveLogs.pl all --save-rolled-logs

To disable session logging and full debug:
1) Run the following command on NCM Application server / Combination Server (all on one line):
. /etc/voyence.conf; $VOYENCE_HOME/cgi-bin/cflist.cgi |sed 's/CM_DEBUGSESSION=1/CM_DEBUGSESSION=0/g' |$VOYENCE_HOME/cgi-bin/cfwrite.cgi

2) Open the logs.cfg file in the device server(s) / Combination Server:
vi $VOYENCE_HOME/conf/logs.cfg

3) Comment out (#) the following line:
*:log(0-9):file(10x1000000)

4) Save and close the logs.cfg file.

5) Restart the voyence service on device server(s)  Combination Server as follows:
service voyence restart

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
•
ログ ブラウザを使用したトラブルシューティングのためのログの確認、検索およびエクスポート (2032888)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
My Workspace ONE UEM 環境が My Workspace ONE ポータル内の My Company 画面に表示されない (2961175)

Results 1-4 of 4

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