From: Guy Farber (gfarber@xxxxxxxxx)
Date: Mon Apr 30 2001 - 06:00:52 GMT-3
I practically gave up on it now... SR/TLB does work with SNA, it just
doesn't bridge ip even with multiring and layer 3 bitswapping. I don't think
it's that important for the lab. I'll know in 2 months...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Pat Bodin
Sent: Sun, April 29, 2001 2:25 PM
To: Mas Kato; gfarber@cisco.com
Cc: ccielab@groupstudy.com
Subject: RE: Bridging IP over SR/TLB
Yes. I do it.
The issue is that this is SRB functionality. SRB include RIFs. If you cut
off the RIFs it won't work. Therefore, anywhere you can bridge using SRB
(limited by RIF count) will allow SNA/IP/etc activity.
Pat
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Mas Kato
Sent: Sunday, April 29, 2001 3:02 PM
To: 'Pat Bodin'; gfarber@cisco.com
Cc: ccielab@groupstudy.com
Subject: RE: Bridging IP over SR/TLB
Interesting... So 'multiring ip' did indeed break the SNA pings?
Supposedly, 'multiring' without any parameters will allow the routing of
layer-3-routable packets only to nodes directly connected to the local
token ring... Do you think if the SR/TLB were more than one ring away in
your scenario it would still be possible to pass both SNA and IP pings?
Mas
-----Original Message-----
From: Pat Bodin [mailto:pbodin@cisco.com]
Sent: Saturday, April 28, 2001 9:11 AM
To: Mas Kato; gfarber@cisco.com
Cc: ccielab@groupstudy.com
Subject: RE: Bridging IP over SR/TLB
You can use the multiring token ring interface command without the ip
setting and it won't break your sna pings. Plus, you will get your ip
pings. Multiring generates rifs and w/o rifs the bridge (srb) doesn't
know
where to send the traffic. This would be different if the bridge was
transparent.
Pat
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Mas Kato
Sent: Saturday, April 28, 2001 8:37 PM
To: gfarber@cisco.com
Cc: ccielab@groupstudy.com
Subject: RE: Bridging IP over SR/TLB
Yeah--the current EIGRP-related thread sounds interesting--but to get
the IP pings across, try 'bitswap-layer3-addresses' in R8's transparent
bridge and moving 'multiring ip' from R8's to0/0 to R2's to0/0... Hope
it doesn't break your SNA pings <g>.
Regards,
Mas Kato
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
crl
Sent: Saturday, April 28, 2001 11:30 AM
To: Groupstudy
Subject: Re: Bridging IP over SR/TLB
Check out the bitswap-layer3-addresses command... (although in practice
I
find it doesn't work with _all_ types of IP traffic)
----- Original Message -----
From: "Guy Farber" <gfarber@cisco.com>
To: <ccielab@groupstudy.com>
Sent: Saturday, April 28, 2001 8:45 AM
Subject: Bridging IP over SR/TLB
> Hi,
>
> I'm trying to bridge ip over the following network:
>
> R2 - (TR 411) - R8 - (Ethernet) - R7 - (Ethernet) - R3
>
> R7 is bridging IP and works ok (I can ping from R3 to R8). R8 runs
SR/TLB
> and that works fine as well (I can sna ping from R2 to R3). What I can
seem
> to get is an ip ping form R2 to R3.
>
> What am I missing?
>
> R2:
>
> version 12.1
>
> service timestamps debug uptime
>
> service timestamps log uptime
>
> no service password-encryption
>
> !
>
> hostname R2
>
> !
>
> ip subnet-zero
>
> no ip finger
>
> no ip domain-lookup
>
> !
>
> cns event-service server
>
> !
>
> interface TokenRing0/0
>
> mac-address 4000.0000.0002
>
> ip address 161.22.2.5 255.255.255.0
>
> ring-speed 16
>
> !
>
> snasw cpname NETA.R2
>
> snasw port R2TK0 TokenRing0/0 conntype nohpr
>
> snasw link R3E0 port R2TK0 rmac 0200.0000.00c0
>
>
> R3:
>
> version 12.0
>
> service timestamps debug uptime
>
> service timestamps log uptime
>
> no service password-encryption
>
> !
>
> hostname R8
>
> !
>
> ip subnet-zero
>
> no ip routing
>
> no ip domain-lookup
>
> !
>
> source-bridge ring-group 1000
>
> source-bridge transparent 1000 3 1 1
>
> !
>
> interface Ethernet0/0
>
> ip address 161.22.2.4 255.255.255.0
>
> no ip directed-broadcast
>
> no ip route-cache
>
> bridge-group 1
>
> !
>
> interface TokenRing0/0
>
> no ip address
>
> no ip directed-broadcast
>
> no ip route-cache
>
> ring-speed 16
>
> multiring ip
>
> source-bridge 411 1 1000
>
> source-bridge spanning
>
>
> R7:
>
> version 12.0
>
> service timestamps debug uptime
>
> service timestamps log uptime
>
> no service password-encryption
>
> !
>
> hostname R7
>
> !
>
> !
>
> ip subnet-zero
>
> no ip routing
>
> no ip domain-lookup
>
> !
>
> interface Ethernet0/0
>
> no ip address
>
> no ip directed-broadcast
>
> no ip route-cache
>
> bridge-group 1
>
> !
>
> interface Ethernet0/1
>
> no ip address
>
> no ip directed-broadcast
>
> no ip route-cache
>
> bridge-group 1
>
> !
>
> R3:
>
> version 12.1
>
> service timestamps debug uptime
>
> service timestamps log uptime
>
> no service password-encryption
>
> !
>
> hostname R3
>
> !
>
> memory-size iomem 10
>
> ip subnet-zero
>
> no ip domain-lookup
>
> !
>
> cns event-service server
>
> !
>
> interface Ethernet0/0
>
> mac-address 4000.0000.0003
>
> ip address 161.22.2.1 255.255.255.0
>
> !
>
> snasw cpname NETA.R3
>
> snasw port R3E0 Ethernet0/0 conntype nohpr
>
> Thanks
>
> Guy
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:01 GMT-3