RE: Bootcamp Lab 19 - DLSW

From: Armon Richardson (ar28@xxxxxxxxxx)
Date: Sun Sep 16 2001 - 15:17:29 GMT-3

   
Traffic that originates on Ethernet is picked up from the local Ethernet
bridge group and transported across the DLSw+ network. DLSw+ always
transfers data in noncanonical format. DLSw+ will automatically make the
correct MAC address conversion depending on the destination media. When
DLSw+ receives a MAC address from an Ethernet-attached device, it assumes it
is canonical and converts it to noncanonical for transport to the remote
peer. At the remote peer, the address is either passed unchanged to Token
Ring-attached end systems or converted back to canonical if the destination
media is Ethernet. Note that when an SNA resource resides on Ethernet, if
you configure a destination SNA address in that device, you must use
canonical format. For example, Ethernet-attached 3174s must specify the MAC
address of the FEP in canonical format. If the Token Ring or noncanonical
format of the MAC address of the FEP is 4000.3745.0001, the canonical format
is 0200.ECA2.0080.

---------------------------------------------------------------------------- 

----
Note

thanks,

" Where the willingness is great, the difficulties cannot be great "

Armon Richardson
CNE, MCSE, CCNP, CCDP
Network Systems Engineer

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Bob Chahal
Sent: Sunday, September 16, 2001 11:32 AM
To: Devender Singh; ccielab@groupstudy.com
Subject: Re: Bootcamp Lab 19 - DLSW

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
**Please read:http://www.groupstudy.com/list/posting.html

This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:18 GMT-3