“The important lesson I wanted to show you here is that EIGRP uses the slowest bandwidth in the path and the sum of delays” I don’t understand. Wasn’t it supposed to be the sum of the metric of the path links???
I mean…if R5 is announcing a route, (assuming lowest metric is through R2) the feseable distance from the point of view of R1 would not be the sum of the metric of the links R1-R2-R3-R5 + the metric announced by R5 for that given route?? I am pretty sure it is… but the result is not the same as depicted here so I am a bit confused.
As always very thanks in advance!!!
Hello Jorge
EIGRP doesn’t work like OSPF where you simply sum the metric of each link along the path to get a total cost for a path. The metric is assigned and is actually defined on a per-path basis using this metric formula. Actually, what Rene is describing here is the way in which metric is measured, by definition.
In this particular part of the lesson, we are calculating the metric from R1 to R5 using the path R1-R2-R3-R5. When we do so, we use the EIGRP metric formula. What do we put in the “bandwidth” variable? There are so many different bandwidths in the links between these routers! By definition, however, we use the lowest bandwidth only, in other words, the link which causes the bottleneck. Remember, we’re not calculating the metric on each link, but the metric for the total path. That’s how EIGRP works.
However, when it comes to the delay component of the metric, we count the cumulative delays introduced by all links, so we must sum them. Once again, this is by definition how we calculate metric in EIGRP.
Not quite. When R5 announces a route to, say its loopbak interface, that information will be propagated to R3, R2, and R1, and along the way, EIGRP will learn the delays and the bandwidths of each link. Once R1 receives this info, it will calculate the metric to the destination by first using the metric formula as we described, and then adding to that the metric announced by R5 to the destination in question.
PS in this lesson, we can assume that the destination being advertised by R5 is the interface directly connected to R3, so there is no “additional metric” announced by R5. So we’re looking purely at the metric from R1 to that particular interface only.
I hope this has been helpful!
Laz
What will happen if my FD is bigger than the 32bit ??
How it scales with RIB and whats the ranges ??
Hello Narad
The maximum value that you can get with the classic EIGRP formula is 4,294,967,295. Using an online EIGRP metric calculator, I tried to find the combinations that would exceed that value. In order to do so you must set the delay to an extremely large number, and most IOS versions limit this number to somewhere around 16 million. You must also set the load very high, and you must take into account the other K values.
The highest value I was able to get (limited to 16 million for the delay) was around 5,549,000,000, which is indeed larger than a 32 bit value can represent. However, such a scenario is so rare that it doesn’t affect the operation of EIGRP. In such cases, EIGRP will use the highest value of 4,294,967,295 for the result of that formula.
Of course, EIGRP wide metrics is a new way of calculating EIGRP metrics that uses a 64-bit value. However, this was done to make the metrics more accurate for high bandwidth interfaces and was not necessarily done in order to achieve higher metric values. You can find out more about this in the following lesson:
I hope this has been helpful!
Laz
HI Rene,
Could you explain a bit more the metric formula. In the OCG, the formula is presented as follows. Which does give different results.
Hello Artur
Rene uses the following in the lesson:
Metric = [K1*bandwidth + ((K2*bandwidth)/(256-load))+K3*delay]
In the above formula, it is assumed that K4 and K5 are zero, which is the default. He then says that if K4 and K5 are not equal to 0 then the formula becomes:
Metric =
Metric
*[K5/(reliability+K4)]
Where the second Metric
that I’ve bolded represents the whole first equation above. So if you write it all out, it becomes:
Metric = [K1*bandwidth + ((K2*bandwidth)/(256-load))+K3*delay]*[K5/(reliability+K4)]
Now, later in the lesson, Rene clarifies what bandwidth is:
Bandwidth= [10^7 / minimum bandwidth in the path] * 256. In the formula you shared, that 256 multiplier is applied outside of the brackets.
So ultimately, the formula is the same, however Rene has written it out differently. I will let Rene know to see if he can clarify the way the formula is written in the lesson to be clearer.
I hope this has been helpful!
Laz
Hi Laz,
Thanks for the explanation. I was quite confused when I first tried to compare the two!
Thanks.