• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3448
  • Last Modified:

NetConfig jobs failing on network devices

I am using Cisco Works Version 4.0.5. I used NetConfig jobs to run automatic jobs on Cisco Switches and other devices on my network. I get about a 50% failure rate on every job. 150 devices take the job and 150 devices fail. I get the error: "ERROR:RME_CDL1031:Transport session to device failed TFTP: Failed on the device. SSH: Failed to establish SSH connection to x.x.x.x - Cause: Authentication failed on device 3 times." But I can SSH or telnet to these devices outside of Cisco Works. Does anyone have any idea how to fix this? Thanks.  
0
Majestica
Asked:
Majestica
1 Solution
 
Kamran ArshadIT AssociateCommented:
0
 
thomaschalmersCommented:
I had the exact same problem as you and I read the article above but the solutions offered were of no use to me. In particular i was following the section that read:

"NetConfig Job Failed Because of Telnet Timeout"
NetConfig jobs can sometimes timeout and the configuration changes fail, especially if the devices are over WAN links, or if you schedule configuration changes for multiple devices.

You can modify TelnetTimeout values (the default is 60 seconds) and increase them accordingly in TransportIos.ini and/or TransportCat.ini. The default location is:

From UNIX
/opt/CSCOpx/objects/cmf/data/TransportIos.ini
/opt/CSCOpx/objects/cmf/data/TransportCat.ini

From Windows NT or Windows2000
NMSROOT\objects\cmf\data\TransportIos.ini
NMSROOT\objects\cmf\data\TransportCat.ini


As our Ciscoworks box is actually running Windows Server 2003 (x64 edition) I couldnot find the Transport.ini or transportcat.ini files. However, the articles did alert me to the fact that I might need to find another way of increasing the telnet timeout time.

As such I went into Ciscoworks RME under the heading of administration. In this section I navigated to RME Device Attributes - in here are telnettimeout settings and tftp timeout settings. I changed my settings from:

Telnettimeout 36seconds
TFTP timeout 5 seconds

to

Telnet timeout 60 seconds
TFTP timeout 30 seconds


After applying these settings I ran netconfig again on a small LAN at our work (40 devices) and it ran successfully.

I hope this helps you too!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now