Don't know if the picture will go through... But I'll try.

From: Edwards, Andrew M (andrew.m.edwards@boeing.com)
Date: Mon Apr 05 2004 - 13:09:05 GMT-3


I need some help with this scenario...

Basically there is OSPF and EIGRP overlapping each other across the
frame relay cloud... OSPF on R2,1,3. EIGRP on R1,3,4. Overlap
OSPF/EIGRP on R1 and R3.

The problem I had before I even got to redistribution is as follows.....
 <<picture.doc>>

OSPF restrictions:

R2 must be physical, R1 must be multipoint, R3 must be POINT to POINT.
R2 is BDR, R1 is DR, and R3 never be BDR/DR

EIGRP restrictions:

The usual split horizon issue at the spoke...

Problem... configured eigrp fine, sall all routes for eigrp on R4, R3,
and R1.

Configured OSPF area correctly. Set interface priorities, ip ospf
network types, and changed hello interval on R3 to match up with OSPF
adjacent routers timers. Show ip ospf neighbor shows both adjacencies
from R1. R2 see's R1 adjacent, and R3 sees R3 adjacent.

Here is where I had the problem that I don't understand....

On R1 I had all OSPF routes and eigrp routes in database / topology, as
well as in main routing table. E.g. show ip route for eigrp routes
gives me all advertised EIGRP routes, similar for OSPF.

Go to R3 though and here is what I had... All EIGRP routes were in
topology table as well as in the routing table. There were only a few
so it was easy to verify. Now on to the problem. Show ip ospf database
shows all OSPF routes/routers, type3/5, tagged routes, etc. in the
database. But, do a show ip for any OSPF learned routes and they were
not in the main routing table. I had not yet redistributed any
routes.... And it wasn't an AD issue because none of the routes from the
OSPF area were there as EIGRP routes either... they just werent'
there...

Someone pleas tell me this was faulty equipment 8) or else help me
pull my head out of my.. Well, you know.

Thanks,

andy

[GroupStudy removed an attachment of type application/msword which had a name of picture.doc]



This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:42 GMT-3