|
gradgrind
6 posts
 |
On a 6500 with sup720 with IOS 12.2+ we are deciding he best way to have a spare cold sup. With just the config -or- also to include the vlan.dat. Common thinking was with just the config the vlan.dat should auto populate as the switch comes up reading the vlan info in the config and the int vlan (since we don't have to use the vlan database commands to make them state active,etc anymore), however we are not seeing this to be the case. I was wondering if others have had similar experiences. We have found that if you do a copy start run, then they will start to come up. And yes the running config has the vlan info in them the first time. Its like the config isn't being read fully the first time it starts up. Thoughts ? |
|
WannabeCCIE
1 post
|
I replied on Twitter as well but I prefer to run my switches in transparent VTP mode and not care about the vlan.dat file. |
|
stretch
258 posts
 |
Sure, but I think he means the VLANs aren't being automatically populated from the config. |
|
Phil
4 posts
|
I experienced this behaviour, too. We placed an updated startup-config with a new vlan-interface (and the command to create the vlan) on a router on the customers site. The router was reloaded but the interface didnt come up. After connecting to the cli via console and creating the vlan again manually, the interface came up. It seams that it's not possible to create vlans via startup-config. You have to execute these commands on the running system. So, you should backup your vlan.dat on the spare sup. Other question: Why dont you just put the memory card (with up to date config and vlan.dat) from the running sup into the spare sup when it comes to the exchange? |
Viewing 1 - 4 of 4
- 1