Answer the question
In order to leave comments, you need to log in
Two RIP routes with the same cost?
There is a relatively small network, several providers, IPSEC over GRE. 95% of the equipment is Cisco, of which more than 50% are the simplest routers (857/861). Currently, RIP is used as a dynamic routing protocol, because it is supported by all hardware. There was a need to make backup channels to some remote points: backup 2Mbps, main 10Mbps. Since RIP does not take into account the width of the channels, it turns out 2 equivalent routes, which is not buzzing. Found a solution: offset-list ACL in|out # interface#/# command. But it does not suit the convergence time when links fall. I started looking towards EIGRP (routers at those points allow it to be used). Now the question is:
Is it worth it to redistribute routes between EIGRP and RIP in the network, or is it better to leave only RIP and apply offset-list in the right places?
Answer the question
In order to leave comments, you need to log in
If the convergence time remains the only problem in using RIP, then you can try to fix the timers (config-router# timers basic), the main thing is not to overdo it. Regarding redistribution, without seeing the structure of your network and the size of the routing table, it is difficult to advise, but in my opinion it is worth trying to avoid it. Well, if the issue is acute, then it’s better to consider changing the protocol, for example, to ospf, I don’t think that in your case this will load routers any more than RIP, and as a bonus you will get a more accurate metric with the same protocol openness .
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question