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

452 Sign Ups in 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,

    Very useful topic , many thanks for this.

    Question 1

    with this command “ip route 11.11.11.0 255.255.255.0 null0 track 1”, do you mean that we have created static route for R1 via "default-information originate " command, due to reaching ip 192.168.23.3 from R2.

    when R2 can not reach R3 , “R2#default-information originate route-map TRACK_LINK” is autmatically removed and there is no default route for R1.

    Question 2

    when R1 state is like below,

    R1#show ip route rip
    R* 0.0.0.0/0 [120/1] via 192.168.12.2, 00:00:12, FastEthernet0/0
    

    Schould R3 be also like

    ... Continue reading in our forum

  2. Hi Onur,

    1. We need a "dummy" route, something that is in the routing table but it doesn't matter what it is or where it points to. In that case, it's best to point it to the null interface. I've added object tracking to this dummy router, it doesn't have anything to do with the default-information originate command (which is for the default route). When IP SLA fails, this dummy route will be removed from the routing table. The default route will disappear because the dummy route is now gone.
    2. That's right, R3 will also learn the default route from R2.
    Rene

  3. Hi Zaman,

    The route-map has the following match rule:

    match ip address prefix-list DUMMY_PREFIX

    And it is attached under the RIP process so it is actively monitored.

    Rene

  4. Hello Manuel.

    The dummy route that you indicated above will not work for two reasons. First the route must be in the format:

    ip route network-address subnet-mask Next-Hop-address/interface track1

    I believe you meant the following:

    ip route 0.0.0.0 0.0.0.0 192.168.23.3 track 1

    If this is the case, then this would not work either, because 0.0.0.0 0.0.0.0 is a legitimate route and would affect your routing. You must use a network address that does not exist in your topology. Also, it is always safer to use the null0 interface as the next hop interface so no acc

    ... Continue reading in our forum

  5. Hi Rene, rather than using the null interface here, would using the static route

    _ip route 192.168.23.3 255.255.255.255 F0/1 track 1_

    work the same?

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