From: Kinton Connelly (kinton@xxxxxxxxxxxx)
Date: Wed May 03 2000 - 18:08:53 GMT-3
Thanks, Nnanna - that did the trick! I should have remembered to look in
the Tech Tips section - they had exactly the config I was looking for - and
you DO need the "source-bridge ring-group x" command - even when it's
ethernet to ethernet over DLSW+.
Kinton
Here are the configs from Cisco:
3. Ring to Ethernet over WAN
ring1--ROUTER A------WAN-----ROUTER B--ethernet
Router A
--------
!
source-bridge ring-group 2000
dlsw local-peer peer-id 150.150.1.1
dlsw remote-peer 0 tcp 150.150.2.1
!
interface Loopback0
ip address 150.150.1.1 255.255.255.0
!
interface Serial0
ip address 150.150.100.1 255.255.255.0
!
interface TokenRing0
ip address 150.150.10.1 255.255.255.0
ring-speed 16
source-bridge 1 1 2000
source-bridge spanning
Router B
--------
!
source-bridge ring-group 2000
dlsw local-peer peer-id 150.150.2.1
dlsw remote-peer 0 tcp 150.150.1.1
dlsw bridge-group 1
!
interface Loopback0
ip address 150.150.2.1 255.255.255.0
!
interface Serial0
ip address 150.150.100.2 255.255.255.0
!
interface Ethernet0
ip address 150.150.30.1 255.255.255.0
bridge-group 1
!
bridge 1 protocol dec
!
In this example, the station on the Ethernet segment is allowed to talk to
the stations on the Token Ring segment. The DLSw+ router will take care of
the conversion from Ethernet format into Token Ring format. The
bridge-group number is used to tie the Ethernet segment to the DLSw+
process just like the source bridge statement ties the Token Ring segment
to the DLSw+ through the virtual ring-group.
At 5/3/00, you wrote:
>http://cisco.com/warp/public/701/45.html
>
>I for one did not know that the config could work without te source-bridge
>command on the ethernet side...
>Plug in a netbios enabled pc into the ethernet side, and see if the name
>will show up on the other dlsw peers
>
>Nnanna
>
>----- Original Message -----
>From: "Kinton Connelly" <kinton@oldmedia.com>
>To: <ccielab@groupstudy.com>
>Sent: Wednesday, May 03, 2000 3:51 PM
>Subject: quick DLSW+ question
>
>
> > Ok, so I'm going back through some of the CCIE Boot Camp labs and on lab
>3,
> > it wants me to establish a DLSW+ connection between R2's ethernet0 and
>R3's
> > tokenring0. No problem. Here's how I'd do it:
> >
> > R2
> > --
> > dlsw local-peer peer-id 137.20.100.2
> > dlsw remote-peer 0 tcp 137.20.3.33
> > dlsw bridge-group 1
> > !
> > interface Ethernet0
> > ip address 137.20.20.1 255.255.255.0
> > bridge-group 1
> >
> > R3
> > --
> > source-bridge ring-group 10
> > dlsw local-peer peer-id 137.20.3.33
> > dlsw remote-peer 0 tcp 137.20.100.2
> > dlsw bridge-group 1
> > !
> > interface TokenRing0
> > ip address 137.20.30.1 255.255.255.0
> > ring-speed 16
> > source-bridge 1 1 10
> > source-bridge spanning
> >
> > This config seems to work just fine - the circuits get all set up and seem
> > to be happy. But then I reviewed the solution configs and they added this
> > one line to R2 (right above the first dlsw entries):
> >
> > source-bridge ring-group 10
> >
> > Can someone please give me a sanity check on this? I didn't think you
> > needed a "source-bridge ring-group" command for DLSW+ if you were using
> > ethernet interfaces - I thought all you needed was the "dlsw bridge-group
> > x" command.
> >
> > I just read through the CCO docs on this and couldn't find a straight
> > answer - one of their examples uses the "source-bridge ring-group x"
> > command on an ethernet-only router, but that's in the context of SR/TLB.
> >
> > Ok...wait a minute...I just did a little more searching. In the "Designing
> > DLSw+ Internetworks" guide:
> >
> > <http://www.cisco.com/univercd/cc/td/doc/cisintwk/idg4/nd2007.htm>
> >
> > there is a similar example - and they don't use the "source-bridge
> > ring-group x" command. So now I'm even more confused. Any takers?
> >
> > Thanks,
> >
> > Kinton
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:27 GMT-3