From: sovan parida (sovanp@yahoo.com)
Date: Tue Apr 22 2003 - 12:16:00 GMT-3
Thanks for all the responses.
Sovan.
--- cannonr <cannonr@attbi.com> wrote:
> The lab scenarios and books that do not translate
> are incorrect. The best
> way to convince yourself of this is to try it
> yourself. Configure the
> scenario you have outlined, turn on dlsw bridging.
> Let the router
> dynamically learn one of the real mac addresses on
> the ethernet interface
> and then look at the dlsw reachability table on the
> remote router. Or dlsw
> local reach. You will see that the mac address is
> converted for you. If
> you add the canonical form of the address, it will
> not be converted when you
> do a show dlsw reach.
>
> Here is a test that I did to convince myself a while
> back.....
>
>
> R5 ethernet0
>
> Internet 150.20.101.7 31 0001.9696.0cd1
> ARPA Ethernet0
> Internet 150.20.101.6 31 0001.9695.fc11
> ARPA Ethernet0
> Internet 150.20.101.5 - 0010.7b80.867b
> ARPA Ethernet0
> Internet 150.20.101.10 56 0009.7c36.5c00
> ARPA Ethernet0
>
> R4 show dlsw reach
>
>
> 0080.6969.308b FOUND REMOTE 150.10.5.5(2065)
> 0080.69a9.3f88 FOUND REMOTE 150.10.5.5(2065)
> 0090.3e6c.3aa0 FOUND REMOTE 150.10.5.5(2065)
>
>
> Lets pick an ethernet mac to convert from R5's arp
> table.
>
> 0001.9696.0cd1
>
> 0000 0000 0000 0001 | 1001 0110 1001 0110 | 0000
> 1100 1101 0001
>
> 0000 0000 1000 0000 | 0110 1001 0110 1001 | 0011
> 0000 1000 1011
>
> non-canonical (tokenring) format =
>
> 0080 6969 308b
>
> This is the same entry found in the dlsw reach on R4
> dynamically.
>
> Lets take this a step further and add a dlsw
> icanreach for the remote mac
> on R5. We'll add the ethernet mac this time...
>
> R5
> dlsw icanreach mac-address 0001.9696.0cd1
>
> show dlsw reach (r4)
>
> 0001.9696.0cd1 UNCONFIRM REMOTE 150.10.5.5(2065)
> 0080.6969.308b FOUND REMOTE 150.10.5.5(2065)
> 0080.69a9.3f88 FOUND REMOTE 150.10.5.5(2065)
> 0090.3e6c.3aa0 FOUND REMOTE 150.10.5.5(2065)
>
> It clearly didn't translate it. This is the
> incorect mac.
>
> Now, we'll remove the icanreach and add one for the
> non-canonical address
> on R5
>
> no dlsw icanreach mac-address 0001.9696.0cd1
> dlsw icanreach mac-address 0080.6969.308b
>
> R4 - show dlsw reach
>
> 0080.6969.308b UNCONFIRM REMOTE 150.10.5.5(2065)
> 0080.69a9.3f88 FOUND REMOTE 150.10.5.5(2065)
> 0090.3e6c.3aa0 FOUND REMOTE 150.10.5.5(2065)
>
> You can see that the dynamically learned entry was
> replaced by the one
> learned
> from the icanreach statement.
>
>
> HTH
> ----- Original Message -----
> From: "sovan parida" <sovanp@yahoo.com>
> To: <ccielab@groupstudy.com>
> Sent: Monday, April 21, 2003 12:15 PM
> Subject: dlsw icanreach mac-add
>
>
> > Hi group,
> > I need to clarify the following.
> >
> > client----enet---R1----FR-----R2---enet--client
> >
> > It is mentioned that the client on R1's Ethernet
> is
> > having a mac-add of 0200.0000.0004. If I need to
> > configure 'dlsw icanreach mac-add 'on R1, should
> this
> > mac address be the same as 0200.0000.0004 or the
> > bit-inverse of it(4000.0000.0020).
> > As far as I understand it should be bit-inverse,
> but I
> > am confused to see many reputed books and
> > lab-scenarios using the mac address as
> 0200.0000.0004.
> > Please comment.
> > Sovan.
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo
> > http://search.yahoo.com
This archive was generated by hypermail 2.1.4 : Thu May 01 2003 - 13:36:01 GMT-3