RE: IRB issues from lab 8

From: perkinsr@xxxxxxxxxxxxxx
Date: Mon Oct 15 2001 - 17:44:46 GMT-3


   
When debuging durring that ping, I get nothing. I wish I could debug
bridged packets.

'Bridge 1 route ipx' is in the config, I must have snipped it out or tried
it after that message went out. I am bridging and routing now. R1 is now a
layer 3 switch for IPX.

I haven't found much, but your not shows that serial links use ethernet
addressing "Note that when a bridged packet traverses a serial link, it has
an Ethernet-style address."

I have pretty much decided that bridging serial and token is a bad idea. I
test Thursday and am going to just hope it doesn't come up. I don't have
time to fight with this anymore. I got IRB working as advertised on the two
routers with serial links and am aware there are issues with token to serial
bridging.

Thinking about this, I have always seen bridging over WAN examples with
ethernet, never token ring. To bridge token over a WAN you would simply
RSRB, I guess your WAN is a bad spot to bridge token and ether segements,
unless you want to use dlsw I suppose. There are many options here, I just
picked one that won't fly, at least not without a lot of work.

Ray

-----Original Message-----
From: Brian Lodwick [mailto:xpranax@hotmail.com]
Sent: Monday, October 15, 2001 1:33 PM
To: perkinsr@WellsFargo.COM
Cc: ccielab@groupstudy.com
Subject: RE: IRB issues from lab 8

If you debug ipx packet on R5 and ping for R7 what do you get?
I still believe there is a canonical to non-canonical issue.
I see you added ipx routing to the config, but by adding IRB and not adding
bridge 1 route ipx you are still bridging ipx - correct?
Also you mentioned the serial link will act like an Ethernet (MAC-canonical)

This is the only thing I could find that said anything about it.

Note MAC addresses on Ethernets are "bit swapped" when compared with MAC
addresses on Token Ring and FDDI. For example, address 0110.2222.3333 on
Ethernet is 8008.4444.CCCC on Token Ring and FDDI. Access lists always use
the canonical Ethernet representation. When using different media and
building access lists to filter on MAC addresses, keep this point in mind.
Note that when a bridged packet traverses a serial link, it has an
Ethernet-style address.

If you read in Bruce Caslow's Volume 2 book on SRT (pg. 633)it says
"Source-route Transparent Bridging allows a bridge to perform both
source-route bridging and transparent bridging for Token-Ring networks."

Then later in the paragraph he says "SRT is transparent bridging for all
Token-Ring networks. Do not confuse SRT with source-route translational
bridging (SR/TLB). SR/TLB involves bridging between Token-Ring and Ethernet

segments and is covered in the next section."

Have you found something saying a serial link MAC address is read in
canonical format?

>>>Brian

>From: perkinsr@WellsFargo.COM
>To: xpranax@hotmail.com
>CC: ccielab@groupstudy.com
>Subject: RE: IRB issues from lab 8
>Date: Mon, 15 Oct 2001 12:49:48 -0700
>
>Now I have put IRB on R1 so I can test in the middle. Now, Routes are in
>all 3 routers, R1 can ping R7 and R5, but R5 cannot ping through to R7. I
>would guess this has to be an addressing issue. I don't now what else it
>could be.
>
>Any ideas?
>
>
> BVI1 BVI1
> | |
>-----R5----------------------R1----------------------R7--t5/3
> s0 s1 to0 t5/0
>
>R1
>ipx routing 0000.0000.0001
>ipx internal-network 1
>!
> interface Serial0
> ip address 137.20.25.2 255.255.255.0
> no ip route-cache
> no ip mroute-cache
> clockrate 64000
> bridge-group 1
>!
>interface TokenRing0
> ip address 137.20.10.1 255.255.255.0
> no ip route-cache
> no ip mroute-cache
> ring-speed 16
> bridge-group 1
>!
>interface BVI1
> no ip address
> ipx encapsulation SAP
> ipx network 700
>!
>bridge irb
>bridge 1 protocol ieee
> bridge 1 route ip
>
>
>R5
>ipx routing 0000.0000.0005
>!
>interface Serial1
> ip address 137.20.25.1 255.255.255.0
> no ip directed-broadcast
> ip accounting output-packets
> no logging event subif-link-status
> bridge-group 1
>!
>interface BVI1
> no ip address
> no logging event subif-link-status
> ipx encapsulation SAP
> ipx network 700
> no ipx route-cache
>!
>ipx router eigrp 10
> network 5130
> network 5004
> network 695
>!
>ipx router rip
> no network 5130
> no network 5004
> no network 695
>!
>bridge irb
>bridge 1 protocol ieee
> bridge 1 route ip
> bridge 1 route ipx
> no bridge 1 bridge ip
>
>
>R1
>ipx routing 0000.0000.0007
>!
>interface TokenRing5/0
> mac-address 0000.0000.00ff
> ip address 5.5.5.5 255.255.255.0 secondary
> ip address 137.20.10.70 255.255.255.0
> ipx network 700
> no ipx route-cache
> ring-speed 16
>!
>interface TokenRing5/3
> mac-address 0000.0000.00ff
> ip address 172.168.70.1 255.255.255.0
> ipx network 701
> no ipx route-cache
> ring-speed 16
>!
>
>
>
>
>
>-----Original Message-----
>From: Brian Lodwick [mailto:xpranax@hotmail.com]
>Sent: Monday, October 15, 2001 11:00 AM
>To: perkinsr@WellsFargo.COM
>Cc: ccielab@groupstudy.com
>Subject: RE: IRB issues from lab 8
>
>
>It would be logical that RIP updates would work and not pings if SR/TLB was
>not configured. I know you can transparently bridge Token-Ring frames, but
>you cannot just Trnasparently bridge Ethernet frames into Token-Ring. You
>must translate. SRT is only for going from Token-Ring to Token-Ring.
>
> >>>Brian
>
>
> >From: perkinsr@WellsFargo.COM
> >To: xpranax@hotmail.com
> >CC: ccielab@groupstudy.com
> >Subject: RE: IRB issues from lab 8
> >Date: Mon, 15 Oct 2001 10:55:55 -0700
> >
> >These are good points, but my impressin was that Because I have not
> >configured SRB on the token interface and have configured a bridge group
>I
> >should be doing transparent bridging over the token interface. The MTU
> >could be an issue but I don't think it would affect my 100 byte pings. I
> >am
> >bridiging from Serial to token, but those are still valid issues. I just
> >don't see why this isn't working. Especially when it sort of works, RIP
> >broadcasts are getting through and the route tables are full.
> >
> >To be clear I am routing IP and bridging IPX on R1.
> >
> >Thanks for your input,
> >Ray
> >
> >
> >-----Original Message-----
> >From: Brian Lodwick [mailto:xpranax@hotmail.com]
> >Sent: Monday, October 15, 2001 10:49 AM
> >To: perkinsr@WellsFargo.COM
> >Cc: ccielab@groupstudy.com
> >Subject: Re: IRB issues from lab 8
> >
> >
> >I'm sorry looks like I jumped a little too fast there. I guess I
>should've
> >made sure you trying to bridge IPX from r5 to r7?
> >If yes, my response should be correct. Also I believe you will run into
>an
> >issue bridging between the Ethernet and Token-Ring networks.
> >Won't you have to configure SR/TLB on r1 since you are trying to bridge
> >from
> >
> >Ethernet to Token-Ring?
> >Also I believe you will want to assure the max MTU all around is 1500 so
> >that you don't get an oversized frame on the Ethernet segment from the
> >Token-Ring segment?
> >
> > >>>Brian
> >
> >
> > >From: perkinsr@WellsFargo.COM
> > >Reply-To: perkinsr@WellsFargo.COM
> > >To: ccielab@groupstudy.com
> > >Subject: IRB issues from lab 8
> > >Date: Mon, 15 Oct 2001 10:21:01 -0700
> > >
> > >I cannot get IRB to work. Here is the IRB scenario from lab 8, the
>only
> > >differance is there is token instead of ether between R1 and R7.
> > >
> > >
> > > BVI1
> > > |
> > >-----R5----------------------R1----------------------R7--t5/3
> > > s0 s1 to0 t5/0
> > >
> > >
> > >
> > >This is tough, I can't ipx ping from R7 to R5, but routing info is
> >passed.
> > >R7 all routes beyond R5, R7 is a stub, but net 701 (off t5/3) is
>visible
> > >from R5. Pings will not work though. I was thinking frame type
> > >concic/non-concical type problems. I tried making the MAC of t5/3
>0.0.ff
> > >so
> > >that it would be the same either way, but that didn't work. The BVI1
>on
> >R5
> > >is set to SAP frame type just like the token interface on R7.
> > >
> > >Help....
> > >
> > >
> > >
> > >configs:
> > >R5
> > >ipx routing 0000.0000.0005
> > >!
> > >interface Serial1
> > > ip address 137.20.25.1 255.255.255.0
> > > no ip directed-broadcast
> > > ip accounting output-packets
> > > no logging event subif-link-status
> > > bridge-group 1
> > >!
> > >interface BVI1
> > > no ip address
> > > no logging event subif-link-status
> > > ipx encapsulation SAP
> > > ipx network 700
> > >!
> > >ipx router eigrp 10
> > > network 5130
> > > network 5004
> > > network 695
> > >!
> > >!
> > >ipx router rip
> > > no network 5130
> > > no network 5004
> > > no network 695
> > >!
> > >bridge irb
> > >bridge 1 protocol ieee
> > > bridge 1 route ip
> > > bridge 1 route ipx
> > > no bridge 1 bridge ip
> > >
> > >R1
> > >!
> > >interface Serial0
> > > ip address 137.20.25.2 255.255.255.0
> > > no ip route-cache
> > > no ip mroute-cache
> > > clockrate 64000
> > > bridge-group 1
> > >!
> > >interface TokenRing0
> > > ip address 137.20.10.1 255.255.255.0
> > > no ip route-cache
> > > no ip mroute-cache
> > > ring-speed 16
> > > bridge-group 1
> > >!
> > >bridge 1 protocol ieee
> > >
> > >R7
> > >ipx routing 0000.0000.0007
> > >!
> > >interface TokenRing5/0
> > > ip address 5.5.5.5 255.255.255.0 secondary
> > > ip address 137.20.10.70 255.255.255.0
> > > ipx network 700
> > > ring-speed 16
> > >!
> > >interface TokenRing5/3
> > > ip address 172.168.70.1 255.255.255.0
> > > ipx network 701
> > > ring-speed 16



This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:19 GMT-3