From: Bob Chahal (bob.chahal@xxxxxxxxxxxx)
Date: Mon Sep 17 2001 - 04:42:32 GMT-3
Thanks for the input people.
----- Original Message -----
From: "John Elias" <jelias_@hotmail.com>
To: <bob.chahal@ntlworld.com>; <devender.singh@cmc.cwo.net.au>;
<ccielab@groupstudy.com>
Sent: Sunday, September 16, 2001 7:30 PM
Subject: Re: Bootcamp Lab 19 - DLSW
> Bob,
> I believe you are correct. If you plug a pc into that ethernet
segment,
> and go to the other side of the dlsw connection, go into Network
> Neighborhood, search on any name, you will see on the remote side a mac
> address. This mac address is the mac address of your pc that is plugged
> into your ethernet. (Using the 'show dlsw reach' command.) You will
notice
> that your mac address was converted to non-canonical format. So I would
say
> that you need to convert your mac address that is on the ethernet segment
to
> a non-canonical format before you do an 'dlsw icanreach mac-address'
> statement.
>
> John E.
> CCIE #8150
>
>
> >From: "Bob Chahal" <bob.chahal@ntlworld.com>
> >Reply-To: "Bob Chahal" <bob.chahal@ntlworld.com>
> >To: "Devender Singh" <devender.singh@cmc.cwo.net.au>,
> ><ccielab@groupstudy.com>
> >Subject: Re: Bootcamp Lab 19 - DLSW
> >Date: Sun, 16 Sep 2001 16:32:26 +0100
> >
> >I know what you're saying but lets say for example the device is on an
> >ethernet segment with a mac address of 4444.3333.2222 and you want to
> >configure an icanreach statement that prevents explorers for this mac
> >address you have to convert the cannonical mac address into
non-canonical.
> >
> >dlsw icanreach 2222.cccc.4444
> >
> >Another way of putting this is (forgetting any multicast mac address
> >clashes)
> >
> >HostA---ethernet---R1------DLSW-------R2----token-ring-----HostB
> >
> >HostA: macaddr 1111.1111.1111
> >HostB: macaddr 2222.2222.2222
> >
> >if you wanted to prevent explorers for both the Host devices you would
> >configure
> >
> >R1
> >dlsw local peer 1.1.1.1
> >dlsw remote 0 tcp 1.1.1.2
> >dlsw bridge 1
> >dlsw icanreach 8888.8888.8888
> >!
> >bridge 1 pro ieee
> >!
> >int e0
> >bridge-group 1
> >
> >
> >R2
> >dlsw local peer 1.1.1.2
> >dlsw remote 0 tcp 1.1.1.1
> >dlsw icanreach 2222.2222.2222
> >!
> >source-bridge ring 10
> >!
> >int to0
> >source-bridge 1 1 10
> >source-bridge spanning
> >
> >If HostB is an SNA mainframe then HostA will have a hard configured MAC
> >address for the Mainframe as 4444.4444.4444. When Host A sends an
explorer
> >for 4444.4444.4444 the DLSW router converts the mac adress to
non-canonical
> >(2222.2222.2222) and replies to the explorer as it has the mac address in
> >its cache.
> >
> >Another example could be if HostA is a key Netbios server and HostB sends
> >and explorer to 8888.8888.8888. It is RouterA that converts this to
> >1111.1111.1111 when the frame passes onto the ethernet segment to HostA.
> >
> >
> >----- Original Message -----
> >From: "Devender Singh" <devender.singh@cmc.cwo.net.au>
> >To: "Bob Chahal" <bob.chahal@ntlworld.com>; <ccielab@groupstudy.com>
> >Sent: Sunday, September 16, 2001 1:19 PM
> >Subject: RE: Bootcamp Lab 19 - DLSW
> >
> >
> > > Bob,
> > > I disagree, may be I am wrong. But I think dlsw talks only
> >non-cannonical
> > > format. Cannonical formats should be only used when configuring
ehternet
> > > interfaces for redundancy.
> > >
> > > Devender Singh
> > > BE(Hons), CCNP
> > > IP Solution Specialist
> > >
> > >
> > > -----Original Message-----
> > > From: Bob Chahal [mailto:bob.chahal@ntlworld.com]
> > > Sent: Sunday, 16 September 2001 8:38
> > > To: ccielab@groupstudy.com
> > > Subject: Bootcamp Lab 19 - DLSW
> > >
> > >
> > > Hi all,
> > >
> > > I've searched the archives and no one seems to have picked up on the
q5
> >in
> > > task two.
> > >
> > > You are asked to configure a static resource on R6 for MAC address
> > > 4444.3333.2222. Since this router has only an ethernet configured as
> >part
> >of
> > > DLSW then this resource would be an ethernet device. so shouldn't you
be
> > > converting the address into non-canonical and configure as follows
> > >
> > > dlsw icanreach 2222.cccc.4444
> > >
> > > If this kind of thing comes up on the real lab I guess I'll ask the
> >proctor
> > > for clarification. And the same applies for q3 as this address range
> > > 3003.3003.xxxx could be for ethernet of token ring devices as the DLSW
> > > config includes both interface types.
> > >
> > > Anyone agree or disagree. Appreciate nay comments.
> > >
> > > Thanks
> > >
> > > Bob
> > > **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:32:19 GMT-3