Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

How to debug hung config change template jobs.

Using the NCM web interface i've created some config change templates to run on some 3com 4400 switches.

These Jobs hang at the execution phase and never time out or fail. I left one job running over 7 days before canceling it. I've enabled session tracing and there is no logs created as a result of these jobs. Its as if it never gets to the point.

What else can I look at to try and determine what is causing the issue?

Find more posts tagged with

Accepted answers

All comments

rschroeder

Sean,

I had some similar troubles when I first started using NCM. I found a variety of issues and fixes.

* First off, reboot the NCM server to clear anything that's hung, then try again.

* If you have session tracking enabled, there are two files that should be created or updated, and they're supposed to have the info you need to troubleshoot it. One will be named after the ip address of the device you're trying to backup, followed with "-trace.txt" (e.g.: 192.168.0.1-trace.txt). The other file is called SWTelnetDebug.txt. These files are found in the Session-Trace folder. If there's any question, I deleted everything in this folder and ran the config download manually again, and then I found the traces, and shared them with Tech Support in a new case.

* One issue was associated with the tftp server, and I found I occasionally had to kill the service before NCM worked OK. This was eventually fixed by upgrading to the current version, and it normally only impacted systems when I had tftp selected as the preferred download method for any device--even if it was just for one device. Disabling tftp and moving to ssh or telnet was another work around, until the new version came out.

Other NCM users may have similar stories, but you're at the point where you should open a ticket with Support.

Best of luck!

Rick