Thus spake Mike McHenry
This exact problem has happened to me several times and it was NOT caused by the ARC deciding to become the DR. I have a small network of about 13 Lucent portmasters, 3 USR TC chassis, one Cisco 4500 and one Cisco 4700 router. ALL of the termservers are set with OSPF priority 0, meaning they will never become a DR or BDR. The Cisco 4500 and 4700 OSPF priorities were left as-is leaving one to become the DR and the other to become the BDR.
If I rebooted or otherwise disturbed the DR the USR TC chassis would lose all their OSPF routing. The Lucent equipment did not have a problem at all. Getting the OSPF back on the USRs required a reboot of every chassis. For now I have set one of the Ciscos to priority 0 so that it will never become a BDR or DR. It seems as though the HARC cards have a problem recognizing a change of a BDR to a DR while the rest of my equipment does not.
If this problem is indeed being caused by an ARC deciding to become a DR then it would seem to be a bug. In my case this should not be happening as all the HARCs are set to NOT participate in DR/BDR elections.
Sounds like you've played with it considerably more than myself at least, I'll defer to your experience with this code. I had just played with it enough to know that it puked mightily when something happened to the DR...I hadn't played enough to know specifically what caused it. Sounds like you've dug into it far enough that you know more specifics. -- 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.