Joe Clarke Thu, 05/15/2008 - 18:58

If the vlan.dat doesn't actually exist, it should be skipped, and an error should not get registered. What devices (type and software version) are throwing this error?

csco10000174 Mon, 05/19/2008 - 07:21

For example, I have a 3825 running 12.3(14)T with no VLAN.DAT file in it's file system. It succeeds on the Running and Startup but fails on the VLAN. Generating a Partial Successful operation and the following:

VLAN Config fetch is not supported using TFTP. Command failedTELNET: Failed to establish TELNET connection to 10.x.x.x - Cause: connect timed out. VLAN Config fetch is not supported using RCP. VLAN Config fetch is not supported using SCP.

Joe Clarke Mon, 05/19/2008 - 08:29

This is a different failure. RME requires the device be accessible via telnet or SSH to be able to fetch the vlan.dat. If those protocols are not available, then RME has no way to determine if the vlan.dat exists or not. Therefore, it throws an error. If, however, RME is able to login to the device successfully, it can determine if the vlan.dat really exists.

csco10000174 Mon, 05/19/2008 - 08:53

We don't use Telnet in my company, but SSH is open. I have been able to SSH from our CW box to the hosts just fine using the credentials so I know that is functional.

Joe Clarke Mon, 05/19/2008 - 09:00

Make sure SSH is one of the selected protocols for config fetch under RME > Admin > Config Mgmt > Transport Settings.


This Discussion