Jim, I'm going to bring this one back public, if you don't mind. I think
there are some points worth studying.
I did a quick lab to test a couple of things. I'm going to have to ask
everyone to trust me that all things are configured correctly. I don't want
to spend all night copying configs and writing books.
First of all, I can find no evidence of EIGRP automatically redistributing
anything but IGRP, and that only if the IGRP process has the same process
number as does the EIGRP process. This is in line with my recollection of my
reading and studying. For all protocols other than EIGRP/IGRP, one must
manually redistribute.
Secondly, I think you can migrate to EIGRP from your RIP environment with
little worry. Check out the following:
1) I set up a RIP network on three routers. Here is the routing table:
Router#sh ip route
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
R 192.168.8.0/24 [120/2] via 192.168.254.5, 00:00:03, Serial1
R 192.168.9.0/24 [120/2] via 192.168.254.5, 00:00:03, Serial1
R 192.168.10.0/24 [120/2] via 192.168.254.5, 00:00:03, Serial1
R 192.168.11.0/24 [120/2] via 192.168.254.5, 00:00:03, Serial1
R 192.168.4.0/24 [120/1] via 192.168.254.5, 00:00:03, Serial1
R 192.168.5.0/24 [120/1] via 192.168.254.5, 00:00:03, Serial1
R 192.168.6.0/24 [120/1] via 192.168.254.5, 00:00:03, Serial1
R 192.168.7.0/24 [120/1] via 192.168.254.5, 00:00:04, Serial1
C 192.168.0.0/24 is directly connected, Loopback0
192.168.254.0/30 is subnetted, 2 subnets
C 192.168.254.4 is directly connected, Serial1
R 192.168.254.0 [120/1] via 192.168.254.5, 00:00:04, Serial1
C 192.168.1.0/24 is directly connected, Loopback1
C 192.168.2.0/24 is directly connected, Loopback2
C 192.168.3.0/24 is directly connected, Loopback3
Router#
Notice that all routes are RIP ( except for the directly connected )
2) I then configured EIGRP n all the routers. Here is the routing table:
Router#sh ip route
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
D 192.168.8.0/24 [90/2809856] via 192.168.254.5, 00:00:55, Serial1
D 192.168.9.0/24 [90/2809856] via 192.168.254.5, 00:00:55, Serial1
D 192.168.10.0/24 [90/2809856] via 192.168.254.5, 00:00:55, Serial1
D 192.168.11.0/24 [90/2809856] via 192.168.254.5, 00:00:55, Serial1
D 192.168.4.0/24 [90/2297856] via 192.168.254.5, 00:00:56, Serial1
D 192.168.5.0/24 [90/2297856] via 192.168.254.5, 00:00:56, Serial1
D 192.168.6.0/24 [90/2297856] via 192.168.254.5, 00:00:56, Serial1
D 192.168.7.0/24 [90/2297856] via 192.168.254.5, 00:00:57, Serial1
C 192.168.0.0/24 is directly connected, Loopback0
192.168.254.0/24 is variably subnetted, 3 subnets, 2 masks
C 192.168.254.4/30 is directly connected, Serial1
D 192.168.254.0/24 is a summary, 00:00:59, Null0
D 192.168.254.0/30 [90/2681856] via 192.168.254.5, 00:00:57, Serial1
C 192.168.1.0/24 is directly connected, Loopback1
C 192.168.2.0/24 is directly connected, Loopback2
C 192.168.3.0/24 is directly connected, Loopback3
Router#
Notice that all RIP routes have been replaced by EIGRP routes. Why? Because
EIGRP routes have a lower administrative distance than do RIP routes, and
therefore they are preferred, and therefore they are placed into the routing
table, overwriting the previous RIP routes.
I will not be so bold as to suggest that it is impossible for loops or other
problems to occur during the migration you propose. But I am suggesting that
with a bit of thought and planning, all things being equal, you should not
suffer major problems.
I believe that if you were to add the EIGRP process into the distant end
routers, install the appropriate network statements, then install the EIGRP
process onto your local routers, you will see fast convergence and a stable
network. If you have few enough routers, you can probably do this in a
couple of hours.
Caveats? Static routes. Redistributions that you are currently doing with
RIP. Typo's. Be sure to document everything. Write your scripts, proofread
them carefully, and follow them religiously.
HTH
Chuck
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jim
Dixon
Sent: Monday, September 25, 2000 8:10 AM
To: [EMAIL PROTECTED]
Subject: Converting RIP to EIGRP (Online)
I am looking for information on taking a RIP, Static Route, BGP
backbone, to EIGRP instead of Rip between access nodes All Routers are
Cisco, some 1601, 3640, 3620, 2610, 7507
I am concerned that when I turn EIGRP on, that it will auto redistribute
the RIP, probably causing a loop or two. Since this is a production net
with about 10 access nodes and 5 backbone nodes I cannot afford to be
down while I troubleshoot each loop.
(R1) ----- (Core 7507)
(R2) ----- (Core 7507)
(R3) ----- (Core1 3640) ----- (Core 7507)
(R4) ----- (Core1 3640) ----- (Core 7507)
All run RIP v2 and/or Static routes with passive interfaces on some of
client side routers.
I have looked at Cisco's website and other sites on the internet as well
as my books.
I am still not finding the "HOW to change routing protocols RIP to EIGRP
while avoiding problems" list of steps. Although I didn't find what I
was looking for I did find many pages on EIGRP on syntax, protocol
specifics, etc... which have not answered my questions yet.
If any of you on the list have done this before and have some references
that you could send to me I would really appreciate it.
**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]