From: Gajewski Mariusz (Mariusz.Gajewski@telekomunikacja.pl)
Date: Mon Jan 31 2005 - 17:58:28 GMT-3
Hi everyone,
I'm sure that subject was talked about but I couldn't find much in
archives so , if someone could clarify this for me please ? We have the
application server that resides on ethernet segment and its mac is
0001.9623.9ac0 and we must make sure that R4 only initiates DLSW peering do
R5 when there is interesting traffic from vlan 43 (ethernet segment on R4 )
destined to the application server. I don't understand why the solution
doesn't convert to noncanonical mac-addr .
I found on doc-cd that :
..."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..."
So my understanding is that when we have something connected to ethernet
segment and we block/forward traffic based on the dlsw remote
dmac-output-list conversion is done automaticly by the router itself ,
right?
But , according to Brian :
http://forum.internetworkexpert.com/ubbthreads/showflat.php?Cat=
<http://forum.internetworkexpert.com/ubbthreads/showflat.php?Cat=&Number=245
3&page=4&view=collapsed&sb=5&o=&fpart=1>
&Number=2453&page=4&view=collapsed&sb=5&o=&fpart=1
..."Conversion is required because the router does an internal bit swap when
traffic is received in an ethernet interface, then reswapped as it's sent
out the destination ethernet interface. The problem with doing the icanreach
mac address is that the first bitswapping does not occur, therefore when the
explorer is received it's for a different address. In order to fix this
problem you must swap the address manually"...
So when doing things with "dlsw remote dmac-output-list " with ethernet we
DO NOT convert , but with "dlsw icanreach mac-address" we HAVE TO convert
to noncanonical ?
I'm lost ...
Please clarify,
Thank you,
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:27 GMT-3