Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

%NETSTACK-3-OTV_SDBREAD: Error reading vlan database

Hi All,

Anybody have an idea what this error means? I don't even have OTV running in this VDC (I do in another VDC).

%NETSTACK-3-OTV_SDBREAD: Error reading vlan database

I don't have any issues, all vlans are fine and working as expected, but this error is filling up my logs.

fyi, this is a vPC setup and the second N7K doesn't generate this error, only the first.

Nexus 7010 with 2x SUP2 and 1x F2e card in the affected VDC.

Appreciate the help.

Everyone's tags (4)
3 REPLIES
Cisco Employee

%NETSTACK-3-OTV_SDBREAD: Error reading vlan database

Hello,

Check whether the vlan.dat file still exist in the bootflash directory.

#dir bootflash:

         46    Dec 30 11:51:15 2010  ..tmp-kickstart

         36    Dec 30 11:51:15 2010  ..tmp-system

   25164288    Dec 30 11:51:15 2010  .tmp-kickstart

  156932426    Dec 30 11:51:15 2010  .tmp-system

       3626    Dec 30 12:01:28 2010  assoc_ascii_cnv.log

      49152    Dec 30 11:51:15 2010  lost+found/

       2327    Jan 07 13:35:44 2011  mts.log

       4096    Jan 01 11:02:51 2005  vdc_2/

       4096    Jan 01 11:02:51 2005  vdc_3/

       4096    Jan 01 11:02:51 2005  vdc_4/

       472    Jan 07 13:36:13 2011  vlan.dat

If doesn't exist, make a backup of all vlans in your running-config to add again after reboot the switch.

New Member

Re: %NETSTACK-3-OTV_SDBREAD: Error reading vlan database

Hi Richard,

I don't seem to have a vlan.dat on any of my N7K switches.... or N5K switches for that matter....

However, I get this error on just one N7K so I don't think it's related to that.

Do I need to have a vlan.dat btw? I don't use VTP.

%NETSTACK-3-OTV_SDBREAD: Error reading vlan database

Hi EDC,

Have you fix this trouble?

I have the same issue on 6.0.4 software.

It is solved when I temporarily enable feature otv in core vdc.

But its not a better way.

575
Views
0
Helpful
3
Replies
CreatePlease to create content