The hello intervals on any given link must match, but the intervals on the ethernet side have nothing to do with the intervals on the FR side. Also, if the network type point-to-point is used, no DR election occurs but the timers must still match or an adjacency will not form.
In Priscilla's scenario, she said that adjacencies were forming but the routes were not showing up in the routing table. This doesn't sound like a timer issue. Since she mentioned that there were virtual links involved, I'm guessing that something happened that broke them and that issue needs to be resolved. If the router in area 2--on the other side of the VL--does not have anything in its OSPF database then this is most likely a VL problem. If that is resolved and the routes are still not in the table, then we need to see if the LSAs have at least made it into the database. That should lead us to the source of the problem. John >>> "Walter Rogowski" 2/4/02 4:23:40 PM >>> If you debug ospf adjacencies you might see complaints re mismatched hello intervals. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Baker, Jason Sent: 04 February 2002 22:51 To: [EMAIL PROTECTED] Subject: RE: OSPF DR problem [7:34379] hmmm in ospf NBMA network i thought when you specified point to point there was no DR, BDR election. so maybe playing with the priorities may have caused problems > -----Original Message----- > From: Kane, Christopher A. [SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, 5 February 2002 9:36 am > To: [EMAIL PROTECTED] > Subject: RE: OSPF DR problem [7:34379] > > Priscilla, > > Now that you have R1 as the DR, it's his responsibility to announce > that network out to everyone else. Is R1 sending out LSAs (Network > LSA, type 2) to wherever it is that you are trying to see that > network? (Is it R3's routing table that you can't see the Ethernet > segment of R1 and R2?) Does the network show up in the OSPF database > but not the routing table? Or just the routing table? > > Chris > > -----Original Message----- > From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 4:31 PM > To: [EMAIL PROTECTED] > Subject: OSPF DR problem [7:34379] > > > Hi Group Study, > > Playing with IP OSPF priority to influence which router became the > Designated Router (DR) caused routing problems for me in a recent bout > with a lab exercise. Can anyone help me understand if I did something > wrong? > > I have 2 routers on an Ethernet LAN. Both of them also have WAN > connections to remote sites. R1 has a Frame Relay link to the > corporate "cloud" via its > S0 port. S0 is configured as "ip ospf network point-to-point." > > R2 has an ISDN link to yet another router, R3. This link is configured > as an OSPF point-to-point demand circuit. > > R1 and R2 are connected via an Ethernet switch. My goal was to make > sure R1 became the DR on Ethernet. Both routers have loopbacks, but > R2's is higher, > so to make sure R2 did not become the DR, I configured it with: > > ip ospf priority 0 > > R1 then did indeed become the DR on the Ethernet LAN because it was > using the default priority 1. > > Now, finally to the question...... On the other side of the ISDN and > across the Frame Relay cloud, I couldn't see the Ethernet LAN in the > routing table. Routers formed adjacencies correctly and could reach > most networks, > > but not that darn Ethernet LAN. R1 and R2 on the Ethernet LAN formed > an adjacency and could see the rest of the internetwork. > > Could I have broken something by playing with the priority?? > > Thanks for your help. > > Priscilla > > > > ________________________ > > Priscilla Oppenheimer > http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34404&t=34379 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
