Definitely! The biggest gotcha is if the router ID changed on either router that has virtual links configured. The configs will have to be changed to reflect the new router IDs or the virtual link won't work. If it's a virtual link problem, though, at the console (or by using term mon) or R1 you should see some virtual-link-related errors every few seconds. You can also use "show ip ospf virt" to help troubleshoot that particular issue.
That's my official guess. Somewhere the VL is broken and it's probably due to a change in router ID. Let me know if that's not the problem and I'll put the thinking cap back on! John >>> "Priscilla Oppenheimer" 2/4/02 3:30:18 PM >>> There was a virtual link. The virtual link was from R1 over to another router across the Frame Relay cloud. R1 is an ABR connecting Area 0 and Area 1. Area 0 is the Ethernet LAN. Area 1 is the Frame Relay cloud. For some unknown reason, there's an Area 2 also on the other side of Area 1. Does that ring a bell regarding any gotchas?? Thanks Priscilla At 03:03 PM 2/4/02, John Neiberger wrote: >Priscilla, > >I can't think of anything that could have been broken by using the ip >ospf priority command. Unless you've run into some sort of bug I'm >guessing that there must be another issue. Were you playing around with >the loopback addresses? Do you have any virtual links configured? >I'm just wondering if you configured something that depended on a static >router ID and by adding or changing a loopback you've confused one or >two of the other routers. > >You mentioned that the frame relay interface is configured as >point-to-point. Is the opposite side configured the same way? It must >be since you said the adjacencies are forming...nevermind. Hmm... > >Are the missing routes in the OSPF database, just not in the routing >table? If so, check out this link: > >http://www.cisco.com/warp/public/104/26.html > >I can't think of any one thing that describes this issue but I'll keep >pondering... > >John > > >>> "Priscilla Oppenheimer" 2/4/02 2:30:35 PM > >>> >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 ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=34398&t=34379 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
