Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Changing RIP to EIGRP

Status
Not open for further replies.

chipk

IS-IT--Management
Joined
Mar 23, 2006
Messages
1,226
Location
US
I'm looking at changing my routing protocol, which is currently RIP v1 to EIGRP (exclusively Cisco network). Just wanted to see if anyone knows of any documentation, or specific gotchas/pitfalls to look out for in doing this. I have a working knowledge of routing - I've just never had to switch routing protocols before.

I've already got the Cisco documentation on the protocols themselves, I'm looking for specific info on changing over from one to the other. Thanks!
 
If I were you I would setup 2 spare routers and get them talking EIGRP so you understand the basic show/debug commands for troubleshooting. RIP vs. EIGRP has alot of differences. Also make a list of your subnets that are currently routed in RIP so you know what networks you need to announce in EIGRP.

Also take into consideration the fact that today you may have an all-Cisco network which is probably because they've been the leader in data networking for the past 10-20 years, however sometimes things change. You dont want to be stuck with a vendor-specific routing protocol in the event that you ever plan on adding a non-Cisco device to your routing protocol.

You should look at OSPF or IS-IS. EIGRP is very nice and fancy, and has the fastest convergence times however OSI routing protocols are also very nice and will not keep you locked to a specific vendor. I personally recommend running Integrated IS-IS because:

- support for IPV6
- fast convergence
- doesn't need network statements to announce IPV4 subnets (less chance of configuration problems due to user error).
- larger area sizes so chances are you probably can run your whole network in 1 area versus OSPF having to have multiple areas.

In my opinion EIGRP is good for:
- fastest convergence times
- unequal-cost load sharing

You have to weigh out your network needs and plan for future growth when choosing a new routing protocol to migrate to.


-Rainman
 
Hi,

Also keep in mind that if you need a solution in the future where cisco kit cannot be used.... say cough, a nortel device it wont support EIGRP.

LEEroy
MCNE6,CCNP,CWNA,CCSA,Project+
 
Thanks for your responses. I'm still probably going to stick with EIGRP because that's what my parent company uses, and so I have a lot of expertise available to me on it. If I do ever have to put a non-Cisco device on my network - I find it highly unlikely - I can redistribute my routes with OSPF or IS-IS as Rainman suggests.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top