Rolling out rip with eigrp

[alialjamri2008]

We have heavy loaded network, almost full day, consisting of more than 60 L2/L3 3560 switches, which is initially configured with rip v2, and we need to roll out rip with eigrp, some one from the forum suggested to me to configured eigrp along with rip till neighbors forms and then to remove all rip configs., unfortunately I am not able to do this because of the traffic generated with eigrp, I first thought to adjust the hello and hold timers but this is not practical at least on our network.

Appreciate if any body suggest to me other good ideas.

Thanks

Ali

[mellowdrifter]

Change the AD of EIGRP to 255 and then configure EIGRP everywhere. Once you're happy with it change the EIGRP AD back to 90.

EIGRP doesn't create a lot of traffic at all

[JohnTylerPearce]

I agree with Darren, you will need to change the AD of EIGRP since it has an internal AD of 90, and RIP has an internal AD of 120. If you didn't then the EIGRP routes would be installed in the routing table over the RIP routes that you currently have. Also, this allow EIGRP to be running throughout your network while RIP is still used. Once yo uare satisfied with the way EIGRP is working in your network you can start turning off RIP obviosuly do all this on a maintenance window. EIGRP puts out less traffic than RIP, you will only have the first full routing table exchange, and then only updates, and updates pertaining to any changes or route addes, metric changes that you have. After the initial routing table exchange, the only thing you should really see in a stable EIGRP network are keepalives.