From: Rob Ehlers (ccieorbust@xxxxxxxxxxxxxxxxxxx)
Date: Sat Mar 18 2000 - 22:41:33 GMT-3
>From my (limited) understanding, dlsw only talks between "peers", not
between interfaces on the same router. Consider the following network...
+--------+ +---------+
TokenRing 0 --| | WAN | |
| R1 |------| R2 |--Ethernet0
Ethernet 0 --| | | |
+--------+ +---------+
R1
---------------------------------
source-bridge ring-group 10
dlsw local-peer peer-id 10.0.0.1
dlsw remote-peer 0 tcp 10.0.0.2
dlsw bridge-group 60
interface TokerRing0
source-bridge 20 1 10
interface Ethernet0
bridge-group 60
R2
----------------------------------
dlsw local-peer peer-id 10.0.0.2
dlsw remote-peer 0 tcp 10.0.0.1
dlsw bridge-group 1
interface Ethernet0
bridge-group 1
With this configuration, end stations can communicate to each other over
the following paths:
R1-To0 <-> R2-Eth0
R1-Eth0 <-> R2-Eth0
However, R1's 2 interfaces cannot communication to each other. You have to
configure SR/TLB on that router... add the following line:
source-bridge transparent 10 30 1 60
Now R1-To0 and R1-Eth0 can talk to each other, but not through dlsw,
through SR/TLB.
If I've missed anything, hopefully someone else can fill in the blanks.
Rob
On Sat, 18 Mar 2000 Ben_J_Durand@tivoli.com wrote:
> Hi guys,
>
> Here's the situation. I have a router with both an e0 and a to0 on it, and I
> want both ports to participate in DLSW, and be able to talk to each other as
> well.
>
> I understand how translational bridging works to get from the ethernet to the
> token ring. I also know that "dlsw bridge-group X" is required when dealing
> with a bridged ethernet port with dlsw, and that dlsw also attaches
> automatically to a defined virtual ring in a token-ring environment.
>
> What happens when you mix all those together? What gets defined? the
> translational bridging? (source-route transparent...), the "dlsw bridge-group
> X"? both?
>
> If you could descrive the path of the source-routed/transparently bridged pac
ket
> as well, I would much appreciate that. Basically I don't know it the etherne
t
> hits DLSW first and then appears as a local MAC in the reacheability table an
d
> answers to the TR port when a TR host is looking for an ethernet resource, o
r
> if it gets translationally bridged (if that's a word) and then go from the
> virtual ring to the DLSW process.
>
> Thanks for your insight.
>
> Anyone going to the big dance in RTP on 28-29 March?
>
> - Ben
>
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:05 GMT-3