LDP and ECMP
Load isis.cfg
ISIS is already pre-configured. Configure LDP on all routers using LDP IGP autoconfig.
Notice that R2 has ECMP routes in its RIB. How will R2 treat traffic sourced from 1.1.1.1 destined for 19.19.19.19 by default?
Answer
Explanation
LDP follows the IGP. So if there are ECMP paths in the IGP, both label bindings are installed in the LFIB.
We can check this by inspecting the LFIB entry for 19.19.19.19/32 on R2:
It just so happens that both R3 and R4 allocated the label 23 for 19.19.19.19/32.
We can verify which path will be used for traffic sourced from R1 using the following command:
By default, the CEF load-sharing algorithm is universal, which only uses L3 information, but uses a hash so that each router makes a different hashing calculation. So when we traceroute from R1, we should see that all traffic is forwarded out Gi2.23 only.
If we want, we can change the CEF load-sharing algorithm to include L4 flow information into the hash. This produces a different hop for each traceroute probe due to the different L4 port.
Last updated
