In message <[email protected]> Fred Baker writes: > > On Oct 15, 2011, at 6:35 PM, Curtis Villamizar wrote: > > > All adjacencies have to go down to change router-id. The other end of > > the adjacency will withdraw its side of the adjacency. > > well, yes, and if I change my routerid, all adjacencies will go > down. Not sure what the point here is...
If you've just booted up and there is a one in a few million chance that you'll get half way on the database load on the first adjacency to come up and have to start over, then I don't think it is a big deal. If the point is what if you've been up and running for a while, then perhaps we need a holdup timer to see if the problem clear if one or more adjacencies has previously completed a full database load. This means that on a power up of everything, there will be merged islands with conflicts and the conflicts won't resolve until the holdup timer expires. Some advice on being slow to correct "staleness" in this situation would prevent the current OSPF staleness correction wars (each corrects the other as fast as it can if you manage to configure a conflict today - apparently common when people clone and edit configs but occasionally forget to change the router-id - I wouldn't know since we machine generated the configs where I used to play). Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
