From: Mike Gutknecht (mike@xxxxxxxxxxxxx)
Date: Thu May 24 2001 - 11:45:41 GMT-3
Excellent! Thanks.
-----Original Message-----
From: Michael E. Flannagan [mailto:mflannag@cisco.com]
Sent: Thursday, May 24, 2001 6:39 AM
To: Mike Gutknecht
Subject: RE: RE: dlsw in ccbootcamp lab 16 V2
Example:
If R1 is connected to R2, R3 & R4 and R4 send R1 an ICANREACH for xxxx
then, you are correct, R1 will still need to send a local explorer to
determine which LAN interface he can get to xxxx through. The difference
is that R4 will ONLY send explorer packets to R1....this will eliminate
excess WAN traffic to R2 & R3. This can also be accomplished by having
R2 & R3 send an ICANNOTREACH for xxxx. One last note, from a best
practices standpoint -- Simply saying ICANREACH xxxx does not mean that
you CAN'T reach anything else (ie, it's not exclusive). If the ONLY
thing connected to R4 is xxxx, then R4 should be configured for an
ICANREACH xxxx and mac-exclusive, which basically says "I can only reach
xxxx, don't bother me about anything else because I can't get there."
Hope that helps :-)
---------------------------------------------------------
C i s c o S y s t e m s Michael E. Flannagan
| | Network Consulting Engineer
||| ||| Research Triangle Park, NC
||||||| ||||||| (919) 392-4550
.:|||||||||||:.:|||||||||||:. mflannag@cisco.com
---------------------------------------------------------
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Mike Gutknecht
> Sent: Thursday, May 24, 2001 9:40 AM
> To: 'phillipscurtis@netscape.net'; CCIELAB (E-mail)
> Subject: RE: RE: dlsw in ccbootcamp lab 16 V2
>
>
> Thanks! How does icanreach actually tell R3 where the station
> is? It's not
> like a static route that points to an interface.
>
> It seems to me that icanreach XXX basically tells the router
>
> 1. not to look to DLSW peers to find this station XXX
> 2. to inform other DLSW peers during capabilities exchange that XXX is
> locally reachable from R3
>
> However, if R3 has 4 local token ring interfaces, I don't
> understand how
> we've told it which interface to use to find XXX. It would seem like we
> would still need to send a local explorer to find it.
>
> Comments?
>
> -----Original Message-----
> From: phillipscurtis@netscape.net [mailto:phillipscurtis@netscape.net]
> Sent: Thursday, May 24, 2001 4:57 AM
> To: mike@justcisco.com
> Subject: Re: RE: dlsw in ccbootcamp lab 16 V2
>
>
> By configuring an icanreach entry with the address of the AS400 on R3
> you are statically telling it that it know where the AS400 is.
> Subsequent
> inquiries by local stations on the r3 segment will not result
> in R3 sending
> exporers to discover the path to the AS400.
>
>
>
>
> Mike Gutknecht <mike@justcisco.com> wrote:
> >
> > I'm a bit confused here. The lab statement says "Configure
> R3 so that it
> > can respond locally and not send explorer frames for the
> host AS400." By
> > explorer frames, do they mean, frames destined for other
> DLSW peers or
> frame
> > destined for local interfaces.
> >
> > My initial thought was to use a dlsw netbios-name command to
> keep R3 from
> > asking it's peers for reachability info on AS400. However,
> the answers
> use
> > icanreach.
> >
> > Are we assuming that AS400 is hanging directly off a
> connected interface
> > (ethernet or TR)?
> >
> > -----Original Message-----
> > From: Bob Chahal [mailto:bob.chahal@ntlworld.com]
> > Sent: Sunday, May 20, 2001 2:36 PM
> > To: Steven Weber; GROUPSTUDY..
> > Subject: Re: dlsw in ccbootcamp lab 16 V2
> >
> >
> > icanreach for netbios name AS400 I seem to remember, put that on R3.
> >
> >
> > ----- Original Message -----
> > From: "Steven Weber" <itweber@earthlink.net>
> > To: "GROUPSTUDY" <ccielab@groupstudy.com>
> > Sent: Sunday, May 20, 2001 7:14 PM
> > Subject: dlsw in ccbootcamp lab 16 V2
> >
> >
> > > I can't seem to configure Section 3 task 3 step 3.
> > > Configure r3 so that it can respond locally and not send
> explorer frames
> > for
> > > the host AS400.
> > > Can someone please shed some light.
> > >
> > > Thanks
> > > Steve
> > > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
> > **Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:52 GMT-3