ed_the_lad wrote: Any aspiring ccie student out there know why B doesnt begin a diffuse algorithm and C does? Since an update is received on B with a metric increase for the successor to 1.1.1.1/32, the FD on B will stay the same but the local distance to 1.1.1.1/32 will be increased,since the local distance is greater than the FD and no FSs are present shouldnt B perform a diffuse algorithm? Why B doesnt and C does? Anyone?
ed_the_lad wrote: Ok, i found the answer,when the metric is increased on A, since 1.1.1.1/32 is locally connected the FD will be increased and an update sent to B, B will modify its locally calculated distance (FD/AD) pair but leave the actual FD for the route the same(If FD was lower i.e. better it would be modified,since its higher the old FD is kept).If the (AD) stays below the actual FD,B will only send an update as the local calculation still results in a successor.If the value of (AD) raises above the actual FD a diffuse calc is required and queries will be sent.C in this case just happened to have its (AD) exceed the actual FD. Only took 2 or 3 days to figure out,if i continue like this i should have ccie by 2011 . Doyles explanation of the diffuse alogorithm is incorrect in both the old and new version.New version diffuse example 2,page 331,332.He ends up with the correct answer but his description of events isnt acurate,this along with other bad descriptions from other sources have caused me great mental pain but now since i understand it, i have a feeling of euphoria!