trouble ticket 1... i have a procedure for this and it is working out... yesterday i loaded the base configs to flash on all six devices, then copy flash:filename run... checked all connectivity including server and clients... again, the trouble ticket configs are the complete configs for the devices that include the lab errors... the manual wants you to load the tt's into flash... i ain't doing that... instead i copy tftp run for the tt configs so i don't have to load up flash with a bunch of shit... don't look at errors upon load nor syslog server... and don't forget to eliminate crypto from the tt files, as well as adjust the router configs for the proper interfaces... yeah, you gotta put your imagination hat on a little for this...
here is my trick for the server and the pc's... i use the same win7 box for all three functions using dhcp... the manual wants you to set a static ip for the srv but that's a pain in the ass dicking around in windows... so i added dhcp to support the srv as well, see below... you don't even have to /renew on the win box... i don't have 3 pc's to dedicate solely to these exercises...
this way when i check connectivity i simply unplug and plug into the proper port with debug ip dhcp server packet on dls1(dhcp server)... then ping and tracert tests from the iternerant pc for further verification throughout the network...
DLS1#sh ip dhcp bind
Bindings from all pools not associated with VRF:
IP address Client-ID/ Lease expiration Type
Hardware address/
User name
10.1.10.3 01e8.9a8f.98a7.03 Jan 08 2013 05:31 AM Automatic
10.1.30.3 01e8.9a8f.98a7.03 Jan 08 2013 05:34 AM Automatic
10.1.50.1 01e8.9a8f.98a7.03 Jan 08 2013 05:35 AM Automatic
also, stay away from show run of any sort... the vendor guys are correct that resorting to show run will not improve your skills...
and the banners are important too...
*** Lab 4-1 Router R1 TT-A Config ***
R1#
No comments:
Post a Comment