05-15-2008 10:37 AM
How can I get rid of the Partial Successful status on the archive of devices that do not have a VLAN database?
05-15-2008 06:58 PM
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?
05-19-2008 07:21 AM
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.
05-19-2008 08:29 AM
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.
05-19-2008 08:53 AM
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.
05-19-2008 09:00 AM
Make sure SSH is one of the selected protocols for config fetch under RME > Admin > Config Mgmt > Transport Settings.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide