From: Jason Sinclair (sinclairj@xxxxxxxxxxxxxxx)
Date: Mon Mar 18 2002 - 21:00:30 GMT-3
Guy,
Please post your configs. The dlsw source-bridge command is ONLY used for
bridging the ethernet bridging domain to DLSW. If you send your configs I
can see what is going on.
Regards,
Jason Sinclair
Manager, Network Support Group
POWERTEL
Ground Level, 55 Clarence Street,
SYDNEY NSW 2000
AUSTRALIA
office: + 61 2 8264 3820
mobile: + 61 416 105 858
* sinclairj@powertel.com.au
-----Original Message-----
From: Lupi, Guy [mailto:Guy.Lupi@eurekaggn.com]
Sent: Tuesday, 19 March 2002 08:17
To: 'Frank B'
Cc: ccielab@groupstudy.com
Subject: RE: DLSW and Source Bridge
I did have source bridge spanning on the interfaces, it
still didn't work.
The only time it worked was if I used the dlsw bridge-group
command and put
the token ring interface into that bridge group. I noticed
you said that
you do require the source bridge statements, but that
doesn't seem to be the
case, after I found that I got it working with the bridge
group commands I
removed all the srb commands and it still worked with no srb
commands on the
router. Why do you say you have to have them, are there
certain situations
where they are required, and some where they are not? By
the way, my ASCII
drawing didn't come out very well so I figured I would give
it another shot
below, any responses are appreciated:
workstation--e0--r1--/\/\/\--r3--to0--to0--r6(bridge)--workstation
-----Original Message-----
From: Frank B [mailto:frank@buff-net.com]
Sent: Monday, March 18, 2002 5:12 PM
To: Lupi, Guy
Cc: ccielab@groupstudy.com
Subject: RE: DLSW and Source Bridge
Guy,
You also need the source-bridge spanning command on
the token
ring interface. This command enables spanning tree
explorers. I assume
you're testing using a windows workstation and enabling
netbeui on you
NIC. If so, you MUST enable spanning tree explorers to see
the shares
across the network if you use SRB.
On your other comment, YES! You need SRB commands with
token ring
interfaces in DLSW. The router uses SRB to get from the
physical ring
through the "bridge" to the virtual-ring you created with
the command:
Source-bridge 1 1 12
DLSW picks it up from the virtual ring.
And lastly, this WILL work with the transparent bridging
commands as you
suspect. Try it out man...post your results to the group.
Aloha, Frank
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]
On Behalf Of
Lupi, Guy
Sent: Monday, March 18, 2002 5:31 AM
To: 'ccielab@groupstudy.com'
Subject: DLSW and Source Bridge
In documents that I have seen, it shows that on a token ring
router
running
dlsw, all that is required is a source-bridge command i.e.
"source-bridge
ring-group 12", and on the interface "source-bridge 1 1 12"
linking the
interface to the virtual ring. I set up dlsw between a
token ring
router
and an ethernet router, I don't have a token ring
workstation so I set
up
one router with ethernet and token ring as a transparent
bridge as seen
below. But it didn't work like I thought. I could not get
it to work
with
the source bridge commands, but when I made the token ring
interface
part of
a bridge group and put in the dlsw bridge-group command, it
worked with
no
problem, I could find the other workstation and transfer
files. I have
also
seen configs where an ethernet router has a source bridge
command when
peering with a dlsw token ring router. When do we use the
source bridge
commands in dlsw, are they really necessary, or can it be
done just
using
bridge groups? I included an ASCII drawing of what I had
set up below,
maybe the source bridge commands didn't work because I had
this setup
with
the transparent bridge?
workstation--------e0-------r1----/\/\/\----r3------------to0--------to0
----
-----------r6--------------------e0--------workstation
(Transparent bridge)
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:12 GMT-3