Since the spoke routers are NBMA, multicast hello's will not locate the neighbor. The ospf router neighbor command must be used to manually identify the neighbor so routing updates can be exchanged. I'm not sure why you would want to implement in this way, but it will work.
Regards ""The Long and Winding Road"" wrote in message news:[EMAIL PROTECTED] > Ran into something in Parkhurst's OSPF book while studying tonight. Looking > for validation of my observation. > > The example: OSPF over frame relay > > The topology: hub and spoke, with a twist. The hub uses subinterfaces ( one > to each spoke router ) and the spokes use physical interfaces. > > Now, the Parkhurst examples show leaving the physical interfaces as ospf > type non-broadcast, change the ospf timers on the subinterfaces, place > neighbor statements on the spoke routers ( physical interfaces ) and all is > well. > > Except I don't believe it works this way. > > The subinterfaces are point-to-point networks, and expect the other side to > be a point-to-point connection and adjacency. the physical interfaces are > non-broadcast, and expect DR elections to occur, something the router with > the subinterfaces will not do. > > I believe the correct solution is to make the physical interfaces ospf type > point-to-multipoint. > > An alternative is to change the physical interfaces to ospf point-to-point. > > In any case - can anyone else verify what I see and do not see - that > Parkhurst chapter 11, example 3, pages 275-279 answer is incomplete? > > thanks. > > -- > TANSTAAFL > "there ain't no such thing as a free lunch" Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=65560&t=65532 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
