Generate session trace logs for NCM and NPM modules

This article provides information and steps on how to enable/disable the Session Tracing feature in NCM and NPM CLI polling. A session trace is a plain text file that contains all communication sent to and received from the network device NCM or NPM is trying to connect to. These files are generated on the Polling Engine, which is currently managing the device. It is important while troubleshooting NCM configuration downloads or script execution issues, and NPM CLI polling. The session trace contains any commands or messages sent, including errors the device has responded with.

To enable Session Tracing:

On each Polling Engine:

1. Go to the trace files log location:
   1. For NPM: C:\ProgramData\SolarWinds\Logs\Orion\CLI\Session-Trace
   2. For NCM: C:\ProgramData\SolarWinds\Logs\Orion\CLI\Session-Trace\NCM
2. Delete the trace files.
3. Open the Orion Web Console.
4. Go to Settings > All Settings > CLI Settings
5. Select the Enable Session Tracing check box and Submit.
6. Reproduce the issue for a single device.
7. Collect the latest session trace logs for the specific node (files created with the IP address of the node in the filename) found in:
   1. For NPM: C:\ProgramData\SolarWinds\Logs\Orion\CLI\Session-Trace
   2. For NCM: C:\ProgramData\SolarWinds\Logs\Orion\CLI\Session-Trace\NCM

To disable Session Tracing:

1. Open the Orion Web Console.
2. Go to Settings > All Settings > CLI Settings
3. Clear the Enable Session Tracing check box.
4. Go to the trace log location on each Polling Engine:
   1. For NPM: C:\ProgramData\SolarWinds\Logs\Orion\CLI\Session-Trace
   2. For NCM: C:\ProgramData\SolarWinds\Logs\Orion\CLI\Session-Trace\NCM
5. Delete the trace files.

Notes:

• Disable Session Tracing and delete traces when not in use to avoid creating unnecessary log files and overloading the Polling Engine.

• Zip the Session Trace log files when sending them to the Technical Support team for review.

Related articles:

• NCM How to Read a Session Trace