In this post id like to provide an example of a fairly new development to EIGRP which is called EIGRP Over The Top (OTP). In all its simplicity it establish an EIGRP multihop adjacency using LISP as the encapsulation method for transport through the WAN network.

In the process of restudying EIGRP as a protocol, and more specifically as to how it converges, you can’t avoid running into the saying “Remember to bound your queries!”. From a conceptual point of view its fairly easy to understand that the further out you ask for a prefix the longer the convergence process will take.

Update: By most examinations, this seems to be a bug. A clever guy at the Cisco support forums might offer the reason why this happens. Thanks to everyone for clearing this up! (https://supportforums.cisco.com/message/3519430) I was trying someting out the other day concerning EIGRP when i ran into an issue i still cant explain, so i would like to put it out there for scrutiny.

So yesterday, I started with all the lab exercises that has to do with EIGRP. I did the one in the self-study guide, and one (2.7.1) in the lab portfolio. I also started on 2.7.2. So far, the labs in the labportfolio are far better written than the ones in the self-study guide.

Alright, I am done with reading about EIGRP. I am now skimming through the chapter, and taking notes. I have an okay understanding of how EIGRP works, and I am looking forward to the labs to nail out unknowns. I am not 100% convinced about taking notes, or rather doing it in the order im doing (reading first, then skimming and taking notes, then going to the lab).

Today, I am continuing reading about EIGRP. My goal for today is to get at least 40 pages of EIGRP reading done. Lots of nitty gritty details such as unequal-load balancing and route authentication. To understand and process the material, 10 pages takes up 30 minutes of reading time.

Chapter 3, EIGRP. Started reading about the inner workings of EIGRP today. EIGRP is an improved distance vector protocol provided by Cisco themselves. It is an improved distance vector protocol, because it passes updates directly to its neighbours. It is more advanced than traditional distance vector protocols, because it supports VLSM and it does not use periodic updates.