k values... quote of the day

don't change them... of course you will, to further understand why they should not be changed... if you screw with them in a production network, you get what you deserve...

here is the quote, from wendell and the gang:

From a design perspective, Cisco strongly recommends against using link load and link reliability in the EIGRP metric calculation. Most shops that use EIGRP never touch the k-values at all. However, in labs, it can be useful to disable the use of bandwidth from the metric calculation, because that simplifies the metric math, and makes it easier to learn the concepts behind EIGRP.

...useful to disable the use... WENDELL!!

a note on MTU...

MTV is NOT used in the calculation of eigrp, nor is MTU, contrary to some accounts...

the default is bandwidth and delay for the calculation

in this old post i present some bandwidth manipulation:

 http://insearchofthecert.blogspot.com/2011/12/bandaid-64.html

and here is another discussion from last year about successor's and feasibility:


http://insearchofthecert.blogspot.com/2011/12/successor-excess.html

memorize these requirements now: