From: Andrew Bratchell (a.bratchell@caeuk.com)
Date: Mon Nov 04 2002 - 10:48:20 GMT-3
Senthil,
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 format 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 format if the destination media is Ethernet.
Also be aware that when filtering with DLSw+ on Mac addresses DLSw+ works in non-canonical format (Token-Ring format). Thus, you always need to put MAC addresses in this format. If you are using access-lists to specify MAC output list on a DLSw+ statement, you will always use non-canonical format. If the access-list will be using to filter on a token-ring interface it will be non-canonical. If the access-list will be used to filter on an Ethernet interface it will be canonical. Make sure you know how to convert between non-canonical and canonical format. As an aid, you can use Cisco's Bitswapping tool, which can be found on their web site.
Sara's question was using Icanreach statements - because Sara is configuring this as an administrator, DLSw is not doing this by itself, again the MAC addresses must be in non-canonical format because that is what is expected.
BOttom line is this, if you connect networks via DLSw, it sorts out all the conversions for you whether TR to TR, Eth to TR or ETH to ETH. As soon as you start filtering, configuring reachability etc on MAC addresses, IT IS ALWAYS non-canonical.
Andy
-----Original Message-----
From: Senthil Kumar [mailto:senthil.kumar@intechnology.co.uk]
Sent: 04 November 2002 13:23
To: Senthil Kumar; Andrew Bratchell; Sara Li; clarson52@comcast.net;
ccienxtyear@hotmail.com; ghie_pogi@yahoo.com; ccielab@groupstudy.com
Subject: RE: DLSW help
To work around this problem, configure a MAC address on the target device
that is always the same whether it is canonical or non-canonical (for
example, 4242.6666.ffff). [CSCdj48606]-
as your host is ethernet it is canonical, so canonical entry in icanreach
mac tells the peer that it can reach mac-a(in canonical) when the host on
peer end sends an explorer to this mac..the peer knows how to forward.??
isnt this right?
-----Original Message-----
From: Senthil Kumar [mailto:senthil.kumar@intechnology.co.uk]
Sent: 04 November 2002 13:11
To: Andrew Bratchell; Sara Li; clarson52@comcast.net;
ccienxtyear@hotmail.com; ghie_pogi@yahoo.com; ccielab@groupstudy.com
Subject: RE: DLSW help
i dont think you require this as the dlsw peers are not doing translational
bridging.
you can have the macs entered same..and when the remote node sends an
explorer with canonical mac (ethernet) which solves the purpose..
-----Original Message-----
From: Andrew Bratchell [mailto:a.bratchell@caeuk.com]
Sent: 04 November 2002 00:44
To: Sara Li; clarson52@comcast.net; ccienxtyear@hotmail.com;
ghie_pogi@yahoo.com; ccielab@groupstudy.com
Subject: RE: DLSW help
Sara,
If you are working with DLSW - it is always non-canonical.
If you look at your peers and their capabilities using show dlsw
capabilities you will see the MAC address exactly as you entered it with the
dlsw i canreach command - therefore it is up to you to put into the correct
format.
Andy
-----Original Message-----
From: Sara Li [mailto:saralilin@hotmail.com]
Sent: 04 November 2002 00:26
To: clarson52@comcast.net; ccienxtyear@hotmail.com; ghie_pogi@yahoo.com;
ccielab@groupstudy.com
Subject: Re: DLSW help
Chris
thanks for reply, say if i have some ethernet host, i want remote dlsw
peers to access, i need to convert the mac address of the eth host to
non-canonical in the dlsw icanreach statement?
Sara
>From: Chris >Reply-To: Chris >To: Sara Li , ccienxtyear@hotmail.com,
ghie_pogi@yahoo.com, ccielab@groupstudy.com >Subject: Re: DLSW help
>Date: Sun, 03 Nov 2002 09:12:00 -0500 > >when doing DSLW all filters
etc. using MAC addresses are non-canonical. >Always non cananical with
DLSW. > >----- Original Message ----- >From: "Sara Li" >To: ; ; > >Sent:
Saturday, November 02, 2002 8:52 PM >Subject: Re: DLSW help > > > > jay,
> > > > the macaddress in icanreach command, it the mac address here is
canonical > > or non-canonical? or it can be both? > > > > Thanks > > > >
> > > > >From: "Jay" > > > > >Reply-To: "Jay" >To: "Angelo De Guzman" ,
>Subject: Re: DLSW help >Date: > > Sat, 2 Nov 2002 16:17:52 -0800 > >DLSW
protocol filter > >access-list 200 > > permit 0xf0f0 0x0101 > >dlsw
remote-peer 0 tcp (ip address of remote > > peer) lsap-output-list >200
---this will only permit Netbios traffic to > > this peer. > > >DLSW MAC
filter > >dlsw icanreach mac-address > > 4000.3725.0101 (dlsw will take
care of the >canonical/non-canonical > > conversions) >dlsw icanreach
mac-exclusive > > >-Jay > > >----- Original > > Message ----- >From:
"Angelo De Guzman" >To: >Sent: Saturday, November > > 02, 2002 4:04 AM
>Subject: DLSW help > > > > hi, > > I'm not really > > familiar with
dlsw. Need help on > > this. > > Thanks. > > > > DLSw+ > > Protocol
filter: > > - Configure a filter such that the only protocol > > that > >
is transported via DLSw is NetBIOS. Apply this filter > > to > > > > the
DLSw+ remote peer statements on R5. > > DLSw+ MAC filter: > > - > >
Configure DLSw+ such that R2 informs all its peers > > that the only MAC
> > address that R2 can reach is > > 4000.3725.0101. > > - Verify your >
> configuration is correct by viewing the > > peer capabilities. > > > >
> > Thanks in Advance, > > Angelo > > > > > >
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:52 GMT-3