Has anyone encountered a situation where HiPer ARCs will not reestablish an OSPF adjacency with a new Backup Designated Router after a network undergoes a BDR reelection? This weekend I had rebooted 2 ARCs because they were refusing to establish an adjacency with a Cisco 7206 which was the acting BDR until this morning. The reboot fixed the adjacency problem with the Cisco. However, this morning I rebooted the BDR as part of a software update. When that happened one of our Juniper M5s was elected as the new BDR. The BDR reelection was expected. But both HiPer ARCs would not establish an adjacency with the Juniper and went into an Init, ExStart cycle as had happened before with the Cisco. I cleared the OSPF process on the Juniper M5 to force reelection of our Cisco 7206 as the BDR. The Cisco 7206 became the BDR once again, but the HiPer ARCs still could not reestablish their adjacency with the Cisco. As before they went into an Init, ExStart cycle. I'd hate to have to reboot a HiPer ARC everytime an OSPF BDR reelection occurs. On the other hand the failure to establish an adjacency with the BDR doesn't seem to be affecting the routing since they're adjacency with the DR is ok. Still this is somewhat annoying. Both HiPer ARCs are running 5.1.99 and installed in the same chassis. Anybody got any suggestions?