Thus spake Mike Wronski
|Mike Andrews writes... |>I've been having a really bizarre problem off and on the last week or two. |>Occasionally some of my ARCs will suddenly stop doing OSPF right. The |>routing table loses all OSPF routes, and the ARC stops announcing its |>routes via OSPF to our Ciscos. Disabling/enabling OSPF doesn't help, but |>most of the time (not all the time) rebooting the ARC will.
|>One thing that seemed to trigger it was rebooting some of our Ciscos... |>and since that happens so infrequently (not rebooted since going to ARC |>4.2 in fact) it's hard to track down. I don't know which one exactly, |>maybe our AS border router dying is what threw it off.
|>Has anyone seen anything like this before or know of any particular |>settings that I might want to check? This is driving me nuts (not to |>mention my customers) and I'm not sure where to start.
|Make sure your tc's aren't becoming the DR. To check, do a "list ospf nei", |see if any of them are in any state other than "two way". To fix, do a |"set ospf interface THE_OSPF_INTERFACE router_priority 0" on each of |them and reboot.
That recomendation is actually in the release notes for 4.2.32...
There are problems with the DR/BDR code in 4.2.x then? Hrmm...could suck if you don't have 2 other OSPF speakers on a subnet...if they reboot, then the Arc would become DR, and when they come back up, they won't take over from it. :/ Would require a reboot of possibly two Arcs for get the DR to be something other than an Arc in that situation. :/ -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.