From: radha rani (radhaccie@xxxxxxxxxxx)
Date: Fri Nov 03 2000 - 12:04:43 GMT-3
Jack, Thanks for this explanation. I've been reading TR switching from the
Catalyst 5000 config manual this morning and it is extremely confusing. I
don't think i got it yet.
Maybe you can answer this question:
So if i have 2 trcrfs configured on the switch with one parent trbrf, and i
need to connect a router to this switch to - say data link switch or RSRB
traffic to a remote Token-ring lan, do I use two ports on the router - one
on each trcrf hence placing each on a seperate ring? In that case i won't
really use the trbrf for anything. The trbrf is used to bridge traffic
between the rings in the absence of an external bridge - is that right?
-Radha
>From: "Jack Heney" <jheneyccie@hotmail.com>
>Reply-To: "Jack Heney" <jheneyccie@hotmail.com>
>To: jconnary@cisco.com
>CC: radhaccie@hotmail.com, stiff.yu@datacraft-asia.com,
>ccielab@groupstudy.com
>Subject: Re: (actually SRB) - another question with a token ring switch
>3900
>Date: Thu, 02 Nov 2000 22:47:59 GMT
>
>You have multiple bridging options on the 3900...It breaks down like
>this...
>
>The concentrator function (trcrf) is used to move traffic between ports in
>the same ring (sort of like a MAU), but it uses 2 functions to handle this
>movement. It uses transparent bridging, where it simply learns what MAC
>addresses are attached to what ports in the trcrf, and source route
>switching, where it uses the RIF information to make a forwarding decision
>but doesn't modify it at all. So if all that is attached to the trcrf are
>devices in that ring, transparent bridging works fine. But, if you have
>another bridge plugged into a trcrf, the 3900 will need to use the RIF
>information to learn what rings are attached to what ports, so the source
>route switching functionality is used.
>
>The bridging function (trbrf) is used to move traffic between ports in
>different rings, and is much closer in functionality to an ethernet vlan
>than the trcrf is. It defines the broadcast domain, and you must route to
>get from one trbrf to another. The trbrf gives you two options as
>well...source route bridging and source route transparent bridging. If you
>want the trbrf to move traffic to or from a ring (trcrf) based on RIF
>information only, configure the trcrf for source route bridging (this
>allows
>the use of duplicate MAC addresses across different trcrf's). If you want
>the trbrf to move traffic to or from a ring (trcrf) based on either RIF
>information or MAC address, configure the trcrf for source route
>transparent
>bridging (since MAC addresses are learned, all MAC addresses in the trbrf
>must be unique if you use SRT).
>
>This is my understanding of the functionality of token ring vlans, and if
>anyone knows of any errors in the above, I would love to have my
>understanding cleared up even further. I hope this helps.
>Jack
>
>
>>From: "Connary, Julie Ann" <jconnary@cisco.com>
>>Reply-To: "Connary, Julie Ann" <jconnary@cisco.com>
>>To: jconnary@cisco.com
>>CC: "radha rani" <radhaccie@hotmail.com>, stiff.yu@datacraft-asia.com,
>> ccielab@groupstudy.com
>>Subject: Re: (actually SRB) - another question with a token ring switch
>>3900
>>Date: Thu, 02 Nov 2000 17:02:27 -0500
>>
>>Hi again,
>>
>>I've looked at this some more and it seems that on the 3900, the SRB is
>>shown configured under the TrCRFs and not
>>the TrBRF. So what is the use of the TrBRF? I guess I'll have to go back
>>and read the document again. If anyone
>>understands this - that would be great. Also, if that is true, then why
>>when I had the Routers in the same TrCRF did
>>I not need multiring ip configured if the TrCRF is setup for SRB? I'm
>>assuming because they were
>>then on the same ring?
>>
>>totally confused. I've just begun my bridging and DLSW studying - yuck is
>>my first impression.
>>
>>Julie Ann
>>
>>
>>At 04:04 PM 11/2/2000 -0500, Connary, Julie Ann wrote:
>>>Hi,
>>>
>>>I thought that I was setting up exactly the same thing, but withh the
>>>3900
>>>as a token-ring switch with SRB:
>>>
>>>Both routers are running 11.2 code. The 3900 is running version 3 code.
>>>
>>>
>>>R1 ------------------------------------------------------ 3900
>>>------------------------------------------------------ R2
>>> port 2 port 1
>>> trcrf 12 trcrf 11
>>> \trbrf 10/
>>> ip addr 10.1.1.1
>>> SRB
>>>interface Tokenring 0 interface
>>>tokenrin 0
>>>ip addr 10.1.1.4 255.255.255.0 ip addr
>>>10.1.1.5 255.255.255.0
>>>multiring
>>>all multiring
>>>all
>>>
>>>
>>>
>>>I can ping from both R1 and R2 to 10.1.1.1 but cannot ping from R1 to R2.
>>>I tried turning off ip routing, no effect.
>>>
>>>I understood from reading the token ring manuals that a TrBRF would
>>>Source
>>>Route Bridge between two groups
>>>of TrCRFs. When I configure R1 and R2 in the same TrCRF it works fine. I
>>>wanted to test how
>>>SRB works in a TrBRF.
>>>
>>>Any ideas on why this does not work? I thought that multiring all would
>>>allow the R1 and R2 routers
>>>to understand RIF's. But does that mean they act as end stations and send
>>>out explorers? I see R1 or R2 sending
>>>out arp requests out token 0 when I do the pings.
>>>
>>>Julie Ann
>>>
>>>
>>>
>>>
>>>At 01:56 PM 11/1/2000 -0500, radha rani wrote:
>>>>Okay, SRB is working now. Here's what I had to do:
>>>>
>>>>1. Disable ip routing on R4. Until I did that, R1 could not get a reply
>>>>when it arp'd for R3's mac address. That's because R4 was routing ip
>>>>and
>>>>considered R1 & R3 to be on a common subnet so it did not reply via
>>>>proxy-arp. Debug arp showed no reply to the arp request and a debug ip
>>>>packets on R1 generated 'encapsulation failed' messages.
>>>>
>>>>2. Add 'multiring ip' on R1 & R3's TR interfaces
>>>>
>>>>3. Add 'multiring all' on both TR ints on R4 (although 'multiring ip'
>>>>should also suffice since I only configured ip)
>>>>
>>>>4. Adding 'source-bridge ring-group xxx' globally in NOT necessary as R4
>>>>is only a two-port bridge. (I did try it with this comand and it
>>>>worked).
>>>>
>>>>Here are my working configs. I'm off to try RSRB next. Thanks for the
>>>>help everyone.
>>>>
>>>>R1 (ip host):
>>>>
>>>>r1#sh run
>>>>Building configuration...
>>>>
>>>>Current configuration:
>>>>!
>>>>version 11.2
>>>>no service password-encryption
>>>>no service udp-small-servers
>>>>no service tcp-small-servers
>>>>!
>>>>hostname r1
>>>>!
>>>>!
>>>>no ip routing
>>>>no ip domain-lookup
>>>>!
>>>>interface Serial0
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface Serial1
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface TokenRing0
>>>>ip address 10.10.1.1 255.255.255.0
>>>>no ip route-cache
>>>>ring-speed 16
>>>>multiring ip
>>>>!
>>>>no ip classless
>>>>!
>>>>!
>>>>line con 0
>>>>line aux 0
>>>>line vty 0 4
>>>>login
>>>>!
>>>>end
>>>>
>>>>R4 (Source-Route-Bridge):
>>>>
>>>>r4#sh run
>>>>Building configuration...
>>>>
>>>>Current configuration:
>>>>!
>>>>version 11.2
>>>>no service password-encryption
>>>>no service udp-small-servers
>>>>no service tcp-small-servers
>>>>!
>>>>hostname r4
>>>>!
>>>>!
>>>>no ip routing
>>>>!
>>>>interface Serial0
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface Serial1
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface TokenRing0
>>>>no ip address
>>>>no ip route-cache
>>>>ring-speed 16
>>>>multiring all
>>>>source-bridge 100 1 300
>>>>source-bridge spanning
>>>>!
>>>>interface TokenRing1
>>>>no ip address
>>>>no ip route-cache
>>>>ring-speed 16
>>>>multiring all
>>>>source-bridge 300 1 100
>>>>source-bridge spanning
>>>>!
>>>>no ip classless
>>>>!
>>>>!
>>>>line con 0
>>>>line aux 0
>>>>line vty 0 4
>>>>login
>>>>!
>>>>end
>>>>
>>>>
>>>>R3 (ip host) :
>>>>
>>>>r3#sh run
>>>>Building configuration...
>>>>
>>>>Current configuration:
>>>>!
>>>>version 11.2
>>>>no service password-encryption
>>>>no service udp-small-servers
>>>>no service tcp-small-servers
>>>>!
>>>>hostname r3
>>>>!
>>>>!
>>>>no ip routing
>>>>!
>>>>interface Ethernet0
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface Serial0
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface Serial1
>>>>no ip address
>>>>no ip route-cache
>>>>shutdown
>>>>!
>>>>interface TokenRing0
>>>>ip address 10.10.1.3 255.255.255.0
>>>>no ip route-cache
>>>>ring-speed 16
>>>>multiring ip
>>>>!
>>>>no ip classless
>>>>!
>>>>!
>>>>line con 0
>>>>line aux 0
>>>>line vty 0 4
>>>>login
>>>>!
>>>>end
>>>>
>>>>r3#
>>>>
>>>>
>>>>>From: "yujianchun" <stiff.yu@datacraft-asia.com>
>>>>>Reply-To: "yujianchun" <stiff.yu@datacraft-asia.com>
>>>>>To: "radha rani" <radhaccie@hotmail.com>, <ccielab@groupstudy.com>
>>>>>Subject: Re:
>>>>>Date: Wed, 1 Nov 2000 17:52:38 +0800
>>>>>
>>>>>can you tell result? I wait for you.
>>>>>-----Original Message-----
>>>>>From: radha rani <radhaccie@hotmail.com>
>>>>>To: ccielab@groupstudy.com <ccielab@groupstudy.com>
>>>>>Date: 28 October 2000 06:43
>>>>>
>>>>>
>>>>> >Hello,
>>>>> > I have a very simple SRB configuration which is not working. I
>>>>> >would be very grateful if someone could shed some light on this.
>>>>> >
>>>>> >My topology is :
>>>>> >
>>>>> >r1 --- ring100---r4---ring300---r3
>>>>> >
>>>>> >r1 and r3 are acting as hosts and have ip addresses 10.10.1.1/24 and
>>>>> >10.10.1.3/24 resp. r4 is the source-route-bridge. I am unable to
>>>>>ping
>>>>> >r1 and r3 from each other.
>>>>> >
>>>>> >Thanks for your help.
>>>>> >
>>>>> >R4's config is as follows:
>>>>> >
>>>>> >r4#sh run
>>>>> >Building configuration...
>>>>> >
>>>>> >Current configuration:
>>>>> >!
>>>>> >version 11.2
>>>>> >no service password-encrypt
>>>>> >no service udp-small-server
>>>>> >no service tcp-small-server
>>>>> >!
>>>>> >hostname r4
>>>>> >!
>>>>> >!
>>>>> >!
>>>>> >interface Serial0
>>>>> >no ip address
>>>>> >shutdown
>>>>> >!
>>>>> >interface Serial1
>>>>> >no ip address
>>>>> >shutdown
>>>>> >!
>>>>> >interface TokenRing0
>>>>> >no ip address
>>>>> >ring-speed 16
>>>>> >source-bridge 100 1 300
>>>>> >!
>>>>> >interface TokenRing1
>>>>> >no ip address
>>>>> >ring-speed 16
>>>>> >source-bridge 300 1 100
>>>>> >!
>>>>> >no ip classless
>>>>> >!
>>>>> >!
>>>>> >line con 0
>>>>> >line aux 0
>>>>> >line vty 0 4
>>>>> >login
>>>>> >!
>>>>> >end
>>>>> >
>>>>> >r4#
>>>>> >
>>>>> >-Radha
>>>>> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:41 GMT-3