From: Rick (ccie_2003@hotmail.com)
Date: Thu Oct 24 2002 - 11:25:10 GMT-3
I think I have found a trick to get the nonconical mac address without the
wasted effort of converting it. If you can create a circuit first with the
host you want to filter than you can do show dlsw reachability to view the
cach the MAC address, which is always in noncanical format in the cache and
then you can simply copy it into your access-list 700-799.
Also, someone mentioned there as a conversion table on the doc cd for
canonical to noncanoncal... Do you know where it is?
One thing maybe you could help me with is how to work with mask for mac
addresses. I don't understand how to create them...
Here is a quick example:
config# access-list 700 permit 0000.f600.0000 0000.00ff.ffff <---- I
do derive this mask (I guess the truth is I very weak with Hex too...
config# access-list 700 pemit c000.0000.00.80 0000.0000.0000 <---- don't
forget to allow the broadcast for the NetBIOS Name_Query or the circuit to
the peer will not even be established with peer on demand.
Example how to apply it:
dlsw peer-on-demand-defaults dmac-output-list 700
Here is another dumb question......
Can some explain what a SAP is?
Hope this helps,
Rick
----- Original Message -----
From: "Andrew Bratchell" <a.bratchell@caeuk.com>
To: "Prio Utomo" <rionaldi@cbn.net.id>; <ccielab@groupstudy.com>
Sent: Thursday, October 24, 2002 6:13 AM
Subject: RE: DLSW Canonical/NonCanonical
> Prio,
>
> 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-cononical and canonical format. As an aid, you can use Cisco's
Bitswapping tool which can be found on their web site.
>
> Andy
> -----Original Message-----
> From: Prio Utomo [mailto:rionaldi@cbn.net.id]
> Sent: 24 October 2002 03:29
> To: ccielab@groupstudy.com
> Subject: DLSW Canonical/NonCanonical
>
>
> Dear All,
>
> In dlsw configuration, do we need to be aware of canonical/non-canonical
> conversion? or it is done automatically by the router in
ethernet-tokenring
> dlsw bridging?
>
> Can you provide examples if it must be done manually and in what
circumstance
> it must be implemented? (is it in filtering or maybe peering...)
>
> Regards,
> PU
>
>
> **********************************************************************
> Disclaimer
> This email is confidential and intended solely for the use of
> the individual to whom it is addressed. Any views or opinions
> presented are solely those of the author and do not necessarily
> represent those of CAE Office Systems. If you are not the
> intended recipient, be advised that you have received this
> email in error, and that any use, dissemination, forwarding,
> printing or copying of this email is strictly prohibited. If you
> received this email in error, please contact Lee Gatland on
> +44 (0) 1923 477600
> **********************************************************************
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:55 GMT-3