%SW_VLAN-4-VTP_INVALID_DATABASE_DATA

[Luke Smith]

I've recently added a new VLAN on many of my switches and I have a small percentage of sites that are reporting this error in the logs.  I've looked around Cisco's site and couldn't find a bug about it and the error message decoder states to delete the VLAN database and reboot the switch.  When I do this the error message goes away but I want to ensure that it doesn't come back again.  Has anyone seen this message before and what did you do get rid of it and ensure it didn't come back?

The full error message is the following:

%SW_VLAN-4-VTP_INVALID_DATABASE_DATA: VLAN manager received bad data of type device state: value 0 from vtp database

    function vtp_get_domain_info

-Traceback= 1865F0 315DBC 31B17C 316134 31D30C CDA83C CDA894 31B984 31B0F0 31799C 3183E8 B81A18 B78DE0

[Jon Marshall]

Luke

It seems a common issue across all switches. There may be a bug fix for it. What switch and IOS are you running ?

The messages seems to be about exiting vlan database mode. Do you add the vlans by going into vlan database mode rather than simply adding the vlan  in global config ?

If so it may be worth changing to creating vlans from global config mode.

Jon

[Luke Smith]

John,

Thanks for your reply.  I looked through the known bugs and couldn't find anything to corrolate it being a bug, I could have not had my search criteria right though ... I am adding the VLANS via the global config and not the VLAN database. The Switch model is the 2960 and the IOS they are running is 12.2(37)EY.

[Jon Marshall]

Luke

I'm not sure it is a bug as such but i thought they may have introduced a solution to the issue. I couldn't find anything to say exactly what causes it unfortunately.

Jon

[Peter Paluch]

Jon, Luke,

As I see this, it might be a software bug - if the 2960 are indeed running the 12.2(37)EY then they are running some rather prehistoric IOS version and should be upgraded ASAP, as the newest one is 15.0(1)SE (I was shocked to see the 15.x designator on the 2960 IOS! ).

But one other thing occured to me: is it, by any means, possible that the FLASH filesystem got full and thus the changes to the VLAN database could not be correctly stored to the vlan.dat, thereby causing the error Luke mentioned?

Best regards,

Peter

[Luke Smith]

Hmm... I never thought to check the flash to see if it was full.  Unfortunately after looking, I have plenty of flash room left. 

I didn't realize they were that far behind on the IOS, I'll have to look into testing out a newer version of IOS to see if how that works in my environment ...

[kapathak]

Hello Luke,

What is the complete image name of the IOS being used?

Regards

Kapil

[Luke Smith]

Kapil,

Here you go, this is the file name ... c2960-lanlitek9-mz.122-37.EY.bin

[kapathak]

Luke,

There are a couple of internal bugs filed to address this issue. Looks like newer IOS's 12.2(46)SE onwards do not see this problem. I can't really share the bug details with you, but you should look into an IOS upgrade on the affected switches.

Cheers!

Kapil