cisco switches: new config with vlan defintion is not applied to startup-config for some reason
Hi list
During a future migration I will migrate the configuration of around onehundert already existing switches. Because I am lazy as many it guys I prepared the configs which I want to apply to the switches in order to safe time. Many things change from the previous config to the future one: lacp uplinks, vlan defintions, management vlan and so on.
So during the miration I want to do something like this:
copy tftp://10.6.100.3/config.txt startup-config and do a reload or configure replace tftp://10.6.100.3/config.txt
I tested my miration path in the lab and I figured out that low numbering vlans in the range of 2-1001 are for some strange reason not applied to the config. I tried also deleting vlan.dat and change to vtp of or transparent/server/client and diffrent vtp versions before applying the config without success.
Does somebody have a clou about the strange behaviour?
I use iso version 15.0(2)SE on a 2960S
Cheers
Luke
Hi
Regarding to the cisco docu (1) it depends on the vtp mode and the config of vlan.dat.
If both the VLAN database and the configuration file show the VTP mode as transparent and the VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in the startup configuration file are used. The VLAN database revision number remains unchanged in the VLAN database.
If there is no vlan.dat file, or if the vlan.dat cannot be read, the switch boots with the default vlan characteristics. You can use the archiv commands to safe and restore the vlan.dat file.
Regards Erich
[1] http://www.cisco.com/en/US/products/hw/switches/ps5213/products_tech_note091...
Am Wed Jul 24 14:35:15 2013 schrieb Lukas Eisenberger:
So during the miration I want to do something like this:
copy tftp://10.6.100.3/config.txt http://10.6.100.3/config.txt startup-config and do a reload or configure replace tftp://10.6.100.3/config.txt http://10.6.100.3/config.txt
I tested my miration path in the lab and I figured out that low numbering vlans in the range of 2-1001 are for some strange reason not applied to the config. I tried also deleting vlan.dat and change to vtp of or transparent/server/client and diffrent vtp versions before applying the config without success.
Does somebody have a clou about the strange behaviour?
Hi Erich
Thank you for your answer. I also saw this in the documentation. But the switch behaves differently. If I have a switch with already configured vlans with vtp mode transparent (with the same infos in vlan.dat ) then only the higher numbered vlans are going to be applied from the startup config. The lower numbered vlans are copied from vlan.dat to the configuration.
Regards
Luke
2013/7/24 Erich Hohermuth erich@hoh.ch
Hi
Regarding to the cisco docu (1) it depends on the vtp mode and the config of vlan.dat.
If both the VLAN database and the configuration file show the VTP mode as transparent and the VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in the startup configuration file are used. The VLAN database revision number remains unchanged in the VLAN database.
If there is no vlan.dat file, or if the vlan.dat cannot be read, the switch boots with the default vlan characteristics. You can use the archiv commands to safe and restore the vlan.dat file.
Regards Erich
[1]
http://www.cisco.com/en/US/products/hw/switches/ps5213/products_tech_note091...
Am Wed Jul 24 14:35:15 2013 schrieb Lukas Eisenberger:
So during the miration I want to do something like this:
copy tftp://10.6.100.3/config.txt http://10.6.100.3/config.txt startup-config and do a reload or configure replace tftp://10.6.100.3/config.txt http://10.6.100.3/config.txt
I tested my miration path in the lab and I figured out that low numbering vlans in the range of 2-1001 are for some strange reason not applied to the config. I tried also deleting vlan.dat and change to vtp of or transparent/server/client and diffrent vtp versions before applying the config without success.
Does somebody have a clou about the strange behaviour?
Hi Luke
I have the same problem with Cisco Series 800 Router. And so far I've solved it by adding a few lines to the startup-config. For every VLAN: vlan xxx state active
Regards Florian
Am 25.07.2013 16:07, schrieb Lukas Eisenberger:
Hi Erich
Thank you for your answer. I also saw this in the documentation. But the switch behaves differently. If I have a switch with already configured vlans with vtp mode transparent (with the same infos in vlan.dat ) then only the higher numbered vlans are going to be applied from the startup config. The lower numbered vlans are copied from vlan.dat to the configuration.
Regards
Luke
2013/7/24 Erich Hohermuth <erich@hoh.ch mailto:erich@hoh.ch>
Hi Regarding to the cisco docu (1) it depends on the vtp mode and the config of vlan.dat. If both the VLAN database and the configuration file show the VTP mode as transparent and the VTP domain names match, the VLAN database is ignored. The VTP and VLAN configurations in the startup configuration file are used. The VLAN database revision number remains unchanged in the VLAN database. If there is no vlan.dat file, or if the vlan.dat cannot be read, the switch boots with the default vlan characteristics. You can use the archiv commands to safe and restore the vlan.dat file. Regards Erich [1] http://www.cisco.com/en/US/products/hw/switches/ps5213/products_tech_note09186a0080a49dbf.shtml Am Wed Jul 24 14:35:15 2013 schrieb Lukas Eisenberger: > So during the miration I want to do something like this: > > copy tftp://10.6.100.3/config.txt <http://10.6.100.3/config.txt> <http://10.6.100.3/config.txt> > startup-config > and do a reload > or > configure replace tftp://10.6.100.3/config.txt <http://10.6.100.3/config.txt> > <http://10.6.100.3/config.txt> > > I tested my miration path in the lab and I figured out that low > numbering vlans in the range of 2-1001 are for some strange reason not > applied to the config. I tried also deleting vlan.dat and change to > vtp of or transparent/server/client and diffrent vtp versions before > applying the config without success. > > Does somebody have a clou about the strange behaviour?
swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
-
Erich Hohermuth -
Florian Schlums -
Lukas Eisenberger