Config Fetch Fails

Unanswered Question
Aug 20th, 2008

I have been getting the following error when I archive my configs: CM0151 VLAN RUNNING Config fetch failed. The configuraiton file is backed up fine, its just the vlan.dat file that does not work. my transport protocols are Telnet, then TFTP. I am using RME 4.1.1

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
krhashbarger Wed, 08/20/2008 - 08:06

Thats the thing. Those switches do not have a vlan.dat file, because there is no vlans configured on those devices.

stephenscott Fri, 04/10/2009 - 05:56

I am having the same problem...I am running RME 4.2.0.

Is there still a bug?

krhashbarger Fri, 04/10/2009 - 06:02

To fix this you have to copy a vlan.dat file from a switch that has one on the flash. Then TFTP that vlan.dat file to the switches that do not have one. That is what fixed my problem.

krhashbarger Fri, 04/10/2009 - 06:56

Its just mainly tftp a vlan.dat file from another switch, then tftp that file to the switches that do not have one. They do not have a patch out for this yet, so this is a work around.

stephenscott Fri, 04/10/2009 - 07:01

OK, Thanks. I am assuming by your response that ANY vlan.dat file will do? I want to make sure before I do this. I do not want to 'break' anything when I do this. Thanks again.

stephenscott Fri, 04/10/2009 - 11:28

I found another work around. Simply create a VLAN and ust keep it shutdown. I used VLAN 2 and issed the shutdown command, resync'd the archive and voila.

Joe Clarke Fri, 04/10/2009 - 11:33

The patch is certainly available, and has been given out to a number of customers. However, it is now out of date. If you have a newer version of the SharedDcmaCatIOS package, my patch will overwrite it, and could break other things. Therefore, the workaround is recommended now until LMS 3.2 comes out this summer.

pvanvuuren Sat, 04/11/2009 - 01:49

The creation of a vlan and a name worked for me too.

vlan 2

name TEST

and it created a VLAN.dat file in flash.

patrick.peuten_2 Wed, 04/15/2009 - 03:12

I had this problem, too. I had about 250 devices Partially Collected because CW could not download the vlan.dat.

I just started a netconfig job for those devices.

The job ran the following command:

vlan database

vlan 666 name CiscoBug


vlan database

no vlan 666


Works fine for me =). The vlan.dat keeps on flash even if u delete the just created vlan with the "no" command.



This Discussion