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

 

351 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 ive done the redistribution but I can’t seem to get router 1 to see the 192.168.23.0/24 network I can see the 1.1.1.0/24 network from router 3 and I can make it work if I put in the static route on router 1 so if router 3 pings router 1 from a source ip in the ospf area it can get back but i can’t get the network in it’s route table I’ve debugged routing on router 4 and its being told about the ospf network from router 3 but router 2 is not telling router 1 about the ospf network

  2. 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

  3. Hello Rene,

    If we go with the same approach by adding a route map like this when redistributing routes, will this resolve the AD metric issue on 1.1.1.0/24 route?

    route-map TAG deny 10
    match tag 1
    route-map TAG permit 20
    set tag 1

  4. Hello Ray,

    You could add that route-map to R2 and R4 so that R2 sets the tag and R3 doesn’t redistribute it back into OSPF because of the tag.

    That works, but it also means that the OSPF domain won’t know about the 1.1.1.0/24 network. If you have another router (let’s say R5) in the OSPF domain that needs that route, then you have a problem.

    Of course, it’s unlikely to see stuff like this on a production network but be very careful when reading the requirement(s) on an exam.

    Here is an example where you should use tags:

    https://cdn-forum.networklessons.com/uplo

    ... Continue reading in our forum

  5. Found a couple mistakes I think:

    The internal route was learned through EIGRP external (AD 170) and the internal route is learned through RIP (AD 120).
    The internal route was learned through BGP internal (AD 200) and the internal route is learned through OSPF (AD 110).

    I think the bolded 'internal’s should read ‘external’ instead.

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