Solved

NetConfig jobs failing on network devices

Posted on 2008-06-17
2
3,342 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

What Is Transaction Monitoring and who needs it?

Synthetic Transaction Monitoring that you need for the day to day, which ensures your business website keeps running optimally, and that there is no downtime to impact your customer experience.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We all know how boring and exhausting it is to transfer huge web projects developed locally to a webserver simply via FTP. The File Transfer Protocol is a really nice solution if you need to transfer small amounts of files, but if you're plannin…
Secure Shell (SSH) is a network protocol for secure data communication, mainly used to administer remote Unix / Linux servers via command line. But it also allows the user to open a secure tunnel between a client and a server where he can send any k…
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…

724 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