From: BUI, TIN T (SBCSI) (tb4565@xxxxxxx)
Date: Fri Jan 26 2001 - 16:53:45 GMT-3
What I mean in term of linking them together is that station on R1 e0 can
talk to R2 e0 and R1 e1 can talk to R2 e0 and vice versa. R1 e0 does not
need to talk to R1 e1. I don't need bgroup as the default is "all". My
only question is: Do I need dlsw bridge-group 1 and dlsw bridge-group 2 on
R1 or can I get away with only specifying just dlsw bridge-group 1. The
reason I'm asking is I think the "1" is a virtual bridge-group in statement
dlsw bridge-group 1 and will take all bridges on the router and attach via
dlsw.
Another way to reword this question is: Does the "1" in dlsw bridge-group 1
have to match the "1" in bridge-group 1 in interface mode for R1. If it has
to match then I would need two dlsw bridge-group statements because I have
both bridge-group 1 and bridge-group 2 on R1.
> Tin T. Bui
> Senior Network Manager
> CCNP, CNE, MCP
> Network Management Center
> SBC Services Inc.
> 7337 Trade Street, Rm 1110
> San Diego, Ca 92121
> Office #: 858-886-4644/858-886-4589
> Pager #: 858-494-0482
> Fax #: 858-549-4103
> Email: tb4565@sbc.com
>
-----Original Message-----
From: Jarrod Mills [mailto:jarrod.mills@bellnetworks.com]
Sent: Friday, January 26, 2001 11:31 AM
To: BUI, TIN T (SBCSI); ccielab@groupstudy.com
Subject: Re: multiple dlsw bridges
what do you mean by link them together? If you mean you want traffic from
bridge group 1 on R1 to only goto bridge-group 1 on R2 and vice-versa, you
need additional commands (bgroups, etc) and add the bgroup list number to
the remote peer statement.
HTH
----- Original Message -----
From: "BUI, TIN T (SBCSI)" <tb4565@sbc.com>
To: <ccielab@groupstudy.com>
Sent: Friday, January 26, 2001 1:05 PM
Subject: multiple dlsw bridges
> Suppose I have bridge group 1 and bridge group 2 on R1 and I have bridge
> group 1 on R2 and I want to link them together via dlsw. Would this be a
> correct config or do I not need dlsw bridge-group 2? thanks
>
> Router 1
> !
> source-bridge ring-group 2000
> dlsw bridge-group 1
> dlsw bridge-group 2
> 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 Ethernet0
> ip address 150.150.30.1 255.255.255.0
> bridge-group 1
> !
> interface ethernet1
> ip address 150.150.31.1 255.255.255.0
> bridge-group 2
>
> bridge 1 protocol dec
> bridge 2 protocol dec
> !
> Router 2:
> !
> 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.40.1 255.255.255.0
> bridge-group 1
> !
> bridge 1 protocol dec
>
> > Tin T. Bui
> > Senior Network Manager
> > CCNP, CNE, MCP
> > Network Management Center
> > SBC Services Inc.
> > 7337 Trade Street, Rm 1110
> > San Diego, Ca 92121
> > Office #: 858-886-4644/858-886-4589
> > Pager #: 858-494-0482
> > Fax #: 858-549-4103
> > Email: tb4565@sbc.com
> >
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:44 GMT-3