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

 

295 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. Hi Rene,
    You explained the subject in a very detailed manner. Thanks a lot . No one actually have explained it like the way you done. Thanks a lot

    Ammar,
    CCIE R&S - in progress

  2. Hi Sergio,

    When you redistribute OSPF into EIGRP then it should advertise 192.168.23.0/24 to R4. You don't have to redistribute connected, that's only needed when the network is not advertised in OSPF.

    Rene

  3. Hi Sergio,

    Good to hear you figured it out. RIP and EIGRP require a seed metric, if you don't specify it then the metric will be infinite and it can't be installed in the routing table.

    Rene

  4. Yep, seed metric is key for those routing protocols. Won't forget now.

  5. Hi Shaun,

    First of all, let's forget about the static routes :slight_smile: With static routes we can make anything work but in this example, we are using routing protocols only.

    The problem with R1 and 192.168.23.0/24 is that R2 will never install a route from R4 about 192.168.23.0/24.

    Why? For R2, it's a directly connected network so whatever R4 advertises...the directly connected link is always preferred.

    If you want reachability to it from R1 then it's best to do a "redistribute connected" on R2, make sure you use a route-map so that only the FastEthernet0/0 interface is selected.

    Rene

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