We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 651 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

451 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. Hi Rene…


    What an awesome article… simple and nice explanation,…

  2. Hi Rene,

    This is all I have to say, THANK YOU! :clap::clap::clap:

    Complicated concepts, made very objective.

  3. thank you for your reply, from my understanding, router will share the reported AD from other router which means when R3 receives (AD=25 from R1) and (AD=19 from R2) so as a result --> R3 should send both AD’s to R4 and this does not make sense!

  4. Hi Ziad,

    In reality, when R3 receives an update from R1 or R2 about the destination behind R4, it won’t install them since these don’t pass the feasibility condition (AD of the feasible successor has to be lower than FD of successor).

    R3 will only advertise its successor route to other neighbors. In this topology, R4 is the successor route so normally R3 would advertise this route to R4. However, because of split horizon (don’t advertise a route to a neighbor if you learned that route from the neighbor)…this route is not advertised.

    It might be helpful to see a

    ... Continue reading in our forum

  5. The topology is being viewed from the standpoint of R3. We have the benefit here of seeing the full network topology, and you can trace if R3 used R1 or R2 as a feasible successor, to reach the destination, you’ll be going in a loop back to R3 (where you started).

116 more replies! Ask a question or join the discussion by visiting our Community Forum