|
vinisantos
3 posts
 |
Today, when I logged into the devices I had to erase all the configuration and reload the devices AGAIN. It took me from 15 to 20 minutes in order to erase all the configuration, reload all the devices and apply the basic configuration so I could start working on the lab. At the end of my session, I took the last 10 minutes to erase all the configuration and reload the devices. I had scheduled the lab for two hours...so I spent around 30 minutes (25% of all the time I had...) power cycling devices, etc. It's okay to spend the last 10 minutes in order leave the lab in good condition for the next person to use it as I would like to get it. However, IT IS NOT okay to spend all that time doing something someone else should have done. I wonder if it is that hard being at least polite and erasing all the configuration and reloading the devices as the instructions of use of the lab states. The same way it's free of charge for you and a great opportunity it's also for me...so we should have the same rights and duties. From the times I used the lab I got all the devices ready for use only ONCE! |
|
stretch
159 posts
 |
Sorry man. I have been considering implementing an automated system to take care of it, but I'm not sure how reliable it will be. |
|
joshlowe
44 posts
 |
One of the things I'm currently testing in my lab is using configuration rollback. Basically, every router and switch has a file in flash called default.cfg. This file was simply a copy of the default startup config immediately after the device was wiped. My students simply enter the privileged EXEC command: configure replace flash:default.cfg when they are finished with the lab. This essentially reverts the entire configuration back to the blank config. It's different than copy flash:default.cfg run because that command merges the current running config with the default.cfg file, whereas configure replace actually removes the current running config completely, then copies the default.cfg file. It takes roughly 5 seconds to complete (depending on how much configuration has to be removed) and requires no restart. It will issue the "shutdown" command on interfaces, remove passwords, and even removes loopbacks and subinterfaces. I've only been testing it a short time, but so far it works really well. The only thing it can't do is delete the vlan.dat file and remove VLANs, so that's still a manual process. As long as nobody deletes or modifies the default.cfg file though, this can be a huge time saver. You may even be able to implement a script on the console server that can run the command for you after the user is disconnected. Hope that helps. Even if you don't decide to implement it for all users, maybe some users can make use of it to make switching between configurations faster. |
|
cmcisco
5 posts
 |
vinisantos, Definitely I agree with you that people should erase the configurations of all routers before their sessions end. However, I doubt how good they can do regarding delete 3550 switch configurations. I will explain a bit here: For example, user A is configuring switches in block A while user B try to delete vlan.dat file and the running configuration of switches in block B, then reload them. If user A doesn't shut down all trunk interfaces between block A and block B, the switches in block B will learn the vlan configurations from block A anyway after reloading even the user B has done everything he's supposed to do. I can't think of any solution so far. Comments are most welcome. |
|
zekkerj
3 posts
|
Does anyone ever tried to create an EXPECT script to clean up the devices? This could be done at start and/or end of reservation. With a little more effort, we could even think of a way this script load initial configurations from the user machine, or even from a TFTP server. |
|
skydiver
3 posts
|
I completely agree with vinisantos post. Had to erase the running- and startup-configs on all six routers this afternoon without the erase command. First I tried joshlowe suggestion but found out that there was no default config in flash. Viewed the IFS also. Finally I gave an "erase startup-config" command. After a reload, evasing initial configuration and sh run I had to check for any ip add on the int's or any running protocols to erase or disable them too. Was no problem to perform this cleanup, but didn't have time to check/cleanup all switches and to do my own lab. Maybe it could be helpful to add a instuction example on the LAB FAQ in how to perform a cleanup before ending a session. A script performed from the access server would be better of course. Regarded it all as a good lesson for real-life situations after passing my CCNA. ;) |
|
JustJames
2 posts
|
I ran into the same problem with configs stored on the routers. Having something set up that would automatically clear configs and reset the equipment 5-10 minutes before the end of each booked session would help a lot. |
|
dantel
17 posts
 |
Stretch: I'm not a Kiwi CatTools expert, just recently started using it. I only use it to do automated backups of my devices though it seems to have the ability to upload files and issue commands as well. There is a free version which supports up to 20 devices, you might give this a shot. CatTools has a scheduling option though I'm not sure how you'd sync this up with reservation times. |
|
stretch
159 posts
|
I've actually been talking with Opengear recently about the possibility of implementing Expect on the console server, which would be the ideal first step in implementing such a solution. I'm still working with their (awesome) development team at the moment to see if it's doable. If not, I'll have to proceed with plan B. |
Viewing 1 - 9 of 9
- 1
