Enable debug and session logging on a Device Server

Products

• VMware Smart Assurance

Issue/Introduction

How to turn on verbose logging to troubleshoot a device driver related issue in Network Configuration manager (NCM)?

Environment

Network Configuration manager (NCM) 10.1.x

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 by removing the "#" character:

#*: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/^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) Comment the following line in the logs.cfg file using the "#" character:

*: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