Do you have split horizon enabled on the spoke router? If so, EIGRP will not send any route updates out an interface where it learned a route from. OSPF is a link state protocol and has no concept of split horizon.
To verify the status of split horizon, do a 'show ip int s0.3' and that will tell you if it is enabled. If it is, in your config you need to add 'no ip split-horizon'. Be aware that this sort of thing can cause routing problems depending on your topology. Judicious use of distribute lists might be helpful. HTH, John >>> "Cisco Nuts" 1/11/02 11:50:02 AM >>> Hello John, How about this one? OSPF always takes precedence over EIGRP in a multipoint FR config!!! I have a subif s0.3 configed as multipoint on the hub router with the 2 spokes using the physical interfaces. All 3 routers are running EIGRP and OSPF. But I only seee OSPF routes on the hub router. And also to add to this mess, the hub router is not sending routing updates to either of the spoke routers. Ever experienced such a thing?? Please advise. Thank you. >From: "John Neiberger" >Reply-To: "John Neiberger" >To: [EMAIL PROTECTED] >Subject: OSPF and The Disappearing Neighbor Statement [7:31656] >Date: Fri, 11 Jan 2002 13:17:23 -0500 > >It was hot, too hot. Our detective had been working feverishly to >configure OSPF over NBMA without the use of ip ospf network statements. >He knew that to do this he must explicitly add neighbor statements or >adjacencies would not form. > >He logs into the hub router and types in his three neighbor statements. > All seems well. It's still too hot, but it's a dry heat. > >He now logs into one of the spoke routers and types in his neighbor >statement. He pauses momentarily and then checks the OSPF adjacencies. >Something seems to be wrong, he thinks to himself. This ought to be >working, but it isn't. Why not? He looks through the running config to >look for any errors and notices the the neighbor statement that he just >entered is missing! > >He slowly and deliberately types it in again making sure there are no >mistakes but yet it still does not show up in the running configuration. > Is this an IOS issue? Operator error? Some rift in the space-time >continuum? > >He jumps to another spoke router running a different IOS and tries the >same thing with the same result. He is frantic now, beads of sweat >pouring down his face. What if this were the real CCIE lab exam? Could >this be a fatal stumbling block? > >He finally notices that adjacencies do eventually form after clearing >the relevant interfaces. This must be because the hub router accepted >the neighbor statements. But what if it hadn't, he ponders. He thinks >forward into the future when--a day after taking the lab exam--he >receives the dreaded email that says, "We're sorry, it is apparent that >you have no clue." > >Back to the real world.... > >What was the cause of the missing neighbor statements? Have any of you >run into this before? I've never bothered to explicitly use neighbor >statements as I'm in the habit of using the ip ospf network command to >make them unnecessary. > >Any thoughts? > >Thanks, >John _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=31662&t=31656 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
