From: Joe Soricelli (jsoricelli@xxxxxxxx)
Date: Fri Jul 23 1999 - 11:36:01 GMT-3
Mark-
Excuse the following configs, they are all I have stored on my laptop
currently. The example below is kind of simple, but I think that it shows
the basics. These basics can then scale as large as you wish. The routers
below are configured at the edge of a network that has a Frame Cloud in the
middle as well as 3-4 other routers, so the IP addresses will not make sense
in this chopped up format.
>From a DLSW perspective, R2 is a group member of Group 10. R5 is a group
member of Group 10. R4 is the border peer in Group 10. R2 wants to
communicate with R5.
R5 has the TR interface in it. You can look below for the bridging
commands, but the important thing to remember is this: DLSW terminates the
RIF!! What this means to you is that under the TR interface, you need the
source-bridge <local-ring> <bridge> <virtual-ring> command and in the DLSW
section you need the source-bridge <virtual-ring> command. They only need
to match on that router. Another TR router in the network can use a
completely different virtual ring and DLSW will work just fine.
For those that are curious, if there was another group floating around out
there somewhere, the configs for them would look exactly the same with one
exception. The two border group routers would have remote-peer statements
pointing at each other. Just remember that the border peers need to know
about all the other border peers (full-mesh).
HTH,
Joe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
hostname r2
!
dlsw local-peer peer-id 172.16.64.2 group 10 promiscuous
dlsw remote-peer 0 tcp 172.16.160.1
dlsw bridge-group 1
!
interface Ethernet0
no ip address
bridge-group 1
!
interface Serial0
ip address 172.16.64.2 255.255.255.0
encapsulation frame-relay
frame-relay map ip 172.16.64.1 102 broadcast
frame-relay map ip 172.16.64.3 102 broadcast
hostname r4
!
dlsw local-peer peer-id 172.16.160.1 group 10 border promiscuous
!
interface Serial0
ip address 172.16.160.1 255.255.255.0
encapsulation frame-relay
frame-relay map ip 172.16.160.2 104 broadcast
hostname r5
!
source-bridge ring-group 100
dlsw local-peer peer-id 172.16.96.2 group 10 promiscuous
dlsw remote-peer 0 tcp 172.16.160.1
!
interface Ethernet0
ip address 172.16.96.2 255.255.252.0
!
interface TokenRing0
no ip address
ring-speed 16
source-bridge 10 1 100
------------------------------------------------------------------
Joseph M. Soricelli, CCIE #4803, CCNP
EMAIL: jsoricelli@ccci.com
Chesapeake Computer Consultants, Inc.
8110 Gatehouse Road, Suite 101E Phone: (703) 207-0757
Falls Church, VA 22042 Fax: (703) 207-0441
FYI - About Chesapeake: We are a Cisco Certified Training and
professional services partner. We offer most of the Cisco
training courses as well as training for Fore, NetScout, and
CheckPoint-1 Firewalls. We provide network consulting services,
including design, network health, management, firewall,
and problem solving. We now have 21 CCIEs on our staff
of instructor/consultants.
-------------------------------------------------------------------
-----Original Message-----
From: Mark, Detrick <mdetrick@cisco.com>
To: Chuah Eng Wee <chuahew@cyberway.com.sg>; Joe Soricelli
<jsoricelli@fridge.ccci.com>; ccielab@groupstudy.com
<ccielab@groupstudy.com>
Date: Thursday, July 22, 1999 12:10 PM
Subject: Re: DLSW+ border peer
>I have a question concerning DLSW+...
>
>For the border config, what source commands are needed to make this work.
>Are none needed or have they been left out? For example, if TR is attached
>to peers. Where would the virtual ring extend, just within the border or
>across borders? Does anybody have complete configs with peers that have
>rings within each border group? Unfortunately, I have no access to any TR
>equipment and I am at a loss.
>
>Thanks,
>Mark Detrick
>DSL Business Unit
>Cisco Systems
>2569 McCabe Way
>Irvine, CA 92614
>
>----- Original Message -----
>From: Chuah Eng Wee <chuahew@cyberway.com.sg>
>To: Joe Soricelli <jsoricelli@ccci.com>; <ccielab@groupstudy.com>
>Sent: Thursday, July 22, 1999 8:12 AM
>Subject: Re: DLSW+ border peer
>
>
>> Hi Joe,
>>
>> Thanks, it works after adding in promiscuous.
>>
>> One more question on dlsw peer-on-demand command, when do we
>> need to use this command ??
>>
>> Thanks
>> Eng Wee
>>
>> At 07:47 22/07/99 -0400, Joe Soricelli wrote:
>> >Add promiscuous statements to r6 and r2
>> >------------------------------------------------------------------
>> > Joseph M. Soricelli, CCIE #4803, CCNP
>> > EMAIL: jsoricelli@ccci.com
>> >
>> > Chesapeake Computer Consultants, Inc.
>> > 8110 Gatehouse Road, Suite 101E Phone: (703) 207-0757
>> > Falls Church, VA 22042 Fax: (703) 207-0441
>> >
>> > FYI - About Chesapeake: We are a Cisco Certified Training and
>> > professional services partner. We offer most of the Cisco
>> > training courses as well as training for Fore, NetScout, and
>> > CheckPoint-1 Firewalls. We provide network consulting services,
>> > including design, network health, management, firewall,
>> > and problem solving. We now have 21 CCIEs on our staff
>> > of instructor/consultants.
>> >-------------------------------------------------------------------
>> >
>> >-----Original Message-----
>> >From: Chuah Eng Wee <chuahew@cyberway.com.sg>
>> >To: ccielab@groupstudy.com <ccielab@groupstudy.com>
>> >Date: Thursday, July 22, 1999 5:06 AM
>> >Subject: DLSW+ border peer
>> >
>> >
>> >>Hi..
>> >>
>> >>I am trying out DLSW with border peer. Setup as below :
>> >>
>> >>[r6]------------[r7]----------------[r1]---------------[r2]
>> >> 67.6 67.7 71.1 71.2 12.1 12.2
>> >>
>> >>r6, r7 peer group 70, r7 border peer
>> >>r1, r2 peer group 10, r1 border peer
>> >>
>> >>I have 2 PCs each at e0 of r6 and r2, but I cannot
>> >>find the computer using network neighborhood.
>> >>
>> >>Below config. Did I miss out anything ? Can anyone
>> >>explain what is peer-on-demand. I read the documentation,
>> >>but couldn't really understand.
>> >>
>> >>THanks
>> >>ENg Wee
>> >>
>> >>
>> >>
>> >>
>> >>r6 config
>> >>----------
>> >>dlsw local-peer peer-id 172.16.60.1 group 70
>> >>dlsw remote-peer 0 tcp 172.16.71.7
>> >>dlsw bridge-group 1
>> >>!
>> >>interface Ethernet0
>> >> ip address 172.16.60.1 255.255.255.0
>> >> bridge-group 1
>> >>
>> >>
>> >>r7 config
>> >>----------
>> >>dlsw local-peer peer-id 172.16.71.7 group 70 border promiscuous
>> >>dlsw remote-peer 0 tcp 172.16.71.1
>> >>
>> >>
>> >>r1 config
>> >>----------
>> >>dlsw local-peer peer-id 172.16.71.1 group 10 border promiscuous
>> >>dlsw remote-peer 0 tcp 172.16.71.7
>> >>
>> >>
>> >>
>> >>r2 config
>> >>----------
>> >>dlsw local-peer peer-id 172.16.20.1 group 10
>> >>dlsw remote-peer 0 tcp 172.16.71.1
>> >>dlsw bridge-group 1
>> >>!
>> >>interface Ethernet0
>> >> ip address 172.16.20.1 255.255.255.0
>> >> bridge-group 1
>> >>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:42 GMT-3