4.3 RIPv2

Hi,

After fiddling with the SG's solution to this task for a while, I just can't get it to work. It seems to advertise the default out both f0/0 and f0/1 wether I use the SG's route-map or not... Am I the only student encountering this problem?

Another easy way to do this would be to "ip summary-address rip 0.0.0.0 0.0.0." on R4's f0/1.

Eric

Comments

  • After fiddling with the SG's solution to this task for a while, I just can't get it to work. It seems to advertise the default out both f0/0 and f0/1 wether I use the SG's route-map or not... Am I the only student encountering this problem?

    Another easy way to do this would be to "ip summary-address rip 0.0.0.0 0.0.0." on R4's f0/1.

    I also used ip summay-address for generating default route to sw2. I also think that this is a better and easy way of accomplish this task. SG uses a more comlicated solution in this case.

  • Hi Eric,

    Don't have lab with me, if requirement only says to generate default route, I also recommend to use ip summary-address command (easy method).

  • Hi,

    I did the summary-address as well, there are other ways to accomplish this task, but if the task itself do not limit you using one vs the other, you should be good.

    Just my 2 cents

  • I did the summary-address as well, there are other ways to accomplish this task, but if the task itself do not limit you using one vs the other, you should be good.

    There are other post on this, wherein people tried other methods like default-information originate but they could not get the desire results due to some other task in the lab. Though i have not tried that yet.

  • There are other post on this, wherein people tried other methods like default-information originate but they could not get the desire results due to some other task in the lab. Though i have not tried that yet.

    Here's the other post - in fact this stuff probably should have posted to this thread.

    Update - with the actual link this time :O

    http://ieoc.com/forums/t/18892.aspx

     

  • Contrary to what others above are posting, I don't believe you can generate a default route with RIP by using the "ip summary-address rip 0.0.0.0 0.0.0.0" command alone.  I tested in out for this task by configuring it on R4's F0/1 interface, but all it succeded in doing was suppressing all routes from being advertised to SW2.  It didn't advertise 0.0.0.0/0.  This effectively made SW2 isolated from the rest of the network.

    However, I agree with everybody that I don't think you can use a route-map this way with the default-information originate to "set" an interface to advertise the default to the way the SG demonstrates.  I ended up using default-information originate on SW2 and poisening 0.0.0.0/0 (via outbound offset list) to R5. It's kind of an ugly solution but the only one I could come up with considering the restriction of not using a distribute-list.

     


  • My solution is pretty much what the SG says, and a quick debug shows the defualt being sent to SW2 via fa0/1, and nowhere else, 

     

    !

    ! R4

    !

    conf t

    !

    route-map DEFAULT_TO_SW2

     set interface fa0/1

    !

    router rip

     default-information originate route-map DEFAULT_TO_SW2

    !

    end

     

     

     

     

    RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (156.8.48.4)

    RIP: build update entries

    0.0.0.0/0 via 0.0.0.0, metric 1, tag 0

    156.8.0.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.45.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.45.5/32 via 0.0.0.0, metric 1, tag 0

    156.8.54.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.57.0/24 via 0.0.0.0, metric 2, tag 0

    RIP: sending v2 update to 224.0.0.9 via Serial0/0/0.1 (156.8.0.4)

    RIP: build update entries

    150.8.8.0/24 via 0.0.0.0, metric 2, tag 0

    156.8.8.0/24 via 0.0.0.0, metric 2, tag 0

    156.8.45.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.45.5/32 via 0.0.0.0, metric 1, tag 0

    156.8.48.0/24 via 0.0.0.0, metric 1, tag 0

    RSRack8R4#

    156.8.54.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.57.0/24 via 0.0.0.0, metric 2, tag 0

    RSRack8R4#

    RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (156.8.54.4)

    RIP: build update entries

    150.8.8.0/24 via 0.0.0.0, metric 2, tag 0

    156.8.0.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.8.0/24 via 0.0.0.0, metric 2, tag 0

    156.8.45.0/24 via 0.0.0.0, metric 1, tag 0

    156.8.45.5/32 via 0.0.0.0, metric 1, tag 0

    156.8.48.0/24 via 0.0.0.0, metric 1, tag 0

     

    Id be interested on hearing others thoughts on this, as I feel like I have met the requirement of the task. 

     

    Marc


  •  

    My solution is pretty much what the SG says, and a quick debug shows the defualt being sent to SW2 via fa0/1, and nowhere else, 

     

     

    same here Marc.

  • but I had to use summary address because of issue described here:

    http://ieoc.com/forums/t/18892.aspx

     

Sign In or Register to comment.