<P> The Routing Information Protocol (RIP) is one of the oldest distance - vector routing protocols which employ the hop count as a routing metric . RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from source to destination . The maximum number of hops allowed for RIP is 15, which limits the size of networks that RIP can support . A hop count of 16 is considered an infinite distance and the route is considered unreachable . RIP implements the split horizon, route poisoning and holddown mechanisms to prevent incorrect routing information from being propagated . </P> <P> Originally, each RIP router transmitted full updates every 30 seconds . In the early deployments, routing tables were small enough that the traffic was not significant . As networks grew in size, however, it became evident there could be a massive traffic burst every 30 seconds, even if the routers had been initialized at random times . It was thought, as a result of random initialization, the routing updates would spread out in time, but this was not true in practice . Sally Floyd and Van Jacobson showed in 1994 that, without slight randomization of the update timer, the timers synchronized over time . </P> <P> In most networking environments, RIP is not the preferred choice for routing as its time to converge and scalability are poor compared to EIGRP, OSPF, or IS - IS . However, it is easy to configure, because RIP does not require any parameters unlike other protocols . </P> <P> RIP uses the User Datagram Protocol (UDP) as its transport protocol, and is assigned the reserved port number 520 . </P>

Where do you change the timers for ripng