From: crl (cisco@xxxxxxxxxxxx)
Date: Sat Apr 28 2001 - 17:37:33 GMT-3
Did a debug ip packet. RIP2 was sending multicasts for sure. Did a debug
eigrp packet. The HELLOs are getting across in one direction only:
HELLOs from R1 to R2:
Apr 28 16:31:03.227 EDT: EIGRP: Sending HELLO on TokenRing0
Apr 28 16:31:03.231 EDT: AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely
0/0
Apr 28 16:31:03.229 EDT: EIGRP: Received HELLO on Ethernet0 nbr 1.1.1.1
Apr 28 16:31:03.233 EDT: AS 1, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely
0/0 peerQ un/rely 0/1
but when R2 sends HELLOs, they never come across to the other end. Then,
because R2 had sent a HELLO, it then sends an UPDATE. The UPDATE (strangely
enough) makes it across:
UPDATEs from R2 to R1:
Apr 28 16:31:04.625 EDT: EIGRP: Sending UPDATE on Ethernet0 nbr 1.1.1.1,
retry 7, RTO 5000
Apr 28 16:31:04.629 EDT: AS 1, Flags 0x1, Seq 14/0 idbQ 0/0 iidbQ un/rely
0/0 peerQ un/rely 0/1 serno 1-2
Apr 28 16:31:04.631 EDT: EIGRP: Received UPDATE on TokenRing0 nbr 1.1.1.2
Apr 28 16:31:04.635 EDT: AS 1, Flags 0x1, Seq 14/0 idbQ 0/0
Apr 28 16:31:04.639 EDT: EIGRP: Neighbor not yet found
Because R1 gets this UPDATE, but never heard the HELLO, it compalins about
it in the last message above.
So it seems the HELLO doesn't make it accross from the Ethernet TO the Token
Ring, but it works the other way around. Explains why the output of the
EIGRP neighbor table has the neighbor at one end but not the other...
----- Original Message -----
From: "Johnny Dedon" <johnny.dedon@exodus.net>
To: "crl" <cisco@crl.fdns.net>
Sent: Saturday, April 28, 2001 3:50 PM
Subject: Re: Transparent Bridging between TR and Ethernet (Conclusion)
> Crl
> Have you done a debug eigrp packets and rip packets?
> I would be curious to see if rip is not sending broadcast packets accross.
>
> Johnny Dedon
> Senior Staff Consultant
> Exodus Professional Services
> johnny.dedon@exodus.net
> www.exodus.net
> ----- Original Message -----
> From: "crl" <cisco@crl.fdns.net>
> To: "Groupstudy" <ccielab@groupstudy.com>
> Sent: Saturday, April 28, 2001 2:30 PM
> Subject: Re: Transparent Bridging between TR and Ethernet (Conclusion)
>
>
> > Very simple test scenario:
> >
> > r1---eth---r2---tok---r3
> >
> > r2 has IP routing disabled. It is strictly doing transparent bridging.
His
> > relevant config is as follows:
> >
> > no ip routing
> > !
> > interface Ethernet0
> > bridge-group 1
> > !
> > interface TokenRing0
> > bridge-group 1
> > !
> > bridge 1 protocol ieee
> > bridge 1 bitswap_layer3_addresses
> >
> >
> > Now - r1 and r3 are addressed on the same subnet. They each have a
> loopback
> > as well. They can ping and telnet to each other through the transparent
> > bridge. When RIP is enabled, they each learn a route for each other's
> > loopback. When EIGRP is enabled, they cannot establish an adjacency.
> >
> > Conclusion is that the bitswap_layer3_addresses kludge does not work
with
> > EIGRP and OSPF.
> >
> > Now - the fun part? Theories why? I thought multicast was the issue, but
> > RIP2 is multicast and works properly...
> >
> > ----- Original Message -----
> > From: "crl" <cisco@crl.fdns.net>
> > To: "Groupstudy" <ccielab@groupstudy.com>
> > Sent: Friday, April 27, 2001 12:13 PM
> > Subject: Translational Bridging between Token Ring and Ethernet, IRB,
and
> > Various Routing Protocols
> >
> >
> > > Doing some experiments. Topology is:
> > >
> > > r4---token-ring---r3---ethernet---r2
> > >
> > > On r3, I'm doing SR/TLB and IRB. The Token Ring and Ethernet are a
> common,
> > > bridged subnet, and r3 has other interfaces that are routed (serials)
> but
> > I
> > > don't think they're relvant to this discussion.
> > >
> > > Experimenting with various routing protocols on this network segment.
I
> > > found that RIP1, RIP2, and IGRP work well in this situation. OSPF and
> > EIGRP
> > > do not establish adjacencies. I have the bitswap-layer3-addresses
> command
> > in
> > > place to allow ping, telnet etc to work well between all three
routers.
> > >
> > > Take OSPF for example.
> > > r4#sh ip ospf nei
> > > <no output>
> > >
> > > r3#sh ip ospf nei
> > > Neighbor ID Pri State Dead Time Address
> > Interface
> > > 197.7.77.1 1 INIT/DROTHER 00:00:35 197.7.8.4 BVI1
> > > 197.7.8.10 1 FULL/DR 00:00:33 197.7.8.10 BVI1
> > >
> > > r2#sh ip ospf nei
> > > Neighbor ID Pri State Dead Time Address
> > Interface
> > > 197.7.77.1 1 INIT/DROTHER 00:00:39 197.7.8.4
> > Ethernet0
> > > 197.7.8.3 1 FULL/BDR 00:00:31 197.7.8.3
> > Ethernet0
> > >
> > > Doesn't seem to make much sense. I suspected it was a multicast issue,
> but
> > > RIP2 works well. It's not an MTU problem, I checked that out -
> everything
> > is
> > > set to 1500. I suspect the bitswap-layer3 command might be mangling
> EIGRP
> > > and/or OSPF, but not RIP and IGRP.
> > >
> > > Here's the relevant configs. I'd just like to know if this is
impossible
> > > (great!) or if I'm missing something (doh!):
> > >
> > >
> > > r4#sh run
> > > !
> > > interface Loopback0
> > > ip address 197.7.77.1 255.255.255.0
> > > no ip directed-broadcast
> > > !
> > > interface TokenRing0
> > > mtu 1500
> > > ip address 197.7.6.4 255.255.255.0 secondary
> > > ip address 197.7.8.4 255.255.255.0
> > > no ip directed-broadcast
> > > ip nat outside
> > > ring-speed 16
> > > !
> > > router ospf 1
> > > network 197.7.0.0 0.0.255.255 area 0
> > >
> > > -------------------------------------------
> > >
> > > r3#sh run
> > > !
> > > bridge irb
> > > !
> > > interface Ethernet0
> > > no ip address
> > > no ip directed-broadcast
> > > bridge-group 1
> > > !
> > > interface Serial1
> > > ip address 197.7.7.3 255.255.255.0
> > > no ip directed-broadcast
> > > !
> > > interface TokenRing0
> > > mtu 1500
> > > no ip address
> > > no ip directed-broadcast
> > > ring-speed 16
> > > bridge-group 1
> > > !
> > > interface BVI1
> > > ip address 197.7.8.3 255.255.255.0
> > > no ip directed-broadcast
> > > !
> > > router ospf 1
> > > network 197.7.0.0 0.0.255.255 area 0
> > > !
> > > bridge 1 protocol ieee
> > > bridge 1 bitswap-layer3-addresses
> > > bridge 1 route ip
> > >
> > > -------------------------------------------
> > >
> > > r2#sh run
> > > !
> > > interface Ethernet0
> > > ip address 197.7.8.10 255.255.255.0
> > > !
> > > !
> > > router ospf 1
> > > network 197.7.0.0 0.0.255.255 area 0
> > > **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:00 GMT-3