Netconfig in Cisco Works

Unanswered Question
Dec 19th, 2007
User Badges:

I wondering is someone can help me.

I'm pretty new to using netconfig to schedule config change in Cisco Works.

The problem I am having is that all off the jobs fail.

I ran an adhoc job yesterday to copy the startup config to bootflash:

Netconfig reported this as having failed but when I checked on the device it had actually been done.

I also ran a job over night to change the enable secret password and to set a local username and password on one device and the job failed.

What I can't find is the reason the job failed, does netconfig keep a log of what it has done.

With jobs with multiple config changes in them I can't see which part of the config it couldn't do it just says the job failed.

Any ideas on where to look for logs ?

I'm running Cisco Works version 4.0.5



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)

Ahh welcome to netconfigs' all white or all black world. You'll quickly discover that if a single scheduled action for any device in the job fails , the job itsself is considered failed.

It could be something as simple as sync'ing the archive before the deployment.

I've had jobs run that touched thousands of devices that most would consider successful, but a failure or two on a trivial item that didnt impact the overall functionality cause the whole thing to "fail"

David Stanford Wed, 12/19/2007 - 06:03
User Badges:
  • Cisco Employee,

Have a look at the job logs in under:


This should show the reason for failure. Even if a job pushes its commands it may fail if it can't send an email or something similar.


This Discussion