Solved

NetConfig jobs failing on network devices

Posted on 2008-06-17
2
3,272 Views
Last Modified: 2008-11-11
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
Comment
Question by:Majestica
2 Comments
 
LVL 32

Expert Comment

by:Kamran Arshad
ID: 21801506
0
 
LVL 1

Accepted Solution

by:
thomaschalmers earned 125 total points
ID: 21931752
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

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Join & Write a Comment

Network ports are the threads that hold network communication together. They are an essential part of networking that can be easily ignore or misunderstood, my goals is to show those who don't have a strong network foundation how network ports opera…
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now