We have the same problem. Several different classes taking different semesters and
leaving the routers in various configurations and register settings. Our solution has
been to have default configurations on a TFTP server and each instructor is responsible
for setting up the lab for whatever basic config they need, often having the students
do
it as part of the training experience.
If any body has a better way, I would sure like to hear about.
Tom Lisa, Instructor, CCNA, CCAI
Community College of Southern Nevada
Cisco Regional Networking Academy
Ben Hockenhull wrote:
> A student of mine just came into my office and posed this problem to me:
>
> Given a set of lab routers, where a student is allowed to do anything they
> wish to the router, how can things be set up so that the router is
> automatically restored to a known default configuration at the end of the
> student's session?
>
> My initial response is that there's really no good way to do this, short
> of special boot roms that would somehow intelligently tftpboot.
>
> boot net statements won't work, as the student can remove them.
> config register frobbing won't work, as the student can change the config
> register, and, indeed, might have to do so to practice password recovery.
>
> Given that the student can change config registers, write erase, set
> enable passwords, reload, etc, how do labs manage their routers in these
> situations? He seemed to think that Cisco Academy has some kind of
> software that helps them with this problem, but I don't see how it's
> possible.
>
> Seems to me that all you can really do is have a staff of people to set
> things right all the time.
>
> Anyone have any ideas?
>
> Ben
>
> --
> Ben Hockenhull
> [EMAIL PROTECTED]
>
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
