cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
898
Views
0
Helpful
1
Replies

Vlan configuration incomplete or missing on reload after new Config Copy (TFTP or USB) on cat2960X

During prepartions for a big rollout of 2960x and configuration copys and softwaredeployment on 2960X (200+ Switches) we are experiencing the behaviour which is explained in Bug ID CSCup52223 (https://tinyurl.com/hl46wqd) 

After the config.txt copy to the startup-config  (via TFTP or USB) all or most of the Vlans disappear after reload. They are still seen in the Startup Config however the Vlan.dat is not probably created.  

There are two explained workarounds in the bug, one is issueing a write memory before reloading the Switch. The other is modifying the VTP Domain before the config file copy to startup-Config.

Rollouts of this size require smallest possible config overhead per Switch. So it would be great if we found a solution that requires no Console access before or after the config is copied as used to with every other Switchplatform we have been working with like cat2960, cat2960s, cat3560 and cat3650.  

Can anyone think of a solution for this? 

tested IOS Releases:
15.2.2.E3
15.2.2.E4
15.2.2.E6
15.2.5.E1

1 Reply 1

Seems there is a solution provided on the Cisco Bug Search Page:

"

At this point the switch will in same state as it is out of box. Now I tried the following sequence.
Configure VTP domain. ---> this will create the vlan.dat
Configure VTP mode to transperant ---> it will be preserved in the vlan.dat, and mode is preserved between reloads.
Copy tftp: startup_config
Reload -------> this sequence does not require double reload.

"

AND:

it seems there are other Platforms effected: Cat2960S.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card