From: Oliver Boehmer (oboehmer@xxxxxxxxx)
Date: Wed Jul 10 2002 - 12:01:46 GMT-3
Hi,
never tried this myself, but you have two issues in this environment:
- Multicast address issue
- MTU difference
OSPF will not form an adjacency if MTU is different. You can turn off the
check with the interface command "ip ospf mtu-ignore", or you can lower the
"ip mtu" on the TR.. I think the latter is better, because even if you
disable the MTU check, large DBD packets sent from the TR side can't be
handled by the ethernet..
I heard that this setup works when using "ip ospf network non-broadcast"
and statically define the neighbors.. Should be an acceptable solution..
How far do you make it in the OSPF neighbor state? You might want to check
http://www.cisco.com/warp/public/104/12.html
oli
At 07:25 10.07.2002 -0700, perkinsr@WellsFargo.COM wrote:
>I am working on lab 5 in my make-shift lab. Most of my routers have token
>ring, but a few are ethernet, to overcome this obsticle I have all the token
>interfaces connected to a 7500 (R7) and all the ethernet interfaces
>connected to a 2924 (SW0). The 7500 also has connections to the 2924. In
>order to get the topology I need I am using the 7500 to bridge between token
>and ethernet. I have that much working, I can ping from the ethernet to the
>token interface, but I can't get OSPF to come adjacent. I suspect there is
>an issue with translating multicast traffic from token to ether. Does
>anyone know what might be the problem?
>
>
>
>R2-----O-----R7-------SW0-------R5
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:25 GMT-3