Config Archival: Failed and Partially Successful Device

Unanswered Question
Mar 5th, 2009

Hi Experts,

I have two problems in archiving the devices.

1. Failed to establish TELNET connection to -Cause: Authentication failed on device 3 times Failed to detect SSH version running on the device.

(I am able to telnet to the device manually. Telnet and enable passwords are double verified and confirmed to be correct.)

2.Command failedFailed to detect SSH version running on the device. VLAN Config fetch is not supported using TFTP. (Both running and startup config are successful but VLAN config is failed. Config archival is successful on the same model of switch -- 3548XL.)

I am wondering why are these two switches failed. Please advice.

Thanks and Regards,


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (3 ratings)
Joe Clarke Thu, 03/05/2009 - 00:17

The first error is almost always correct. I know you've verified the credentials, but since you're using telnet, you should start a sniffer trace filtering on TCP port 23 traffic to this device, then perform another Sync Archive. When it fails, check the sniffer trace to see what credentials RME is using, and where the fetch fails.

The second problem indicates an issue being able to either login to this switch using telnet or SSH, or more likely, the TFTP is not allowed between device and server. In order for the vlan.dat config to be fetched, RME will login to the device using either telnet or SSH, then perform a "copy flash:vlan.dat tftp:" to transfer the file back to the RME server. If the network does not allow udp/69 and ephemeral UDP ports between the device and server, then you will see this error.

jeeyishyuan Thu, 03/05/2009 - 01:32

Hi joe,

Thanks for the reply but how could I check if the Port 69 is enable in between device and LMS? I thought I read that VLAN.dat is not supported by TFTP?

"Command failedFailed to detect SSH version running on the device. VLAN Config fetch is not supported using TFTP."

jeeyishyuan Thu, 03/05/2009 - 01:42

Hi Joe,

I have captured the telnet packets that I sniffed when I rerun the config archival for Possible for you to advise based on the text file? Thanks!



Joe Clarke Thu, 03/05/2009 - 09:28

RME sends:


The device replies with the password prompt again indicating that this password is incorrect.

Joe Clarke Thu, 03/05/2009 - 09:30

You could try to manually TFTP the vlan.dat file from the switch to the RME server. Create an empty vlan.dat in the NMSROOT\tftpboot on the RME server. Then, attempt to copy the vlan.dat from the switch to the server. I'm betting this times out.

When RME says that the vlan.dat fetch is not supported with TFTP it means it is not supported with SNMP-triggered TFTP. The vlan.dat is, in fact, transferred using TFTP, just not the same way as the running and startup configs.

jeeyishyuan Fri, 03/06/2009 - 00:12

Hi Joe,

Something that I don't understand is I am able to TFTP manually. The Vlan.dat file is actually successfully fetch from the switch using a third party TFTP server.

Aft I have tried to TFTP manually, the fetching of vlan.dat using Config Archival is successful instead. Just wondering why is it so?



Joe Clarke Fri, 03/06/2009 - 08:18

Run another sniffer trace filtering on all traffic to this switch. Perform a new Sync Archive job. When the vlan.dat fetch fails, the sniffer trace should show you why.

axa-wongjeff Mon, 03/16/2009 - 13:21

What is your login prompt? Is it the standard "Username:" prompt or is it custom?

If it's custom, then Ciscoworks has a problem with it.


This Discussion