Antonio Querubin wrote: > > > There are a dozen routers connected to a common 10.65.127.224/27 L2 > > backbone. All are running OSPF area 0. Any router which has the IP > > address 10.65.127.246 cannot establish OSPF adjacency with some other > > routers, showing them forever in the INIT/DROTHER or EXSTART/DROTHER > > state. > > > > When a different IP address is configured on the same router, the > > problem is solved. More over, when 10.65.127.246 is configured on ANY > > router in the segment, it experiences adjacency problems. > > > > We are currently using a workaround of never assigning 10.65.127.246 > > to any router. Is this Sauron's IP address, or is there some kind of curse > > thereon? > > Are you absolutely positively sure 10.65.127.246 still does not exist > somewhere else on one of the devices on that network, for example as a > stale router ID?
I know that a duplicate router ID should cause a message like "%OSPF-4-DUP_RTRID, and I have not seen this message in the logs. So am I not absolutely positively sure, but I am pretty sure. And I have posted a "show ip ospf database" output in another message. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/