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 637 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

367 New Members signed up the last 30 days!

satisfaction-guaranteed

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

Tags:


Forum Replies

  1. I am curious…what is the difference in using stub and passive-interface for EIGRP? Having a bit of trouble wrapping my mind around separating these 2.

    Sincerely,
    Rob

  2. Hi Rob,

    There’s a big difference between the two. An EIGRP router that is configured as a stub does not receive queries when one of its neighbors loses a network.

    Passive-interface is about sending hello packets on an interface. Normally when you use the network command to advertise something then it does two things:

    1. It advertises all networks that fall within the range of your network commmand on all active interfaces.
    2. It sends hello packets on all active interfaces that have networks that fall within the range of your network command.

    When you enable passiv

    ... Continue reading in our forum

  3. Hello Hussein

    There are several specialised cases where the receive-only option is useful. Some of these include:

    1. When applying it to a dual homed stub router with more than one connection to the same EIGRP AS. In a Dual-homed scenario “receive-only” would prevent the stub router from becoming a transit router incase of link failure in your core and still have redundancy from the stubs perspective.
    2. When using a route server connected to an eBGP network
    3. When using DMVPN spokes.

    I hope this has been helpful!

    Laz

  4. Hi,

    Yes this is pretty much exactly what I said in my post.

    There are some specific use cases where you will need to allow a stub router to process queries (such as multihomed branch offices in a DMVPN deployment where if R1’s uplink fails, you have to reconverge through R2 etc).

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