cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
946
Views
0
Helpful
1
Replies
Highlighted
Beginner

Comparing vlan.dat and interface vlans

I have a customer whose 6500's reboot sometimes. When they do, they create interface vlans 1-700 even though most of them should exist.  I was wondering if this is possible:

1.  Monitor for a "software forced reboot" in syslog (I got this part)

2.  Action to compare the interface vlans in a show ip interface brief to the vlan.dat file

3.  Action to delete the interface vlans where they don't appear in the vlan.dat file

It isn't a really big deal for this customer.  However, they do currently have to manually remove all of the erroneously created interface vlans.  The ones that shouldn't exist are all in a "down/down" state. So, I know they don't exist in the vlan.dat file.  This problem also causes a significant spike in their syslog server and monitoring software because it begins monitoring all these interface vlans.

Whatever help you can provide, if this is even possible, i'd appreciate it.

Brent

Everyone's tags (3)
1 REPLY 1
Hall of Fame Cisco Employee

Comparing vlan.dat and interface vlans

The vlan.dat is opaque binary data.  You cannot inspect it.  You can, however, remove VLANs based on their state.  I just don't have a clear enough picture of what they're doing manually to clean up these switches.  Can you provide the manual steps?

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards