From: Darby Weaver (darbyweaver@yahoo.com)
Date: Fri Oct 19 2007 - 02:04:49 ART
Amen!
Think about this one:
I'm discussing the candidate default route and its
usage in practice labs and its potential of being an
easy feature, that might be easily misunderstood if
encountered in a graded lab environment and if one
either takes it for granted and/or does not properly
understand its potential for being a valuable tool.
Some people wandered what it does, others though "ip
default-route" might be considered a static route, and
most people seem to have declined to comment or form
and opinion for whatever reasons...
Now if one is asked to ensure full reachability and
there is a layer two device with only an ip address
but "no ip routing" in effect...
How do you communicate this device's ip address to the
rest of your pod?
You know the usage of nat did come up and so did using
policy routing...
But no one (from that forum) had yet considered using
the candidate default as a tool in this scenario or
one similar to it.
So... since this may be a tool required to get a
switch's ip addressess propagated to the rest of the
pod, maybe it is a useful discussion and maybe not.
Just another thought on tools and switching and things
that get over-looked sometimes.
Kinda like bridging... and fallback bridging...
Again just a thought...
Val beat this one into me... and it took a while for
the lights to come on...
:)
--- Scott Morris <smorris@ipexpert.com> wrote:
> The same can be said about any task... Most things,
> when broken down, are
> very simple. However, many people get hung up in
> the basics without being
> able to see that.
>
> And oftentimes, the problems occur at the
> interaction of tasks, not any one
> thing by itself! So knowing "how to configure"
> something doesn't
> necessarily help with how it works.
>
> I think that the Brians' or anyone's workbook will
> provide a number of
> different samples of things, some similar, some not,
> but it's not just one
> individual thing that makes a lab good or bad. Just
> as it's not just one
> individual thing that makes someone fail a lab
> attempt.
>
> Look for the details though. The devil is in there
> (not trying to pull too
> much on what DR was talking about!). Most people
> fail because of small
> simple things, although at the time they most
> certainly don't seem that way!
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service
> Provider) #4713, JNCIE-M
> #153, JNCIS-ER, CISSP, et al.
> CCSI/JNCI-M/JNCI-ER
> VP - Technical Training - IPexpert, Inc.
> IPexpert Sr. Technical Instructor
>
> A Cisco Learning Partner - We Accept Learning
> Credits!
>
> smorris@ipexpert.com
>
> Telephone: +1.810.326.1444
> Fax: +1.810.454.0130
> http://www.ipexpert.com
>
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Darby Weaver
> Sent: Thursday, October 18, 2007 9:59 PM
> To: darth router
> Cc: bdennis@internetworkexpert.com; shiran guez;
> CCIE.LAB;
> ccielab@groupstudy.com
> Subject: Re: IEWB sample lab - switching approach
>
> DR,
>
> When they put every scenario in their worbooks...
> it really does not leave
> out the possiblity that one might come across a
> similar scenario in either
> another workbook or even the lab.
>
> The possibilities are finite as Brain MaGahan stated
> previously...
>
> But you know this already...
>
> I mean how many ways are there to configure
> etherchannel?
>
>
> --- darth router <darklordrouter@gmail.com> wrote:
>
> > IEs switching in v 4 is pretty kick ass (Brian,
> free stuff over here
> > for that plug!). Sometimes they give you all
> configs, sometimes you
> > are forced to draw a painful Layer 2 diagram out
> to figure stuff out.
> > Sometimes I ponder whether the Brians are psychic,
> or possibly made a
> > deal with satan to know how to put the "right"
> switching in their
> > workbooks to best prepare you for the lab.
> >
> > DR
> >
> > On 10/18/07, Darby Weaver <darbyweaver@yahoo.com>
> > wrote:
> > >
> > > Good point.
> > >
> > > I'm just going through the first couple of labs
> in
> > > version 4 and have not yet made that distinction
> > yet.
> > >
> > > I did recall that being an issue from about
> > version 2,
> > > I think, when I had went to NMC's bootcamp, and
> > took
> > > me a bit to overcome since I was considerably
> > weaker
> > > with switching at the time (about lethargic),
> and
> > used
> > > the chart as a "crutch" and when it was
> removed...
> > I
> > > trembled and fell a bit - but that was a
> reference
> > to
> > > a past event from about 2 years ago and may not
> > > represent the current product at all.
> > >
> > > The current product is much improved by the way.
>
> > I'm
> > > impressed that each lab appears to have nearly
> 100
> > > pages more or less of very well written and
> easily
> > > understood descriptions of exactly what is
> > happeing in
> > > each lab.
> > >
> > > And I'll tell you another thing, and this is
> > premature
> > > since I'm only on the third one and there are at
> > least
> > > 7 available at the moment, those COD's that you
> > guys
> > > have taken the time to create... are the best
> > thing
> > > since sliced bread.
> > >
> > > I watch so many questions get asked over the
> years
> > > hear on GS, you know the how or why, etc. Why
> > this
> > > solution versus these other 2 or 3... And you
> > guys
> > > hit PAYDIRT... with the COD. I was surprised at
> > how
> > > much you packed in and did so, incredibly
> > concisely
> > > too.
> > >
> > > The product is FANTASTIC! I understand that
> > others
> > > are following this trend. The pricing is great
> > and
> > > the value is there...
> > >
> > > Talk about taking a handful of labs, say just
> labs
> > 1-5
> > > or 1-7 and just mastering them. Know the
> why/why
> > not
> > > and taking the time to enjoy the mastery of some
> > of
> > > the more complex issues discussed in each lab.
> > >
> > > The COD's allow one to do this, verus spending a
> > lot
> > > of time second guessing solutions - happens alot
> > on
> > > this list.
> > >
> > > So 100 pages or so of descriptions and breakdown
> > and
> > > then a carefully worded COD... that spots the
> > > issues...
> > >
> > > Kewl idea brought to life and masterfully
> > executed.
> > >
> > >
> > > --- Brian Dennis
> <bdennis@internetworkexpert.com>
> > > wrote:
> > >
> > > > Darby,
> > > > In version 4 of the IEWB Vol 2 Workbook
> there
> > > > isn't a "style" to how
> > > > the VLANs are given. There was a "style" in
> > version
> > > > 3 to how things
> > > > were done but in version 4 you will find that
> > there
> > > > are many "things"
> > > > done differently between the labs. Sometimes
> > you
> > > > get the VLAN
> > > > information in a table, sometimes through the
> > output
> > > > of various show
> > > > commands, sometimes you are asked to determine
> > the
> > > > VLANs needed by
> > > > referencing the diagram and finally sometimes
> > they
> > > > are already done for
> > > > you in the initial configurations.
> > > >
> > > > Brian Dennis, CCIE4 #2210
> > (R&S/ISP-Dial/Security/SP)
> > > > bdennis@internetworkexpert.com
> > > >
> > > > Internetwork Expert, Inc.
> > > > http://www.InternetworkExpert.com
> > > > Toll Free: 877-224-8987
> > > > Direct: 775-745-6404 (Outside the US and
> Canada)
> > > >
> > > >
> > > > >----- Original Message -----
> > > > Subject: Re: IEWB sample lab - switching
> > approach
> > > > Date: Wed, October 17, 2007 21:08
> > > > From: "Darby Weaver" <darbyweaver@yahoo.com>
> > > >
> > > > > I would not fall in love with any vendor's
> > style
> > > > of
> > > > > how they depict the VLAN's given.
> > > > >
> > > > > Since you never know what you may be given
> as
> > (an)
> > > > > exhibit(s) and you never know what may be
> > asked
> > > > later
> > > > > that may not appear in the initial given
> > > > exhibit(s)
> > > > > anyway.
> > > > >
> > > > > I'd almost recommend just looking at a given
> > > > diagram
> > > > > and then making my own table and diagrams
> from
> > > > that.
> > > > >
> > > > > Then, I'd read the lab tasks given and
> ensure
> > that
> > > > > there are no other tasks that modify, add,
> or
> > > > remove
> > > > > anything from the initial given materials
> and
> > go
> > > > from
> > > > > there.
> > > > >
> > > > > I recall going to my first NMC Bootcamp...
> and
> > I
> > > > was
> > > > > used to IE's charts... kicked me into lala
> > trying
> > > > to
> > > > > get used from one to the other style.
> > Realtime.
> > > > >
> > > > > But it made me think differently too. And
> Bob
> > > > > Sinclair will tell you first thing... that
> > Switch
> > > > > diagram and color codes (vlan = color) real
> > > > quickly...
> > > > >
> > > > > Hard to digest at first for some like me...
> > > > >
> > > > > Get used to seeing them anyway they can be
> > thrown
> > > > at
> > > > > you and quckly get used to asking yourself
> > what
> > > > they
> > > > > are doing.
> > > > >
> > > > > Ask yourself, where's the root bridge... of
> > each
> > > > > spanning-tree instance. Is it where you
> want
> > it?
> > > > >
> > > > > Lots of stuff one needs to pay attention too
> > and
> > > > all
> > > > > at the same time.
> > > > >
> > > > > You'll get used to it after a while.
> > > > >
> > > > > But that diagram will become as important as
> > your
> > > > L3
> > > > > to some folks... especially later in the
> lab
> > > > if/when
> > > > > you find yourself troubleshooting something
> > you
> > > > > thought you resolved earlier in the morning.
> > > > >
> > > > >
> > > > > --- shiran guez <shiranp3@gmail.com> wrote:
> > > > >
> > > > > > I think the key to understand how the
> > logical
> > > > > > topology work is to know the
> > > > > > Physical topology so I would draw that
> > first,
> > > > then
> > > > > > if the logical topology
> > > > > > is not already given to you then I would
> > draw it
> > > > to
> > > > > > but I would not delay on
> > > > > > that for ever.
> > > > > >
> > > > > > Vlan Table is also a key element as if you
> > want
> > > > to
> > > > > > be quick and know
> > > > > > problems before they start then you need
> it.
> > > > > >
> > > > > > Note: some time its just as easy as it
> look
> > but
> > > > for
> > > > > > training I would
> > > > > > practice worst case so in the lab I would
> > not be
> > > > > > tackled due to a hard
> > > > > > looking topology.
> > > > > >
> > > > > >
> > > > > > On 10/15/07, CCIE.LAB
> <ccie.lab@verizon.net>
> > > > wrote:
> > > > > > >
> > > > > > > On doing the sample labs, what is the
> > > > recommended
> > > > > > approach on the CAT
> > > > > > > Switching sections.
> > > > > > >
> > > > > > > Do I need to draw out the switch
> topology
> > or
> > > > is it
> > > > > > just as easy as it
> > > > > > > looks
> > > > > > > by configuring what's in the vlan tables
> > > > > > > and then configure the appropriate
> trunks
> > in
> > > > the
> > > > > > trunk table?
> > > > > > > Does the switch config come into play
> > > > elsewhere in
> > > > > > the lab that I should
> > > > > > > draw
> > > > > > > it out?
> > > > > > >
> > > > > > >
> > > > > > > Thnks
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:17 ART