From: R.J.Neill Craven (ncraven@xxxxxxxxxxxxxxx)
Date: Wed Oct 17 2001 - 00:51:20 GMT-3
Brian,
I am having a little trouble sifting through your scenario. For
example, where does R4 fit in? Are you positioning R4 as a next hop
router to R9? If so, you need an IP address on the Token Ring
interfaces of both routers, and they must be in the same subnet.
Anyway, let me see if I can clear up some of the mystery with some
rantings. (I don't mean to insult your intelligence so forgive me if
I am stating the obvious or appear to be speaking down.)
I have been seeing threads of two different issues; first,
successfully communicating over SRB and, second, SR/TLB. Let me
discuss the first in this reply. If you or others have questions
relating to SR/TLB, I'd be pleased to take them up subsequently.
Unless otherwise configured, a Cisco router assumes its Token Ring
interface(s) is(are) associated with a single ring environment. So,
by default, when ARPing to resolve an IP address of another system
such as a router, or when sending a routing update, for example, the
router sends a broadcast onto the local ring only; the router does
not invoke the explorer capability of SRB. In other words, it does
not set the RII (the top bit of the source MAC address). To have the
router set the RII and, therefore, perform an all-routes (or is it a
single-route explorer, I forget), you must "tell" the Token Ring
interface that it lives in a "multiring" environment. Appropriately,
the interface command is "multiring <protocol>". You must be sure to
enter this command on both routers, otherwise the forward path will
work but the reverse path will not. Assuming you have SRB configured
correctly in whatever technology you have between the routers, this
is all you need to do for the routers to talk to each other.
On R4...
interface to1
ip address 172.16.70.10 255.255.255.0 ! or some other addresss
multiring ip ! or "multiring all" if you prefer
On R9...
interface to0
ip address 172.16.70.9 255.255.255.0
multiring ip ! or "multiring all" if you prefer
Notice that you do not need to configure the Token Ring interfaces to
be part of the SRB environment. In other words, you do not require a
"source-bridge" command on the interface. Now, you might want to
configure SRB on the interfaces for other reasons, but you don't need
SRB enabled on the interface for what we are talking about here. (An
earlier question of mine might have implied that configuring the
Token Ring interfaces for SRB was useful. After I sent the message, I
realized my question could be taken out of context. Anyway, you do
not need to configure the interfaces themselves for SRB.)
At this point, the routers should be talking to each other, but if
you still are unable to ping or send routing updates or do any of the
neat IP things we like to do between routers, then focus on the
intervening SRB environment, itself. From your message I see you have
a Catalyst 3920. From what I can glean, you have configured the 3920
correctly with TrCRFs 4 (ring 4) and 9 (ring 9), and have associated
the CRFs correctly with TrBRF 49 (bridge 1). So, if you are confident
the interfaces are configured properly, I suggest you try resetting
the 3920 to see if the problem disappears. I have a rule of thumb
with Cisco technology. When I have exhausted all logical
explanations, I try reloading. Too often the problem goes away!
Let me know how you make out.
Cheers,
Neill
At 1:00 AM +0000 17/10/01, Brian Lodwick wrote:
>Both r4 and r9 have the command "multiring all" on them.
>from below configs
>r4
>interface TokenRing1
>mtu 1500
>no ip address
>no ip directed-broadcast
>ring-speed 16
>multiring all
>source-bridge 4 2 1000
>source-bridge spanning
>
>r9
>interface TokenRing0
>mtu 1500
>ip address 172.16.70.9 255.255.255.0
>no ip directed-broadcast
>no ip route-cache
>ring-speed 16
>multiring all
>
>Since my last e-mail message I have revised this to:
>r4
>interface TokenRing1
>mtu 1500
>no ip address
>no ip directed-broadcast
>ring-speed 16
>multiring all all-routes
>source-bridge 4 2 1000
>source-bridge proxy-explorer
>
>r9
>interface TokenRing0
>mtu 1500
>ip address 172.16.70.9 255.255.255.0
>no ip directed-broadcast
>no ip route-cache
>ring-speed 16
>multiring all all-routes
>
>I thought I knew this stuff, but obviously I am all screwed up.
>Thanks for the idea. Is this how it should be? Or should the
>multiring command only be on r9 since r9 is supposed to be acting
>like an endstation? I figured it should also be on r4 since r4 needs
>to send explorers to get to r9 as well?
>
>>>>Brian
>
>
>
>>From: Jason Sinclair <sinclairj@powertel.com.au>
>>To: 'Brian Lodwick' <xpranax@hotmail.com>, ccielab@groupstudy.com
>>Subject: RE: SR/TLB using routers as end-stations
>>Date: Wed, 17 Oct 2001 10:43:31 +1000
>>
>>Brian,
>>
>>It looks as though you are missing the RIF info - I believe that you require
>>the multiring command under the interface on the router to enable the router
>>to make use of the RIF info?
>>
>>Regards,
>>
>>Jason Sinclair
>>Network Support Manager
>>POWERTEL Limited
>>Level 11, 55 Clarence Street, SYDNEY
>>Phone: 61-2-8264-3820
>>Fax: 61-2-9279-2604
>>Mobile: 0416 105 858
>>jasons@powertel.net.au
>>
>> -----Original Message-----
>> From: Brian Lodwick [mailto:xpranax@hotmail.com]
>> Sent: Wednesday, 17 October 2001 09:52
>> To: ccielab@groupstudy.com
>> Subject: SR/TLB using routers as end-stations
>>
>> It seems as though Source-route bridging and SR/TLB are sore
>>subjects with
>> everyone. Is there anyone out there on the list that knows
>>SR/TLB well
>> enough to help me out with this scenario? I am STRUGLING!
>>
>> r9 tok0--ring9--3920---ring4----tok1 R4 e0-----e0 R11
>>
>> This is the diagram of my scenario.
>> The 3920 Token-Ring switch has the port from r9 in TrCRF
>>0x09, and the port
>> from r4 in TrCRF 0x04.
>> Both TrCRF's 0x09 and 0x04 are in TrBRF 0x01.
>>
>> On router r9's Tok0 interface I have configured an ip
>>address
>> (172.16.70.9/24)
>> And on r11's e0 interface I have configured an ip address
>>(172.16.70.11/24)
>>
>> On r4 I have configured SR/TLB to translate from the
>>ethernet segment to the
>> Token-Ring and back.
>>
>> The hopefull outcome is to enable r11 and r9 to be able to
>>ping each other.
>> With the current configuration I resolve arp for r11 on r9,
>>and on r11 I
>> resolve arp for r9, but I cannot ping back and forth.
>> r4 shows the Ring group 1000 to be a part of bridge group 1,
>>and is in the
>> forwarding state.
>> When I do show bridge verbose on r4 it shows RingGroup1000
>>with the MAC
>> address of r9's tok 0 flipped to canonical.
>>
>> r9#sh int tok 0
>> TokenRing0 is up, line protocol is up
>> Hardware is TMS380, address is 0000.3090.c7de (bia
>>0000.3090.c7de)
>> ...snipped....
>> r4#sh bridge verbose
>>
>> Total of 300 station blocks, 297 free
>> Codes: P - permanent, S - self
>>
>> BG Hash Address Action Interface VC Age
>>RX count TX
>> count
>> 1 5F/0 0000.0c4a.99c6 forward Ethernet0 - 1
>>1
>> 0
>> 1 98/0 0000.0c09.e37b forward RingGroup1000 - 0
>>219
>> 11
>> 1 DA/0 0050.547f.d00a forward Ethernet0 - 3
>>1
>> 0
>>
>> This seems right, but I cannot ping across.
>>
>> Below are my configs:
>> r11#sh run
>> Building configuration...
>>
>> Current configuration:
>> !
>> version 12.0
>> service timestamps debug uptime
>> service timestamps log uptime
>> no service password-encryption
>> !
>> hostname r11
>> !
>> !
>> ip subnet-zero
>> no ip routing
>> no ip domain-lookup
>> bridge irb
>> !
>> !
>> !
>> interface Ethernet0
>> ip address 172.16.70.11 255.255.255.0
>> no ip directed-broadcast
>> no ip route-cache
>> arp snap
>> bridge-group 1
>> !
>> interface Serial0
>> no ip address
>> no ip directed-broadcast
>> no ip route-cache
>> no ip mroute-cache
>> shutdown
>> no fair-queue
>> !
>> interface Serial1
>> no ip address
>> no ip directed-broadcast
>> no ip route-cache
>> shutdown
>> !
>> ip classless
>> !
>> bridge 1 protocol ieee
>> alias exec ip sh ip route
>> alias exec ipx sh ipx route
>> alias exec int sh ip int brief
>> !
>> line con 0
>> transport input none
>> line aux 0
>> line vty 0 4
>> !
>> end
>>
>>
>> r4#sh run
>> Building configuration...
>>
>> Current configuration:
>> !
>> version 12.0
>> service timestamps debug uptime
>> service timestamps log uptime
>> no service password-encryption
>> !
>> hostname r4
>> !
>> !
>> !
>> !
>> !
>> !
>> ip subnet-zero
>> no ip domain-lookup
>> !
>> cns event-service server
>> !
>> !
>> bridge irb
>> !
>> source-bridge ring-group 1000
>> source-bridge transparent 1000 11 2 1
>> !
>> !
>> interface Ethernet0
>> no ip address
>> no ip directed-broadcast
>> arp snap
>> bridge-group 1
>> !
>> interface Ethernet1
>> no ip address
>> no ip directed-broadcast
>> shutdown
>> media-type 10BaseT
>> !
>> interface Serial0
>> no ip address
>> no ip directed-broadcast
>> no ip mroute-cache
>> shutdown
>> !
>> interface Serial1
>> no ip address
>> no ip directed-broadcast
>> shutdown
>> !
>> interface Serial2
>> no ip address
>> no ip directed-broadcast
>> shutdown
>> !
>> interface Serial3
>> no ip address
>> no ip directed-broadcast
>> shutdown
>> !
>> interface TokenRing0
>> no ip address
>> no ip directed-broadcast
>> shutdown
>> ring-speed 16
>> !
>> interface TokenRing1
>> mtu 1500
>> no ip address
>> no ip directed-broadcast
>> ring-speed 16
>> multiring all
>> source-bridge 4 2 1000
>> source-bridge spanning
>> !
>> !
>> ip classless
>> no ip http server
>> !
>> !
>> !
>> !
>> !
>> !
>> !
>> !
>> !
>> !
>> bridge 1 protocol ieee
>> bridge 1 priority 2
>> alias exec ip sh ip route
>> alias exec ipx sh ipx route
>> alias exec int sh ip int brief
>> !
>> line con 0
>> transport input none
>> line aux 0
>> line vty 0 4
>> login
>> !
>> end
>>
>> r9#sh run
>> Building configuration...
>>
>> Current configuration:
>> !
>> version 12.0
>> service timestamps debug uptime
>> service timestamps log uptime
>> no service password-encryption
>> !
>> hostname r9
>> !
>> !
>> ip subnet-zero
>> no ip routing
>> no ip domain-lookup
>> ipx routing 0009.0009.0009
>> bridge irb
>> !
>> !
>> !
>> interface Loopback0
>> ip address 172.168.70.1 255.255.255.0
>> no ip directed-broadcast
>> no ip route-cache
>> ipx network 701
>> !
>> interface Serial0
>> no ip address
>> no ip directed-broadcast
>> no ip route-cache
>> no ip mroute-cache
>> shutdown
>> no fair-queue
>> !
>> interface Serial1
>> no ip address
>> no ip directed-broadcast
>> no ip route-cache
>> shutdown
>> !
>> interface TokenRing0
>> mtu 1500
>> ip address 172.16.70.9 255.255.255.0
>> no ip directed-broadcast
>> no ip route-cache
>> ring-speed 16
>> multiring all
>> !
>> ip classless
>> !
>> !
>> !
>> !
>> alias exec ip sh ip route
>> alias exec ipx sh ipx route
>> alias exec int sh ip int brief
>> !
>> line con 0
>> transport input none
>> line aux 0
>> line vty 0 4
>> !
>> end
>>
>> VTP VLAN Configuration
>>
>> TrBRF/TrCRF ID Brdg/Rng
>>Ports Local
>> State
>> r4r9 49 0x01
>>
>> preferred
>> r4 4 0x04
>>yes
>> preferred
>> r9 9 0x09
>>yes
>> preferred
>> Vlan1 100 0x0F
>>
>> preferred
>> Vlan1.1 101 auto
>>yes
>> preferred
>> Vlan2 200 0x0F
>>
>> preferred
>> Vlan2.2 201 auto
>>yes
>> preferred
>> Vlan3 300 0x0F
>>
>> preferred
>> Vlan3.1 301 auto
>>yes
>> preferred
>> trbrf-default 1005 0x0F
>>
>> preferred
>> trcrf-default 1003 auto
>>no
>> preferred
>>
>> Local VLAN Port Configuration
>>
>> Port Mode TrCRF TrBRF
>> 1 Static r4 r4r9
>> 2 Static r9 r4r9
>> 3 Static Vlan1.1 Vlan1
>> 4 Static Vlan1.1 Vlan1
>> 5 Static Vlan1.1 Vlan1
>> 6 Static Vlan1.1 Vlan1
>> 7 Static Vlan1.1 Vlan1
>> 8 Static Vlan1.1 Vlan1
>> 13 Static Vlan2.2 Vlan2
>> 14 Static Vlan2.2 Vlan2
>> 15 Static Vlan2.2 Vlan2
>> 16 Static Vlan2.2 Vlan2
>> 17 Static Vlan3.1 Vlan3
>> 18 Static Vlan3.1 Vlan3
>> 19 Static Vlan3.1 Vlan3
>>
>> Return More Change
>>
>>
>> Thanks in advance everyone.
>>
>> >>>Brian
>>
>>
>>
>>
>>
>>
>>
>>
>>
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:20 GMT-3