Thanks Keller.
I will try to see if I can modify this specifically for all of the IPexpert
config files. Unfortunately, my perl experience is very limited (lots of
books/practice, but little practical). If you want to help me get the script
working for the IPexpert's NET file -- I will do the work of testing and
packaging all of the labs -- so other IPexpert students can take advantage of
the time spent.
It is kind of amazing to me that IPexpert did not do anything in for lab
configs
to use with their NET file. Great blog about it, but what the heck? No lab
files for students? ouch lol
*****
If anyone already has converted lab-config files -- or if they want to help do
the work, please let me know offline. I would like to go through all of these
labs (workbook 1) and package them -- so that all of the interfaces are ready
to
go out-of-the-box.
If we could get IPexpert's blessing on this project, that would be great.
*****
Mark
>>>>>>>>>>>>
I am surprised none of the vendors (that I know of) have gone to a more
flexible initial config generation system. I wouldn't think it would be
that complicated to write them template-style ('interface
$serialInterface1' instead of 'interface s0/0/0') and then ask you what
your interfaces are. That way, even if you have equipment that is similar,
or have slightly different WIC cards, you can generate configs just for
your kit.
I use this Perl script that I hacked together myself.
http://pastebin.com/3eJndW33
It uses different router names than the IPX setup, but you should be able
to modify it fairly easily. Besides, knowing Perl really helps with
automating tasks -- well worth learning!
Keller Giacomarro
[email protected]
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
Are you a CCNP or CCIE and looking for a job? Check out
www.PlatinumPlacement.com
http://onlinestudylist.com/mailman/listinfo/ccie_rs
