Dec
30

To start my reading from Petr’s excellent CCDE reading list for his upcoming LIVE and ONLINE CCDE Bootcamps, I decided to start with:
EIGRP for IP: Basic Operation and Configuration by Russ White and Alvaro Retana
I was able to grab an Amazon Kindle version for about $9, and EIGRP has always been one of my favorite protocols.
The text dives right in to none other than the composite metric of EIGRP and it brought a smile to my face as I thought about all of the misconceptions I had regarding this topic from early on in my Cisco studies. Let us review some key points regarding this metric and hopefully put some of your own misconceptions to rest.

  • While we are taught since CCNA days that the EIGRP metric consists of 5 possible components – BW, Delay, Load, Reliability, and MTU; we realize when we look at the actual formula for the metric computation, MTU is actually not part of the metric. Why have we been taught this then? Cisco indicates that MTU is used as a tie-breaker in a situation that might require it. To review the actual formula that is used to compute the metric, click here.
  • Notice from the formula that the K (constant values) impact which components of the metric are actually considered. By default K1 is set to 1 and K3 is set to 1 to ensure that Bandwidth and Delay are utilized in the calculation. If you wanted to make Bandwidth twice as significant in the calculation, you could set K1 to 2, as an example. The metric weights command is used for this manipulation. Note that it starts with a TOS parameter that should always be set to 0. Cisco never did fully implement this functionality.
  • The Bandwidth that effects the metric is taken from the bandwidth command used in interface configuration mode. Obviously, if you do not provide this value – the Cisco router will select a default based on the interface type.
  • The Delay value that effects the metric is taken from the delay command used in interface configuration mode. This value depends on the interface hardware type, e.g. it is lower for Ethernet but higher for Serial interfaces. Note how the Delay parameter allows you to influence EIGRP pathing decisions without the manipulation of the Bandwidth value. This is nice since other mechanisms could be relying heavily on the bandwidth setting, e.g. EIGRP bandwidth pacing or absolute QoS reservation values for CBWFQ.
  • The actual metric value for a prefix is derived from the SUM of the delay values in the path, and the LOWEST bandwidth value along the path. This is yet another reason to use more predictive Delay manipulations to change EIGRP path preference.

In the next post on the EIGRP metric, we will examine this at the actual command line, and discuss EIGRP load balancing options. Thanks for reading!


You can leave a response, or trackback from your own site.

4 Responses to “The EIGRP Composite Metric – Part 1”

 
  1. Dragons & Faeries says:

    What’s the best EIGRP-related command?
    According to Brian Dennis, it’s “no eigrp”; I’d agree with Brian on this one. LOL!

  2. Zabeel Musa says:

    nice post! Thanks

  3. Ned says:

    How does EIGRP figure out the lowest bandwidth along a path in order to compute the metric. For eg if there are 4 routers A-B-C-D and the BW between A-B is 1000Mb, B-C is 100M and C-D is 10Mb, how does A know when calculating the route to reach a network connected to D that that the BW between C and D is the lowest?

    • @Ned

      C will receive prefix from D and use the bandwidth on the connection to D to build metric to be advertised to B. This goes on recursively, and every router in turn replaces the bandwidth in the composite metric for the prefix with the lowest value, comparing the local bandwidth on the receiving interface with the bandwidth learned in the update.

 

Leave a Reply

Categories

CCIE Bloggers