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


314 New Members signed up the last 30 days!


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

Tags: ,

Forum Replies

  1. Hey René,
    you missed something in the command syntax. After I have read your lesson, I tried the example. With the shown syntax John still doesn't advertise the Loopback addresses and the connected network. You probably wrote it in the lesson, but I had to complete:

    John(config)#router eigrp 12
    John(config-router)#redistribute rip
    John(config-router)#redistribute connected
    John(config)#router rip
    John(config-router)#redistribute eigrp 12
    John(config-router)#redistribute connected

    With this syntax, John started to advertise the Loopback and his directly connected networks. I hope it's no mistake from my side.

    Have a good one!

  2. Hi Sascha,

    That's right, this tutorial is just an overview of redistribution but I didn't show the full config. Here's the configuration example for those 3 routers:


    You don't have to use "redistribute connected" in this example. The /24 network has been advertised in EIGRP so it will be redistributed into RIP. The /24 network has been advertised in RIP so it will be redistributed into EIGRP. If we don't use the "network" command for these networks then you'll have to use redistribute connected.

    Oh and also be careful not to forget the seed metric...RIP and EIGRP require it or the metric will be infinite.


  3. Lazaros,
    Many thanks for your usual support

  4. Hello Subbu

    Yes you are correct, that should read "and advertise it to R1." not R3.

    I will let @ReneMolenaar know to change it.

    Thanks very much!


  5. Thanks for letting me know, just fixed this typo.

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