|
dan
5 posts
 |
Greetings, When i logged in to the switches there were lots of vlans. Just wondering if it should be made best practice to delete the vlan.dat files before switch reloads at the end of each session? Of course all the interfaces will have to be shutdown so no vlans propagate along the trunks. Or is this just going to over complicate things? Just thought it could be mentioned in the lab docs for people planning on doing vlan work and maybe put at the bottom of the session email as a reminder. Cheers, Dan |
|
vinisantos
3 posts
 |
I think it's a good idea! Also, if you discover it after you got started you'll have to erase the vlan.dat and reload the switches once again. |
|
SciFiHiFi
15 posts
|
I planed on doing a delete flash:vlan.dat as part of cleaning up after my first lab sessin, but I read in the FAQ that DELETE is a disallowed command. |
|
stretch
269 posts
 |
This works just as well: Switch(config)# no vlan 2-4094 And no, I still don't have an automated cleanup script in place. Sorry. :( |
|
luismg
130 posts
 |
In real life if you are in front of a cisco 6500 catalyst switch, and you do that and reboot, you will get all vlans again, it stores the vlan creation on the running config :-) |
Viewing 1 - 5 of 5
- 1