1 2 Previous Next 15 Replies Latest reply: Aug 16, 2014 8:14 AM by Amit RSS

    RIP static route redistribution

    durga

      I have been doing exercises from the exploraion books recently , I encountered a RIP redistricution of a static route.

      R1 <-->R0<-->R2 <-->S0 & S2

       

      RIP is running in all three routers and a static route has been configured from R2 to S1 and R2 to S2

      I could not understand the point why we are redistributing a static route ( of rip onto rip) when it could be as well broadcasted suing network command.

      Like the R2<-->S0 is a redistributed route to R1 and

      R2<-->S2 is a normal rip broadcasted route

      How are both functionalities different? is there  a benefit of using one over other??

      I undertand why we opt ofr redistribution when multiple protocols are being used in a network, but why would we wnat to redistribute same protocl network??

       

      Attaching the PT file

       

      P.S:I did go through few posts here on redistribution but could not find the information i am seeking

        • 1. Re: RIP static route redistribution
          Martin

          redistributing a static routes  will put those static routes into neighbors' routing table but will not create a default gateway/route;

          (unless you have ip route 0.0.0.0 0. 0.0.0 xy configured)

           

          default-information originate will add default route/gateway in RIP domain;

           

          the original router where those static are connected does not advertise those routes via RIP. so question is why not ?

           

          Message was edited by: Martin

          • 2. Re: RIP static route redistribution
            Kumar Mantri

            Hi Martin,

             

                 In router1 ,i negated the "redistribution static" and did "default information originate" when i did this the routing table in Router1 has changed to

             

            R    200.1.1.0/24 is possibly down, routing via 172.16.2.2, Serial2/0

            R    209.165.201.0/24 is possibly down, routing via 172.16.2.2, Serial2/0

            R*   0.0.0.0/0 [120/1] via 172.16.2.2, 00:00:06, Serial2/0

             

            here so what i observed is, if we give "redistribution static" means it gives all the static routes to the other or if we give "default information originate" then which ever the route it doesn't know it pass that to 172.16.2.2

             

            so the routing table gets reduced when we assign "default information originate" right? can u explain in detail how these both are helpful and when to use?

            • 3. Re: RIP static route redistribution
              Martin

              RIP is slow, so wait a bit or use clear ip ro * 

               

              I made correction above;

               

              Not sure what is purpose of that lab and why 3rd router does not advertise its connected routes;

              • 4. Re: RIP static route redistribution
                durga

                Hello Martin,

                 

                The purpose of the lab is that the third router wont advertise the statis routes through RIP, ( My question is almost the same, why cant these routes just be advertised through RIP?) but are statically conencted to the second router and the second router redistributes them to the first router .

                 

                 

                The intial lab had only one static route and second router was to redistribute it, I configured the second static route and published it through R2's RIP just to see what difference does both set ups make, I could not find any ( or may be I was careless).

                • 5. Re: RIP static route redistribution
                  Kumar Mantri

                  redistributing a static routes  will put those static routes into neighbors' routing table but will not create a default gateway/route;

                  (unless you have ip route 0.0.0.0 0. 0.0.0 xy configured)

                   

                  MARTIN  , i dont understand the statement above, that u mentioned "will not create default gateway/route" what does it mean?

                   

                   

                  Yeah i got it,suppose if we have two or more static routes then it will put all those static routes in the neibours routing table right?

                   

                  suppose i created both that is default route and all the static routes so which it will keep in th neighbours routing table with "redistribute static" command?

                  • 6. Re: RIP static route redistribution
                    Martin

                    ok, reducing routing table is always good idea;

                    if something else comes to mind, I let you know.

                    • 7. Re: RIP static route redistribution
                      Martin

                      Gateway of last resort is not set

                      and there is no route 0.0.0.0 like this:

                      R*   0.0.0.0/0 [120/1] via 172.16.2.2, 00:00:06, Serial2/0

                       

                      now, if  you add;

                      default-information originate

                      or

                      redistribute static and ip route 0.0.0.0 .0.00.0 x/y

                      you will get default route in the table;

                      (Gateway of last resort is set .... and one route will have * )

                       

                      Play with this lab and see differences; good exercise !

                      • 8. Re: RIP static route redistribution
                        Kumar Mantri

                        Martin, i found the difference, i think "default information originate" more efficient than "redistribute static"...because it adds only one single default route in the neibours routing table

                         

                        so why they designed both instead of keeping only "default information originate" command?is there any other purpose?

                        • 9. Re: RIP static route redistribution
                          Brian

                          You should actually remove the static routes from R0 and just run the RIP process for these networks on R2.  So, on R2 you would have the following:

                           

                          router rip

                          version 2

                          net 200.1.1.0

                          net 209.165.201.0

                           

                          In addition, I would run RIP version 2 on all routers since you have variable subnets in the topology.  You do not need to even worry about redistribution of static routes.

                           

                          I will post one possible solution in a bit.

                           

                          Brian

                           

                          • 10. Re: RIP static route redistribution
                            Brian

                            Now, you can leave RIP as Version 1, but network 209.165.201.0/30 will show as a /24 due to the "auto-summarization" feature of RIPv1.  It still works just fine.

                             

                            I noticed you have not yet configured either of the servers with an IP address.  was this intentional or just forgot?

                             

                            I just removed the static routes from R0 and added the network commands under the RIP process on R2.

                             

                            R2(config)#router rip

                            R2(config-router)#net 200.1.1.0

                            R2(config-router)#net 209.165.201.0

                            R2(config-router)#end

                            R2#

                             

                            Now, both R0 and R1 have the routes in their routing tables learned via RIP.

                             

                            R1#sh ip rou

                            Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

                                   D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

                                   N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

                                   E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

                                   i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

                                   * - candidate default, U - per-user static route, o - ODR

                                   P - periodic downloaded static route

                             

                            Gateway of last resort is not set

                             

                                 172.16.0.0/24 is subnetted, 4 subnets

                            C       172.16.1.0 is directly connected, FastEthernet0/0

                            C       172.16.2.0 is directly connected, Serial2/0

                            R       172.16.3.0 [120/1] via 172.16.2.2, 00:00:23, Serial2/0

                            R       172.16.4.0 [120/1] via 172.16.2.2, 00:00:23, Serial2/0

                            R    200.1.1.0/24 [120/2] via 172.16.2.2, 00:00:23, Serial2/0

                            R    209.165.201.0/24 [120/2] via 172.16.2.2, 00:00:23, Serial2/0

                            R1#ping 200.1.1.1

                             

                            Type escape sequence to abort.

                            Sending 5, 100-byte ICMP Echos to 200.1.1.1, timeout is 2 seconds:

                            !!!!!

                            Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/9 ms

                             

                            R1#

                             

                            R0#sh ip rou

                            Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

                                   D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

                                   N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

                                   E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

                                   i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area

                                   * - candidate default, U - per-user static route, o - ODR

                                   P - periodic downloaded static route

                             

                            Gateway of last resort is not set

                             

                                 172.16.0.0/24 is subnetted, 4 subnets

                            R       172.16.1.0 [120/1] via 172.16.2.1, 00:00:19, Serial2/0

                            C       172.16.2.0 is directly connected, Serial2/0

                            C       172.16.3.0 is directly connected, FastEthernet0/0

                            C       172.16.4.0 is directly connected, Serial3/0

                            R    200.1.1.0/24 [120/1] via 172.16.4.2, 00:00:01, Serial3/0

                            R    209.165.201.0/24 [120/1] via 172.16.4.2, 00:00:01, Serial3/0

                            R0#ping 209.165.201.1

                             

                            Type escape sequence to abort.

                            Sending 5, 100-byte ICMP Echos to 209.165.201.1, timeout is 2 seconds:

                            !!!!!

                            Success rate is 100 percent (5/5), round-trip min/avg/max = 2/4/6 ms

                             

                            R0#

                             

                            Once you complete the server configurations you should be able to ping from either laptop to the servers.

                             

                            HTH

                             

                            • 11. Re: RIP static route redistribution
                              durga

                              I had to remove the version 2, was trying to implement RIPv1 ans RIPv2and realised PT doesnot support interface command ' ip rip send version 1 2' , and had to revert all of them to v1.

                               

                              So Martin and Brian,

                              From your posts i see that there is no real point in re-distributing static routes,  they can as well be  just published through  'network' command.

                              • 12. Re: RIP static route redistribution
                                durga

                                thenon -configuration of IP addresses for servers though was not intentional, it was neither forgetten, I was more preoccupied thinking why should I even do a redistirbution.. thanks for the suggestions. will keep them in mind.

                                PS:giving my exam in sep , hopefully things turn out well.

                                • 13. Re: RIP static route redistribution
                                  Brian

                                  PT does not support the interface level commands.  You should still be ok with enabling version 2 under the RIP process.  I know it works there as I have done many labs in PT.

                                   

                                  Regarding the redistribution, it is not really necessary in this lab, yes.  There maybe a time when you need to redistribute static routes, but for this lab I do not think it is needed.  Of course if it was a requirement of the lab, then that is a different story.

                                   

                                  Best of luck to you on the exam.

                                   

                                  Brian

                                   

                                  • 14. Re: RIP static route redistribution
                                    Martin
                                    there is no real point in re-distributing static routes

                                    in this lab ? Yes, it looks like it;

                                     

                                    Redistribution is not on CCNA, isn't it?

                                     

                                    and RIP 1 configuration is also not tested on exam, although, you are expected to know differences between versions 1 and 2 : v.2 supports VLSM, discontinuous networks, etc.

                                    1 2 Previous Next