From: S Malik (ccie.09@gmail.com)
Date: Sun Oct 05 2008 - 10:15:12 ART
I use alias for router ospf # and "sh ip int brief | assi". this way I can
quickly get iIPs for nterfaces and for router-id I just type ro and then
press tab.
On Sun, Oct 5, 2008 at 3:18 AM, Rick Mur <rick@rickmur.nl> wrote:
> I really see problems when you create the whole config for each router and
> edit that.
> What I see as the best practice for notepad use is just create the config
> you would type in for each questions.
>
> So question 1 is run ospf area 0 on this interface, you type:
>
> router ospf 1
> router-id 1.1.1.1
> network 172.16.0.1 0.0.0.0 area 0
>
> Question 2 is put this interface in area 2 and make it stub
>
> router ospf 1
> area 2 stub
> network 172.17.0.2 0.0.0.0 area 2
>
> So with this you can paste the question in your routers and verify it.
> This takes a little more time, but keeps the important thing of verifying
> each question. If you do have a problem later on, you can scroll back in
> notepad and see your error. You can even create little notes at each
> question why you did it. So when you are done the verification of the whole
> lab is much easier, because you know your thought process behind each
> question.
>
> Rick Mur
> CCIE #21946
>
>
>
> On 5 okt 2008, at 09:05, Bogdan Sass wrote:
>
> Charles Henson wrote:
>>
>>> No No. Not the whole lab. Not a chance. I am doing that now only because
>>> I'm
>>> starting off with fresh routers. For the real lab, I was considering it
>>> for
>>> the L2/L3 config and possibly for the routing protocols but nothing
>>> beyond
>>> that. Security, QOS, Multicast, etc. would all be worked "real time".
>>> This
>>> just seems to suit my personality so I was curious if anyone else had
>>> taken
>>> the approach. Right now, it's not really impacting my time so I couldn't
>>> see
>>> the harm in it. Considering that "existing" configurations could mess up
>>> my
>>> copy/paste, I'll probably need to either be prepared (somehow) to deal
>>> with
>>> that or scrap the idea completely. How much "preconfig" could they have?
>>> That was rhetorical! :) As long as frame are shut for the obvious
>>> LMI/DLCI
>>> reasons then it shouldn't take me long to "sho ru" a router and make sure
>>> I
>>> don't see anything ugly. Maybe I'm simplifying this. It's my first
>>> attempt
>>> for the most part...
>>>
>>> I can see a few problems with doing that:
>> 1) you lose access to the CLI help - and there may be times in the lab
>> where
>> 2) it may seem like a timesaver now (when you can do the typing outside
>> of the rack rental time), but it might prove to be a timewaster in the lab
>> ("type/copy/paste" vs just "type").
>> 3) as someone has already said, you need to build/verify/build/verify.
>> Check every step along the way. You cannot do that with c/p
>> So I would recommend at least trying to do the configs directly on the
>> routers. Give it a try - if you still feel that doint it first in notepad is
>> better for you, you can always go back. Everybody has his own approach, and
>> what works for one person may not work for another.
>>
>> --
>> Bogdan Sass
>> CCAI,CCSP,JNCIA-ER,CCIE #22221 (RS)
>> Information Systems Security Professional
>> "Curiosity was framed - ignorance killed the cat"
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:19 ARST