02-26-2015 03:34 AM - edited 03-05-2019 12:53 AM
Solved! Go to Solution.
02-26-2015 06:57 AM
Okay, that make sense, thought I had forgotten how RIP worked for a minute there :-)
I suspect you are right in that regardless of how you modify the route with your redistribute static RIP will see that as a connected route and simply advertise it out.
If I get the chance I'll have a look at in a lab today but I am not too hopeful.
I appreciate you have probably considered this and it may very well not be possible but have you though about using EIGRP instead.
It's more efficient in terms of routing updates etc, is the recommended protocol for DMVPN and more importantly for you is classless so it would mean that the route did not overlap with other spoke networks.
Jon
02-26-2015 04:03 AM
Carlos
Is there any way to avoid static routes becoming connected?
The general answer to this is yes, use a next hop IP instead of an interface.
But I'm not sure that would fix your problem.
If your RIP configuration includes network 10.0.0.0 then it is going to pick it up anyway with your redistribute static command.
You may be able to use a route map with your redistribution to filter out the routes you don't want.
Can you clarify what it is you are trying to do and why the company needs it.
Jon
02-26-2015 04:37 AM
Jon
Thanks for your answer
My bad. Sorry let me try to explain better.
The routing protocol we are using is rip and the main idea is to avoid that the new technicians from making the mistake of using the interface as next hop.
The redistribute static metric 16 wouldn´t redistribute the routes because it will recognize them as unreachable but it isn´t a solution since the router learns the route as connected/static and we have 2 tunnel interfaces pointing to the same next hop/router.
With the redistribute static metric 16 i´m filtering the redistribution of static routes including the one that has the interface as next hop but the router is also learning the route as conected so is redistributing the route as connected from the other tunnel
sorry if i cant explain it so well, english is not my main lenguage
Regards and thanks for taking your time to answer!
02-26-2015 05:22 AM
Carlos
No problem and believe me your English is a lot better than my ability to speak any other language :-)
You seem to be saying that you can stop it being redistributed by adding a metric but that because it is connected it is still being redistributed which I'm not quite following.
Could you perhaps give me an example from your network ie. the router configs regarding the tunnel and the RIP config and explain exactly what happens.
Jon
02-26-2015 06:24 AM
Jon
Thanks for your patience!
Here is the exact situation:
02-26-2015 06:26 AM
Carlos
Thanks for the detailed explanation.
One more clarification. In the second scenario where the static route via the tunnel is added to R1 are you saying RIP automatically redistributes this ?
I ask because the RIP configuration on R1 has no network statement for that network and there is no "redistribute static" under your RIP configuration so I'm not sure why it is being passed to R3 ?
Or because RIP is classful is the b.b.b.b network part of the t.t.t.t or v.v.v.v networks ?
Jon
02-26-2015 06:43 AM
Jon, thats correct.
I missed that part when writing the explanation.
The b.b.b.b network is of the v.v.v.v network.
And its being redistributed because of the "interface" on the static route that learns the static route as connected
02-26-2015 06:57 AM
Okay, that make sense, thought I had forgotten how RIP worked for a minute there :-)
I suspect you are right in that regardless of how you modify the route with your redistribute static RIP will see that as a connected route and simply advertise it out.
If I get the chance I'll have a look at in a lab today but I am not too hopeful.
I appreciate you have probably considered this and it may very well not be possible but have you though about using EIGRP instead.
It's more efficient in terms of routing updates etc, is the recommended protocol for DMVPN and more importantly for you is classless so it would mean that the route did not overlap with other spoke networks.
Jon
02-26-2015 07:18 AM
Dont worry Jon, if you want to do it, it would be a fun lab to do i guess! Running Eigrp is not possible sadly because the whole network (the 600+ nodes) are low end routers that only support rip. Im stuck with rip..
Thanks again for your time!
Regards
Carlos
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide