From: Kumar, Senthil (senthil.kumar@intechnology.co.uk)
Date: Wed Nov 27 2002 - 11:40:32 GMT-3
many thanks Andy,, good ref you've sent me just twodays before the session
-----Original Message-----
From: Andrew Bratchell
To: Senthil Kumar; Sara Li; clarson52@comcast.net; ccienxtyear@hotmail.com;
ghie_pogi@yahoo.com; ccielab@groupstudy.com
Sent: 04/11/2002 22:20
Subject: RE: DLSW help
Senthil,
Re dlsw Icanreach ,it is always non-canonical, regardless of whether it
is Ethernet or Token-Ring.
Reasons :-
1) DLSW was invented by IBM for their Token-Ring networks, this is why
DLSW works in non-canonical format.
2)I quote from a TAC case I opened at Cisco a while back "You need to
use the non-canonical format when configuring the icanreach. The MAC
is always bit swapped between ethernet and DLSW, which means it will be
swapped again when going from DLSW back to ethernet at the other end.
Show dlsw reach and icanreach will both be in the non-canonical form. "
Please note that there is one exception to this rule, and that is if
your are configuring DLSW with Advanced Ethernet Load Balancing. In this
case it is canonical.
For more information please refer to
www.cisco.com/warp/public/697/8.html
Thanks
Andy
-----Original Message-----
From: Senthil Kumar [mailto:senthil.kumar@intechnology.co.uk]
Sent: 04 November 2002 19:10
To: Senthil Kumar; Andrew Bratchell; Sara Li; clarson52@comcast.net;
ccienxtyear@hotmail.com; ghie_pogi@yahoo.com; ccielab@groupstudy.com
Subject: RE: DLSW help
sorry. ethernet's mac's need non-canonical conversion while deploying
filters, but when hosts start communicating the dlsw peers will
autosense
the media and does the can -2 -noncan automatically.
remember to use non-can format while using ethernet macs for defining
filters in dlsw.
-----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:23:11 GMT-3